IBM Support

PM68533: JZOS BATCH LAUNCHER DOES NOT PREPEND ENVIRONMENT DATA WITH NEWLI NE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Error Message: The JZOS Batch Launcher does not prepend its
    environment data with a newline. This means that if an
    environment script produces messages that do not end with a
    newline, JZOS cannot successfully parse its environment data and
    cannot start.
    The failure will produce messages similar to the following:
    JVMJZBL1009E Child shell process exited without printing
    environment; //STDENV should not contain 'exit'
    JVMJZBL1042E JZOS batch launcher failed, return code=101
    Enabling LOGLVL='+T' tracing will show the JZOS environment
    start string prepended with the output from the environment
    script:
    JVMJZBL2999T <OSB>ERROR<CSB>Script Error.___JZOS_ENV_START
    Where "Script Error" is the error printed by the environment
    script. This prevents JZOS from finding the environment start
    string, causing the failure messages above.
    .
    Stack Trace: N/A
    .
    

Local fix

  • Update any environment scripts to ensure that all statements
    that are printed to STDOUT or STDERR are appended with a
    newline.
    

Problem summary

  • When using the JZOS batch launcher, if the customer's
    environment script produces messages that do not end with a
    newline, JZOS will not be able to start successfully.
    

Problem conclusion

  • This defect will be fixed in:
    7.0.0 SR3 (z/OS 31-bit)
    .
    The JZOS batch launcher has been updated so that it will be able
    to start successfully even if the customer's environment script
    produces messages that do not end with a newline.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM68533

  • Reported component name

    JAVA Z/OS 31

  • Reported component ID

    620700105

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-07-10

  • Closed date

    2012-07-10

  • Last modified date

    2012-07-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

    JAVA Z/OS 31

  • Fixed component ID

    620700105

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"700","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"700","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
09 August 2022