IBM Support

PK95888: CHANGE QCF INITIALIZATION TO NOT WAIT FOR SCI TO COME UP

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • Change QCF initialization to not just wait for SCI to come
    up. Instead a message will be issued and QCF initialization
    will continue.  On SCI start it will connect and QCF services
    will be active.  If SCI does not start, no QCF functions
    will be available (panels, batch jobs, etc.).
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All QCF V3.1 users                           *
    ****************************************************************
    * PROBLEM DESCRIPTION: If the SCI task has not been started wh *
    *                      en IMS is restarted, QCF initialization *
    *                       just wait for SCI to come up. But depe *
    *                      ndent regions started in this state wil *
    *                      l not be initialized and consequently n *
    *                      ot be able to process transactions.     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If the SCI task has not been started when IMS is restarted, QCF
    initialization wait for SCI to come up and hung the MPP region.
    

Problem conclusion

Temporary fix

Comments

  • Now the QCF initialization was changed to be as that. When we st
    art IMS, if no SCI is up, QCF would auto-start specified SCI PRO
    C; if nothing specified or SCI start fail, QCF would wait till S
    CI available then do the SCI register. For the first 30 minutes,
     QCF would try to register at a 6 sec interval (same as the old
    logic); then after 30 min, QCF would try to register every 10 mi
    nutes. And the IMS hung problem is solved, the user should be ab
    le to run MPP when IMS is successfully started, QCF waiting for
    the SCI should not be an impact.
    

APAR Information

  • APAR number

    PK95888

  • Reported component name

    IMS QUEUE CNTL

  • Reported component ID

    5697E9900

  • Reported release

    310

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2009-09-10

  • Closed date

    2010-07-06

  • Last modified date

    2010-08-02

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

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

    UK58602

Modules/Macros

  • IQC##### IQCBPECF IQCCCPRM IQCCIN0A IQCCIN0B
    IQCCIN0X IQCCIN08 IQCCIN09 IQCCIN1A IQCCIN1B IQCCIN1X IQCCIN18
    IQCCIN19 IQCCQAB  IQCCSLSI IQCC1ENU IQCIMSII IQCSCI   IQCSIN10
    

Publications Referenced
SC18987503    

Fix information

  • Fixed component name

    IMS QUEUE CNTL

  • Fixed component ID

    5697E9900

Applicable component levels

  • R310 PSY UK58602

       UP10/07/09 P F007

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:
02 August 2010