Previous Topic: 10.1.3 Add or Modify CICS Account Codes

Next Topic: 10.1.4.1 Incremental Update Considerations

10.1.4 Alter the Active Timespans for a File


For each CIC information area file, there is a corresponding
FILE statement in sharedprefix.MICS.GENLIB(CICGENIN).  The
FILE statement defines the file name, the file type, the file
status (active or inactive) in each timespan, and the file
status for archive (audit and history collection).

*************************************************************
*                                                           *
*  Note:  If incremental update is active, be sure to       *
*         review the important considerations in Section    *
*         10.1.4.1 of this guide before applying the        *
*         TAPEfff option or USRXfff exits.                  *
*                                                           *
*************************************************************

This section includes three checklists:

o  Checklist 4.1, steps for activating the DETAIL timespan
   for the CICCSU file on tape.

o  Checklist 4.2, steps for activating the DETAIL timespans
   for the CICCAC, CICCAU, and CICCSU files on disk.

o  Checklist 4.3, steps for altering active timespans.

   Notes:  Do NOT activate the CICS Incident File (CICCIN) in
           higher timespans because its data is only
           meaningful in the DETAIL timespan.

           Do NOT change in any way the file status for the
           CICS Dictionary File (CICCDC).  This is a special
           file required to process CMF data and is not used
           for reporting purposes.

           To capture DETAIL timespan data for the CICS User
           Application Count (CICCAC), CICS Application Unit
           Activity (CICCAU), or CICS User Activity (CICCSU)
           files, you must code a USRXfff exit, where fff is
           the three-character file ID.  Refer to Section
           10.2.3 for more information about these exits.

           To activate the CICS File/DBD Activity File
           (CICCSF), refer to Section 10.1.9.

           To activate the CICS MRO Activity File (CICCMR),
           refer to Section 10.1.13.
   *****************************************************
   *                                                   *
   *    CHECKLIST 4.1 - ACTIVATE DETAIL TIMESPAN       *
   *    of CICCSU file on CA MICS GDG tape             *
   *                                                   *
   *    If incremental update is active, be sure to    *
   *    review the considerations in Section 10.1.4.1  *
   *    of this guide.                                 *
   *                                                   *
   *****************************************************

___ 1.  Review the descriptions of the FILE statement as
        provided by Section 4.2.4.2 of the System
        Modification Guide (SMG).

___ 2.  To activate and deactivate data elements in the
        DETAIL timespan, update the NAME/NAMX statements in
        sharedprefix.MICS.GENLIB(CICGENIN).

        The TAPECSU feature uses the KEEP list (macro)
        generated from the CSWCSU file.  Any file tailoring
        (activation/deactivation of elements) should be done
        to the CSWCSU file in
        sharedprefix.MICS.GENLIB(CICGENIN).

        Note:  Deactivating elements in the CSWCSU file makes
        them unavailable to other files as well, such as
        CICCAU, CICCAC, and CICCSU at DAYS and higher
        timespans.

        Several types of data elements are not meaningful in
        the DETAIL timespan.  Among these are elements
        related to averages, minimums, and maximums.
        Elements that are based on TRANTYPE, such as response
        time distributions, are also meaningless, because
        they are not calculated during detail input
        processing.  Turning off these elements in the DETAIL
        file will save DASD space.

___ 3.  Skip this step if you did not perform Step 2.
        Otherwise, submit sharedprefix.MICS.CNTL(CICCGEN).

   ****************************************************
   *     Repeat the following steps for each database *
   *     unit containing the CICS Analyzer.           *
   ****************************************************

___ 4.  Edit prefix.MICS.PARMS(CICOPS) and add the following
        statement anywhere in the member:

        TAPECSU

___ 5.  Submit prefix.MICS.PARMS(CICPGEN).

___ 6.  Edit prefix.MICS.PARMS(JCLGENU) so that it reads:

        CICGDGGN DAILY

___ 7.  Submit prefix.MICS.CNTL(JCLGENU) to regenerate the
        JCL for DAILY and CICGDGGN.

