DATACK parameter - IBM-JCL

Parameter Type

Keyword, optional

Purpose

Use the DATACK parameter to indicate whether or not print-positioning and invalid-character data-check errors are to be blocked or unblocked for printers accessed through the Print Services Facility (PSF) functional subsystem.

A print-positioning error occurs when the designated position of any kind of printable information is beyond the limits of either the physical page, or the overlay or logical page of which it is part.

An invalid-character data-check error occurs when the hexadecimal representationof a text character has no mapping in the code page to a member of the font raster patterns.

If an error type is unblocked, the printer reports the error at the end of the page in which it occurs, and PSF processes the error and generates an error message.

If an error type is blocked, the printer does not report the error to PSF. Printing continues but data may be lost on the output.

1.Syntax

DATACK= {BLOCK } {UNBLOCK} {BLKCHAR} {BLKPOS }

2.Subparameter Definition

BLOCK
Indicates that print-positioning errors and invalid-character errors are not reported to PSF.

UNBLOCK
Indicates that print-positioning errors and invalid-character errors are reported to PSF.

BLKCHAR
Indicates that invalid-character errors are blocked, and not reported to PSF. Print-positioning errors are reported normally.

BLKPOS
Indicates that print-positioning errors are blocked, and not reported to PSF. Invalid-character errors are reported normally.

3.Defaults
If you do not code the DATACK parameter, the DATACK specification from the PSF PRINTDEV statement is used. If not specified in the PRINTDEV statement, the default is BLOCK. For information about the PRINTDEV statement.

4.Relationship to Other Parameters
If DATACK is specified as UNBLOCK, BLKCHAR, or BLKPOS, and an unblocked error occurs, the printer reports the error to PSF which processes the error. The coding of the PIMSG parameter then determines whether or not printing of the data set continues after the page in error, and if error messages are printed at the end of the data set.

5.Example of the DATACK Parameter

//OUTDS1 OUTPUT DATACK=BLKCHAR,PIMSG=(YES,0)

In this example, when a print-position error occurs, it is reported to the user via a printed error message. If an invalid-character error occurs, it is not reported. In either case, the printing of the data set continues, and all functional subsystem messages are printed.

DEFAULT parameter

Parameter Type

Keyword, optional

Purpose

Use the DEFAULT parameter to specify that this OUTPUT JCL statement can or cannot be implicitly referenced by a sysout DD statement. An OUTPUT JCL statement that contains a DEFAULT=YES parameter is called a default OUTPUT JCL statement.

1.Syntax

DEFAULT= {YES} {Y } {NO } {N }

2.Subparameter Definition

YES
Indicates that this OUTPUT JCL statement can be implicitly referenced by sysout DD statements. This subparameter can also be coded as Y.

NO
Indicates that this OUTPUT JCL statement cannot be implicitly referenced by sysout DD statements. This subparameter can also be coded as N.

3.Defaults
If you do not code DEFAULT=YES, the default is NO. In order to take effect, an OUTPUT JCL statement without DEFAULT=YES must be explicitly referenced in an OUTPUT parameter on a sysout DD statement.

4.Location in the JCL

  • A step-level OUTPUT JCL statement appears within a step, that is, anywhere after the first EXEC statement in a job.
  • A job-level OUTPUT JCL statement appears after the JOB statement and before the first EXEC statement.
  • You can place more than one job- or step-level default OUTPUT JCL statement in a job or step.
  • You must place an OUTPUT JCL statement in the input stream before any sysout DD statement that explicitly or implicitly refers to it.

5.References to Default OUTPUT JCL Statements

  • A sysout DD statement makes an explicit reference in an OUTPUT parameter that specifies the name of an OUTPUT JCL statement.
  • A sysout DD statement makes an implicit reference when it does not contain an OUTPUT parameter, and the job or step contains one or more default OUTPUT JCL statements.
  • A sysout DD statement implicitly references all step-level default OUTPUT JCL statements in the same step.
  • A sysout DD statement implicitly references all job-level default OUTPUT JCL statements when the step containing the DD statement does not contain any step-level default OUTPUT JCL statements.
  • A sysout DD statement can explicitly reference a default OUTPUT JCL statement.

