Appendix F. VSAM DATASET ACTIVITY-RELATED INTERFACE

While information about VSAM dataset action-related
information and Integrated Catalog Facility activity does not
currently reside in CA MICS, StorageMate provides an external
interface that allows you to place this information in a
non-CA MICS SAS dataset, and then read that dataset with
CA MICS StorageMate.  This section documents the steps you
must take to create this external SAS dataset before
attempting to use this information in StorageMate
(STGEJF,STGEJG) reports. You need not be concerned about
performing the items described here unless you plan to use
VSAM dataset actions or ICF activity as an input source to
StorageMate.

A sample job is distributed with this product as an example
of how VSAM dataset action and Integrated Catalog Facility
activity information can be placed into a SAS dataset and
then read as input by CA MICS StorageMate.  This job is
contained in the following member:

 o sharedprefix.MICS.CNTL(STGEJFG)

   This sample is designed to use input from your SMF data
   sets as input to the CA MICS StorageMate product. This job
   will process SMF record types 61, 62, 64, 65, and 66 based
   on the parameters set in the MACRO call for %CREATEDB.

   You have an option to collect Integrated Catalog Facility
   activity information from the SMF 61, 65, and 66 records
   by specifying the ICFCAT parameter. This will create a SAS
   file called SMF6156 containing one observation for every
   record which was INSERTED, UPDATED, or DELETED from an ICF
   controlled catalog.  You also have the option to collect
   VSAM dataset activity information from the SMF 62 and 64
   records by specifying the OPENCLOSE parameter. This will
   produce two SAS files, SMF62 and SMF64. The SMF62 file
   will contain OPEN requests for VSAM datasets, and SMF64
   will contain CLOSE requests for VSAM datasets.

   Simply code the MACRO call as follows:

   /********************************************************
   /* CODE THE FOLLOWING MACRO AS FOLLOWS:
   /*
   /*           PARAMETER     SMF RECORD          ACTION
   /*          -----------   ------------     ---------------
   /*            ICFCAT       61,65,66         INS. UPD. DEL.
   /*            OPENCLOSE    62,64            OPEN, CLOSE
   /*            ALL          61,62,64,65,66
   /*
   /*  %CREATEDB([OPENCLOSE][ICFCAT][ALL])
   /*
   /*  EXAMPLES: %CREATEDB(OPENCLOSE);
   /*            %CREATEDB(OPENCLOSE ICFCAT);
   /*            %CREATEDB(ICFCAT);
   /*            %CREATEDB(ALL);
   /********************************************************
   %CREATEDB(ALL);

Usage Notes

A. SMF Record Creation

   VSAM Dataset Open and Close Activity

   SMF record type 62 is written at the successful or
   unsuccessful opening of a VSAM component or cluster.  This
   record identifies the VSAM component or cluster, gives the
   VSAM catalog in which the object is defined, and the
   volume on which the catalog and object are stored.  It
   identifies the job by job log identification and user
   identification.

   SMF record type 64 is written when a VSAM component or
   cluster is closed, VSAM must switch to another volume to
   continue to read or write, or there is no more space
   available for VSAM to continue processing. If a cluster is
   closed, one record is written for each component in the
   cluster.

   VSAM Integrated Catalog Facility Activity

   SMF record type 61 is written during any processing that
   results in a DEFINE request to Catalog Management
   Services. One record is written for each record inserted
   or updated in a catalog. This record identifies the entry
   being defined (the catalog in which the catalog record is
   written) and identifies the job by job log and user
   identifiers.

   SMF record 65 is written during any processing that
   results in a DELETE request to Catalog management
   services.  One type 65 record is written for each record
   updated or deleted from a catalog. Record type 65
   identifies the entry being deleted and the catalog in
   which the catalog record is updated or deleted. It
   indicates whether a VSAM cluster or non-VSAM dataset was
   scratched, or only catalog information was deleted. It
   also indicates the job by job log identification and user
   identification.

   Record type 66 is written during any processing that
   results in an ALTER request to Catalog Management
   Services. One type 66 record is written for each record
   written or deleted from a catalog. Record type 66
   identifies the entry being altered and the catalog in
   which the catalog record is written or deleted.  It
   indicates if the entry was renamed and, if so, gives the
   old and new names of the entry.  It also indicates the job
   by job log identification and user identification.