Function

To dynamically define a functional subsystem (FSS) to JES2.

Parameters

accccccc

The 1 to 8 character name of this functional subsystem (FSS).

AUTOstop={No|Yes}

Specifies whether JES2 is to automatically stop (shutdown) the FSS address space when all devices attached to the FSS are drained.

HASPFSSM={HASPFSSM|accccccc}

The 1 to 8 character name of the load module that is loaded into the functional subsystem address space. This load module contains the various JES2-supplied FSI service routines.

PROC=accccccc

The 1 to 8 character name of the JCL procedure (usually in SYS1.PROCLIB) required to start the functional subsystem.

Default: The value specified as the FSS token (accccccc).

Authority Required

This command requires system authority. The description of the $T RDRnn command explains how to ensure that the authority of the appropriate MVS™ system command group is assigned.

This command requires control security access authority. For a description of assigning command input authority, see z/OS JES2 Initialization and Tuning Guide, SA32-0991.

Processing Considerations

When you dynamically define an FSS to JES2, its specifications are carried across a restart of JES2 only if you perform a hot start. To permanently define the functional subsystem, add a new FSS initialization statement before restarting JES2.

Scope

Single Member. The values supplied for this command will be in effect for this member only.

Depending on your installation's setup, however, you might want this command to be applied to all members of the MAS (to ensure a consistent environment across the MAS). If so, you can use the MVS ROUTE *ALL command to issue this command to all active members (if the JES2 command character is the same on all members). See z/OS MVS System Commands, SA38-0666 for more information on using the ROUTE *ALL command.

Messages

The $HASP824 message displays the current values of all the parameters that define this functional subsystem.