4. CUSTOMIZATION › 4.17 Activating/Deactivating the ACTYEAR4 element. › 4.17.2 Deactivating the ACTYEAR4 element.

4.17.2 Deactivating the ACTYEAR4 element.

Deactivating ACTYEAR4 requires making edits to NAME
statements in the AJFGENIN and/or ACTGENIN members of
sharedprefix.MICS.GENLIB.

Refer to Section 4.2.4.3.3 of the CA MICS System Modification
Guide for more information on the structure of the NAME
statement.

___ 1.  To deactivate ACTYEAR4 in a journal file:

        Edit the AJFGENIN member in sharedprefix.MICS.GENLIB.
        Locate the NAME statement for the ACTYEAR4 element.

        Deactivate ACTYEAR4 by changing the NAME statement
        from:

        NAME ACTYEAR4 99 0 N N N N .

        to:

        NAME ACTYEAR4 99 N N N N N .

 ___ 2. To deactivate ACTYEAR4 in a ledger file:

        Edit the ACTGENIN member in sharedprefix.MICS.GENLIB.
        Locate the NAME statement for the ACTYEAR4 element in
        the ledger file.

        Deactivate ACTYEAR4 by changing the NAME statement
        from:

        NAME ACTYEAR4 99 N 0 N 0 N .

        to:

        NAME ACTYEAR4 99 N N N N N .

 ___ 3. To deactivate ACTYEAR4 in any of the
        sharedprefix.MICS.TABLES files ACTRCP, ACT_YR,
        ACTSCT, ACTSDT, ACTBGT, ACT_RR, ACT_RC, ACT_YT,
        ACT_SC, ACT_RT:

        Edit the ACTGENIN member in sharedprefix.MICS.GENLIB.
        For each file in which you wish to deactivate the
        element, locate the NAME statement for the ACTYEAR4
        element.

        Deactivate ACTYEAR4 by changing the NAME statement
        from:

        NAME ACTYEAR4 99 0 N N N N .

        to:

        NAME ACTYEAR4 99 N N N N N .

 ___ 4. Submit sharedprefix.MICS.CNTL(ACTCGEN). Ensure that
        the job terminates with a RC=0 and that there are no
        error messages in either ISPLOG nor in the CA MICS
        Log.

 ___ 5. If you deactivated ACTYEAR4 in the journal file(s),
        submit prefix.MICS.CNTL(MAGRUN) in each unit that
        contains CA MICS Accounting and Chargeback. Ensure
        that the job terminates with a RC=0 and that there
        are no error messages in the CA MICS Log.