PM93853: WHEN IMS IS STARTED, THERE ARE A GREAT MANY HOURGLASS MESSAGES PUT IN THE JOB LOG, AND IMS DOES NOT START PROPERLY (LOOPING)

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • IMS is started, but fails to completely start.  Looking in the
    job log of the message region it is seen that HourGlass messages
    are being logged over and over, apparently in a loop.  This
    continues until the IMS job is cancelled.
    It was found that an HourGlass customization parameter
    "GTRACE=D" was causing the problem.  Recustomizing (AGGCUSTM)
    without GTRACE=D and stopping and restarting HourGlass resolved
    the problem.
    

Local fix

  • Ensure that GTRACE=D is not part of the HourGlass customization.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IBM HourGlass R610 users who have        *
    *                 implemented the HourGlass IOPCB              *
    *                 feature.                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: IMS message region IOPCB support hangs, *
    *                      without issuing msg AGGRC01I.           *
    *                      With GTRACE=D on, it will produce an    *
    *                      infinitely long log.                    *
    *                      No IOPCB time adjustments will happen.  *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF.                               *
    ****************************************************************
    

Problem conclusion

  • ***************************************************************
    * FIX DESCRIPTION:     Logic in AGGRRC01 was changed to       *
    *                      not try to add TCB address info to log *
    *                      msgs because they were causing a S0C4. *
    *                      Infinite ABEND retries caused hang.    *
    *                      Retries are now correctly limited to 5.*
    *                      Also log progress msgs when GTRACE=L   *
    *                      instead of GTRACE=D.                   *
    *                      Note that HourGlass must be started for*
    *                      AGGRRC01 to log HourGlass IMS          *
    *                      initialization progress debugging msgs *
    *                      when customization includes GTRACE=L.  *
    *                      Logic in AGGCUST was changed to        *
    *                      allow for GTRACE=L to be set.          *
    ***************************************************************
    * PRODUCT ELEMENTS AFFECTED BY THIS FIX:                      *
    ***************************************************************
    * NEW ELEMENTS ADDED:                                         *
    *     None.                                                   *
    *                                                             *
    ***************************************************************
    * EXISTING ELEMENTS MODIFIED:                                 *
    *   SAGGLOAD(AGGCUST ).#000006 2013/08/07.16:00:44.PM93853    *
    *   SAGGLOAD(AGGRATE0).#000003 2009/06/11.15:13:40.PK88589    *
    *   SAGGLOAD(AGGRRC01).#000012 2013/08/07.15:55:45.PM93853    *
    ***************************************************************
    * EXISTING ELEMENTS DELETED:                                  *
    *     None.                                                   *
    *                                                             *
    ***************************************************************
    * IMPLEMENTATION:    * After installing the fix for this APAR,*
    *                      it will be necessary to rerun the      *
    *                      HourGlass customization job (AGGCUSTM),*
    *                      if you wish to use GTRACE=L to produce *
    *                      HourGlass IMS initialization progress  *
    *                      debugging msgs from AGGRRC01.          *
    *                    * It will be necessary to stop and       *
    *                      restart HourGlass after customization  *
    *                      with a different GTRACE= option value. *
    *                    * After installing the fix for this APAR,*
    *                      it will be necessary to stop and       *
    *                      restart any running IMS versions.      *
    *                                                             *
    ***************************************************************
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM93853

  • Reported component name

    IBM HOURGLASS

  • Reported component ID

    5655U4200

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-07-25

  • Closed date

    2013-09-05

  • Last modified date

    2013-10-03

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  •    AGGCUST  AGGRATE0 AGGRRC01
    

Fix information

  • Fixed component name

    IBM HOURGLASS

  • Fixed component ID

    5655U4200

Applicable component levels

  • R610 PSY UK97354

       UP13/09/10 P F309

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Rate this page:

(0 users)Average rating

Document information


More support for:

HourGlass

Software version:

6.1

Reference #:

PM93853

Modified date:

2013-10-03

Translate my page

Machine Translation

Content navigation