JES2 is responsible for controlling all system input devices, initiators,
and output devices, except those devices controlled by the external
writer and programs interfacing with JES2 through an internal reader.
The JES2 initiator and device control commands, except the $T command
for devices, can be used to control several local and/or remote devices
simultaneously. You can specify local input and output devices by
either their full or abbreviated names. The device namesand their abbreviations are:
Device Name |
Abbreviation |
Explanation |
---|
LINE(nnnn) |
LNE(n) |
RJE or NJE line (1-32767) |
LOGON(n) |
LGN(n) |
JES2/VTAM interface |
NETSERV(n) |
NSV(n), NETSRV(n) |
JES2 TCP/IP interface |
L(n).JR(n) |
|
NJE job receiver |
L(n).JT(n) |
|
NJE job transmitter |
L(n).SR(n) |
|
NJE SYSOUT receiver |
L(n).ST(n) |
|
NJE SYSOUT transmitter |
OFFLOAD(n) |
|
Offload device |
OFF(n).JR |
|
Offload job receiver |
OFFn.JT |
|
Offload job transmitter |
OFFn.SR |
|
Offload SYSOUT receiver |
OFFn.ST |
|
Offload SYSOUT transmitter |
PRINTERnnnn |
PRTnnnn |
Local printers 1-32767 |
PUNCHnn |
PUNn |
Local punches 1-99 |
RDI |
|
All internal readers 1-32767 |
READER(nn) |
RDR(nn) |
Local readers |
R(nnnn).CON* |
|
Remote console |
R(nnnn).PR(m)* |
|
Remote printers |
R(nnnn).PU(m)* |
|
Remote punches |
R(nnnn).RD(m)* |
|
Remote readers |
All JES2 input devices, initiators, and output devices are in one
of several states:
- Active: The device or initiator is actively
performing a function.
- Inactive: The device or initiator is available
to perform a function, but no jobs are available.
- Startable: A $S command has been issued
for the indicated offload transmitter/receiver, but the corresponding
offload device has not yet been started.
- Starting (JES2): An MVS™ START
command has been issued to activate an initiator, but successful creation
of the address space has not been verified. The initiator is not
processing work and will not do so until a request is made by MVS started
task control to start the initiator job.
- Starting (device): A device supported by
a functional subsystem (such as a 3800-3 printer) has been started
by a $S device command, but successful creation and initialization
of the functional subsystem address space has not been verified.
The device becomes active or inactive when
functional subsystem initialization is complete.
- Draining: The device or initiator is performing
a function, but will not begin any new activity upon completion of
the current function.
- Drained: The device or initiator is inactive
and will not become active until you enter a $S command for the
device or initiator.
- Halting: The initiator is active, but will
not select another job after completing the current function.
- Halted (initiator): The initiator is inactive
and will not become active until you enter a $S command. This
differs from drained because the system does not free the resources
associated with the initiator.
- Halted (device): The device has been halted
by a $Z device command or by a requirement for you to perform
an action, such as changing the forms, carriage tape, or print train.
A $S device command will allow the device to continue.
- Paused: The local printer or punch has paused
between data set groups. It can be restarted by entering a $S command
or by resetting it from a not-ready to a ready state.
Keep the following in mind when entering JES2 device control commands:
- You can enter up to 20 operands in a single JES2 initiator command
or device control command.
- Devices generally perform the requested operation after the response
to the command.
- Many commands will accept operands as valid, even though the devices
are unable to perform the requested function.
- If you enter an incorrect operand on a device command other than
a $T device command, JES2 processes all operands preceding the incorrect
operand. The operand in error, and those that follow, are ignored.
- Operators at JES2 remote workstations can normally control only
the devices attached to their workstations.