RESFMT parameter - IBM-JCL

Parameter Type

Keyword, optional

Purpose

Use the RESFMT parameter to specify the resolution used to format the print data set. PSF will use this value to select the resource libraries for the resolution indicated.

1.Syntax

RESFMT = {P240 | P300}

2.Subparameter Definition

P240
Indicates that the data set was formatted with resources at 240 pels per inch.

P300
Indicates that the data set was formatted with resources at 300 pels per inch.

3.Relationship to Other Control Statements
If RESFMT is the highest priority specified resolution for a data set, then PSF will use the corresponding resource libraries as defined by the system programmer on the PRINTDEV statement.

4.Example of the RESFMT Parameter

//OUTRES OUTPUT RESFMT=P240

In this example, the print data set was formatted for printing at 240 pels per inch.

RETAINS and RETAINF parameyter

Parameter Type

Keyword, optional

Purpose

RETAINS specifies the amount of time to retain a successfully transmitted data set. RETAINF specifies the amount of time to retain a data set that failed to be transmitted. Each of these keywords consists of a numeric value indicating hours, minutes, and seconds.

These parameters apply only to data sets processed by a functional subsystem that can perform Internet Protocol (IP) transmission. JES does not use the RETAINS or RETAINF parameters, but passes them to the functional subsystem during data set selection.

Use RETAINS= when the functional subsystem has successfully transmitted the data set. Use RETAINF= when the functional subsystem employing the IP routing has not successfully transmitted the data set, despite performing all the indicated retries through any RETRY parameters specified. You have the option of manipulating the data set through the facilities provided by the functional subsystem before that subsystem releases the data set to JES.

1.Syntax

RETAINS=’<hhhh>:<mm>:<ss>’ -or- RETAINS=FOREVER RETAINF=’<hhhh>:<mm>:<ss>’ -or- RETAINF=FOREVER

2.Subparameter Definition

<hhhh>:<mm>:<ss>
Specifies the successful (RETAINS=) and failed (RETAINF=) time intervals to retain the data set.

One to ten characters, where <hhhh>, <mm>, and <ss> are numeric. This format requires that for either keyword you enclose the entire parameter in single quotes due to the colon as a special character.

You may specify FOREVER to request the system to retain the data set indefinitely.

You can also specify these keywords by using a dynamic output descriptor.

Only functional subsystems may use these keywords.

3.Relationship to Other Control Statements
The RETAIN keywords interact with the RETRY keywords in determining how long the functional subsystem is to hold on to the data set after either a successful or failed transmission of the data set before releasing it back to JES.

4.Relationship to Other System Functions
The RETAINS and RETAINF keywords can be used by functional subsystem applications (FSAs), such as IP PrintWay, that can perform Internet Protocol (IP) transmission.

5.Examples of the RETAIN Keywords

Example : RETAINS and RETAINF

//OUTRETRY OUTPUT RETAINS=’0001:00:00’,RETAINF=’0002:00:00’

In this example the functional subsystem will not release the data set to JES until one hour after a successful transmission. If the data set was not successfully transmitted, the subsystem will not release the data set to JES until two hours after the last unsuccessful transmission attempt.

Example : RETAINF Only

//OUTRETRY OUTPUT RETAINF=’0003:00:00’

In this example the functional subsystem will retain the data set for three hours following a failed transmission before releasing it to JES.

RETRYL and RETRYT parameter

Parameter Type

Keyword, optional

Purpose

Each of these keywords specifies a numeric value, as follows:

  • RETRYL=limit defines the maximum number of attempts to transmit a data set before the RETAIN keyword options take effect.
  • RETRYT=’retry time’ defines how much time to wait between each attempt to transmit the data set. It is formatted into hours, minutes, and seconds.

RETRYL and RETRYT apply only to data sets processed by a functional subsystem that can perform Internet Protocol (IP) transmission. JES does not use the RETRYL or RETRYT parameters, but passes them to the functional subsystem during data set selection.

1.Syntax

RETRYL=nnnnn RETRYT=’<hhhh>:<mm>:<ss>’

2.Subparameter Definition

<nnnnn>
An integer from 0 to 32,767 (decimal) that specifies the maximum number of retries to attempt before the RETAIN keyword options are to take effect.

