ACCODE parameter - IBM-JCL

Parameter Type

Keyword, optional

Purpose

Use the ACCODE parameter to specify or change an accessibility code for an ISO/ANSI/FIPS Version 3 or ISO/ANSI Version 4 tape output data set. An installation-written file-access exit routine verifies the code after the code is written to tape. If the code is authorized, the job step’s program can use the data set; if not, the system issues messages and may abnormally terminate the job step.

A data set protected by an accessibility code should reside only on a volume protected by RACF or a volume accessibility code. The volume should not contain any unprotected data sets.

Note: ACCODE is supported only for ISO/ANSI/FIPS Version 3 and ISO/ANSI Version 4 tape data sets. ACCODE is ignored for all label types except AL and AUL label tapes.

1.Syntax

ACCODE=access-code

2.Subparameter Definition

access-code
Specifies an accessibility code. The access code is 1 through 8 characters. In ISO/ANSI/FIPS Version 3 the first character must be an upper case letter from A through Z. In ISO/ANSI Version 4 the first character must be an upper case letter from A to Z, number from 0 to 9, or one of the special characters ! * ² % ’( ) + , - . / : ; < = > ? and _ .

Enclose the ACCODE in apostrophes if you specify special characters. For example, ACCODE=’AB/CD’. Specify two apostrophes if you include an apostrophe as a special character. For example, to specify DAY’SEND, use ACCODE=’DAY’’SEND’.

Note: ISO/ANSI/FIPS Version 3 and ISO/ANSI Version 4 use only the first character as the accessibility code; the installation can use the other seven characters. If the first character is other than those allowed, the installation does not give control to the file-access exit routine.

3.Defaults
If you do not specify an accessibility code on a DD statement that defines an ISO/ANSI/FIPS Version 3 or ISO/ANSI Version 4 tape data set, the system writes an ASCII blank character (X'20') in the tape label. A blank authorizes unlimited access to the tape’s data sets unless access is limited by RACF data set protection. If the installation does not supply a file-access exit routine, the system prevents access to any ISO/ANSI/FIPS Version 3 or ISO/ANSI Version 4 tape volume.

4.Overrides
If PASSWORD or NOPWREAD is coded on the DD statement LABEL parameter, password access overrides the ACCODE parameter.

5.Example of the ACCODE Parameter

In this example, the DD statement ACCODE parameter specifies an accessibility code of Z for tape volume T49850. The volume has ISO/ANSI/FIPS Version 3 or ISO/ANSI Version 4 labels. The data set TAPEDS is first on the tape.

AMP Parameter

Parameter Type

Keyword, optional

Purpose
Use the AMP parameter to complete information in an access method control block (ACB) for a VSAM data set. The ACB is a control block for entry-sequenced, key-sequenced, and relative record data sets.

AMP is supported only for VSAM data sets.

Note: With SMS, you can create new VSAM data sets with JCL DD statements.

1.Syntax

The subparameters are:

Parentheses: Parentheses are required only when you are continuing the statement.

Multiple Subparameters:When a parameter contains more than one sub parameter, separate the sub parameters by commas and enclose the subparameter list in apostrophes inside the parentheses. For example, AMP=('AMORG,STRNO=4').

Null Positional Subparameters: Null positions in the AMP parameter are invalid. Special Characters: When a parameter contains only one subparameter and that subparameter contains special characters, enclose the subparameter in apostrophes inside the parentheses. For example, AMP=('STRNO=4').

Note: Do not enclose a subparameter in a subparameter list in apostrophes.

If you code a symbolic parameter on the AMP parameter, you can code the symbolic parameter in apostrophes.

Continuation onto Another Statement: Enclose the subparameter list in only one set of parentheses. Enclose all the subparameters on each statement in apostrophes. End each statement with a comma after a complete subparameter.For example:

2.Subparameter Definition

AMORG
Indicates that the DD statement describes a VSAM data set. Code AMORG when data set access is through an ISAM interface program and the DD statement contains VOLUME and UNIT parameters.

It is unnecessary to code AMP=AMORG for a data set that is SMS-managed. An SMS data set is cataloged at allocation; all information pertaining to the data set creation (such as RECORG) must be fully defined at allocation to ensure the success of the job.

