Create RJE Configuration (CRTRJECFG)

Create RJE Configuration

The CRTRJECFG command creates the following objects, which are necessary for operating a session in a specific environment:

• Session description
• Job queues
• Message queue
• Subsystem description
• Job descriptions
• Line, controller, and device descriptions
• Communications or BSC files
• Printer and physical files.

A configuration must be created for each environment (host subsystem or line type).

If you decide not to use this command, you can use other CL commands to create these objects individually.

Error messages for CRTRJECFG

*ESCAPE Messages

RJE0013

RJE configuration for session &1 was not created.

RJE5303

Create RJE Configuration (CRTRJECFG) command was canceled.

Parameters

Session (SSN)

Specifies the session name associated with the configuration being created. The name specified is also the name of the session description, subsystem description, and message queue.

The possible values are:

• QRJE: QRJE is the name of the session, the session description, the subsystem description, and the message queue.
• RJE-session-name: Specify the name of the session, the associated session description, subsystem description, and message queue.

Configuration Lib (CFGLIB)

Specifies the name of the configuration library that stores the RJE configuration objects (other than the line, controller, and device descriptions) being created.

The possible values are:

• QRJE: The IBM-supplied library (QRJE) stores the objects.
• RJE-configuration-library-name: Specify the name of the configuration library.

Host System Type (TYPE)

Specifies the host subsystem type with which the session communicates.

The possible values are:

• *JES2: MVS/SP JES2 is used.
• *JES3: MVS/SP JES3 is used.
• *RSCS: VM/SP RSCS is used.
• *PWR: VSE/POWER subsystem is used.
• *RES: OS/VS1 RES is used.

Communication Line Type (LINTYPE)

Specifies the type of communications line or protocol that is associated with this configuration.

The possible values are:

• *BSC: A point-to-point line with the BSC communications protocol is used.
• *SDLCS: A secondary line with SDLCS communications protocol is used. The SDLC link (station) address of the server system is specified by the STNADR parameter.
• *X25: A connection to an X.25 network is used.
• *LAN: A line connection to a token-ring network is used.

Host Logon Command (LOGON)

Specifies the signon (logon) value the host subsystem receives from the server system.

Note: For formatted logons, this value must equal the value expected at the host subsystem.

The possible values are:

• *PROMPT: An input display is used to assist in assigning the signon text. LOGON(*PROMPT) is not valid for LINTYP(*BSC) when a device name (DEV parameter) is specified.
• *NONE: If LINTYP(*SDLCS) is specified, the host subsystem uses the SIMLOGON feature (no signon or logon text).
• 'host-system-signon/logon-text': Specify up to 80 characters of text, enclosed in apostrophes, for the signon or logon information for the host subsystem. (For BSC, if the controller description already exists, any value entered here is ignored because the logon text is specified in the controller description.)

Note: Apostrophes are not needed if the prompt is used to enter the text.

Format SNA Logon (FORMATTED)

Specifies (for SNA only) whether the signon text is formatted.

The possible values are:

• *NO: The signon text is not formatted.
• *YES: The signon text is formatted. This text must be entered in uppercase characters and must match the host system data.

Number of Readers (RJERDRS)

Specifies the number of readers supported by the session.

For LINTYP(*BSC), a device description, BSC file, and job queue are created for each reader. Associated reader and communications entries are added to the session description.

For LINTYP(*SDLCS), LINTYP(*LAN), and LINTYP(*X25), a job queue is created for each reader. Associated reader entries are added to the session description. Unless the number of readers specified is 0, a job queue and a reader entry provide the automatic reader function for either SDLC or BSC.

The possible values are:

• 3: The default is three readers.
• number-of-readers: Specify the number of readers supported by the session. Valid values range from 0 through 15 readers. Objects are created for each SNA or BSC reader. The entries associated with the reader are added to the session description.

Number of Printers (RJEPRTS)

Specifies the number of printers supported by the session.

