EXTENT

Syntax:

      *----------------------------------------------------------------
      *    EXTENT OPERANDS
      *    // EXTENT [logical-unit],
     *       [volser],
      *      [type],
      *       [seq-number],
      *       [relative-track | block ],
      *       [number of tracks | blocks ],
      *       [split-cylinder-track]
      *----------------------------------------------------------------

Where:

logical-unit
Logical unit (SYSxxx) of the volume for which this extent is effective. Parsed but not processed*.
volser
Logical unit (SYSxxx) of the volume for which this extent is effective. Parsed but not processed*.
type
Single character that indicates the type of extent. Parsed but not processed*.
relative-track or block
Number of the track where the extent is to begin. Parsed but not processed*.
number of tracks or blocks
Number of tracks to be allocated to the file. Parsed but not processed*.
split-cylinder-track
Upper track number for split cylinder in SAM files. Parsed but not processed*.
Note: The command and operand combinations listed in these topics are supported unless indicated as "parsed but not processed". Where indicated, this means:
  • Parsed but not processed - indicates that the command and the operand are not supported, however, Enterprise Developer parses it and, if it fails validation, a JCL error is generated.
  • Parsed but not processed* - indicates that a number of the operands for JCL and POWER commands (for example, any tape or volume-specific operands) do not apply in the Enterprise Developer environment. See General Differences.