Required Parameters

NONVSAM
specifies that a non-VSAM non-SMS-managed data set is to be defined or that a collection of objects is to be defined. The collection of objects you define are SMS-managed. To define a non-VSAM SMS-managed data set that is not a collection of objects, use either the ALLOCATE command or JCL.

Abbreviation: NVSAM

NAME(entryname)
specifies the name of the non-VSAM data set or collection of objects being defined. The entryname is the name that appears in the catalog; it is the name used in all future references to the data set. The entryname must be unique within the catalog in which it is defined.

You identify a GDS with its GDG name followed by the data set's generation and version numbers (GDGname.GxxxxVyy). The update or higher RACF® authority to the GDG is required. The GDG must exist before the GDS is defined.

Exception: For OAM, the entryname is the name of the OAM collection.

To define an OAM collection, you must specify both the COLLECTION and RECATALOG parameters.

DEVICETYPES(devtype[ devtype...])

Start of changeYou can specify a generic device name that is supported by your system, for example, 3390. See Device Type Translate Table for a list of generic device types.End of change

Restriction: Do not specify an esoteric device group such as SYSDA, because allocation can be unsuccessful if:
  • Input/output configuration is changed by adding or deleting one or more esoteric device groups.
  • The esoteric definitions on the creating and using systems do not match when the catalog is shared between the two systems.
  • The data set was cataloged on a system not defined with the Hardware Configuration Definition (HCD), but used on a system that is defined with HCD.

If you expect to change the device type of the system residence volume, you can code DEVICETYPES(0000) and this field is resolved at LOCATE, and DELETE time to the device type. This will allow you to use the non-VSAM data sets without having to recatalog them to point to the new volume. When you code DEVICETYPES(0000) you must also code VOLUMES(******), or an error will result.

You can code DEVICETYPES(0000) if the VOLUMES parameter specifies an indirect volume serial ('******'), or an extended indirect volume serial (a system symbol). A value of DEVICETYPES(0000) will cause the actual device type to be determined from the current system residence volume (or its logical extension) at the time the catalog entry is retrieved. DEVICETYPES(0000) is only valid with an indirect volume serial specification in the VOLUMES parameter.

In addition to the above, if you are using the symbolic form of volume serials, the volume must be mounted and online at the time the catalog entry is retrieved from the catalog. If it is not, the catalog request will be terminated with a return and reason code.

Exception: DEVICETYPES is not applicable for an OAM non-VSAM entry and is ignored if specified.

Abbreviation: DEVT

VOLUMES(volser[ volser...])
specifies the volumes to contain the non-VSAM data set. VOLUMES is required when you define a non-OAM non-VSAM data set.

There are two special forms of the VOLUMES parameter that can be provided, and they are referred to as the indirect volume serial forms. They result in the system dynamically resolving the volume serial to the system residence (or its logical extension) serial number when the catalog entry is retrieved. It is not resolved when the DEFINE NONVSAM is processed. This allows you to later change the volume serial number(s) of the system residence volume (or its logical extensions) without having to recatalog the non-VSAM data sets on those volumes.

The two special forms are:

  1. VOLUMES(******)
  2. VOLUMES(&xxxxx), where &xxxxx is a symbol contained in the SYS1.PARMLIB IEASYMXX member that was specified at IPL time. The symbol name is intended to represent the volume that is a logical extension of the system residence volume. The symbol name must be specified as a single, simple (not substringed) symbol of no more than six characters including the leading ampersand. If a symbol is intended to represent a six-character volume serial number, the symbol must be six characters long and the ending period must be omitted. As an example:
    • VOLUMES(&SYSR2)

    If &SYSR2 has been defined at IPL by an entry in the IEASYMxx member, the value of that symbol will be used when this catalog entry is retrieved from the catalog. If the symbol is not defined, the value returned for the volume serial will be &SYSR2.

    IBM® recommends the use of the symbol &SYSR2 for the first logical extension to the system reference volume, &SYSR3 for the second, and so on.

Exception: VOLUMES is not applicable for an OAM non-VSAM entry and is ignored if specified.

If you code VOLUMES(******), then the system dynamically resolves this to the system residence volume serial number whenever the catalog entry is used. It is not resolved when the DEFINE NONVSAM is processed. This allows you to later change the volume serial number of system residence volume without also having to recatalog the non-VSAM data sets on that volume.

Abbreviation: VOL

Use RACF commands to specify an ERASE attribute in a generic or discrete profile for a non-VSAM data set. Use of this attribute renders all allocated DASD tracks unreadable before space on the volume is made available for reallocation. Refer to the appropriate RACF publications for information about how to specify and use this facility.

Parent topic: DEFINE NONVSAM Parameters