Object type - schedule

The following table gives the additional access keywords required to work with job streams, other than those described in Access keywords for composer actions:

Table 1. Job streams - additional access keywords
Activity Access keywords required
Conman

Dynamic Workload Console

adddepAdd dependencies to job streams in the production plan. Not valid for workstations in end-to-end environment.adddep
altpriAlter the priority of job streams in the production plan. Not valid for workstations in end-to-end environment. altpri
cancel schedCancel job streams in the production plan. Not valid for workstations in end-to-end environment.cancel
deldep schedDelete dependencies from job streams in the production plan. Not valid for workstations in end-to-end environment. deldep
displayDisplay job streams in the plan. .display
limit schedModify the limit for jobs concurrently running within a Job Scheduler. limit
release schedRelease job streams from dependencies in the production plan. Not valid for workstations in an end-to-end environment.release
replyReply to job stream prompts in the production plan. reply
showschedulesDisplay information about job streams in the production plan.list
submit sched Submit job streams into the production plan.

If the submit also identifies a second job stream with the "ALIAS" argument, the user must have "submit" access to that other job stream as well.

If the job stream is defined in a folder, then use access is required on the workstation (cpu) where the job stream is defined, in addition to access to the folder itself and the objects it contains.

Not valid for workstations in an end-to-end environment.

submit
Using the workload service assurance feature All activitiesFor any user to perform any workload service assurance activities, the TWS_user must have the following access keywords:display, modify, list