6.Example of the DEFAULT Parameter

In this example, the JOB named EXMP2 contains two job-level OUTPUT JCL statements: OUTDAL and OUTPOK. OUTDAL is a default OUTPUT JCL statement because it contains DEFAULT=YES; OUTDAL can be implicitly referenced by a sysout DD statement. OUTPOK must be explicitly referenced in a sysout DD OUTPUT parameter for its processing options to be used. The purpose of both of these OUTPUT JCL statements is to specify a destination for a sysout data set.

STEP1 contains a step-level OUTPUT JCL statement: OUTHERE. The purpose of this statement is to specify that JES process the data set locally in output class D. OUTHERE can be used only if it is explicitly referenced.

STEP2 contains a step-level default OUTPUT JCL statement: OUTHQ. The purpose of this statement is to specify a destination for a sysout data set. OUTHQ can be implicitly referenced.

The references in this job are as follows:

  • In STEP1 and STEP2, sysout DD statements RPT1 and MONTH explicitly reference OUTPUT JCL statement OUTHERE. These two sysout data sets are printed locally in the same output class.
  • Note: You can explicitly reference an OUTPUT JCL statement in a preceding job step.

  • In STEP1, DD statement RPT2 implicitly references OUTPUT JCL statement OUTDAL. This implicit reference occurs because all of the following are true:
    1. DD statement RPT2 contains a SYSOUT parameter but does not contain an OUTPUT parameter. Thus, this DD statement is making an implicit reference.
    2. STEP1 does not contain a default OUTPUT JCL statement, so the implicit reference must be to job-level default OUTPUT JCL statements.
  • OUTDAL is the only job-level default OUTPUT JCL statement.
  • In STEP2, DD statement SUM implicitly references OUTPUT JCL OUTHQ because all of the following are true:
    1. DD statement SUM contains a SYSOUT parameter but does not contain an OUTPUT parameter. Thus, this DD statement is making an implicit reference.
    2. STEP2 contains a default OUTPUT JCL statement: OUTHQ. Therefore, the implicit reference is to OUTHQ and cannot be to any job-level default OUTPUT JCL statements.
  • In STEP2, DD statement FULRPT explicitly references OUTPUT JCL statements OUTDAL and OUTPOK.

DEPT parameter

Parameter Type

Keyword, optional

Purpose

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

1.Syntax

DEPT= {’department identification’} {department-identification }

Valid Characters Within Enclosing Apostrophes:

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

Valid Characters Without Enclosing Apostrophes: When the value for department 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

department identification
Specifies the department identification associated with the sysout. The value for department 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 DEPT, 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).
In a non-APPC scheduling environment:
There is no default for the DEPT parameter on the OUTPUT JCL statement.

4.Overrides
In an APPC scheduling environment:
In both JES2 and JES3 systems, the DEPT parameter on the OUTPUT JCL statement overrides the department in the RACF profile.

In a non-APPC scheduling environment:
In both JES2 and JES3 systems, there are no override considerations for DEPT.

5.Example of the DEPT Parameter

//OUTDS4 OUTPUT DEPT=’PAYROLL’

In this example, PAYROLL will be printed on the line reserved for DEPT on separator pages of any sysout data set that references OUTDS4.

DEST parameter

Parameter Type

Keyword, optional

Purpose

Use the DEST parameter to specify a destination for the sysout data set. The DEST Parameter can send a sysout data set to a remote or local terminal, a node, a node and remote work station, a local device or group of devices, or a node and userid.

1.Syntax

DEST=destination

The destination subparameter for JES2 is one of the following:

LOCAL|ANYLOCAL’IP:ipaddr’ name Nnnnnn NnRmmmmm NnnRmmmm NnnnRmmm NnnnnRmm NnnnnnRm (node,remote) nodename.userid’nodename.IP:ipaddr’ Rnnnnn RMnnnnn RMTnnnnn Unnnnn userid

The destination subparameter for JES3 is one of the following:

ANYLOCAL’IP:ipaddr’ device-name group-name nodename’nodename.IP:ipaddr’ nodename.remote

2.Subparameter Definition for JES2 Systems

LOCAL|ANYLOCAL
Indicates any local device.

