HCL Workload Automation, Version 9.4

Creating an intermediate plan for a plan extension

The planman command with the ext option is invoked from within the JnextPlan command when:

JnextPlan is invoked.
A production plan, represented by the Symphony file on the master domain manager, already exists.

The result of running this command is the creation of a new intermediate production plan, named Symnew, covering the extra time the new production plan that is being generated will span. The following syntax is used:

planman [connection_parameters] ext

{-to mm⁄dd⁄[yy]yy[hh[:]mm[tz | timezone tzname]] |

-for [h]hh[:]mm [-days n] |

-days n}

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.
-to: Sets the end time of the extended production plan. The -to argument is mutually exclusive with the -for and -days arguments.
-for: Sets the length of the production plan extension. The format is hhhmm, where hhh are the hours and mm are the minutes. The -for argument is mutually exclusive with the -to argument.
-days n: Sets the number of days you want to extend the production plan for. The -days argument is mutually exclusive with the-to argument.

Note:

Make sure you run the planman command from within the JnextPlan command.
The format used for the date depends on the value assigned to the date format variable specified in the localopts file.
When the production plan is extended the numbers associated to prompts already present in the plan are modified.

If no -to, -for, or -days arguments are specified then the production plan is extended by one day.