09.07.2015 Views

z/OS V1R6.0 DFSMS Access Method Services for Catalogs

z/OS V1R6.0 DFSMS Access Method Services for Catalogs

z/OS V1R6.0 DFSMS Access Method Services for Catalogs

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

DEFINE NONVSAMDEFINE NONVSAM ParametersThe DEFINE NONVSAM command uses the following parameters.Required ParametersNONVSAMspecifies that a non-VSAM non-SMS-managed data set is to be defined or thata collection of objects is to be defined. The collection of objects you define areSMS-managed. To define a non-VSAM SMS-managed data set that is not acollection of objects, use either the ALLOCATE command or JCL.Abbreviation: NVSAMNAME(entryname)specifies the name of the non-VSAM data set or collection of objects beingdefined. The entryname is the name that appears in the catalog; it is the nameused in all future references to the data set. The entryname must be uniquewithin the catalog in which it is defined.||||||You identify a GDS with its GDG name followed by the data set’s generationand version numbers (GDGname.GxxxxVyy). The update or higher RACFauthority to the GDG is required. The GDG must exist be<strong>for</strong>e the GDS isdefined.Exception: For OAM, the entryname is the name of the OAM collection.To define an OAM collection, you must specify both the COLLECTION andRECATALOG parameters.See “How to code subparameters” on page xvii <strong>for</strong> additional considerationson coding entryname.DEVICETYPES(devtype[ devtype...])specifies the device types of the volumes containing the non-VSAM data setbeing defined. If the non-VSAM data set resides on different device types, thedevice types must be specified in the same order as the volume serial numberslisted in the VOLUMES parameter.You can specify a generic device name that is supported by your system, <strong>for</strong>example, 3390. See “Device Type Translate Table” on page 376 <strong>for</strong> a list ofgeneric device types.Restriction: Do not specify an esoteric device group such as SYSDA, becauseallocation can be unsuccessful if:vvvInput/output configuration is changed by adding or deleting one or moreesoteric device groups.The esoteric definitions on the creating and using systems do not matchwhen the catalog is shared between the two systems.The data set was cataloged on a system not defined with the HardwareConfiguration Definition (HCD), but used on a system that is defined withHCD.If you expect to change the device type of the system residence volume, youcan code DEVICETYPES(0000) and this field is resolved at LOCATE, andDELETE time to the device type. This will allow you to use the non-VSAMdata sets without having to recatalog them to point to the new volume. Whenyou code DEVICETYPES(0000) you must also code VOLUMES(******), or anerror will result.182 z/<strong>OS</strong> <strong>V1R6.0</strong> <strong>DFSMS</strong> <strong>Access</strong> <strong>Method</strong> <strong>Services</strong> <strong>for</strong> <strong>Catalogs</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!