In synchronous processing, maximum wait times apply: HSMS statements are rejected if HSMS fails to accept the request in question before the respective wait time has elapsed. If the request has not been completed, processing of the statement continues asynchronously.
The maximum wait times are defined by the HSMS administrator by means of
//MODIFY-HSMS-PARAMETERS REQUEST-WAIT-LIMITS=*PARAMETERS(...)
This statement serves to define:
a maximum wait time for acceptance of the request (DIALOG- or BATCH-REQUEST-TIME) separately for interactive and batch requests.
a maximum wait time for request execution (DIALOG- or BATCH-EXEC-TIME) separately for interactive and batch requests.
If the request is not terminated after the maximum wait time defined with DIALOG- or BATCH-REQUEST-TIME for request acceptance has elapsed, a check is made to determine whether the request has already been accepted by an HSMS server task. How processing continues is dependent on the result of this check:
If the request has already been accepted, the system waits for the request to be executed. Here the maximum wait time for request execution applies which was defined with DIALOG- or BATCH-EXEC-TIME.
If the request has not yet been accepted, it is rejected.
Note
HSMS issues a SECURE-RESOURCE-ALLOCATION command with wait time for the input and output volumes. This wait time is the same as the specification in the HSMS parameter BATCH-REQUEST-TIME (see also section "Volume and device reservation").