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.

Performing a FORCE_STARTJOB thru iXp gives error message "No such file or directory"

book

Article ID: 222630

calendar_today

Updated On:

Products

CA Workload Automation iXP

Issue/Introduction

When trying to perform a FORCE_STARTJOB a pop-up message is produced with following message:

Sendevent successes:0/1
jobname1:/opt/CA/ixp/ixphome/dat/tmp/comm-20210728112123917.out (No such file or directory)

Cause

The default method for iXp to execute sendevent/jil is like

/bin/sh -c  "sendevent"

However when the Admin sets the "Sendevent Shell Command" or "JIL Shell Command" it changes the default shell invocation method to something else.
Here are some examples

/bin/bash -c

/bin/ksh -c   #Only for Solaris systems that still have ksh maybe

/bin/csh

Resolution

In the iXpAdminTool, selecting "Instance" and under "Command Line" the following 2 fields were emptied.

Sendevent Shell Command: <removed this entry, now blank>

JIL Shell Command: <removed this entry, now blank>

After saving these config changes, no need to restart iXp server, the Sendevents starting working.

Powered by Wolken Software