Automic z/OS Agent Fails to Start Due to Missing JCL Path Delimiters for JAVA_HOME/APP_HOME Variables

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

The z/OS Agent startup process terminates with specific error messages originating from the JZOS batch launcher, which is used to run Java applications on z/OS:

 JVMJZBL1005I Output from DD:STDENV config shell script:
 JVMJZBL2999T waiting for child shell process to complete
 JVMJZBL2999T -> waitChild()
 JVMJZBL1038E Child shell process exited with exit code: 125
 JVMJZBL2999T <- waitChild()
 JVMJZBL2999T <- adoptEnvironment()
 JVMJZBL2999T <- run()
 JVMJZBL2999T -> cleanup()
 JVMJZBL2999I JZOS batch launcher elapsed time=0 seconds, cpu time=0.010000 seconds (zOS release 29)
 JVMJZBL1042E JZOS batch launcher failed, return code=102
 JVMJZBL2999T <- cleanup()
 JVMJZBL2999T -> ~JzosVM()
 JVMJZBL2999T <- ~JzosVM()

Environment

Product: CA Automic Workload Automation - Automation Engine

Component: Automic z/OS Agent

Versions Affected: 24.x

Cause

Wrong configuration

Resolution

Check:

- if there are angle bracket (<>) delimiters in agent JCL:

export APP_HOME=</path/to/app_home>                             
export JAVA_HOME=</path/to/java_home>  

- if there are no line numbers in  the JCL you're submitting as it can cause shell script syntax errors.