A — allocate new data set

Use option A to allocate a new data set with or without the Storage Management Subsystem classes (management class, storage class, and data class). A data set that is allocated on a volume that is managed by the Storage Management Subsystem (SMS) is called a managed data set. A data set that is allocated on a volume that is not managed by the SMS is called a non-managed data set.

To use option A, you must:

Enter one of these:
- An ISPF library name in the Project, Group, and Type fields
- Another partitioned or sequential data set name in the Data Set Name field.
  See the "ISPF Libraries and Data Sets" topic of the z/OS ISPF User's Guide Vol I for information on how to enter the ISPF library name or the data set name.
If you entered an ISPF library name, the value in the Volume Serial field is ignored. However, if you entered another data set name, you can specify the volume on which to allocate the data set in the Volume Serial field. Do not enter a volume serial if you want to do one of these:
- Use the authorized default volume.
- Enter a generic unit address in the "Generic unit" field on the Allocate New Data Set panel.
Note that an SMS-eligible data set may be allocated on a volume different from any entered value.

For more information about Volume Serials, see the "ISPF Libraries and Data Sets" topic of the z/OS ISPF User's Guide Vol I.
If your ISPF libraries and data sets are password-protected, enter the password in the Data Set Password field.
For more information about Data Set Passwords, see the "ISPF Libraries and Data Sets" topic of the z/OS ISPF User's Guide Vol I.

Note: You cannot assign a password to a managed data set. Therefore, the Data Set Password field is ignored when you allocate a managed data set.
Press Enter.

The Allocate New Data Set panel is displayed. This panel enables you to specify data set allocation values. The fields displayed on this panel depend upon the value of the ALLOWED_ALLOCATION_UNITS keyword in the ISPF configuration table. When ALLOWED_ALLOCATION_UNITS is not 'A' the panel shown in Figure 1 is displayed.

Figure 1. Allocate New Data Set panel (ISRUAAP2)

  Menu  RefList  Utilities  Help
 ───────────────────────────────────────────────────────────────────────────────
                             Allocate New Data Set
                                                                    More:     +
 Data Set Name  . . . : HANKO.TEST.DATADEV

 Management class . . . PRIMARY        (Blank for default management class)
 Storage class  . . . . PRIMARY        (Blank for default storage class)
  Volume serial . . . . A$US20         (Blank for system default volume) **
 Data class . . . . . .                (Blank for default data class)
  Space units . . . . . CYLINDER       (BLKS, TRKS, CYLS, KB, MB, BYTES
                                        or RECORDS)
  Average record unit                  (M, K, or U)
  Primary quantity  . . 1              (In above units)
  Secondary quantity    20             (In above units)
  Directory blocks  . . 0              (Zero for sequential data set) *
  Record format . . . . FB    
  Record length . . . . 80     
  Block size  . . . . . 27920 
  Data set name type                   (LIBRARY, HFS, PDS, LARGE, BASIC, *
                                        EXTREQ, EXTPREF or blank)
  Data set version  . .  
  Extended Attributes                  (NO, OPT or blank)										            
  Expiration date . . .                (YY/MM/DD, YYYY/MM/DD
                                        MM.DDD, MMMM.DDD in Julian form)
 Command ===>                                                                  
  F1=Help      F2=Split     F3=Exit      F7=Backward  F8=Forward   F9=Swap
 F10=Actions  F12=Cancel

Otherwise, this panel is displayed: (Figure 2).

Figure 2. Allocate New Data Set —managed data set support panel (ISRUAASE)

  Menu  RefList  Utilities  Help
 ───────────────────────────────────────────────────────────────────────────────
                            Allocate New Data Set
                                                                   More:     +
Data Set Name  . . . : MYPROJ.DEV.SOURCE2

Management class . . . STANDARD       (Blank for default management class)
Storage class  . . . . BASE           (Blank for default storage class)
 Volume serial . . . . MVS8WF         (Blank for system default volume) **
 Device type . . . . .                (Generic unit or device address) **
Data class . . . . . .                (Blank for default data class)
 Space units . . . . . CYLINDER       (BLKS, TRKS, CYLS, KB, MB, BYTES
                                       or RECORDS)
 Average record unit                  (M, K, or U)
 Primary quantity  . . 1              (In above units)
 Secondary quantity    1              (In above units)
 Directory blocks  . . 0              (Zero for sequential data set) *
 Record format . . . . FB    
 Record length . . . . 80     
 Block size  . . . . .       
 Data set name type  . PDS            (LIBRARY, HFS, PDS, LARGE, BASIC, *
                                       EXTREQ, EXTPREF or blank)
 Data set version  . .  									   
 Extended Attributes                  (NO, OPT or blank)
 Command ===>                                                                  
 F1=Help      F2=Split     F3=Exit      F7=Backward  F8=Forward   F9=Swap
F10=Actions  F12=Cancel

When you press Enter with this panel displayed, the new data set is allocated and cataloged. Entering the END command returns you to the previous panel without allocating the data set.

