10. MODIFICATION › 10.2 User Exits › 10.2.2 Parameter-Related Exits
10.2.2 Parameter-Related Exits
This section identifies the CICS parameter-related exits that
you define at product installation time. Detailed
descriptions of these exits are presented in Chapter 7 of
this guide.
+---------------+
| C I C A C R T | CICS Account Code Derivation Exit
+---------------+
DESCRIPTION: The CICACRT exit derives the value of the
account code elements defined in
sharedprefix.MICS.PARMS(CICACCT). It is a complex-level exit
(it resides in the same library as CICACCT) and its
definition applies to all data base units in which the CICS
Analyzer is installed.
INVOCATION: The CICACRT exit gains control during the input
format routine of the daily update process step DAY040.
It is invoked once for each detail transaction record
processed by the CICS Analyzer.
ACCOUNTING INTERFACE: No interface is provided.
USES: This exit sets the value of the CICACTx variables.
ELEMENTS AVAILABLE: All DETAIL timespan elements of the
files are available.
CODING RESTRICTIONS: Refer to Section 7.2.3 of this guide.
SPECIAL NOTES: The exit code is contained in
prefix.MICS.PARMS(CICACRT).
SAMPLE USER EXIT: See Section 7.2.3 for a sample exit.
+---------------+
| C I C A U R T | CICS Application Unit Definition
+---------------+
DESCRIPTION: The CICAURT exit derives the value of the CICS
Application Unit ID (CICAPU).
INVOCATION: The CICAURT exit gains control during the input
format routine of the daily update process step DAY040.
It is invoked once for each detail transaction record
processed by the CICS Analyzer.
ACCOUNTING INTERFACE: No interface is provided.
USES: This exit sets the value of the CICAPU data element.
ELEMENTS AVAILABLE: All DETAIL timespan elements of the
files are available.
CODING RESTRICTIONS: Refer to Section 7.3.5 (CICAPU) of this
guide.
SPECIAL NOTES: The exit code is contained in
prefix.MICS.PARMS(CICAURT).
SAMPLE USER EXIT: See Section 7.3.6 (CICAURT) for a sample
exit.
+---------------+
| C I C R L R T | CICS Relative Longevity Derivation Routine
+---------------+
DESCRIPTION: The CICRLRT exit derives the data element
TRANTYPE to identify the transaction type.
INVOCATION: The CICRLRT exit gains control during the input
format routine of the daily update process step DAY040.
It is invoked once for each detail transaction record
processed by the CICS Analyzer.
ACCOUNTING INTERFACE: No interface is provided.
USES: This exit sets the value of the TRANTYPE data element.
ELEMENTS AVAILABLE: All DETAIL timespan elements of the
files are available.
CODING RESTRICTIONS: Refer to Section 7.3.7 of this guide.
SPECIAL NOTES: The exit code is contained in
prefix.MICS.PARMS(CICRLRT).
SAMPLE USER EXIT: See Section 7.3.7 for a sample exit.
+---------------+
| C I C M S A C | CICS Multisystem Account Derivation Exit
+---------------+
DESCRIPTION: The CICMSAC exit allows you to override the
account code values after they are derived in the input
processing step. It is used to identify transactions that
have been routed to other CICS regions for processing in an
MRO or ISC environment.
INVOCATION: The CICMSAC exit is invoked after the input
processing has completed and the detail transaction work
files have been created in DAY040. It is invoked when you
specify the MSACCOUNT keyword in prefix.MICS.PARMS(CICOPS).
ACCOUNTING INTERFACE: No interface is provided.
USES: This exit sets the value of the CICACTx variables.
ELEMENTS AVAILABLE: All DETAIL timespan elements of the file
are available.
CODING RESTRICTIONS: Refer to Section 7.3.9 of this guide.
SPECIAL NOTES: The exit code is contained in
prefix.MICS.PARMS(CICMSAC).
SAMPLE USER EXIT: See Section 7.3.9 for a sample exit.