UNIX jobs throw shell error after upgrade to 24.4.0
search cancel

UNIX jobs throw shell error after upgrade to 24.4.0

book

Article ID: 401675

calendar_today

Updated On: 06-19-2025

Products

CA Automic Workload Automation - Automation Engine CA Automic One Automation Automic SaaS

Issue/Introduction

After upgrading to 24.4.0, it appears that the user shell options are lost.  UNIX or Linux job no longer have a shell selected in the UNIX tab:

And the message "Select" is also missing.  Normally if no shell was chosen, it would show as follows:

if the Shell option is changed on a UNIX or Linux job to something like -ksh, it shows in upper case in the dropdown:

When the job is run, if Korn-Shell should have been used, a message like the following shows up:

The current shell (bash) is not supported; use ksh

Comparing an .xml export of an older version job shows:

<Shell>-ksh</Shell>

and the 24.4.0 version shows:

<Shell>-KSH</Shell>

Environment

Automation Engine 24.4.0 only

Cause

This is a known issue

Resolution

This is fixed with 24.4.1 which is planned to be available on June 24, 2025

Workaround:
Do not change the Shell parameter after upgrade until 24.4.1 is able to be put in place

Another possible workaround is the following:

  1. Log into client 0
  2. Open the HEADER.UNIX object
  3. Create an include called HEADER.UNIX.USER.START and add the following lines:

    !The following is added as a workaround for the issue described in Broadcom KB# 401675 and should be removed after upgrade to 24.4.1
    !In 24.4.0, the Shell was saved in upper case.  This if statement checks for Upper case KSH and sets it to lower case
    !Other shells can be added using an "or" command in the if statement
    :IF &UC_UNIX_SHELL = '-KSH'
    :  put_att UNIX_SHELL = conv_lc(&UC_UNIX_SHELL)
    :ENDIF
    !end workaround