7. PARAMETERS › 7.2 Complex-level Parameters › 7.2.2 Account Code Definition (SNTACCT)
7.2.2 Account Code Definition (SNTACCT)
This section explains how to define the CA MICS Network
Analyzer Option account code structure. These definitions
apply to every unit database in the database complex.
In CA MICS, data is stored by account number in the following
files:
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 listed above accept data from NetView Session
Monitor/NLDM and from CA NetMaster Network Management NTS.
The parameters that you specify in
sharedprefix.MICS.PARMS(SNTACCT) define the number of
accounting fields that will be carried in these files, the
length of each field, and the descriptive names that are
associated with each field. Note that once you have defined
these fields, you must provide a routine that assigns them
values (the SNTACRT member).
First you must determine what your accounting structure will
be; then decide how you want it expressed in the database.
You can choose to use a different account structure for each
file.
Once you design your accounting structure, you must determine
the number of accounting fields you will need (CA MICS
supports from 1 to 9) and what data will be placed in them.
Because the accounting fields are part of the sort sequence,
there will be at least one record for each unique combination
of values. You must decide between keeping a fine level of
granularity via the accounting fields and, therefore, having
a large database, or keeping a coarser level of granularity,
but perhaps not meeting your reporting or analysis
requirements.
While you may assign different values to the accounting
fields for each file, the number of accounting fields is not
variable and, therefore, must be large enough to accommodate
both. In addition, we recommend that you establish an
additional accounting field for future expansion. Thus, if
you determine the need for accounting fields 1-4, add
SNTACT5.
Three commonly-used choices for setting this account code
structure are:
1 - Organization by virtual route
Each record in a summarized timespan represents the
activity and response time for a unique combination of
PLU, virtual route, transmission priority, and explicit
routes (one inbound and one outbound) during the
recording interval. This file organization is useful
for virtual route planning.
A sample account code structure for this arrangement is
shown below:
SNTPSU File
-----------------------
SNTACT1 - PLU
SNTACT2 - SLUSAPU
SNTACT3 - VR
SNTACT4 - TP
SNTACT5 - Inbound ER
SNTACT6 - Outbound ER
SNTNSS File
-----------
SNTACT1 - PLU
SNTACT2 - NSSTSA (the terminal subarea number)
SNTACT3 - NSSVRRTE
NVSNSA, NVSNSC, NVSRTE, NVSRTM Files
------------------------------------
SNTACT1 - PLU
SNTACT2 - SLUSAPU
SNTACT3 - VR
SNTACT4 - TP
SNTACT5 - Inbound ER
SNTACT6 - Outbound ER
Note: This structure is the same as that described for
the SNTPSU file above.
Virtual route numbers are not unique within a network
and must be identified by their end-point nodes, PLUSAPU
and SLUSAPU, and transmission priority. PLUSAPU is not
included in the account code structure shown above
because all CA MICS Network Analyzer Option files have
SYSID as a fixed key, which usually corresponds to the
PLUSAPU. An exception is an application-to-application
session, in which case SYSID corresponds to the SLUSAPU
in the host containing the SLU, and it corresponds to
the PLUSAPU in the host containing the PLU.
2 - Organization by Cluster Controller
Each record in a summarized timespan represents the
activity and response time for a controller during the
recording interval. A sample account code structure for
arrangement by cluster controller is shown below:
SNTPSU File
(NPM)
-----------------------
SNTACT1 - PLUSAPU
SNTACT2 - PLU
SNTACT3 - SLULINK
SNTACT4 - SLUPU
Note: This organization is not recommended for the NPM
SNTPSU file, because it is redundant with the fixed key
structure of the NPM Link Activity File, SNTNPL.
SNTNAC File SNTNAC File
(CA NetSpy) (NPM)
----------------------- -----------------------
SNTACT1 - PLUSA SNTACT1 - PLUSAPU
SNTACT2 - PLU SNTACT2 - PLU
SNTACT3 - SLULINK SNTACT3 - SLULINK
SNTACT4 - SLUPU SNTACT4 - SLUPU
SNTNSS File
-----------
SNTACT1 - PLU
SNTACT2 - NSSTSA (the terminal subarea number)
SNTACT3 - SLULINK
SNTACT4 - SLUPU
NVSNSA, NVSNSC, NVSRTE, NVSRTM Files
------------------------------------
SNTACT1 - PLUSAPU
SNTACT2 - PLU
SNTACT3 - SLULINK
SNTACT4 - SLUPU
3 - Organization by Terminal
Each record in a summarized timespan represents the
activity and response time for a terminal during the
recording interval. A sample account code structure for
this arrangement is shown below:
SNTPSU File
-----------------------
SNTACT1 - PLUSAPU
SNTACT2 - PLU
SNTACT3 - SLUNETID
SNTACT4 - SLUPU
SNTACT5 - SLUSAPU
SNTACT6 - SLU
SNTNAC File SNTNAC File
(CA NetSpy) (NPM)
----------------------- -----------------------
SNTACT1 - PLUSA SNTACT1 - PLUSAPU
SNTACT2 - PLU SNTACT2 - PLU
SNTACT3 - SLUNETID SNTACT3 - SLUNETID
SNTACT4 - SLUPU SNTACT4 - SLUPU
SNTACT5 - SLUSA SNTACT5 - SLUSAPU
SNTACT6 - SLU SNTACT6 - SLU
SNTNSS File
-----------
SNTACT1 - PLU
SNTACT2 - NSSTSA (the terminal subarea number)
SNTACT3 - SLUPU
SNTACT4 - SLU
NVSNSA, NVSNSC, NVSRTE, NVSRTM Files
------------------------------------
SNTACT1 - PLUSAPU
SNTACT2 - PLU
SNTACT3 - SLUPU
SNTACT4 - SLUSAPU
SNTACT5 - SLU
You may establish a different account code structure for NPM,
CA NetSpy, NetView, or CA NetMaster. See Section 7.2, Account
Code Exit Routine Definition (SNTACRT), for specific
information.
CA MICS Network Analyzer Option accounting fields have names
in the form SNTACTn, where n is the sequential number of the
accounting field. If three fields are defined, they will be
SNTACT1, SNTACT2, and SNTACT3. In your accounting structure,
these might identify primary logical unit (application), link
(line), and physical unit (3274 cluster controller),
respectively. The sequential number is called the
account-code level number. There is a maximum of nine
levels. A sample account code structure is provided in
sharedprefix.MICS.HOLD.PARMS(SNTACCT).
Coding the Account Code Parameter
---------------------------------
The format of the statement is:
level (mask) length description
where:
level The sort sequence designation of the account
code. Up to nine levels may be specified.
Level 1 is the highest level and level 9 is the
lowest in sort order.
(mask) An option for deactivating account code levels
in the DAYS, WEEKS, MONTHS, and YEARS
timespans. For example, the DETAIL timespan
may use account code levels 1, 2, and 3, while
the MONTHS timespan may use only level 1.
Setting account code levels by timespan is
accomplished by specifying this additional
parameter on the account code statements, using
values Y or N to specify whether or not the
account code is active.
length The field length of the specified element.
Valid lengths range from 1 to 30.
description The title that describes the account code
level. Valid descriptions range from 1 to 40
characters.
Use the worksheet in Figure 7-1 to collect the information
for coding into sharedprefix.MICS.PARMS(SNTACCT). Observe
the following conventions when coding:
o Blank statements are permitted. Comments are coded by
beginning the statement with an asterisk (*).
o Account levels must be specified in ascending order,
starting with 1. You can specify up to nine account
levels, with no gaps between the numbers.
o The statements are free-form but positional.
Additional Notes on Specifying the TimeSpan Mask Option
--------------------------------------------------------
The timespan mask option is used to deactivate the account
code in specified timespans. Specifying a timespan mask
requires coding the account code statement using the
timespan mask parameter T(......), as follows:
level T(......) length 'descriptive title'
This example shows the placement and syntax of the timespan
mask on the account code statement. Each "." position in the
parentheses represents a timespan in the following order:
DETAIL, DAYS, WEEKS, MONTHS, YEARS, and TABLES. For each
timespan, a Y indicates that the account level should be
active and an N indicates that the account level should be
inactive.
This parameter is optional. If it is not coded, the assumed
value is T(YYYYYY).
The following rules apply if you code this parameter:
o DETAIL must always be Y. Account codes may not be
deactivated in this timespan.
o If DAYS is N, then WEEKS, MONTHS, and YEARS must also be
N. If the account code level is inactive in the DAYS
timespan, it cannot be active in higher timespans.
o If MONTHS is N, then YEARS must be N. If the account code
level is inactive in the MONTHS timespan, it cannot be
active in the YEARS timespan.
Example
-------
A sample SNTACCT member is illustrated below:
* SAMPLE NETWORK ACCOUNTING ROUTINE
1 8 'PRIMARY LOGICAL UNIT (PLU)'
2 8 'SLUSAPU NETV/NPM1.3, SLUSA NPM1.2 OR NSPY'
3 8 'SLUPU IF NLDM OR NETSPY, SLU IF NPM'
4 8 'PERFCLSS IF NLDM, NPM BLANK, NSPY SLU'
5 8 'NOT USED'
As you plan for the definition of the CA MICS Network
Analyzer Option accounting fields at your data center, be
aware that some of the standard reports provided with the
product depend on a particular definition of these account
codes. Specifically, the SNT113 report assumes that the
SNTACT3 element is set to the value of the SLUPU data element
for network data from either NetView or CA NetMaster.
Similarly, the SNT115 report assumes that the SNTACT4 element
is set to the value of the PERFCLSS data element for network
data from either NetView or CA NetMaster. These are the
default settings that were defined when the product was
shipped to you.
+--------------------------------------------------------------------------+
| INSTALLATION PREPARATION WORKSHEET: Network Account Code Definition |
| PARMS Library Member is SNTACCT |
| Reference: Section 7.2.2, CA MICS Network Analyzer Option Guide |
+--------------------------------------------------------------------------+
| |
| ACCOUNT TIMESPAN FIELD |
| CODE LEVEL MASK- LENGTH DESCRIPTION |
| (1-9) optional |
| |
| _ T(______) ___ '________________________________________' |
| |
| _ T(______) ___ '________________________________________' |
| |
| _ T(______) ___ '________________________________________' |
| |
| _ T(______) ___ '________________________________________' |
| |
| _ T(______) ___ '________________________________________' |
| |
| _ T(______) ___ '________________________________________' |
| |
| _ T(______) ___ '________________________________________' |
| |
| _ T(______) ___ '________________________________________' |
| |
| _ T(______) ___ '________________________________________' |
| |
| |
| |
| |
| |
+--------------------------------------------------------------------------+
| ....5...10...15...20...25...30...35...40...45...50...55...60...65...70.. |
+--------------------------------------------------------------------------+
Figure 7-1. Network Analyzer Account Code Level Definition Worksheet
Copyright © 2014 CA.
All rights reserved.
|
|