The SAVE-OPTIONS operand can be used to set options for the current backup run.
Saving UDS databases online (SAVE-ONLINE-FILES)
In HSMS, SAVE-ONLINE-FILES=*YES can be specified to save files which are open during the backup operation. However, not all files are saved, but rather only opened files for which online backup has been expressly specified, using the OPNBACK operand in the CATAL macro (see the “DMS macros” manual [22]).
This function is intended only for database files, since this type of backup can result in file inconsistency if used with normal files.
Online backup of UDS databases can be used for UDS-SQL V1.2 and higher. This requires that an after-image file be used (for additional conditions. Please refer to the manuals for UDS-SQL).
Saving the archive directory (SAVE-DIRECTORY)
The archive directory which is updated during the save operation can also be written to the save file on backup volume or pubset at the end of the save request. In addition to the saved data, the save file then also contains a directory of the saved data.
Saving of the archive directory is initiated by specifying SAVE-DIRECTORY=*YES. It is not saved by default.
The HSMS administrator is permitted to save the archive directory, as is also the archive owner and the co-owner of the archive directory.
The following applies to saving the archive directory:
If no data was saved with the request, the directory is not saved either.
Only a full backup of the archive directory is carried out, even if incremental backups are implemented.
The archive directory is not distributed to different volumes. Saving of the archive directory and the volume used for this are displayed in the report.
When MAREN V12.0 or higher is used, the backup volume (tape or MTC) which contains the archive directory is assigned the "Volume Contains Directory" attribute in the MAREN catalog. When the directory is restored using IMPORT-FILES, the corresponding volume can be ascertained again.
When the archive directory has been saved, it can be restored from save file on tape, Net-Storage, or private or public disk in the event of an emergency (if it no longer exists or is not readable). To do this you use the IMPORT-FILES statement with *DIRECTORY and SAVE-FILE specified:
If the directory was saved to tape, Net-Storage (with SAVE-FILE-PROCESSING=*HSMS-V9-COMPATIBLE) or private disk, SAVE-FILE=*BY-VOLUME must be specified.
If the directory was saved to public disk or within SAVE-FILE-PROCESSING=*HSMS-V10-COMPATIBLE mode to Net-Storage, SAVE-FILE=*BY-PUBLIC-DISK must be specified.
Save files on tape have a several SVID structure. In this case you need to specify an SVID, and in any other case the SFID. The SFID, SVID and volume or pubset are noted in the report on the backup. When MAREN V12.0 or higher is used, the volume (tape or MTC) can also be ascertained from the MAREN catalog.
The attributes of an archive are also stored in the archive directory. If the archive definition has been lost the archive can be restored from the archive directory using the CREATE-ARCHIVE statement (RECONSTRUCT-ARCHIVE=*YES operand).
During reorganization of version backup archive it is not possible to save the archive directory.
Backing up information from a PLAM library (SAVE-PLAM-INFO)
The SAVE-PLAM-INFO operand of the HSMS statements BACKUP-FILES or BACKUP-FILE-VERSIONS causes metadata of a PLAM library to be saved. The default setting *STD causes the archive attribute SAVE-PLAM-INFO of the same name to be evaluated. In the case of the HSMS statement ARCHIVE-FILES the metainformation is saved only if the archive attribute is set accordingly.
HSMS uses the backed-up information of a PLAM library if one or more library elements are to be restored using the HSMS statement RESTORE-LIBRARY-ELEMENTS. You can use RESTORE-LIBRARY-ELEMENTS to
restore an old version of a library element to a library without having to restore the complete library.
restore the last backup status of a library element without having to restore the complete library.
The HSMS statement RESTORE-LIBRARY-ELEMENTS can also be used to copy selected elements to another library (target library).
The library elements addressable with RESTORE-LIBARY-ELEMENTS cannot be displayed in a dialog. SHOW-ARCHIVE does not allow any elements to be displayed either; only all PLAM libraries saved with PLAM-INFO=*YES are displayed:
//SHOW-ARCHIVE <archiv-name>,SELECT=*FILES(..., - // FILE-SAVE-STATE=*SAVED(TYPE=*WITH-PLAM-INFO), ...), ...
To restore library elements users must either know the element names at the time of the backup or they have the elements listed beforehand with the ELEMENTS=*LIST-ALL-TO-REPORT operand in the RESTORE-LIBRARY-ELEMENTS statement.
The additional information that is saved requires a certain amount of space on the backup volume and lengthens the backup operation. The space and time required depend on the size of the library and the number of elements present in the backed-up PLAM library.
To obtain optimum performance when performing backups, you should use SAVE-PLAM-INFO
only if you use the HSMS statement RESTORE-LIBRARY-ELEMENTS frequently, or
prefer it for large libraries containing a small number of elements if you encounter storage space problems.
Saving the data or catalog entries of BS2000 Net-Storage files
- This section refers only to backups via BACKUP-FILES statement. Version backup does not provide such an option. Within version backup Net-Storage files are always saved with data and catalog entry.
- This section refers only to Net-Storage files of the type BS2000 file. Net-Storage files of the type node file are always backed up fully – with data and the catalog entry.
- This section refers only to Net-Storage files originating from NETSTOR volume type. Net-Storage files residing on volumes of NETVOL volume type are always backed up fully.
The default SAVE-NET-STOR-DATA=*YES in the HSMS statement BACKUP-FILES saves the catalog entries and data of Net-Storage files. With SAVE-NET-STOR-DATA=*NO, only the catalog entries of BS2000 Net-Storage files are saved.
//SHOW-ARCHIVE causes files on Net-Storage for which only the catalog entries have been saved to be displayed with the save type CATL (meaning catalog only). The CATL mark is also displayed in the reports in the SAVE TYPE column.
When only the catalog entry has been backed up for a Net-Storage file, the save version of the file is not incremented.
When backup takes place with SELECT-FILE=*MODIFIED-FILES (incremental backup), Net-Storage files which have not been changed since the last backup are saved according to the following rule:
Last saved with | Current incremental backup with SAVE-NET-STOR-DATA= | |
*YES | *NO | |
FULL only | CNS | CATL |
CATL only | FULL | CATL |
Both FULL and CATL | CNS | CATL |
No FULL, no CATL | FULL | CATL |
With //RESTORE-FILES, privileged users can use the NET-STORAGE-FILES operand to choose whether data and the catalog entry or only the catalog entry are restored for Net-Storage files originated from NETSTOR volume type:
- *DATA-AND-CATALOG restores data and catalog entry.
*CATALOG-ONLY restores only the catalog entry.
Save versions containing FULL saves of a Net-Storage file can also be used for restoring catalog entries of the file on Net-Storage.
Special aspects of SAM node files
Files on Net-Storage with the file type NODE-FILE can be processed by BS2000 as well as open systems. Open system files are stored without structure.
NODE-FILE PAM files are processed as unstructured data by the BS2000. No further special aspects have to be taken into account for backup and recovery.
For SAM node files, the BS2000 access method writes the traditional SAM data structure into Net-Storage. On their way into the UFS, Net-Client removes the SAM specific structure information will be removed from the data blocks, which are to be migrated, and the code is converted into an ASCII code. This means that a file is saved on the remote Net-Storage, which could be considered as a text file by the open world.
There are two possible ways to access a SAM node file from BS2000:
one is to maintain the SAM structures in the BS2000 application by adding them with Net-Client during the write process when the files are migrated from the Net-Server or
without conversion, i.e. without adding SAM structures to the data blocks and without code conversion to EBCDIC (this is called RAW mode).
Accessing the SAM node files in RAW mode is more efficient and is the best way to achieve fast backups. However, SAM node files backed up this way can only be recovered as NODE-FILE type files on Net-Storage.
RAW mode is used if the SAVE-SAM-STRUCTURE=*NO operand is specified for the backup in the SAVE-OPTIONS; this is the default value, due to the better performance.
If SAVE-SAM-STRUCTURE=*YES is specified, the conversion of the file is used for the backup of the SAM node file. This process creates data blocks in SAM format and the data is converted into EBCDIC characters according to the coded character set and net coded character set in the catalogue entry of the file. This means that the “true” SAM file will be written to the save file. This backup type is less efficient, however, has the benefit of enabling a restore of the saved files on both Net-Storage (BS2000 or NODE-FILE type) and Public-Space (NEW-SUPPORT). So SAVE-SAM-STRUCTURE=*YES enables highly flexible restoring.