Setting up customer IDs
Because the IMS environment does not have batch accounting codes or any similar facility, a unique identifier must be created to associate jobs with specific customers.
This identifier is called the MainView for IMS Offline product customer ID. Both the IMS resource utilization file (IRUF) and the MainView for IMS Offline transaction accounting system are based on the customer ID field, which is used to associate all resource usage measurements and costs to a specific user.
The customer ID field is also used by the TASCOSTR program when it performs IRUF summarization.
- Transaction records are summarized by customer ID and transaction code.
- Terminal (LTERM) records are summarized by customer ID and LTERM name.
- Program records are summarized by program name.
The customer ID is an 18-byte alphanumeric field defined by the user. The field is included in the IRUF through a user exit routine (PRSCEXIT) during Log Edit processing .
The PRSCEXIT user exit routine (described in Customizing-user-exit-routines) is distributed with MainView for IMS Offline and has a customer ID default value of LTERM. Although this value can be modified by the user, it is recommended that the default LTERM or equivalent be retained as part of the customer ID . Retaining the default or equivalent ensures maximum efficiency during the IRUF summarization process.
Many of the identification fields available in IRUF records can be used to associate individual records with the right customer. The IRUF record identification fields that can be used to create the customer ID are listed below. Fields with an asterisk (*) are those that are used in MainView for IMS Offline reports.
AGN | PERFORMANCE GROUP |
ASID | PLINE* |
CLASS* | PROGRAM* |
CUSTOMER ID* | PROGRAM TYPE* |
FP ROUTE CODE* | PTERM* |
MVIMS SYSID* | REGION* |
IMSID | SMFID |
LTERM* | TRANCODE* |
MSC DESTINATION ID | USERID* |
MSC ORIGIN ID | VTAM NODE |
The customer ID should be structured in the same way as existing site budget and accounting codes. Ideally, the customer ID should be identical, or at least similar, to the accounting codes used in the site batch processing environment.
Related topic