BUFND=number
Specifies the number of I/O buffers that VSAM is to use for data records. The minimum is 1 plus the STRNO subparameter number. This value overrides the BUFND value specified in the ACB or GENCB macro, or provides a value if one is not specified. If you omit STRNO, BUFND must be at least 2. If you omit BUFND from AMP and from the ACB macro instruction, the system uses the STRNO number plus 1.

BUFNI=number
Specifies the number of I/O buffers that VSAM is to use for index records. This value overrides the BUFNI value specified in the ACB or GENCB macro, or provides a value if one is not specified. If you omit BUFNI from AMP and from the ACB macro instruction, VSAM uses as many index buffers as the STRNO subparameter number; if you omit both BUFNI and STRNO, VSAM uses 1 index buffer.

If data access is through the ISAM interface program, specify for the BUFNI number 1 more than the STRNO number, or specify 2 if you omit STRNO, to simulate having the highest level of an ISAM index resident. Specify a BUFNI number 2 or more greater than the STRNO number to simulate having intermediate levels of the index resident.

BUFSP=number
Specifies the maximum number of bytes for the data and index buffers in the user area. This value verrides the BUFSP value specified in the ACB or GENCB macro, or provides a value if one is not specified. If BUFSP specifies fewer bytes than the BUFFERSPACE parameter of the access method services DEFINE command, the BUFFERSPACE number overrides the BUFSP number.

CROPS=NCK
CROPS=NRC
CROPS=NRE
CROPS=RCK

Requests a checkpoint/restart option.

NCK
Requests no data set post-checkpoint modification tests.

NRC
Requests neither a data-erase test nor data set post-checkpoint modification tests.

NRE
Requests no data-erase test.

RCK
Requests a data-erase test and data set post-checkpoint modification tests. If the CROPS subparameter is omitted, RCK is the default.

If you request an inappropriate option, such as the data-erase test for an input data set, the system ignores the option.

FRLOG=NONE
FRLOG=REDO

Specifies if VSAM batch logging will be performed for your VSAM data set.

NONE
Disables the VSAM batch logging function for your VSAM data set. Changes made by applications will not be written to the MVS log stream indicated on the LOGSTREAMID parameter.

REDO
Enables the VSAM batch logging function for you VSAM data set. Changes made by applications will be written to the MVS log stream indicated on the LOGSTREAMID parameter.

Notes:

  1. If FRLOG=REDO is specified, the LOGSTREAMID parameter must be specified for the VSAM data set(s). If LOGSTREAMID is not specified, IEC161I is issued.
  2. There is no default JCL value for FRLOG. If FRLOG is omitted, the catalog value will be used.

OPTCD=I
OPTCD=L
OPTCD=IL

Indicates how the ISAM interface program is to process records that the step’s processing program flags for deletion.

I Requests, when the data control block (DCB) contains OPTCD=L, that the ISAM interface program is not to write into the data set records marked for deletion by the processing program. If AMP=('OPTCD=I') is specified without OPTCD=L in the DCB, the system ignores deletion flags on records.

L Requests that the ISAM interface program is to keep in the data set records marked for deletion by the processing program. If records marked for deletion are to be kept but OPTCD=L is not in the DCB, AMP=('OPTCD=L') is required.

Note: This parameter has the same meaning and restrictions for the ISAM interface as it has for ISAM. While it was not required in the ISAM job control language, you should code it in the AMP parameter.

IL Requests that the ISAM interface program is not to write into the data set records marked for deletion by the processing program. If the processing program had read the record for update, the ISAM interface program deletes the record from the data set.

AMP=('OPTCD=IL') has the same effect as AMP=('OPTCD=I') coded with OPTCD=L in the DCB.

RECFM=F
RECFM=FB
RECFM=V
RECFM=VB

Identifies the ISAM record format used by the processing program. You must code this RECFM subparameter when the record format is not specified in the DCB.

Note: This parameter has the same meaning and restrictions for the ISAM interface as it has for ISAM. While it was not required in the ISAM job control language, you should code it in the AMP parameter.

All VSAM requests are for unblocked records. If the processing program requests blocked records, the ISAM interface program sets the overflow-record indicator for each record to indicate that each is being passed to the program unblocked.

