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

According to the tool tip text, this argument is the number of days of job history to keep, so this job
cleans up the history of the job in the PlateSpin Orchestrate audit database after the job reaches the
age of 60 days. Data older than 60 days is to be deleted. If you want to, you can change this
parameter, or any other parameter in a job argument.
If the default value for a job argument parameter is missing, the job might fail, so you should inspect
these parameters carefully.
User Environment
As explained in Section 3.1.2, "Creating or Modifying a Job Schedule," on page
environment variables are available in the Job Scheduler only if that user utilizes the zos command
line tool and elects to pass those environment variables to the server at login time or when he or she
runs a job (running the job creates the environment variables as facts in the job). The
command passes the environment for that particular job run only.
In this walkthrough, the
zosSystem
The User Environment Tab of the Job Scheduler Editor, No User Environment Variables Available
Figure 3-12
Because there are no environment variables listed, there are none to pass to the schedule, so it is not
necessary to select the Pass User Environment check box. By default, this check box is not selected,
even if environment variables are present for a user specified to run the job.
Sometimes a job is written to work from a user's environment variables. In this case, if a user has
not logged in or has not run the job from the zos command line using the necessary environment
option, the schedule must pass those variables to the job when it is invoked.
If you associated a user who had user environment variables with this schedule, you would see a list
of those environment variables as they would be passed to the job.
The User Environment Tab of the Job Schedule Editor, User Environment Variables Available
Figure 3-13
Selecting the Pass User Environment check box in this scenario would create these variables as facts
used for this job invocation.
Constraints
As explained in Section 3.1.2, "Creating or Modifying a Job Schedule," on page
tab displays a constraint editor that you can use to create additional constraints for the job being
scheduled.
user shows no user environment variables.
28, a user's
zos run
28, the Constraints
The PlateSpin Orchestrate Job Scheduler 47