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

IMPORTvvvIf VOLUMES is specified with the cluster or alternate index name, thespecified volume list is defined for the data component. For akey-sequenced cluster or alternate index, the specified volume list is alsodefined for the index component.If VOLUMES is specified with the data component name, the specifiedvolume list is defined for the data component. Any specification ofVOLUMES with the cluster or alternate index name is overridden.For a key-sequenced cluster or alternate index, if VOLUMES is specifiedwith the index component name, the specified volume list is defined forthe index component. Any specification of VOLUMES with the cluster oralternate index name is overridden.If a guaranteed space storage class is assigned to the data sets (cluster) andvolume serial numbers are specified, space is allocated on all specifiedvolumes if the following conditions are met:vvAll volumes specified are in the same storage group.The storage group to which these volumes belong is in the list of storagegroups selected by the ACS routines for this allocation.For clusters or alternate indexes, if multiple volumes are specified, theymust be of the same device type. By repeating the OBJECTS parameter setfor each component and including VOLUMES in each parameter set, youcan have the data and index components on different volumes. Althoughthe index and data components can reside on different device types, eachvolume of a multivolume component must be of the same type.If the receiving volume is different from that which originally containedthe cluster or alternate index, the job might end because of allocationproblems. Each space allocation quantity is recorded in a catalog entry asan amount of cylinders or tracks even if RECORDS was specified in theDEFINE command.When a cluster or alternate index is imported, the number of cylinders ortracks in the catalog entry is not modified, even though the object might beimported to reside on a device type other than that it was exported from.If an object is exported from a smaller DASD and imported to a largerDASD, more space is allocated than the object needs. Conversely, if anattempt is made to import an object that previously resided on a largerDASD to a smaller DASD, it might be unsuccessful.You can avoid space allocation problems by defining an empty cluster oralternate index and identifying it as the target for the object beingimported as described below:vvUse the DEFINE command to define a new entry for the cluster oralternate index in the catalog to which it is to be moved. If space wasallocated in RECORDS, you can specify the same quantity; if it wasallocated in TRACKS or CYLINDERS, you must adjust the quantity forthe new device type. If an entry already exists in the catalog for theobject, you must delete that entry or use a different name in the DEFINEcommand.Use the IMPORT command to load the portable data set into the newlydefined cluster or alternate index. When IMPORT encounters an emptytarget data set, the exported catalog information is bypassed and onlythe data records are processed.Chapter 25. IMPORT 265