![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
2. Upload to your z/OS system the ostarrec.bin file to a data set with LRECL=80 and RECFM=FB, in BINARY format.
3. Copy the OSTARREC file produced to a data set in your SYSPROC or SYSEXEC concatenation.
6. In ISPF 3.4, type OSTARREC against the uploaded data set. You are then prompted for data set names, as documented for the TSO receive command, into which the following data sets should be stored:
− OSTAREDC, an optional load module to improve the performance of OSTARXMT and OSTARREC
9.
In z/OS Release 1.9, the TRSMAIN program was added to the BCP element of z/OS; so you do not need to download or install it. The main program is called AMATERSE, but the alias TRSMAIN is maintained for compatibility with the previously downloadable version.
− When prompted, give the name of the load library where you want the TRSMAIN program restored.
− Change the constant after the equal sign to contain the full data set name of the program. The string must start with a double quote and a single quote, and end with a single quote and a double quote, because the double quotes delimit the string and the single quotes tell TSO that the data set name is fully qualified. For example:
1. Use OSTARXMT, on the source z/OS system, to package multiple data sets into one sequential XM1 or XM2 data set.If the resultant data set is larger than the CHUNKSIZE value specified, the XM1 and XM2 data sets are divided into multiple smaller data sets with suffixes of XMxFnn. For details on the difference between the XM1 and XM2 formats, see Data Set Formats.
2. Make the XM1 or XM2 data set available to TIBCO Support by FTPing the data set to ftp.objectstar.com for download via the Internet.
3. Load the XM1 file, in binary format, to a sequential z/OS data set with LRECL=1024 and RECFM=FB.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |