Planman command line
The planman command line is used to manage intermediate production plans, trial plans, and forecast plans. It is also used to have information about the currently active production plan, to unlock the database entries locked by the plan management processes, to deploy scheduling event rules, and to replicate plan data in the database. The command runs on the master domain manager. Use the following syntax when running planman:
planman -U
planman -V
planman [connection_parameters] command
- -U
- Displays command usage information and exit.
- -V
- Displays the command version and exit.
- connection_parameters
- If you are using planman from the master domain manager,
the connection parameters were configured at installation and do not
need to be supplied, unless you do not want to use the default values. If you are using planman from the command line client on another workstation, the connection parameters might be supplied by one or more of these methods:
- Stored in the localopts file
- Stored in the useropts file
- Supplied to the command in a parameter file
- Supplied to the command as part of the command string
- command
- Represents the command you run to manage plans using the planman interface.
These are the actions you can perform with plans:
- Creating an intermediate production plan
- Creating an intermediate plan for a plan extension
- Retrieving the production plan information
- Creating a trial plan
- Creating a trial plan of a production plan extension
- Creating a forecast plan
- Unlocking the production plan
- Removing the preproduction plan
- Resetting the production plan
- Replicating plan data in the database
- Monitoring the replication of plan data in the database
You can also use planman to deploy scheduling event rules. The command is explained in: Deploying rules. Refer to the related subsections for additional details on these commands.
Comments
If you receive the AWSBEH021E
error message, check the
WebSphere Application Server
Liberty
message.log file to obtain further details of the error. Note that the
planman command is also run by JnextPlan and by the
MakePlan job.