|
|
 |
MVS or z/OS
File naming convention
When you create the terse archive, using the following naming
convention allows the support tools to move the testcase automatically
to the proper directories and update the PMR to indicate that
the testcase is available.
If the testcase files cannot be associated with an existing
PMR, they will be tagged as lost and eventually deleted.
xxxxx.bbb.ccc.yyy.yyy.[TRS][.CRY | .CRY64] --->
| xxxxx |
PMR Number |
34143 |
| bbb |
Branch Office |
055 |
| ccc |
IBM Country Code |
724 |
| yyy.yyy |
A short description for the file type |
dump |
| TRS |
Mandatory 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)
Take care to use the binary option before transfer.
Some additional remarks:
- to reduce reaction time, inform your IBM software support
about the transfered files
- the material will be automatically deleted after 7 days
- the FTP GET and LS options are intentionally disabled
- we strongly recommend to transfer files in a tersed format (using TRSMAIN)
|
|
| |
|
|
|
