This section provides examples dealing with the following subjects:
combining save files
moving save files from S1 to S2
Moving node save files from S1 to S2
combining save files
Various archive operations have been performed to several save files on several cartridges. These save files are to be combined. Combination is only possible and feasible for migration and long-term archives.
The new save file still contains the original save versions.
/START-HSMS //COPY-SAVE-FILE ARCH-NAME=$SYSHSMS.HSMS.AR.2BY, - ——————————————————— (1) // S-F-ID=S.160812.142005,SAVE-F=*NEW, - // TO-STOR=*S2-STOR(VOL=*FROM-POOL), - // OPER-CONTROL=*PAR(REPORT=*FULL,OUT=HSMS.MAN.R.CSF.13, - // WAIT-F-C=*YES) % HSM0003 HSMS STATEMENT COMPLETED //COPY-SAVE-FILE ARCH-NAME=$SYSHSMS.HSMS.AR.2BY, - ——————————————————— (2) // S-F-ID=S.160812.142018,SAVE-F=*CONT(S-F-ID=*LATEST), - // TO-STOR=*S2-STOR, - // OPER-CONTROL=*PAR(REPORT=*FULL,OUT=HSMS.MAN.R.CSF.14, - // WAIT-F-C=*YES) % HSM0003 HSMS STATEMENT COMPLETED //END % HSM0014 HSMS PROGRAM TERMINATED
Report HSMS.MAN.R.CSF.13 (extract): —————————————————————————————————— (3)
*** COPY-SAVE-FILE HSMS V12.0 FULL REPORT *** 2016-08-12 14:21:53 PAGE 3
REQUEST-NAME=CSF#0AAK REQUEST-DATE=2016-08-12 14:21:40 USER-ID=SYSHSMS REQUEST-STATE=COMPLETED WITHOUT ERROR
SAVE FILE IDENTIFIER - S.160812.142142
SUBSAVE
NUMBER VSNS
0 HSMS33
SAVE FILE IDENTIFIER - S.160812.142142
*** CATALOG - 2BY USER - MANUAL ***
** OUTPUT SAVE VERSION: SAVE-VERSION-DATE=16-08-12 SAVE-VERSION-TIME=14:21:43 *
FILE/JOB VARIABLE NAME LASTPG/ SAVE INPUT DEV SUB OUTPUT
VERS SIZE TYPE VSN TYP SAVE VSN(S)
FILE.01 1 3 FULL HSMS11 T 0 HSMS33
FILE.02 1 8 FULL HSMS11 T 0 HSMS33
FILE.03 1 13 FULL HSMS11 T 0 HSMS33
FILE.11 1 3 FULL HSMS11 T 0 HSMS33
FILE.12 1 8 FULL HSMS11 T 0 HSMS33
FILE.13 1 13 FULL HSMS11 T 0 HSMS33
FILE.21 1 3 FULL HSMS11 T 0 HSMS33
FILE.22 1 8 FULL HSMS11 T 0 HSMS33
FILE.23 1 13 FULL HSMS11 T 0 HSMS33
*** E N D O F HSMS V12.0 FULL REPORT *** 2016-08-12 14:21:53 ***
Report HSMS.MAN.R.CSF.14 (extract): —————————————————————————————————— (4)
*** COPY-SAVE-FILE HSMS V12.0 FULL REPORT *** 2016-08-12 14:23:51 PAGE 3
REQUEST-NAME=CSF#0AAK REQUEST-DATE=2016-08-12 14:21:54 USER-ID=SYSHSMS REQUEST-STATE=COMPLETED WITHOUT ERROR
SAVE FILE IDENTIFIER - S.160812.142142
SUBSAVE
NUMBER VSNS
0 HSMS33
SAVE FILE IDENTIFIER - S.160812.142142
*** CATALOG - 2BY USER - MANUAL ***
** OUTPUT SAVE VERSION: SAVE-VERSION-DATE=16-08-12 SAVE-VERSION-TIME=14:21:57 *
FILE/JOB VARIABLE NAME LASTPG/ SAVE INPUT DEV SUB OUTPUT
VERS SIZE TYPE VSN TYP SAVE VSN(S)
FILE.04 1 18 FULL HSMS22 T 0 HSMS33
FILE.05 1 16 FULL HSMS22 T 0 HSMS33
FILE.06 1 11 FULL HSMS22 T 0 HSMS33
FILE.14 1 18 FULL HSMS22 T 0 HSMS33
FILE.15 1 16 FULL HSMS22 T 0 HSMS33
FILE.16 1 11 FULL HSMS22 T 0 HSMS33
FILE.24 1 18 FULL HSMS22 T 0 HSMS33
FILE.25 1 16 FULL HSMS22 T 0 HSMS33
FILE.26 1 11 FULL HSMS22 T 0 HSMS33
** OUTPUT SAVE VERSION: SAVE-VERSION-DATE=16-08-12 SAVE-VERSION-TIME=14:21:58 *
MAX-SIZE.1 1 277 FULL HSMS22 T 0 HSMS33
MAX-SIZE.3 1 14998 FULL HSMS22 T 0 HSMS33
*** E N D O F HSMS V12.0 FULL REPORT *** 2016-08-12 14:23:51 ***
//MODIFY-ARCHIVE ARCH-NAME=$SYSHSMS.HSMS.AR.2BY, - ——————————————————— (5) // SAVE-F=*DEL(S-F-ID=(S.160812.142005,S.160812.142018)) % HSM0003 HSMS STATEMENT COMPLETED //SHOW-ARCHIVE ARCH-NAME=$SYSHSMS.HSMS.AR.2BY,SEL=*VOLUMES ———————————— (6)
SHOW-ARCHIVE (VOLUMES) ARCHIVE-NAME = $SYSHSMS.HSMS.AR.2BY VOLUME-STATE = ANY -------------------------------------------------------------------------------- VSN SFID VOLUME-STATE EXP-DATE DEVICE OWNER HSMS11 AVAILABLE TAPE-C4 POOL HSMS22 AVAILABLE TAPE-C4 POOL HSMS33 S.160812.142142 OBSOLETE 16-08-12 TAPE-C4 POOL ... NEXT-PAGE: + (+, -, ++, --, E) % HSM0012 END OF OUTPUT LIST REACHED
% HSM0003 HSMS STATEMENT COMPLETED //END % HSM0014 HSMS PROGRAM TERMINATED
(1) | The save file identified by the SFID is copied to a new save file. The volume is taken from the archive pool. |
(2) | Another save file is copied. Specifying CONTINUE=*LATEST causes the save file created via the preceding COPY-SAVE-FILE statement to be continued. Both of the old save files are now in a save file on cartridge, as indicated by the reports. |
(3) | The report of the first copy requests is output. |
(4) | The report of the second copy requests is output. |
The two reports list the save files and the files contained in them. Both reports have the same SFID. | |
(5) | Both of the original save files are released. |
(6) | The HSMS11 and HSMS22 cartridges have been released. Only the HSMS33 cartridge to which data has just been written is still in use. |
Moving save files from S1 to S2
In this example the backups of the DMS files are to take place first at S1 level instead of S2 level. These are regularly moved from S1 level to S2 level provided the save versions have already been residing at S1 level for more than three days.
Daily backup with the BACKUP-FILES statement:
//BCF FILE-NAMES=DMS. - // ,SELECT-FILES=*ALL-FILES - // ,ARCHIVE-NAME=MANUAL.DMS - // ,TO-STORAGE=*S1-STORAGE-LEVEL - // ,OPERATION-CONTROL=*PARAMETERS(REPORT=*FULL,OUTPUT=#2)
Overview of the save versions after three saves, before MOVE-SAVE-FILE
SHOW-ARCHIVE (SAVE-VERSIONS) INFORMATION = SUMMARY ENVIRONMENT = SF ARCHIVE-NAME = $SYSHSMS.MANUAL.DMS SV-NAME = ANY SV-DATE = INTERVAL EARLIEST LATEST USER-ID = OWN EXP-DATE = ANY -------------------------------------------------------------------------------- M SAV-DATE SAV-TIME EXP-DATE SFID SEL-F BC IND USER-ID SV-NAME 16-05-12 16:41:02 16-05-14 S.160512.164102 ALL-F D SYSHSMS 16-05-13 08:59:33 16-05-13 S.160513.085933 MOD-F D SYSHSMS 16-05-14 15:50:13 16-05-14 S.160514.155013 MOD-F D -------------------------------------------------------------------------------- NEXT-PAGE : + (+, -, ++, --, E) % HSM0012 END OF OUTPUT LIST REACHED
Moving all save versions that have been on S1 for more than three days
The MOVE-SAVE-FILES statement was executed on 16.05.16:
//MSF ARCHIVE-NAME=MANUAL.DMS - // ,FROM-STORAGE=*DISK(MINIMUM-DAYS-ON-DISK=3) - // ,OPERATION-CONTROL=*PARAMETERS(REPORT=*FULL,OUTPUT=#1)
Overview of the save versions after three saves, after MOVE-SAVE-FILE
SHOW-ARCHIVE (SAVE-VERSIONS) INFORMATION = SUMMARY ENVIRONMENT = SF ARCHIVE-NAME = $SYSHSMS.MANUAL.DMS SV-NAME = ANY SV-DATE = INTERVAL EARLIEST LATEST USER-ID = OWN EXP-DATE = ANY -------------------------------------------------------------------------------- M SAV-DATE SAV-TIME EXP-DATE SFID SEL-F BC IND USER-ID SV-NAME 16-05-12 16:41:03 16-05-12 S.160516.110025 ALL-F D SYSHSMS 16-05-13 08:59:34 16-05-13 S.160516.110025 MOD-F D SYSHSMS 16-05-14 15:50:13 16-05-14 S.160514.155013 MOD-F D -------------------------------------------------------------------------------- NEXT-PAGE : + (+, -, ++, --, E) % HSM0012 END OF OUTPUT LIST REACHED
Overview of the save files after MOVE-SAVE-FILE
SHOW-ARCHIVE (SAVE-FILES) INFORMATION = SUMMARY ENVIRONMENT = SF ARCHIVE-NAME = $SYSHSMS.MANUAL.DMS SAVE-FILE-STATE = ANY SAVE-FILE-STORAGE = ANY CREATED-BEFORE = LATEST EXPIRATION-BEFORE = LATEST -------------------------------------------------------------------------------- M SFID CREA-DATE EXP-DATE OBS ACCESS ST DEVICE #VOL #SV #RUNS S.160514.155013 16-05-14 16-05-14 YES OWNER PUB 1 1 S.160516.110025 16-05-16 16-05-16 YES OWNER TAP TAPE-C4 1 2 1 -------------------------------------------------------------------------------- NEXT-PAGE : + (+, -, ++, --, E) % HSM0012 END OF OUTPUT LIST REACHED
Moving node save files from S1 to S2
The example shows the moving of all S1 save files to S2 level for node files with shadow archive.
Rather than at S2 level, all the node files should first be saved at S1 level (for example because of hardware maintenance of the tape units). Subsequently all S1 saves are moved to S2 level. The archive is assigned a shadow archive.
Three saves are performed on public disk (S1 level) using the BACKUP-NODE-FILES statement:
//BNF PATH-NAMES=*PATH-NAME(PATH=/manual) - // ,ARCHIVE-NAME=MANUAL.NF - // ,SELECT-FILES=*MODIFIED-FILES - // ,TO-STORAGE=*PUBLIC-DISK(PUBSET-ID=DUB) - // ,OPERATION-CONTROL=*PARAMETERS(REPORT=*FULL,OUTPUT=#1)
Save versions and save files after three saves
Main archive
SHOW-ARCHIVE (SAVE-VERSIONS) INFORMATION = SUMMARY ENVIRONMENT = SF ARCHIVE-NAME = $SYSHSMS.MANUAL.NF SV-NAME = ANY SV-DATE = INTERVAL EARLIEST LATEST USER-ID = OWN EXP-DATE = ANY -------------------------------------------------------------------------------- M SAV-DATE SAV-TIME EXP-DATE SFID SEL-F BC IND USER-ID SV-NAME 16-05-19 13:13:57 16-05-19 S.160519.131355 MOD-F SYSHSMS 16-05-19 13:14:43 16-05-19 S.160519.131441 MOD-F SYSHSMS 16-05-19 13:15:24 16-05-19 S.160519.131522 MOD-F SYSHSMS -------------------------------------------------------------------------------- NEXT-PAGE : + (+, -, ++, --, E) % HSM0012 END OF OUTPUT LIST REACHED
SHOW-ARCHIVE (SAVE-FILES) INFORMATION = SUMMARY ENVIRONMENT = SF ARCHIVE-NAME = $SYSHSMS.MANUAL.NF SAVE-FILE-STATE = ANY SAVE-FILE-STORAGE = ANY CREATED-BEFORE = LATEST EXPIRATION-BEFORE = LATEST -------------------------------------------------------------------------------- M SFID CREA-DATE EXP-DATE OBS ACCESS ST DEVICE #VOL #SV #RUNS S.160519.131355 16-05-19 16-05-19 YES OWNER PUB 1 1 S.160519.131441 16-05-19 16-05-19 YES OWNER PUB 1 1 S.160519.131522 16-05-19 16-05-19 YES OWNER PUB 1 1 -------------------------------------------------------------------------------- NEXT-PAGE : + (+, -, ++, --, E) % HSM0012 END OF OUTPUT LIST REACHED
Shadow archive
The shadow archive is still empty. Saves to S1 level/public disk have not yet been taken over into the shadow archive!
The saves are moved to S2 level using the MOVE-SAVE-FILES statement:
//MSF ARCHIVE-NAME=MANUAL.NF - // ,ENVIRONMENT=*NODE-STD - // ,OPERATION-CONTROL=*PARAMETERS(REPORT=*SUMMARY,OUTPUT=#1)
Save versions and save files after the move
Main archive
SHOW-ARCHIVE (SAVE-VERSIONS) INFORMATION = SUMMARY ENVIRONMENT = SF ARCHIVE-NAME = $SYSHSMS.MANUAL.NF SV-NAME = ANY SV-DATE = INTERVAL EARLIEST LATEST USER-ID = OWN EXP-DATE = ANY -------------------------------------------------------------------------------- M SAV-DATE SAV-TIME EXP-DATE SFID SEL-F BC IND USER-ID SV-NAME 16-05-19 13:13:58 16-05-19 S.160519.131806 MOD-F UNDEF 16-05-19 13:14:44 16-05-19 S.160519.131806 MOD-F UNDEF 16-05-19 13:15:25 16-05-19 S.160519.131806 MOD-F UNDEF -------------------------------------------------------------------------------- NEXT-PAGE : + (+, -, ++, --, E) % HSM0012 END OF OUTPUT LIST REACHED
SHOW-ARCHIVE (SAVE-FILES) INFORMATION = SUMMARY ENVIRONMENT = SF ARCHIVE-NAME = $SYSHSMS.MANUAL.NF SAVE-FILE-STATE = ANY SAVE-FILE-STORAGE = ANY CREATED-BEFORE = LATEST EXPIRATION-BEFORE = LATEST -------------------------------------------------------------------------------- M SFID CREA-DATE EXP-DATE OBS ACCESS ST DEVICE #VOL #SV #RUNS S.160519.131806 16-05-19 16-05-19 YES OWNER TAP TAPE-C4 1 3 1 -------------------------------------------------------------------------------- NEXT-PAGE : + (+, -, ++, --, E) % HSM0012 END OF OUTPUT LIST REACHED
Shadow archive
SHOW-ARCHIVE (SAVE-FILES) INFORMATION = SUMMARY ENVIRONMENT = SF ARCHIVE-NAME = $SYSHSMS.MANUAL.NF.SH SV-NAME = = ANY SAVE-FILE-STORAGE = INTERVAL EARLIEST LATEST USER-ID = OWN EXP-DATE = ANY -------------------------------------------------------------------------------- M SAV-DATE SAV-TIME EXP-DATE SFID SEL-F BC IND USER-ID SV-NAME 16-05-19 13:13:58 16-05-19 S.160519.131806 MOD-F UNDEF 16-05-19 13:14:44 16-05-19 S.160519.131806 MOD-F UNDEF 16-05-19 13:15:25 16-05-19 S.160519.131806 MOD-F UNDEF -------------------------------------------------------------------------------- NEXT-PAGE : + (+, -, ++, --, E) % HSM0012 END OF OUTPUT LIST REACHED
SHOW-ARCHIVE (SAVE-FILES) INFORMATION = SUMMARY ENVIRONMENT = SF ARCHIVE-NAME = $SYSHSMS.MANUAL.NF.SH SAVE-FILE-STATE = ANY SAVE-FILE-STORAGE = ANY CREATED-BEFORE = LATEST EXPIRATION-BEFORE = LATEST -------------------------------------------------------------------------------- M SFID CREA-DATE EXP-DATE OBS ACCESS ST DEVICE #VOL #SV #RUNS S.160519.131806 16-05-19 16-05-19 YES OWNER TAP TAPE-C4 1 3 1 -------------------------------------------------------------------------------- NEXT-PAGE : + (+, -, ++, --, E) % HSM0012 END OF OUTPUT LIST REACHED