<hhhh>:<mm>:<ss>
One to ten characters, where <hhhh>, <mm>, and <ss> are numeric. This format requires that you enclose this entire parameter in single quotes due to the colon as a special character.

These keywords are for use only by functional subsystems such as IP PrintWay. You can also specify these keywords by using a dynamic output descriptor.

3.Relationship to Other Control Statements
The RETRYL and RETRYT keywords interact with the RETAINS and RETAINF keywords to determine the number and frequency of retry attempts to transmit the data set before the values of RETAIN for successful or failed attempts, respectively, take effect.

4.Relationship to Other System Functions
The RETRYL and RETRYT keywords can be used by functional subsystem applications (FSAs), such as PrintWay, that can perform Internet Protocol (IP) transmission.

5.Examples of the RETRY Keywords

Example : RETRYT and RETRYL

//OUTRETRY OUTPUT RETRYT=’0001:00:00’,RETRYL=5

In this example a retry is attempted every hour, for a maximum of five attempts.

Example : RETRYT Only

//OUTRETRY OUTPUT RETRYT=’0000:05:00’

In this example a retry is attempted every five minutes.

ROOM parameter

Parameter Type

Keyword, optional

Purpose

Use the ROOM parameter to print a room identification on the separator pages of the output for a sysout data set. An installation can use the room identification to assist in sysout distribution.

1.Syntax

ROOM= {’room identification’} {room-identification }

Valid Characters in Enclosing Apostrophes:

  • A room identification enclosed in apostrophes can contain any EBCDIC text character.
  • When the value for room identification contains a blank, enclose the value in apostrophes.
  • To code an apostrophe in the room identification, code 2 apostrophes, and enclose the preferred name in single apostrophes. For example:
  • //OUTDS OUTPUT ROOM=’DIRECTOR’’S ROOM’
  • Each value may optionally be enclosed in apostrophes.

Valid Characters Without Enclosing Apostrophes: When the value for room identification is not enclosed in apostrophes, the following characters are valid:

  • Alphanumeric and national (@, $, #) characters
  • Period (.) and asterisk (*); however, an asterisk followed by a period indicates a referral and is not allowed as the start (first and second characters) of the value.
  • Ampersand (&). An ampersand that refers to a symbolic is substituted. Two consecutive ampersands are not substituted, but they will result in a single ampersand as part of the value.
  • Plus sign (+)
  • Hyphen (-).
  • Slash (/)

Symbolic Parameters: Do not enclose symbolic parameters in apostrophes. Symbolic parameters within apostrophes are not resolved for this keyword.

2.Subparameter Definition

room identification
Specifies the room identification to be associated with the sysout. The room identification is 1 - 60 EBCDIC text characters.

3.Defaults

  • In an APPC scheduling environment:
  • In both JES2 and JES3 systems, if you do not code the ROOM parameter on the OUTPUT JCL statement, the system uses the value defined in the transaction program (TP) user’s RACF profile when:
    – The user submitting the TP profile has a RACF profile defined for him, and
    – The transaction program profile includes TAILOR_SYSOUT(YES).
    Otherwise, the system uses the value defined on the transaction initiator’s job statement.
  • In a non-APPC scheduling environment:
  • In a JES2 system, if you do not code the ROOM parameter on the OUTPUT JCL statement, the system uses the 4-character room field defined in the JES2 accounting parameter on the JOB statement.

    In a JES3 system, there is no default for the ROOM parameter on the OUTPUT JCL statement.

4.Overrides

  • In an APPC scheduling environment:
  • In both JES2 and JES3 systems the ROOM parameter on the OUTPUT JCL statement overrides the room defined in the RACF profile. The room in the RACF profile overrides the room defined in the transaction initiator’s job statement.
  • In a non-APPC scheduling environment:
  • In both JES2 and JES3 systems, the ROOM parameter on the OUTPUT JCL statement overrides the 4-character room field defined in the JES2 accounting parameter on the JOB statement.

5.Example of the ROOM Parameter

//OUTDS8 OUTPUT ROOM=’CONFERENCE ROOM’

In this example, CONFERENCE ROOM is printed on the line reserved for ROOM on the separator pages of any sysout data set that references OUTDS8.

All rights reserved © 2020 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

IBM-JCL Topics