PM86361: RER HANGS TSO SESSION WITH HIGH CPU AND MEMORY USE WHEN RESTART OPERATION IS SELECTED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In TWSz 8.5.0, 8.5.1, and 8.6.0, a RERUN OCCURRENCE (RER)
  request may cause the ISPF TSO session of the requesting user
  to hang with high CPU and memory usage for an extended time
  (5 to 30 minutes or more) when the operation at which the
  occurrence is to be restarted is selected.
  .
  During this time, only the one TSO user is affected.  All other
  TWSz functions and other dialog users continue to process
  normally.
  .
  The hang occurs while the dialog code analyzes the SUCCESSOR
  dependency network of the selected restart point, and simulates
  the required updates to those successors with respect to
  CONDITIONAL DEPENDENCIES.
  .
  The problem has been recreated at the TWSz Rome lab by the TWSz
  Change/Development team, and has been identified as occurring in
  code added beginning in TWSz V8R5M0 in support of conditional
  dependencies.
  .
  Also, the TWSz documentation should be updated to clearly state
  that when a RERUN OCCURRENCE request is made, the dialog code
  issues an ALLDEPS request to the CONTROLLER.  This results in
  message EQE032I being written to the CONTROLLER EQQMLOG, and if
  the user requesting the RERUN lacks needed access to the ADEP
  FIXED RESOURCE, the RERUN request is denied.
  .
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: ALL TWS for z/OS 851 and 860 USERs.          *
  *                                                              *
  *                 FUNCTION=DIALOG                              *
  *                                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: A low performing process can occur      *
  *                      in the ISPF dialog when selecting       *
  *                      the starting point for an occurrence    *
  *                      rerun.                                  *
  ****************************************************************
  * RECOMMENDATION: APPLY THE PTF FIXING THIS APAR               *
  ****************************************************************
  A low performing process can occur in ISPF dialog when
  selecting the starting point for an occurrence rerun.
  

Problem conclusion

• The problem is caused by the use of an old algorithm to scan
  recursively the network and process not waiting operations.
  This to produce a simulation of the status changes that
  the code will apply in the occurrence to rerun it.
  This apar changed the code to restrict the use of this
  algorithm to the minimum possible. The only case when
  it will be used is when there is at least an operation in
  X status (suppressed by cond) among the predecessors or
  successors for the starting point at any level.
  510N
  512Y
  600N
  602Y
  EQQMGOOX
  EQQMOSTX
  

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:

  UK94575 UK94576 UK94577 UK94578

Modules/Macros

• EQQMGOOX EQQMOSTX
  

Fix information

• Fixed component name

  TIV WRKLD SCHD

• Fixed component ID

  5697WSZ01

Applicable component levels

• R512 PSY UK94577

     UP13/08/13 P F308

• R602 PSY UK94578

     UP13/08/13 P F308

• R510 PSN

     UP

• R600 PSN

     UP

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.