Controlling Command Field Content for AutoSys Command Jobs

Products

• Autosys Workload Automation

Issue/Introduction

Users often seek a mechanism to control or validate the content entered into the "command" field for command-type AutoSys jobs. The challenge arises because there is no direct Embedded Entitlements Manager (EEM) policy or built-in configuration option that has scope over the specific content of this field for command job definitions. This means that, by default, administrators lack granular control or enforcement over what commands can be specified by job creators.

Environment

• AutoSys Workload Automation
• Enterprise Event Manager (EEM)

Resolution

While a direct EEM policy for the command field is not available, you can implement custom restrictions by utilizing the JIL Verification Exit utility. This utility allows you to code and integrate your own validation logic into the AutoSys Job Information Language (JIL) processing, effectively controlling the content of the command field during job definition submission or modification.

1. Implement JIL Verification Exit: Develop custom code that intercepts JIL submissions and inspects the command attribute of command-type jobs. Your code can then apply desired validation rules (e.g., checking for specific commands, disallowed keywords, proper syntax, etc.).
2. Refer to Examples: The following resources provide examples and guidance on how to implement the JIL Verification Exit utility:
   • JIL Verification Exit Utility Overview (Video)
   • JIL Verification Exit Utility Documentation
3. Custom Coding Responsibility: The development and maintenance of the custom code for the JIL Verification Exit utility would be the responsibility of your internal team.
4. Services Engagement (Optional): If you require assistance from Broadcom for the development of such custom coding, this would fall under the scope of a professional services engagement. You can contact your Broadcom account team for details if you wish to explore this option.