7. DEFINING PARAMETERS › 7.2 Complex Level Parameters › 7.2.1 Account Code Specification (TSOACCT)
7.2.1 Account Code Specification (TSOACCT)
Account code data elements, a part of the file's sort and
summarization key, have names of the form TSOACTx, where x is
1 through 9. If you activate the account code support, the
TSO Analyzer uses these TSOACTx elements to associate monitor
data with the responsible individual or group.
The following TSO Analyzer files support account codes:
o TSO User Activity File (TSOTSU)
o TSO User Command Counts File (TSOTSC)
o TSO User Interactive Usage File (TSOTSI)
o TSO Batch User Activity File (TSO_BU)
o TSO Batch User Command Counts File (TSO_BC)
o TSO Batch Command Information File (TSO_BI)
The account code parameter, sharedprefix.MICS.PARMS(TSOACCT),
defines how many account code fields are maintained in the
TSO Analyzer's files. (CA MICS supports from one through
nine account codes.) In addition to defining the number of
fields, the TSOACCT parameter defines the length of each
field and its contents.
The parameters specified in the TSOACCT member of the
sharedprefix.MICS.PARMS data set define the account field
structure. To assign values to the account fields, you need
to code an account code exit routine, TSOACRT, described in
Section 7.2.2.
Once you have defined the account codes and their derivation,
you need to activate them by setting an option in the
sharedprefix.MICS.GENLIB(TSOGENIN) member. Section 7.2.3
describes how to activate the account codes.
PREPARATION
Each installation has its own method for associating commands
and users with the projects or departments within the
organization. Before defining the account codes, you should
investigate your installation's accounting standards, in
order to:
o Identify the coding system (e.g., your cost center
coding system for identifying the division,
department, project and employee).
o Identify how the codes are specified. For example,
the division may be determined by part of the user ID.
o Identify if and how the codes are verified to ensure
that they correspond to a valid definition. We
recommend that you validate all account codes and
assign unidentified or invalid account codes to a
special installation overhead account code (see the
documentation of the TSOACRT exit). This approach
provides two benefits: it will filter out invalid
codes from inclusion in the data base and, therefore,
will require less DASD space for storing the data in
the TSO Information Area files; and you can easily see
how much of this unidentifiable activity is taking
place.
Consider the following in determining the number of account
fields required to meet your installation's reporting and
analysis needs:
o Account fields are part of the file keys for the files
that support them. As such, at least one record is
generated for each combination of values. (More than
one record may be generated because other fields also
make up the file keys.) A greater number of account
fields means that the data base will be larger than if
fewer account fields are defined, but reporting and
analysis can be performed in greater detail.
o If you anticipate needing to expand the account code
structure in the future, establish an extra account
code now to eliminate the need to retrofit the data
base later to add the new account code.
DEFINING THE TSO ACCOUNT CODE PARAMETER
Once prepared, code the contents of the worksheet in the data
set sharedprefix.MICS.PARMS(TSOACCT). 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.
SAMPLE TSOACCT MEMBER
The sample TSOACCT member is distributed to contain:
* SAMPLE ACCOUNT CODE SPECIFICATION
1 10 'DIVISION'
2 10 'USER'
This sample uses only two account codes: one for division,
the other for user. Each account code is ten bytes long.
SPECIFYING THE TIME-SPAN MASK OPTION
The time-span mask option is used to deactivate the account
code in specified time-spans. Specifying a time-span mask
requires coding the account code statement using the time-
span mask parameter T(......), as follows:
level T(......) length 'descriptive title'
This example shows the placement and syntax of the time-span
mask on the account code statement. Each "." position in the
T position represents a time-span, in the order: DETAIL,
DAYS, WEEKS, MONTHS, YEARS, and TABLES. For each time-span,
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 time-span.
o If DAYS is N, then WEEKS, MONTHS, and YEARS must also
be N. If the account code level is inactive in the
DAYS time-span, it cannot be active in higher
time-spans.
o If MONTHS is N, then YEARS must be N. If the account
code level is inactive in the MONTHS time-span, it
cannot be active in the YEARS time-span.
COLLECTING DATA TO SPECIFY ACCOUNT CODES
Use the worksheet in Figure 7-1 to organize the information
needed to code TSOACCT.
+--------------------------------------------------------------------------+
| INSTALLATION PREPARATION WORKSHEET: TSO Account Code Specification |
| PARMS Library Member is TSOACCT |
| Reference: Section 7.2.1 - CA MICS TSO Analyzer Guide |
+--------------------------------------------------------------------------+
| |
| ACCOUNT TIME SPAN FIELD |
| CODE LEVEL MASK LENGTH DESCRIPTION |
| (1-9) |
| |
| _ 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. TSO Account Code Specification Worksheet
where the fields are:
ACCOUNT the level of importance of the element. Level 1
CODE is the most important field, and level 9 is the
LEVEL least important.
TIME- account code levels can be deactivated in the
SPAN DAYS, WEEKS, MONTHS, and YEARS time-spans. For
MASK example, the DETAIL time-span may have account
code levels 1, 2, and 3, while the MONTHS
time-span has only level 1. Setting account
code levels by time-span is accomplished by
specifying this additional parameter on the
account code statements, as described below.
FIELD the length of the specified element. Valid
LENGTH lengths range from 1 to 30.
DESCRIPTION the title that describes the account code level.
Valid descriptions range from 1 to 40
characters.