___ 8.  Submit prefix.MICS.CNTL(CICGDGGN) to define the tape
        GDG.  See Section 9.3.4 for additional documentation
        regarding the CICGDGGN job.

___ 9.  (Optional) Edit prefix.MICS.USER.SOURCE(#CICEXIT) and
        define the USRTCSU exit if you want to limit the
        amount of output that will be written to the CICCSU
        file.

   *****************************************************
   *                                                   *
   *    CHECKLIST 4.2 - ACTIVATE DETAIL TIMESPANS      *
   *    FOR CICCAC, CICCAU, and CICCSU files on disk   *
   *                                                   *
   *    If incremental update is active, be sure to    *
   *    review the considerations in Section 10.1.4.1  *
   *    of this guide.                                 *
   *                                                   *
   *****************************************************

___ 1.  Make a backup copy of the
        prefix.MICS.USER.SOURCE(#CICEXIT) member for each
        CICS unit to be modified.

___ 2.  Review the descriptions of the FILE statement as
        provided by Section 4.2.4.2 of the System
        Modification Guide (SMG).

___ 3.  Update the FILE statement in
        sharedprefix.MICS.GENLIB(CICGENIN) for each file to
        be activated in the DETAIL timespan.  Change the
        file status from N to Y.  Use IEBUPDTE to apply the
        change.  See Section 6.2.2.2 in the SMG for an
        example.

        Note:  In order to activate the CICCAC and/or CICCAU
        files in the DETAIL timespan, they MUST also be
        active in the DAYS timespan.  Additionally, any
        elements you require MUST be active in the DAYS
        timespan of the CICCSW and or CICCAC/CICCAU files
        even if you only require them at the DETAIL timespan.

___ 4.  Update the NAME/NAMX statements in the CICGENIN
        member of sharedprefix.MICS.GENLIB to activate or
        deactivate data elements in the DETAIL timespan.
        Elements that are only in the CICCSU file may be
        added to the CICCAU and/or CICCAC files.  To do this,
        review how the element is defined in the CICCSU file
        and then define it identically in the CICCAU and/or
        CICCAC file.  The only difference in the definitions
        should be the data element name.  For example,
        CSUINCH is named CACINCH if it is being added to the
        CICCAC file.  Again, any element required in the
        CICCAC and/or CICCAU files MUST be active in the DAYS
        timespan of the CICCSW file and the requested output
        files CICCAC/CICCAU even if you only require them
        at the DETAIL timespan.

        Several types of data elements are not meaningful in
        the DETAIL timespan.  Among these are elements
        related to averages, minimums, and maximums.
        Elements that are based on TRANTYPE, such as response
        time distributions, are also meaningless, because
        they are not calculated during detail input
        processing.  Turning off these elements in the DETAIL
        file will save DASD space requirements.

        If you activate an element in the CICCSU file, you
        MUST activate the element in the CSWCSU file as
        well.

        If you deactivate an element in the CICCSU file AND
        that element is also inactive or does not exist in
        the CICCAU and CICCAC files, you should deactivate
        the element in the CSWCSU file to save work space and
        DAY040 run time.

___ 5.  Submit sharedprefix.MICS.CNTL(CICCGEN).

___ 6.  If the CICCAC file is being activated in the DETAIL
        timespan, then make the following updates to the
        _USRXCAC macro in prefix.MICS.USER.SOURCE(#CICEXIT):

        Note:  See examples under Step 8 below for additional
        coding techniques.

 DATA &CICX..CICCAC00(%%CACFILE(OP=FILEOPTS,TS=DETAIL));
   SET %%WRKMERG(WRK=CSW,CCC=CIC,R=CACREN);
 RUN;

___ 7.  If the CICCAU file is being activated in the DETAIL
        timespan, then make the following updates to the
        _USRXCAU macro in prefix.MICS.USER.SOURCE(#CICEXIT):

        Note:  See examples under Step 8 below for additional
        coding techniques.

 DATA &CICX..CICCAU00(%%CAUFILE(OP=FILEOPTS,TS=DETAIL));
   SET %%WRKMERG(WRK=CSW,CCC=CIC,R=CAUREN);
 RUN;

___ 8.  If the CICCSU file is being activated in the DETAIL
        timespan, then make the following updates to the
        _USRXCSU macro in prefix.MICS.USER.SOURCE(#CICEXIT):

 /*********************************************************/
 /***               EXAMPLE ONE                         ***/
 /***                                                   ***/
 /*** Write DETAIL.CICCSU to disk in compressed format  ***/
 /*** (if file is generated with compression on)        ***/
 /*** using the generated KEEP macro (created from      ***/
 /*** sharedprefix.MICS.GENLIB(CICGENIN) CSWCSU file    ***/
 /*********************************************************/

 DATA &CICX..CICCSU00 (KEEP=%%CSWKEEP(TS=DETAIL)
                       COMPRESS=%%INTRST(CCC=CIC));
   SET %%WRKMERG(WRK=CSW,CCC=CIC);
 RUN;

 /*********************************************************/
 /***               EXAMPLE TWO                         ***/
 /***                                                   ***/
 /*** Write DETAIL.CICCSU to disk FORCING to compressed ***/
 /*** format regardless of compression option, and still***/
 /*** using the generated KEEP macro from CSWCSU file.  ***/
 /*** If compression is not desired, omit the COMPRESS= ***/
 /*** option keyword, or change YES to NO.              ***/
 /*********************************************************/

 DATA &CICX..CICCSU00 (KEEP=%%CSWKEEP(TS=DETAIL)
                       COMPRESS=YES) ;
   SET %%WRKMERG(WRK=CSW,CCC=CIC);
 RUN;

 /*********************************************************/
 /***               EXAMPLE THREE                       ***/
 /***                                                   ***/
 /*** Write DETAIL.CICCSU to disk and provide your own  ***/
 /*** KEEP list, again using file compression.          ***/
 /*** Any elements you specify MUST be active in the    ***/
 /*** CSWCSU file or DAY040 will abend.                 ***/
 /***                                                   ***/
 /*** If compression is not desired, omit the COMPRESS= ***/
 /*** option keyword, or change YES to NO.              ***/
 /*********************************************************/

 DATA &CICX..CICCSU00
   (KEEP = CICSID USERID TRANCODE STARTTS ENDTS CSUTRSTM
           CSUCPUTM CSUFCOPS COMPRESS=YES );
   SET %%WRKMERG(WRK=CSW,CCC=CIC);
 RUN;

   ****************************************************
   *     Repeat the following steps for each database *
   *     unit containing the CICS Analyzer.           *
   ****************************************************

___ 9.  Review the definitions in prefix.MICS.PARMS(DBMODEL).
        Modify the cycle retention number to match the file
        status in each timespan.  For example, at least one
        cycle is retained for the DETAIL timespan for the
        files you activated.  See Section 7.3.10 of this
        guide for details on DBMODEL definitions.

___ 10. Submit the job in prefix.MICS.CNTL(CYCLEGEN).

   *****************************************************
   *                                                   *
   *  CHECKLIST 4.3 - ALTER ACTIVE TIMESPANS FOR FILE  *
   *                                                   *
   *****************************************************


___ 1.  Save a copy of sharedprefix.MICS.GENLIB(CICGENIN) in
        sharedprefix.MICS.LOCALMOD.CNTL for recovery
        purposes.

___ 2.  Review the description of the FILE statement in
        Section 4.2.4.2 of the System Modification Guide.

___ 3.  Update the FILE statement in
        sharedprefix.MICS.GENLIB(CICGENIN) for each file to
        be modified.  Use IEBUPDTE to apply the change.

___ 4.  Regenerate the CICS Analyzer by submitting the job in
        sharedprefix.MICS.CNTL(CICCGEN).

   ****************************************************
   *     Repeat the following steps for each database *
   *     unit containing the CICS Analyzer.           *
   ****************************************************

___ 5.  Review the definitions in prefix.MICS.PARMS(DBMODEL).
        Modify the cycle retention number to match the
        file status in each timespan.  For example, zero
        cycle is retained for all inactive timespans.  See
        Section 7.3.10 of this guide for details on DBMODEL
        definitions.

___ 6.  Submit the job in prefix.MICS.CNTL(CYCLEGEN).