

7. PARAMETERS › 7.2 Complex Level Parameters › 7.2.2 IMS Account Code Structure (IMSACCT)
7.2.2 IMS Account Code Structure (IMSACCT)
In CA MICS, data about IMS activity is stored by account
number(s) in the following files:
IMS User Activity File (IMSISU)
IMS User Activity File - EMH Non-BMC (IMS_IS)
MAINVIEW for IMS Online
IMS User Application Count File (IMSIAC)
The parameters you are asked to specify in
sharedprefix.MICS.PARMS(IMSACCT) define the number of
account code fields that will be carried in the files listed
above within the CA MICS IMS user database, the length of
each field, and the SAS long names that are associated with
each field. Note that once you have defined these
fields, you must provide a routine that assigns them values
(see Section 7.2.3).
PREPARATION
Each installation has its own method for associating the work
performed through IMS transactions with the projects or
departments within the organization that are responsible.
Prior to defining the account code parameters required by
CA MICS in this area, it is important to investigate your
installation's accounting standards, in order to:
o Identify the coding system (e.g. cost center coding
system identifying the division, department, project,
and employee).
o Identify how the codes are specified. For example, the
division and department may be determined by the first
character of the IMS terminal identifier and the project
from the first two characters of the IMS transaction ID.
o Identify if, and how, the codes are verified to ensure
that they correspond to a valid definition. We
recommend that account code validation be performed in
all cases, and that unidentified or invalid account
codes be assigned to a special installation overhead
account code (see Section 7.2.3). This approach
provides two benefits. It filters out invalid codes
from inclusion in the database and, therefore, requires
less DASD space to hold the data in the IMS Information
Area files. Also, it makes it easy to see how much of
this unidentifiable activity is taking place.
Once you have determined the accounting structure, consider
the following when determining the number of account fields
(CA MICS supports from 1 to 9) 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.) The trade-off you must make is
between keeping a fine level of detail via the account
code fields and, therefore, having a large database,
and keeping a small level of detail and perhaps not
meeting your reporting or analysis requirements.
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 database
later to add the new account code.
IMS account code fields have names in the form "IMSACTn",
where 'n' is the sequential number of the IMS account code
field. If three fields are defined, they will be IMSACT1,
IMSACT2, and IMSACT3 (in your accounting structure, these
might identify Division, Department, and Project,
respectively). The sequential number is called the account
code field "level" number. There are a maximum of nine (9)
levels. A Sample IMS Account Code structure is provided in
sharedprefix.MICS.PARMS(IMSACCT).
Figure 7-1 provides a worksheet for collecting the data.
Once you have completed this form, code the contents of
sharedprefix.MICS.PARMS(IMSACCT) as follows:
o A separate statement is coded for each account code
level.
o Blank statements are permitted. Comments are coded by
beginning the statement with an '*'.
o Account levels are provided in order, starting with "1".
o Up to nine levels are permitted, with no gaps between the
numbers permitted.
o The statement format is free-form, but positional. All
parameters are required. The form of each statement is
as follows:
n m 'SAS long name to be assigned to IMSACTn'
o The parameters to be coded are:
ACCOUNT LEVEL n
The level of importance of each element is specified
with Level 1 being the most important (major field)
and the highest level number being least important
(minor field). From 1 to 9 levels can be specified.
FIELD LENGTH m
The length of the specified element. The length may
be in the range from 1-30.
ACCOUNT CODE LEVEL DESCRIPTION
The title that describes the Account Code field.
The length of the title is limited to forty
characters.
A sample IMSACCT member is illustrated below:
1 4 'APPLICATION'
2 4 'DIVISION'
3 3 'OPERATOR'
+--------------------------------------------------------------------------+
| INSTALLATION PREPARATION WORKSHEET: IMS Account Code Level Definition |
| |
| PARMS Library Member is IMSACCT |
| Reference Sections: 7.2.2 |
+--------------------------------------------------------------------------+
| |
| ACCOUNT FIELD |
| CODE LEVEL LENGTH ACCOUNT CODE LEVEL DESCRIPTION |
| (1-9) |
| |
| _ __ '________________________________________' |
| |
| _ __ '________________________________________' |
| |
| _ __ '________________________________________' |
| |
| _ __ '________________________________________' |
| |
| _ __ '________________________________________' |
| |
| _ __ '________________________________________' |
| |
| _ __ '________________________________________' |
| |
| _ __ '________________________________________' |
| |
| _ __ '________________________________________' |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+--------------------------------------------------------------------------+
| ....5...10...15...20...25...30...35...40...45...50...55...60...65...70.. |
+--------------------------------------------------------------------------+
Figure 7-1. IMS Account Code Level Definition Worksheet
Copyright © 2014 CA.
All rights reserved.
 
|
|