Unicenter AutoSys Job Management Integration ... - SupportConnect

Conclusion
eTrust> showres as-owner _default
(localhost)
Data for as-owner '_default'
-----------------------------------------------------------
Defaccess
: X
Update time : 25-Nov-2003 11:24
Updated by
: root
As you can see, all users are able to be defined as the owner, and the
owner will be able to run this job. Let’s create a new specific resource
which will deny the root user from owning a job, thereby, controlling
root from ever executing a process on the remote agent machine.
2. Define a new resource for the root user under the as-owner class, and
deny this user execute permissions.
eTrust> newres as-owner root* owner(nobody) defaccess(none)
(localhost)
Successfully created as-owner root*
Conclusion
Hopefully, by now you should have a basic understanding to how eTrust AC
integrates with Unicenter AutoSys Job Management. As you can see, there are
many additional Unicenter AutoSys Job Management user-defined classes to
eTrust AC which will help you in securing additional items like calendars and
global variables. Security does not only encompass access rights to these
Unicenter AutoSys Job Management elements, you can also use it to enforce
naming conventions for jobs as well as limit how and where a job stream will
flow.
This quick start guide is meant to be used in conjunction with the security
module in the current Unicenter AutoSys Job Management document.
Real World Situations 2–9