7. PARAMETERS › 7.2 Complex-level Parameters › 7.2.3 Account Code Exit Routine Definition (SNTACRT)
7.2.3 Account Code Exit Routine Definition (SNTACRT)
This section explains how to code an account code exit for
the CA MICS Network Analyzer. These definitions will be used
for every database unit that contains this analyzer.
A network account code exit routine is a user-written routine
that is invoked for each input record processed. This SAS
routine builds the account code data elements defined in the
previous section. For example, if
sharedprefix.MICS.PARMS(SNTACCT) defines four account code
levels, this user routine builds the data values of those
four fields for each record processed.
The object of the account code exit routine definition
process is to build the data elements SNTACT1 to SNTACT9 (as
many as have been defined in SNTACCT) from the data made
available in the DETAIL timespan files. You should follow
the exit coding guidelines given in Section 2.3.1.5, Notes on
Coding CA MICS Parameters, in the PIOM.
The user account code exit routine is written in SAS code.
The testing and accuracy of the process is your
responsibility. However, CA MICS provides a sample account
code exit routine and certain program aids to help verify the
accuracy of the user modifications to the routine. The
sample routine is contained in
sharedprefix.MICS.HOLD.PARMS(SNTACRT). The worksheet for
structuring the network account code exit routine is shown in
Figure 7-2.
The account code exit routine has been made available for
each of the data elements contained in each of the files for
which account fields may be set. The files are:
o NCP Network Accounting (SNTNAC) File
o CA NetSpy Terminal (SNTNSS) File
o NPM User Activity (SNTPSU) File
o NLDM Session Accounting (NVSNSA) File
o NLDM Session Connectivity (NVSNSC) File
o NLDM Response Time (NVSRTM) File
o NLDM Route (NVSRTE) File
The NLDM files accept data from NetView Session Monitor/NLDM
and CA NetMaster NTS.
Chapter 5 lists the elements available in each file.
Common elements that might be useful for account codes are:
PLU - The primary logical unit (application) name
SLULINK - The name of the link associated with a secondary
logical unit
SLUPU - The name of the SNA physical unit (cluster
controller) associated with the secondary logical
unit
SLU - The secondary logical unit (terminal) name
Additional elements that may be useful in the SNTPSU File
are:
For NPM
--------
PLUSAPU - The primary logical unit subarea physical unit
SLUSAPU - The secondary logical unit subarea physical unit
PLUNETID - The PLU network identifier
SLUNETID - The SLU network identifier
In the SNTNSS File, the NSSTSA data element contains the
terminal subarea number and can be useful for identifying
groups of users at a subarea level.
Elements that may be useful in the NVSNSA, NVSNSC, NVSRTE,
and NVSRTM Files are:
PLUSAPU - The primary logical unit subarea physical unit
SLUSAPU - The secondary logical unit subarea physical unit
The example below assumes that a data center defined five
account code levels in SNTACCT, and they are derived as
described below:
SNTACT1 - The host application name (primary logical unit)
SNTACT2 - If NLDM, CA NetMaster NTS, NPM, the primary
logical unit, subarea physical unit name
- If CA NetSpy, the primary logical unit subarea
name
SNTACT3 - If CA NetSpy, NLDM, or CA NetMaster NTS, the
secondary logical unit physical unit name
(cluster controller)
- If NPM, the secondary logical unit name
(terminal)
SNTACT4 - If NLDM or CA NetMaster NTS, the performance
class
- If NPM SNTPSU file, blank
- If CA NetSpy or SNTNAC file, the terminal ID
SNTACT5 - Blank for future expansion
The COMPT data element specified in the following example is
an eight-character product and data source identifier used as
a work element during CA MICS DAILY processing. The valid
values for this element are:
'SNT NPDA' - NetView (NPDA) or CA NetMaster NEWS SMF record
type 37
'SNT NPMN' - NPM Network data SMF record type 28
'SNT NPMS' - NPM Session data or Network Session Accounting
data SMF record type 28
'SNT NLDM' - NetView (NLDM) or CA NetMaster NTS SMF record
type 39
'SNT NSPY' - CA NetSpy user-defined SMF record type that
includes data from CA NetSpy VTAM Interface,
NCP Interface, and Network Session Accounting
'SNT TCP ' - IBM TCP/IP SMF record types 118 or 119
WARNING! In the example below, the variable FILEID is
used instead of COMPT to set account codes for the SNTNAC
file. This is the only file for which account codes may be
set based on the value of FILEID. Using FILEID to set
account codes for any file other than SNTNAC will cause the
SNTACRT exit routine to fail. FILEID was used to assign
account codes for the SNTNAC file, because both the SNTPSU
file and the SNTNAC file have the same COMPT value (NPMS),
and we wanted to set account code values differently for the
two files.
Assuming the sample SNTACCT routine described earlier, the
SAS code defined for the SNTACRT user account code exit would
be:
*EXAMPLE - SNT ACCOUNT CODE DERIVATION EXIT
* NOTE: THIS ROUTINE IS %INCLUDED MULTIPLE TIMES SO
* LABELS ARE NOT PERMITTED.
*
* IN THIS EXAMPLE, SNTACT1 = PLU
* SNTACT2 = SLUSAPU/SLUSA
* SNTACT3 = SLUPU/SLU
* SNTACT4 = PERFCLSS/'BLANKS'/SLU
* SNTACT5 = 'BLANKS'
;
* SET DEFAULT VALUES ;
SNTACT1 = 'OVERHEAD';
SNTACT2 = ' ';
SNTACT3 = ' ';
SNTACT4 = ' ';
SNTACT5 = ' ';
* CHECK INPUT DATA SOURCE AND SET ACCOUNT FIELDS ;
IF COMPT='SNT NLDM' THEN DO; /*NETVIEW, NETMASTER*/
SNTACT1 = PLU;
SNTACT2 = SLUSAPU;
SNTACT3 = SLUPU;
SNTACT4 = PERFCLSS;
SNTACT5 = ' ';
END;
IF COMPT='SNT NPMS' THEN DO; /* NPM*/
SNTACT1 = PLU;
IF NPMVRRL GE '0013' THEN SNTACT2 = SLUSAPU;
ELSE SNTACT2 = SLUSA;
SNTACT3 = SLU;
SNTACT4 = ' ';
SNTACT5 = ' ';
END;
IF COMPT='SNT NSPY' THEN DO; /*NETSPY*/
SNTACT1 = PLU;
SNTACT2 = NSSTSA; /* SAME AS SLUSA */
SNTACT3 = SLUPU;
SNTACT4 = SLU;
SNTACT5 = ' ';
END;
IF COMPT='SNT NPMS' AND FILEID='SNTNAC' THEN DO;
SNTACT1 = PLU;
SNTACT2 = SLUSAPU;
SNTACT3 = SLUPU;
SNTACT4 = SLU;
SNTACT5 = ' ';
END;
+--------------------------------------------------------------------------+
| DATA CENTER PREPARATION WORKSHEET: Network Account Code Exit |
| PARMS Library Member is SNTACRT |
| Reference Section: 7.2.3, CA MICS Network Analyzer Option |
+--------------------------------------------------------------------------+
| |
| * VALIDATE FOR VALID ACCOUNT CODES, WHERE POSSIBLE ; |
| |
| IF { account data is valid } THEN DO; |
| |
| * BUILD ACCOUNT CODE FIELDS AS IN THE WORKSHEET 7-1 |
| |
| SNTACT1=field source 1 ; |
| SNTACTn=field source n ; |
| ____________________________________________________________________ |
| ____________________________________________________________________ |
| ____________________________________________________________________ |
| ____________________________________________________________________ |
| ____________________________________________________________________ |
| ____________________________________________________________________ |
| ____________________________________________________________________ |
| |
| END; |
| ELSE DO; |
| |
| * ROUTINE TO BUILD INSTALLATION OVERHEAD ACCOUNT CODES ; |
| |
| SNTACT1='overhead category' ; |
| SNTACTn='overhead category' ; |
| ____________________________________________________________________ |
| ____________________________________________________________________ |
| ____________________________________________________________________ |
| ____________________________________________________________________ |
| ____________________________________________________________________ |
| ____________________________________________________________________ |
| |
| END; |
| |
+--------------------------------------------------------------------------+
| ....5...10...15...20...25...30...35...40...45...50...55...60...65...70.. |
+--------------------------------------------------------------------------+
Figure 7-2. Network Account Code Routine Definition Worksheet
Copyright © 2014 CA.
All rights reserved.
|
|