Appendix E. NON-VSAM DATA SET ACTION-RELATED INTERFACE

While information about actions such as OPEN, CLOSE, DELETE,
and RENAME performed on your non-VSAM data sets does not
currently reside in CA MICS, StorageMate provides an external
interface that allows you to place data set action-related
information in a non-CA MICS SAS data set, and read that data
set with CA MICS StorageMate. This section documents the
steps you must take to create this external SAS data set
before attempting to use this information in the StorageMate
(STGEJD) report. You need not be concerned about doing the
items described here unless you plan to use non-VSAM data set
actions as an input source to StorageMate.

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

 o sharedprefix.MICS.CNTL(STGEJD)

   This sample is designed to use input from your SMF data
   sets as input into the CA MICS StorageMate product. This
   job will process SMF record types 14, 15, 17, and 18,
   based on the parameters set in the MACRO call for
   %CREATEDB.  You can select the following non-VSAM data set
   actions to report on OPEN, CLOSE, DELETE, and RENAME.
   Simply code the MACRO call as follows:

   /********************************************************/
   /* CODE THE FOLLOWING MACRO AS FOLLOWS:                 */
   /*                                                      */
   /*             ACTION   SMF RECORD                      */
   /*             ------   ----------                      */
   /*              OPEN      14                            */
   /*              CLOSE     15                            */
   /*              DELETE    17                            */
   /*              RENAME    18                            */
   /*              ALL       14,15,17,18                   */
   /*                                                      */
   /*  %CREATEDB([OPEN][CLOSE][DELETE][RENAME][ALL])       */
   /*                                                      */
   /*  EXAMPLES: %CREATEDB(OPEN DELETE);                   */
   /*            %CREATEDB(OPEN CLOSE);                    */
   /*            %CREATEDB(OPEN CLOSE DELETE RENAME);      */
   /*            %CREATEDB(ALL);                           */
   /********************************************************/

Usage Notes

A. SMF Record Creation

   The SMF 14 record is created for non-VSAM direct access
   data sets, tape data sets, VIO data sets defined by DD
   statements, or dynamically allocated and opened for RDBACK
   or INPUT processing. The SMF 15 record is created for
   non-VSAM data sets when they are opened for OUTPUT, UPDAT,
   INOUT, or OUTIN processing.

   The SMF 17 record is created when a non-temporary or
   temporary non-VSAM data set is scratched. The SMF 18
   record is created when a non-VSAM data set defined by a DD
   statement is either explicitly or implicitly renamed.
   CA MICS creates one observation for each SMF record
   processed.

B. Data Volume Issue for SMF Record Type 14

   Be selective in your data collection for OPEN actions
   performed on your data sets. The data volume is very high
   for this record type. Remember, a record is created for
   every non-VSAM data set that is opened for OUTPUT, UPDAT,
   INOUT, or OUTIN processing.

C. Concatenated Sequential data sets

   Records created for this type of data set will contain
   only the DDNAME for the first data set in the
   concatenation. All other data set DDNAMEs in the
   concatenation will be blank.

D. EXCP Counts

   Use caution when relying on the EXCP counts from the SMF
   14 and 15 records, because they may be invalid. The EXCP
   counts will only be valid if there is one occurrence of
   the DDNAME in the entire job. When there are multiple
   occurrences of the DDNAME within the job, the EXCP counts
   are accumulated across multiple opens within the same
   step.  Due to this accumulation, EXCP counts are invalid.

E. Multiple Volume data sets

   With SMF record types 17 and 18 representing the DELETE
   and RENAME data set actions, there is a recurring section
   in the record for data sets spanning multiple volumes.
   CA MICS StorageMate will store up to five volume serial
   numbers in elements VOLUME01 through VOLUME05. Element
   VOLSER will be set to the first volume (VOLUME01).

F. Concatenated BPAM data sets

   If no member name is provided in the JCL for a PDS data
   set, the access method is BPAM. If this is the access
   method for the data set then only one 14 or 15 SMF record
   is generated. The record will contain only the DSNAME of
   the first data set in the concatenation.  Although the
   record contains a UCB for each concatenation CA MICS
   StorageMate will create one observation for the entire
   record.

G. ISAM data sets

   The ISAM sections of SMF record types 14 and 15 are not
   processed.