IBM Support

PK54670: IMS THAT IS STARTED WITH AOS=F FAILS TO BECOME ACTIVE WHEN THE ONLY IMS WITH AOS=N LEAVES THE GROUP.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as duplicate of another APAR.

Error description

  • Customer has 3 IMS systems in the sysplex group. IMS1 and IMS2
    are started with AOS=F. IMS3 has AOS=N. When IMS3 shuts down
    and leaves the group, IMS2 has a global status that remains
    inactive. At this time both IMS1 and IMS2 should be active and
    should be able to have synchronous APPC and OTMA message
    processing using the shared queues.
     There is a timing problem in DFSAOSW0 in aosleav where IMS1
    fails to provide IMS2 with its global status.
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  • APAR is being closed as a DUP of PK44263.  The customer
    applied PK44263 (Versioning APAR) and that resolved the
    problem.
    

APAR Information

  • APAR number

    PK54670

  • Reported component name

    IMS V9

  • Reported component ID

    5655J3800

  • Reported release

    900

  • Status

    CLOSED DUA

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2007-10-12

  • Closed date

    2007-11-30

  • Last modified date

    2007-11-30

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

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

Fix information

  • Fixed component name

    IMS V9

  • Fixed component ID

    5655J3800

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVRBJ","label":"System Services"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
30 November 2007