This statement is used by HSMS administrators only. It serves to correct inconsistencies in the catalog entries of migrated files. It checks the validity of the reference to the save file in the catalog entry of each migrated file. If the reference is invalid, HSMS restores the save file’s data from a backup or version backup archive, which contains the file with the same internal name (CFID).
The following files on the specified S0 pubset are selected for processing:
files for which the catalog entry contains no localization information
files whose localization information references a save file which no longer exists or a save file which is not in the current system migration archive (SYSMIGRATE; error NOT-IN-ARC with //SHOW-PUBSET-USAGE)
The files selected are restored from the specified backup or version backup archive to the level indicated in the TO-STORAGE operand.
If any of the migrated files in question has been partially saved in the backup archive, it is impossible to restore it to a migration level. The file is restored to S0 instead.
Requests for REPAIR-CATALOG-BY-RESTORE that were issued on an SF pubset are entered in the HSMS global request file.
Requests issued on an SM pubset are entered in the request file of the SM pubset. To output the requests, the user must specify the correct environment in the ENVIRONMENT operand of the SHOW-REQUESTS statement.
Format (only for HSMS administrators)
REPAIR-CATALOG-BY-RESTORE | Alias: RCR | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
S0-PUBSET-ID = <cat-id>
Names the S0 pubset to which the HSMS statement refers.
TO-STORAGE =
Defines the location to which the files are to be restored.
TO-STORAGE = *SAME
The data is restored to the level indicated in the catalog entry.
TO-STORAGE = *S0-STORAGE-LEVEL
The data is restored to the level S0.
TO-STORAGE = *S1-STORAGE-LEVEL
The data is restored to the level S1.
TO-STORAGE = *S2-STORAGE-LEVEL
The data is restored to the level S2.
ARCHIVE-NAME =
Names the backup or version backup archive from which the data is to be restored.
If the S0 pubset ID is an SF pubset, the archive is taken from the SF pubset environment. If the S0 pubset ID is an SM pubset, the archive is taken from the SM pubset environment.
ARCHIVE-NAME = *SYSBACKUP
The files are restored from the system backup archive which is defined in the environment of the S0 pubset ID.
ARCHIVE-NAME = *SYSVERSION
The files are restored from the system version backup archive which is defined in the environment of the S0 pubset ID.
ARCHIVE-NAME = <filename 1..22 without-cat-gen-vers>
The files are restored from the specified backup or version backup archive which is defined in the environment of the S0 pubset ID.
COMPRESS-FILES =
Only when restoring to a migration level.
Specifies whether the data is to be compressed when restored.
COMPRESS-FILES = *STD
The default setting is derived from the archive definition of the migration archive which belongs to the specified S0 pubset.
COMPRESS-FILES = *NO
The data is restored in uncompressed form.
COMPRESS-FILES = *YES
The data is restored in compressed form.
OPERATION-CONTROL =
Enables the user to define a number of parameters which are relevant for the execution of the restore run.
OPERATION-CONTROL = *STD
The default values of the operands described below apply.
OPERATION-CONTROL = *PARAMETERS(...)
The operands controlling the restore run can be modified as follows:
REQUEST-NAME = *STD / <name 1..8>
Request name that can be used in the HSMS request management statements (DELETE-REQUESTS, RESTART-REQUESTS and SHOW-REQUESTS) to refer to this request. The name is extended internally by a prefix derived from the user ID (or SYSHSMS for the HSMS administrator) and a suffix in the form of a time stamp. Unless otherwise specified, the request name is formed by the short code “RCR#” and the TSN of the calling user task yyyy as follows: RCR#yyyy.
REQUEST-DESCRIPTOR = *NONE / <text 1..60>
It is possible to enter any text that describes the request in more detail.
This text is displayed at the operator console when the request is started. The text can be output using the HSMS statement SHOW-REQUESTS.
EXPRESS-REQUEST = *NO / *YES
Determines whether tape access is to take place during the sessions defined for express requests.
CONTROL-JV = *NONE / <filename 1..54 without-gen-vers>
Specifies the name of a job variable that HSMS supplies with various values corresponding to important actions performed by HSMS/ARCHIVE.
The user issuing the request can query the job variable to obtain an overview of the current processing status. How to use the job variable is described in detail in the “HSMS Vol. 1” manual [1] in the section “Job variable for request monitoring”.
WAIT-FOR-COMPLETION = *NO / *YES
Specifies whether the user wishes to wait until processing of his or her request has been completed (synchronous processing) or whether control is to be returned to the user after the validity of the HSMS statement has been checked (asynchronous processing).The maximum wait times for batch tasks and interactive tasks are different and are determined by preset global HSMS parameters.
Interactive tasks are permitted to carry out synchronous HSMS statement processing during tape sessions only.
PARALLEL-RUNS = *STD / <integer 1..16>
This operand is only significant if you are working at storage level S2. It specifies the number of save tasks (ARCHIVE subtasks) running in parallel.
For duplication there must be two tape devices available for each task.
Unless otherwise specified, the preset value from the archive definition applies.
For further information on parallel processing, see the “HSMS Vol. 1” manual [1].
WRITE-CHECKPOINTS = *STD / *YES / *NO
Defines whether any checkpoints are to be written to the ARCHIVE checkpoint file during processing; these checkpoints permit a request to be restarted following an interrupt (INTERRUPTED state).
Unless otherwise specified, the preset value from the archive definition applies.
OPERATOR-INTERACTION = *STD / *NOT-ALLOWED / *ALLOWED
Determines whether messages requiring an operator response are to output at the console (*ALLOWED) or not (*NOT-ALLOWED). If *NOT-ALLOWED applies, HSMS performs default handling (see the description of the PARAM statement in the “ARCHIVE” manual [2]).
Unless otherwise specified, the default value from the archive definition applies.
TAPE-CONTROL =
Defines parameters which are relevant for restoring files from tape.
TAPE-CONTROL = *STD
The preset values from the definition of the archive from which the files are to be restored apply.
TAPE-CONTROL = *PARAMETERS(...)
The operands relevant to restoring from tape can be modified as follows:
UNLOAD-TAPE = *STD /*YES / *NO
Specifies whether or not tapes are to be unloaded after processing.
Unless otherwise specified, the preset value from the archive definition applies.
It is possible that HSMS ignores the value of this operand to avoid irrational processing of tapes, for example to avoid unloading the tape several times while rewinding it.
PERFORMANCE-ANALYSIS =
Specifies whether a statistics file is to be produced for each ARCHIVE subtask. ARCHIVE writes a new line to this statistics file:
when it opens a save file ARCHIVE.SAVE.FILE.
when it closes this save file.
whenever it begins saving or restoring a new file.
every 2 seconds while it is saving/restoring.
This gives a detailed overview of the ARCHIVE activities taking place during the save and restore operations.
PERFORMANCE-ANALYSIS = *NO
No statistics file is to be produced.
PERFORMANCE-ANALYSIS = *YES(...)
A statistics file is to be produced for each ARCHIVE subtask.
SEPARATOR = ; / <c-string 1..1>
Character that is inserted between the different fields in the statistics files. This enables programs such as EXCEL or LOTUS to differentiate the different fields.The default value is “ ; ”. This corresponds to the EXCEL default setting.
REPORT =
Serves to define whether a report is to be output for this repair request and to determine the scope of this report.
REPORT = *SUMMARY
A summary of the results of the repair request, including any error messages, is to be output.
REPORT = *RESTORED-FILES
A full report is to be output, including a list of all files actually restored.
REPORT = *FULL
A full report is to be output, including a list of all files which should have been restored but were not due to an error.
REPORT = *NONE
No report is to be output.
OUTPUT =
Specifies where the report is to be output.
OUTPUT = *STD
The output destination of the report is determined by the default value that is defined by the global HSMS parameter OUTPUT.
OUTPUT = *PRINTER
The report for this repair request is to be printed.
OUTPUT = *NONE
No report is output. Nevertheless the report is available as a pdf file via the SE manager application Backup Monitoring, if the monitoring is activated in the global HSMS parameters.
OUTPUT = *MAIL
The report for this repair request is sent as an email attachment to the address which is entered in the caller’s user entry. If it is not possible to send the report by email, it is printed out.
OUTPUT = *LIBRARY-ELEMENT(...)
The report for this repair request is edited and output to the specified PLAM library element (type P). If this is not possible, the report is printed out.
LIBRARY = <filename 1..54 without-gen-vers>
Name of the PLAM library.
ELEMENT = <composed-name 1..64 with-under>
Name of the element. A type P element is created with a version which contains the user ID plus the date and time.
OUTPUT = <filename 1..54 without-gen-vers>
The report for this repair request is to be edited and written to the specified file.If the file already exists, the following applies:
if it is a non-empty SAM file, it is continued
if not, the report is printed.