PAGEDEF parameter - IBM-JCL

Parameter Type

Keyword, optional

Purpose

Use the PAGEDEF parameter to identify a library member that contains statements to tell the Print Services Facility (PSF) how to print the sysout data set on a page-mode printer (such as the Infoprint 4000). The data set may be sysout or a data set that is allocated directly to a printer. The statements can specify the following:

  • Logical page length and width.
  • Fonts.
  • Page segments.
  • Multiple page types or formats.
  • Lines within a page; for example:
  • – Line origin.
    – Carriage controls.
    – Spacing.
  • Multiple logical pages on a physical page.

The member must be in the library named in the cataloged procedure that was used to initialize PSF, or in a library specified in the USERLIB parameter.

Note: PAGEDEF applies only for data sets printed on a page-mode printer controlled by PSF.

1.Syntax

PAGEDEF=membername

2.Subparameter Definition

membername
Specifies the name of the library member. membername is 1 through 6 alphanumeric or national ($, #, @) characters; the first two characters are pre-defined by the system.

3.Overrides
The statements in the library member specified by the OUTPUT JCL PAGEDEF parameter override the installation’s PAGEDEF defaults in the PSF-cataloged procedure.

PSF uses the following parameters, in override order, to select the font list:

  1. Font list in the library member specified by an OUTPUT JCL PAGEDEF parameter.
  2. DD CHARS parameter.
  3. OUTPUT JCL CHARS parameter.
  4. DD UCS parameter.
  5. OUTPUT JCL UCS parameter.
  6. JES installation default for the device.
  7. Font list on the PAGEDEF parameter in the PSF-cataloged procedure.

4.Example of the PAGEDEF Parameter

//OUTDS1 OUTPUT PRMODE=PAGE,PAGEDEF=SSPGE

In this example, PSF is to print the sysout data set on an AFP printer operating in page mode. The printing is to be done according to the parameters in the library member SSPGE.

PIMSG parameter

Parameter Type

Keyword, optional

Purpose

Use the PIMSG parameter to indicate the handling of messages by Print Services Facility (PSF). PIMSG is used to specify whether all error messages are to be printed, and the number of errors sufficient to cause the printing process to be terminated and the data set to be purged.

When you code PIMSG=YES, the system prints all these messages at the end of the output data set.

When you code PIMSG=NO, no messages are printed unless there is an error that forces premature termination of the printing of the data set. If an error occurs, the system prints the set of messages (called a message group) associated with the error that caused the termination.

As errors are detected by PSF or reported to PSF by the printer, a count is kept of the associated message groups. When the count equals the number specified on the PIMSG parameter, PSF terminates the printing of the current data set. PSF interprets a count of zero as infinite, and does not terminate the printing of the data set on the basis of the number of errors detected.

Note: PIMSG can be specified only for data sets printed through PSF.

1.Syntax

PIMSG= {(YES[,msg-count])} {(NO[,msg-count]) }
  • You can omit the parentheses if you do not specify msg-count.

2.Subparameter Definition

YES
Requests the system to print all messages generated by PSF. You can also code this subparameter as Y.

NO
Requests that the system print no error messages, unless printing of the data set is prematurely terminated. If a terminating error occurs, only the set of messages (called a message group) associated with the error that caused the termination is printed. You can also code this subparameter as N.

msg-count
Requests the system to cancel the printing of the current data set after the specified number of errors (as represented by the associated message groups) have been detected by PSF or reported to PSF by the printer. In this context, errors refers to data-stream errors, and errors resulting from any malfunction that would cause the printer to halt, such as a mechanism failure, or out-of-paper condition. However, these errors do not include those caused by operator intervention.

Valid values for msg-count are 0-999, where 0 is interpreted as infinite.

The types of errors that increment the message count are those that induce a message group to be printed at the end of the data set. However, even though the printing of the message groups is inhibited by PIMSG=NO, the associated error still increments the message count. (A message group consists of a primary message and variable number of informational messages that result from a single error.)

In the case that multiple transmissions have been specified for a single data set (user-specified multiple copies), the message count would apply on a per copy basis. If the specified number of errors are discovered during the printing of any copy, the subject copy is terminated, and the remaining copies are not printed.

3.Defaults
If you do not code the PIMSG parameter, the PIMSG specification from the PSF PRINTDEV statement applies. If not specified in the PRINTDEV statement, the default is PIMSG=(YES,16).

4.Examples of the PIMSG Parameter

Example

//OUTDS2 OUTPUT DATACK=UNBLOCK,PIMSG=(YES,0)

In this example, regardless of how many message-generating errors are detected by PSF or reported to PSF by the printer, the printing of the current data set continues to completion or until a terminating error is encountered. All the messages are printed by the system.

Example

//OUTDS2 OUTPUT DATACK=UNBLOCK,PIMSG=(NO,5)

In this example, after five message-generating errors are detected by PSF or reported to PSF by the printer, the printing of the current data set is terminated. Only the last message group is printed by the system.

PORTNO parameter

Parameter Type

Keyword, optional

Purpose

Use the PORTNO parameter to specify the TCP/IP port number at which the FSS (for example, IP Printway) connects to the printer.

1.Syntax

PORTNO=nnnnn

2.Subparameter Definition

nnnnn
Specifies the TCP/IP port number, where nnnnn is a number from 1 through 65,535.

3.Relationship to Other System Functions
The port number must match the port number configured at the printer.

4.Example of the PORTNO Parameter

//OUTPORT OUTPUT PORTNO=5005

In this example, 5005 is the TCP/IP port number.

PRMODE parameter

Parameter Type

Keyword, optional

Purpose

Use the PRMODE parameter to identify the process mode required to print the sysout data set. JES schedules the data set to a printer that can operate in the specified mode. For a list of valid process modes, contact your system programmer.

1.Syntax

PRMODE= {LINE } {PAGE } {process-mode}

2.Subparameter Definition

LINE
Indicates that the data set is to be scheduled to a line-mode printer.

PAGE
Indicates that the data set is to be scheduled to a page-mode printer.

process-mode
Specifies the required process mode. The process-mode is 1 through 8 alphanumeric characters.

For an NJE-transmitted data set, use PRMODE to request specific processing without having to obtain output classes for the node that processes the data set.

3.Defaults
If you do not code the PRMODE parameter, JES schedules output processing as follows:

  • If the sysout data set does not contain page-mode formatting controls, the process mode of line is given to the data set.
  • If the sysout data set contains page-mode formatting controls, the process mode of page is given to the data set.

4.Printing a Line-Mode Data Set Using PSF
To print a line-mode data set using the Print Services Facility (PSF) and an AFP printer, code PRMODE=PAGE. PSF formats this line-mode data set using the installation’s default values for PAGEDEF and FORMDEF defined in the PSF-cataloged procedure; if these defaults are unsatisfactory, code the PAGEDEF and FORMDEF parameters on the OUTPUT JCL statement.

5.Example of the PRMODE Parameter

//DS18 OUTPUT PRMODE=LINE

In this example, JES schedules the sysout data set to a printer with a process mode of line.

PRTERROR parameter

Parameter Type

Keyword, optional

Purpose

Specifies the disposition of the SYSOUT data set used if a terminating error occurs during printing through the PSF functional subsystem. (A terminating error is an error that the automated recovery of PSF cannot correct.) You can specify which of the following actions PSF is to take for a terminating error:

  • Use the default error disposition (DEFAULT),
  • Release the SYSOUT data set back to JES as complete (QUIT), or
  • Hold for operator action (HOLD).

1.Syntax

PRTERROR=(DEFAULT|QUIT|HOLD)

2.Subparameter Definition

DEFAULT
Specifies that PSF will take the standard (default) action if a terminating error occurs during printing. When operator action is expected to correct the error, PSF releases the SYSOUT data set for hold. Otherwise, it treats the SYSOUT data as complete. For JES2, processing of the data set proceeds according to the OUTDISP keyword value that is associated with it. For JES3, the data set is deleted from the SPOOL.

QUIT
Specifies that PSF is to release the data set complete even if a terminating error occurs during printing. JES then disposes of the data set as if it completed printing successfully. For JES2, processing of the data set proceeds according to the OUTDISP keyword value that is associated with it. For JES3, the data set is deleted from the SPOOL.

HOLD
Specifies that if a terminating error occurs during printing, the data set will remain on the JES SPOOL until the system operator releases it.

3.Relationship to Other Control Statements
For the JES2 subsystem, OUTDISP affects the processing when PRTERROR=DEFAULT or PRTERROR=QUIT is performed and PSF releases the data set as complete.

An installation can control (through the PSF PRINTDEV initialization statement) whether the system honors or ignores the specification of the PRTERROR keyword on the OUTPUT JCL statement or dynamic output descriptors.

Note: There are conditions under which PRTERROR has no effect.

4.Examples of the PRTERROR Parameter

Example

//OUTPRTER OUTPUT PRTERROR=HOLD

In this example, if a terminating error occurs during printing, the data set remains on the JES SPOOL until the system operator releases it.

Example

//OUTPRTER OUTPUT PRTERROR=QUIT

In this example, if a terminating error occurs during printing, PSF quits processing the data set and releases it as “complete,” and JES applies processing appropriate for a completed data set.

PRTOPTNS parameter

Parameter Type

Keyword, optional

Purpose

PRTOPTNS defines a named entity that contains additional print options a functional subsystem can use. The PRTOPTNS keyword applies only to data sets processed by a functional subsystem that can perform Internet Protocol (IP) transmission. JES does not use PRTOPTNS, but passes it to the functional subsystem during data set selection.

1.Syntax

PRTOPTNS=<options name>

2.Subparameter Definition

<options data set entry name>
Identifies the print options data. The name can be 1 to 16 characters long. If the name includes any special characters (for example, a dash), enclose the entire parameter in single quotes. You can also specify this keyword by using a dynamic output descriptor.

3.Relationship to Other System Functions
The PRTOPTNS parameter can be used by functional subsystem applications (FSAs), such as IP PrintWay, that can perform Internet Protocol (IP) transmission.

4.Examples of the PRTOPTNS Parameter

//OUTOPTNS OUTPUT PRTOPTNS=’Boulder4019Optns’

In this example Boulder4019Optns is the name of the entity used to reference additional print options.

PRTQUEUE parameter

Parameter Type

Keyword, optional

Purpose

PRTQUEUE defines the name of the target print queue on a remote host system. The PRTQUEUE keyword applies only to data sets processed by a functional subsystem that can perform Internet Protocol (IP) transmission. JES does not use PRTQUEUE, but passes it to the functional subsystem (for example, IP PrintWay), during data set selection.

1.Syntax

PRTQUEUE=<print queue name>

2.Subparameter Definition

<print queue name>
Identifies the target print queue name. The name can be 1 to 127 characters long and may include any printable character. If the name includes any special character (for example, a dash or lower case letter), enclose the entire parameter in single quotes. You can also specify this keyword by using a dynamic output descriptor.

3.Relationship to Other System Functions
The PRTQUEUE parameter can be used by functional subsystem applications (FSAs), such as PrintWay, that can perform Internet Protocol (IP) transmission.

4.Example of the PRTQUEUE Parameter

//OUTQUEUE OUTPUT PRTQUEUE=’4019’

In this example 4019 is the name of the target print queue destination.

PRTY parameter

Parameter Type

Keyword, optional

Purpose

Use the PRTY parameter to specify the priority at which the sysout data set enters the output queue. A data set with a higher priority is printed sooner.

1.Syntax

PRTY=nnn

2.Subparameter Definition

nnn
Specifies the initial priority. nnn is a decimal number from 0 through 255; 0 is the lowest priority while 255 is the highest.

3.Defaults
If you do not code the PRTY parameter, JES3 uses an installation default specified at initialization. JES2 uses a priority that is calculated for all output.

4.Overrides
In JES2 systems, the installation can specify at JES2 initialization that JES2 is to ignore the OUTPUT JCL PRTY parameter.

In JES3 systems, the OUTPUT JCL PRTY parameter is ignored for JES3 networking.

5.Example of the PRTY Parameter

//PRESRPT OUTPUT PRTY=200,FORMS=TOPSEC

In this example, JES prints one copy of the president’s report, PRESRPT, on forms named TOPSEC. Because a priority of 200 is specified, the report is probably printed immediately after entering the output queue.


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

IBM-JCL Topics