Job fails with exit code -655 in a CA-WAAE to CA7 Cross Platform environment

Article Id: 6720
Status: Published
Updated On: 14-02-2018 07:56
Legacy Id: TEC1545005
Products:
CA Workload Automation AE - Business Agents (AutoSys) , CA Workload Automation AE - Scheduler (AutoSys) , CA Workload Automation Agent
Issue/Introduction:

 

I have enabled Cross Platform scheduling to run Jobs from Autosys on Linux to CA-7 on MainFrame.

This is done by setting option "CrossPlatformScheduling" in file $AUTOUSER/config.$AUTOSERV and restarting Autosys.

The CCI connection with the MainFrame is up and any CCI  command executed on Linux works fine and properly displays the CCI OIDs on MainFrame.

- "ccinet status"

- "ccinet ping <MainFrame CCI Sysid>"

- "ccii" properly displays the SUBMITC OID of the MainFrame

For example:

Oid(CA66,SUBMITC Server      ) Did( , )  type(R)

During Job submission on Autosys, following messages are displayed in the event_demon log file:

CAUAJM_I_10073 AutoSys --> Cross Platform Interface: machine=CA66 job_name=test_CA7
CAUAJM_I_40245 EVENT: CHANGE_STATUS STATUS: RESTART JOB: test_CA7 MACHINE: CA66
CAUAJM_I_40245 EVENT: ALARM ALARM: MAX_RETRYS JOB: test_CA7 MACHINE: CA66
CAUAJM_I_40245 EVENT: CHANGE_STATUS STATUS: FAILURE JOB: test_CA7 MACHINE: CA66 EXITCODE: -655
 <Have EXCEEDED the Max # of times (10) to attempt a restart. Something is wrong and needs to be investigated manually.>

 

Cause:

The local ccirmtd.prf file on the Linux server was:

     LOCAL = Linux-serveur1.ca.com Linux-serveur1 32768 STARTUP ALIAS=server1
     REMOTE = MainFrame1 CA66 32768 STARTUP HEARTBEAT=YES

 

The output of "uname -n" was

Linux-serveur1.ca.com

 

During the CCI SEND operation, Autosys picks up its local CCI SYSID to send the Job to CA-7, regardless of the CCI SYSID defined by the second parameter of the LOCAL statement in the ccirmtd.prf file.

The local CCI SYSID is built from the output of "uname -n"  or "hostname" (For example Linux-serveur1.ca.com) and not from the second parameter of LOCAL statement of the ccirmtd.prf file which is in this example Linux-serveur1.

Environment:

CA WAAE 11.3.6 on Linux & CA-7 On MainFrame.But this problem might happen with any other Autosys release.

Resolution:

Get the output of the "ccii" command showing the Oid of the local CCI applications, and modify the ccirmtd.prf file accordingly.

For example, a partial output of "ccii", displays

Oid(Linux-serveur1.ca.com,ASRBTRK Job track ) Did( , ) type(L)

type(L) means Local CCI application while type(R) means Remote CCI application

Then use this value in your ccirmtd.prf file

     LOCAL = Linux-serveur1.ca.com Linux-serveur1.ca.com 32768 STARTUP ALIAS=server1
     REMOTE = MainFrame1 CA66 32768 STARTUP HEARTBEAT=YES

 

Additional Information:

 The location of the ccirmtd.prf file on Unix/Linux is $CASHCOMP/ccs/cci/config/*/ccirmtd.prf

Any changes to this file, require a restart of CA-cci component, then the scheduler to enable the Cross Platform scheduling interface.