Job/JCL files (J[RUNID].TXT) include file extension .sh on java-based agents
search cancel

Job/JCL files (J[RUNID].TXT) include file extension .sh on java-based agents

book

Article ID: 426720

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic One Automation

Issue/Introduction

In upgrading agents to the java-based unix agents (later 21.0 agents and all v24 Linux/UNIX agents), it was noticed that the files created to run the scripts - J[runid].TXT - now include a .sh at the end.  For instance, if the ALPHA representation of a runid (see RUNNR2ALPHA) is AAAAAA, then in version 21.0 agents, a file JAAAAAA.TXT was created on the agent server which held the commands to execute on the OS.  In the later 21.0 agents and v24 agents, it will be created as JAAAAAA.TXT.sh

Environment

OS: Linux/UNIX
Agent version: 24.x and later 21.0 java-based agents

Cause

By design

Resolution

The new behavior of the java-based agents creating a J*.TXT.sh is as designed.  This is because the shell script must be executed as a .sh since a .txt is not technically executable.  We have left the JXXXXXX.* files out of the documentation on purpose as they should not be used or altered by customers and are only for internal Automic use, so they can be changed at any time.