Client-wide resource directory vs the job specific directory

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

As per our documentation:

In the client-wide resource directory you should clean up unused files yourself.
The job specific cache will be cleaned up by the Automation Engine system, since its resources will be used by the respective job only.

The UC_EX_PATH_CACHE parameter points to the client-wide resource directory, but where does the user configure the job specific cache path parameter or is it generated?

What is the difference between a Client-wide resource directory vs the job specific directory?

Resolution

With the script statement :ATTACH_RES resources (from storage objects) can be transferred to an Agent and thus made available for usage with the JCL in a job execution on an Agent (Windows, UNIX).

The root directory for caching resources is set via UC_EX_PATH_CACHE in the INI file of the Agent. This is usually set as:  UC_EX_PATH_CACHE=../resources.
(Please note also the INI-file parameters FolderPermissionMask* and FolderOwner*)

When using :ATTACH_RES, it can be specified ("Usage") whether the transferred files should be placed directly in the "cache" directory or in a sub directory related to the running job (task specific/job specific). The job specific path is generated by the engine and directly sent to the Agent. In the Automation Engine Script the generated paths are available via &$AGENT_RESOURCES_CLIENT# or &$AGENT_RESOURCES_TASK# .

Please look at the documentation on ATTACH_RES