Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Appendix E Data Transmission for z/OS : Error Messages

Error Messages
The OSTARXMT and OSTARREC programs may produce error messages. Other than typing or usage errors, the most likely error is that the ALLOCATE commands used to create work and output data sets do not conform to specific site standards, or do not allocate big enough data sets for some large sets of objects. In this case, find the message listed in this section and modify the appropriate ALLOCATE command in the REXX program. Inform TIBCO Support via a z/OS service request of any such problem.
OSTARXMT Messages
 
OSTARXMT wants to create a data set but a data set with that name already exists. Rename or delete the existing data set and try again.
OSTARXMT cannot find the data set. Check that the name was typed correctly using normal TSO naming standards. (If the name is not in single quotes, it is prefixed with your user ID.) If the name is correct, check that the data set is not migrated. If you had a typing error, correct it and retry.
Either the output data set filled up, the volume is full, or you do not have write access to the data set. If the output data set has gone to 16 extents, increase the size allocated for SYSUT1.
The DCB information of the data set is not supported by OSTARXMT. Review the data set’s DCB information. If you think it is valid, contact TIBCO Support.
Only some of the datasets were processed. % is valid.
OSTAREDC program not available.
The procedure was unable to find the OSTAREDC program. Refer to steps # and #9 of “Installation of OSTARXMT and OSTARREC” on page 1.
Unable to allocate file % with DISP=NEW.
The data set may already exist. Otherwise, see other TSO messages and modify the allocation for SYSUT1 to conform to local standards.
The TSO TRANSMIT command failed to write the input data set to the work data set. If this is a large data set, try increasing the size of the work data set allocated via SYSUT2. Otherwise, check preceding TSO errors.
Workfile 'SYSUT2' allocation failure.
The procedure was unable to allocate a temporary work data set. See other TSO messages and modify the allocation for SYSUT2 to conform to local standards.
OSTARREC Messages
 
OSTARREC wants to create a data set but a data set with the specified name already exists. Rename or delete the existing data set and try again.
DSN % suffix % is not XMT, XM1, or XM2.
For OSTARREC to know how to uncompress the file, it needs to know the type of file is supplied. Match the file suffix to the correct type of file.
OSTARREC is unable to allocate a temporary work data set. Modify the allocation for SYSUT2 to conform to local standards.
File level error checking failed.
The end of file record has invalid checksum information (it has been corrupted in transit). Download the file again from the server ensuring that you use binary FTP and that there are no errors. Another cause may be that the LRECL is not 1024.
Incomplete XMT dataset. End of file record not found.
After uncompressing an XM1 or XM2 file, the uncompressed work file did not have a valid end of file record. Download the file again from the server ensuring that you use binary FTP and that there are no errors.
INMR152I RECEIVE FAILED. SENDER'S NODE ID NOT RECOGNIZED.
This message is produced by the TSO RECEIVE command, which is used, under the covers, by OSTARREC. It is produced when the TSO TRANSMIT/RECEIVE customization has not been performed at the site when TSO/E was installed.
Input dataset is %. You need a new version of OSTARREC.
Invalid input dsn %. Invalid header.
The input data set does not start with the expected header information. Possible causes are a transmission error or a wrong input data set used.
Invalid LRECL=% for dataset with sfx=%.
The logical record length of the data set is incorrect. XMT files should have an LRECL of 88. For XM1 or XM2 files, the LRECL should be 1024. Correct the data set LRECL.
Record level error checking failed.
A record has invalid checksum information (it has been corrupted in transit). Download the file again from the server ensuring that you use binary FTP and that there are no errors.
Record/file level error checking failed.
Data set validation failed. Transmission error. Download the file again from the server ensuring that you use binary FTP and that there are no errors.
TRSMAIN not available. Cannot decompress data.
OSTARREC cannot find the TRSMAIN program needed to decompress the input file. For information on identifying TRSMAIN to the program, refer to Implementing the Compression Option.
Allocation of the specified data set failed. Check other error messages. Possible causes are security violations or exclusive shares. Also check that the names used exist or do not exist as required.
Unable to find dataset %. Respecify.
Unable to uncompress %. RC=%.
The temporary work data set allocated via SYSUT2 is not big enough. Find the allocate statement for SYSUT2 and increase the size.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved