z/OS TSO/E Command Reference
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


ATTRIB command operands

z/OS TSO/E Command Reference
SA32-0975-00

attr_list_name
specifies the name for the attribute list. You can specify this name later as an operand of the ALLOCATE command. The name must consist of 1 to 8 alphanumeric and the special characters #, $, or @, or both must begin with an alphabetic or special character, and must be different from all other attribute list names and ddnames that exist during your terminal session.
BLKSIZE(blocksize)
specifies the block size for the data sets. The block size must be a decimal number and must not exceed 32760 bytes.
The block size you specify must be consistent with the requirements of the RECFM operand. If you specify:
  • RECFM(F), then the block size must be equal to or greater than the logical record length.
  • RECFM(F B), then the block size must be an integral multiple of the logical record length.
  • RECFM(V), then the block size must be equal to or greater than the largest block in the data set. For unblocked variable-length records, the size of the largest block must allow space for the four-byte block descriptor word in addition to the largest logical record length. The logical record length must allow space for a four-byte record descriptor word.
  • RECFM(V B), then the block size must be equal to or greater than the largest block in the data set. For block variable-length records, the size of the largest block must allow space for the four-byte block descriptor word in addition to the sum of the logical record lengths that will go into the block. Each logical record length must allow space for a four-byte record descriptor word. Because the number of logical records can vary, you must estimate the optimum block size and the average number of records for each block based on your knowledge of the application that requires the I/O.
  • RECFM(U), then the block size can be any value up to what is supported by the device or 32760, whichever is smaller. If allocated to a TSO/E terminal and BLKSIZE(80) is coded, then one character (the last byte) is reserved for an attribute character.
BUFL(buffer_length)
specifies the length, in bytes, of each buffer in the buffer pool. Specify a decimal number for buffer_length. The number must not exceed 32760.

If you omit this operand and the system acquires buffers automatically, the BLKSIZE and KEYLEN operands are used to supply the information needed to establish buffer length.

BUFNO(number_of_buffers)
specifies the number of buffers to be assigned for data control blocks. Specify a decimal number for number_of_buffers. The number must not exceed 255. You might be limited to a smaller number of buffers depending on the limit established at your installation. The following table shows the condition that requires you to include this operand.

When you use one of the following methods of obtaining the buffer pool, then:

LRECL(logical_record_length)
specifies the length, in bytes, of the largest logical record in the data set. You must specify this operand for data sets that consist of either fixed-length or variable-length records.

If the data set contains undefined-length records, omit this operand.

The logical record length must be consistent with the requirements of the RECFM operand and must not exceed the block size (BLKSIZE operand), except for variable-length-spanned records. If you specify:
  • RECFM(V) or RECFM(V B), then the logical record length is the sum of the length of the actual data fields plus four bytes for a record descriptor word.
  • RECFM(F) or RECFM(F B), then the logical record length is the length of the actual data fields.
  • RECFM(U), then you should omit the LRECL operand.

LRECL(NNNNNK) allows users of ISO/ANSI extended logical records and QSAM locate mode users to specify a K multiplier on the LRECL operand. NNNNN can be within 1-16,384. The K indicates that the value can be multiplied by 1024.

For variable-length spanned records (VS or VBS) processed by QSAM (locate mode) or BSAM, specify LRECL (X) when the logical record exceeds 32756 bytes.

NCP(number_of_channel_programs)
specifies the maximum number of READ or WRITE macro instructions allowed before a CHECK macro instruction is issued. The maximum number must not exceed 255 and must be less than 255 if the address space does not have enough virtual storage. If you want to use chained scheduling, you must specify an NCP value greater than 1. If you omit the NCP operand and the application program does not specify the MULTSDN parameter on the DCBE macro, the default value is 1. This parameter has an effect only if the program uses GSAM or BPAM and does not set its own value for NCP.
INPUT | OUTPUT
INPUT
specifies a BSAM data set opened for INOUT or a BDAM data set opened for UPDAT is to be processed for input only. This operand overrides the INOUT (BSAM) option or UPDAT (BDAM) option in the OPEN macro instruction to INPUT. This is useful if you only have READ access authority to the data set.
OUTPUT
specifies a BSAM data set opened for OUTIN or OUTINX is to be processed for output only. This operand overrides the OUTIN option in the OPEN macro instruction to OUTPUT or the OUTINX option in the OPEN macro instruction to EXTEND.
EXPDT(year_day)
specifies the data set expiration date. Specify the year and day in one of two forms:
  • yyddd, where yy is the last two-digit number for the year and ddd is the three-digit number for the day of the year. The maximum value for the year is 99 (for 1999). The minimum value for the day is 000 and the maximum value is 366.

    If you specify 99365 or 99366, the system retains your data sets permanently. Do not use those dates as an expiration date. Use them as "no scratch" dates only.

  • yyyy/ddd, where yyyy is the four-digit number for the year and ddd is the three-digit number for the day of the year. The slash is required. The maximum value for the year is 2155. The minimum value for the day is 000 and the maximum value is 366.

If you specify 1999/365 or 1999/366, the system retains your data sets permanently. Do not use those dates as an expiration date. Use them as "no scratch" dates only. If you code any of these special values after 1999, they will have the same effect.

If SMS is active, the expiration date might have been defined by the DATACLAS operand.

RETPD(number_of_days)
specifies the data set retention period in days. The value can be a five-digit decimal number with a current maximum value of 93000. If the system calculates the date as the equivalent of 1999/365 or 1999/366, the system does not use that date. Instead it uses 2000/001.
BFALN({F | D})
specifies the boundary alignment of each buffer as follows:
D
Each buffer starts on a doubleword boundary.
F
Each buffer starts on a fullword boundary that might not be a doubleword boundary.

If you do not specify this operand and it is not available from any other source, then data management routines assign a doubleword boundary.

OPTCD(A, B, C, E, F, H, J, Q, R, T, W, and Z or all)
specifies the following optional services that you want the system to perform. See the OPTCD subparameter of the DCB parameter in z/OS MVS JCL Reference.
A
specifies actual device addresses be presented in READ and WRITE macro instructions.
B
specifies the end-of-file (EOF) recognition be disregarded for tapes.
C
specifies the use of chained scheduling.
E
requests an extended search for block or available space.
F
specifies feedback from a READ or WRITE macro instruction should return the device address in the form it is presented to the control program.
H
requests the system to check for and bypass.
J
specifies the character after the carriage control character is the table reference character for that line. The table reference character tells TSO/E which character arrangement table to select when printing the line.
Q
requests the system to translate a magnetic tape from ASCII to EBCDIC or from EBCDIC to ASCII.
R
requests the use of relative block addressing.
T
requests the use of the user totaling facility.
W
requests the system to perform a validity check when data is written on a direct access device.
Z
requests the control program to shorten its normal error recovery procedure for input on magnetic tape.

You can request any or all of the services by combining the values for this operand. You may combine the characters in any sequence, being sure to separate them with blanks or commas.

EROPT({ACC | SKP | ABE})
specifies the option that you want to enter if an error occurs when a record is read or written. The options are:
ACC
to accept the block of records in which the error was found.
SKP
to skip the block of records in which the error was found.
ABE
to end the task abnormally.
BFTEK({S, E, A, R})
specifies the type of buffering that you want the system to use. The types that you can specify are:
S
Simple buffering
E
Exchange buffering
A
Automatic record area buffering
R
Record buffering
RECFM(A, B, D, F, M, S, T, U, and/or V)
specifies the format and characteristics of the records in the data set. The format and characteristics must be completely described by one source only. If they are not available from any source, the default is an undefined-length record. For a discussion of the formats and characteristics of the RECFM subparameter of the DCB parameter, see z/OS MVS JCL Reference.
Use the following values with the RECFM operand:
A
indicates the record contains ASCII printer control characters.
B
indicates the records are blocked.
D
indicates variable-length ASCII records.
F
indicates the records are of fixed-length.
M
indicates the records contain machine code control characters.
S
indicates, for fixed-length records, the records are written as standard blocks (there must be no truncated blocks or unfilled tracks except for the last block or track). For variable-length records, a record might span more than one block. Exchange buffering, BFTEK(E), must not be used.
T
indicates the records can be written onto overflow tracks, if required. Exchange buffering, BFTEK(E), or chained scheduling, OPTCD(C), cannot be used.
U
indicates the records are of undefined-length.
V
indicates the records are of variable-length.

You can specify one or more values for this operand; at least one is required. If you use more than one value, you must separate each value with a comma or a space.

With SMS, the record format for a new data set might have been defined by the DATACLAS operand.

RECFM is mutually exclusive with RECORG.

DIAGNS(TRACE)
specifies the Open/Close/EOV trace option that gives a module-by-module trace of the Open/Close/EOV work area your DCB.
LIMCT(search_number)
specifies the number of blocks or tracks to be searched for a block or available space. The number must not exceed 32,760.
BUFOFF({block_prefix_length | L})
specifies the buffer offset. The block prefix length must not exceed 99. L is specified if the block prefix field is four bytes long and contains the block length.
DSORG({DA, DAU, PO, POU, PS, PSU})
specifies the data set organization as follows:
DA
Direct access
DAU
Direct access unmovable
PO
Partitioned organization
POU
Partitioned organization unmovable
PS
Physical sequential
PSU
Physical sequential unmovable
DEN({0 | 1 | 2 | 3 | 4})
specifies the magnetic tape density as follows:
0
200 bpi/7 track
1
556 bpi/7 track
2
800 bpi/7 and 9 track
3
1600 bpi/9 track
4
6250 bpi/9 track (IBM® 3420 Models 4, 6, and 8, or equivalent)
TRTCH({C | E | T | ET}, {COMP | NOCOMP})
specifies the recording technique for 7 or 18 track tape as follows:
C
Data conversion with odd parity (the default) and no translation (the default).
E
Even parity with no translation (the default) and no conversion (the default).
T
Odd parity (the default) and no conversion (the default). BCD to EBCDIC translation when reading and EBCDIC to BCD translation when writing.
ET
Even parity, and no conversion (the default). BCD to EBCDIC translation when reading and EBCDIC to BCD translation when writing.
COMP | NOCOMP
specifies whether data sets are to be compressed to save space.

This operand is mutually exclusive with KEYLEN.

KEYLEN(bytes)
specifies the length, in bytes, of each of the keys used to locate blocks of records in the data set when the data set resides on a direct access device. The key length must not exceed 255 bytes. If an existing data set has standard labels, you can omit this operand and let the system retrieve the key length from the standard label. If a key length is not supplied by any source before you issue an OPEN macro instruction, a length of zero (no keys) is assumed. This operand is mutually exclusive with TRTCH.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014