Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

RESTART-REQUESTS Restart requests

&pagelevel(4)&pagelevel

This statement is used for restarting interrupted requests from the request file located in an SF or SM pubset environment.

  • Requests which were interrupted before an ARCHIVE run was created to process them can be restarted.

  • Requests for which an ARCHIVE run had already been started but not completed (INTERRUPTED state) cannot be restarted unless

    • the request was started with the option WRITE-CHECKPOINTS=*YES,

    • and the ARCHIVE checkpoint file is available and contains the relevant ARCHIVE run.

The requests cannot be restarted unless the current operating mode is the same as at the time they were accepted by HSMS (OPERATION mode or SIMULATION mode).

This statement has different formats for nonprivileged users and HSMS administrators. Privileged operands or operand values are marked with *P).

Note

The RESTART-REQUESTS statement creates a new request for monitoring the migration or recall. 

Format

RESTART-REQUESTS

Alias: RSR

REQUEST-NAME = *ANY / <name 1..8>

,ENVIRONMENT = *STD / *NODE-STD / *SINGLE-FEATURE / *SYSTEM-MANAGED(...)


*SYSTEM-MANAGED(...)



|

CATALOG-ID = <cat-id>

,REQUEST-DATE = *LATEST / *INTERVAL(...) / <date with-compl>(...)


*INTERVAL(...)



|

CREATED-BEFORE = *LATEST-DATE / <date with-compl> / <integer -99999..0 days>



|

,CREATED-AFTER = *EARLIEST-DATE / <date with-compl> / <integer -99999..0 days>


<date with-compl>(...)



|

TIME = <time>

,USER-ID*P) = *OWN / *ALL / <name 1..8>

,ARCHIVE-NAME = *ALL / <filename 1..22 without-cat-gen-vers>

,WAIT-FOR-COMPLETION = *NO / *YES / *FROM-RESTARTED-REQUEST

*P) Privileged operand or operand value

REQUEST-NAME =
Serves to select the requests to be restarted using the request name as the selection criterion. The name specified via the action statement or the default name assigned by HSMS is extended internally by a prefix formed by the user ID and a suffix in the form of a time stamp. Since the name by itself need not be unique, the request name can be used to refer to more than one request at a time.

REQUEST-NAME = *ANY
The requests to be restarted are to be selected irrespective of their names.

REQUEST-NAME = <name 1..8>
Restricts restart to requests with the specified name.

ENVIRONMENT =
Defines the HSMS environment where the specified archive is located.

ENVIRONMENT = *STD
The HSMS statement relates to the default environment for DMS requests:

  • For privileged users: *STD is set to the value *SINGLE-FEATURE.

  • For nonprivileged users: *STD is the environment that is associated with the user’s default pubset (the default pubset is defined in the user catalog). 

ENVIRONMENT = *NODE-STD
The HSMS statement relates to the default environment for node requests:

  • For privileged users: *NODE-STD is set to the value *SINGLE-FEATURE.

  • For nonprivileged users: *NODE-STD is set to the value of the environment in which the home directory of the user is defined.

ENVIRONMENT = *SINGLE-FEATURE
The HSMS statement relates to the SF environment only. Only requests which are located in the request file of the SF pubset environment are processed.

ENVIRONMENT = *SYSTEM-MANAGED(...)
The HSMS statement relates only to the specified SM pubset environment. Only requests that are located in the request file of the SM pubset environment are processed.

CATALOG-ID = <cat-id>
Catalog ID of the SM pubset to which the HSMS statement applies.

REQUEST-DATE =
Serves to select the requests to be restarted using the creation date as the selection criterion. The date is output using the SHOW-REQUESTS statement of HSMS.

REQUEST-DATE = *LATEST
Restricts restart to the most recently generated requests.

REQUEST-DATE = *INTERVAL(...)
The requests to be restarted are to be selected using a time interval as the selection criterion. The interval includes all requests created between CREATED-AFTER and CREATED-BEFORE.
Unless otherwise specified, all requests starting with the one created first (*EARLIEST-DATE) up to the one created last (*LATEST-DATE) are selected.

CREATED-BEFORE = *LATEST-DATE
The requests are to be restarted irrespective of whether they were created before a specific date.

CREATED-BEFORE = <date with-compl>
Restricts restart to requests created on or before the specified date.

CREATED-BEFORE = <integer -99999..0 days>
Restricts restart to requests created on or before the specified relative date.

CREATED-AFTER = *EARLIEST-DATE
The requests are to be restarted irrespective of whether they were created after a specific date.

CREATED-AFTER = <date with-compl>
Restricts restart to requests created on or after the specified date.

CREATED-AFTER = <integer -99999..0 days>
Restricts restart to requests created on or after the specified relative date.

REQUEST-DATE = <date with-compl>(...)
The requests to be restarted are selected using the date and time of their creation as the selection criterion.

TIME = <time>
Time specification in the format hh:mm:ss

USER-ID =
This operand is only available to the HSMS administrator.
Serves to select the requests to be restarted using the user ID under which they were created as the selection criterion.

USER-ID = *OWN
Restricts restart to requests created under the user’s own ID (or, in the case of the HSMS administrator, under SYSHSMS).

USER-ID = *ALL
Requests from all users are to be restarted.

USER-ID = <name 1..8>
Only requests of the specified user ID are to be restarted.

ARCHIVE-NAME =
Only for archive owners:
the requests to be started can be selected in the specified environment via the archive for which they were created.

ARCHIVE-NAME = *ALL
The requests to be started are selected irrespective of the archive.

ARCHIVE-NAME = <filename 1..22 without-cat-gen-vers>
Only requests referring to the archive in the specified environment are started.

WAIT-FOR-COMPLETION = *NO / *YES / *FROM-RESTARTED-REQUEST
Specifies whether or not the user should wait for the completion of his request, or whether the setting used when the request was last started should be used again.