You can allocate single-volume OSAM data sets by using JCL or z/OS®
DFSMS Access Method Services (AMS)
IDCAMS. For single-volume HALDB OSAM data sets, the allocation can be done either before or during the load step, although doing it in the load step is recommended.
- To allocate a single-volume sequential OSAM data set by using JCL, model your JCL after
the following example JCL.
//ALLOC1 EXEC PGM=IEFBR14
//DD1 DD DSN=HIGHNODE.MIDNODE.LOWNODE,
// DISP=(NEW,CATLG),
// SPACE=(CYLS,(200,100)),
//* add UNIT and VOLSER if needed
//* add SMS parameters if needed
//* do not code DCB parameters
/*
- To allocate a single-volume sequential OSAM data set by using AMS IDCAMS, model your JCL
after the following example JCL.
//ALLOC1 EXEC PGM=IDCAMS,REGION=4096K
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
/* */
/* DELETE OLD DATA SET IF IT EXISTS */
/* */
DELETE 'HIGHNODE.MIDNODE.ENDNODE'
IF LASTCC <= 8 THEN SET MAXCC = 0
/* */
/* ALLOCATE - WITH SMS PARAMETERS */
/* */
ALLOCATE DSN('HIGHNODE.MIDNODE.ENDNODE') -
NEW CATALOG -
DATACLAS(DCLAS) -
MGMTCLAS(MCLAS) -
STORCLAS(SCLAS) -
SPACE(200 100) CYLINDERS
/*
- To allocate an sequential OSAM data set capable of
residing in the extended addressing space on an extended address volume on non-SMS managed DASD,
model your JCL after the following example JCL.
//OSAMALLO JOB A,OSAMEXAMPLE
//S1 EXEC PGM=IEFBR14
//EAVD DD VOL=SER=EAV001,SPACE=(CYL,(20,5)),UNIT=3390,
// DSN=OSAM.SPACE,DISP=(,KEEP),EATTR=OPT