Restrictions for IEFSSNxx

The following restrictions apply:

• All subsystem definitions in a single IEFSSNxx member must use the same format. A single member cannot contain both positional and keyword definitions.
  • If a member begins with the positional format and switches to the keyword format, processing of the member stops, and the IEFJ002I message is issued. The last subsystem definition processed for the member is the last positional format definition before the switch. The system does not process another definition of either format from the member, but continues processing with the next member, if any.
  • If a member begins with the keyword format and a positional format definition is found, the system issues a syntax error message, and processing continues with the next definition of the keyword format.
  • Once a subsystem name is defined to the system, any attempt to start that subsystem (or any started task with the same name as that subsystem) via a START command which does not explicitly specify SUB=JES2 (or JES3) will result in that subsystem or started task being started under the Master subsystem rather than under the job entry subsystem. Because the only procedure libraries available to the Master subsystem are those specified in the MSTJCLxx's IEFPDSI data set, any procedures being started that are defined in the job entry subsystem's PROC00 data set, but not in the MSTJCLxx's IEFPDSI data set, will be unavailable. Therefore they will not be found; the system will issue message IEFC612I.

Only subsystems that have been defined using the keyword format IEFSSNxx parmlib member, the IEFSSI REQUEST=ADD macro or the SETSSI ADD system command can use the following dynamic SSI services:

• Macros
  • IEFSSI REQUEST=ACTIVATE
  • IEFSSI REQUEST=DEACTIVATE
  • IEFSSI REQUEST=OPTIONS
  • IEFSSI REQUEST=SWAP
  • IEFSSI REQUEST=GET
  • IEFSSI REQUEST=PUT
  • IEFSSVT
• System commands
  • SETSSI ACTIVATE
  • SETSSI DEACTIVATE