For LINTYP(*BSC), a device description, a BSC file, and an output printer file are created for each printer. Associated writer and communications entries are added to the session description.

For LINTYP(*SDLCS), LINTYP(*LAN), and LINTYP(*X25), an output printer file is created for each printer. Associated writer entries are added to the session description.

The possible values are:

• 3: The default is three printers.
• number-of-printers: Specify the number of printers supported by the session. Valid values range from 0 through 15 printers.

Number of Punches (RJEPUNS)

Specifies the number of punches supported by the session.

For LINTYP(*BSC), a device description, a BSC file, and an output physical file are created for each punch device. Associated writer and communications entries are added to the session description.

For LINTYP(*SDLCS), LINTYP(*LAN), and LINTYP(*X25), an output physical file is created for each punch device. Associated writer entries are added to the session description.

The possible values are:

• 3: The default is three punches.
• number-of-punches: Specify the number of punches supported by the session. Valid values range from 0 through 15 punches. The number depends on the host subsystem and the line protocol supported by the session.

User Data (USRDATA)

Specifies whether the user data field of the printer spooled file is overwritten with the two-byte configuration identifier plus the current system date stamp.

The possible values are:

• *SAME: The value specified for the user data field of the printer spooled file does not change.
• *SYSDATE: The user data field is overwritten. The description does not change.
• *PRTF: The user data field is not overwritten.

Separate Files (SEPFILE)

Specifies whether jobs with multiple data sets have separate output files created for them when they specify the same form type and number of copies.

This parameter will affect output directed to any of the destinations that RJE supports:

• Diskette files (spooled)
• DDM files
• Physical file members
• Printer files (spooled or non-spooled)
• User programs.

Some host subsystems send a PDIR before every data set; others send one at the beginning of the job, and after that only if the following data set has setup changes. Subsystems that support PDIRs before each data set are MVS/SP JES2 and MVS/SP JES3, the latter only if PDIR=ALL is specified on the device statement for the SNA workstation definition.

This parameter applies only to SNA sessions.

The possible values are:

• *NO: RJE writes each print or punch data set in a job to the same output file. If, however, a host data set specifies a different form type or number of copies than the previously received data set of the job, RJE will begin a new output file.
• *YES: RJE writes each printer or punch data set in a job to a new file.

If your host subsystem does not fully support PDIRs, specifying *YES or *NO for this parameter has no effect. (The OS/VS1 RES and VSE/POWER subsystems do not fully support PDIRs.)

BSC Spooled File (SPLFNAME)

Specifies the name of the spooled file for printer or punch device output. This parameter applies only to BSC sessions.

Note: SNA sessions use the job name in the peripheral data set information record (PDIR) sent from the host subsystem.

The possible values are:

• *DEVFNAME: The spooled file name is the same as the printer file name.
• *JOBNAME: The spooled file name is the same as the job name received in the job name message of the BSC host subsystem.

Block Length (BLKLEN)

Specifies the maximum block length (in bytes) of the data being sent and received.

For LINTYP(*BSC), the default block length is 400, but a block length up to 8192 can be specified. The value specified must equal the block length specified for the host subsystem.

For LINTYP(*SDLCS) and LINTYP(*X25), the default block length is 256, but any block length up to 4096 that is a multiple of 256 can be specified. The value specified is the same as the request/response unit (RU) size specified at the host subsystem, and it is used on the MAXLENRU parameter in the CRTDEVHOST command. The BLKLEN parameter on the CRTRJECMNF command is assigned the value (*CALC).

Output Rcd Lngth (OUTRCDLEN)

Specifies the record length of data that is received from the host and written to an output file.

The possible values are:

