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

Displays command usage information and exit.
Displays the command version and exit.
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
For an overview of these options see Setting up options for using the user interfaces. For full details of the configuration parameters see the topic on configuring the command-line client access in the HCL Workload Automation: Administration Guide.
Represents the command you run to manage plans using the planman interface. These are the actions you can perform with plans:

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.


If you receive the AWSBEH021E error message, check the WebSphere Application Server Liberty Basemessage.log file to obtain further details of the error. Note that the planman command is also run by JnextPlan and by the MakePlan job.