An optional installation exit, the data set allocation exit, can control all data set creation, deletion, allocation, and deactivation done directly by ISPF. This does not include allocations done by ISPF, the TSO ALLOCATE command, or other TSO commands. See z/OS ISPF Planning and Customizing for more information about the data set allocation exit.

Your installation must use DFSMSdfp to define the values that you enter in the "Management class", "Storage class", and "Data class" fields. If you have no specific requirements, you can leave these fields blank. However, be aware that your installation may provide default management, storage, and data classes. These defaults would take effect if you leave any of the class fields blank and may even override any classes that you specify.

Management class: Used to obtain data management-related information (migration, backup, and retention criteria, such as expiration date) for the data set allocation.
If you have no specific management class requirements, you can leave this field blank. However, be aware that your installation may provide a default management class. This default may even override any management class that you specify.
Storage class: Used to obtain the storage-related information (volume serial) for the data set allocation. Any volume serial that you enter in the " Volume serial" field is ignored unless the storage class that you use includes the Guaranteed Space=Yes attribute (useful if you are allocating multivolume data sets).
Data class: Used to obtain the data-related information (space units, primary quantity, secondary quantity, directory block, record format, record length, and data set name type) for the allocation of the data set.

Default values are provided for the fields in Figure 1, except for expiration date, based on which of these occurred most recently:

What you last entered on this panel
The last display data set information request (options 3.1, 3.2, or 3.4).

You can type over the displayed defaults if you want to change them. Here is a list of the fields on this panel and their definitions:

Volume serial

This field is one that you probably will not need to use very often. It is not required and is usually ignored by the Storage Management Subsystem. Do not enter a volume serial if you want to do one of these:

Use the authorized default volume.
Enter a generic unit address in the Generic unit field.
Use the volume specified by the storage class you are using.

When a storage class is used, your installation and the SMS assume joint responsibility for determining the volume on which the data set is allocated. The SMS enables the installation to select the volumes that are eligible to contain the data set. It then chooses one of those volumes and allocates the data set. The SMS's volume choice is based on:

storage requirements
The amount of space a volume has available.

Note: ISPF does not support allocation of tape data sets.

Generic unit

The generic unit address for the direct access volume that is to contain the data set, such as 3380 or 3390. This field overrides the Volume Serial field on the Data Set Utility panel. Therefore, you should leave this field blank if you want to do one of these:

Use the authorized default volume
Enter a volume serial in the Volume serial field.

Note:

Leave both the Volume serial and Generic unit fields blank to allow ISPF to select an eligible volume. Eligibility is determined by the unit information in your user entry in the TSO User Attribute Data Set (UADS) or the TSO segment of RACF®.
At some installations, you are limited to eligible volumes even when an explicit volume serial is specified. At other installations you can specify any mounted volume. This is an installation option.
To allocate a data set to a 3850 virtual volume, you must also have MOUNT authority, gained by using the TSO ACCOUNT command or by using the RACF PERMIT command for the TSO AUTH general resource class.
If you are allocating an SMS data set, you can enter either an installation defined group name or a generic device type in the Generic unit field, but not a specific device number.

Space units

Any of these:

Track: Shows that the amounts entered in the primary and secondary quantity fields are expressed in tracks.
Cylinder: Shows that the amounts entered in the primary and secondary quantity fields are expressed in cylinders.
Block: Shows that the amounts entered in the primary and secondary quantity fields are expressed in blocks.
Megabyte: Shows that the amounts entered in the primary and secondary quantity fields are expressed in megabytes.
Kilobyte: Shows that the amounts entered in the primary and secondary quantity fields are expressed in kilobytes.
Byte: Shows that the amounts entered in the primary and secondary quantity fields are expressed in bytes.
Records: Shows that the amounts entered in the primary and secondary quantity fields are the average number of records of the size specified by the block size field.

Note: "Space units" allows the shortest unique abbreviation for each attribute; for example, T for TRKS, C for CYLS, K for KB, and M for MB, BY for BYTE, R for RECORDS, and BL for BLKS.

Average record unit

Shows the unit used when allocating average record length. U specifies single-record units (bytes). K specifies thousand-record units (kilobytes). M specifies million-record units (megabytes). The default value is U.

Primary quantity

The primary allocation quantity in tracks, cylinders, blocks, megabytes, kilobytes, bytes, or records, as shown in the "Space units" field. This number can be zero for sequential data sets, but must be greater than zero for PDSs. Also, if the primary quantity is zero, the secondary quantity must be greater than zero.

Secondary quantity

The secondary allocation quantity in tracks, cylinders, blocks, megabytes, kilobytes, bytes, or records, as shown in the "Space units" field. This quantity is allocated when the primary quantity is insufficient.

Directory blocks

Enter one of these:

For partitioned data sets, you must specify the number of directory blocks. Each 256-byte block accommodates these number of directory entries:
- Data sets with ISPF statistics: 6
- Data sets without ISPF statistics: 21
- Load module data sets: 4-7, depending on attributes
ISPF requests a data set organization (DSORG) of PS when the value is zero or PO if the value is greater than zero. Note that ISPF converts a blank value to zero.