• *FIXED: RJE re-blocks the data according to its own defaults, which are as follows:
  • When an RJE printer is processing the output stream:
    • If data is being written to a printer file, it is re-blocked to 132-byte records for 10 or fewer characters per inch (cpi), and 198-byte records when the cpi is greater than 10.
    • If data is being written to a physical file, it is re-blocked to 132-byte records.
  • When an RJE punch is processing the output stream, the data is re-blocked to 80-byte records.
  • For diskette files, the output stream is re-blocked to 128-byte records.
• *FILE: RJE re-blocks the output stream as follows:
  • When an RJE printer is processing the output stream:
    • If data is being written to a printer file, the record length is determined by the page width of the printer file.
    • If data is being written to a physical file, the record length of the output data is determined by the record length of that file.
  • When an RJE punch is processing the output stream:
    • If data is being written to a printer file, the record length is determined by the page width of the printer file.
    • If data is being written to a physical file, the record length of the output data is determined by the record length of that file.
  • For diskette files, the output stream is re-blocked to 128-byte records.

  The maximum record length that RJE supports, including carriage-control characters, is 255 bytes. To ensure record alignment, the record length (page width) of the output file must be greater than or equal to the logical record length of the data that is received from the host subsystem.

Snd as Transparent (TRNSPY)

Specifies (for BSC only) whether text transparency is used to send blocked records. Text transparency allows all 256 EBCDIC character codes to be sent. This is used to transmit packed or binary data fields. The value must equal the value specified for the host subsystem.

1. ASCII text transparency is not supported by the operating system.
2. Transparency of received data is determined by the data stream; therefore, this parameter does not apply to received data.

The possible values are:

• *NO: Text transparency is not used. Files sent do not contain data characters less than hex 40.
• *YES: Text transparency is used. Files sent contain data characters less than hex 40. If *YES is specified for this parameter, *NO must be specified for the DTACPR parameter.

Compress Output (DTACPR)

For BSC only, specifies whether data compression is performed.

Note: The value must be the same as the value specified for the host subsystem. For SNA, data compression is controlled by the bind request sent by the host subsystem.

The possible values are:

• *YES: Data compression is performed. If *YES is specified for this parameter, *NO must be specified for the TRNSPY parameter.
• *NO: Data compression is not performed.

Forms Cntrl Table (FCT)

Specifies the qualified name of the FCT associated with this session. To create the FCT, use the CRTFCT command.

The possible values are:

• *NONE: An FCT is not specified.

  The possible library values are:

  • *LIBL: The library list for the job is used to locate the FCT.
  • *CURLIB: The current library for the job is used to locate the FCT. If no current library is specified, QGPL is used.
  • library-name: Specify the name of the library where the FCT is located.
• forms-control-table-name: Specify the name of the FCT.

Output Queue (OUTQ)

Specifies the qualified name of the output queue that contains output being sent to the printer. The output queue name is the queue name for the job description and printer files created as a result of this command.

Only one set of RJE job descriptions is created in a configuration library. The first RJE configuration created in a library specifies an output queue. Additional configurations in the library use the existing job descriptions and their output queues. Use the Create Output Queue (CRTOUTQ) command to create an output queue.

The possible library values are:

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

The possible values are:

• QPRINT: The IBM-supplied output queue, QPRINT, is used.
• output-queue-name: Specify the name of the output queue.

Resource Name (RSRCNAME)

Specifies the resource name that identifies the hardware that the description represents. Use the Work with Hardware Resources (WRKHDWRSC) command to determine the resource name.

The resource name consists of the input/output adapter (IOA) resource name and the port number on the IOA. For example, if the resource name of the IOA is LIN01 and the port on the IOA is 2, then the resource name would be LIN012.

Configuration ID (CFGID)

Specifies the two-character identifier that is used to name RJE objects associated with this configuration. This value must be unique because all line, controller, and device descriptions are stored in the QSYS library.

The possible values are:

• 01: The two-character identifier is 01.
• RJE-configuration-identifier: Specify a two-character alphanumeric identifier.

Note: The only special characters you can use are: @, #, $.

Devices (DEV)

Specifies the device description objects associated with the host subsystem and this configuration.

