Allocating multivolume OSAM data sets on SMS-managed DASD

The following examples show alternate methods for allocating multivolume OSAM data sets on SMS-managed DASD.

When allocating data sets using the following JCL, you must specify an SMS storage class that was defined by your installation with guaranteed space (GUARANTEED_SPACE=YES) and specify the volume serial numbers. Without the guaranteed space attribute and the volume serial numbers, only the first volume will get a primary extent, and the other volumes will get secondary extents.

Use the following JCL samples to allocate multivolume OSAM data sets:

Use the following JCL sample to allocate multivolume OSAM data sets. These data sets are compatible with the Database Image Copy 2 utility. In the example, gtdstcls is a storage class that is defined with the guaranteed space attribute.

//OSAMALLO   JOB  A,OSAMEXAMPLE
//          EXEC  PGM=IEFBR14
//DD123       DD DSN=HIGHNODE.MIDNODE.ENDNODE,
//            DISP=(NEW,CATLG),
//            SPACE=(CYL,(200,100)),
//            UNIT=(3390)
//            VOL=SER=(VOL111,VOL222,VOL333),
//            STORCLAS=gtdstcls
/*

Use the following JCL sample, which uses the DFSMS Access Method Services ALLOCATE command to allocate multivolume OSAM data sets. These data sets are compatible with the Database Image Copy 2 utility. In the example, gtdstcls is a storage class that is defined with the guaranteed space attribute.
```
//OSAMALLO   JOB  A,OSAMEXAMPLE
//          EXEC  PGM=IDCAMS,REGION=4096K
//SYSPRINT    DD  SYSOUT=A
//SYSIN       DD *
	         DELETE 'HIGHNODE.MIDNODE.ENDNODE'

            IF LASTCC<=8 THEN SET MAXCC=0

            ALLOCATE DSN('HIGHNODE.MIDNODE.ENDNODE') -
            NEW CATALOG -
            SPACE(200,100) CYLINDERS -
            UNIT(3390) -
            VOL(VOL111,VOL222,VOL333) -
            STORCLAS(gtdstcls)
/*
```
For more information about allocating space for data sets on SMS-managed DASD, see z/OS® DFSMS Storage Administration Reference (for DFSMSdfp, DFSMSdss, and DFSMShsm).