ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Remote Execution Agent with TCSH as the default SHELL

book

Article ID: 132992

calendar_today

Updated On:

Products

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

Issue/Introduction

We have installed the System Agent and also the Remote Execution Plug-in. Created a PROXY Job to a SHELL Script that complete with exit code 10. When we execute the PROXY Job, the job executed and completed with SUCCESS state and the exit code is 0. We were expecting the PROXY Job will failed with exit code 10. Note that the user defined for PROXY Job is setup with TCSH as the default SHELL. Refer attached for screens shots taken for the issue.

Cause

The issue happens only for the remote user default SHELL is TCSH. We have done the following but it does not help.

1. Add the shell in the agentparm.txt oscomponent.validshell=/usr/bin/sh,/bin/csh,/bin/ksh,/usr/bin/ksh,/bin/sh,/bin/bash,/bin/tcsh

2. Execute the command as tcsh shell remote_command: "tcsh -c /home/darryl/jms/jms.csh"

Environment

Workload Automation AE 11.3.6

Agent 11.4 SP1 on Linux Build 1933

Resolution

There is an agentparm property which can be set for tcsh jobs to work.

The property to set is as follows. proxy.envType.tcsh=csh

 Restart the agent and Ran the same job , it was working fine