The IMS Interface translates IMS data into Report Writer format and can assign a cost center identification to each record. This cost center identification is accomplished using a User Accounting Table. The IMS Interface scans the User Accounting Table for an entry whose transaction ID matches the data element value in the IMS log record.
The IMS Interface examines the transaction ID in each User Accounting Table entry, in order, from the beginning to the end of the table. The user accounting information from the first table entry found to match the record is inserted into the output record. If no match is found, the output user accounting information field contains blanks.
A blank (nonspecified) value for the transaction ID in a table entry is ignored for comparison, and therefore treated as a matching identifier. An asterisk (*) in any position of a table entry is treated as matching the corresponding position in the record identifier(s).
Example
Suppose an IMS log record has the following value for its transaction ID:
Transaction
ABCDEFGH
All of the following identifiers for User Accounting Table entries would match the basic record:
Transaction
ABCDEFGH
ABCDEFG*
ABCDEF**
ABC*****
***D****
(and so on)
Note: The user accounting information from the first User Accounting Table entry found to match the input record is used.
The User Accounting Table is built by assembling a set of JSIUA macro instructions. JSIUA macro instructions are written in Assembler Language. Follow the rules for coding Assembler Language macro statements when using the JSIUA macro. Object code is generated as the statements are processed.
If serious errors in the macro specification are detected, a message is issued and assembly continues even though the assembled module may not produce the intended results.
| Copyright © 2012 CA. All rights reserved. |
|