Job Owner/User Name Relationship

[Corrie Kantowski]

We are have version 12.0, SP1 on a single RHL server. I am fairly new to AutoSys.  Broadcom documentation states that "...You can change the owner a job by specifying a different user ID in the job definition." Is this user ID the same as a User Name that would be found in the Credentials tab? We have User Names in the Credentials tab with a format of user@host. Broadcom documentation specifies the format of the owner field is: owner: user@host, so it seems like user ID and owner share the same pool of entries. But our jobs have the owner field populated with user alone - not user@host, and those owners correspond with the file owners on the executable files specified in the command field. So, I am confused as to why things are working. Is it because we only have a single AutoSys server, we do not need to specify host in the owner field?

So, to clarify, in our office, someone's Credentials tab may have "john@autosys", but the job's owner field has "john." This doesn't seem to fit with the specifications of the Broadcom documentation, but things are working fine. and I am not sure why!

Thank you

[Antony Askew]

Hi Corrie - They are two completely different user ids. 

The user id in the job definition 'owner:' field is the account under which the job runs, on the Agent machine ('machine:' field).

The user id in the WebUI Credentials tab is used only in the WebUI, to manage "credentials for back-end servers" - in other words if you need to use a different account in the WebUI to the default one you logged in with.  This is usually to make the Enterprise Command Line work as the commands you enter here are sent from the WebUI Enterprise Command Line to the back end AutoSys server to be executed.