Unicenter AutoSys Job Management Integration ... - SupportConnect

Chapter
2
Real World Situations
Your company has recently moved to Unicenter AutoSys Job Management 4.5
and needs additional security for job definitions. You have recently consolidated
your disparate Unicenter AutoSys Job Management instances, so they will need
to maintain security between these jobs. By using the as-classes in eTrust,
Unicenter AutoSys Job Management 4.5 can help your company in securing your
environment while allowing it to expand.
The job scheduling group for your company consists of four groups with distinct
roles:
• Administrators - define the rules
• Developers - create the jobs and define them to the Unicenter AutoSys
Job Management database
• Scheduling operators - monitor their particular job flows and take action
on failed jobs by resubmitting them
• Casual users
Scenario 1: Defining Naming Standards
Your company has attempted to enforce naming conventions for jobs so that they
can be easily identified by the scheduling operators. However, at times, these
naming conventions are not adhered to by some developers who forget the
syntax of this nomenclature. Your scheduling administrator does not want any
jobs to be created within the database that do not follow this naming standard.
eTrust AC functions optimally when naming conventions are followed. It would
be much easier to define rules when job names, global variables, and calendars
follow a standard. As a job name standard, CA recommends that you define your
job names with something similar to the following:
applicationIdentifier_boxname_jobname
Real World Situations 2–1