Contents

The CA VM:Account/CA VM:Batch interface enables you to charge and report separately on CA VM:Batch and interactive resource usage. You can also charge users who run jobs on a remote system (even one on which their user IDs are not defined).

This interface can decrease the prime-time workload by charging users less for batch jobs that run during off hours than those that run during the peak operating periods.

Enable this interface if you have coded a CA VM:Batch account user exit that allows users to submit jobs to be charged to an account number that is not their default account number. The interface will ensure that these jobs will be charged to the account number specified when the job was submitted, rather than the user's default account number, even if the jobs use CA VM:Account PACKAGE or PROJECT accounting.

The interface also provides a solution to the loss of user ID/accounting information when performing an SQL function through CA VM:Batch. With the interface implemented and the CA VM:Account version of the SQL ARIUXIT in place, CA VM:Account will supply the correct user ID and account number to SQL to place in its accounting records.

How the Interface Works

  • CA VM:Batch sends CA VM:Account information describing the batch job, including the job number, job name, user ID, job class, priority, and account number to be charged.
  • CA VM:Account places this information in a table for later use.
  • CA VM:Account encodes a special 8-byte account number and sends this information to CA VM:Batch.
  • CA VM:Batch uses this encoded account number when setting the accounting information that will appear in the CP accounting records for the batch job.
  • When CA VM:Account receives the CP accounting records produced by the batch jobs, CA VM:Account uses the encoded account number to search the table during the costing process and uses the information in the table to supply the correct user ID, job name, job class, priority, and account number in the costed record.

If CA VM:Account is not available at the beginning of the batch job, CA VM:Batch sends a C0/H0 record describing the batch job to the CA VM:Account reader. CA VM:Batch then creates an encoded account number that contains binary zeros in the first six bytes and the hexadecimal batch job number in the remaining two bytes, and uses this account number when setting the accounting information that will appear in the CP accounting records for the job. CA VM:Account performs accounting for these records when the CA VM:Account service virtual machine becomes available, by reading the C0/H0 (Event) record first and using this information when costing the job records.

CA VM:Batch jobs produce C1 (session), C2 (dedicated device), and C3 (TDISK) records for processing by CA VM:Account.

Note: For more information about these accounting records, see the CA VM:Account System Administrator's Guide.

Restrictions and Requirements

Only one CA VM:Batch service virtual machine can be interfaced to CA VM:Account. If there are two or more CA VM:Batch systems interfaced with CA VM:Account, users may get charged for jobs they did not submit.

Implementation

  1. Log on to VMANAGER.
  2. Enter the CA VM:Batch CONFIGUR command.
  3. Make sure there is a PRODUCT VMACCOUNT VMACCT record in the VMBATCH CONFIG file. This configuration file record provides CA VM:Batch with the CA VM:Account service virtual machine user ID. This record activates the CA VM:Batch side of the interface.
  4. Make sure there is an ACCT option in the VMBATCH directory entry OPTION statement. This option allows CA VM:Batch to create accounting records.
  5. Log on to VMACCT.
  6. Enter the END command to shut down VMACCT.
  7. Make sure there is a PRODUCT VMBATCH VMBATCH record in the VMACCT CONFIG file. This configuration file record provides CA VM:Account with the CA VM:Batch service virtual machine user ID. This record activates the CA VM:Account side of the interface.
  8. Enter the PROFILE command to restart VMACCT.
  9. Enter the #CP DISCONN command to leave VMACCT running disconnected.
  10. Use the CA VM:Account full-screen UPDATE command to update the VMBATCH COSTABLE file.