IBM Support

PH40554: ENHANCE ERROR MESSAGE WHEN APPLY OF IHS PTF FAILS WHEN THERE IS NOT A VALID SMPJHOME

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • SMP/E APPLY of an IHS PTF fails with:
    
    jar: /usr/lpp/ihsa_zos/IBM/HAPCE001 71: FSUM7351 not found
    
    
      ** Could not unjar /usr/lpp/ihsa_zos/IBM//HAPCCB001: jar
    command
    
    exited with  status=127
    
    The FSUM7351 and exit status 127 means the jar command is not
    found.  This can happen if valid Java runtime is not found in
    SMP/E.  To fix this, ensure the java runtime exists at the
    directory specified by SMPJHOME DD statement or mounted at the
    directory specified by SMPJHOME.
    
    This APAR will enhance the script so that if the status code is
    127, an additional message will come out saying to check the
    directory specified by SMPJHOME DD statement or mounted at the
    directory specified by SMPJHOME.
    

Local fix

  • Ensure ther java runtime exists at the directory specified by
    SMPJHOME DD statement or mounted at the directory specified by
    SMPJHOME.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM HTTP Server on z/OS using  *
    *                  SMPE installation.                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: SMP/E APPLY of an IHS PTF fails with:   *
    *                      jar: /usr/lpp/ihsa_zos/IBM/HAPCE001 71: *
    *                      FSUM7351 not found                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The FSUM7351 and exit status 127 means the jar command is not
    found.  This can happen if valid Java runtime is not found in
    SMP/E.  To fix this, ensure the java runtime exists at the
    directory specified by SMPJHOME DD statement or mounted at the
    directory specified by SMPJHOME.
    This APAR will enhance the script so that if the status code is
    127, an additional message will come out saying to check the
    directory specified by SMPJHOME DD statement or mounted at the
    directory specified by SMPJHOME.
    

Problem conclusion

  • The installation script was updated to emit a more specific
    message if jar is not in the path:
    
    Check to ensure your java runtime exists at the directory
    specified by SMPJHOME DD statement or mounted at the directory
    specified by SMPJHOME
    
    The fix for this APAR is targeted for inclusion in IBM HTTP
    Server fix packs 9.0.5.11. For more information, see
    'Recommended Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH40554

  • Reported component name

    WAS IHS ZOS

  • Reported component ID

    5655I3510

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-09-13

  • Closed date

    2021-11-18

  • Last modified date

    2021-11-18

  • 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

    WAS IHS ZOS

  • Fixed component ID

    5655I3510

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0.0.0"}]

Document Information

Modified date:
19 November 2021