z/OS Batch Identification Codes

Usage and Accounting Collector can use the following fields as KEY FIELDS and MOVE FIELDS for table lookup purposes. In addition, Usage and Accounting Collector can use sub-strings of the following fields:

JOB NAME ACCOUNT CODE PROGRAMMER NAME
SECURITY CODES SYSTEM ID WORK ID
TSO USER ID Etc.1  

1 Usage and Accounting Collector supports the entire SMF record type 30. Multiple techniques are available to support any field contained in the record for table lookup purposes. If you need a field other than those listed above, contact IBM to discuss your options.

Program DRLCACCT provides powerful Account Code conversion features to translate combinations of the above z/OS identifiers into meaningful Account Codes. Without changing your JCL or logon procedures, DRLCACCT can place a customized Account Code into each Usage and Accounting Collector record.

To implement this feature

  1. Design an Account Code that meets your reporting requirements.
  2. Determine the identifiers that are required to build the Account Code. (For example, User-ID might be used to determine the Cost Center or Department Code, and certain positions of the Job Name might be used to determine the Application Code.)
  3. Use the DEFINE FIELD and DEFINE MOVEFLD control statements to specify the identification codes that are necessary to build the Account Code that you designed in Step One. (Account Code Character String for field locations of the various identifiers.)
  4. Build an Account Code table that matches ID codes to your Account Code structure. You can either key this information into a PDS Member or create the information dynamically. It is important that the main source of the table information is maintained in only one place. For this reason, many organizations build Account Code conversion tables dynamically from information contained in Human Resource files, Security tables, and other data sources.
  5. Process DRLCACCT, DRLCEXTR, DRLCMONY, etc.