General Page
There are two basic steps that need to be followed in order to prepare your z/OS data before sending it to IBM:
- Gather diagnostic data.
- IBM z/OS Software Support representative informs you what diagnostic data is required.
- Compress (fix block) and rename data
All diagnostic data delivered electronically to IBM must be in a compressed / fixed block format and following the IBM file naming convention starting with case number.
Options for z/OS datasets is utilizing:
Preferred, z/OS Utility z/OS Problem Documentation Upload Utility (PDUU), which compresses the datasets split the data into upload slices and upload the slices in parallel threads efficiently to IBM Support Upload systems using encrypted HTTPS or FTPS upload.
For more information about IBM PDUU, please refer to the most current z/OS MVS Diagnosis: Tools and Service Aids documentation.
Alternatively, z/OS clients can utilize AMATERSE service aid to compress their data sets [PACK parameter] which is part of z/OS and manually upload the data using a FTPS job to ECuRep FTPS upload server.
For more information about AMATERSE, please refer to the most current z/OS MVS Diagnosis: Tools and Service Aids documentation.
When using AMATERSE and FTPS upload, please ensure an appropriate naming convention wit file suffix .TRS
File naming convention for IBM My Support (CSP) cases: TS<xxxxxxxxx>.yyy.yyy.[TRS]
Example for an IBM My Support (CSP) case number: TS012345678.datasetname.TRS (TS<Case ID>.<datasetname>.TRS)
Special MVS data handling
To prevent problems with special MVS data (SMF data, GDG's etc.), review the information provided in Help section for handling Special Data.
Please note:
For z/OS Unix System Services (USS) files, do not use IBM PDUU or AMATERSE/FTPS, handling datasets.
For z/USS files, utilize the IBM SDDUU Java utility to compress and upload the data in parallel threads using HTTPS upload protocol instead.
Related links
Was this topic helpful?
Document Information
Modified date:
11 August 2026
UID
ibm10739607