Where allowed to run: All environments (*ALL) Threadsafe: No |
Parameters Examples Error messages |
The Start Subsystem (STRSBS) command starts a subsystem using the subsystem description specified in the command. When the subsystem is started, the system allocates the necessary and available resources (storage, work stations, and job queues) that are specified in the subsystem description.
Allocating Storage: Storage is allocated to the subsystem according to the storage pool definitions specified in the subsystem description, starting with the lower numbered storage pool definitions. If all the pool definitions cannot be allocated, because the maximum number of storage pools on the system is reached or because insufficient storage is available, messages indicating which pools could not be allocated are sent to the system operator. If storage becomes available later, or if the number of active storage pools is reduced, the available resources are automatically allocated to the subsystem to satisfy its unfulfilled requirements. Any jobs that would normally run in a storage pool that is not allocated are run in the shared storage pool *BASE.
Allocating Work Stations: Work stations are allocated to the subsystem according to the work station entries in the subsystem description. Each work station whose name (or type, if not specified by name) is contained in one of the subsystem description's work station entries, and whose entry specifies AT(*SIGNON), is allocated to this subsystem unless it is currently signed on to another subsystem. The sign-on prompt is displayed on each work station that is allocated. Work stations that are already signed on in another subsystem remain allocated to that subsystem until the subsystem that allowed the sign-on is ended, or until the user transfers the job to this subsystem.
If multiple subsystems specify the same work station in their work station entries, each subsystem, as it is started, attempts to allocate that work station. Each successive subsystem allocates that work station unless a user signs on while the work station is allocated to one of the previously started subsystems. When a signed-on work station is signed off, it still remains allocated to the same subsystem until another subsystem is started that specifies that work station. However, if a work station is varied offline and several active subsystems specify that work station, the subsystem to which the work station is allocated when it is varied online is unpredictable.
Allocating Job Queues: If a job queue is specified in the work entries of the subsystem description, the job queue is allocated to the subsystem. If the job queue does not exist or if it is already allocated to an active subsystem, no job queue is allocated to the subsystem and a message is sent to the system operator. If the job queue later becomes available, it is automatically allocated to the subsystem.
Restrictions:
Top |
Keyword | Description | Choices | Notes |
---|---|---|---|
SBSD | Subsystem description | Qualified object name | Required, Positional 1 |
Qualifier 1: Subsystem description | Name | ||
Qualifier 2: Library | Name, *LIBL, *CURLIB |
Top |
Specifies the name and library of the subsystem description that defines the operational environment (subsystem) being started.
The name of the subsystem description cannot be the same as the name of a subsystem that is currently active, even though the subsystem descriptions are in different libraries.
This is a required parameter.
Qualifier 1: Subsystem description
Note: The IBM-supplied object named QLPINSTALL is not allowed for the subsystem description name.
Qualifier 2: Library
Note: The library QTEMP is not allowed for the library name.
Top |
Example 1: Starting the Batch Subsystem
STRSBS SBSD(QBATCH)
This command starts the batch subsystem named QBATCH.
Example 2: Starting a User Subsystem
STRSBS SBSD(QGPL/TELLER)
This command starts the subsystem that is associated with the TELLER subsystem description in the QGPL library. The subsystem name is TELLER.
Top |
*ESCAPE Messages
Top |