The Interface to CA Datacom/DB › Creating the Summary File › Creating a User Accounting Table

Creating a User Accounting Table

The Interface Translate Component creates CA JARS summary records from the Accounting Table. One item in this translation is the assignment of a cost center identification to each record.

For transaction activity, the Translate Component examines the two identifiers

• job name
• operator ID

and searches the table sequentially from beginning to end. The table is not sorted before the search. The user accounting information contained in the first entry that matches the Accounting Table record fields is inserted into the summary record. Any identifier that is omitted is considered a match. An asterisk can be used as a wild-card character.

Example

Suppose a table record has the following values for the identifiers:

      Job Name          Operator

      BAGJA01           JLB

All of the following identifiers for User Accounting Table entries produce a match.

      Job Name         Operator

      BAGJA01T         JLB
      blank            J*
      *******T         blank
      blank            JLB
      B*******         blank

Because the table is searched sequentially from top to bottom, the order of inclusion is significant. Although all the previous examples met the criteria, if all of them had been included in a single table, only the first one would be used to assign the cost center identification. The use of the asterisk as a wild-card character is illustrated by this example.

The User Accounting Table is built by assembling a set of macro instructions. You must follow the rules for coding Assembler Language macro statements when coding the table. During assembly, 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.