IBM Support

IJ47667: STDOUT/STDERR MESSAGES NOT CAPTURED TO TARGET FILE WHEN REDIRECTED BETWEEN A ZFS FILE AND AN MVS DATASET

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

  • Error Message: Diagnostic messages from JVM or attached agents
    written to standard error were not captured in JES output.
    .
    Stack Trace: N/A
    .
    N/A
    

Local fix

  • N/A
    

Problem summary

  • On z/OS, the java/io/FileOutputStream implementation relies on
    the POSIX write() API, which uses file descriptors that can only
    target either MVS datasets or UNIX System Services (USS) zFS
    files, whichever is used first. If the application does a
    freopen() call to redirect stdout/stderr streams to the opposite
    file type, messages written to stdout/stderr may not be captured
    in the redirected file.
    

Problem conclusion

  • A new Java property, com.ibm.writeToStandardOutputsUsingStreams,
    when set to true, will cause stdout/stderr messages to be
    written via file streams, which support redirection between MVS
    datasets and USS zFS files. Note, this alternate implementation
    changes the default buffering behaviour to line-buffering, and
    output may not be flushed in a timely fashion. This issue can be
    addressed by updating the buffering behaviour after freopen() to
    use no-buffering via a setbuf or setvbuf call.
    .
    This APAR will be fixed in the following Releases:
    .
    IBM Semeru Runtimes
       11              11.0.20.1
       17              17.0.7.0 (GA)
    IBM SDK, Java Technology Edition
        8    SR8 FP15  (8.0.8.15)
    .
    Contact your IBM Product's Service Team for these Service
    Refreshes and Fix Packs.
    For those running stand-alone, information about the available
    maintenance can be found at:
               https://www.ibm.com/support/pages/java-sdk
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ47667

  • Reported component name

    OPENJDK CLASS L

  • Reported component ID

    621800100

  • Reported release

    H00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-07-21

  • Closed date

    2023-08-25

  • Last modified date

    2024-01-23

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    IJ49773

Fix information

  • Fixed component name

    OPENJDK CLASS L

  • Fixed component ID

    621800100

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"H00","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
23 January 2024