IBM
      Home   |   Products & services   |   Support & downloads   |   My account
Select a country
 
Fixes, drivers, updates, tools
Related links:
PartnerWorld
PartnerWorld for Developers

 
 
Recommended File Exchange Procedures

Recommended Procedures: Upload to IBM Level 2

  1. Open a problem record.

    Documentation can only be exchanged after an IBM problem managment record (PMR) is opened. Your 5 character PMR number with the 3 character branch office and 3 character country code will be used when naming files which are exchanged with IBM.

  2. Compress your file.

    z/OS customers should use the TRSMAIN program to compress your file [PACK parameter]. By compressing your data, you improve data transfer time, convert your file into a familiar record length and record format, and the original dataset characteristics are imbeded.

    Note: In z/OS Release 1.9 the TRSMAIN program has been added to the BCP element of z/OS, and it has been redesigned to support large format sequential data sets and has also been rewritten to follow IBM programming conventions. The new utility is called AMATERSE. You may use it instead of TRSMAIN if you are at z/OS Release 1.9, or have the fix for APAR OA19194 on z/OS Releases 1.7 or 1.8.

    TRSMAIN is shipped as an alias entry point to AMATERSE. When the TRSMAIN entry point of AMATERSE is invoked, ddnames INFILE and OUTFILE remain as the defaults, so little or no change to JCL should be required to take advantage of AMATERSE. The ddnames INFILE and OUTFILE that were required by the TRSMAIN utility are replaced by SYSUT1 and SYSUT2 respectively when the utility is called as AMATERSE.

    VM users should compress the file to be ftp'ed using the CMS COPYFILE command with the PACK option.

  3. When placing the file on the server use of the following naming convention will result in the automatic update the PMR and notify the support representative when the file is successfully uploaded.

    xxxxx.bbb.ccc.yyy.yyy.[TRS][.CRY | .CRY64]
    Where

    xxxxx
    PMR Number
    i.e. 34143
    bbb
    Branch Office
    i.e 055
    ccc
    IBM Country Code
    i.e. 000
    yyy.yyy
    A short description for the file type
    i.e. dump1
    TRS
    Identifier for a tersed file
    CRY
    Optional additional Identifier for non-DES encrypted file (FTPENCR module is used)
    CRY64
    Optional additional Identifier for 64-bit DES encrypted file (FTPENCRD module is used)

    Example
    34143.055.724.dump.TRS.CRY
    (PMR_#.branch_office_#.country_code.dump.TRS.CRY)


  4. Upload your file with binary protocol.

    Upload your file using binary transfer mode to testcase.boulder.ibm.com into the proper subdirectory. The subdirectory to use should be supplied to you by Level 2.

  5. Contact Level 2.

    Notify Level 2 that you have successfully tranfered your file to the testcase server. Inform them that you compressed the file with TRSMAIN, or, for VM, COPYFILE with the PACK option, and that you used the binary transfer protocol. This will speed up the process of downloading your file at the IBM Level 2 site.



Recommended Procedures: Download from IBM Level 2

  1. Verify file location.

    Check the testcase.boulder.ibm.com site under the proper subdirectory to verify that the file from IBM Level 2 is available for you to download.

  2. Verify file format.

    Verify that IBM Level 2 has compressed the file with the TRSMAIN program for z/OS, or that they have used COPYFILE with the PACK option for VM, and that the binary protocol was used when uploading the file.

  3. Download your file with binary protocol.

    IBM Level 2 should use the same procedure above (TRSMAIN + binary transfer, or for VM, COPYFILE with the PACK option or TERSE, + binary transfer) when placing the file onto the testcase.boulder.ibm.com server. Download your file from testcase.boulder.ibm.com using binary transfer protocol.

  4. Uncompress your file.

    z/OS: Using the TRSMAIN program, uncompress your file [UNPACK parameter].

    VM: Use COPYFILE with the UNPACK option or the DETERSE MODULE depending on if COPYFILE with PACK or TERSE was used.



   About IBM   |   Privacy   |   Legal   |   Contact