Defining RJE workstations to JES2

RJE workstations are defined to JES2 through the following initialization statements and operator commands. (For detailed information about parameter formats, default values, and other coding considerations, see z/OS JES2 Initialization and Tuning Reference and z/OS JES2 Commands.

Table 1. JES2 Initialization Statements and Commands Used to Define a Network
Statement	Purpose	BSC or SNA
APPL(jxxxxxxx)	Associates a JES2 node with a VTAM® application identifier and specifies session characteristics for SNA connections. See z/OS Communications Server: SNA Resource Definition Reference for information about defining application identifiers.	SNA
COMPACT	Defines a compaction table to be used by JES2 in SNA RJE workstation communications.	SNA
DESTID(jxxxxxxx)	Defines the symbolic name for a JES2 route code, which may define a specific RJE workstation.	Both
LINE(nnnn)	Defines the characteristics of a telecommunication line, such as whether it is a logical SNA line (UNIT=SNA) or an actual BSC line (UNIT= the line's unit address).	Both
LOGON(nnn)	Specifies the VTAM application identifier this node uses to communicate with VTAM for an SNA connection.	SNA
RMT(nnnn) $ADD RMT(nnnn)	Defines an RJE workstation to JES2. For SNA RJE workstations, these definitions must specify DEVTYPE=LUTYPE1. LUTYPE1 indicates that this RJE workstation requires a logical line to communicate with JES2. Also, SNA RJE workstations can specify CONS=YES if the workstation contains a remote console. This remote console is considered as one of the eight devices an RJE workstation can possess.	Both
TPDEF	Defines the JES2 teleprocessing characteristics: Buffer size and placement VTAM sessions Message limits for remote consoles Highest number RJE workstation allowed	Both

You can define an RJE workstation on one or more members of a multi-access spool (MAS) configuration, but an RJE workstation can be active on only one member at a time. If an RJE workstation is not defined on a particular member, then no device control blocks (DCBs) are allocated for that RJE workstation on that member. The processor control elements (PCEs) required to support the devices attached to RJE workstations are not allocated until the RJE workstation becomes active and are not freed until the RJE workstation is no longer connected. Also, note that necessary control blocks for BSC RJE workstations on dedicated lines are built when the line is started.

An installation must specify a RMT(nnnn) statement or a $ADD RMT(nnnn) command to define an RJE workstation. Specify the highest number for an RJE workstation allowed on a member through the RMTNUM= parameter on the TPDEF initialization statement. The RMTNUM= parameter defines the virtual storage (68 bytes below 16 Mb in virtual storage for each RJE workstation) for RJE workstations. If RMTNUM=99, JES2 provides enough virtual storage for 99 RJE workstations whether those RJE workstations have been defined or not. If, at initialization, your highest-numbered RJE workstation is numbered above the RMTNUM= value, for example, you define RJE workstation 106, JES2 accepts the definition, increases RMTNUM= to 106, and responds with the following informational message:

$HASP510 TPDEF RMTNUM PARAMETER INCREASED TO 106

where 106 is the highest–numbered RJE workstation specified at initialization. By defining RJE workstation (RMT106) be aware that you have left a ‘gap’ of six (RMT100 through RMT105) RJE workstations that are available for future definition.