Statement Summary

Table 1. DEVICE (Define I/O Device) Summary
Variable	Value
Required/Optional Statement	Required
Statement Default	None
Placement in Initialization Stream	This statement must follow the ENDJSAM statement.
Coding Considerations	Dependent on initialization statements, FSSDEF, MAINPROC, RJPLINE, RJPTERM, SETNAME, RJPWS. Do not code the CKPNTPG and CKPNTSEC parameters on the same DEVICE statement; they are mutually exclusive. If you specify the SELECT parameter, JES3 ignores the HEADER parameter. For a SNA-attached AFP printer, specifying JUNIT=(/devnum...) or JUNIT=(devnum...) is not valid. Instead, you must use a comma as a place holder when specifying the JUNIT parameter. The JUNIT parameter cannot precede the DTYPE parameter. Before specifying LDENS=YES, consult the software component description for the receiving unit to determine whether the software supports the set line density command. If it does not and the command is sent, the results are unpredictable. If the device is any AFP printer other than a 3800 model 3, JES3 assumes MODE=FSS. If you use the RDFEAT parameter, place it following the DTYPE parameter. If you omit the XLATE parameter when defining IBM® 3211, IBM 4245, or IBM 4248 devices, JES3 automatically suppresses translation of unprintable characters since the translation is performed by the device itself (that is, JES3 uses a default value of XLATE=NO for these device types). Devices within a specific XTYPE should have compatible characteristics. For the 3820 printer, XTYPE is not a valid parameter. The XTYPE parameter must precede the XUNIT parameter if you specify both. Do not specify XUNIT for an IBM 3820 printer. If the SELECT parameter is specified, the HEADER and BURST parameters on this statement are ignored and no header, or burst is used. When specifying the SELECT=BEn parameter for two devices, the SELECT parameter can be the same on the two DEVICE statements for those devices. However, the LEN parameters cannot be the same because unpredictable results can occur: For example, the following is the correct way to indicate this in the initialization stream: `DEVICE,DTYPE=RMTPRINT,JNAME=WS000PR1, SELECT=BE2,LEN=1 DEVICE,DTYPE=RMTPRINT,JNAME=WS000PR1, SELECT=BE2,LEN=2` When SELECT=EXn is specified, you cannot define more exchange devices than there are physical disks available to support them. If you specify the EDS parameter for a device that is not a SNA RJP device or for a device that uses Peripheral Data Set Information Record (PDIR) support, JES3 ignores the parameter.
Coding Considerations	The JUNIT parameter has a dependency on the NAME parameter of the MAINPROC statement. During a hot start with refresh, the MAINPROC statement is not processed; the MAINPROC from the last warm or cold start is used. Therefore, if you add a MAINPROC statement during a hot start with refresh, JES3 ignores it. JES3 issues error messages if the JUNIT or XUNIT parameter of the DEVICE statement references a MAINPROC statement that was added during a hot start with refresh.
Security Usage	None
Performance Considerations	None
Initialization Stream Overrides	None. However, for information on output service overrides, see z/OS JES3 Initialization and Tuning Guide.

Table 2. DEVICE (Define I/O Device) Summary - cont.
Variable	Value
Restart or Command Modification	Warm start, cold start, or hot start with refresh for all parameters. Omitting one statement might cause a subgeneric split or loss of a device. Omitting all statements for a device causes loss of the device as a JES3-managed device. Hot start with refresh applies for all parameters. When a hot start with refresh is to be performed, consider the following: You cannot delete an FSS managed device if the FSS is active. It does not matter whether a writer was using the device or not. The exception is if the FSS is active on the global and the global was IPLed before performing the hot start with refresh. You cannot add an FSS managed device to an existing FSS (through the FSSNAME parameter) 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. You cannot change the device number in the JUNIT parameter of an FSS managed device if the FSS is active and a writer is using the device. The exception is if the FSS is active on the global and the global was IPLed before performing the hot start with refresh. You cannot delete a device number/system name from the JUNIT parameter of an FSS managed device if the FSS is active and a writer is using the device. The exception is if the FSS is active on the global and the global was IPLed before performing the hot start with refresh. Omitting one statement might cause a subgeneric split or loss of a device. Omitting all statements for a device causes loss of the device as a JES3 managed device. (This is also true of warm and cold starts.) If an FSS managed device is being used by a writer, the following parameters on the DEVICE statement will be ignored if they are changed. These parameters will be restored from checkpointed information when the writer is started: MODE Online/Offline status (from JUNIT) CKPNT/CKPNTPG/CKPNTSEC NPRO SETUPMSG The exception is if the FSS is active on the global and the global was IPLed before performing the hot start with refresh. Use the `MODIFY,CONFIG` command to dynamically add VTAM® attached FSS printers. You cannot add a DEVICE statement for an FSS managed device if the FSS is active. The FSS must be shut down before adding the device. Use the `MODIFY,T` or `MODIFY,W` command to dynamically modify VTAM attached FSS printers. Use the `MODIFY,F,D=` command to change the MODE parameter. Use the `*MODIFY,W` command to change the DGRPONLY, DYNAMIC, PDEFAULT, SETUPMSG, PDIR, and XLATE parameters.