A primary migrated CDAM dataset conforms to the following naming convention:
pmigpref.jobname.jobid.datetime.fileid
where pmigpref is the file name prefix. Based on the length of the DSNPREF parameter in the IOASPRM member in the IOA.PARM library, which should be the same as the length of the IXHPREF parameter in the CTVPARM member, the file name prefix structure can be built in one of the following ways:
For example, if DSNPREF=M and the original CDAM file prefix is CTDP.L2, pmigpref is MCTDP.L2.
For example, if DSNPREF=M6 and the original CDAM file prefix is CTDP.L2, pmigpref is CTDP.ML2.
A secondary migrated CDAM dataset conforms to the following naming convention:
smigpref.jobname.jobid.datetime.fileid
where smigpref is the file name prefix. Based on the length of the SECPREF parameter in the IOASPRM member in the IOA.PARM library, which should be the same as the length of the IXHPREF parameter in the CTVPARM member, the file name prefix structure can be built in one of the following ways:
For example, if SECPREF=S and the original CDAM file prefix is CTDP.L2, smigpref is SCTDP.L2. If SECPREF=S6 and the original index file prefix is CTDP.L2, smigxpref is CTDP.SL2.
The other qualifiers are copied from the original CDAM dataset name. For more information, see the CDAM chapter in the Control-D and Control-V User Guide.
For both primary and secondary migration, the datetime field has the following format:
datetime
This field is a Control-V generated timestamp. When a CDAM dataset migrates from disk to the level 01 target media, this field remains prefixed by the letter D. This letter is replaced by the next letter in alphabetical sequence during each stage of the multistage migration or refresh.
Parent Topic |