Job Profiles

A job profile defines the non-system environment variables for a job. Before running a job, the agent sets the assigned job profile on the job's target computer.

Job profiles apply to the following job types:

Command jobs
File Watcher (FW) jobs that are submitted to the legacy agent

You can use the Job Profiles - CA Workload Automation AE Administrator window to define a job profile that contains the environment variables that must be set for a job to run. After you define a profile, you can use the profile attribute or the CA WCC GUI to assign that job profile to one or more Command or File Watcher jobs.

The legacy agents (4.0, 4.5, 4.5.1, and r11) support the job profiles located in the Windows Registry. The r11.3, Release 11.3.5, or Release 11.3.6 agent can only interpret the job profiles represented as flat files. To support the jobs containing job profiles, all the job profiles in the Windows Registry are converted into flat files. The autoprofm tool is used for this conversion process and is available only on Windows. This tool can be invoked either manually from the console or by the installer during the upgrade, and it creates the flat files at the location specified by the user. You must include the full path when specifying the location of the flat files.

In Unicenter AutoSys JM 4.0, 4.5, 4.5.1, job profiles are instance-specific. In Unicenter AutoSys JM r11, job profiles are product-specific. Therefore, the same job profile name may exist under two different instances. In these situations, the autoprofm tool renames the 4.x files to profilename_instancename or the r11 files to profilename_11.0_Base to avoid overwriting information and sends a notification message to the administrator.

Similarly, if the r11.3, Release 11.3.5, or Release 11.3.6 instance already has job profiles with the same name, the autoprofm tool renames the migrated files to profilename_instancename or profilename_11.0_Base. The files are renamed to avoid overwriting the existing job profiles.

Notes:

For more information about job profiles and how to assign a job profile to a Command job, see the User Guide.
On the agent, you can define environment variables that apply to all jobs at a global agent level, scheduling manager level, or user level. For example, suppose that you want to set an environment variable for all jobs that run on an agent under a specific user (owner). Instead of defining that variable in every job definition using the envvars attribute or in a job profile, you can define the variable on the agent using the oscomponent.environment.variable_user_userid parameter. For more information about setting environment variables on the agent, see the CA Workload Automation Agent for UNIX, Linux, or Windows Implementation Guide.

More information:

View a Job Profile

Create a Job Profile

Delete a Job Profile

Modify an Environment Variable in a Job Profile

Delete an Environment Variable from a Job Profile