Relay/Transfer MVS/TSO (Updated 10/2/1998)

1) What is Relay/Transfer for MVS/TSO?
Relay/Transfer TSO/ provides file transfer capability under TSO using the RELAY protocol with personal computers running Relay/Gold PC.

2) What is the currently support version?
Version 4.1 at zap level 1 plus zap999 is Y2K compatible; Version 5 became available June, 1998.

3) Is this product year 2000 compliant?
Version 4.1 zap 1 makes the product compatible with Year 2000; V5 is year 2000 compliant. Note: Version 4.10 will no longer be supported after December 31, 1998.

4) Is this product supported on OS/390?
It has been successfully tested on through OS390 2.5

5) How can I tell what zap level I have on the product?
There is a zaplog in the RELAYT.DATALIB which has the number of zaps applied when the product was shipped. If you cannot find a zaplog, look at the object or load module for RELAYTSO and you’ll see an eye-catcher ZAPS: R410M001R410M999 (example for V4.1).

6) 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 issuing a D M=CPU from the operator console. There is a ten-digit number under the word SERIAL, for instance:

SERIAL 1207729672 CPUID is 120772; CPU model is 9672.

Relay/TSO uses the last 4 digits of the serial number to generate a codeword. Zap 999 is required.

The Product Serial Number and the system (or check) code are in the object or load module; RELAYTSO. Browse either module for the eye-catcher

 PROGRAM SERIAL NUMBER: X412

001071C348485 23456712345671234567123456712345671

The Program Serial Number is X412001; the system/check code is 071. The C is the beginning of the codeword in the currently installed product.

7) I am getting message RXFR900S This product has not been properly installed!
This is usually a problem with the codeword being used. Be sure that you have followed the above procedure and have a codeword based on a 4-digit serial number if you are using the supported version of Relay/TSO.

If you are using Relay (RELAYTSO) on a backup machine or other machine than that for which the codeword was generated, you will get the same error because the codeword does not match the CPU serial number.

8) I am transferring several members to a PDS and suddenly the transfer stops. When I cancel the transfer I get the error message "FILE ERROR: SYSTEM CODE 'B14', RETURN CODE '004'. Why?
This error message means that the partitioned dataset (PDS) member already exists. Use the REPLACE file transfer option on the RELAY command in native TSO or when using ISPF panels, specify N for standard defaults in ISPF to use REPLACE.

9) Can I upload or download generation data sets with Relay/Transfer TSO?
When using Generation Data Sets, each file is automatically given a relative generation number which allows the user to create files with the same name and keep several versions.

On uploads:

Relay cannot do a GDG file transfer by the relative generation number because it uses the TSO ALLOCATE command that doesn’t support reference to GDG by relation generation number. You could use a batch program to create the new generation and refer to it with the absolute name for example create A.FILE.GDG(0) which is actually A.FILE.GDG.G001V001. You can upload to dataset A.FILE.GDG.G001V001 with the REPLACE option.

On Downloads:

You can download a GDG dataset if you know the actual name including the G00xV00 designation. For example, one of the members of a Generation Data Group may be A.FILE.GDG(0), which is actually A.FILE.GDG.G001V001. You can download the file A.FILE.GDG.G001V001.

10) What would prevent a file transfer from starting?
If you are using a protocol converter check the Relay/Gold KEY file for $PA2, located at the bottom of the file. It is required for going into protocol.

Some multi-session managers trap the PA2 key and prevent it from getting to the host. If you are using a session manager such as TeleView ™ and the switch is set to PA2 change it or try a test outside of the session manager.

If Relay/TSO is installed with a default protocol converter which is something other than what is actually used, try the transfer with the IBM3270 option.

If you are using DFT, TIC TN3270 or Relay/3270 emulating DFT, try the R3270 option on the RELAY command.

11) Does Relay/Transfer support SMS?
Relay/Transfer TSO V4.1 uses the TSO ALLOCATE command and supports DATACLAS, STORCLAS and MGMTCLAS as parameters. This version also supports PDS-E datasets.

12) How do I trace a Relay/TSO session?
Enter the command:

'RELAY UP file name 'any other opts' TRDUMP TRDATA(256) TRACE(9999)'.

All trace options will be used with the TRACE(9999) option.

A dataset with the TSO Userid as the high level qualifier,then TRACE.DATA will be written.

This file should be put on the Relay BBS or website. You must have Relay/Transfer V4.1 to use the trace option.

You may also have to trace from the PC side. You can start a trace as follows at a logical place prior to the error:

COAX Xtrace Start 1024 3270SNA Datafile

TIC Xtrace Start 1024 3270SNA Datafile

Gatewway Xtrace Start 1024 3270SNA Datafile

TN3270 Xtrace Start 1024 3270SNA Datafile

ASYNC Xtrace Start 1024 Frameio Datafile

When you have sucessfully recreated the issue you can stop the XTRACE with

XTRACE WRITE "filename" command. Send this as well to Relay via the BBS or website.

13) If a "File is Waiting to be Received" is not shown on the status line…
If you can download some files but not very large files from your mainframe to your PC try using the NOSIZE option on the RELAY command. This tells Relay/TSO not to try to determine the size of the file before sending it.

14) Undocumented options: SPEED and FAST NOWSF
SPEED(n) option specifies the pause before the next write. There could be multiple frames before a new write and the higher the number, the less the pause. The valid range (n) 0 -99.

FAST option turns off the SPEED option.

NOWSF does not check for a DFT device upon entering file transfer.

15) HOW TO DETERMINE WHAT OPTIONS WERE GENERATED IN RELAYTSO .
There is an object module called CHECKRLY which is shipped with the product or which can be downloaded from this Web site. The module is in RELAY format and can be uploaded to your TSO OBJLIB with the command: RELAY UP dataset(CHECKRLY) RELAY.

Once the module is in a PDS issue the following TSO commands:

ALLOC FI(RELAY) DSN('dataset(RELAYTSO)') the TSO object module you want to preview (be sure it’s the one you already installed.

LOADGO 'dataset(CHECKRLY)'

The subsequent listing will provide the following information:

PROCESSING: RELAY/TRANSFER (MVS/TSO): Vxxx

RELAY SERIAL NUMBER: X412001

RELAY SYSTEM CODE: 246

RELAY INSTALLATION CODEWORD(S):

C290516

LATEST APPLIED ZAP-ID: T400M014

SPECIAL ZAPS APPLIED:

SPECIAL ZAPS APP LIED:

EXPIRATION DATE/CODE: 999999/T261141

DEFAULT PROTOCOL CONVERTER TYPE: NONE (this parameter is important and can affect subsequent attempts to transfer files)

ACT COMPRESSION IS ENABLED

MAXIMUM I/O LENGTH FOR RELAY/3270 OR DFT MODE: 32768

USER INSTALLED EXIT:

PROCESSING COMPLETE!

Top