Previous Topic: 3.1.2.1 Sample JCL Member VCCRUN

Next Topic: 3.1.2.3 Setting Up Hourly Scans with VCC

3.1.2.2 Sample JCL Member VCCRUNH


 The following JCL is used for collecting Hierarchical File
 Systems data.

//jobname  JOB  (accounting_data),'VCCRUN',
//         CLASS=A,
//         MSGCLASS=A,
//         NOTIFY=
//*
//* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
//*                      - Sample JCL -                     *
//*           CA MICS Space Collector Option (VCC)          *
//*         Hierarchical File Systems 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                      *
//*                                                         *
//*                                                         *
//*                                                         *
//* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
//*
//*
//*---------------------------------------------------------*
//* STEP1  -  Collect HFS data                              *
//*---------------------------------------------------------*
//*
//STEP1    EXEC PGM=VCCMAIN,REGION=5000K       <== See Note-1
//*
//STEPLIB  DD   DISP=SHR,DSN=__________        <== See Note-2
//SYSPRINT DD   SYSOUT=*
//VCCSTATS DD   SYSOUT=*
//VCCSNAP  DD   SYSOUT=*
//*
//VCCNTROL DD   DISP=SHR,DSN=______.VCC.DCONTROL
//*
//VCCDATA  DD   DSN=______.VCC.VCCDATA2,
//         DISP=OLD
//*
//*
//*
//VCCPARMS DD   *
HFSSUBT=4
DATALEVEL=(ALL)
/*
//*
//*---------------------------------------------------------*
//* STEP2  -  Copy collected data to SMF Daily GDG          *
//*---------------------------------------------------------*
//*
//STEP2    EXEC PGM=IEBGENER,COND=(4,LT)
//SYSPRINT DD   SYSOUT=*
//SYSUT1   DD   DSN=______.VCC.VCCDATA2,
//         DISP=OLD
//SYSUT2   DD   DSN=______.VCC.HFSBKUP(+1),
//         UNIT=____,
//         DISP=(,CATLG,DELETE),LABEL=(1,SL)
//SYSIN    DD   DUMMY
//*
//*---------------------------------------------------------*
//* STEP3  -  Flag VCC Data Copied                          *
//*---------------------------------------------------------*
//*
//STEP3    EXEC PGM=VCCUTIL,REGION=2048K,
//         COND=(4,LT),PARM='FLAGCOPY'
//SYSPRINT DD   SYSOUT=*
//STEPLIB  DD   DISP=SHR,DSN=__________        <== See Note-2
//*
//VCCSNAP  DD   SYSOUT=*
//*
//VCCNTROL DD   DISP=SHR,DSN=______.VCC.DCONTROL
//*
//

VCCRUNH 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 4096 K.

Step 1

  This step will execute VCC to collect DASD data on
  Hierarchical File Systems.

  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 where the VCC modules were moved during
  installation.  (See Chapter 4, VCC Installation).

  SYSPRINT - Used for the VCC Message Log.  If pre-allocated
  to a disk data set, DCB attributes should include
  RECFM=VBA,LRECL=137.

  VCCSTATS - Used for VCC Status and Statistics Reports.  If
  pre-allocated to a disk data set, DCB attributes should
  include RECFM=VBA,LRECL=137.

  VCCSNAP - VCC uses this DD statement to dump pertinent
  storage areas to assist in problem determination.

  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 *. You
  can code the parameters as part of the JCL stream.

  VCCDATA - This DD statement defines the data set that VCC
  uses as a recording medium if SMF is not used.  This data
  set must be variable blocked. If you do not specify the
  BLKSIZE, VCC will set it based on the output DASD device
  type. For maximum device capacity utilization, you should
  code the following values on the VCCDATA DD statement.


   Device   Optimum device utilization parameters
   -------  -------------------------------------------------
   3390     DCB=(BLKSIZE=27998,LRECL=4096,RECFM=VB)
   3380     DCB=(BLKSIZE=23476,LRECL=4096,RECFM=VB)
   other    DCB=(BLKSIZE=32760,LRECL=4096,RECFM=VB)

  VCCNTROL - Defines the VCC Control File.  Allocated during
  VCC installation, it keeps track of the volumes processed
  and VCC processing timestamps.

  This Control File must be shared across each OS/390 system
  that runs VCC to collect Hierarchical File Systems Data
  within a shared DASD complex.

Step 2

  You need this step only if SMF is not going to be used as
  the VCC recording medium. It uses the IBM standard utility
  IEBGENER to copy the data recorded by VCC to a Generation
  Data Group (GDG) used by CA MICS Daily processing.

  The sample JCL provided and shown above presumes that a GDG
  named '_____.VCC.HFSBKUP' was previously defined.  For
  guidance on how to define a GDG, see IBM's Access Method
  Services Reference manual (GC26-4019).

Step 3

  This step will execute only if Step 2 ran 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 set referenced by the VCCDATA DD
  statement 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, or a new data set is used.
  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.