Statement Summary

Table 1. FSSDEF Summary
Variable	Value
Required/Optional Statement	Optional
Statement Default	None. However, JES3 used the following default if no FSSDEF statement exists when MODE=FSS is specified on a DEVICE statement for an FSS-supported printer: `FSSDEF,TYPE=WTR,FSSNAME=(see note1), SYSTEM=(see note2), PNAME=(see note3),MSGDEST=42,TERM=NO` Note: JES3 uses the name specified on the FSSNAME parameter of the DEVICE statement (if it is coded) or uses the JNAME defined for the device (if the FSSNAME parameter on the DEVICE statement is omitted). If the DEVICE statement specifies the NUMDEV parameter, the JNAME defined for the DEVICE is the JNAME prefix specified on the DEVICE statement combined with the JUNIT determined from the device range, left padded with a zero to a four digit device if the device contains three digits. See the parameter description to determine the default value used for the SYSTEM parameter. See the parameter description to determine the default value used for the PNAME parameter. The default for MSGDEST (routing code 42) is equivalent to JES3 Dest Class JES.
Placement in Initialization Stream	This statement can be placed in any order following the ENDJSAM statement.
Coding Considerations	None
Security Usage	None
Performance Considerations	None
Initialization Stream Overrides	None
Restart or Command Modification	Cold start, warm start, or hot start with refresh for all parameters. The following must be considered when a hot start with refresh is going to be performed: You cannot delete an FSSDEF statement for an FSS if the FSS is active. The exception is if the FSS is active on the global and the global was IPLed before performing the hot start with refresh. If you make changes to an FSSDEF statement for an FSS that is active, JES3 ignores the changes and uses the checkpointed information from when the FSS was started. The exception is if the FSS is active on the global processor and the global was IPLed before performing the hot start with refresh, then your change takes place. The SYSTEM parameter has a dependency on the NAME parameter of the MAINPROC statement. During a hot start with refresh, JES3 does not process the MAINPROC statements, but uses the MAINPROC's from the last warm or cold start. If you add a MAINPROC statement during a hot start with refresh, JES3 ignores it and issues error messages if the SYSTEM parameter of the FSSDEF statement references the MAINPROC statement that you attempted to add during a hot start with refresh. If a writer FSS for a non-VTAM attached printer is not already defined by a DEVICE statement in the initialization stream, you cannot add an FSSDEF statement for the FSS writer. Use the `MODIFY,F` command to change the DSPCNT, MAXASST, START, TERM, SYSTEM, and PNAME parameters. Use the `MODIFY,CONFIG` command to add FSS definitions for non-channel attached FSS managed printers. Use the `MODIFY,T` or `MODIFY,W...` commands to dynamically modify FSS writers. Use FSSDEF with TERM=YES option after an orderly shutdown of JES3. This will incorporate the changes you make in the DYNALLOC, HWSNAME, CIPARM, RESDSN, and SYSOUT initialization statements. Restarting JES3 will establish the new changes.