Create Session Description (CRTSSND)

Create Session Desc

The CRTSSND command creates a session description that defines the attributes of a session. This is necessary for each session.

After the session description is created, it can be updated with commands that add reader entries, writer entries, and communications entries. For more information, see the descriptions of the ADDRJERDRE, ADDRJEWTRE, and ADDRJECMNE commands.

Error messages for CRTSSND

*ESCAPE Messages

RJE0001

Session description &1 already exists in library &2.

RJE0024

Errors found. Processing of request ended.

RJE0032

Ownership of RJE object not correct.

Parameters

RJE Session Desc (SSND)

Specifies the qualified name of the session description.

The possible library values are:

• *CURLIB: The session description is created in the current job library. If no current library is specified, QGPL is used.
• library-name: Specify the name of the library where the session description is created.

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

Host System Type (TYPE)

Specifies the host subsystem type with which the RJE 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.

RJE Job Queue (JOBQ)

Specifies the qualified name of the job queue on which session jobs are placed.

The possible library values are:

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

The possible values are:

• QRJESSN: The job queue named QRJESSN in the library list is used.

  Note: You must first create this job queue, as it is not supplied as part of Communications Utilities.

• job-queue-name: Specify the name of the job queue.

RJE Message Queue (MSGQ)

Specifies the qualified name of the message queue to which RJE messages for this session are sent.

This message queue contains messages received from, and commands sent to, the host subsystem, and messages sent by RJE jobs. It serves as a job log for RJE jobs in the active session. To see the messages in the queue, issue the STRRJECSL command.

The possible library values are:

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

The possible values are:

• QRJE: The RJE message queue named QRJE in the library list is used.

  Note: You must first create this message queue, as it is not supplied as part of Communications Utilities.

• message-queue-name: Specify the name of the message queue.

Forms Cntrl Table (FCT)

Specifies the qualified name of the FCT associated with this session description.

The possible values are:

• *NONE: An FCT is not used.

  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.

Idle Time in Min (IDLETIME)

Specifies, in minutes, the amount of time that the session can remain idle before it ends in a controlled manner.

If the number of minutes is set to zero and a line connection is made, a controlled ending of the session begins immediately.

If the number of minutes is not set to zero, the idle time countdown begins either following the end-of-file character of the last input or output stream, or following the establishment of the line connection. It is reset each time data becomes available for sending or receiving.

Except for console input streams, if input streams start but do not end (that is, no end-of-file character is received), the idle time countdown does not begin.

Ending a session in a controlled manner consists of holding delivery of the reader job queues, allowing reader and writer jobs to complete, and ending the session and all RJE functions.

If an ENDRJESSN command specifies a controlled ending, its IDLETIME parameter value overrides that of the session description.

The possible values are:

• *NOLIMIT: End processing is not started unless the ENDRJESSN command is issued.
• idletime-in-minutes: Specify a value between 0 and 99 for the number of minutes the session remains idle.

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:

*SYSDATE: The user data field is overwritten. The description does not change.

• *PRTF: The user data field is not overwritten.

Text Description (TEXT)

Specifies text that briefly describes the session description.

The possible values are:

• *BLANK: No text is specified.
• 'description': Specify no more than 50 characters of text, enclosed in apostrophes.

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 dataset 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 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.)

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.

Authority (AUT)

Specifies the authority given to users who themselves and whose user group do not have specific authority to the object.

The possible values are:

• *LIBCRTAUT: The public authority for the object is taken from the CRTAUT keyword of the target library (the library that is to contain the object). This value is determined when the object is created. If the CRTAUT value for the library changes after the object is created, the new value does not affect any existing objects.
• *CHANGE: Public users can change the session description.
• *ALL: Public users have all authority to the session description.
• *EXCLUDE: Public users cannot use the session description.
• *USE: Public users can use the session description, but cannot change it.
• authorization-list-name: Specify the name of an authorization list. Users included on the authorization list are granted authority to the object as specified on the list. The authorization list must exist when the object is created.

Examples

Error messages

*ESCAPE Messages

RJE0001

Session description &1 already exists in library &2.

RJE0024

Errors found. Processing of request ended.

RJE0032

Ownership of RJE object not correct.