F Indicates fixed-length records.
FB Indicates blocked fixed-length records.
V Indicates variable-length records. If no RECFM is specified in the AMP parameter or in the DCB, V is the default.
VB Indicates blocked variable-length records.

STRNO=number
Indicates the number of request parameter lists the processing program uses concurrently. The number must at least equal the number of BISAM and QISAM requests that the program can issue concurrently. If the program creates subtasks, add together the number of requests for each subtask plus 1 for each subtask that sequentially processes the data set. This value overrides the STRNO value specified in the ACB or GENCB macro, or provides a value if one is not specified

SYNAD=module
Names a SYNAD exit routine. The ISAM interface program is to load and exit to this routine if a physical or logical error occurs when the processing program is gaining access to the data set.

The SYNAD parameter overrides a SYNAD exit routine specified in the EXLST or GENCB macro instruction that generates the exit list. The address of the intended exit list is specified in the access method control block that links this DD statement to the processing program. If no SYNAD exit is specified, the system ignores the AMP SYNAD parameter.

TRACE=(subparameter[,subparameter]...)
Indicates that the generalized trace facility (GTF) executes with your job to gather information about the opening, closing, and end-of-volume processing for the data set defined on this DD statement. You can use the interactive problem control system to print the trace output.

The TRACE subparameters are: HOOK, ECODE, KEY, PARM1, and PARM2. which you use to obtain diagnostic information during VSAM processing.

ACCBIAS=USER
ACCBIAS=SYSTEM
ACCBIAS=DO
ACCBIAS=DW
ACCBIAS=SO
ACCBIAS=SW

Specify one of these six values to override record access bias in the data class in order to use System-Managed Buffering (SMB) without changing the data class. See OFSMS/MVS Using Data Sets for details on System-Managed Buffering.

USER
Obtain buffers the same way the system would without SMB. This is the default if you code no specification for the ACCBIAS subparameter.

SYSTEM
Force SMB and let the system determine the buffering technique based on the ACB MACRF and storage class specification.

Note: USER and SYSTEM are the only values you may use to specify record access bias in the data class.

DO
SMB with direct optimization.

DW
SMB weighted for direct processing. This option provides the capability to use hiperspace.

SO
SMB with sequential optimization.

SW
SMB weighted for sequential processing.

SMBDFR=Y or SMBDFR=N
With direct optimization, use this subparameter to instruct VSAM whether to defer writing of changed buffers to the medium until either the data set is closed or the buffers are required for some other request. See OFSMS/MVS Using Data Sets for further details on using SMBDFR.

SMBHWT=nn
Specify a requirement for hiperspace where nn is an integer from 0 to 99. Use this parameter with direct optimization. The default value is 0, which means that the system does not obtain any hiperspace.

SMBVSP=nnK or SMBVSP=nnM
Specify the amount of virtual buffer space to acquire for direct optimized processing when opening the data set, where nn is 1 to 2048000 kilobytes or 1 to 2048 megabytes.

RMODE31=ALL
RMODE31=BUFF
RMODE31=CB
RMODE31=NONE

Designate the residency for buffers and control blocks. This subparameter allows you to specify whether or not to allocate the buffers and control blocks in 31-bit addressable storage. You can use this field independently of SMB. With SMB the default location is in 31-bit addressable storage (²above the 16-megabyte line²). Without SMB, the default is in 24-bit addressable storage (²below the line²).

The values you may specify for RMODE31 are:
ALL —Control blocks and buffers above the line.
BUFF —Buffers (only) above the line.
CB —Control blocks (only) above the line.
NONE —Control blocks and buffers below the line.

When you do not specify ACCBIAS, or when you specify ACCBIAS=USER, if you specify nothing for RMODE31 in either the JCL or the ACB, the system obtains the buffers and control blocks in virtual storage with a 24-bit address.

When ACCBIAS=SYSTEM, if you specify nothing for RMODE31 in either the JCL or the ACB, the system obtains the buffers in storage with an address greater than 16 million bytes.

When you specify CB or NONE for RMODE31, the system obtains the buffers in 24-bit addressable storage.

