4. CUSTOMIZATION › 4.3 Specifying Rates › 4.3.1 Defining the Rate Table › 4.3.1.3 Defining a Journal File Exit

4.3.1.3 Defining a Journal File Exit

If you do not need journal file exit code, you can skip this
section.

Each journal file has an exit.  Control is passed to the exit
routine during algorithm generation, after all of the
generated calculations have been performed and just prior to
the output of each journal file record.  The exit is,
therefore, able to reference any values contained within the
journal file or the associated CA MICS file or read in from
the external file. Elements for CA MICS product files are
documented in the Data Dictionary appendix (usually Appendix
B) for that product.  Exits for external journal files not
based on a CA MICS file can reference any element read by the
external file input routine.  In addition, the exit can make
use of some data elements (such as ACTFLD1-5 in the CA MICS
Batch and Operations Analyzer SMF files) that are not written
to the database.

If you specified journal file prorating, all prorating are
calculations made after the journal file output exit is
taken.

To activate a journal file exit, code a SAS routine in the
prefix.MICS.USER.SOURCE data set in member ACTUJjj where jj
is the journal file identifier.

To do this, select Option 2, Journal File Exit, on the Rate
Table - File Options Menu, or edit the member directly with
ISPF edit.  Then submit prefix.MICS.CNTL(MAGRUN).

CAUTION:  If the ACTUJjj member exists in
          prefix.MICS.USER.SOURCE during MAGRUN, the exit
          will be taken.  You must delete the member and run
          MAGRUN to deactivate the exit.


CODING CONSIDERATIONS

In coding the journal file exit, observe the following
conventions:

o Reference any data elements contained within the journal
  file or the associated CA MICS file or read from the
  external file.

o Modify only the data elements contained within the journal
  file, the fffWCOST variable (where fff is the file ID of
  the associated CA MICS file), or the NONZERO variable.

o If the journal file record is to be written, set the
  NONZERO variable to 1.  To prevent a journal file record
  from being written, set the NONZERO variable to 0.

o Do not use a RETURN or a DELETE statement.  The invoking
  routine may not make a single pass through the DATA step
  for each observation.


The following sections describe the Journal File Exit
Worksheet and present an example.

 1 - Journal File Exit Worksheet
 2 - Journal File Exit Example