IBM Support

PK56747: QSUN FUNCTION DOES NOT WORK AS EXPECTED IN SOME CASES

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • QSUN function does not work as expected in some cases.
    
    Additional issue fixed: IMS wait after the IMS commands
    /STOP OTMA and a /CHE FREEZE were issued.  OTMA calls
    QCF routine IQCCQAT0 which never returns.
    Keywords: hang hangs waits /sto stop checkpoint
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of QCF3.1.                         *
    *                 The new functionality in the APAR is for     *
    *                 overflow protection in non-shared queues     *
    *                 environment.                                 *
    *                 Some panel's and program's changes impact    *
    *                 also QCF3.1 in shared queues environment.    *
    *                 It is highly recommended to install this     *
    *                 APAR.                                        *
    *                 In non-shared queues environment you need    *
    *                 to install next IMS APARs:                   *
    *                 IMS9.1 : PK57760                             *
    *                          PK51055                             *
    *                 IMS10.1: PK57762                             *
    *                          PK61677                             *
    ****************************************************************
    * PROBLEM DESCRIPTION: Full description of new functionality   *
    *                      is in QCF3.1 user's guide.              *
    *                      In addition to AREA parameter, that     *
    *                      sets the areas for queues and the       *
    *                      actions to be taken in each area ,      *
    *                      a new parameter is introduced:          *
    *                      FAILSAFE                                *
    *                      Failsafe Design:                        *
    *                                                              *
    *                      Failsafe is a means of identifing the   *
    *                      Total Queue Usage of the IMS Queue      *
    *                      Manager queues to prevent the overflow  *
    *                      of the IMS queues. Total Queue Usage    *
    *                      is defined as the sum of all specific   *
    *                      IMS entities queue usage.               *
    *                      Failsafe represents a view of Queue     *
    *                      Manager queues as a percentage of the   *
    *                      total queue space.                      *
    *                      Failsafe differs from Area in that      *
    *                      Failsafe targets Total Queue Usage not  *
    *                      Specific Queue Usage.                   *
    *                                                              *
    *                      A level of Total Queue Usage is         *
    *                      expressed as a percentage of the total  *
    *                      queue (see the PERCENT=(TOTAL=,  )      *
    *                      parameter)                              *
    *                                                              *
    *                      Failsafe allows any specific IMS entity *
    *                      to continue processing when Failsafe is *
    *                      active (see the                         *
    *                      PERCENT=(  ,USED=) parameter).          *
    *                      Failsafe will allow a specific IMS      *
    *                      to continueprocessing as long as it's   *
    *                      queue usage is less than thespecified   *
    *                      USED percentage.                        *
    *                      Failsafe has two types of analysis to   *
    *                      identify excessive Total Queue Usage    *
    *                                                              *
    *                      Source Analysis :                       *
    *                       Determine if Total                     *
    *                       Queue Usage meets FAILSAFE TOTAL       *
    *                       specification -Identify if a SPECIFIC  *
    *                       SOURCE can continue processing from    *
    *                       the USED specification                 *
    *                                                              *
    *                      Destination Analysis    -               *
    *                       Determine if Total Queue Usage meets   *
    *                       FAILSAFE TOTAL specification- Identify *
    *                       if a SPECIFIC DESTINATION can continue *
    *                       processing from the USED specification *
    *                                                              *
    *                      Failsafe TOTAL/USED Percentages apply   *
    *                      both Source Analysis and Destination    *
    *                      Analysis.                               *
    *                      Failsafe does not allow the targeting   *
    *                      of specific IMS entities so the         *
    *                      TYPE= parameter is not permitted.       *
    *                      An implicit TYPE=ALL is enforced        *
    *                      which includes the following:           *
    *                       TYPE=APPL  A dependent region appl     *
    *                       TYPE=DC    A VTAM terminal             *
    *                       TYPE=APPC  A LU 6.2/APPC application   *
    *                       TYPE=OTMA  A OTMA application          *
    *                       TYPE=MSC   An IMS to IMS commum. pipe  *
    *                                                              *
    *                      Failsafe Actions are global and there   *
    *                      is a single action parameter.           *
    *                        ACTION=(action value)                 *
    *                        The Action Values are:                *
    *                        NONE  applicable to all TYPEs         *
    *                        WTO   applicable to all TYPEs         *
    *                        WAIT  applicable to TYPE=APPL only    *
    *                        STOP  applicable to all TYPEs         *
    *                        ABEND applicable to TYPE=APPL only    *
    *                      Up to 5 failsafe statements can be      *
    *                      specified:                              *
    *                      Failsafe Card Example                   *
    *                      FAILSAFE=(ID=FAIL0001,                  *
    *                        PERCENT=(TOTAL=70,USED=02),           *
    *                        ACTION=WTO)                           *
    *                      FAILSAFE=(ID=FAIL0002,                  *
    *                        PERCENT=(TOTAL=85,USED=00),           *
    *                        ACTION=WTO)                           *
    *                      etc  - up to 5 FAILSAFE statements      *
    ****************************************************************
    * RECOMMENDATION: Install IMS APARs, change IMS start          *
    *                 up proclib member - to include               *
    *                 AREA and FAILSAFE statements                 *
    *                 and recycle IMS.                             *
    ****************************************************************
    Overflow protection functionality in non-shared queues
    environment has been improved - new parameter has been
    introduced - to describe the boundaries and the actions to be
    taken when the queues are close to their limits.
    

Problem conclusion

  • QCF3.1 overflow protection in non-shared queues environment has
    been improved.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK56747

  • Reported component name

    IMS QUEUE CNTL

  • Reported component ID

    5697E9900

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Xsystem

  • Submitted date

    2007-11-16

  • Closed date

    2008-03-10

  • Last modified date

    2008-04-01

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

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

    UK34410

Modules/Macros

  • IQCCCPRM IQCCCVCA IQCCCVCX IQCCCVC8 IQCCCVC9
    IQCCIN0A IQCCIN0X IQCCIN08 IQCCIN09 IQCCIN1A IQCCIN1X IQCCIN18
    IQCCIN19 IQCCQAL  IQCCQAT  IQCCQATA IQCCQATX IQCCQAT8 IQCCQAT9
    IQCCQCI  IQCCQTTA IQCCQTTX IQCCQTT8 IQCCQTT9 IQCC1ENU IQCMRAEQ
    IQCQMRGA IQCQMRGX IQCQMRG8 IQCQMRG9 IQCQMRIA IQCQMRIX IQCQMRI8
    IQCQMRI9 IQCQMR3A IQCQMR3X IQCQMR38 IQCQMR39 IQCQMR6A IQCQMR6X
    IQCQMR68 IQCQMR69 IQCQMR7A IQCQMR7X IQCQMR78 IQCQMR79 IQCXREAD
    

Fix information

  • Fixed component name

    IMS QUEUE CNTL

  • Fixed component ID

    5697E9900

Applicable component levels

  • R310 PSY UK34410

       UP08/03/11 P F803

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.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX8A6","label":"IMS Queue Control Facility"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 April 2008