PH35467: QSVTAP24 SERVICE PROGRAM NOT UPDATED BY FIXPACK IF OWNERSHIP INCORRECT

APAR status

• Closed as program error.

Error description

• If the owner of the QWAS85X/QSVTAP24.SRVPGM is not QSYS the
  fixpack process is not able to update the object. Eventually
  this can lead to severe thread failures in HTTP Apache due to
  increasing levels of code being mismatched.
  

Local fix

• A manual update of the service program object can be
  performed:
  
  1) First we will want to end the QWAS85
  subsystem
  
  2) Once the subsystem has ended we can run the
  following commands to rename the existing service program
  objects
  
  RNMOBJ OBJ(QWAS85A/QSVTAP24) OBJTYPE(*SRVPGM)
  NEWOBJ(QSVTAP2OLD)
  
  3) Next we'll go into STRQSH and run the
  following commands to rebuild this object:
  
  cd
  /QIBM/ProdData/WebSphere/AppServer/V85/Express/bin
  
  _postfpexit
  /QIBM/ProdData/WebSphere/AppServer/V85/Express
  
  4) Once the $
  returns we can exit STRQSH and start the WebSphere server
  again.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  *                  running a fix pack install on IBM i where   *
  *                  service programs are not owned by QSYS.     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Some service programs on the system     *
  *                      might                                   *
  *                      not be updated during a fixpack install *
  *                      if not owned by QSYS.                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  For this particular issue, the service program QSVTAP24 was not
  updated by a fixpack install since it was not owned by QSYS on
  the
  system.  This caused a mismatch between service programs
  QSVTAP24
  and QSVTCMMNH which ultimately led to the IBM HTTP server
  threads
  getting hung.
  

Problem conclusion

• Service program objects will be restored to the system during a
  fix pack install, even if the current owner is not QSYS.
  
  The fix for this APAR is targeted for inclusion in fix pack
  8.5.5.20 and fix pack 9.0.5.8. For more information, see
  'Recommended Updates for
  WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

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:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP

• R900 PSY

     UP