The system abend of the started tasks is most probably a side effect (OEO reason 28) — this may not fix the issue.
3. ACTUAL: The Agent will activate the extended console, it ACTIVATES an extended console, it say successful, but a second later, when the Agent “inactivates” the event console the agent dies. The OS390 agent is using access registers without initializing them. We run with a list for DIAG traps successed by IBM to catch coding errors and need this corrected so we can pass out this agent to our systems. EXPECTED: The Agent stays active This console is only open if the 'defultJobClass' is not set wihin the INIfile of the agent.
Just set within the '(WLM)' section this parameter: f.ex.: (WLM) defultJobClass=C If this is set the function is scipped ($d intrdr,c) – this did not resolve the issue.
For this error, the following information is useful:
Capture of the abend JES log Agent log Agent trace (TCP/IP=9)
Resolution: Update to at least 12.0.2 Automation Engine/Components, but the latest release of 12.0.x or 12.2.x is recommended.