The possible values are:

• *GEN: The device descriptions are created by RJE. This also allows RJE to create the controller and line description if CTL(*GEN) is used.
• device-description-name-list: Specify up to 46 device description names associated with the host subsystem. For BSC, the minimum number of devices must equal the sum of readers (RJERDRS parameter), printers (RJEPRTS parameter), and punches (RJEPUNS parameter), plus two (one for console input, the other for console output).

The BSC devices must be specified in the proper order to appear correctly in the session description display. The proper entry order is the input console, the output console, the printers, the punches, and then the readers.

To create a device description for a device to use with the host subsystem, use the Create Device Description (SNA Host) (CRTDEVHOST) command for SNA devices, and the Create Device Description (BSC) (CRTDEVBSC) command for BSC devices.

Controller Description (CTL)

Specifies the controller associated with the host subsystem.

The possible values are:

• *GEN: The controller and line descriptions are created by the RJE configuration. The line interface is RS232V24.
• controller-name: Specify the name of the controller.

  Both the controller description and the line description must be created manually.

  • To create a controller description, use the CRTCTLHOST command for SNA, or the CRTCTLBSC command for BSC.
  • To create a line description, use the CRTLINSDLC command for SDLC lines, the CRTLINTRN command for token-ring networks, the CRTLINX25 command for X.25 lines, or the CRTLINBSC command for BSC lines.

Phys Interface (INTERFACE)

Specifies the type of physical interface on the input/output adapter port.

The possible values are:

• *RS232V24: RS-232/V.24 physical interface (BSC, SDLC only).
• *V35: V.35 physical interface (BSC, SDLC only).
• *X21: X.21 physical interface (SDLC only).
• *X21BISV24: X.21 BIS/V.24 physical interface (BSC, SDLC only).
• *X21BISV35: X.21 BIS/V.35 physical interface (BSC, SDLC only).

Connection Type (CNN)

Specifies the type of line connection used.

Note: This parameter applies only if *GEN was specified on the DEV and CTL parameters.

The possible values are:

• *NONSWTPP: A point-to-point nonswitched connection is used.
• *SWTPP: A switched connection, accomplished by telephone dial-up, is used.
• *MP: A multipoint connection is used. This parameter value applies only if *SDLCS is specified on the LINTYP parameter.

Linespeed (LINESPEED)

Specifies the line speed in bits per second (bps).

The possible values are:

• 9600: The default is 9600 bits per second.
• data-rate: Specify the data rate in bits per second. Valid values are: 600, 1200, 2400, 4800, 7200, 9600, 14400, 19200, 48000, 56000, 57600, or 64000 bits per second.

Values greater than 19200 cannot be used with the RS-232/V.24 interface.

Switched Ntwk Backup (SNBU)

Specifies, for controllers attached to nonswitched lines only, whether the switched network backup (SNBU) feature is activated or deactivated. This feature lets you bypass a broken nonswitched connection by establishing a switched connection. This parameter applies only if SWITCHED(*NO) and SNBU(*YES) were specified when the controller description was created.

Note: *GEN must be specified on the DEV and CTL parameters.

The possible values are:

• *NO: The nonswitched line modem does not have the switched network backup feature.
• *YES: The nonswitched line modem has the switched network backup feature. To activate the feature when nonswitched connections are broken, specify *YES on the ACTSNBU parameter on both the Change Line Description and Change Controller Description commands.

NRZI Decoding (NRZI)

Specifies whether non-return-to-zero-inverted (NRZI) data encoding is used for modems that are sensitive to certain bit patterns in the data stream. This ensures that the signal does not stay the same for an extended period of time. This parameter applies only if *GEN is specified on the DEV and CTL parameters and *SDLCS is specified on the LINTYP parameter.

Note: All data communications equipment on the line must use the same transmission method.

The possible values are:

• *NO: NRZI data encoding is not used.
• *YES: NRZI data encoding is used.

