7. PARAMETERS › 7.2 Complex Level Parameters › 7.2.2 Account Code Structure (DB2ACCT) › 7.2.2.1 Add or Modify DB2 Account Structure

7.2.2.1 Add or Modify DB2 Account Structure

You can add, delete, or change the definitions of the DB2
account codes.  However, changing the account code structure
affects not only the content of the CA MICS database, but
also your ability to produce consistent reports, as the DB2
files will be summarized differently afterwards.  Your
CA MICS Accounting and Chargeback files will also be
affected.  Therefore, you should implement the new account
code structure when it will produce the least impact on your
CA MICS system, such as during the testing phase or at the
beginning of an accounting month.

Use the following checklist to alter the DB2 account code
structure (DB2ACCT):

___ 1.  Save a copy of sharedprefix.MICS.PARMS members
        DB2ACCT and DB2ACRT (if necessary) in
        sharedprefix.MICS.LOCALMOD.CNTL for recovery
        purposes.

___ 2.  Modify sharedprefix.MICS.PARMS(DB2ACCT) to add,
        delete, or modify an existing account code
        definition.

___ 3.  Submit sharedprefix.MICS.CNTL(DB2CGEN).

___ 4.  Modify the DB2 Account Code Derivation Routine in
        sharedprefix.MICS.PARMS(DB2ACRT) to derive the
        account codes.  Changes to this member take effect
        immediately, as this code is included in the next
        DAILY execution.

___ 5.  Retrofit the 00 cycles of the DB2DSU and DB2DDU files
        in the WEEKS, MONTHS, and YEARS (if active) timespans
        if you added or deleted an account code level or
        shortened the account code length.  See Section 6.3.2
        of the System Modification Guide for a sample
        retrofit routine.