3. USAGE GUIDELINES › 3.1 Setting Up VCC for Operation › 3.1.2 Customizing the VCC JCL › 3.1.2.1 Sample JCL Member VCCRUN
3.1.2.1 Sample JCL Member VCCRUN
The following JCL is used for collecting DASD VTOC, VSAM,
HSM, and System Catalog information.
//jobname JOB (),'',
// CLASS=A,
// MSGCLASS=A,
// NOTIFY=
//*
//* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
//* - Sample JCL - *
//* CA MICS DASD Space Collector (VCC) *
//* VTOC, VSAM, HSM, and System Catalog Data Collection *
//* *
//* Notes: *
//* 1. VCC requires a minimum of 4096K to run. *
//* *
//* 2. If not included in the system linklist, the STEPLIB*
//* must be an authorized library. *
//* *
//* 3. Use of this data set is optional. It is used for *
//* recording information from DFHSM. *
//* *
//* 4. Use of these data sets is optional. They are used *
//* for collecting information from DFHSM. Specify the *
//* data set names for the MCDS and BCDS DFHSM data *
//* sets. You may remove these DD statements allowing *
//* VCC to dynamically allocate them if DFHSM *
//* information is desired. *
//* *
//* 5. If DFHSM information is to be collected and your *
//* data center is using a split MCDS or BCDS, you *
//* should code your DD statements as follows: *
//* *
//* For a split MCDS: *
//* //MCDS DD DISP=SHR,DSN=_____.______.MCDS1 *
//* //MCDS2 DD DISP=SHR,DSN=_____.______.MCDS2 *
//* . *
//* . *
//* . *
//* *
//* For a split BCDS: *
//* //BCDS DD DISP=SHR,DSN=_____.______.BCDS1 *
//* //BCDS2 DD DISP=SHR,DSN=_____.______.BCDS2 *
//* . *
//* . *
//* . *
//* *
//* Note that in both instances the first DD name is *
//* MCDS or BCDS, not MCDS1 or BCDS1. *
//* *
//* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
//*
//*---------------------------------------------------------*
//*STEP1 - Collect DASD VTOC, VSAM, HSM, System Catalog Data*
//*---------------------------------------------------------*
//*
//STEP1 EXEC PGM=VCCNTRL,REGION=5000K <== See Note-1
//*
//STEPLIB DD DISP=SHR,DSN=__________ <== See Note-2
//VCCSTATS DD SYSOUT=*
//VCCVTMSG DD SYSOUT=*
//VCCVSMSG DD SYSOUT=*
//VCCHSMSG DD SYSOUT=*
//VCCSNAP DD SYSOUT=*
//ARCSNAP DD SYSOUT=*
//*
//VCCNTROL DD DISP=SHR,DSN=______.VCC.CONTROL
//*
//VCCDATA DD DSN=______.VCC.VCCDATA1,
// DISP=OLD
//*
//*
//*
//VCCHSM DD DSN=______.VCC.HSMDATA, <== See Note-3
// DISP=OLD
//*
//*
//*
//MCDS DD DISP=SHR,DSN=_____.______.MCDS <== See Note-4,5
//**MCDS2 DD DISP=SHR,DSN=_____.______.MCDS2 <== See Note-5
//**MCDS3 DD DISP=SHR,DSN=_____.______.MCDS3 <== See Note-5
//BCDS DD DISP=SHR,DSN=_____.______.BCDS <== See Note-4,5
//**BCDS2 DD DISP=SHR,DSN=_____.______.BCDS2 <== See Note-5
//**BCDS3 DD DISP=SHR,DSN=_____.______.BCDS3 <== See Note-5
//*
//VCCPARMS DD *
VSAMSUBT=8
VSAMERR=4
VTOCSUBT=8
VTOCERR=4
/*
//*
//*---------------------------------------------------------*
//* STEP2 - Copy collected data to SMF DAILY GDG *
//*---------------------------------------------------------*
//*
//STEP2 EXEC PGM=IEBGENER,COND=(4,LT,STEP1)
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DSN=______.VCC.VCCDATA1,
// DISP=OLD
//SYSUT2 DD DSN=______.VCC.SMFBKUP(+1),
// UNIT=____,
// DISP=(,CATLG,DELETE),LABEL=(1,SL)
//SYSIN DD DUMMY
//*
//*---------------------------------------------------------*
//* STEP3 - Copy collected HSM data to SMF DAILY GDG *
//*---------------------------------------------------------*
//*
//STEP3 EXEC PGM=IEBGENER,COND=(4,LT,STEP1)
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DSN=______.VCC.HSMDATA,
// DISP=OLD
//SYSUT2 DD DSN=______.VCC.HSMBKUP(+1),
// UNIT=____,
// DISP=(,CATLG,DELETE),LABEL=(1,SL)
//SYSIN DD DUMMY
//*
//*---------------------------------------------------------*
//* STEP4 - Flag VCC Data Copied *
//*---------------------------------------------------------*
//*
//STEP4 EXEC PGM=VCCUPDT,REGION=512K,
// COND=((4,LT,STEP1),(0,NE,STEP2),(0,NE,STEP3))
//STEPLIB DD DISP=SHR,DSN=__________ <== See Note-2
//*
//VCCNTROL DD DISP=SHR,DSN=______.VCC.CONTROL
//*
VCCRUN JCL Detail Description
Jobcard
You can run VCC in any job class except a JES3 job class
that has JOURNALING specified. You may need to specify a
region size if your default size is not at least 2048 K.
Step 1
This step will execute VCC to collect DASD information.
STEPLIB - This statement is required only if the VCC
modules were not placed in an authorized library that is in
the system linklist. Otherwise, it should point to the
authorized library to which the VCC modules were moved
during installation. (See Chapter 4, Installation).
VCCSTATS - Used for the VTOC scan message log, as well as
for the VCC Run Status Report. If pre-allocated to a disk
data set, DCB attributes should include
RECFM=VBA,LRECL=133.
VCCVSMSG - Defines the DD statement that VCC uses for the
catalog scan log. If pre-allocated to a disk data set, DCB
attributes should include RECFM=VBA,LRECL=133.
VCCVTMSG - Defines the DD statement that VCC uses for the
VTOC scan log. If pre-allocated to a disk data set, DCB
attributes should include RECFM=VBA,LRECL=133.
VCCSNAP - VCC uses this DD statement to SNAP memory for the
VCC TEST option. It is also used during abnormal
termination of a subtask to produce a SNAP dump.
VCCPARMS - This DD statement is optional. If present, it
defines the VCC parameter data set. This data set can be a
member of a PDS, a physical sequential file, or a DD * and
you can code the parameters as part of the JCL stream.
VCCDATA - This DD statement defines the data set that VCC
will use as a recording medium if SMF is not going to be
used. This data set must be variable blocked. The LRECL
and BLKSIZE are controlled by VCC in order to ensure
maximum density of data per track. At run time, VCC will
override any values you code on the VCCDATA DD statement.
Device Parameters Enforced by VCC
------- -------------------------------------------------
3390 DCB=(BLKSIZE=27998,LRECL=27994,RECFM=VB)
3380 DCB=(BLKSIZE=23476,LRECL=23472,RECFM=VB)
other DCB=(BLKSIZE=32760,LRECL=32756,RECFM=VB)
VCCNTROL - Defines the VCC control file. You allocated it
during VCC installation and it keeps track of the volumes
processed and VCC processing timestamps.
The control file must be unique for each z/OS system that
will run VCC. It must not be shared between z/OS images
within a complex.
Data Sets Used by The VCC Interface to DFHSM (VCC-DFHSM)
VCCHSM - This DD statement defines the data set that VCC
uses as a recording medium if SMF is not used. If you are
writing HSM data directly to the VCCHSM data set, you
should allocate a large data set. If you are using SMF as
the recording source for HSM data, the file will be used as
a work file and you need to allocate only a few tracks. If
the data set is omitted, VCC will not process HSM data and
will issue a return code 8 for this step.
Device Parameters Enforced by VCC
------- -------------------------------------------------
3390 DCB=(BLKSIZE=27998,LRECL=255,RECFM=VB)
3380 DCB=(BLKSIZE=23476,LRECL=255,RECFM=VB)
other DCB=(BLKSIZE=32760,LRECL=255,RECFM=VB)
VCCHSMSG - Defines the DD statement that VCC uses for the
DFHSM Interface Report. If pre-allocated to a disk data
set, DCB attributes should include RECFM=VBA,LRECL=137.
MCDS - Defines the DD statement that specifies the data set
name of the DFHSM Migration Control Data Set. This is
required if HSMMIGRATE=Y is coded or defaulted.
Note: Consult with your systems programmer or DFHSM
administrator on the data set names for the MCDS and
BCDS and decide which z/OS image in a shared DASD
environment will be responsible for initiating a VCC
inventory of DFHSM control data sets.
MCDS2, MCDS3, and so on - Define the DD statements that
describe additional DFHSM Migration Control Data Sets, if
the installation employs a split MCDS. Note that there is
no such DD name as MCDS1.
BCDS - Defines the DD statement that specifies the data set
name of the DFHSM Backup Control Data Set. This is
required if HSMBACKUP=Y is coded or defaulted.
BCDS2, BCDS3, and so on - Define the DD statements that
describe additional DFHSM Backup Control Data Sets, if the
installation employs a split BCDS. Note that there is no
such DD name as BCDS1.
ARCSNAP - Defines a SYSOUT data set that the DFHSM ARCUTIL
program opens when LINKed by the VCCXHSM module. VCC-DFHSM
does not use it, but if you omit the DD statement for
ARCSNAP, you will get a "ARCSNAP DD STATEMENT MISSING"
message in the JES job log when ARCUTIL tries to OPEN it.
Step 2 and Step 3
You need these steps only if SMF is not going to be used as
the VCC recording medium. Step 3 is required if HSM=Y was
specified for VCC parameters. The IBM standard utility
IEBGENER is used to copy the data recorded by VCC to
Generation Data Groups (GDGs) used by DAILY processing.
The sample JCL provided and shown above presumes that GDGs
named '_____.VCC.SMFBKUP' and '____.VCC.HSMBKUP' were
previously defined. For information on how to define a
GDG, see IBM's Access Method Services Reference manual
(GC26-4019).
Step 4
This step will execute only if Step 2 and Step 3 run
successfully. It is required only if SMF is not used as
the recording medium for VCC. This step updates the VCC
control file indicating that a backup of the data sets
referenced by DD statements VCCDATA and VCCHSM (if HSM=Y)
was done. During initialization processing VCC will check
the control file to determine if a backup was done. If no
backup was done, VCC will not record new information to the
VCCDATA data set unless BYPASSBKUP=Y is specified for VCC
parameters. This ensures that VCC will only record DASD
space information if the data from the previous VCC run was
copied successfully.
Descriptions of the STEPLIB and VCCNTROL data sets are
under Step 1.
