CCSID parameter use - IBM-JCL

Parameter Type

Keyword, optional

Purpose

On systems with DFSMS/MVS Version 1 Release 5 or higher, and OS/390 Version 2 Release 5 or higher, you can request DFSMSdfp to convert data from/to the coded character set identifier (CCSID) specified on the JOB or EXEC statement to/from the CCSID specified on the DD statement. Data conversion is supported on access to ISO/ANSI Version 4 tapes using access methods BSAM or QSAM, but not using EXCP.

ISO/ANSI Version 4 tapes are identified by the LABEL=(,AL) or LABEL=(,AUL) keyword. The CCSID parameter does not apply to ISO/ANSI Version 1 or ISO/ANSI/FIPS Version 3 tapes or to tapes with labels other than AL or AUL.Using Data Sets for selecting ISO/ANSI Version 4 tapes. See the latter manual for list of supported CCSIDs.

The CCSID value of 65535 has a special meaning: it suppresses conversion.

When CCSID is not specified at the JOB, EXEC, or DD levels, data passed to BSAM and QSAM is converted to 7-bit ASCII when writing to ISO/ANSI Version 4 tapes. This may result in data loss on conversion. On READ operations the CCSID (if recorded) on the tape header label is used for conversion.

The CCSID is recorded in the tape header label if conversion is not defaulted.

1.Syntax

CCSID= nnnnn

2.Subparameter Definition

nnnnn
The CCSID as a decimal number from 1 through 65535.

3.Default
367.

4.Relationship to Other Parameters
Do not code the following parameters with the CCSID parameter:

* DDNAME QNAME
BURST DYNAM SYSOUT
CHARS FCB TERM
COPIES FLASH UCS
DATA MODIFY

5.Examples of the CCSID Parameter

Example

In this example, the data on the new ISO/ANSI tape is converted from EBCDIC to 7-bit ASCII because CCSID was not specified at the JOB, EXEC, or DD levels. If the data passed to the access methods contain graphic or special characters there could be data loss on conversion to 7-bit ASCII. This is the default operation for ISO/ANSI/FIPS Version 3 and ISO/ANSI Version 4 tapes.

Example

In this example the data on the ISO/ANSI tape is converted from 7-bit ASCII (default) to EBCDIC. This is the default operation for ISO/ANSI/FIPS Version 3 and ISO/ANSI Version 4 tapes.

Example

In this example the data written to the ISO/ANSI Version 4 tape is not converted (CCSID=65535).

Example

In this example the user did not want any conversion (CCSID=65535) on data read by the access methods.

Example

In this example the user wants conversion from a CCSID of 37 (CECP: USA, Canada, Netherlands, Portugal, Brazil, Australia, New Zealand) to 437 (Base PC-data) for data written using BSAM or QSAM for ISO/ANSI Version 4 tape. The CCSID of 437 is recorded on the tape header label.

Example

In this example the user wants data conversion from a CCSID of 437 to a CCSID of 37 for data read by the access method. Note that the CCSID does not have to be specified if it is recorded in the label.

Example

In this example the ISO/ANSI labeled tape had a recorded CCSID of 437 and a CCSID was not specified on the DD statement. Data read from this tape by the access method is converted from a CCSID of 437 to a CCSID of 37.

Example

This example illustrates overriding the CCSID specified on the JOB statement by the specification on the EXEC statement.

In this example, in step S1 the user wants conversion from a CCSID of 37 to 437 for data written using BSAM or QSAM for the ISO/ANSI Version 4 tape.

In step S2 the JOB level CCSID of 37 is overridden by the EXEC level CCSID of 65535. Since a CCSID of 65535 prevents conversion, the data written to tape is not converted. A CCSID of 65535 is recorded in the tape header label because no CCSID was specified on the DD statement.

CHARS parameter

Parameter Type

Keyword, optional

Purpose

Use the CHARS parameter to specify the name of one or more coded fonts for printing this sysout data set on an AFP printer.

Note: CHARS applies only for an output data set that is either printed on an AFP printer or processed by Infoprint Server.

