HCL Workload Automation, Version 9.4

Unlocking the production plan

When HCL Workload Automation starts to create the production plan, it locks the definitions of scheduling objects in the database and then unlocks them either when the creation of the production plan is finished or if an error condition occurs. The lock is applied to prevent object definitions from being modified when the production plan in generated or extended. If the processing ends abnormally the database entries might remain locked. Only users with build access on the prodsked file object type specified in the security file on the master domain manager are allowed to unlock the database. The command used to perform this action is:

planman [connection_parameters] unlock

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.
Note: You can install the HCL Workload Automation Command Line Client feature on fault-tolerant agents and systems outside the HCL Workload Automation network to issue from those systems the planman unlock command.