When you specify BUFF or NONE for RMODE31, the system obtains the control blocks in 24-bit addressable storage.

If your program runs in 24-bit mode and you use locate mode processing for the VSAM data set, you must obtain the buffers in 24-bit addressable storage.

Note: If your program runs with local or global shared resources (LSR/GSR) and uses journaling (JRNAD) or user processing (UPAD) exit routines, the exits must run in 31-bit mode if you obtained the control blocks above the line.

This capability to allocate above the line is necessary when either or both of the following conditions exists:

  • The number of data sets open to a job is quite large.
  • The number of buffers is such as to cause a storage shortage if kept in 24-bit addressable storage.

You may specify RMODE31 only with the JCL DD AMP parameter or in the ACB. The RMODE31 subparameter of AMP overrides any RMODE31 values specified in the ACB. The RMODE31 subparameter is available for all data set types.

3.Relationship to Other Parameters
Do not code the following parameters with the AMP parameter.

Invalid ddnames
The following ddnames are invalid for VSAM data sets:

Invalid DSNAMEs
When you code the AMP parameter, the DSNAME must not contain parentheses, a minus (hyphen), or a plus (+) sign. The forms of DSNAME valid for ISAM, partitioned access method (PAM), and generation data groups (GDG) are invalid with VSAM data sets.

4.Buffer Requirements
For a key-sequenced data set, the total minimum buffer requirement is three: two data buffers and one index buffer. For an entry-sequenced data set, two data buffers are required.

If the number of buffers specified in the BUFND and BU FNI subparameters causes the virtual storage requirements to exceed the BUFSP space, the number of buffers is reduced to fit in the BUFSP space. If BUFSP specifies more space than required by BUFND and BUFNI, the number of buffers is increased to fill the BUFSP space.

5.Examples of the AMP Parameter
Example

In this example, the DD statement defines the size of the user area for data and index buffers, specifies the number of data and index buffers, specifies the number of requests that require concurrent data set positioning, and specifies an error exit routine named ERROR.

Example

In this example, the DD statement defines the values for BUFSP, BUFNI, STRNO, and SYNAD, as in the previous example. It also specifies that a data set post-checkpoint modification test is not to be performed when restarting at a checkpoint and that GTF is to provide a trace of specified data areas.

AVGREC Parameter

Parameter Type

Keyword, optional — use this parameter only with SMS

Purpose
Use the AVGREC parameter when you define a new data set to specify that:

  • The units of allocation requested for storage space are records.
  • The primary and secondary space quantity specified on the SPACE parameter represents units, thousands, or millions of records.

When you use AVGREC with the SPACE parameter, the first subparameter (reclgth) on the SPACE parameter must specify the average record length of the records.

Code the AVGREC parameter when you want to (1) specify records as the units of allocation or (2) override the space allocation defined in the data class for the data set.

If SMS is not installed or is not active, the system checks the syntax and then otherwise ignores the AVGREC parameter.

1.Syntax

AVGREC= {U} {K} {M}

2.Subparameter Definition
U Specifies a record request and that the primary and secondary space quantity specified on the SPACE parameter represents the number of records in units (multiplier of 1).

K Specifies a record request and that the primary and secondary space quantity specified on the SPACE parameter represents the number of records in thousands (multiplier of 1024).

M Specifies a record request and that the primary and secondary space quantity specified on the SPACE parameter represents the number of records in millions (multiplier of 1048576).

3.Overrides
AVGREC overrides the space allocation defined in the DATACLAS parameter for the data set.

4.Relationship to Other Parameters
Do not code AVGREC with the TRK, CYL, or ABSTR subparameters of the SPACE parameter.Do not code the following DD parameters with the AVGREC parameter.

5.Examples of the AVGREC Parameter
Example

In the example, the space allocation defined in the DCLAS03 data class is overridden by the SPACE and AVGREC parameters, which indicate an average record length of 128 bytes, a primary quantity of 5K (5,120) records, and a secondary quantity of 2K (2,048) records.

Example

In the example, the space allocation defined in the DCLAS03A data class is overridden by the AVGREC parameter, which indicates that the primary and secondary quantity represents thousands of records.


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

IBM-JCL Topics