If the field is left blank, the keyword NRZI is not applicable.

Duplex (DUPLEX)

Specifies whether request-to-send (RTS) is set on permanently (for full-duplex modems) or only when transmission is required (for half-duplex modems).

Note: This parameter applies only if *GEN is specified on the DEV and CTL parameters.

The possible values are:

• *FULL: RTS should be permanently set on (for full-duplex modems).
• *HALF: RTS should be turned on only when transmission is required (for half-duplex modems). You can run half-duplex even if the modem can support full-duplex communication. Data is sent in one direction at a time.

Modem (MODEM)

Specifies the type of modem that supports the communications line. This parameter applies only if *GEN is specified on the DEV and CTL parameters.

Refer to the modem manual for the appropriate value to select.

The possible values are:

• *NORMAL: No attempt is made to run diagnostic tests to the modem.
• *V54: A certain type of diagnostic test (as defined by the CCITT recommendations) is run to the modem. The operating system supports CCITT V.54 loop 3, local loop back, and loop 2, which is remote loop back.
• *IBMWRAP: An IBM modem with wrap test capabilities is used on the communications line.
• *IBMLPDA1: An IBM modem with Link Problem Determination Aid-1 (LPDA-1) is used on the line.
• *IBMLPDA2: An IBM modem with Link Problem Determination Aid-2 (LPDA-2) is used on the line.

Unit Address List (UNITADR)

Specifies the unit address of the device associated with the host subsystem for the LU-(logical unit)-to-LU communications in an SNA communications environment. The number of LUs supported depends on the limitations of the host subsystem. This parameter applies only if DEV(*GEN) and SNA line types are specified.

A device description and communications file are created for each unit address. Associated communications entries are added to the session description.

Note: To minimize interruptions during processing, the number of LUs should be the sum of the number of readers (specified by the RJERDRS parameter), printers (RJEPRTS), and punches (RJEPUNS), plus one. Direct-workstation input is accepted only if there are at least two idle LUs.

The possible values are:

• *GEN: The unit address for the device description is used. The number of unit addresses that are created equals the sum of the readers (RJERDRS parameter), printers (RJEPRTS parameter), and punches (RJEPUNS parameter), plus one for console support. Assigned unit addresses range from hex 01 through hex 2E.
• unit-address-list: Specify the logical unit address (in hexadecimal notation) or the list of addresses.

Station Address (STNADR)

Specifies, for LINTYP(*SDLCS), DEV(*GEN), and CTL(*GEN) only, the station address to which the local system responds when polled by the host system if it answers a call. It has a two-digit hexadecimal value between 01 and FE.

SSCP Identifier (SSCPID)

Specifies the system service control point (SSCP) identifier of the host subsystem. This applies only when LINTYP(*SDLCS), DEV(*GEN), and CTL(*GEN) are specified.

Note: The SSCP identifier is a 12-digit hexadecimal value, in which the first two digits are hex 05.

Exchange ID (EXCHID)

Specifies the hexadecimal exchange identifier that is used to identify the local system to the remote system. The eight-digit hexadecimal exchange identifier contains three digits for the block number and five digits for the identifier of this system. This applies only when LINTYP(*SDLCS), DEV(*GEN), and CTL(*GEN) are specified.

The possible values are:

• *SYSGEN: When an exchange identifier is needed, the server system creates one internally.
• exchange-identifier: Specify the identifier of the server system. The exchange identifier is a hexadecimal value in the format nnnxxxxx, where nnn is the block number (which must be 056) and xxxxx is the system identifier.

Max Frame Size (MAXFRAME)

Specifies the maximum frame (path information unit (PIU)) size that the controller can send or receive. This value is used to calculate request unit (RU) sizes. Because the maximum PIU size that the controller can send or receive is negotiated at exchange identifier time, the maximum PIU size used at run time may be different. This value matches the corresponding value on the host subsystem. This applies only when LINTYP(*SDLCS), DEV(*GEN), and CTL(*GEN) are specified.

