PI07284: OSEQ CAN OCCUR AFTER SYMPHONY RENEW ( EQQDSTOP ) IS RUN

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• An OSEQ error can occur after a Symphony Renew is executed
  under the following scenario:
  .
  1) Application started
  2) Application completed
  3) SUBMIT SYMRENEW (EQQDSTOP)
  4) Perform " ALL-TO-W " for the application
  5) Application starts, then OSEQ occurred
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: ALL TWS for z/OS USERs who run               *
  *                 with E2E feature.                            *
  *                                                              *
  *                 FUNCTION=E2E                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: An OSEQ (out of sequence) error         *
  *                      condition can occur when                *
  *                      performing a set to wait of an          *
  *                      occurrence after a symphony renew.      *
  ****************************************************************
  * RECOMMENDATION: APPLY THE PTF FIXING THIS APAR               *
  ****************************************************************
  An OSEQ (out of sequence) error condition can occur when
  performing a set to wait of an occurrence after a symphony
  renew.
  

Problem conclusion

• The problem was caused by the fact that events
  resetting the status for a z/OS operation were not sent to
  the server. After a symphony renew, those operations
  resulted in success status. As a consequence of it,
  any attempt to make the successors run again was
  successful, even if in the CP the operations were changed to
  ready status (via set to wait or also via manual status
  change). This led to the described OSEQ condition.
  By means of this apar, the event is sent for z/OS
  operations that are in the symphony,
  whose old status was complete and the new one
  is ready, arriving or waiting and they have at least
  a successor in the CP.
  When the event for status change (e.g. to ready) is sent
  and the operation in the symphony is already in
  that status, in the MLOG of TWS for z/OS server
  message AWSBHT019E is issued, saying that the event
  has been discarded.
  500Y
  510Y
  600Y
  910Y
  EQQZTWJ
  

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:

  UI13912 UI13913 UI13914 UI13915

Modules/Macros

• EQQZTWJ
  

Fix information

• Fixed component name

  TIV WRKLD SCHD

• Fixed component ID

  5697WSZ01

Applicable component levels

• R500 PSY UI13912

     UP14/01/20 P F401

• R510 PSY UI13913

     UP14/01/20 P F401

• R600 PSY UI13914

     UP14/01/20 P F401

• R910 PSY UI13915

     UP14/01/20 P F401

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.