How data is processed on the mainframe

Usage and Accounting Collector supports feeds from different platforms. To enable Usage and Accounting Collector to process these feeds, the data from the feeds must be formatted into the 79x accounting record layout. There is a separate layout for each 79x record type (791, 792, 793, and 799) defined in the Dictionary.

Each of the interface programs (DRLCACCT, DRLCDB2, DRLCCMF2, DRLCDISK, etc.) generates 79x records by default. The records are processed by DRLCEXTR, which creates input for DRLCMONY and/or IBM Tivoli Usage and Accounting Manager. The 79x records are fixed-column, mainframe-oriented records.

The Usage and Accounting Manager data collectors for UNIX and Windows builds CSR records. These are comma-delimited, distributed-oriented records.

To process CSR records on the mainframe, the records must be converted to 791 records. This conversion is done using a definition in the Dictionary. Usage and Accounting Collector also uses the definitions in the Dictionary to process the 79x records once they are converted.

Each feed type (i.e., CICS, Db2, tape, disk, etc.) has a separate record definition in the Dictionary. All definitions are members in DRL.SDRLCNTL and begin with DRLK (for example, DRLKCICS for CICS, DRLKDB2 for Db2, and DRLKTAPE for tape). To process a feed, the appropriate DRLKxxxx member must be loaded in the Dictionary.

The DRLKxxxx member is used to define identifiers and resources in the 791 records. There is also a common header, member DRLKHDR, which describes the common header fields. These fields are also included in the 791 record. Member DRLKHDR should not be updated.

To convert and process CSR records, you need to load a 791 dictionary definition for the records. In addition, you must create a 791 dictionary definition for any feed that does not have an existing DRLKxxxx member in DRL.SDRLCNTL. For the steps required to add a dictionary definition, Processing New Feeds.