7. PARAMETERS › 7.1 TLM Component Parameters › 7.1.2 TLM Component Complex Level Parameters › 7.1.2.1 Account Code Structure (TLMACCT)

7.1.2.1 Account Code Structure (TLMACCT)

Nine levels of account codes are provided to associate users,
user groups, or any other groups with tape data set and tape
volume ownership. The account codes are used as summarization
keys in the following CA MICS files:

TMCTMD - Tape Management Data Sets
TMCTMV - Tape Management Volumes

To define TLM component account codes, you must modify the
sample member sharedprefix.MICS.PARMS(TLMACCT).  TLMACCT
defines the number of account codes that are to be carried in
the above files, and the length and the label associated with
each account code.  Its definitions apply to these files in
all database units that contain TLM components.

PREPARATION
-----------
Each site determines its own method of associating tape data
set allocations and tape volumes with the responsible users,
projects, or departments.  Before defining TLM component
account codes, investigate your site's accounting standards
to:

o  Identify the current organizational coding system.  For
   example, your standards may require that billable entities
   are identified by:

   - Division
   - Department
   - Project
   - User

   With these requirements, at least four of your nine
   available TLMACTn account codes would be defined to hold
   these values.


o  Determine how account codes will be assigned:

   - For the Tape Management Volumes file, you can use ranges
     of tape volume serial numbers to assign specific
     ownership or overhead account code values.

   - For the Tape Management Data Sets file, the data set
     name qualifiers (nodes) or the job name of the creating
     job are often used to assign account codes.

Consider the following suggestions to determine the number of
account codes you will need to meet your site's reporting and
analysis needs:

o  Account codes are part of the summarization keys for the
   files that support them.  One record is generated for each
   unique combination of values of the summarization keys.

o  It is a good idea to define all nine account codes even if
   you currently need fewer.  If future requirements call for
   additional account codes, they are already defined.

DEFINING ACCOUNT CODES
----------------------
You can define up to nine levels of account codes.  For the
TLM component, the account codes are named TLMACT1 to
TLMACT9.

The TLMACCT member in sharedprefix.MICS.PARMS contains one
statement per account code definition.  Each statement
contains several parameters, which are free-form (separated
by one or more blanks) but positional.  Blank statements are
not permitted.  Comments can be coded by beginning the
statement with an asterisk (*).

The statement format is:

level  length  'descriptive title'

       or

level  mask  length 'descriptive title'

where:

level        The hierarchical level of the account code,
             where level 1 represents the top of the
             hierarchy, and the largest number (for example,
             level 9) represents the most granular level of
             organizational identity.  The levels are defined
             sequentially, starting with 1 and going up to 9.
             This parameter is required.

mask         An optional parameter that can be used to
             deactivate the account code in specified
             timespans.  Specifying a timespan mask requires
             coding T(......) as the second parameter in a
             statement, where each "." represents a file
             timespan in this order: DETAIL, DAYS, WEEKS,
             MONTHS, YEARS, and TABLES.  For each timespan,
             you can specify a Y to indicate that the account
             code is active or an N to indicate that the
             account code is inactive.

             If this parameter is skipped, it has a default
             value of T(YYYYYY).

             The following rules apply if you code the mask:

             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 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 is inactive in the MONTHS
                timespan, it cannot be active in the YEARS
                timespan.

length       The length of the account code.  The length may
             range from 1 to 30.  This parameter is required.

descriptive  The title that describes the account code.  The
title        length of the title is 1 to 40 characters.  The
             title is embedded in quotes (').  This is a
             required parameter.

The following two examples show how all nine account codes
can be coded to allow for future expansion with minimal
impact on database space utilization.  In both examples, the
six currently unused account codes use only six bytes of
space per database observation, but make it much easier to
implement additional account codes if required in the future.

Examples:

This sample TLMACCT has three used and six unused account
codes:

1 3 'DIVISION'
2 6 'DEPARTMENT'
3 8 'USER'
4 1 'UNUSED TLMACT4'
5 1 'UNUSED TLMACT5'
6 1 'UNUSED TLMACT6'
7 1 'UNUSED TLMACT7'
8 1 'UNUSED TLMACT8'
9 1 'UNUSED TLMACT9'

This sample TLMACCT with timespan controls has three used and
six unused account codes:

1            3 'DIVISION'
2 T(YYYNNN)  6 'DEPARTMENT'
3 T(YYYNNN)  8 'USER'
4 T(YYYYYY)  1 'UNUSED TLMACT4'
5 T(YYYYYY)  1 'UNUSED TLMACT5'
6 T(YYYYYY)  1 'UNUSED TLMACT6'
7 T(YYYYYY)  1 'UNUSED TLMACT7'
8 T(YYYYYY)  1 'UNUSED TLMACT8'
9 T(YYYYYY)  1 'UNUSED TLMACT9'