ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

How did jobX get inserted when policies should have not allowed it

book

Article ID: 226696

calendar_today

Updated On:

Products

CA Workload Automation AE

Issue/Introduction

There is a job deployed in our environment that does not have EEM policies established.

We need help figuring out how the user(s) were able to deploy the job without a policy in place. 

Environment

Release : 12

Component : WA AE/AUTOSYS RELATED EEM

Resolution

It is possible that different EEM policies were in place previously which would have allowed the job to be inserted or if EEM was disabled.

For more details on autotrack see:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/autosys-workload-automation/12-0-01/reference/ae-commands/monitor-and-report-on-workload/autotrack-command-tracks-changes-to-the-database.html

If autotrack details are not available to you, if you have access to the database we might be able to see who inserted the job and when. 

The table ujo_job has fields of "CREATE_STAMP" and "CREATE_USERID".