Previous Topic: 10.2.4.1 Output Processing Exits for VCANext Topic: 10.3 File and Data Element Customization


10.2.4.2 Output Processing Exits for HSM

                                                     Catalog Group ===> *
                                                     Inquiry Name  ===> _____
 
 Line Cmds: I Insert  D Delete  S Select  M Move  E Exec-Time  R Reset Parms
 
 Cmd    Name                  Title                        Exec-Time   Catalog
  -   --------  ----------------------------------------  -----------  --------
  _   RMFED1    MVS CPU and ASID Activity (.CSV)          *Specified*  SHARED
  _   RMFED1    MVS CPU and ASID Activity (.CSV)          *Specified*  SHARED
  _   RMFED5    MVS Top-4 CPU Busy Comparison (.CSV)                   SHARED
  _   RMFLPA    Post Processor CPU Activity Report                     SHARED
      CPUBSY    User Reporting CSV Extract                             PRIVATE
 ****************************** BOTTOM OF DATA  ********************************
 
 Scrolling RIGHT on an inquiry display shows the following:
 
 
 SCROLL LEFT TO RETURN TO INQUIRY INFO
 
 Line Cmds: I Insert  D Delete  S Select  M Move  E Exec-Time  R Reset Parms
 
 
     Inquiry
 Cmd   Name    Typ  Prim  2nd  STORCLAS DATACLAS MGMTCLAS
  -  --------  --- ----- ----- -------- -------- --------
      RMFED1   CYL 25    5
      RMFLPA
      RMFCPU   CYL 15    5
      PRTCPU   TRK 10    5
 ******************************** Bottom of data ********************************
 
 
 
 
 

The following exits use the indirect form of exit invocation.
For more information on how this is done, refer to Section
4.3.1.2 of the System Modification Guide.


+---------------+
| U S R S V O L | - Exit prior to output of DETAIL.HSMVOL
+---------------+

DESCRIPTION:  USRSVOL allows access to the data elements used
to build the records in the WORK.HSMVOL file. This file
describes the characteristics of DASD volumes before and
after daily HSM space management, including percentage
occupancy, target and trigger occupancy values, and excess
eligible data occupancy.

INVOCATION:  This exit gains control immediately prior to the
output of a record to the WORK.HSMVOL file.

USES:  This exit can be used to add or change data elements
being written to the WORK.HSMVOL file.

ELEMENTS AVAILABLE:  All the elements that are turned on in
HSMGENIN for the VOL file at the DETAIL timespan.

CODING RESTRICTIONS:  None


+---------------+
| U S R D V O L | - Exit prior to output of DAYS.HSMVOL
+---------------+

DESCRIPTION:  USRDVOL allows access to the data elements used
to build the records in the DAYS.HSMVOL file. This file
describes the characteristics of DASD volumes before and
after daily HSM space management, including percentage
occupancy, target and trigger occupancy values, and excess
eligible data occupancy.

INVOCATION:  This exit gains control immediately prior to the
output of a record to the DAYS.HSMVOL file.

USES:  This exit can be used to add or change data elements
being written to the DAYS.HSMVOL file.

ELEMENTS AVAILABLE:  All the elements that are turned on in
HSMGENIN for the VOL file at the DAYS timespan.

CODING RESTRICTIONS:  None


+---------------+
| U S R S B A C | - Exit prior to output of DETAIL.HSBBAC
+---------------+

DESCRIPTION:  USRSBAC allows access to the data elements used
to build the records in the DETAIL.HSBBAC file. This file
describes the SMS class attributes, number of backups, total
space and current status for the incremental backups
performed for data sets residing on primary DASD and under
DFHSM incremental backup control.

INVOCATION:  This exit gains control immediately prior to the
output of a record to the DETAIL.HSBBAC file.

USES:  This exit can be used to add or change data elements
being written to the DETAIL.HSBBAC file.

ELEMENTS AVAILABLE:  All the elements that are turned on in
HSMGENIN for the BAC file at the DETAIL timespan.


+---------------+
| U S R D B A C | - Exit prior to output of DAYS.HSBBAC
+---------------+

