9. PROCESSING › 9.2 Daily Update Processing Flow › 9.2.2 Information Area Processing

9.2.2 Information Area Processing

The modules DYDEXFM1, DYDEXFM2, and DYDEXFM3 in
sharedprefix.MICS.SOURCE drives the input for the VMS
MONITOR, VMS ACCOUNTING, and CA MICS DEXSUS data.  The actual
input processing code is contained in the DEXACT module in
sharedprefix.MICS.SOURCE for ACCOUNTING read-up, in the
DEXMON module in sharedprefix.MICS.SOURCE for MONITOR
read-up, and in the DEXSUSA module in
sharedprefix.MICS.SOURCE for DEXSUS read-up.  The history
file (CKPTDATA) is created from separate files created in the
read-up steps.

Physical structure:  these modules are constructed at compile
time by the macro %DEXINCL, which is generated into module
$DEXMSTR in prefix.MICS.USER.SOURCE by DEXPGEN.  %DEXINCL
contains the %INCLUDE for DEXACT, DEXACTB (process ACCOUNTING
data), DEXMON, DEXMONB (process MONITOR data), and DEXSUSA,
DEXSUSB, DEXSUSC (process CA MICS DEXSUS data) when these
data sources have been specified in prefix.MICS.PARMS member
DEXOPS.  When a data source has not been specified, a stub
module (DEXACTST, DEXMONST, DEXSUSST) is included to create
the 00 cycle files in DETAIL.  %DEXINCL also performs a save
function for the ADMIHL (CKPTDATA) file so that all input
recording can be seen by CKRTN4.

The CA MICS VAX/VMS Analyzer differentiates between VMS
versions' MONITOR records because record formats differ
between versions.

The various recent versions of VMS ACCOUNTING have the same
record format, with a minor change for VMS 6.1, indicated
by a special flag bit.

The CA MICS VAX/VMS Analyzer differentiates between versions
of CA MICS DEXSUS records, based on the VMS level and CA MICS
DEXSUS maintenance level reported by DEXSUS.


User Exits
----------

During this phase, the USRAfff Accounting Exits are invoked.
These exits are described further in section 9.3 "User
Exits."