Record format

Any valid combination of these codes:

F: Fixed-length records.
V: Variable-length records.
U: Undefined format records.
B: Blocked records.
A: ASA printer control characters.
M: Machine code printer control characters.
S: Standard (for F) or spanned (for V); use only with sequential data sets.
T: Track-overflow feature.

Note:

You must enter either F, V, or U.
You can specify S and T, but ISPF does not otherwise support them.

Record length

The logical record length, in bytes, of the records to be stored in the data set.

Block size

The block size, also called physical record length, of the blocks to be stored in the data set. Use this field to specify how many bytes of data to put into each block, based on the record length. For example, if the record length is 80 and the block size is 3120, 39 records can be placed in each block.

Note: The record length and block size are verified to be consistent with the record format. If you need to use non-standard characteristics, use the TSO ALLOCATE command.

Data set name type

The type of data set to be allocated:

LIBRARY: Allocates a partitioned data set extended.
HFS: Allocates an HFS PDSE. This is valid for DFSMS 1.2 only.
PDS: Allocates a partitioned data set.
LARGE: Allocates a large format sequential data set.
EXTREQ: Indicates that an extended data set is required.
EXTPREF: Indicates that an extended data set is preferred.
BASIC: Indicates that neither an extended nor a large format sequential data set is to be allocated.
blank: Allocates a partitioned or sequential data set based on the data set characteristics entered.

Note: If you specify LIBRARY and a zero directory size, ISPF allocates a PDSE and overrides the zero directory size. If you specify blanks for the directory size, a sequential data set is allocated instead of a PDSE.

Data set version

The version number when the Data set name type is LIBRARY. Valid values are:

1: Library version 1
2: Library version 2
blank: ISPF does not specify the library version and this is determined by system defaults.

Extended Attributes

Valid values are:

NO: Data set cannot have extended attributes or reside in EAS. This is the default for non-VSAM data sets.
OPT: Data set can have extended attributes and reside in EAS. This is the default for VSAM data sets.
blank: Use default based on data type.

Expiration date

Allows you to protect valuable data by specifying a date, in your national language, when the data set may be deleted. If you try to delete an unexpired data set, ISPF displays two panels: a Confirm Delete panel, followed by a Confirm Purge panel. See D — delete entire data set for more information about deleting unexpired data sets.

An expiration date is not required, but if you enter one it should be in one of these formats:

YYYY/MM/DD: Date shown in year, month, and day, or your equivalent national format. The maximum expiration date allowed is 2155/12/31.
YYYY.DDD: Date shown in Julian format, such as 2006.066 for March 7, 2006. The maximum expiration date allowed is 2155.365.
You can specify a DDD value of up to 366 if the YYYY value represents a leap year.
DDDD: The number of days, starting with the creation date, after which the data set can be deleted. DDDD has a range of 0 to 9999.
PERM, NOLIMIT, NEVER, 9999: Specifying any of these values causes ISPF to translate it to a value of 1999.365. This is treated by ISPF as permanent retention.

Allocate Multiple Volumes

Allows you to allocate sequential data sets that span multiple volumes. ISPF supports a maximum of 59 volumes. Place a slash in this field and press Enter to display a panel similar to the one shown in Figure 3.

Figure 3. Multivolume allocation panel (ISRUAMV)

   Menu  RefList  Utilities  Help
 ─ ┌──────────── Multivolume Allocation ─────────────┐ ────────────────────────
   │ ISRUAMV                                         │
   │                                                 │              More:   - +
   │  Enter the number of volumes to allocate or     │  device address) **
 D │  the names of one or more volumes and           │ lt data class)
   │  press Enter to allocate or enter Cancel        │ S, KB, MB, BYTES
   │  command to exit.  If a number is entered,      │
   │  any volume names will be ignored.              │
   │                                   More:     +   │
   │  Number of volumes to allocate:                 │
   │                                                 │ tial data set) *
   │  Volume names:                                  │
   │   1. MVS8WF  2.         3.         4.           │
   │ Command ===>                                    │
   │  F1=Help         F2=Split        F3=Exit        │ DS, or blank)  *
   │  F7=Backward     F8=Forward      F9=Swap        │ MM/DD
   └─────────────────────────────────────────────────┘ D in Julian form
 Enter "/" to select option             DDDD for retention period in days
 /  Allocate Multiple Volumes           or blank)

 Command ===>
  F1=Help      F2=Split     F3=Exit      F7=Backward  F8=Forward   F9=Swap
 F10=Actions  F12=Cancel

This panel allows you to specify up to 59 volumes.

Note:

Although the volume input fields are numbered consecutively, you may enter volume names in any of the fields.
The volume that you enter in the "Volume serial" field on the Allocate New Data Set panel will be placed in the first field of the Multivolume Allocation panel.
If you enter only one volume, standard data set allocation is invoked.
If you enter a number in the "Number of volumes to allocate" field, any volume names left in the name fields are ignored, and might or might not be the volumes the data set is allocated to.
When displaying information about a multivolume data set, depending on your system setup, all volumes might not be shown until they have been accessed.