HCL Workload Automation, Version 9.4

Creating an intermediate production plan

The planman with the crt option is invoked from within the JnextPlan command in one of these two situations:

The first time the JnextPlan command is run after having installed the product.
When generating a production plan after having reset the production plan using the ResetPlan command.

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

planman [connection_parameters] crt

[-from mm/dd/[yy]yy [hh[:]mm [tz | timezone tzname]]]

{-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.

-from

Sets the start time of the new production plan.

If the -from argument is omitted, then:

The default date is today.
The default hour is the value set in the startOfDay global option using optman on the master domain manager.

-to

Is the new production plan end time. The format for the date is the same as that used for the -from argument. The -to argument is mutually exclusive with the -for and -days arguments.

-for

Is the plan extension expressed in time. The format is hhhmm, where hhh are the hours and mm are the minutes. The -for argument is mutually exclusive with -to argument.

-days n

Is the number of days you want to create 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.

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

These are some examples of using the planman command assuming the date format set in the localopts file is mm/dd/yyyy:

This command creates the production plan from 03/21/2011 at 23:07 to 03/22/2011 at 23:06 in the local time zone:
```
planman crt –from 03/21/05 2307 
```
This command creates the production plan from 03/21/2011 at 09:00 to 03/21/2011 at 15:00:
```
planman crt –from 03/21/2011 0900 for 0600
```
If today is 03/21/05 and the value set for the startOfDay variable stored in the database is 0600, this command creates the production plan from 03/21/2011 at 6:00 to 03/25/2011 at 5:59:
```
planman crt –to 03/25/2011
```
This command creates a production plan from 03/21/2011 at 18:05 to 03/24/2011 at 23:00 in the time zone of Europe\Paris:
```
planman crt –from 03/21/2011 1805 tz Europe\Rome 
            –to 03/24/2011 2300 tz Europe\Rome
```