AutoSys Workload Automation

We all know EEM can lock down common job attributes:

• job name
• machine
• owner
• group
• application

Anyone have ideas on locking down other attributes? For Example,

• description
• std_out
• timezone

The question to ask, is why would you need to do such an open ended thing?

if there's a standard then that would be via release control or perhaps inspection jobs.

The old C SDK probably could be rigged to do such a thing, but, again I would wonder if it was worth the effort. Inspect and if you find a job out of compliance remove and save.. etc.

my feeling if you have access to the machine and the job etc. then you should have access to description etc..

just my 3 cents..

Steve C.

It is common to use the JIL Exit Verification facility to restrict or enforce standards on the description and other attributes.

This requires some C programming. If you are interested please open a support case and we can provide example code.

Please check out my latest video on the JIL Verification Exit feature just posted here.

Hope it helps.

Lenn

Chris was hoping not to have to work out the C coding at this time.  and hoped eEM could handle

Steve C.

Can you send me the link for Part 1 video as well.

Here you go:

Tuesday Tip: CA Workload Automation AE Verification Exit - autoextvj

ok, this may be an easy question to some, but where in EEM can you "lock down" job attributes?
I've watched the video, and that might be something we do in the future, but if there is something in EEM that is available, where could I find more information about it?

There is an as-base-jobtype resource class in EEM.

See the CA Workload Automation Security Guide for more information.

Here is an excerpt:

The as-base-jobtype resource class controls whether you can insert, update, override, or delete jobs belonging to predefined CA Workload Automation AE job types like Box (BOX), Command (CMD), Database Monitor (DBMON), and so on. The as-base-jobtype resource class differs from the as-jobtype resource class, which is used to control access to user-defined job types. The base job type resource class has only EXECUTE access mode while the user-defined job type resource class has all access modes.

Here are some links to the relevant information in DocOps:

CA EEM Policies for CA Workload Automation AE:

https://docops.ca.com/display/AE1136SP2p/CA+EEM+Policies+for+CA+Workload+Automation+AE

CA EEM Resource Classes for CA Workload Automation AE: https://docops.ca.com/display/AE1136SP2p/CA+EEM+Resource+Classes+for+CA+Workload+Automation+AE