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 USERCATALOGspace. You can specify the amount of space as a parameter of USERCATALOG,as a parameter of USERCATALOG and DATA, or as a parameter ofUSERCATALOG, DATA and INDEX.This parameter is optional if the cluster is managed by SMS. If it is specified<strong>for</strong> an SMS-managed cluster, it will override the DATACLASS spacespecification. If it is not specified <strong>for</strong> an SMS-managed cluster, it can bemodeled or defaulted by SMS. If it cannot be determined, the DEFINE will beunsuccessful.If you specify KILOBYTES or MEGABYTES, the amount of space allocated isthe minimum number of tracks or cylinders required to contain the specifiednumber of kilobytes or megabytes.To maintain device independence, do not specify the TRACKS or CYLINDERSparameters. If TRACKS or CYLINDERS is specified <strong>for</strong> an SMS-managed usercatalog, space is allocated on the volumes selected by SMS in units equivalentto the device default geometry.z/<strong>OS</strong> <strong>DFSMS</strong>: Managing <strong>Catalogs</strong> describes how space allocation differsdepending on the parameters you specify. It also provides in<strong>for</strong>mation aboutestimating the amount of space to be specified <strong>for</strong> a catalog.primary[ secondary]Specifies the size of the primary and secondary extents to be allocated.After the primary extent is filled, the space can expand to include amaximum of 122 additional secondary extents if you have specified asecondary allocation amount. Secondary allocation should be specified incase the catalog has to be extended. If you specify a secondary spaceallocation greater than 4.0 gigabytes, the value is reset to the maximumvalue <strong>for</strong> that DASD device.Abbreviation: TRKException: The abbreviations CYL, CYLINDER, REC, and RECORD areacceptable to access method services but cannot be used in TSO because theabbreviations do not have enough initial letters to make the keyword unique.VOLUME(volser)Specifies the volume that is to contain the catalog. VOLUME must be specifiedas a parameter of USERCATALOG, unless:v You specify the MODEL parameter, orv The data set is managed by SMS.If the data set is SMS-managed, you should not request specific volume serialnumbers with the VOLUME parameter. The ACS routines will assign the dataset to a storage class containing attributes such as VOLUME and UNIT. Youcan allocate your data set to a specific volume serial number only if yourstorage administrator has selected GUARANTEED SPACE=YES in the storageclass assigned to the data set. Only then can you specify volume serialnumbers that will override the volume serial numbers used by SMS. However,if space is not available on the volumes with the serial numbers you specified,your request will be unsuccessful. See z/<strong>OS</strong> <strong>DFSMS</strong>dfp Storage AdministrationReference <strong>for</strong> in<strong>for</strong>mation about SMS volume selection.You can choose to let SMS assign specific volume serial numbers to anSMS-managed data set by coding an * <strong>for</strong> each volume serial. SMS thendetermines the volume serial. If you omit volser, you get one volume.Chapter 19. DEFINE USERCATALOG 203

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

Saved successfully!

Ooh no, something went wrong!