PK74291: THE XA RECOVERY ALARM IS DELAYED CAUSING THE CONTROL REGION TO DELAY IN INITIALIZATION

APAR status

• Closed as fixed if next.

Error description

• The XA recovery alarm was not set properly, causing the server
  to delay starting until the next alarm expired successfully.
  

Local fix

• User can issue "F <server>,DIAGDATA=SNOO" on the console
  and any expired XA snoozers are forced to pop, so that the
  snoozer queue can be traced.  This should allow the server to
  complete initialization.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of WebSphere Application Server   *
  *                  V5.1.0 for z/OS                             *
  ****************************************************************
  * PROBLEM DESCRIPTION: Delay in scheduling expired alarms      *
  *                      (SnoozeAlarm services, bbootmsa.cpp)    *
  *                      results in significant server startup   *
  *                      delay.                                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  APAR PK74291 is being closed FIN with concurrence from the
  submitting customer. This means that a fix to this APAR is
  expected to be delivered from IBM in a release which is being
  developed at the time that the APAR was closed.
  

Problem conclusion

Temporary fix

Comments

APAR Information

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

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

  PK74292 PK74294 PK74295

Fix information

Applicable component levels

• R510 PSY

     UP