Unix jobs do not use the .profile when running -bash jobs
search cancel

Unix jobs do not use the .profile when running -bash jobs


Article ID: 234641


Updated On:


CA Automic Workload Automation - Automation Engine CA Automic One Automation


In the Automic Job, the shell 'Bourne-Shell on Linux with .profile (-bash)' is selected however it does not invoke the information in “.profile”.

As a test the echo command is used but does not appear in the job report.


Release : All



By default, the job will try to load the information in the .bash_profile first then the .profile.  This is discussed in the following site under the Invocation section:

When bash is invoked as an interactive login shell, or as a non-interactive shell with the --login option, it first reads and executes commands from the file /etc/profile, if that file exists. After reading that file, it looks for ~/.bash_profile~/.bash_login, and ~/.profile, in that order, and reads and executes commands from the first one that exists and is readable. The --noprofile option may be used when the shell is started to inhibit this behavior.

To make sure that .profile is used instead, either ensure that there's no .bash_profile for the user or set the information required in the bash_profile file.

The wording for this has changed in 21.0.6 when -bash is chosen as a shell type in UNIX jobs from:
Bourne-Shell on Linux with .profile (-bash)

Bourne-Again-Shell; login shell, i.e. with profile loaded