Closed as program error.
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 .
Update any environment scripts to ensure that all statements that are printed to STDOUT or STDERR are appended with a newline.
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.
This defect will be fixed in: 6.0.1 SR4 (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.
Reported component name
JAVA Z/OS 31
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
JAVA Z/OS 31
Fixed component ID
Applicable component levels