maximum-frame-size: Specify one of the following values for the maximum frame size for this controller:

• 265 bytes
• 521 bytes (the default)
• 1033 bytes
• 2057 bytes.

Switched Connection (CNNNBR)

Specifies, for switched lines, the telephone number used to establish a switched connection on this line description. This parameter value is sent to the automatic call unit if automatic calling is used to establish a switched connection, or it is sent to the V.25 bis modem if V.25 bis automatic dialing is used to establish the connection. When manual dialing is used to establish a switched connection on the line, this number is displayed to the system operator. For X.25, this number is the remote DTE address for the SVC provided by the X.25 network. This applies only when DEV(*GEN) and CTL(*GEN) are specified.

The possible values are:

• *NONE: There is no telephone number for the controller.
• connection-number: Specify the telephone number of the controller. It uses the digits 0 through 9, and two other special characters: the separator character and the end-of-number character. The separator character is designated by the keyboard's apostrophe symbol, and the end-of-number character is designated by the asterisk symbol.

Remote ID (RMTID)

Specifies, for CTL(*GEN) and DEV(*GEN) only, a list of identifiers for remote BSC controllers. This parameter applies only to switched lines. It is required if SWITCHED(*YES) or SNBU(*YES) is specified.

The possible values are:

• *NONE: A remote identifier is not specified. Do not confuse this value with *NOID, which is a valid remote identifier.
• *NOID: A null remote identifier.
• *ANY: Any remote identifier sent by the host controller.
• remote-identifier: Specify a remote identifier. If a two-character identifier is specified, both characters must be the same. The identifier cannot contain BSC control characters.

Automatic Dial (AUTODIAL)

Specifies, for CTL(*GEN) and DEV(*GEN) only, whether the automatic dialing feature is installed. This feature automatically dials the telephone number of the modem that connects the host subsystem to the server system station. AUTODIAL(*YES) is used only if CNN(*SWTPP) or SNBU(*YES) is specified.

The possible values are:

• *NO: The automatic dialing feature is not installed.
• *YES: The automatic dialing feature is installed.

Automatic Answer (AUTOANS)

Specifies, for CTL(*GEN) and DEV(*GEN) only, whether the automatic answer modem feature is installed. This feature allows incoming calls on the line to connect automatically to communications equipment. AUTOANS(*YES) is used only if CNN(*SWTPP) or SNBU(*YES) is specified.

The possible values are:

• *NO: The automatic answer feature is not installed.
• *YES: The automatic answer feature is installed.

Dial Command Type (DIALCMD)

Specifies, for CTL(*GEN) and DEV(*GEN) only, the type of dial command used to establish a connection with a remote system.

The possible values are:

• *NONE: No dial command type is specified; the autocall unit is used.
• *V25BIS: V.25 bis allows the use of one physical interface for call establishment and data transmission. It is sometimes referred to as a serial automatic call interface, because the digits are presented serially on the link from the system (DTE) to the modem (DCE).

Autocall Unit (AUTOCALL)

Specifies, for CTL(*GEN) and DEV(*GEN) and for switched lines or switched network backup lines, whether the line has an associated automatic call unit that performs automatic calling to the remote system.

The possible values are:

• *NO: The switched line does not have an automatic call unit.
• *YES: The switched line does have an automatic call unit.

Autocall Rsrce (ACRSRCNAME)

Specifies, for CTL(*GEN) and DEV(*GEN) only, the resource name that describes the automatic call unit port. The resource name consists of the input/output adapter (IOA) resource name and the port number on the IOA. For example, if the resource name of the IOA is LIN02 and the port is 1, the resource name is LIN021.

Examples

Error messages

*ESCAPE Messages

RJE0013

RJE configuration for session &1 was not created.

RJE5303

Create RJE Configuration (CRTRJECFG) command was canceled.