IBM Support

PM74923: SERVANT OUTPUT REDIRECTED TO UNIX SYSTEMS SERVICES FILE SYSTEM C OULD COLLIDE WHEN SERVANTS START AT THE SAME TIME.

Fixes are available

8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
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.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
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.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
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.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 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
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customers may redirect Servant output on a z/OS Websphere
    Application Server from SYSOUT and SYSPRINT DD cards to files
    on the Unix System Services(USS) file system. To do this they
    must substitute variables in the PATH name specified on the
    DD card to generate unique file names. The only usable
    variables to do this are date and time and collisions could
    occur between servant regions that start at the same time.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0, V8.0, and V8.5                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: When a WebSphere Application Server     *
    *                      for z/OS is running with multiple       *
    *                      Servants and also redirects output      *
    *                      from SYSOUT and SYSPRINT DD cards to a  *
    *                      Unix System Services(USS) file          *
    *                      system, it is possible for the          *
    *                      output of multiple Servants to get      *
    *                      written to the same file.               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Customers may redirect Servant output on a z/OS Websphere
    Application Server from SYSOUT and SYSPRINT DD cards to files
    on
    the Unix System Services(USS) file system. To do this they must
    substitute variables in the PATH name specified on the DD card
    to generate unique file names. The only usable variables to do
    this are date and time and collisions could occur between
    servant regions that start at the same time.
    

Problem conclusion

  • Code was added to create a new custom way of redirecting
    output. If a customer would like output written to files
    on the Unix System Services(USS) file system, they can specify
    which directory they would like their output redirected to
    using a new Websphere environment variable
    redirect_system_output_dir. If set, output will be redirected
    to files in that directory. If not set, output will be
    redirected to DD cards as before. If USS redirecting is chosen,
    the new file naming scheme for standard output and standard
    error, is as follows:
    cellName.nodeName.serverName.jobName.jobId.asType.date.time
    with .SYSPRINT.txt or .SYSOUT.txt following respectively. A
    ROLL_LOGS modify command has also been created for the aid of
    automation. ROLL_LOGS can be called to re-issue the redirect
    command, creating a new set of ouput files for the specified
    server and its respective servant regions. Messages are
    appended to the end of the previous file and beginning of the
    new file linking them together.
    
    APAR PM74923 requires changes to documentation.
    
    NOTE: Periodically, we refresh the documentation on our Web
    site, so the changes might have been made before you read this
    text. To access the latest on-line documentation, go to the
    product library page at:
    
    http://www.ibm.com/software/webservers/appserv/library
    
    The following changes to the WebSphere Application Server
    Version 7.0 Information Center will be made available in June,
    2013.
    
    The topic "Output destinations" will be updated to include the
    following information:
    
    Starting with Version 7.0.0.29, you can also use the
    redirect_server_output_dir WebSphere environment variable to
    redirect output to files on the Unix Systems Services (USS)
    file system. The value specified for this variable is the
    absolute path of the existing directory that contains the
    files to which you want output redirected. If a value is not
    specified for this variable, output continues to be directed
    to DD statements. Refer to the topic "Application server
    custom properties for z/OS" for a description of how to
    specify a WebSphere environment variable.
    If you decide to use USS redirecting, the new 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.
    You can use the ROLL_LOGS parameter of the modify command to
    automate the use of the redirect_server_output_dir. When you
    issue the following modify command, a new set of ouput files
    is created for the specified server and its respective
    servants. Messages are then appended to the end of the
    previous output file and the beginning of the new file,
    thereby linking them together.
    f <server>, ROLL_LOGS
    
    The topic "Application server custom properties for z/OS" will
    be updated to include the following description of the
    redirect_system_output_dir WebSphere environment variable:
    
     redirect_server_output_dir
    Specifies the output directory on the Unix Systems
    Services(USS) file system to which redirected servant output
    files are to be written.
    This value must be an absolute path to an existing directory
    with appropriate write permissions. If a valid value is not
    specified for this variable, by default, output is redirected
    to DD cards.
    
    Data Type:               String
    Default:                     Empty string
    Used by Daemon:   Yes
    
    The topic "Modify command" will be updated to include the
    following description of the ROLL_LOGS parameter:
    
    ROLL_LOGS
    Used to reissue a redirect of servant output logs to the USS
    file system. A new set of output log files will be created
    under the same output directory, and older log files will be
    preserved. Messages will be written to the end of previous
    logs and to the beginning of new logs. thereby creating a
    logical link between the files.
    
    APAR PM74923 is currently targeted for inclusion in WebSphere
    Application Server Fix Packs 7.0.0.29, 8.0.0.6, and 8.5.0.2.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM74923

  • 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-10-12

  • Closed date

    2013-01-04

  • Last modified date

    2013-07-03

  • 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 UK94926

       UP13/06/20 P F306

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.

[{"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