The APPC application unit derivation routine is a user-
written routine that assigns a value to the Application Unit
Identifier ATPAPU discussed in Section 7.3.11. For example,
if the ATPAPU data element is to be constructed from four
different sources, this routine is responsible for building
the data value from those four fields for each transaction
processed.
Written in SAS, the routine is stored in
prefix.MICS.PARMS(APPCAURT). It is invoked for each SMF type
33 APPC/MVS TP Accounting record processed. A sample routine
is provided in member APPCAURT of the distributed version of
prefix.MICS.PARMS. You are responsible for ensuring the
accuracy of the exit, however. A worksheet for coding the
APPC/MVS Application Unit Derivation Routine is shown in
Figure 7-12.
The application unit derivation routine can use any of the
data elements contained in the APPC/MVS Transaction file
(BATATP). The data elements that are most often used to
determine the application unit value are shown below:
ATPCLASS - The class assigned in the APPC/MVS profile
data set for the TP. ASCH TP classes are
defined with response time goals expected by
the TPs assigned to the class.
ATPNAME - The TP name. This can be a confusing
candidate since programs requesting TPs may
use a symbolic name that is translated to the
true TP name from the APPC side information
file. Because of this, the TP name may not
be recognized by requesting user.
ATPTYPE - The TP type, reported by CA MICS as
'STP/MTP/MSH' for standard, multi-trans, or
multi-trans shell executions, respectively.
The application unit derivation process builds the data
element ATPAPU from the various values available from the SMF
type 33 APPC/MVS TP Accounting record.
CODING CONSIDERATIONS
Follow these guidelines for coding this CA MICS exit routine:
1. Validate input data where possible. When invalid codes
are encountered, they should be assigned to the
application code(s) representing the data center's
overhead accumulator.
NOTE: Allowing invalid or garbage application units into
the CA MICS database significantly increases the number
of records and therefore the DASD space requirements of
the Batch Information Area files.
2. Ensure that all of the fields that you require are
available for application unit construction.
3. Refer to the discussion of exit coding in Section
2.3.1.5, Notes on Coding CA MICS Parameters, in the PIOM.
A sample user application unit exit is shown below.
/* ****************************************************** */
/* APPC/MVS APPLICATION UNIT DERIVATION EXIT */
/* ****************************************************** */
/* ****************************************************** */
/* TP CLASS (ATPCLASS) IS USED TO DEFINE THE APPLICATION */
/* UNIT IDENTIFIER. IN ORDER TO SATISFY SERVICE LEVEL */
/* AGREEMENTS WITH THE VARIOUS BUSINESS UNITS, APPC/MVS */
/* TPS EXECUTED BY ALL USERS OF THE SYSTEM ARE DEFINED */
/* MULTIPLE TIMES WITH A TP CLASS UNIQUE TO EACH BUSINESS */
/* UNIT. THE STRUCTURE OF THE 8 BYTE TP CLASS DEFINITIONS*/
/* IS TO HAVE THE FIRST 2 CHARACTERS IDENTIFY THE */
/* BUSINESS UNIT ALLOWED TO RUN IN APPC INITIATORS OF THAT*/
/* CLASS, WHILE THE LAST 6 CHARACTERS ARE A GENERIC CLASS */
/* DEFINITION FOR THE TYPE OF TP SCHEDULED. FOR */
/* PERFORMANCE ANALYSIS PURPOSES, THE FIRST TWO CHARACTERS*/
/* ARE STRIPPED FROM TP CLASS BEFORE MOVING THE REMAINING */
/* 6 CHARACTERS TO THE ATPAPU APPLICATION UNIT ELEMENT */
/* ****************************************************** */
ATPAPU=SUBSTR(ATPCLASS,2,6) ;
IF ATPAPU EQ ' ' THEN ATPAPU='NONE' ;
AURTRTEX:
+--------------------------------------------------------------------------+ | INSTALLATION PREPARATION WORKSHEET: APPC/MVS Application Unit | | Derivation Routine Definition | | PARMS Library Member is APPCAURT | | Reference Section: 7.3.10 CA MICS Batch and Operations | | Analyzer Guide | +--------------------------------------------------------------------------+ | | | * VALIDATE FOR VALID APPLICATION UNITS, WHERE POSSIBLE ; | | IF application data is not valid assign overhead values ; | | ________________________________________________________________________ | | | | ________________________________________________________________________ | | | | ________________________________________________________________________ | | | | ________________________________________________________________________ | | | | ________________________________________________________________________ | | | | ________________________________________________________________________ | | | | * BUILD APPL. UNIT FIELDS; | | ATPAPU=field source 1 || | | field source n ; | | ________________________________________________________________________ | | | | ________________________________________________________________________ | | | | ________________________________________________________________________ | | | | ________________________________________________________________________ | | | | ________________________________________________________________________ | | GOTO AURTRTEX ; | | * LINKED ROUTINE TO BUILD INSTALLATION OVERHEAD APPLICATION UNITS; | | AURTOVHD: | | ATPAPU='overhead category' ; | | ________________________________________________________________________ | | | | ________________________________________________________________________ | | | | ________________________________________________________________________ | | AURTRTEX: | +--------------------------------------------------------------------------+ | ....5...10...15...20...25...30...35...40...45...50...55...60...65...70.. | +--------------------------------------------------------------------------+
Figure 7-12. APPC/MVS Application Unit Derivation Routine Worksheet
|
Copyright © 2014 CA.
All rights reserved.
|
|