Add RJE Communication Entry (ADDRJECMNE)

Add RJE Comm Entry

The ADDRJECMNE command adds a communications or a BSC file entry to an existing session description. If an entry is added to a session description while the session is active, the change does not take effect until the session is ended and started again.

Each entry refers to a unique communications or BSC file. All files must reference devices attached to the same controller.

For SNA, there must be at least one communications entry to operate RJE. There must be at least two communications entries if you are using direct-workstation input.

There is a maximum of 46 communications entries. Too many burdens the operating overhead, while too few interrupts functions. If more devices are used than communications entries, the entries must be shared among the devices.

BSC requires two communications entries to start a session: one for console input jobs, and one for console output jobs. In addition, one is required for each active reader or writer in the session.

Error messages for ADDRJECMNE

*ESCAPE Messages

RJE0024: Errors found. Processing of request ended.
RJE0036: Maximum of &1 &2 entries was surpassed.
RJE0082: Communications entry &1 already exists in &3.

Parameters

Keyword	Description	Choices	Notes
SSND	RJE session description	Qualified object name	Required, Positional 1
	Qualifier 1: RJE session description	Name
	Qualifier 2: Library	Name, LIBL, CURLIB
FILE	BSC/CMN file	Qualified object name	Required, Positional 2
	Qualifier 1: BSC/CMN file	Name
	Qualifier 2: Library	Name, LIBL, CURLIB
DEV	BSC/CMN device	Name, *FILE	Optional, Positional 3
DTACPR	Compress output data	FILE, YES, *NO	Optional

Top

RJE Session Desc (SSND)

Specifies the qualified name of the session description to which the communications entry is added.

The possible library values are:

*LIBL: The library list for the job used to locate the session description.
*CURLIB: The current library for the job is used to locate the session description. If no current library is specified, QGPL is used.
library-name: Specify the name of the library where the session description is located.

session-description-name: Specify the name of the session description.

BSC/CMN File (FILE)

Specifies the qualified name of the communications or BSC file entry that is added to the session description.

The possible library values are:

*LIBL: The library list for the job is used to locate the communications or BSC file.
*CURLIB: The current library for the job is used to locate the communications or BSC file. If no current library is specified, QGPL is used.
library-name: Specify the name of the library where the communications or BSC file is located.

communications-or-BSC-file-name: Specify the name of the communications or BSC file.

BSC/CMN Device (DEV)

Specifies the communications device to and from which the communications or BSC files send and receive data.

The possible values are:

*FILE: The communications device in the communications or BSC file is used.
device-name: Specify the name of the communications device. This device replaces the device that was specified when the communications or BSC file was created.

Compress Output (DTACPR)

For BSC only, specifies whether data compression is performed.

Note: For SNA, data compression is controlled by the bind request, which is sent by the host subsystem.

The possible values are:

*FILE: Data is compressed according to the specifications in the BSC file.
*YES: Data is compressed.
*NO: Data is not compressed.