Output queues

Normally, JES3 places output data produced by a job on one of the following: output queues when the job ends. (Spin-off data sets are placed on an output queue while the job is still in processing.)

Output service writer queue (Q=WTR): This queue contains data sets waiting to be processed by JES3 output service writers, process SYSOUT (PSO), SYSOUT application program interface applications, and also data sets directed to users on other nodes in a BSC/NJE job entry network. These data sets include data sets directed to JES3 printer or punch devices. The output service writers automatically process data sets on this queue based on writer-selection characteristics such as output device-related requirements, output class, and output priority. You can temporarily place data sets on this queue in operator hold status.
Output service hold queue (Q=HOLD): This queue contains data sets waiting to be processed by system routines other than JES3 output service writers. These data sets include data sets directed to local TSO/E users, to devices other than JES3 print and punch devices, and to the JES3 internal reader.
Data sets on this queue must be processed by the function for which they are being held. The respective functions can then release the data set to an output service writer for processing, or cause the data set to be purged. If necessary, you can force the data set to be processed by JES3 (see Changing the HOLD queue for more information).
Output service BDT queue (Q=BDT): This queue contains network job and SYSOUT streams that are waiting to be transmitted to other nodes in a JES3 SNA/NJE network through the MVS™ Bulk Data Transfer (MVS/BDT) subsystem.
Output service TCP/IP queue (Q=TCP): This queue contains network job and SYSOUT streams that are waiting to be transmitted to other nodes in a JES3 TCP/IP/NJE network through the JES Common NJE component (IAZNJTCP).

You can use the *INQUIRY,U and *MODIFY,U commands to display or alter information related to data sets on each queue.

Information about data sets on each queue is qualified in several ways. The three highest levels are: (1) the amount of work of a general type (PRT or PUN) that exists on the queue; (2) the amount of work of a general type for particular jobs; (3) the amount of work of a general type for a particular job on a data set-by-data set basis. If you consider work on the queue as being qualified in these three levels, information received in response to *INQUIRY,U commands can be very useful.