VSAM clusters

The selection of source data sets is performed through TSO Monitor, in the Define zDMF Group – Panel 2; refer to Source volume definition parameters for a complete description of these parameters. Among these parameters is the source data set option, SPHERE, that you must set up. You must be aware that the SPHERE option affects the processing of data sets that are part of a cluster, irrespective of the SPHERE setting.

The SPHERE(YES|NO) parameter affects the processing of AIXs and PATHs related to a VSAM cluster. SPHERE does not affect any processing on the DATA and INDEX component of a cluster. If a VSAM data set has both a DATA component and an INDEX component, zDMF will not allow migration of one component and not the other. In general, selecting either component of the cluster will cause the selection of both components.

zDMF treats the data component, index component (if INDEXed), and the cluster as a single entity. While the individual components are allocated directly using CVAF services, once the components are allocated, zDMF uses IDCAMS to recatalog the target cluster. So all components of a cluster must be part of the migration.

When migrating VSAM Clusters, make sure you specify the base cluster name, or a dsname mask that will include the VSAM metadata, when setting up VSAM–oriented migration groups. Likewise, the target must be given an appropriate target cluster name. For further information, refer to Target volume definition parameters..

Refer to the following cases for specific configuration:

• Case 1: SPHERE(YES), input volume list not present

  Use the catalog to determine the list of source data sets matching the input mask. If the VSAM component matches the input mask, obtain the SPHERE record and add related data names to source data sets, irrespective of the input mask.

• Case 2: SPHERE(NO), input volume list not present

  A fully qualified data component name is moved even when no volume list is present and SPHERE(NO) is specified.

• Case 3: Input volume list present

  Fully qualified cluster names are NOT moved when a volume list is present; the activation will fail. A fully qualified cluster name is a CATALOG entity, not a VTOC entity. The presence of a volume list implies using the VTOC to build a list of data sets matching the mask RATHER than the CATALOG. Hence a fully qualified cluster name will normally not match anything found in a VTOC.

  Fully qualified data component names, for example, STRUBEL.RS626X.VM2.VV0A0A.DATA, will be moved (including the cluster) irrespective of the setting of the SPHERE parameter with a volume list.

  Note: Migrating Db2® Cluster Data Sets: Since Db2 data sets are VSAM clusters, refer to the information mentioned above. If you are migrating the entire database, ensure that masks matching all database clusters are included.