search cancel

Installation of z/OS Agent 12.3 fails systematically


Article ID: 187446


Updated On:


CA Automic Workload Automation - Automation Engine CA Automic One Automation


After installation of an z/OS Aagent version 12 following the standard procedure, the agent does not come up because the starting of the STC aborts.

07.31.29 STC03383  IEA630I  OPERATOR UC4CN000 NOW ACTIVE,   SYSTEM=XE23    , LU=
07.31.40 STC03383  IEA995I SYMPTOM DUMP OUTPUT  700
   700             SYSTEM COMPLETION CODE=0E0  REASON CODE=00000028
   700              TIME=07.31.29  SEQ=00406  CPU=0000  ASID=00A7
   700              PSW AT TIME OF ERROR  078C4400   801832BC  ILC 4  INTC 28

The Agent log systematically ends abruptly while listing the INI file content and does not go any further, same case if activating traces

Agent logs terminates systematically during the listing of the INI File
000369 20200325/073129.652 -          ; The Assembler-based module is used when
 000370 20200325/073129.652 -          ;
 000371 20200325/073129.652 -          name=UC4JCLE
 000372 20200325/073129.652 -          ;
 000373 20200325/073129.652 -          ; exitFunction: Name of the module's func


z/OS Agents version 12.2 and 12.3


The problem is with IBM's recommended DIAG trap set (IGVINITCPOOL) and not having defaultjob class defined in the .ini file, the Automic z/OS AGENT attempts to allocate an extended console.
It is this piece of code where the abend happens and needs to be resolved.


This behavior is considered by design

The workaround consists of forcing the defaultjobclass in the Agent configuration.

Enter the following definition in the WLM section.of the Agents configuration file.

'defaultJobClass =B '

Now the STC will start up and the agent will get operational and will connect to the AE.