IBM Support

PM67193: APPLYPTF.OUT CONTENTS SHOULD ALSO BE WRITTEN TO SYSOUT PART OF THE JOBLOG OUTPUT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Serviceability defect.  Contents of the applyPTF.out
    (PostInstaller) will be also written to the SYSOUT part of the
    joblog output.
    

Local fix

  • check applyPTF.out file for any  messages and errors.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server for z/OS V7.0, V8.0 and V8.5.        *
    ****************************************************************
    * PROBLEM DESCRIPTION: The APPLY job step output is not        *
    *                      written to the job log when the APPLY   *
    *                      step return code is not 0.              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the APPLY job step for a WebSphere Application Server for
    z/OS encounters an error, the ApplyPTF.out log file should be
    written to the job log for the application server.
    

Problem conclusion

  • The template files that are used to create the WebSphere
    Application Server for z/OS PROCs will be updated to copy the
    contents of the ApplyPTF.out file to SYSOUT when the APPLY job
    step return code is not 0.
    
    For WebSphere Application Server for z/OS Version 7.0, the
    template files that are used to create the PROCs reside within
    the WebSphere Customization Toolkit. These PROC template
    updates will only be made within WebSphere Customization
    Toolkit Version 8.5 (which can be used to customize WebSphere
    Application Server Versions 7.0, 8.0 and 8.5).
    
    For WebSphere Application Server for z/OS Versions 8.0 and
    8.5, the template files that are used to create the PROCs
    reside within the respective WebSphere Application Server
    runtime.
    
    This fix does not update existing WebSphere Application Server
    for z/OS PROCs. Installations desiring the PROC update must
    recreate their PROCs after the appropriate service level has
    been installed as documented below.
    
    APAR PM67193 is currently targeted for inclusion in
    Service Level 8.0.0.6  of WebSphere Application Server Version
    8.0, Service Level 8.5.0.2 of WebSphere Application Server
    Version 8.5 and Service Level 8.5.0.2 of WebSphere
    Customization Toolkit Version 8.5. (Note that the support for
    WebSphere Application Server for z/OS V7.0 is only contained
    within WebSphere Customization Toolkit V8.5.)
    
    Please refer to the Recommended Updates page for delivery
    information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    
    In addition, please refer to URL:
    http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack PTF information.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM67193

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-19

  • Closed date

    2012-10-10

  • Last modified date

    2012-10-10

  • 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

    WEBSPHERE CUST

  • Fixed component ID

    5655N0213

Applicable component levels

  • R700 PSY

       UP

[{"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":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 October 2021