>good example of a continuation in the ADSM doc wouldn't hurt. Also, since
>there is a 100 character limit on parm information, what to do it you have
>more than that amount of info to pass. We eventually ran the install with
Here is some JCL that the DRM feature builds. It exploits the 'FILE:'
parameter of DSMSERV INSTALL. (DRM generates the JCL to recover your
specific server configuration.) This chunk was pulled from an actual
recovery plan file which also included JCL to allocate the DB and
LOG datasets, etc.
//***********************************************************************
//PARMLOG EXEC PGM=IEBGENER LOG PARAMETERS FOR INSTALL
//SYSIN DD DUMMY
//SYSPRINT DD SYSOUT=*
//SYSUT2 DD DSN=DRM.TEST.RP.PLG,
// DISP=(,CATLG,DELETE),
// SPACE=(TRK,(1,1)),
// UNIT=SYSDA,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160)
//SYSUT1 DD *
DRM.TEST.LG01X
DRM.TEST.LG02X
/*
//***********************************************************************
//PARMDB EXEC PGM=IEBGENER DB PARAMETERS FOR INSTALL
//SYSIN DD DUMMY
//SYSPRINT DD SYSOUT=*
//SYSUT2 DD DSN=DRM.TEST.RP.PDB,
// DISP=(,CATLG,DELETE),
// SPACE=(TRK,(1,1)),
// UNIT=SYSDA,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160)
//SYSUT1 DD *
DRM.TEST.DB01X
DRM.TEST.DB02X
/*
//***********************************************************************
//SERVER EXEC PGM=DSMSERV,DYNAMNBR=300,
// PARM='/INSTALL 2 FILE:''DRM.TEST.RP.PLG''
// 2 FILE:''DRM.TEST.RP.PDB'''
//DSMAMENG DD DSN=DSM2.SANRMSG(ANRMENU),DISP=SHR
//OPT DD DSN=DRM.TEST.DSMSERV.OPTX,DISP=SHR
//DSK DD DSN=DRM.TEST.ADSM.DISKLOG,DISP=(NEW,CATLG),
// SPACE=(TRK,(1,1)),
// UNIT=3390,VOL=SER=DRMSC1,
// DCB=(RECFM=FB,BLKSIZE=800,LRECL=80)
//SYSPRINT DD SYSOUT=*
//SYSTERM DD SYSOUT=*
Don Moxley , SSD Software
|