Adding a Run as User

This procedure describes how to add a Run as User An OS account name that is used to execute jobs on the host., which is the account name that is used to log in to an Agent or Agentless Host. To run A Control-M process that adds your job to the Run Queue of the day, according to automatic or manual scheduling, and which enables the job to execute after it fulfills its prerequisites. and execute jobs on a specific Agent or Agentless Host, you must store the account name authentication settings in one of the following scenarios:

• Windows: Jobs that execute in Logon-as-User mode, as described in ctmwincfg.
• Linux: Jobs that execute in non-root mode, as described in set_agent_mode.

Begin

1. From the icon, select Configuration.

   The Configuration domain opens.

2. From the drop-down list, select Agents.

3. The Agents page appears.

4. From the Manage drop-down list, select Run as Ussers.

   The Run as User Management pane appears.

5. From the Server drop-down list, select the Control-M/Server where the Run as User is created.

6. Click .

   The Add Run as User pane appears.

7. In the Run as User Name field, type the account name that is used to log in to the Agent or Agentless Host where the job executes.
8. From the Host Name drop-down list, select an Agent, Agentless Host, or All where the Run as User has login access, and do one of the following:
   • Agent: In the Password filed, define the password.
   • Agentless Host or All: From the Authentication Method drop-down list, do one of the following:

     • Select Password authentication, and in the Password field type the Run as User password. This enables you to execute jobs on an Agent.

     • Select Key authentication (SSH only), then from the Key Name drop-down list select an SSH key name, and in the Pass Phrase field type a logical password. This enables you to execute jobs on an Agentless Host.

       If no SSH key name appears, or you need to create a new SSH key, click Cancel and create and SSH Key, as described in Creating an SSH Key.

       You can only select All if the Configuration access level in the Admin Management role authorization is defined as Update or Full, as described in Role Authorizations.

9. (Optional) Click Test to verify the Run as User credentials are correct.

   You cannot test the Run as User credentials when you select All.

10. Click Add.

    The new Run as User appears in the Run as Users table.