PI11611: NON-CENTRALIZED FT JOB STUCK IN RNN (READY, NO-OPED) AFTER MH/NP/MR COMMAND SEQUENCE.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A NON-CENTRALIZED job on an FT workstation may remain stuck in
  NPP (READY - OPERATION NOPED) status after the following command
  sequence.
  1. MH target operation
  2. NP target operation
  3. (predecessors complete)
  4. MR target operation
  5. Target operation remains in RNN status.
  Problem is related to translation of operation status between
  the CP and SYMPHONY.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: ALL TWS for z/OS USERs who run with          *
  *                 E2E feature.                                 *
  *                                                              *
  *                 FUNCTION=E2E                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: If a non-centralized manually held      *
  *                      job is noped, it may remain in          *
  *                      in ready - operation noped status       *
  *                      even when it is manually released.      *
  ****************************************************************
  * RECOMMENDATION: APPLY THE PTF FIXING THIS APAR               *
  ****************************************************************
  If a non-centralized manually held job is noped, it may remain
  in ready - operation noped status when it is manually released.
  

Problem conclusion

• A code change has been implemented to fix the
  following scenario:
  A non-centralized job having the automatic submit flag set to Y
  is manually held (mh), then is noped (np). In this situation
  once the predecessors are completed the job remains in ready
  (manually held). At this point if it is manually released,
  the job gets completed, as expected.
  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:

  UI16173 UI16174 UI16175 UI16176

Modules/Macros

• EQQZTWJ
  

Fix information

• Fixed component name

  TIV WRKLD SCHD

• Fixed component ID

  5697WSZ01

Applicable component levels

• R500 PSY UI16173

     UP14/08/08 P F408

• R510 PSY UI16174

     UP14/08/08 P F408

• R600 PSY UI16175

     UP14/08/08 P F408

• R910 PSY UI16176

     UP14/08/08 P F408

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.