This section provides examples dealing with the following subjects:
Automatic full and partial backup using repeat jobs
Backup to S1 with and without compression
Partial backup after catalog modification
- Version backup in SM environment
with corresponding notes on restoration.
An example of backing up the archive directory and restoring an archive together with archive directory is provided in the section "Example of long-term archival".
Automatic full and partial backup using repeat jobs
Weekly full backups and daily partial backups are implemented via automatically initiated repeat jobs.
/.FULLSAVE SET-LOGON-PARAMETERS TSOS ————————————————————————————————— (1) / START-HSMS //MODIFY-ARCHIVE ARCHIVE-NAME=HSMS.BACKUP - —————————————————————————— (2) // SAVE-FILES=*DELETE(SAVE-FILE-ID=*BY-ATTR - // (SAVE-FILE-STATE=*OBSOLETE)) //BACKUP-FILES FILE-NAMES=*ALL, - ———————————————————————————————————— (3) // SELECT-FILES=*ALL-FILES, - // ARCHIVE-NAME=*SYSBACKUP, - // SAVE-FILE=*NEW(RETENTION-PERIOD=14, - // USER-ACCESS=*ALL-USERS), - // TO-STORAGE=*S2-STORAGE-LEVEL, - // OPERATION-CONTROL=*PAR(REPORT=*FULL, - // OUTPUT=MANUAL.REPORT.FULL, - // EXPRESS-REQUEST=*YES) //END / SET-JOB-STEP / EXIT-JOB SYSTEM-OUTPUT=*DELETE /.PARTSAVE SET-LOGON-PARAMETERS TSOS —————————————————————————————————— (4) / START-HSMS //BACKUP-FILES FILE-NAMES=*ALL, - ———————————————————————————————————— (5) // SELECT-FILES=*MODIFIED-FILES(PARTIAL-FILE-SAVE=*YES - // (MINIMUM-SIZE=200)), - // ARCHIVE-NAME=*SYSBACKUP, - // SAVE-FILE=*NEW(RETENTION-PERIOD=14, - // USER-ACCESS=*ALL-USERS), - // TO-STORAGE=*S1-STORAGE-LEVEL, - // OPERATION-CONTROL=*PAR(REPORT=*FULL, - // OUTPUT=MANUAL.REPORT.PART, - // EXPRESS-REQUEST=*YES) //END / SET-JOB-STEP / EXIT-JOB SYSTEM-OUTPUT=*DELETE /enter-job hsms.e.full-save,proc-admis=(user-id=tsos, - —————————————— (6) / account=adminstr),start=at(date=*today,time=21:00),repeat-job=*weekly % JMS0066 JOB 'FULLSAVE' ACCEPTED ON 16-08-12 AT 14:27, TSN = 0ABW /enter-job hsms.e.part-save,proc-admis=(user-id=tsos, - —————————————— (7) / account=adminstr),start=at(time=23:30),repeat-job=*daily % JMS0066 JOB 'PARTSAVE' ACCEPTED ON 16-08-12 AT 14:27, TSN = 0ABY
(1) | ENTER file HSMS.E.FULL-SAVE |
(2) | Before backup, MODIFY-ARCHIVE is used to release the obsolete save files so that magnetic tape cartridges from the volume pool are available for the subsequent backup run. The archive cannot be specified in symbolic form here. |
(3) | The BACKUP-FILES statement specifying a weekly full backup is issued: all files on all pubsets are saved to the system backup archive in their entirety; the saved files cannot be deleted for the next two weeks. |
(4) | ENTER file HSMS.E.PART-SAVE |
(5) | The BACKUP-FILES statement specifying daily incremental and partial backup is issued: those pages which have been modified since the last full save in all files larger than 200 pages on all pubsets are saved; all files smaller than 200 pages are saved in their entirety if they have been modified since the last incremental backup. |
(6) | The batch task for a full save is started; it is repeated once a week. |
(7) | The batch task for partial backup is started; it is repeated once a day. On the day on which both tasks are started the full save is executed somewhat earlier. The result is that the subsequent partial backup will be (virtually) empty. |
Users can obtain the most recent status of a file (a file which has been inadvertently deleted, for example) from this system backup by issuing the following HSMS statement:
//RESTORE-FILES FILE-NAMES=<file name>
The file is restored, and, depending on the global HSMS parameter OUTPUT, a report is output on the printer or sent as an email attachment. From this archive, users can also restore any status of a file from the last 14 days.
Earlier versions of the file can be selected via the SELECT-SAVE-VERSIONS operand.
Backup to S1 with and without compression
Files are saved to a backup archive on storage level S1, once with and once without compression of the save file. The save files are compared.
Files are restored from the compressed save file.
//BACKUP-FILES FILE-NAMES=$MANUAL.FILE.*, - —————————————————————————— (1)
// SELECT-FILES=*ALL-FILES, -
// TO-STORAGE=*S1-STORAGE-LEVEL, -
// ARCHIVE-NAME=*SYSBACKUP, -
// SAVE-FILE=*NEW, -
// OPERATION-CONTROL=*PAR(REPORT=*FULL, -
// OUTPUT=HSMS.MAN.R.BCF.1, -
// WAIT-FOR-COMPLETION=*YES)
% HSM0003 HSMS STATEMENT COMPLETED
//END
% HSM0014 HSMS PROGRAM TERMINATED
Report HSMS.MAN.R.BCF.1 (extract): ———————————————————————————————— (2)
*** BACKUP - FILES HSMS V12.0 FULL REPORT *** 2016-08-12 15:57:53 PAGE 2
REQUEST-NAME=BCF#0AAK REQUEST-DATE=2016-08-12 15:57:37 USER-ID=SYSHSMS REQUEST-STATE=COMPLETED WITHOUT ERROR
% ARC0002 STATEMENT ACCEPTED. ARCHIVE SEQUENCE NUMBER 'A.160812.155740', VERSION '11.0' % ARC0033 ARCHIVE
SUBTASK TSN '0AAL' GENERATED
SAVE FILE IDENTIFIER - S.160812.155738 SAVE-VERSION-DATE=16-08-12 SAVE-VERSION-TIME=15:57:38
SUBSAVE NUMBER VSNS 0 0:2BC
/START-HSMS
//BACKUP-FILES FILE-NAMES=$MANUAL.FILE.*, - —————————————————————————) (3)
// SELECT-FILES=*ALL-FILES, -
// TO-STORAGE=*S1-STORAGE-LEVEL, -
// ARCHIVE-NAME=*SYSBACKUP, -
// SAVE-FILE=*NEW, -
// COMPRESS-FILES=*YES, - ——————————————————————————————————————————— (4)
// OPERATION-CONTROL=*PAR(REPORT=*FULL, -
// OUTPUT=HSMS.MAN.R.BCF.2, -
// WAIT-FOR-COMPLETION=*YES)
% HSM0003 HSMS STATEMENT COMPLETED
//END
% HSM0014 HSMS PROGRAM TERMINATED
Report HSMS.MAN.R.BCF.2 (extract): ———————————————————————————————— (5)
*** BACKUP - FILES HSMS V12.0 FULL REPORT *** 2016-08-12 15:58:12 PAGE 3
REQUEST-NAME=BCF#0AAK REQUEST-DATE=2016-08-12 15:57:53 USER-ID=SYSHSMS REQUEST-STATE=COMPLETED WITHOUT ERROR
% ARC0002 STATEMENT ACCEPTED. ARCHIVE SEQUENCE NUMBER 'A.160812.155755', VERSION '11.0' % ARC0033 ARCHIVE
SUBTASK TSN '0AAM' GENERATED
SAVE FILE IDENTIFIER - S.160812.155757 SAVE-VERSION-DATE=16-08-12 SAVE-VERSION-TIME=15:57:57
SUBSAVE NUMBER VSNS 0 0:2BC
/SHOW-FILE-ATT FILE-NAME=$MANUAL.FILE.*,INFORMATION=SPACE-SUMMARY ————— (6) :2BY: PUBLIC: 21 FILES RES= 270 FRE= 45 REL= 27 PAGES /SHOW-FILE-ATT FILE=:2BC:$*.ARCHIVE.SAVE.FILE.010812.155738., - / INFORMATION=SPACE-SUMMARY :2BC: PUBLIC: 1 FILE RES= 255 FRE= 2 REL= 0 PAGES /SHOW-FILE-ATT FILE=:2BC:$*.ARCHIVE.SAVE.FILE.010812.155757., - / INFORMATION=SPACE-SUMMARY :2BC: PUBLIC: 1 FILE RES= 30 FRE= 2 REL= 0 PAGES //RESTORE-FILES FILE-NAMES=$MANUAL.FILE.*, - ————————————————————————— (7) // REPLACE-FILES-AND-JV=*YES, - // ARCHIVE-NAME=*SYSBACKUP, - // SELECT-SAVE-VERSIONS=*LATEST, - // OPERATION-CONTROL=*PAR(REPORT=*FULL, - // OUTPUT=HSMS.MAN.R.RSF.1, - // WAIT-FOR-COMPLETION=*YES) % HSM0003 HSMS STATEMENT COMPLETED //END % HSM0014 HSMS PROGRAM TERMINATED
(1) | The files named FILE. of user ID MANUAL are saved to the system backup archive on S1. |
(2) | Extract from the HSMS-generated report of the save run with output of the SFID. |
(3) | The same files are saved once again, but this time ... |
(4) | ... the data is compressed during writing. |
(5) | Extract from the HSMS-generated report of the save run with output of the SFID. |
(6) | Comparison of the saved files with the save files to which they were written shows the reduced space requirements of the compressed save file. |
(7) | The files are restored from the compressed save file. Decompression need not be explicitly specified, the data is decompressed automatically. |
Partial backup after catalog modification
This backup resembles an incremental backup. All files are backed up which were modified after the specified time.
In the example below 5 files (FILE1, FILE2, ..., FILE5) are backed up according to this procedure:
The files are modified or deleted and occasionally saved after a full backup.
After the 3rd. day the files are restored again.
1st day: Date: 14.04.2016
/START-HSMS //CREATE-ARCHIVE ARCHIVE-NAME=archive, - // ALLOWED-USAGE=*BACKUP(SAVE-FILE-STRUCTURE=*SEVERAL-SVID), - // DIRECTORY-NAME=archive.dir, - // RETENTION-PERIOD=100 //BACKUP-FILES FILE-NAMES=file*, - // SELECT-FILES=*ALL-FILES, - // ARCHIVE-NAME=archive, - // OPERATION-CONTROL=*PAR(REPORT=*FULL,OUTPUT=l.archive) //END
After the full backup FILE2 is modified and FILE3 deleted.
2nd day: Date: 15.04.2016
/START-HSMS //BACKUP-FILES FILE-NAMES=file*, - // SELECT-FILES=*BY-CATALOG-MODIFICATION - // (CHANGED-AFTER=*LATEST-SAVE-VERSION-DATE), - // ARCHIVE-NAME=archive, - // OPERATION-CONTROL=*PAR(REPORT=*FULL,OUTPUT=l.archive) //END
After the backup with *BY-CATALOG-MODIFICATION (here all files that have been modified since the last backup on 14.04.) files FILE2 and FILE4 are modified and FILE5 deleted.
3rd day: Date: 16.04.2016
/START-HSMS //BACKUP-FILES FILE-NAMES=file*, - // SELECT-FILES=*BY-CATALOG-MODIFICATION, - // ARCHIVE-NAME=archive, - // OPERATION-CONTROL=*PAR(REPORT=*FULL,OUTPUT=l.archive) //END
After the backup with *BY-CATALOG-MODIFICATION (here all files that have been modified since the last backup on 15.04.) the archive has the following content:
//SHOW-ARCHIVE ARCHIVE-NAME=archive,SELECT=*SAVE-VERSIONS
... (Extract of the output)
M SAV-DATE SAV-TIME EXP-DATE SFID SEL-F BC IND USER-ID SV-NAME
16-04-14 10:20:02 16-07-23 S.160414.102001 ALL-F D UHU
16-04-15 10:12:44 16-07-24 S.160415.101243 CAT-F D UHU
16-04-16 09:26:12 16-07-25 S.160416.092611 CAT-F D UHU
//SHOW-ARCHIVE ARCHIVE-NAME=archive
... (Extract of the output)
M FILE-NAME VERS SAV-DATE SAV-TIME EXP-DATE TYPE FILE1 1 16-04-14 10:20:02 16-07-23 FULL FILE2 1 16-04-14 10:20:02 16-07-23 FULL FILE2 1 16-04-15 10:12:44 16-07-24 FULL FILE2 1 16-04-14 10:20:02 16-07-23 FULL FILE4 1 16-04-14 10:20:02 16-07-23 FULL FILE4 1 16-04-16 09:26:12 16-07-25 FULL FILE5 1 16-04-14 10:20:02 16-07-23 FULL
Restore of all files:
//RESTORE-FILES FILE-NAMES=*ALL, - // ARCHIVE-NAME=archive, - // OPERATION-CONTROL=*PARAMETERS(REPORT=*FULL,OUTPUT=l.restore)
With this all files FILE1 through FILE5 are restored, regardless of whether they have been deleted in the meantime.
/SHOW-FILE-ATTRIBUTES FILE-NAME=file*,INFORMATION=*PAR(HISTORY=*YES) %00000003 :SBZ3:$UHU.FILE1 % ------------------------------- HISTORY ------------------------------- % CRE-DATE = 2016-02-17 ACC-DATE = 2016-02-17 CHANG-DATE = 2016-02-17 % CRE-TIME = 14:15:21 ACC-TIME = 14:15:21 CHANG-TIME = 14:15:21 % ACC-COUNT = 1 S-ALLO-NUM = 0 %00000003 :SBZ3:$UHU.FILE2 % ------------------------------- HISTORY ------------------------------- % CRE-DATE = 2016-04-15 ACC-DATE = 2016-04-15 CHANG-DATE = 2016-04-15 % CRE-TIME = 10:18:32 ACC-TIME = 10:18:32 CHANG-TIME = 10:18:32 % ACC-COUNT = 6 S-ALLO-NUM = 0 %00000003 :SBZ3:$UHU.FILE3 % ------------------------------- HISTORY ------------------------------- % CRE-DATE = 2016-01-22 ACC-DATE = 2016-01-22 CHANG-DATE = 2016-01-22 % CRE-TIME = 13:10:20 ACC-TIME = 13:10:20 CHANG-TIME = 13:10:20 % ACC-COUNT = 4 S-ALLO-NUM = 0 %00000003 :SBZ3:$UHU.FILE4 % ------------------------------- HISTORY ------------------------------- % CRE-DATE = 2016-04-15 ACC-DATE = 2016-04-15 CHANG-DATE = 2016-04-15 % CRE-TIME = 10:18:52 ACC-TIME = 10:18:52 CHANG-TIME = 10:18:52 % ACC-COUNT = 5 S-ALLO-NUM = 0 %00000003 :SBZ3:$UHU.FILE5 % ------------------------------- HISTORY ------------------------------- % CRE-DATE = 2016-02-17 ACC-DATE = 2016-02-17 CHANG-DATE = 2016-02-17 % CRE-TIME = 13:42:11 ACC-TIME = 13:42:11 CHANG-TIME = 13:42:11 % ACC-COUNT = 3 S-ALLO-NUM = 0 %:SBZ3: PUBLIC: 5 FILES RES= 15 FREE= 10 REL= 0 PAGES
Restore with the last save version:
//RESTORE-FILES FILE-NAMES=*ALL, - // ARCHIVE-NAME=archive, - // SELECT-SAVE-VERSIONS=*BY-ATTRIBUTES, - // OPERATION-CONTROL=*PARAMETERS(REPORT=*FULL,OUTPUT=l.restore)
With this only those files are restored which are contained in the last save version. Files saved earlier are not taken into account.
/SHOW-FILE-ATTRIBUTES FILE-NAME=file* % 3 :SBZ3:$UHU.FILE2 % 3 :SBZ3:$UHU.FILE4
Version backup in SM-environment
Within the example version backup in SM environment is considered.
/START-HSMS //CRA ARCHIVE-NAME=SYSVERS.SMS,ENVIRONMENT=*SYSTEM-MANAGED(CATALOG-ID=SMS),- —————————— (1) // ALLOWED-USAGE=*VERSIONBACKUP,- // USER-ACCESS=*ALL-USERS(ACCESS=*WRITE),- // DIRECTORY-NAME=:SMS:SYSVERS.SMS.DIR,RETENTION-PERIOD=365 //MSP SM-PUBSET-ID=SMS,SYSVERSION=SYSVERS.SMS ———————————————————————————————————————— (2) //CREATE-MANAGEMENT-CLASS ENVIRONMENT=*SYSTEM-MANAGED(CATALOG-ID=SMS),- —————————————— (3) // MANAGEMENT-CLASS=SOURCES,- // MIGRATION-ATTRIBUTES=*PARAMETERS(FROM-S0=*PARAMETERS(UNUSED-DAYS=0)),- // BACKUP-ATTRIBUTES=*PARAMETERS(RETENTION-PERIOD=365),- // VERSION-BACKUP-ATTR=*PARAMETERS(NUM-OF-BACKUP-VERS=20) //CREATE-MANAGEMENT-CLASS ENVIRONMENT=*SYSTEM-MANAGED(CATALOG-ID=SMS),- // MANAGEMENT-CLASS=LISTINGS,- // MIGRATION-ATTRIBUTES=*PARAMETERS(FROM-S0=*PARAMETERS(UNUSED-DAYS=0)),- // BACKUP-ATTRIBUTES=*PARAMETERS(RETENTION-PERIOD=365),- // VERSION-BACKUP-ATTR=*PARAMETERS(NUM-OF-BACKUP-VERS=10) //END /MODIFY-FILE-ATTRIBUTES FILE-NAME=:SMS:*.SRC*,- —————————————————————————————————————— (4) / SUPPORT=*PUBLIC-DISK(MANAGEMENT-CLASS=SOURCES) /MODIFY-FILE-ATTRIBUTES FILE-NAME=:SMS:*.LST*,- / SUPPORT=*PUBLIC-DISK(MANAGEMENT-CLASS=LISTINGS)
| (1) | An HSMS administrator creates public version backup archive in SM environment. |
| (2) | The version backup archive is defined as a system version backup archive for an SM environment. |
| (3) | 2 management classes are created with specifying different values for versioning attribute NUM-OF-BACKUP-VERSION. |
| (4) | The management classes are assigned to some files. |
Let us consider the following files and their backup attributes. Some of them will have a mangement class assigned. All the files have a defined value of NUM-OF-BACKUP-VERSIONS in the catalog entries. The values are different from the values defined in the management classes:
/sh :sms:*.lst*, back=*y
%0000000003 :SMS:$TSOS.NB.FILE1.LST % ------------------------------- BACKUP ------------------------------- % BACK-CLASS = A SAVED-PAG = COMPL-FILE VERSION = 1 % MIGRATE = ALLOWED MAN-CLASS = LISTINGS % #BACK-VERS = 20 %0000000003 :SMS:$TSOS.NB.FILE2.LST % ------------------------------- BACKUP ------------------------------- % BACK-CLASS = A SAVED-PAG = COMPL-FILE VERSION = 1 % MIGRATE = ALLOWED MAN-CLASS = LISTINGS % #BACK-VERS = 20 %0000000003 :SMS:$TSOS.NB.FILE3.LST % ------------------------------- BACKUP ------------------------------- % BACK-CLASS = A SAVED-PAG = COMPL-FILE VERSION = 1 % MIGRATE = ALLOWED MAN-CLASS = LISTINGS % #BACK-VERS = 20
/sh :sms:*.src*, back=*y
%0000000003 :SMS:$TSOS.NB.FILE1.SRC % ------------------------------- BACKUP ------------------------------- % BACK-CLASS = A SAVED-PAG = COMPL-FILE VERSION = 1 % MIGRATE = ALLOWED MAN-CLASS = SOURCES % #BACK-VERS = 15 %0000000003 :SMS:$TSOS.NB.FILE2.SRC % ------------------------------- BACKUP ------------------------------- % BACK-CLASS = A SAVED-PAG = COMPL-FILE VERSION = 1 % MIGRATE = ALLOWED MAN-CLASS = SOURCES % #BACK-VERS = 15 %0000000003 :SMS:$TSOS.NB.FILE3.SRC % ------------------------------- BACKUP ------------------------------- % BACK-CLASS = A SAVED-PAG = COMPL-FILE VERSION = 1 % MIGRATE = ALLOWED MAN-CLASS = SOURCES % #BACK-VERS = 15 %:SMS: PUBLIC: 8 FILES RES= 24 FRE= 16 REL= 0 PAGES
/sh :sms:*.rep*, back=*y
%0000000003 :SMS:$TSOS.NB.FILE1.REP
% ------------------------------- BACKUP -------------------------------
% BACK-CLASS = A SAVED-PAG = COMPL-FILE VERSION = 1
% MIGRATE = ALLOWED
% #BACK-VERS = 5
%0000000003 :SMS:$TSOS.NB.FILE2.REP
% ------------------------------- BACKUP -------------------------------
% BACK-CLASS = A SAVED-PAG = COMPL-FILE VERSION = 1
% MIGRATE = ALLOWED
% #BACK-VERS = 5
Do version backup of the files with //BACKUP-FILE-VERSION statement specifying MANAGEMENT-CLASS as *ANY.
/HSMS //BFV FILE-NAMES=(:SMS:NB.*SRC*,:SMS:NB.*LST*,:SMS:NB.*REP*),- //ENVIRONMENT=*SYSTEM-MANAGED(CATALOG-ID=SMS),- //MANAGEMENT-CLASS=*ANY,- //TO-STORAGE=*S1-STORAGE-LEVEL,- //OPERATION-CONTROL=*PARAMETERS(REPORT=*FULL,OUTPUT=:SMS:REP1)
After request is completed, let see the content of the version backup archive:
//SHA ARCHIVE-NAME=SYSVERS.SMS,- //ENVIRONMENT=*SYSTEM-MANAGED(CATALOG-ID=SMS),- //SELECT=*FILES(INFORMATION=*VERSION)
It can be seen that NUM-OF-BACK-VERS values from management classes have been taken for files assigned to them; while for files, which are not assigned to a management class, the value from their catalog entries.
SHOW-ARCHIVE (FILES) SHOW-FILE-VERSIONS = DIFFERENT ENVIRONMENT = SM(SMS) ARCHIVE-NAME = $SYSHSMS.SYSVERS.SMS CATALOG-ID = SMS SV-NAME = ANY USER-ID = TSOS SV-DATE = INTERVAL EARLIEST LATEST FILE-SAVE-STATE = ANY EXP-DATE = ANY INFORMATION = VERSION -------------------------------------------------------------------------------- M FILE-NAME V# O-DATE O-TIME NUM OBS M S D-DATE NB.FILE1.LST 1 190301 150636 10 NO N Y NB.FILE1.REP 1 190301 150636 5 NO N Y NB.FILE1.SRC 1 190301 150636 20 NO N Y NB.FILE2.LST 1 190301 150636 10 NO N Y NB.FILE2.REP 1 190301 150636 5 NO N Y NB.FILE2.SRC 1 190301 150636 20 NO N Y NB.FILE3.LST 1 190301 150636 10 NO N Y NB.FILE3.SRC 1 190301 150636 20 NO N Y
Here is the report of the version backup run:
A*** BACKUP-FILE-VERSIONS HSMS V12.0 FULL REPORT *** 2019-03-01 15:06:41 PAGE 1
REQUEST-ENVIRONMENT=SM(SMS)
REQUEST-NAME=BFV#2917 REQUEST-DATE=2019-03-01 15:06:36 USER-ID=SYSHSMS REQUEST-STATE=COMPLETED
STATEMENT LISTING:
BFV FILE-NAMES=(:SMS:NB.*SRC*, :SMS:NB.*LST*, :SMS:NB.*REP*), ENVIRONMENT=*SYSTEM-MANAGED(CATALOG-ID=SMS),
MANAGEMENT-CLASS = *ANY, TO-STORAGE = *S1-STORAGE-LEVEL, OPERATION-CONTROL = *PARAMETERS(REPORT = *FULL,
OUTPUT=:SMS:NB.REP1)
SAVE-FILE ATTRIBUTES
TO-STORAGE : S1-STORAGE-LEVEL
RETENTION-PERIOD : 365
SAVE-VERSION ATTRIBUTES
SAVE-VERSION-NAME :
SELECT-FILES PARAMETER
MODIFIED-FILES PARTIAL-FILE-SAVE : NO
MAX-BACKUP-CLASS : STD
% HSM0030 REQUEST 'BFV#2917' CREATED IN ENVIRONMENT 'SM(SMS)' WITH DATE '2019-03-01' AND TIME '15:06:36'
% ARC0002 STATEMENT ACCEPTED. ARCHIVE SEQUENCE NUMBER 'A.190301.150636', VERSION '12.0A10'
% ARC0802 COMPUTED BLOCK-SIZE VALUE IS '239'
% ARC0033 ARCHIVE SUBTASK TSN '6AG4' GENERATED
% ARC0815 SUBTASK '0' HAS TRANSFERRED '9' PAM PAGES FOR '8' FILES AND '0' JVS IN '0' SECONDS
A*** BACKUP-FILE-VERSIONS HSMS V12.0 FULL REPORT *** 2019-03-01 15:06:41 PAGE 4
REQUEST-ENVIRONMENT=SM(SMS)
REQUEST-NAME=BFV#2917 REQUEST-DATE=2019-03-01 15:06:36 USER-ID=SYSHSMS REQUEST-STATE=COMPLETED WITH ERRORS
SAVE FILE IDENTIFIER - S.190301.150636
SUBSAVE
NUMBER VSNS
0 0:HSMS
*** CATALOG - SMS USER - TSOS ***
FILE/JOB VARIABLE NAME LASTPG/ SAVE VERSION SAVE INPUT SUB OUTPUT
VERS SIZE IDENTIFIER TYPE VSN SAVE DISK(S)
NB.FILE1.LST 1 1 190301.150636 FULL SMK.00 0 0:HSMS
NB.FILE1.REP 1 1 190301.150636 FULL SMK.00 0 0:HSMS
NB.FILE1.SRC 1 1 190301.150636 FULL SMK.00 0 0:HSMS
NB.FILE2.LST 1 1 190301.150636 FULL SMK.00 0 0:HSMS
NB.FILE2.REP 1 1 190301.150636 FULL SMK.00 0 0:HSMS
NB.FILE2.SRC 1 1 190301.150636 FULL SMK.00 0 0:HSMS
NB.FILE3.LST 1 1 190301.150636 FULL SMK.00 0 0:HSMS
NB.FILE3.SRC 1 1 190301.150636 FULL SMK.00 0 0:HSMS
NUMBER OF FILES= 8 GLOBAL SIZE= 8 START= 2019-03-01 15:06:36 END= 2019-03-01 15:06:41
*** E N D O F HSMS V12.0 FULL REPORT *** 2019-03-01 15:06:41 ***
Let’s change versioning attribute of management class SOURCES.
//MODIFY-MANAGEMENT-CLASS ENVIRONMENT=*SYSTEM-MANAGED(CATALOG-ID=SMS),- //MANAGEMENT-CLASS=SOURCES,- //VERSION-BACKUP-ATTR=*PARAMETERS(NUM-OF-BACKUP-VERS=32)
And repeat the run without updating any of the files.
//BFV FILE-NAMES=(:SMS:NB.*SRC*,:SMS:NB.*LST*,:SMS:NB.*REP*),- //ENVIRONMENT=*SYSTEM-MANAGED(CATALOG-ID=SMS),- //MANAGEMENT-CLASS=*ANY,- //TO-STORAGE=*S1-STORAGE-LEVEL,- //OPERATION-CONTROL=*PARAMETERS(REPORT=*FULL,OUTPUT=:SMS:NB.REP2)
As a result no files have been saved. However, files which are assigned to the updated management class, have been affected: the new value of NUM-OF-BACKUP-VERS has been written into the directory.
A*** BACKUP-FILE-VERSIONS HSMS V12.0 FULL REPORT *** 2019-03-01 15:13:51 PAGE 1
REQUEST-ENVIRONMENT=SM(SMS)
REQUEST-NAME=BFV#2917 REQUEST-DATE=2019-03-01 15:13:46 USER-ID=SYSHSMS REQUEST-STATE=COMPLETED
STATEMENT LISTING:
BFV FILE-NAMES=(:SMS:NB.*SRC*, :SMS:NB.*LST*, :SMS:NB.*REP*), ENVIRONMENT=*SYSTEM-MANAGED(CATALOG-ID=SMS),
MANAGEMENT-CLASS = *ANY, TO-STORAGE = *S1-STORAGE-LEVEL, OPERATION-CONTROL = *PARAMETERS(REPORT = *FULL,
OUTPUT=:SMS:NB.REP2)
SAVE-FILE ATTRIBUTES
TO-STORAGE : S1-STORAGE-LEVEL
RETENTION-PERIOD : 365
SAVE-VERSION ATTRIBUTES
SAVE-VERSION-NAME :
SELECT-FILES PARAMETER
MODIFIED-FILES PARTIAL-FILE-SAVE : NO
MAX-BACKUP-CLASS : STD
% HSM0030 REQUEST 'BFV#2917' CREATED IN ENVIRONMENT 'SM(SMS)' WITH DATE '2019-03-01' AND TIME '15:13:46'
% ARC0002 STATEMENT ACCEPTED. ARCHIVE SEQUENCE NUMBER 'A.190301.151347', VERSION '12.0A10'
% ARC0802 COMPUTED BLOCK-SIZE VALUE IS '239'
% ARC0033 ARCHIVE SUBTASK TSN '6AG5' GENERATED
% ARC0815 SUBTASK '0' HAS TRANSFERRED '0' PAM PAGES FOR '0' FILES AND '0' JVS IN '0' SECONDS
% ARC0037 SPECIFIED FILE NAME ':SMS:$TSOS.NB.*LST*' NOT PROCESSED
% ARC0037 SPECIFIED FILE NAME ':SMS:$TSOS.NB.*REP*' NOT PROCESSED
A*** BACKUP-FILE-VERSIONS HSMS V12.0 FULL REPORT *** 2019-03-01 15:13:51 PAGE 2
REQUEST-ENVIRONMENT=SM(SMS)
REQUEST-NAME=BFV#2917 REQUEST-DATE=2019-03-01 15:13:46 USER-ID=SYSHSMS REQUEST-STATE=COMPLETED WITH ERRORS
*** CATALOG - SMS USER - TSOS ***
FILE/JOB VARIABLE NAME LASTPG/ SAVE VERSION SAVE INPUT SUB OUTPUT
VERS SIZE IDENTIFIER TYPE VSN SAVE DISK(S)
NB.FILE1.SRC 1 1 190301.151347 SMK.00 0 DIR-UPD: #BACK-VERS
NB.FILE2.SRC 1 1 190301.151347 SMK.00 0 DIR-UPD: #BACK-VERS
NB.FILE3.SRC 1 1 190301.151347 SMK.00 0 DIR-UPD: #BACK-VERS
NUMBER OF FILES= 3 GLOBAL SIZE= 3 START= 2019-03-01 15:13:47 END= 2019-03-01 15:13:51
*** E N D O F HSMS V12.0 FULL REPORT *** 2019-03-01 15:13:51 ***
Let’s check the content of the version backup archive:
//SHA ARCHIVE-NAME=SYSVERS.SMS,- //ENVIRONMENT=*SYSTEM-MANAGED(CATALOG-ID=SMS),- //SELECT=*FILES(INFORMATION=*VERSION)
Files assigned to modified management class now have new values for NUM-OF-BACK-VERS (see the column ‘NUM’):
SHOW-ARCHIVE (FILES) SHOW-FILE-VERSIONS = DIFFERENT ENVIRONMENT = SM(SMS) ARCHIVE-NAME = $SYSHSMS.SYSVERS.SMS CATALOG-ID = SMS SV-NAME = ANY USER-ID = TSOS SV-DATE = INTERVAL EARLIEST LATEST FILE-SAVE-STATE = ANY EXP-DATE = ANY INFORMATION = VERSION -------------------------------------------------------------------------------- M FILE-NAME V# O-DATE O-TIME NUM OBS M S D-DATE NB.FILE1.LST 1 190301 150636 10 NO N Y NB.FILE1.REP 1 190301 150636 5 NO N Y NB.FILE1.SRC 1 190301 150636 32 NO N Y NB.FILE2.LST 1 190301 150636 10 NO N Y NB.FILE2.REP 1 190301 150636 5 NO N Y NB.FILE2.SRC 1 190301 150636 32 NO N Y NB.FILE3.LST 1 190301 150636 10 NO N Y NB.FILE3.SRC 1 190301 150636 32 NO N Y