No output is generated when running autosys command in ECLI
search cancel

No output is generated when running autosys command in ECLI

book

Article ID: 4838

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent

Issue/Introduction

When executing an Autosys command thru ECLI (Enterprise Command Line Interface), no output is being shown in the 'Output' section nor in the 'Errors' section.

Environment

Release: All Supported Versions
Component: CA WCC

Cause

ECLI communicates to Autosys using the Command Sponsor binaries. Command from WCC is being passed thru iGateway to the Command Sponsor binaries who builds environment to execute the autosys command. It will check the file 'instance2script.map' to see if instance and it's script path is defined.

Also it requires an entry that will execute the autosys command also called AutosysCommandWrapper. This line was missing in instance2script.map file.

Resolution

On the Autosys box, run following steps:

1. cd $IGW_LOC

2. edit file 'instance2script.map

3. add following line

ASCMDWRP     /opt/CA/SharedComponents/iTechnology/AutoSysCommandWrapper.exe