10. MODIFICATION › 10.2 Standard User Exits › 10.2.4 Output Processing Exits › 10.2.4.1 Output Processing Exits for VCA
10.2.4.1 Output Processing Exits for VCA
The following exits use the direct form of exit invocation.
For more information on how to do this, please refer to
Section 4.3.1.1 of the System Modification Guide.
+---------------+
| U S R S D A A |- Exit Prior to Output of DETAIL.VCADAA File
+---------------+
DESCRIPTION: USRSDAA allows access to the data elements used
to build the records in the DETAIL.VCADAA file. This file
contains information from the VTOC that is collected by the
CA MICS Space Collector.
INVOCATION: This exit gains control immediately prior to the
output of a record to the DETAIL.VCADAA file.
USES: Use this exit to add or change data elements being
written to the DETAIL.VCADAA file. You can also use this exit
to set the value of the element DAACOST.
ELEMENTS AVAILABLE: All the elements that are turned on in
VCAGENIN for the DAA file at the DETAIL timespan.
CODING RESTRICTIONS: None
SPECIAL NOTES: If CA MICS Accounting and Chargeback is active
in the unit that contains the CA MICS Space Analyzer, DAACOST
will be set by Accounting and Chargeback.
+---------------+
| U S R U D A A | - Exit included in USRSDAA
+---------------+
DESCRIPTION: The USRSDAA exit routines calls this user exit.
Since it is called within the USRSDAA exit, it has access to
the same information that the USRSDAA has.
INVOCATION: The USRSDAA exit routine invokes this user exit.
USES: You can code this exit in the #VCAEXIT member of
prefix.MICS.USER.SOURCE instead of the USRSDAA exit. This
will allow the exit logic to be unit dependent thus allowing
greater flexibility.
ELEMENTS AVAILABLE: Same as the USRSDAA exit.
+---------------+
| U S R S _ V S |- Exit Prior to Output of DETAIL.VCA_VS File
+---------------+
DESCRIPTION: USRS_VS allows access to the data elements used
to build the records in the DETAIL.VCA_VS file. This file
contains VSAM data set information from catalogs read by the
CA MICS Space Collector.
INVOCATION: This exit gains control immediately prior to the
output of a record to the DETAIL.VCA_VS file.
USES: You can use this exit to add or change data elements
being written to the DETAIL.VCA_VS file. You can also use it
to set the value of the element DAACOST.
ELEMENTS AVAILABLE: All the elements that are turned on in
VCAGENIN for the _VS file at the DETAIL timespan.
SPECIAL NOTES: If CA MICS Accounting and Chargeback is active
in the unit that contains the CA MICS Space Analyzer, DAACOST
will be set by Accounting and Chargeback.
+---------------+
| U S R U _ V S | - Exit included in USRS_VS
+---------------+
DESCRIPTION: The USRS_VS exit routine calls this user exit.
Since it is called within the USRS_VS exit, it has access to
the same information that the USRS_VS has.
INVOCATION: The USRS_VS exit routine calls this user exit.
USES: This exit can be coded in the #VCAEXIT member of
prefix.MICS.USER.SOURCE instead of the USRS_VS exit. This
will allow the exit logic to be unit dependent thus allowing
greater flexibility.
ELEMENTS AVAILABLE: Same as the USRS_VS exit.
+---------------+
| U S R S V O A |- Exit Prior to Output of DETAIL.VCAVOA File
+---------------+
DESCRIPTION: USRSVOA allows access to the data elements used
to build the records in the DETAIL.VCAVOA file. This file
contains Volume information from VTOCs and catalogs read by
the CA MICS Space Collector.
INVOCATION: This exit gains control immediately prior to the
output of a record to the DETAIL.VCAVOA file.
USES: Use this exit to add or change data elements being
written to the DETAIL.VCAVOA file.
ELEMENTS AVAILABLE: All the elements that are turned on in
VCAGENIN for the VOA file at the DETAIL timespan.
+---------------+
| U S R U V O A | - Exit included in USRSVOA
+---------------+
DESCRIPTION: The USRSVOA exit routine calls this user exit.
Since it is called within the USRSVOA exit, it has access to
the same information that the USRSVOA has.
INVOCATION: The USRSVOA exit routine calls this user exit.
USES: This exit can be coded in the #VCAEXIT member of
prefix.MICS.USER.SOURCE instead of the USRSVOA exit. This
will allow the exit logic to be unit dependent thus allowing
greater flexibility.
ELEMENTS AVAILABLE: Same as the USRSVOA exit.
+---------------+
| U S R S D I R |- Exit Prior to Output of DETAIL.HFSDIR File
+---------------+
DESCRIPTION: USRSDIR allows access to the data elements used
to build the records in the DETAIL.HFSDIR file. This file
contains UNIX System Service's File System directory entries
that are read by the CA MICS USS file systems Collector.
INVOCATION: This exit gains control immediately prior to the
output of a record to the DETAIL.HFSDIR file.
USES: Use this exit to add or change data elements being
written to the DETAIL.HFSDIR file.
ELEMENTS AVAILABLE: All the elements that are turned on in
VCAGENIN for the DIR file at the DETAIL timespan.
+---------------+
| U S R U D I R | - Exit included in USRSDIR
+---------------+
DESCRIPTION: The USRSDIR exit routine calls this user exit.
Since it is called within the USRSDIR exit, it has access to
the same information that the USRSDIR has.
INVOCATION: The USRSDIR exit routine calls this user exit.
USES: This exit can be coded in the #VCAEXIT member of
prefix.MICS.USER.SOURCE instead of the USRSDIR exit. This
will allow the exit logic to be unit dependent thus allowing
greater flexibility.
ELEMENTS AVAILABLE: Same as the USRSDIR exit.
+---------------+
| U S R D D A A | - Exit prior to output of DAYS.VCADAA File
+---------------+
DESCRIPTION: USRDDAA allows access to the data elements used
to build the records in the DAYS.VCADAA file. This file
contains information from the VTOC that the CA MICS Space
Collector collects.
INVOCATION: This exit gains control immediately prior to the
output of a record to the DAYS.VCADAA file.
USES: Use this exit to add or change data elements being
written to the DAYS.VCADAA file. Note that the observations
being written have been summarized. You can use this exit to
set DAACOST if it is not being set at the DETAIL level.
ELEMENTS AVAILABLE: All the elements that are turned on in
VCAGENIN for the DAA file at the DAYS timespan.
CODING RESTRICTIONS: None
SPECIAL NOTES: If CA MICS Accounting and Chargeback is active
in the unit that contains the CA MICS Space Analyzer, DAACOST
will be set by Accounting and Chargeback.
+---------------+
| U S R D _ V S | - Exit prior to output of DAYS.VCA_VS File
+---------------+
DESCRIPTION: USRD_VS allows access to the data elements used
to build the records in the DAYS.VCA_VS file. This file
contains VSAM data set information from catalogs read by the
CA MICS Space Collector.
INVOCATION: This exit gains control immediately prior to the
output of a record to the DAYS.VCA_VS file.
USES: Use this exit to add or change data elements being
written to the DAYS.VCA_VS file. Note that the observations
being written have been summarized. You can use this exit to
set DAACOST if it is not being set at the DETAIL level.
ELEMENTS AVAILABLE: All the elements that are turned on in
VCAGENIN for the _VS file at the DAYS timespan.
SPECIAL NOTES: If CA MICS Accounting and Chargeback is active
in the unit that contains the CA MICS Space Analyzer, DAACOST
will be set by Accounting and Chargeback.
+---------------+
| U S R D V O A | - Exit prior to output of DAYS.VCAVOA File
+---------------+
DESCRIPTION: USRDVOA allows access to the data elements used
to build the records in the DAYS.VCAVOA file. This file
contains Volume information from VTOCs and catalogs read by
the CA MICS Space Collector.
INVOCATION: This exit gains control immediately prior to the
output of a record to the DETAIL.VCAVOA file.
USES: This exit can be used to add or change data elements
being written to the DETAIL.VCAVOA file.
ELEMENTS AVAILABLE: All the elements that are turned on in
VCAGENIN for the VOA file at the DAYS timespan.
+---------------+
| U S R D D I R | - Exit prior to output of DAYS.HFSDIR File
+---------------+
DESCRIPTION: USRDDIR allows access to the data elements used
to build the records in the DAYS.HFSDIR file. This file
contains Directory entry information that is collected by
USS File Systems Collector.
INVOCATION: This exit gains control immediately prior to the
output of a record to the DAYS.HFSDIR file.
USES: Use this exit to add or change data elements being
written to the DAYS.HFSDIR file.
ELEMENTS AVAILABLE: All the elements that are turned on in
VCAGENIN for the DIR file at the DAYS timespan.
+---------------+
| U S R D D C S | - Exit prior to output of DAYS.VCADCS File
+---------------+
DESCRIPTION: USRDDCS allows access to the data elements used
to build the records in the DAYS.VCADCS file. This file
contains Data Class information for sites that have SMS
implemented. This file is derived from the VCADAA file.
INVOCATION: This exit gains control immediately prior to the
output of a record to the DAYS.VCADCS file.
USES: Use this exit to add or change data elements being
written to the DAYS.VCADCS file.
ELEMENTS AVAILABLE: All the elements that are turned on in
VCAGENIN for the DCS file at the DAYS timespan.
+---------------+
| U S R U S E G | - User Segment Processing Exit
+---------------+
DESCRIPTION: USRUSEG is called when a user segment is
present in the records written by the CA MICS Space
Collector. The Space Collector creates the user segments
through the use of an exit called VCCUEXIT. This is provided
for sites that have certain site specific information in the
VTOC that is not read by the Space Collector. By coding the
VCCUEXIT, this information can be written as part of the
Space Collector records.
INVOCATION: This exit is called if a user segment exists
else it is bypassed.
USES: Use this exit 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 USRUSEG 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. Use this logic to read the user segment which is
as follows:
INPUT DAAXXXXX PIB2.
DAAYYYYY $CHAR3. @;
(DAAXXXXX and DAAYYYYY are user defined elements. In this
example there are 2 fields in the user segment).
Copyright © 2014 CA.
All rights reserved.
|
|