Resetting the production plan
The following script is used to either reset or scratch the production plan:
ResetPlan [connection_parameters] [-scratch]
where:
- connection_parameters
- Defines the settings to use when establishing the connection using HTTP or HTTPS through WebSphere Application Server to the master domain manager. For more information refer to Planman command line.
- If you reset the production plan, the preproduction plan
is kept, it is updated with job statistics, and it is used later to
generate a new production plan. This means that when you create a
new production plan, it will contain all job stream instances which
were not in COMPLETE state when you run the ResetPlan. The
steps performed by the product when resetting the production plan
are the following:
- The current Symphony file is archived.
- The job statistics are updated.
- If you scratch the production plan, the preproduction plan
is scratched too. The preproduction plan will be created again based
on the modeling information stored in the database when you later
generate a new production plan. This means that the new production
plan will contain all job stream instances scheduled to run in the
time frame covered by the plan regardless of whether or not they were
already in COMPLETE state when the plan was scratched. The steps performed
by the product when scratching the production plan are the following:
- The current Symphony file is archived and the plan data replicated in the database is deleted.
- The job statistics are updated.
- The preproduction plan is scratched.
Note: If you use the -scratch option, make sure you run dbrunstats before the JnextPlan script. See the Administration Guide for details on dbrunstats.
When you run ResetPlan command a joblog file is created in the directory <TWS_INST_DIR>\TWS\stdlist\<DATE>, where <TWS_INST_DIR> is the HCL Workload Automation installation directory and <DATE> is the date when the script run.