’IP:ipaddr’ | ’nodename.IP:ipaddr’
Identifies a TCP/IP routing designation, where ipaddr can be any printable character string of from 1 to 124 characters. The entire parameter list is limited to 127 characters, and it must be enclosed in single quotes. This keyword is for use only by functional subsystems (for example, IP PrintWay). See the documentation for the particular subsystem for additional information.

name
Identifies a destination by a symbolic name (for example, a local device, remote device, or a userid) which is defined by the installation during JES2 initialization. The name can be, for example, a local device, remote device, or a userid. The name is 1 through 8 alphanumeric or national ($, #, @) characters.

Nnnnnn
Identifies a node. nnnnn is 1 through 5 decimal numbers from 1 through 32,767. For example,N103.

NnRmmmmm
NnnRmmmm
NnnnRmmm
NnnnnRmm
NnnnnnRm
Identifies a node and a remote work station connected to the node. The node number, indicated in the format by n, is 1 through 5 decimal numbers from 1 through 32,767. The remote work station number, indicated in the format by m, is 1 through 5 decimal numbers from 1 through 32,767. Do not code leading zeros in n or m. The maximum number of digits for n and m combined cannot exceed six.

Note: R0 is equivalent to LOCAL specified at node Nn.

nodename.userid
Identifies a destination node and a VM or a TSO/E userid, a remote workstation, or a symbolic name defined at the destination node. The nodename is a symbolic name defined at the node of execution. nodename is 1 through 8 alphanumeric or national ($, #, @) characters. userid is 1 through 8 alphanumeric or national ($, #, @) characters, and must be defined at the specified node.

Rnnnnn
RMnnnnn
RMTnnnnn
Identifies a remote workstation. nnnnn is 1 through 5 decimal numbers from 1 through 32,767. Note that with remote pooling, the installation may translate this route code to another route code.

If you send a job to execute at a remote node and the job has a ROUTE PRINT RMTnnnn statement, JES returns the output to RMTnnnn at the node of origin. For JES2 to print the output at RMTnnnn at the executing node, code DEST=NnnnRmmm on an OUTPUT JCL statement or sysout DD statement.

Note: R0 is equivalent to LOCAL.

Unnnnn
Identifies a local terminal with special routing. nnnnn is 1 through 5 decimal numbers from 1 through 32,767.

If you send a job to execute and the job has a ROUTE PRINT Unnnn statement, JES returns the output to Unnnn at the node of origin.

userid
Identifies a userid at the local node. Userid for TSO/E is 1 through 7 alphanumeric or national ($, #, @) characters. The userid can also be a destination name defined in a JES2 DESTID initialization statement.

Note: JES2 initialization statements determine whether or not the node name is required when coding a userid. See your system programmer for information about how routings will be interpreted by JES2.

3.Subparameter Definition for JES3 Systems

ANYLOCAL
Indicates any local device.

’IP:ipaddr’ | ’nodename.IP:ipaddr’
Identifies a TCP/IP routing designation, where ipaddr can be any printable character string of from 1 to 124 characters. The entire parameter list is limited to 127 characters, and it must be enclosed in single quotes. This keyword is for use only by functional subsystems (for example, IP PrintWay).

device-name
Identifies a local device by a symbolic name defined by the installation during JES3 initialization. device-name is 1 through 8 alphanumeric or national ($, #, @) characters.

group-name
Identifies a group of local devices, an individual remote station, or a group of remote stations by a symbolic name defined by the installation during JES3 initialization. group-name is 1 through 8 alphanumeric or national ($, #, @) characters.

nodename
Identifies a node by a symbolic name defined by the installation during JES3 initialization. The node is 1 through 8 alphanumeric or national ($, #, @) characters. If the node you specify is the same as the node you are working on, JES3 treats the output as though you had specified ANYLOCAL.

nodename.remote
Identifies a destination node and either a remote work station or VM userid at that node, as follows:

nodename
A symbolic name defined by the installation during JES3 initialization. The nodename is 1 through 8 alphanumeric or national ($, #, @) characters.

remote
A name for a remote work station. The name is 1 through 8 alphanumeric or national ($, #, @) characters and must be defined at the node. Enclose it in apostrophes when it contains special characters or begins with a number.

4.Defaults
In a JES2 system, if you do not code a DEST parameter, JES directs the sysout data set to the default destination for the input device from which the job was submitted.

In a JES3 system, if you do not code a DEST parameter, the default destination is the submitting location. For jobs submitted through TSO/E and routed to NJE for execution, the default is the node from which the job was submitted, and the destination ANYLOCAL. If a specified destination is invalid, the job fails.

Note: Most JCL syntax errors are detected and reported by JES or the functional subsystem that is processing the sysout data set, rather than when the system first reads in the JCL.

5.Overrides
A DEST parameter on the sysout DD statement overrides the OUTPUT JCL DEST parameter.

6.Relationship to Other Parameters
For JES3, you can code the DEST=nodename parameter with the OUTPUT JCL WRITER=name parameter; however, do not code DEST=nodename.userid with WRITER=name.

7.Examples of the DEST Parameter

Example

//REMOT1 OUTPUT DEST=R444

In this example, JES2 sends the sysout data set to remote terminal 444.

Example

//REMOT2 OUTPUT DEST=STAT444

In this example, JES sends the sysout data set to an individual remote station named by the installation STAT444.

Example

//REMOT3 OUTPUT DEST=KOKVMBB8.DP58HHHD

In this example, JES sends the sysout data set to VM userid DP58HHHD at node KOKVMBB8.

Example

//REMOT4 OUTPUT DEST=’NEWYORK.IP:bldprt-2’

In this example JES2 sends the sysout data set to node NEWYORK, where a functional subsystem that can process IP-distributed data sets sends the data to the bldprt-2 host system.

Example

//REMOT5 OUTPUT DEST=’IP:9.117.84.53’

In this example the functional subsystem sends the sysout data to the host machine at IP address 9.117.84.53.

DPAGELBL parameter

Parameter Type

Keyword, optional

Purpose

Use the DPAGELBL (data page labelling) parameter to indicate whether the system should print the security label on each page of printed output. The security label represents a security level and categories as defined to RACF.

The security label that the system prints is determined by the SECLABEL parameter of the JOB statement. If you do not specify SECLABEL on the JOB statement, the security level at which the job is executing is printed.

1.Syntax

DPAGELBL= {YES} {Y } {NO } {N }

2.Subparameter Definition

YES
Requests the system to print the security label on each page of printed output. You can also code this parameter as Y.

NO
Requests that the system print no security label on each page of printed output You can also code this parameter as N.

3.Defaults
If you do not code the DPAGELBL parameter, an installation default determines if a security label is printed.

4.Relationship to Other Parameters
Use the DPAGELBL parameter with the SYSAREA parameter on the OUTPUT JCL statement and the SECLABEL parameter on the JOB statement as instructed by your security administrator.

You can code the DPAGELBL parameter with any other OUTPUT JCL statement parameters.

5.Example of the DPAGELBL Parameter

In this example, the security label CONF (specified on the SECLABEL parameter of the JOB statement) is printed on each page of printed output. The sysout data set is printed on forms named VP20.

DUPLEX parameter

Parameter Type

Keyword, optional

Purpose

Use DUPLEX to specify whether or not printing is to be done on both sides of the sheet. This overrides what is specified in the FORMDEF in use.

1.Syntax

DUPLEX={NO } {N } {NORMAL} {TUMBLE}

2.Subparameter Definition

NO or N
Specifies to print on one side only.

NORMAL
Specifies that the physical page is rotated about the Y axis. For most page orientations (including the default orientation), the Y axis is the long edge of the sheet. This allows for binding on the long side of the sheet.

TUMBLE
Specifies that the physical page is rotated about the X axis. For most page orientations (including the default orientation), the X axis is the short edge of the sheet. This allows for binding on the short side of the sheet.

3.Relationship to Other Keywords on This Statement
The DUPLEX keyword overrides the duplex option from the forms definition, which may be specified by the FORMDEF keyword.

4.Example of the DUPLEX Parameter

//OUTDUP OUTPUT DUPLEX=NO

In this example, the output is to be printed in simplex (printed on only one side of the paper).

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

IBM-JCL Topics