HSMS provides a number of server tasks for processing requests simultaneously. The HSMS administrator can define the maximum number of server tasks permanently using the NUMBER-OF-SUBTASKS operand of the HSMS statement MODIFY-HSMS-PARAMETERS. The system administrator can change the value temporarily for the current HSMS session using the same operand of the START-HSMS statement.
At least one server task per default system archive should be available, with additional server tasks for requests concerning private archives. In addition, there should also be server tasks for read requests to S1. In addition, there should also be server tasks for read requests to S1. The number of server tasks in addition to those per system archive and for requests to S1 should correspond to the number of tape units available.
Server tasks are not automatically restarted following a program crash.
This means that the number of server tasks active at a given time may be smaller than desired, with the result that a request is not processed. If the situation arises in which requests are accepted but not started, the HSMS administrator should check how many server tasks are active (HSMS statement SHOW-HSMS-PARAMETERS). The HSMS administrator can use the HSMS statement MODIFY-HSMS-PARAMETERS to create new server tasks, if necessary.