Novell PLATESPIN ORCHESTRATE 2.0.2 - DEVELOPMENT CLIENT REFERENCE 08-28-2009 Reference page 36

Figure 3-10
The jobargs are defined by the deployed job. Some jobs might already have a default value
displayed, but others must have values specified in order for the job to be able to run.
IMPORTANT: Job arguments displayed in blue are required. You must supply data in the
accompanying fields.
A job argument defines the values that can be passed in when a job is invoked. These values let you
statically define and control job behavior. To learn more about each job argument, mouse over each
jobarg line to display tool tip text.
The Job Scheduler uses the values you enter into the fields of this area to build a jobargs namespace
in the policy for this job.
Each job argument has an accompanying Lock check box. When Lock is not selected, the
accompanying job argument uses the default value specified in the job's policy. When Lock is
selected, the value specified in the field is locked down and overrides the default value in the policy.
A locked value continues to be used even if the policy value is modified.
You can click Restore Jobargs to restore job arguments to the values specified in the job policy. This
function removes any changes you might have specified in the Job Scheduler and deselects all Lock
check boxes.
For more information, see
Developer Guide and
User Environment
This tab displays an area (in the lower left corner of the Job Schedule Editor) that includes the Pass
User Environment check box. Select this check box if you want to pass the assigned user's
environment variables to the job when it runs. When environment variables are recorded on the user
account, selecting the Pass User Environment check box makes those environment variables
available to the job and joblet.
A user's environment is recorded under the
when a user logs in to PlateSpin Orchestrate and is persisted until changed. A user's environment
variables can be uploaded with the zos command line tool at login time in one of two variations:
zos login --user=foo --env
This command uploads the entire environment to the Job Scheduler. The upload can also be
seen on the User object in the Orchestrate Development Client.
zos login --user=foo --env=PATH
When the user logs in, he or she can specify one or more environment variables to use at login.
The example above would result in just the PATH environment variable being uploaded.
36 PlateSpin Orchestrate 2.0 Development Client Reference
The Job Arguments Area of the Job Scheduler View
"Job Arguments and Parameter
Reference.
Lists" in the
fact on his or her account. This fact can be set
user.env
PlateSpin Orchestrate 2.0