Requests for restoring of data sets can be deferred over a period of time until a batch DISPOSE run is made. Use of this facility is desirable in that the number of tape mounts will be minimized. This is a consequence of the sequencing of perhaps several restore requests by archive tape volume serial and file number, and restoring all within a single mount and scan of the needed tapes.
A deferred request is made by adding the DEFER parameter to the RESTORE command (or using DRESTORE instead of RESTORE as the command name).
Deferred restore requests are queued and kept in the RESTCMDS subfile of the CA Disk files data set. After a queued request has been processed, its completion status is maintained for a default period of five days, after which it is automatically deleted during the next dispose run. Through the ISPF panels, the saved status can also be displayed online. Otherwise the output from the dispose run must be inspected to determine the outcome of processing for the request. Sysparm DRESKEEP can be used to alter the default period for which the status is maintained in the RESTCMDS file.
Normally, DRESTORE requires that the requestor has sufficient authority to restore the data set, determined by sysparm SECURDRS. However, if the SYSCTLG parameter is specified and sysparm ARSECURE has a value of 'N' or 'R', the requestor will only require INPUT authority. When the DISPOSE job is run, the SYSCTLG parameter will only allow the restore to complete if the data set is cataloged to the pseudo volser, and the USERID associated with DISPOSE has sufficient authority to create or update the data set.
For both TSO and ISPF DRESTORE commands, if the data set is cataloged to the pseudo volser, the SYSCTLG parameter will automatically be generated for the request, allowing these functions to operate exactly like DMSAR.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|