Enhanced Customer Data Repository
There are three basic steps that need to be followed in order to prepare your z/OS data.
- Gather diagnostic data.
- Your IBM SSR will inform you what diagnostic data is required.
This could be probably the use of z/OS Management Facility (z/OSMF) Incident Log.
- Your IBM SSR will provide you with a Problem Management Record number (PMR). Write this down.
- Compress data
- All diagnostic data delivered electronically to IBM must be in a compressed or packed format following the IBM file naming convention. Use the IBM file naming convention as shown below. This will be provided to you by your IBM SSR.
- z/OS clients should use the AMATERSE service aid to compress their data sets [
PACK parameter] which is part of z/OS. By compressing the data, you improve data transfer time and convert your files into a familiar record length and format. For more information about AMATERSE, please refer to the most current z/OS MVS Diagnosis: Tools and Service Aids documentation.
To meet additional security requirements, it is possible to instead of using AMATERSE.
- Note: To prevent problems with special MVS data (like e.G. SMF data, GDG's etc.), please see the document: ECuRep – Handling of MVS Special Data (PDF,36KB)
- Another option to compress (optionally encrypt) and to transfer data under z/OS is the usage of z/OS utility z/OS Problem Documentation Upload Utility (PDUU)
- File naming convention: xxxxx.bbb.ccc.yyy.yyy.[TRS]
- Example: 34143.055.724.dump.TRS (PMR_#.branch_office_#.country_code_#.dump.TRS)
||Branch office number
||Short description of the file
||Mandatory Identifier for a tersed file
- Send data