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

ALLOCATE||||||||||||||||||||||||||||||||||||||||||||||||ETEven parity and no conversion. BCD to EBCDIC translation whenreading, and EBCDIC to BCD translation when writing.T Odd parity and no conversion. BCD to EBCDIC translation whenreading, and EBCDIC to BCD translation when writing.The TRTCH and KEYLEN parameters are mutually exclusive.UCOUNT(count)|PARALLELShows device allocation.UCOUNT(count)This allocates the maximum number of devices, where count is a valuefrom 1-59.If you do not use VOLUME and PRIVATE parameters and MAXVOLexceeds UCOUNT, the system removes no volumes when the mountedvolumes have been used, causing abnormal termination of your job. Ifyou use PRIVATE, the system removes one of the volumes and mountsanother volume in its place to continue processing.PARALLELMounts one device for each volume given on the VOLUME parameteror in the catalog.UNIT(type)Defines the unit type to which a file or data set is to be allocated. You canlist an installation-defined group name, a generic device type, or a specificdevice address. If you do not supply volume information (the systemretrieves volume and unit information from a catalog), the unit type that iscoded overrides the unit type from the catalog. This condition exists only ifthe coded type and class are the same as the cataloged type and class.For VSAM data sets, use the AFF subparameter carefully. If the clustercomponents and the data and its index reside on unlike devices, the resultsof UNIT=AFF are unpredictable.When you allocate a new SMS-managed data set, the system ignores theUNIT parameter. The system determines the UNIT and VOLUME from thestorage class associated with the data set. Use UNIT only if you want toallocate a non-SMS-managed data set to a specific unit type.If the storage administrator has set up a default unit under SMS regardlessof whether the data set is SMS-managed, you do not have to use UNIT. Ifyou do not, the system determines the default UNIT for bothSMS-managed and non-SMS-managed data sets.VOLUME(serial-list)This is the serial number of an eligible direct access volume on which anew data set is to reside or on which an old data set is located. If you useVOLUME for an old data set, the data set must be on the specified volumefor allocation to take place. If you do not include VOLUME, the systemallocates new data sets to any eligible direct access volume. The UNITinformation in your procedure entry in the user attribute data set (UADS)determines eligibility. You can use up to 255 volume serial numbers.For VSAM data sets you must use this subparameter carefully. See thesection that discusses DD parameters to avoid when processing VSAMdata sets in z/OS MVS JCL User’s Guide before using the VOLUMEsubparameters REF, volume-sequence-number, or volume-count.Chapter 4. ALLOCATE 47