IBM Support

PI24328: SAME FILE NAMES WHEN USING REDIRECT_SERVER_OUTPUT_DIR FUNCTION ON JES3 SYSTEM

Fixes are available

8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When redirect_server_output_dir is used, the file naming scheme
    for standard output and standard error is as follows:
    
    cellName.nodeName.serverName.jobName.jobId.asType.date.time
    followed by either .SYSPRINT.txt or .SYSOUT.txt respectively.
    
    This should make the file names unique because of the jobId
    field.  The field is set by the JSABPREF value.  This works
    fine in a JES2 environment.  But, on a JES3 system, the
    JSABPREF value is set to the jobname not the STCxxxxx
    equivalent of JOBxxxxx. The JSABJBID field should be used to
    build the filename.
    
    When using the modify command: f <sever>,ROLL_LOGS
    And there are multiple servants, this can cause all servants to
    use the same SYSPRINT and SYSOUT files.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0, V8.0, and V8.5                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere Application server for z/OS   *
    *                      servants may write to the same file     *
    *                      when using redirect_server_output_dir   *
    *                      on a JES3 system.                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When redirect_server_output_dir is used, the file naming
    pattern is as follows:
    cellName.nodeName.serverName.jobName.jobId.asType.date.time
    followed by either .SYSPRINT.txt or .SYSOUT.txt respectively.
    The Job Id should make the file names unique across
    the set of servants.  However, the jobId value is set from
    the JSABPREF field. This works fine in a JES2 environment.
    But, on a JES3 system, the JSABPREF value is set to the job
    name not the STCxxxxx equivalent JOBxxxxx. The JSABJBID field
    should be used to build the filename.
    The modify command "f <server>,ROLL_LOGS" on a server running
    on
    a JES3 system, configured with multiple servants, can cause all
    the servants to use the same SYSPRINT and SYSOUT files.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI24328

  • 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

    2014-08-21

  • Closed date

    2014-11-11

  • Last modified date

    2015-04-02

  • 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 FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UI25330

       UP15/03/13 P F503

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.



Document information

More support for: WebSphere Application Server for z/OS
General

Software version: 7.0

Reference #: PI24328

Modified date: 02 April 2015