DESCRIPTION:  USRDBAC allows access to the data elements used
to build the records in the DAYS.HSBBAC file. This file
describes the SMS class attributes, number of backups, total
space and current status for the incremental backups
performed for data sets residing on primary DASD and under
DFHSM incremental backup control.

INVOCATION:  This exit gains control immediately prior to the
output of a record to the DAYS.HSBBAC file.

USES:  This exit can be used to add or change data elements
being written to the DAYS.HSBBAC file.

ELEMENTS AVAILABLE:  All the elements that are turned on in
HSMGENIN for the BAC file at the DAYS timespan.


+---------------+
| U S R S M I G | - Exit prior to output of DETAIL.HSMMIG
+---------------+

DESCRIPTION:  USRSMIG allows access to the data elements used
to build the records in the DETAIL.HSMMIG00 file. This file
describes the SMS class attributes, HSM level, space and
current status for each data set in the installation that has
been migrated from primary DASD.

INVOCATION:  This exit gains control immediately prior to the
output of a record to the DETAIL.HSMMIG00 file.

USES:  This exit can be used to add or change data elements
being written to the DETAIL.HSMMIG00 file.

ELEMENTS AVAILABLE:  All the elements that are turned on in
HSMGENIN for the MIG file at the DETAIL timespan.


+---------------+
| U S R D M I G | - Exit prior to output of DAYS.HSMMIG
+---------------+

DESCRIPTION:  USRDMIG allows access to the data elements used
to build the records in the DAYS.HSMMIG00 file. This file
describes the SMS class attributes, HSM level, space and
current status for each data set in the installation that has
been migrated from primary DASD.

INVOCATION:  This exit gains control immediately prior to the
output of a record to the DAYS.HSMMIG00 file.

USES:  This exit can be used to add or change data elements
being written to the DAYS.HSMMIG00 file.

ELEMENTS AVAILABLE:  All the elements that are turned on in
HSMGENIN for the MIG file at the DAYS timespan.


+---------------+
| U S R S T A P | - Exit prior to output of DETAIL.HSMTAP
+---------------+

DESCRIPTION:  USRSTAP allows access to the data elements used
to build the records in the DETAIL.HSMTAP file. This file
describes the tapes under control of DFHSM for incremental
backup, full volume backup, and HSM Level 2.

INVOCATION:  This exit gains control immediately prior to the
output of a record to the DETAIL.HSMTAP file.

USES:  This exit can be used to add or change data elements
being written to the DETAIL.HSMTAP file.

ELEMENTS AVAILABLE:  All the elements that are turned on in
HSMGENIN for the TAP file at the DETAIL timespan.


+---------------+
| U S R D T A P | - Exit prior to output of DAYS.HSMTAP
+---------------+

DESCRIPTION:  USRDTAP allows access to the data elements used
to build the records in the DAYS.HSMTAP file. This file
describes the tapes under control of DFHSM for incremental
backup, full volume backup, and HSM Level 2.

INVOCATION:  This exit gains control immediately prior to the
output of a record to the DAYS.HSMTAP file.

USES:  This exit can be used to add or change data elements
being written to the DAYS.HSMTAP file.

ELEMENTS AVAILABLE:  All the elements that are turned on in
HSMGENIN for the TAP file at the DAYS timespan.



+---------------+
| U S R H S E G | - User Segment Processing Exit
+---------------+

DESCRIPTION:  USRHSEG is called when a user segment is
present in the VCCHSM data.

INVOCATION:  This exit is called if a user segment exists
else it is bypassed.

USES:  This exit is used to read the user segment and store
the information into user defined elements.

ELEMENTS AVAILABLE:  This should be determined by the
installation.

SPECIAL NOTES: When the USRHSEG exit is called, the pointer
in SAS is at the user segment. Therefore, it is not necessary
to calculate the offset of the user segment from the start of
the record. The logic that should be used to read the user
segment is as follows:

     INPUT  HSMUSRA1    $CHAR8. @;

(HSMUSRA1 is a user defined element)

Another feature that has been provided is the ability to
carry these user defined elements in the data step by the use
of the macro symbolic USRKEEP. Defining the user defined
elements in the USRKEEP list ensures that the elements are
available during the data step.  For example, the user
element HSMUSRA1 is defined to be in the keep list as
follows.

    %LET USRKEEP= HSMUSRA1;