Change Session Description (CHGSSND)

Change Session Description

The CHGSSND command changes attributes in an existing session description.

Changes to the session do not take effect until the session is started again.

Error messages for CHGSSND

*ESCAPE Messages

RJE0024: Errors found. Processing of request ended.

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
TYPE	Host system type	SAME, JES2, JES3, RSCS, PWR, RES	Optional, Positional 2
JOBQ	RJE job queue	Single values: SAME Other values: Qualified object name*	Optional
	Qualifier 1: RJE job queue	Name
	Qualifier 2: Library	Name, LIBL, CURLIB
MSGQ	RJE message queue	Single values: SAME Other values: Qualified object name*	Optional
	Qualifier 1: RJE message queue	Name
	Qualifier 2: Library	Name, LIBL, CURLIB
FCT	Forms control table	Single values: SAME, NONE Other values: Qualified object name	Optional
	Qualifier 1: Forms control table	Name
	Qualifier 2: Library	Name, LIBL, CURLIB
IDLETIME	Idle time in minutes	0-99, SAME, NOLIMIT	Optional
USRDTA	User data	SAME, SYSDATE, *PRTF	Optional
TEXT	Text 'description'	Character value, SAME, BLANK	Optional
SEPFILE	Separate files	SAME, NO, *YES	Optional
OUTRCDLEN	Output record length	SAME, FIXED, *FILE	Optional

Top

RJE Session Desc (SSND)

Specifies the qualified name of the session description being changed.

The possible library values are:

*LIBL: The library list for the job is 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 being changed.

Host System Type (TYPE)

Specifies the host subsystem type with which the session communicates.

The possible values are:

*SAME: The host subsystem in the session description does not change.
*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. Session jobs are jobs associated with the RJE session other than RJE reader jobs.

The possible values are:

*SAME: The job queue in the session description does not change.
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.
job-queue-name: Specify the name of the job queue on which the session jobs are placed.

RJE Message Queue (MSGQ)

Specifies the name of the message queue to which messages are sent.

The possible values are:

*SAME: The RJE message queue in the session description does not change.
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 RJE message queue is located.
message-queue-name: Specify the name of the RJE message queue.

Forms Cntrl Table (FCT)

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

The possible values are:

*SAME: The FCT in the session description does not change.
*NONE: An FCT is not associated with this session description.
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 associated with this session.

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:

*SAME: The idle time value in the session description does not change.
*NOLIMIT: End processing of a session is not started unless the ENDRJESSN command is issued.
idletime-in-minutes: Specify the idle time between 0 and 99 minutes.

User Data (USRDTA)

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 which 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:

*SAME: The current value is used.
*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 and VSE/POWER subsystems do not fully support PDIRs.)

Output Rec Lngth (OUTRCDLEN)

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

The possible values are:

*SAME: The record length specified in the session description does not change.
*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.