[ Home | Evals | Support | Buy | Investors | Search ]
  Subsribe to the NewMange SOA Newsletter  
NetManage Worldwide Sites
 
  Technical Support
  Legacy
  Solutions
    Search Knowledgebase
    FAQs
    Technical Documents
  Downloads
    Patches, Fixes and Updates
    Manuals and Guides
  Legacy Products FAQ


Relay/Transfer CICS (Updated 10/2/1998)

1) What is Relay/Transfer CICS?
Relay/Transfer CICS (MVS and VSE) provides file transfer capability under as a CICS transaction using either VSAM data, spool data or data in transient data queues. It uses the Relay protocol in conjunction with personal computers running Relay/Gold PC.

2) What is the currently support version?
Version 2.0.1 at zap level 12 (VSE) or 10 (MVS)

3) Is this product year 2000 compliant?
Zap 9 makes the products year 2000 compatible.

4) Is the MVS version supported on OS/390?
Yes, it has been tested with OS/390 2.5 and CICS/4.1.

5) Is this product supported with the latest versions of CICS?
Yes it is written at the CICS macro level.

6) How can I tell what zap level I have on the product?
Using the RL00 transaction, select 1) Maintain Control Parameters. From that screen choose P8 - Zap List and a list of the applied zaps will be displayed.

7) I need a new codeword; where do I find the information about my current product?
If you are a new user of the product, contact NetManage (Vienna) with the Product Serial Number of your tape, your CPU model and group number and the CPUID (CPU serial number). This can be obtained by the RL02 transaction that displays the CPUID, as follows:

CPUID: 0207729672

CPUID is 20772; CPU model is 9672.

If you are a current user of Relay/Transfer CICS V2.0:

The information you need is available by invoking the RL02 transaction as above. The CPUID, Product Serial Number, System/Check Code and current codeword information are displayed on that screen.

8) I cannot download a spool file.
Be sure the System Initialization Table specifies SPOOL=YES.

VSE: do a D LST

F1 0001 1R46I C200D009 01176 3 D B 1 9 1 TO=(UZER) FROM=(SIE1)

MVS, from SDSF look at the O queue:

AJOB1 TSU00928 AJOB 9 B STD UZER

The transfers don’t depend on the Filename (Jobname) for the spool file but on the class and

userid or destination (DEST) files. Change the DEST in VSE with the Alter command and in JES2 with the $T command.

Enter the following in the Relay/CICS Download Screen:

FILENAME C200D009 (jobname)

SPL/TDQ/TSQ SPL (spool file)

R3270 OPTION Y (if needed)

USERID UZER (TO=(username) from D LST

CLASS B (PRT class from D LST

9) My transfer hangs at the Banner Screen:
Specify R3270 OPTION Y under PROTCOL OPTIONS if you are using a coax connection (DFT), a gateway connection, a TN3270 connection.

If you set R3270 OPTION Y when you are coax (CUT) you will get a PROG403 and the session will drop. The Relay/CICS log will have the following message:

RLY094E "TERMINAL I/O ERROR, SESSION TERMINATED"

10) File transfer shows 0 characters transferred
If a coax CUT connection try the following:

  • Specify MAXMSG 2048 on PC (in Modify Connection/Settings/Advanced)
  • Specify FRAMESIZE 512 (same as above)
  • Be sure that R3270 OPTION N is set (the default)

11) How to print from the Power queue to a PC printer. (VSE ONLY)
If the Spool files you download are losing the control characters (form feeds), there is an exit in Relay/Transfer CICS V2.0 called RLYPCFM which converts machine code characters from the Power queue spool file to PC format and allows correct printing. Specify RLYPCFM in the EXIT PGM field on the Relay/CICS download screen.

12) BAD OR MISSING MEMBERS when IVP transaction is used.

If you run RIVP, a program used to verify that all of the necessary programs can be found in Relay/Transfer CICS and you get the above message:

The RIVP in the Relay CICS/MVS isn't looking for the correct file name or isn’t looking in the correct place. Disregard this step.

The RIVP in Relay CICS/VSE does work and if it saying files are missing they probably are so recheck the installation to be sure all of the files were included and you added the Relay group with the CEDA transaction.

13) Closing files at end of transfer
If you choose the CLOSE option on the Relay/CICS Upload Screen, the file will be closed but at the first occurrence of access, the file will be reopened by CICS. If you want to keep the file closed you must also use DISABLE Y option along with the CLOSE Y option.

14) Causes of ATCV abends during CICS transfer
If you are making a CUT connection (protocol converter or coax CUT) and you specify R3270 OPTION Y (indicating a DFT connection) you can get this abend as an I/O related problem.

If you disconnect the terminal while the transfer is going, you may get this abend.

Be sure to apply zap 8 on CICS/MVS for ATCV problems.

In your scripts, be sure to have a WAIT UNTIL RECVING/RECVFILE/WAIT WHILE RECVING when doing multiple file transfer.

15) How to get a Relay/CICS Trace
Go into Option 1 from the RL00 screen; reset the trace file by putting an R in TRACE STATUS, hit PF5.

Go to the upload/download screen and supply the DSN i in the appropriate field with all of the options you were using PLUS a Y in the TRACE field; perform the transfer (PF5).

Go into option 5 (View Trace File) from RL00 screen. If you want the file printed, put a Y next to the print option and hit enter.

If you want to change userid or print class do it before hitting enter.

If you want the file on disk, go to the Download screen and for data set use RLYTRC with the options CRLF=N, NOCONVERT=Y; then the file can be uploaded and printer.

For more information pertaining to Relay/Transfer CICS,
please send e-mail to:
   support@netmanage.com .
Top
    [ Contact Us | Site Map | Legal | Feedback ]