Requesting a Tivoli Workload Scheduler (maestro) id

There are three parts to creating a new maestro id.

1. A unix logon id – created by platform services

2. An entry in the TWS Security File - created by enterprise systems management

3. A Tivoli administrator id - created by enterprise systems management

Note:

1. In requesting a unix id you will need to open a help desk request and ensure that it is directed to the appropriate department.

2. The unix id must exist on every server on which jobs are expected to run. The id must have an associated home directory on dmsdrop (eg /u/maestro.)

3. The Tivoli admin id is necessary for using the new Java-based Job Scheduling Console, which is now the only means for users to interact with TWS.

To request a new id and Security File entry, you will need to supply the following:

1. A list of all servers you expect to be running jobs on

2. A list indicating the initial letters (two or more) you expect to use in naming your jobs and schedules

3. The name of the id you wish to use to run jobs – for your guidance it should reflect some reality connected with the work you are engaged in Example: pshrbnpy – peoplesoft human resources benefits and payments

4. Maestro access requirements – for example display only, creating submitting jobs or schedules, releasing dependencies, creating or submitting jobs using another login id. If you are aware of an existing id, which already has the rights you need, it is enough to name it.

5. You must supply the individual unix ids of the personnel you expect to be creating and submitting jobs. TWS objects can no longer be created using the group id’s such as lradmin, malltele etc.

6. If the server is new to TWS, indicate which environment it is to be in – currently either production or development.