9. PROCESSING › 9.5 Account Physical Structure

9.5 Account Physical Structure

The VM Account Data processing contains two logical sections,
the input raw data module (VMCACTFI) and the post-processing
module (VMCACTFU).

The input raw data section consists of two subsections.  The
first subsection sets up the files that will be created,
together with element lengths and formats, as well as
constant value (literal) and work element definitions.  This
is followed by %CKRTN1, which performs checkpoint validation;
%VMCLUPA, which calls the second subsection for data input;
and %CKRTN3 for end-of-input processing.

The second input raw data subsection begins at label ACTPROC
and continues to the end of the SAS data step.  This
subsection is called by %VMCLUPA for each system defined in
VMCOPS which provides VM Account data to CA MICS. The data
input processing is confined to a single loop which
terminates at end-of-file for each separate system.

The data input loop identifies the current input record, and
if the record is either a 'C0' (user format) or an
unrecognized type, %VMC0EXIT is called to allow installation
record identification as an RSCS record, or to cause %CKRTN2
processing to be executed (date range validation).  The
record is then passed to the appropriate routine for data
input.  Unrecognized records are passed to the %VMCUACC exit
for input.  (See Chapter 10 for a complete description of VM
and CMS Analyzer exits.)

The post-processing section contains one subsection per file
built from VM Account data.  These subsections provide any
extra file-specific processing, invoke exit VMCACRT, and
provide the standard interface with the CA MICS Installation
Accounting Product.

Additional processing for the VMCCMU File determines new
session start.

For the VMCDAC File, new device allocations are identified
and device typing is performed.  See Section 9.2.2 for
special notes about VMCDAC processing.

VMCVRA post-processing assigns a value to the element
VRASBSYS for the Installation Accounting Product and assigns
device type based on the virtual unit record device
identified in the input data.

VMCNTU post-processing performs no extra function, other than
interfacing to CA MICS Accounting and Chargeback.