HCL Workload Automation, Version 9.4

AWSTPL - Time planner messages

This section lists error and warning messages that might be generated by the time planner module.

The message component code is TPL.

AWSTPL001E   The critical jobs predecessors network table is not available.

Explanation

Either the plan that contains the critical jobs predecessors network table is not present and in the correct state, the workload service assurance feature is not enabled, or an internal error has occurred.

System action

The connector stops and the operation cannot be performed.

Operator response

Check for the presence and state of the plan that includes the critical jobs predecessors network table. Check that the workload service assurance is enabled. Solve any error you find and retry the operation.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSTPL002E   The planned start time was not reloaded.

Explanation

The planned start time was not reloaded because the program incurred an error while reading the information from the database.

System action

The planned start time is recalculated. It will almost certainly be different from the saved planned start time.

Operator response

If you are concerned about the impact of a possible change in the planned start date, check the job information.

To understand what caused the problem, and to ensure it does not repeat, check whether the database is up and running and the connection is good by issuing a composer command:

  • If the command fails, there is a problem with the database or the access to it. Get your HCL Workload Automation or database administrator to check why the database cannot be accessed, or is not responding. When the database problem is fixed the problem reloading the planned start time will not re-occur.
  • If the database command succeeds, it means that an internal error must have caused the failure to reload the planned start time. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSTPL003E   A loop condition was detected in the critical job predecessors network.

Explanation

See message.

System action

The connector stops and the operation cannot be performed.

Operator response

Redefine the dependencies to avoid the loop, and retry the action.

AWSTPL005E   An error occurred while persisting the planned start times in the database.

Explanation

Each time a new plan is created, planned start times are calculated for each job in the plan.

The workload service assurance feature uses these planned start times for its processing.

These values are persisted in the database to be reloaded if the WebSphere Application Server is restarted or if the master domain manager is switched.

But an internal error has occurred and the planned start times were not persisted in the database.

System action

JnextPlan continues, but planned start times are not persisted. This means that the planned start times will be recalculated if the WebSphere Application Server is restarted or the switch manager action is performed, giving results that might be different than expected.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSTPL006E    An inconsistency is present in the critical jobs predecessors network table.

Explanation

See message.

An internal error has occurred.

System action

The processing continues. The workload service assurance feature might not work properly.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.