1.Syntax

  • You can omit the parentheses if you code only one font-name or only DUMP.
  • Null positions in the CHARS parameter are invalid. For example, you cannot code CHARS=(,font-name) or CHARS=(font-name,,font-name).

2.Subparameter Definition

font-name
Names a coded font or character-arrangement table. Each font-name is 1 through 4 alphanumeric or national ($, #, @) characters. Code from one to four names.

DUMP
Requests a high-density dump of 204-character print lines from a 3800. If more than one font-name is coded, DUMP must be first.

Note: Use DUMP on a SYSABEND or SYSUDUMP DD statement.

3.Defaults
If you do not code the DD CHARS parameter, JES uses the following, in order:

  1. The CHARS parameter on an OUTPUT JCL statement, if referenced by the DD statement.
  2. The DD UCS parameter value, if coded.
  3. The UCS parameter on an OUTPUT JCL statement, if referenced.
  4. If no character-arrangement table is specified on the DD or OUTPUT JCL statements, JES uses an installation default specified at initialization.

4.Overrides
A CHARS parameters on a sysout DD statement overrides the OUTPUT JCL CHARS parameter. For a data set scheduled to the Print Services Facility (PSF), 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.

5.Relationship to Other Parameters
Do not code the following parameters with the CHARS parameter.

* DISP PROTECT AMP DSID QNAME DATA DYNAM VOLUME DDNAME LABEL

6.Relationship to Other Control Statements
CHARS can also be coded on the following:

  • The OUTPUT JCL statement.
  • The JES3 //*FORMAT PR statement.
  • The JES2 /*OUTPUT statement.

7.Requesting a High-Density Dump
You can request a high-density dump on the 3800 through two parameters on the DD statement for the dump data set or on an OUTPUT JCL statement referenced by the dump DD statement:

  • FCB=STD3. This parameter produces dump output at 8 lines per inch.
  • CHARS=DUMP. This parameter produces 204-character print lines.

You can code one or both of these parameters. You can place both on the same statement or one on each statement.

Examples of the CHARS Parameter

Example

//DD1 DD SYSOUT=A,CHARS=(GT10,GB12)

In this example, the CHARS parameter specifies two fonts to be used when printing the data set: GT10 and GB12.

Example

//SYSABEND DD UNIT=3800,CHARS=DUMP,FCB=STD3

The CHARS parameter on this SYSABEND DD statement specifies a high-density dump with 204 characters per line. The FCB parameter requests the dump output at 8 lines per inch.

Note: This example pertains only to 3800 printers.

CHKPT parameter

Parameter Type

Keyword, optional

Purpose

Use the CHKPT parameter to request that a checkpoint be written when each end-of-volume is reached on the multivolume data set defined by this DD statement. Checkpoints are written for all volumes except the last. Checkpoints can be requested for input or output data sets.

Note: CHKPT is supported only for multivolume QSAM or BSAM data sets. CHKPT is ignored for single-volume QSAM or BSAM data sets or for ISAM, BDAM, BPAM, or VSAM data sets. CHKPT is not supported for partitioned data sets extended (PDSEs).

1.Syntax

CHKPT=EOV

2.Subparameter Definition

EOV
Requests a checkpoint at each end-of-volume.

3.Overrides

  • The RD parameter values of NC and RNC on the JOB or EXEC statements override the CHKPT parameter.
  • The CHKPT parameter overrides cataloged procedure values or START command values for checkpoints at end-of-volume.

4.Relationship to Other Parameters
Do not code the following parameters with the CHKPT parameter.

* DYNAM DATA QNAME DDNAME SYSOUT

5.Relationship to the SYSCKEOV DD Statement
If you specify CHKPT, you must also provide a SYSCKEOV DD statement in the job or step.

6.Checkpointing Concatenated Data Sets
For concatenated BSAM or QSAM data sets, CHKPT must be coded on each DD statement in the concatenation, if checkpointing is desired for each data set in the concatenation.

7.Examples of the CHKPT Parameter

Example

In this example, the DD statement defines data set INDS, a multivolume QSAM or BSAM data set for which a checkpoint is to be written twice: once when end-of-volume is reached on TAPE01 and once when end-of-volume is reached on TAPE02

Example

In this example, OUTDS is a multivolume data set that is being created. The data set requires eight volumes. Seven checkpoints will be written: when the end-of-volume is reached on volumes one through seven.

CNTL parameter

Parameter Type

Keyword, optional

Purpose

Use the CNTL parameter to reference a CNTL statement that appears earlier in the job. The reference causes the subsystem to execute the program control statements within the referenced CNTL/ENDCNTL group.

The system searches for an earlier CNTL statement with a label that matches the label in the CNTL parameter. If the system finds no match, the system issues an error message.

1.Syntax

2.Subparameter Definition

*.label
Identifies an earlier CNTL statement, named label. The system searches for the CNTL statement first earlier in this step, then before the first EXEC statement of the job.

*.stepname.label
Identifies an earlier CNTL statement, named label, that appears in an earlier step, stepname, in the same job.

*.stepname.procstepname.label
Identifies a CNTL statement, named label, in a cataloged or in-stream procedure. Stepname is the name of the job step that calls the procedure; procstepname is the name of the procedure step that contains the CNTL statement named label.

3.Examples of the CNTL Parameter

Example

//MONDAY DD CNTL=*.WKLYPGM

In this example, the DD statement requests that the system use the program control statements following the CNTL statement named WKLYPGM and located earlier in this step or preceding the first step.

Example

//TUESDAY DD CNTL=*.SECOND.BLOCKS

In this example, the DD statement requests that the system use the program control statements following the CNTL statement named BLOCKS and located in a preceding step named SECOND.

Example

//WEDNES DD CNTL=*.THIRD.PROCTWO.CANETTI

In this example, the DD statement requests that the system use the program control statements following the CNTL statement named CANETTI and located in the procedure step PROCTWO of the procedure called in the preceding job step THIRD.

COPIES parameter

Parameter Type

Keyword, optional

Purpose

Use the COPIES parameter to specify how many copies of this sysout data set are to be printed. The printed output is in page sequence for each copy.

For printing on an AFP printer, this parameter can instead specify how many copies of each page are to be printed before the next page is printed.

Note: For more information about the subparameters supported for AFP printers.

1.Syntax

COPIES= {nnn } {(nnn,(group-value[,group-value]...))} {(,(group-value[,group-value]...)) }
  • You can omit the parentheses if you code only COPIES=nnn.
  • The following are not valid:
  • – A null group-value, for example, COPIES=(5,(,)) or COPIES=(5,)
    – A zero group-value, for example, COPIES=(5,(1,0,4))
    – A null within a list of group-values, for example, COPIES=(5,(1,,4))

2.Subparameter Definition

nnn
A number (from 1 through 255 in a JES2 system, from 1 through 254 in a JES3 system) that specifies how many copies of the data set are to be printed.

For a data set printed on an AFP printer, JES ignores nnn if any group-values are specified.

group-value
Specifies how many copies of each page are to be printed before the next page is printed. Each group-value is a number from 1 through 255 in a JES2 system and from 1 through 254 in a JES3 system. You can code a maximum of eight group-values. Their sum must not exceed 255 or 254. The total copies of each page equals the sum of the group-values.

3.Defaults
On any of the following statements, if you do not code a COPIES parameter, code it incorrectly, or code COPIES=0, the system uses the DD COPIES parameter default of 1.

DD statement
OUTPUT JCL statement
For JES2, the /*OUTPUT statement

4.Overrides
A COPIES parameter on a sysout DD statement overrides an OUTPUT JCL COPIES parameter.

If this DD statement references an OUTPUT JCL statement and that OUTPUT JCL statement contains a FORMDEF parameter, which specifies a library member, the COPYGROUP parameter on a FORMDEF statement in that member overrides any group-value subparameters on the OUTPUT JCL COPIES parameter or the sysout DD COPIES parameter.

5.Relationship to Other Parameters
Do not code the following parameters with the COPIES parameter.

* DDNAME LABEL AMP DISP QNAME DATA DYNAM VOLUME

Relationship to FLASH Parameter

If this DD statement or a referenced OUTPUT JCL statement also contains a FLASH parameter, JES prints with the forms overlay the number of copies specified in one of the following:

  • COPIES=nnn, if the FLASH count is larger than nnn. For example, if COPIES=10 and FLASH=(LTHD,12) JES prints 10 copies, all with the forms overlay.
  • The sum of the group-values specified in the COPIES parameter, if the FLASH count is larger than the sum. For example, if COPIES=(,(2,3,4)) and FLASH=(LTHD,12) JES prints nine copies in groups, all with the forms overlay.
  • The count subparameter in the FLASH parameter, if the FLASH count is smaller than nnn or the sum from the COPIES parameter. For example, if COPIES=10 and FLASH=(LTHD,7) JES prints seven copies with the forms overlay and three copies without.

Restriction When Coding UNIT Parameter

The COPIES parameter is normally coded with the SYSOUT parameter. If, however, both COPIES and UNIT appear on a DD statement, JES handles the COPIES parameter as follows:

  • nnn defaults to 1.
  • Only the first group-value is used, if group-values are specified and printing is on a 3800.

6.Relationship to Other Control Statements
The number of copies can also be specified on the COPIES parameter of the following:

  • The OUTPUT JCL statement.
  • The JES2 /*OUTPUT statement.
  • The JES3 //*FORMAT PR statement.
  • The JES3 //*FORMAT PU statement.

For JES2, if you request copies of the entire job on the JES2 /*JOBPARM COPIES parameter and also copies of the data set on the DD COPIES or OUTPUT JCL COPIES parameter, and if this is a sysout data set, JES2 prints the number of copies equal to the product of the two requests.

Using OUTPUT JCL COPIES by Nullifying DD Copies
If both a DD statement and a referenced OUTPUT JCL statement contain COPIES parameters, the DD COPIES parameter normally overrides the OUTPUT JCL COPIES parameter. For example, four copies are printed of sysout data set DDA:

//OTA OUTPUT COPIES=3 //DDA DD SYSOUT=A,OUTPUT=*.OTA,COPIES=4

However, if the DD COPIES is a null parameter, the OUTPUT JCL COPIES parameter is used. For example, three copies are printed of sysout data set DDB:

//OTB OUTPUT COPIES=3 //DDB DD SYSOUT=A,OUTPUT=*.OTB,COPIES=

The following example shows a null COPIES parameter on an in-stream DD statement that overrides a procedure DD statement. The null COPIES parameter on DD statement PS.DDA nullifies the COPIES parameter on the procedure DD statement DDA, thereby allowing the COPIES parameter on OUTPUT JCL statement OT to be used. The system prints three copies of the DDA sysout data set.

Note: If a null COPIES parameter appears on a DD statement that either does not reference an OUTPUT JCL statement or references an OUTPUT JCL statement that does not contain a COPIES parameter, the system uses a default of 1.

7.Examples of the COPIES Parameter

Example

//RECORD1 DD SYSOUT=A,COPIES=32

This example requests 32 copies of the data set defined by DD statement RECORD1 when printing on an impact printer or an AFP printer.

Example

//RECORD2 DD SYSOUT=A,COPIES=(0,(1,2))

In this example, when printing on an AFP printer, three copies of the data set are printed in two groups. The first group contains one copy of each page. The second group contains two copies of each page.When printing on an impact printer, one copy (the default for nnn) is printed.

Example

//RECORD3 DD SYSOUT=A,COPIES=(8,(1,3,2))

In this example, when printing on an AFP printer, six copies of the data set are printed in three groups. The first group contains one copy of each page, the second group contains three copies of each page, and the last group contains two copies of each page. When the output device is not an AFP printer, the system prints eight collated copies.

Example

//RECORD4 DD UNIT=AFP1,COPIES=(1,(2,3))

Because the UNIT parameter is coded and the device is an AFP printer, the system prints only the first group-value: two copies of each page.


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

IBM-JCL Topics