Automic Workload Automation

I am setting up a new AWA v11.2 system and am trying to get our Z/OS Mainframe to kick off a job using the CallAPI. This is working with our v9 system, but when I create a new ini file pointing to the v11 system it returns back "CP identifies itself as system '', CallAPI expects 'TEST'" I have the same version of the Windows CallAPI working on v11. I know very little about Mainframes so I don't know where to start troubleshooting, telnet did not shed any insight like I was hoping. Any pointers would be greatly appreciated. 

Hi BrandonMcClure610423 
I think best is to activate a trace at the CallAPI, this will show more details and hopefully the root cause.

Here a description on how to do a trace:
https://community.automic.com/discussion/7917/

KR, Josef

I actually did use your post as a reference and found that we are doing that by default. Someone had suggested that maybe this is being blocked by RACF

if it helps this is the error I get from the JCL

JAAIXOFT UCCALL - STEP WAS EXECUTED - COND CODE 0012

another point is that I have the agent working without issue in v11, just not the CallAPI

I think without the complete JES output of the job it’s not possible to find the root cause.

You should open a ticket with support.

This ended up being that even though the Z/Os Agent and the Windows CallAPI v9 work with v11 the Z/Os CallAPI does not