Unable to execute AutoSys commands due to Resource bundle is not available errors

Products

• Autosys Workload Automation

Issue/Introduction

Attempting to execute any AutoSys commands (chk_auto_up, autoping, autorep, jil, etc) results in error like the following:

Resource bundle is not available while looking for key="CAUAJM_I_50054".
Resource bundle is not available while looking for key="CAUAJM_I_50055".
Resource bundle is not available while looking for key="CAUAJM_I_50128".
Resource bundle is not available while looking for key="CAUAJM_I_50038".
Resource bundle is not available while looking for key="CAUAJM_I_50044".
Resource bundle is not available while looking for key="CAUAJM_I_50045".

Environment

• Product: AutoSys Workload Automation
  • Version: All supported releases

Cause

Due to permissions on the AutoSys message files located in $AUTOSYS/messages/autosys/ directory.

-rw-------. 1 autosys autosys    128 Sep 16  2023 en.res
-rw-------. 1 autosys autosys    128 Sep 16  2023 en_US.res
-rw-------. 1 autosys autosys 674184 Sep 16  2023 root.res

Resolution

• Resolve the permissions issues with the AutoSys message files.
  chmod 644 $AUTOSYS/messages/autosys/*
• After resolving the permissions issue, you should now be able to execute the commands and receive correct response from the system.
  /opt/CA/WorkloadAutomationAE/autosys/messages/autosys

  $ chk_auto_up
______________________________________________________________________________

  CAUAJM_I_50054 Attempting (1) to Connect with Database: AEDB
CAUAJM_I_50055 *** Have Connected successfully with Database: AEDB. ***
______________________________________________________________________________

  CAUAJM_I_50128 Connected with Event Server: AEDB

  ______________________________________________________________________________

  ______________________________________________________________________________

  CAUAJM_I_50038 Checking AutoSys Primary Scheduler on Machine: your_machine.example.com
CAUAJM_I_50044 Primary Scheduler is RUNNING on machine: your_machine.example.com