AWSJPL - Planner messages

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

The message component code is JPL.

AWSJPL001E

An internal error has occurred. The creation of the plan "plan" plan has failed.

See message.

plan identifies the plan that has not been created.

The plan cannot be created and the planner process stops.

Check that the user running the command has permission to write in the <TWSHome> directory, and that there is sufficient space on the disk. If you find a problem, correct it and rerun the command.

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

AWSJPL002E

An internal error has occurred. The workstation "workstation" cannot be added to the plan.

See message.

workstation identifies the workstation that cannot be added to the plan.

The plan is not created or extended and the planner process stops.

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

AWSJPL003E

An internal error has occurred. The domain "domain" cannot be added to the plan.

See message.

domain identifies the domain that cannot be added to the plan.

The plan is not created or extended and the planner process stops.

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

AWSJPL004E

The workstation is not the master domain manager. The workstation name in the this_cpu option: "workstation" in the localopts file does not match the workstation name of the master domain manager in the database. The plan can be managed only on the master domain manager.

See message.

workstation is the workstation name in the this_cpu option in the localopts file.

The planner process stops.

If you are using the wrong computer to run the planner process, retry the operation from the correct master domain manager.

If this workstation is supposed to be the master domain manager, the most likely answer is that you have carried out a switch manager operation on the fly (in the plan), and now need to consolidate the situation (in the database). The steps to perform are as follows:
  1. View the localopts file and check that the value in the this_cpu option is the correct workstation name.
  2. Optionally use composer or the Dynamic Workload Console to verify the name of the master domain.
  3. Use composer or the Dynamic Workload Console to modify the workstation definition of the previous master domain manager workstation:
    1. Check that the domain of the workstation is the master domain
    2. Change the workstation type from manager to fta
    A domain can remain without a manager temporarily.
  4. Use composer or the Dynamic Workload Console to modify the workstation definition of the workstation you want to become the master domain manager:
    1. Check that the domain of the workstation is the master domain
    2. Change the workstation type from fta to manager.
    Other database tables that contain this information are adjusted automatically.
  5. Rerun the planner process.
The Reference Manual or the Dynamic Workload Console User's Guide for details of how to do these actions in detail.

AWSJPL005E

The specified end time is not valid or is earlier than the start time.

See message.

The plan is not created or extended and the planner process stops.

Retry the operation, supplying a valid end time parameter.

AWSJPL006E

An internal error has occurred. A database object "object" cannot be loaded from the database.

See message.

object identifies the object that cannot be loaded from the database.

The plan is not created or extended and the planner process stops.

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

AWSJPL008E

An internal error has occurred. The database cannot be locked.

The program has tried to lock the database without success for the timeout period defined in the TWS_config_properties file.

The plan is not created or extended and the planner process stops.

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

AWSJPL009E

An internal error has occurred. The database cannot be unlocked.

The program has tried to unlock the database without success for the timeout period defined in the TWS_config_properties file.

The plan is not created or extended and the planner process stops.

Unlock the database if is locked, and retry the operation.

AWSJPL010E

An internal error has occurred. One or more of the parameters to planman are null or missing.

See message.

The plan is not created or extended and the planner process stops.

Check the parameters you supplied to the planman command. Correct any error you find and retry the command.

The Reference Manual for full details of the syntax of the planman command.

AWSJPL011E

An internal error has occurred. The class "class" has given an exception.

See message.

class identifies the class that gave the exception.

The plan is not created or extended and the planner process stops.

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

AWSJPL012E

An internal error has occurred. The object "object" cannot be added to the plan.

See message.

object identifies the object that cannot be added.

The plan is not created or extended and the planner process stops.

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

AWSJPL013E

An internal error has occurred. The object "object" is not now in the database.

The probable reason is that an object has been deleted or modified while the planner process was working, after the database was unlocked manually.

The plan is not created or extended and the planner process stops.

Retry the command.

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

AWSJPL014E

An internal error has occurred. The plan cannot be closed.

See message.

The plan is not created or extended and the planner process stops.

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

AWSJPL015E

The production or trial plan cannot be extended because it does not exist.

Either you have not created the production or trial plan or you have misidentified the plan you want to extend.

The plan is not extended and the planner process stops.

If the plan has not been created, create it with the extended times. If you misidentified the plan, rerun the command, correctly identifying the plan you want to extend.

AWSJPL016E

An internal error has occurred. A global option "option" cannot be set.

To complete the operation you have requested, planman needs to modify a global option in the database. However, this operation has failed.

option identifies the global option that cannot be set. This option might be an internal option that is not documented in the optman documentation in the Reference Manual.

The plan is not created or extended and the planner process stops.

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

AWSJPL017E

The production plan cannot be created because a previous action on the production plan did not complete successfully. See the message help for more details.

This can be caused by one of two conditions:
  • You have tried to run a plan extension before a creation has completed.
  • JnextPlan has been launched before the previous JnextPlan has run the SwitchPlan command.

The production plan is not created and the planner process stops.

  • In the former situation, check that the existing production plan has the same dates as the plan you wanted to create. If it does not, you could choose to extend the existing production plan. If you want to replace the existing production plan, reset the old production plan and then retry the command.
  • In the latter situation, either reset the plan or run planman unlock.

AWSJPL018E

The database is already locked.

The Planner cannot lock the database because is already locked.

The plan is not created or extended and the planner process stops.

Wait until no other planner processes are running and issue the command planman -unlock. Then retry the operation that failed.

AWSJPL019E

An internal error has occurred. The native libraries cannot be loaded.

See message.

The plan is not created or extended and the planner process stops.

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

AWSJPL020E

An internal error has occurred. The Windows user "Windows_user" cannot be added to the plan.

See message.

The plan is not created or extended and the planner process stops.

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

AWSJPL021W

A date in calendar "calendar" is not in ISO format.

The requested plan operation has tried to load a calendar that includes one or more dates not in ISO format. The calendar is ignored and not added to the plan.

calendar identifies the calendar that contains one or more dates not in ISO format.

The plan cannot be created or extended and the planner process stops.

Check the dates in the indicated calendar. Correct any that are not in ISO format. Run the command JnextPlan -for 0000 to regenerate the plan and include the calendars with the corrected dates.

AWSJPL022E

An internal error has occurred. The calendar "calendar" cannot be added to the plan.

See message.

calendar identifies the calendar that cannot be added.

The plan is not created or extended and the planner process stops.

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

AWSJPL023E

An internal error has occurred. The internal global option "option" cannot be obtained from the database, or is incorrect.

To complete the operation you have requested, planman needs to access a global option in the database. However, this operation has failed.

option identifies the global option that cannot be accessed. This option might be an internal option that is not documented in the optman documentation in the Reference Manual.

The plan is not created or extended and the planner process stops.

Verify that the database is running and can be reached.

If the option is one of those available for user editing, check its value and attempt to modify the value so that it is correct for planman to use; then retry the planman operation. Otherwise, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJPL024E

An internal error has occurred. The preproduction plan is not valid.

The creation of the production plan requires the availability of a valid preproduction plan.

The plan is not created or extended and the planner process stops.

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

AWSJPL025E

The application job plug-in with ID "plug-in_ID" cannot be found.

plug-in_ID is the application job plug-in identifier.

If you are submitting a job or a job stream containing a job to the plan, the job is submitted but is marked as generic job.

Check for the existence of the file plug-in_ID.jar located in the folder <installation_dir>/TWS/applicationJobPlugIn.

If the file exists and has the correct read permissions, try restarting the server.

AWSJPL026E

The job stream instance "job_stream" cannot be added to the plan. Either the plan has been temporarily locked by the database because of excessive activity (for example during the creation of a trial plan), or an internal error has occurred.

You are either running JnextPlan or have submitted a job stream to the plan.

job_stream identifies the job stream definition, an instance of which could not be added to the plan.

If you are running JnextPlan, the plan is not created or extended and the planner process stops.

If you are submitting a job stream to the plan, the job stream is not submitted but the plan is not affected.

Check if an activity like the creation of a Trial Plan was being performed when the problem occurred. If so, wait until that activity is complete before either rerunning JnextPlan or resubmitting the job stream, as appropriate.

If no such activity was being performed, an internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJPL027E

An internal error has occurred. The trial plan extension has failed because the production plan either does not exist in the database or is not valid.

Either the start time or the end time of the production plan, or both, are not defined in the database. The production plan might not have been created or is corrupt. Therefore, the trial plan cannot be extended.

The plan is not created or extended and the planner process stops.

Attempt to recreate the production plan. Then create the trial plan with the extended dates.

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

AWSJPL029E

An internal error has occurred. The job "job" cannot be added to the plan.

See message.

job identifies the job definition, an instance of which could not be added to the plan.

The plan is not created or extended and the planner process stops.

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

AWSJPL030E

The specified end time for the plan extension is not valid or is earlier than the current end time.

See message.

The plan is not created or extended and the planner process stops.

Rerun the plan extension, providing a valid end time that is later than the current end time.

AWSJPL031E

The specified plan extension period must be greater than zero.

See message.

The plan is not created or extended and the planner process stops.

Rerun the plan extension, providing a valid extension period that is greater than zero.

AWSJPL032E

An internal error has occurred. The internal file "file" could not be created.

The internal prodigy file could not be created.

The plan is not created or extended and the planner process stops.

Check that the user running planman has permission to create files in the <TWSHome> directory, and that there is sufficient available disk space. If you find a problem, correct it and rerun the command.

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

AWSJPL033E

The required object "object" could not be found in the database.

The object has been deleted, or modified, or contains a reference to an object that has not been created, or has been deleted.

The plan is not created or extended and the planner process stops.

Create the missing object and retry the planner operation.

AWSJPL034E

The supplied file name "file_name" is a reserved word and cannot be used. Alternatively, you might have omitted the file name and planman is treating the succeeding keyword as the file name.

See message.

The plan is not created or extended and the planner process stops.

Rerun the command, supplying a valid file name for the plan. Check your operating system file naming rules to determine what are valid names.

AWSJPL035E

The planner encountered the following problem while changing the properties of the database to manage its state: "error"

See message.

The plan is not created or extended and the planner process stops.

Check the database problem with the database administrator. If the problem can be solved rerun the command.

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

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

AWSJPL036E

The planner did not find the definition for the master domain manager workstation in the database, or the workstation has the ignore attribute set.

See message.

The plan is not created or extended and the planner process stops.

Check whether the problem is with the master domain manager definition or the workstation definition. Both of these conditions are anomalous, so try and discover why the problem occurred.

If you are sure that you understand why the problem occurred, correct the information in the database and retry the command.

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

AWSJPL037E

A plan with the same name is already running. If you are submitting the production plan, wait until it completes on the server before submitting another plan. If you are submitting a trial or a forecast plan, wait until the first request to create the plan completes, or submit another request using a different plan name.

A request to create a plan with the same name as the one you are trying to create has already been submitted.

The first request continues while the second one is stopped.

If you are submitting the production plan, wait until it completes on the server before submitting another plan. If you are submitting a trial or a forecast plan, wait until the first request to create the plan completes, or submit another request using a different plan name.

AWSJPL200W

The password for the Windows user "Windows_user" is not valid. It is reset to null in the plan.

The decryption of the password failed. Probably the password is corrupt in the database.

Windows_user identifies the user whose password is not valid.

Planner continues. The password is set to null in the plan.

Use composer to reset the password in the database, to avoid any further password-related problems with this Windows user.

Review the consequences of the password being set to null in the plan. If you need the password to have its correct value, run the command conman altpass to to change the password in the plan to the same value as you reset the password in the database.

AWSJPL201W

The planner process is waiting to lock the database.

Another process is using the database, and planner is waiting for the timeout period defined in the TWS_config_properties file before abandoning the attempt to use the database.

Planner waits.

If you know what process is locking the database, you might want to take steps to stop that process.

AWSJPL202W

The timeout configuration value for locking or unlocking the database is not valid. The planner process is using the default value.

The timeout configuration value for locking or unlocking the database is stored in the TWS_config_properties file. However, the value is not valid. Planner uses its hard-coded default value.

Planner continues, using the hard-coded default value for the timeout.

Check why the timeout value is not valid. Correct the problem so that the next time planner needs to use the timeout value the value is valid.

AWSJPL203W

The workstation "workstation" belongs to a domain that has no manager. For the current plan only it has been moved to the master domain.

See message.

workstation identifies the workstation that belongs to a domain that has no manager.

Planner continues. For the current plan only the workstation is set to belong to the master domain.

If it is important for the plan that the workstation is not in the master domain, make the necessary changes in the database using composer. Then run the command JnextPlan -for 0000 to regenerate the plan and include the correct domain information for the workstation. Otherwise, take no action.

AWSJPL204W

Time zone-related information has been found for one or more workstations. However, time zones are not enabled in the global options. The time-zone-related information is ignored.

See message.

Planner continues. The time-zone-related information is ignored.

Check why there is this discrepancy. If time zones should be enabled in the global options, use optman to enable them. Then run the command JnextPlan -for 0000 to regenerate the plan and include the time zone information in it. If it is correct that time zones are not enabled, to avoid the reoccurrence of this message in future plans remove the time zone-related information from the workstation definitions using composer.

AWSJPL205W

Time zone-related information has been found for job stream "job_stream". However, time zones are not enabled in the global options. The time-zone-related information is ignored.

See message.

job_stream identifies the job stream that contains time zone-related information.

Planner continues. The time-zone-related information is ignored.

Check why there is this discrepancy. If time zones should be enabled in the global options, use optman to enable them. Then run the command JnextPlan -for 0000 to regenerate the plan and include the time zone information in it. If it is correct that time zones are not enabled, to avoid the reoccurrence of this message in future plans remove the time zone-related information from the job stream definitions using composer.

AWSJPL206W

Time zones are enabled in the database but the master domain manager definition does not include a time zone. The default time zone of the system where the master domain manager is running is used.

See message.

The default time zone of the system where the master domain manager is running is used for the master domain manager's time zone.

Use composer to add the time zone definition to the master domain manager workstation definition.

If the time zone now defined for the master domain manager is different to that used in the plan, run the command JnextPlan -for 0000 to regenerate the plan and include the updated time zone information in it.

AWSJPL207W

The production plan does not exist and the planner creates it.

You are trying to extend the production plan but it does not exist. The production plan has been created automatically with the extended dates.

See message.

Ensure that it is correct that you should be extending the production plan even though it did not exist previously. If this is what was intended, take no further action.

AWSJPL208W

The job stream "job_stream" has not been added to the production plan because the workstation "workstation" has the ignore attribute set.

You are trying to add to the production plan a job stream running on a workstation with the ignore attribute set in the database.

job_stream identifies the job stream that gave the exception.

workstation identifies the workstation where want to run the job stream.

See message.

If you want to add this job stream to the production plan, unset the ignore attribute of the workstation. Otherwise, take no further action.

AWSJPL209W

The job "job" has not been added to the production plan because the workstation "workstation" has the ignore attribute set.

You are trying to add to the production plan a job running on a workstation with the ignore attribute set in the database.

job_stream identifies the job stream that gave the exception.

workstation identifies the workstation where you want to run the job.

See message.

If you want to add this job to the production plan, unset the ignore attribute of the workstation. Otherwise, take no further action.

AWSJPL505E

The ad-hoc job stream cannot be submitted because the production plan does not exist.

See message.

The ad-hoc job stream is not submitted.

Create the current plan using JnextPlan and repeat the ad-hoc job stream submission.

AWSJPL506E

The job stream "job_stream" cannot be submitted because the specified scheduled time "job_stream_scheduled_time" on the master domain manager is later than the end time of the production plan "production_plan_end_time" on the master domain manager.

See message.

job_stream_scheduled_time is the scheduled time specified for the job stream on the master domain manager (or the default scheduled time if it was not explicitly specified).

production_plan_end_time is the end time of the current plan on the master domain manager.

The job stream is not submitted.

Resubmit the job stream, specifying a scheduled time before the end of the current plan. Alternatively, extend the current plan using JnextPlan and resubmit the job stream.

AWSJPL507E

The submitted ad hoc job stream does not exist.

See message.

The ad-hoc job stream is not submitted.

Check whether you have correctly identified the ad-hoc job stream. Use composer to look at the job streams available in the database. Resubmit the ad hoc job stream identifying an existing job stream definition.

AWSJPL508E

The submitted ad hoc job stream cannot be processed because it is a draft.

See message.

The ad-hoc job stream is not submitted.

Use composer to remove the draft status from the job stream. Repeat the ad hoc job stream submission.

AWSJPL509E

The submitted ad hoc job cannot be processed because it is defined for a workstation class, which is not allowed.

See message.

The ad-hoc job is not submitted.

Either use composer to change the job definition so that it is defined for a workstation or submit a different ad hoc job which is defined for a workstation.

AWSJPL510E

The submitted ad hoc job stream cannot be processed because it is defined for a workstation class which has the ignore flag set.

See message.

The ad-hoc job is not submitted.

Check why the ignore flag is set on the workstation class. If appropriate, use composer to change the workstation class definition so that the ignore flag is unset. Alternatively, use composer to change the job stream definition so that it is defined for a workstation or workstation class that does not have the ignore flag set.

AWSJPL511W

The job or job stream "job_or_job_stream" has an external dependency on itself without the explicit matching criteria Closest preceding (previous). The planner process assumes the matching criteria to be closest preceding (previous) which is the only valid matching criteria for this type of dependency.

The job or job stream job or job_stream has an external dependency on itself which either has no explicit matching criteria, or has a matching criteria which is not Closest preceding (previous). This is the only supported matching criteria for this kind of dependency.

The dependency is resolved as Closest preceding (previous).

To suppress this warning explicitly define the dependency as Closest preceding (previous).

AWSJPL512W

The job statistics have been reset for the following job "job", because the maximum values were exceeded.

job is the job for which the statistics have been reset.

The statistics for job job are reset. The program continues.

None.

AWSJPL513E

The ad hoc job cannot be submitted because the query filters are not valid.

See message.

The ad-hoc job is not submitted.

Check the query filters, correct any errors you find, and retry the operation.

AWSJPL514E

The ad-hoc job stream cannot be submitted because its start time "job_stream_start_time" is later than the value of the valid to argument in the job stream definition.

See message.

job_stream_start_time is the start time specified for the job stream (or the default start time), which is later than the value of the valid to argument in the job stream definition.

The job stream is not submitted.

Specify a start time between the valid from and valid to values in the job stream definition.

AWSJPL515E

The ad-hoc job stream cannot be submitted because its start time "job_stream_start_time" is earlier than the value of the valid from argument in the job stream definition.

See message.

job_stream_start_time is the start time specified for the job stream (or the default start time), which is earlier than the value of the valid from argument in the job stream definition..

The job stream is not submitted.

Specify a start time between the valid from and valid to values in the job stream definition.

AWSJPL516E

The ad-hoc job stream instance cannot be viewed or modified before submission because the job stream definition on which it is based contains one or more external dependencies on a job stream defined for a workstation class.

Dependencies on a job stream defined for a workstation class are resolved differently for each job stream instance generated for each workstation in the workstation class, so any particular instance cannot be viewed or edited.

The job stream is not submitted.

Submit the job stream directly without attempting to edit or view an instance.

AWSJPL517E

The time extension specified for the creation of the production plan is not valid.

See message.

The planner process stops.

Check that the time extension parameters are correct. Check in the Reference Manual for the correct syntax for the -to and-for parameters. Correct any error you find and resubmit the command.

AWSJPL518E

An internal error has occurred. A previous job history cannot be removed from the database.

Before creating the job history statistics, planner needs to remove a previous job history as part of a regular maintenance procedure. This operation has failed.

Planner goes ahead to create new job history statistics. However, because the maintenance procedure cannot be performed, the database size increases to allow for the new statistics being created.

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

Search for assistance in determining why the previous job histories are not being removed from the database, and to restore the correct functioning of the maintenance procedure.

AWSJPL519E

An internal error has occurred. A job history cannot be created in the database.

See message.

Planner does not create the history for this job. However, planner does not stop, and continues to attempt to create other job histories.

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

AWSJPL521W

The workstation of a job is different to the workstation of its resource.Job "job" in job stream "job_stream" is for workstation "workstation". Resource "resource" is for workstation "workstation_resource"

See message.

job identifies the job that has a workstation different to that of the resource.

job_stream identifies the job stream to which the job belongs.

workstation identifies the workstation for which the job stream is defined.

resource identifies the resource that has a workstation different to that of the job.

workstation_resource identifies the workstation for which the resource is defined.

Ignoring the different workstations, planner adds the resource to the plan.

You need take no action, although you might decide to correct this situation for the future by modifying the workstation of either the job or the resource in the database.

AWSJPL522W

The workstation of a job stream is different to the workstation of its resource.Job stream "job_stream" is for workstation "workstation". Resource "resource" is for workstation "workstation_resource"

See message.

job_stream identifies the job stream that has a workstation different to that of the resource.

workstation identifies the workstation for which the job stream is defined.

resource identifies the resource that has a workstation different to that of the job stream.

workstation_resource identifies the workstation for which the resource is defined.

Ignoring the different workstations, planner adds the resource to the plan.

You need take no action, although you might decide to correct this situation for the future by modifying the workstation of either the job stream or the resource in the database.

AWSJPL523W

The variable "variable" was not found in the database and so could not be resolved.

You have defined a variable referring to a variable object defined in the database. However, that object does not exist.

variable is the variable name that could not be resolved in the database.

planner stores the variable in the plan as a variable reference and proceeds to the next action.

If no action is taken, and the variable is not defined in the local parameters file on the target workstation, the job might fail because the job requires the resolved value from the database.

If the variable is correctly defined in the local parameters file on the target workstation (using the parms utility), it is resolved at run time, and you need take no action.

Check that the indicated variable is the one that you intended. If this is not the case, change it in the job definition.

If you specified the correct variable, check that it has not been deleted in the database. Recreate the variable if necessary.

If it has not been deleted in the database, check that you have specified the variable table containing this variable in at least one of the following objects: workstation, job stream or run cycle.

Rerun JnextPlan to update the variable in the plan with the information in the database.

AWSJPL524E

The parameter "parameter" has been resolved, but the subsequent resolution makes the command string too long.

See message.

parameter is the parameter definition that makes the command string too long after it has been resolved.

The plan is not created or extended and the planner process stops.

Check the parameters defined for the job. Reduce the length of the parameters, or redesign the job so that it needs fewer or shorter parameters. Rerun JnextPlan.

AWSJPL525W

The fully-qualified file name is longer than the maximum of "maximum" bytes. The dependency is ignored and the priority is set to 0.

See message.

maximum is the maximum length of the file name.

planner ignores the file dependency and sets the priority to 0.

Check the file name. See if you can change the file name or move the file to a shorter path. If you can, change the dependency to reflect the new path.

AWSJPL526W

An external dependency in job stream "job_stream", or a job belonging to it, cannot be resolved because the matching criteria could not be satisfied.

See message.

planner ignores the dependency and continues with the next action.

Check the follows dependency and the matching criteria specified. Change the dependency so that it can be resolved.

AWSJPL527E

The specified date "date" exceeds the maximum value of 00:00:00 January 1, 2038 GMT.

See message.

date is the date that exceeds the maximum allowed value (00:00:00 January 1, 2038 GMT).

The plan is not created or extended and the planner process stops.

Check the input parameters, correct the error and retry the operation.

AWSJPL528E

The job stream cannot be submitted because either another job stream has previously been submitted to this plan instance with the same alias, or you are trying to submit two or more job streams with the same alias.

See message.

The job stream is not submitted.

Resubmit the job stream, ensuring that all submitted versions of the same job stream have different aliases.

AWSJPL529E

You have requested an extension of the existing production plan, but have supplied the -from parameter, which is only used for the creation of a plan. Use the -for or -to or -days parameters to extend the production plan.

See message.

The planner process stops.

Check that the time parameters for the extension of the plan are correct. Check in the Reference Manual for the correct syntax for the -to, -for, and -days parameters. Correct any error you find and resubmit the command.

AWSJPL530E

The trial plan cannot be created because the production plan already exists.

If the production plan already exists, the trial plan cannot be created, only extended.

The trial plan is not created.

Extend the trial plan.

AWSJPL531E

An internal error has occurred. The symphony ID cannot be updated in the preproduction plan.

See message.

The plan is not created or extended and the planner process stops.

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

AWSJPL532E

An internal error occurred while loading the HTTPS port from the JMXBrowser.

See message.

The plan is not created or extended and the planner process stops.

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

AWSJPL533E

An internal error occurred while loading the HTTP port from the JMXBrowser.

See message.

The plan is not created or extended and the planner process stops.

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

AWSJPL534W

The event processor workstation is set to ignore in the production plan. The master domain manager workstation is used as the event processor, instead.

See message.

The master domain manager workstation is used as the event processor. Planner continues.

If you do not want to use the master domain manager workstation as the event processor, unset the ignore attribute for the original event processor workstation and repeat the operation.

AWSJPL535W

The Workload Service Assurance feature is not enabled but at least one critical job was found in the plan.

See message.

The production plan will be correctly created, but the critical jobs functionality will not work.

If you do not want to use the Workload Service Assurance feature, remove the critical attribute from all jobs defined as critical and repeat the operation.

AWSJPL536W

On the remote engine the production plan was deleted by a user command.

On the remote engine the production plan was deleted by a ResetPlan command.

See message.

If you still need to monitor the remote job, first wait until a new production plan is generated on the remote engine, then rerun or submit again the shadow job.

AWSJPL537W

The remote preproduction plan was deleted by a user command.

The remote preproduction plan was deleted by a ResetPlan -scratch command.

See message.

To monitor the remote job, rerun the shadow job, or submit a new one, after a new production plan has been generated on the remote engine.

AWSJPL540E

Cleanup of old job history has failed due to the following error: "exception_message".

See message.

exception_message describes the error.

The old job history are not removed from the Database.

Fix the problem causing the failure to allow the next plan extension to correctly cleanup the job history.

AWSJPL550E

Cleanup of detailed statistics has failed due to the following error: "exception_message".

See message.

exception_message describes the error.

The detailed statistics are not removed from the Database.

Fix the problem causing the failure to allow the next plan extension to correctly cleanup the detailed statistics.

AWSJPL551E

An internal error has occurred. A detailed statistic cannot be removed from the database.

After updating the job statistics, planner removes orphan job detailed statistics as part of a regular maintenance procedure. This operation has failed.

Planner goes ahead to create new job detailed statistics. However, because the maintenance procedure cannot be performed, the database size increases to allow for the new statistics being created.

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

Search for assistance in determining why the orphan job detailed statistics are not being removed from the database, and to restore the correct functioning of the maintenance procedure.

AWSJPL552W

A cleanup operation of old job history is already running. Any other requests are skipped until the current operation completes.

See message.

A cleanup operation of old job history is still in progress.

Wait for the current operation to complete.

AWSJPL553W

The resubmit job is not added to the job stream because the pool workstation "exception_message" cannot be found in the database. Verify the value of the resubmitJobName optman property, providing the name of a valid pool workstation.

See message.

The resubmit job is not added to the job stream.

Define the resubmitJobName property providing the name of a valid pool workstation.

AWSJPL601E

The date string "date_string" in the date list expression "date_list_expression" is not a valid date in ISO format (yyyymmdd).

See message.

date_string is the string which is not a valid ISO date.

date_list_expression identifies the date list expression which contains the non-valid string.

The evaluation of the date list is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, in the API the object is not added or modified, while in the planner the job stream is not scheduled.

If using the API correct the specified ICalendar and retry the operation.

If the message appens in the planner, check if the database has been manually modified. If it has, attempt to reverse the modification and retry the operation.

If the database has not been manually modified, or you are unable to reverse a modification that has taken place, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJPL602E

An internal error has occurred. The recur expression "recur_expression" is not compliant with the ICalendar standard.

See message.

recur_expression is the recur expression which is not compliant with the ICalendar standard.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

Check if the database has been manually modified. If it has, attempt to reverse the modification and retry the operation.

If the database has not been manually modified, or you are unable to reverse a modification that has taken place, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJPL603E

An internal error has occurred. A run cycle has a non-valid ICalendar parameter: "ICalendar_parameter".

See message.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

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

AWSJPL604E

An internal error has occurred while evaluating the run cycles. The calendar "calendar_name" ("calendar_id") is not available.

See message.

calendar_name (calendar_id) identifies the calendar that is not available.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

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

AWSJPL605E

The ICalendar recur expression "recur_expression" used in the run cycle is not supported .

The recur expression used in the run cycle, although compliant with RFC 2445, is not supported by HCL Workload Automation.

recur_expression is the valid ICalendar expression that is not supported by the product.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

Correct the run cycle, specifying a supported recur expression, and retry the operation.

AWSJPL606E

The ICalendar recur expression "recur_expression" used in the run cycle, contains the unsupported token "token".

A token used in the recur expression in the run cycle, although compliant with RFC 2445, is not supported by HCL Workload Automation.

recur_expression is the ICalendar expression used in the run cycle.

token is the token in the expression that is not supported by the product.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

Correct the run cycle, specifying a supported token in the recur expression, and retry the operation.

AWSJPL607E

The ICalendar recur expression "recur_expression" used in the run cycle, contains a value for the frequency which is not supported by HCL Workload Automation.

The value for frequency used in the recur expression in the run cycle, although compliant with RFC 2445, is not supported by HCL Workload Automation.

recur_expression is the ICalendar expression used in the run cycle.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

Correct the run cycle, specifying a supported value for the frequency in the recur expression, and retry the operation.

AWSJPL608E

The ICalendar recur expression "recur_expression" used in the run cycle, contains two or more interval tokens. Only one token is permitted per expression.

See message.

recur_expression is the ICalendar expression used in the run cycle.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

Correct the run cycle, specifying only one interval token in the recur expression, and retry the operation.

AWSJPL609E

The ICalendar recur expression "recur_expression" used in the run cycle is not valid. In rules that use the byfreeday or byworkday tokens, only the daily frequency is supported.

See message.

recur_expression is the ICalendar expression used in the run cycle.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

Correct the run cycle, specifying only the daily frequency in the byfreeday or byworkday tokens, and retry the operation.

AWSJPL610E

The ICalendar recur expression "recur_expression" used in the run cycle, is not valid. An interval has been supplied that is not a positive integer.

See message.

recur_expression is the ICalendar expression used in the run cycle.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

Correct the run cycle, specifying only a positive integer for the interval, and retry the operation.

AWSJPL611E

The ICalendar recur expression "recur_expression" used in the run cycle, is not valid. The following token is not valid when using a byfreeday or a byworkday token: "token".

See message.

recur_expression is the ICalendar expression used in the run cycle.

token is the token that cannot be used when either a byfreeday or byworkday token is being used.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

Correct the run cycle, by either not specifying the indicated token, or not specifying the byfreeday or byworkday token, and retry the operation.

AWSJPL612E

The ICalendar recur expression "recur_expression" used in the run cycle, is not valid. You can use only one byfreeday token or one byworkday token. You cannot use both, or more than one of either.

See message.

recur_expression is the ICalendar expression used in the run cycle.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

Correct the run cycle, specifying only one byfreeday or one byworkday token, and retry the operation.

AWSJPL613E

An internal error has occurred. The following error message was given by the call to the ICalendar library: "error_message".

See message.

error_message is the message given by the ICalendar library

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

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

AWSJPL614E

An internal error occurred when attempting to create the following ICalendar token "token". This token cannot be added to a recur expression using a byfreeday token or a byworkday because an expression of this type including this token is not supported by HCL Workload Automation.

See message.

token is the token that, if added to the recur expression, would make it not valid.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

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

AWSJPL615E

The following run cycle "run_cycle" in the following job stream "job_stream" is not valid because the from date and time have not been specified.

See message.

run_cycle identifies the run cycle that is not valid.

job_stream identifies the job stream to which the run cycle belongs.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream run dates are not calculated, while in the planner the job stream is not scheduled.

Correct the run cycle, specifying a valid from date and time, and retry the operation.

AWSJPL616E

The ICalendar recur expression "recur_expression" used in the run cycle, contains an interval value greater than the maximum allowed: "value".

An interval value used in the recur expression in the run cycle is incompatible with the frequency type specified.

recur_expression is the ICalendar expression used in the run cycle.

value is the maximum interval value allowed for the defined type of frequency.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

Correct the run cycle, specifying a valid interval value in the recur expression, and retry the operation.

AWSJPL617E

The ICalendar recur expression "recur_expression" used in the run cycle, has the following missing token or tokens: "token_or_tokens".

See message.

recur_expression is the ICalendar expression used in the run cycle.

token_or_tokens identifies the missing token or tokens.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

Correct the run cycle, specifying the missing valid token in the recur expression, and retry the operation.

AWSJPL618E

The ICalendar recur expression "recur_expression" used in the run cycle, contains an invalid interval value. The value must be not less than 1.

See message.

recur_expression is the ICalendar expression used in the run cycle.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

Correct the run cycle, specifying a valid interval value in the recur expression, and retry the operation.

AWSJPL619E

The ICalendar recur expression "recur_expression" used in the run cycle, specifies a week number in the byday token. This is not allowed in a weekly rule.

See message. Week numbers can be used only in monthly rules.

recur_expression is the ICalendar expression used in the run cycle.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

Correct the run cycle, removing the week number in the byday clause in the recur expression, and retry the operation.

AWSJPL620E

The ICalendar recur expression "recur_expression" used in the run cycle, has a non-valid value for the week number in the byday token. Week number can be from -5 to -1 or from 1 to 5.

See message.

recur_expression is the ICalendar expression used in the run cycle.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

Correct the run cycle, specifying a valid week number in the byday clause in the recur expression, and retry the operation.

Week numbers from -5 to -1 specify the week counting back from the end of the month.

Week numbers from 1 to 5 specify the week counting from the beginning of the month.

AWSJPL621E

The ICalendar recur expression "recur_expression" used in the run cycle has been specified with two mutually exclusive tokens for the frequency "frequency".The tokens are"token1" and "token2".

See message.

recur_expression is the ICalendar expression used in the run cycle.

token1 and token2 are the ICalendar tokens that cannot both be specified with the indicated frequency: frequency.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

Correct the run cycle, specifying either token1 or token2, but not both, and retry the operation.

AWSJPL622E

The ICalendar recur expression "recur_expression" used in the run cycle has been defined with a value "value" for the list-type token "list" which is less than the minimum allowed value: "minimum".

See message.

recur_expression is the ICalendar expression used in the run cycle.

value is the value supplied for the list-type ICalendar token list.

minimum is the minimum allowed value for this token.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

Correct the run cycle, specifying a value not less than the minimum value for the token, and retry the operation.

AWSJPL623E

The ICalendar recur expression "recur_expression" used in the run cycle has been defined with a value "value" for the list-type token "list" which is greater than the maximum allowed value: "maximum".

See message.

recur_expression is the ICalendar expression used in the run cycle.

value is the value supplied for the list-type ICalendar token list.

maximum is the maximum allowed value for this token.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

Correct the run cycle, specifying a value not greater than the maximum value for the token, and retry the operation.

AWSJPL624E

The ICalendar recur expression "recur_expression" used in the run cycle has been defined with a value of zero for the list-type token "list" which is not allowed for that token.

See message.

recur_expression is the ICalendar expression used in the run cycle.

list is the list-type ICalendar token for which a value of zero has been incorrectly supplied.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

Correct the run cycle, specifying a non-zero value for the token, and retry the operation.

AWSJPL625E

The ICalendar recur expression "recur_expression" used in the run cycle has been specified with an interval value "value" which is not greater than zero.

See message.

recur_expression is the ICalendar expression used in the run cycle.

value is the incorrect value specified for the interval.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

Correct the run cycle, specifying a value for the interval greater than zero, and retry the operation.

AWSJPL626E

The ICalendar recur expression "recur_expression" used in the run cycle is specified with an incorrect weekday "weekday" in the day list.

See message.

recur_expression is the ICalendar expression used in the run cycle.

weekday is the incorrect value specified as a weekday. Permitted values are as follows:
  • SU = Sunday
  • MO = Monday
  • TU = Tuesday
  • WE = Wednesday
  • TH = Thursday
  • FR = Friday
  • SA = Saturday

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

Correct the run cycle, specifying a valid weekday, and retry the operation.

AWSJPL627E

The ICalendar recur expression "recur_expression" used in the run cycle has been specified with three mutually exclusive tokens for the frequency "frequency".The tokens are"token1", "token2", and "token3".

See message.

recur_expression is the ICalendar expression used in the run cycle.

token1, token2, and token3 are the ICalendar tokens that cannot all be specified with the indicated frequency: frequency.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

Correct the run cycle, specifying only one of token1, token2, or token3, and retry the operation.

AWSJPL628E

The ICalendar recur expression "recur_expression" used in the run cycle is defined with a token "token" that cannot be used in a rule with the frequency "frequency".

See message.

recur_expression is the ICalendar expression used in the run cycle.

token is the token that cannot be used.

frequency is the ICalendar frequency.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

Correct the run cycle, removing the incorrect token, and retry the operation.

AWSJPL629E

An internal error has occurred while evaluating the run cycles. The run cycle group "run_cycle_group_name" ("run_cycle_group_id") is not available.

See message.

run_cycle_group_name (run_cycle_group_id) identifies the run cycle group that is not available.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the job stream or run cycle group run dates are not calculated, while in the planner the job stream is not scheduled.

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

AWSJPL630E

The following run cycle "run_cycle" in the following run cycle group "run_cycle_group" is not valid because the from date and time have not been specified.

See message.

run_cycle identifies the run cycle that is not valid.

run_cycle_group identifies the run cycle group to which the run cycle belongs.

The evaluation of the run cycle rules is interrupted. In the Dynamic Workload Console the run cycle group run dates are not calculated, while in the planner the job stream that references the run cycle group is not scheduled.

Correct the run cycle, specifying a valid from date and time, and retry the operation.

AWSJPL701E

An internal error has occurred in the planner while creating a UUID. The error message is: "error_message".

The problem described in the error_message has occurred in the algorithm that creates unique identifiers.

A number of processes use the code where this error occurred.

The identifier cannot be created. The planner stops.

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

AWSJPL702E

An internal error has occurred. The planner is unable to load the status of the preproduction plan from the database because the property: "property_name" has the following incorrect value: "property_value".

This problem indicates that the database is corrupt or has been changed outside HCL Workload Automation.

property_value is the value for the property property_name in the database which is incorrect. This property is part of the preproduction plan status.

The planner stops.

If you think that you know why this value is not correct, take a backup of the database and then use the facilities of the database software to correct the value in error. Then retry the action.

If the problem persists, or you do not know why the value is incorrect, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJPL703E

An internal error has occurred. The planner is unable to load the status of the preproduction plan because of a problem accessing the database.

See message.

The planner stops.

Check the HCL Workload Automation engine log for other messages that describe the error that caused the problem. If you can resolve the problem, do so, and then retry the action.

If you cannot discover what the problem is or cannot fix it, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJPL704E

An internal error has occurred. The planner is unable to extend the preproduction plan.

See message.

The planner stops.

Check the HCL Workload Automation engine log for other messages that describe the error that caused the problem. If you can resolve the problem, do so, and then retry the action.

If you cannot discover what the problem is or cannot fix it, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJPL705E

An internal error has occurred. The planner is unable to create the preproduction plan.

See message.

The planner stops.

Check the HCL Workload Automation engine log for other messages that describe the error that caused the problem. If you can resolve the problem, do so, and then retry the action.

If you cannot discover what the problem is or cannot fix it, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJPL706E

An internal error has occurred. The planner is unable to confirm the preproduction plan.

See message.

The planner stops.

Check the HCL Workload Automation engine log for other messages that describe the error that caused the problem. If you can resolve the problem, do so, and then retry the action.

If you cannot discover what the problem is or cannot fix it, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJPL707E

An internal error has occurred. The planner is unable to save the status of the preproduction plan because of a problem accessing the database.

See message.

The planner stops.

Check the HCL Workload Automation engine log for other messages that describe the error that caused the problem. If you can resolve the problem, do so, and then retry the action.

If you cannot discover what the problem is or cannot fix it, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJPL718E

An internal error has occurred. The planner is unable to delete the preproduction plan.

See message.

The planner stops.

Check the HCL Workload Automation engine log for other messages that describe the error that caused the problem. If you can resolve the problem, do so, and then retry the action.

If you cannot discover what the problem is or cannot fix it, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJPL719W

An error occurred when the planner tried to update the preproduction plan statistics.

See message.

The planner stops. The planning activity is complete.

It is not necessary that the statistics in the preproduction plan are updated. However, the fact that planner could not update them might indicate some more-serious problem. You might decide, for example, to let one instance of this problem go by without investigating it, and take action only if the problem persists.

If you decide to take action, check the HCL Workload Automation engine log for other messages that describe the error that caused the problem. If you can resolve the problem, do so, and then retry the action.

If you cannot discover what the problem is or cannot fix it, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJPL720E

An error occurred when the planner tried to remove completed and obsolete instances from the preproduction plan.

See message.

The planner continues. The completed and obsolete instances will be removed during the next extension of the preproduction plan.

It is not necessary that the completed and obsolete instances in the preproduction plan are removed. However, the fact that planner could not remove them might indicate some more-serious problem. You might decide, for example, to let one instance of this problem go by without investigating it, and take action only if the problem persists.

If you decide to take action, check the HCL Workload Automation engine log for other messages that describe the error that caused the problem. If you can resolve the problem, do so, and then retry the action.

If you cannot discover what the problem is or cannot fix it, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJPL721E

An internal error has occurred. An error occurred when the planner tried to resolve the dependency in the preproduction plan.

See message. In normal circumstances a dependency is checked when it is created or amended, or the dependent objects are created or amended. Thus, this error should only arise in the event of some exceptional situation.

The planner continues.

If you cannot discover what the problem is or cannot fix it, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJPL722E

An internal error has occurred. An error occurred when the planner was evaluating the run cycles of job stream "job_stream". The error message is: "error_message".

The problem described in the error_message has occurred in the algorithm that evaluates the run cycles. Run cycles are validated when they are created, so this error should only arise in the event of some exceptional situation.

The instances for the job stream job_stream cannot be calculated.

The planner does not process the indicated job stream but continues with the other job streams.

Check the error_message to determine what caused the problem. If you cannot discover what the problem is or cannot fix it modifying run cycles, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJPL723E

An internal error has occurred. An internal error has occurred when the planner was evaluating the runcycles of the job stream "job_stream".

An unknown problem has occurred in the algorithm that evaluates the run cycles. Run cycles are validated when they are created, so this error should only arise in the event of some exceptional situation.

The instances for the job stream job_stream cannot be calculated.

The planner does not process the indicated job stream but continues with the other job streams.

If you cannot discover what the problem is or cannot fix it modifying the run cycles, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJPL724E

An internal error has occurred. The same thread is trying to create multiple contexts. The name of the thread is: "thread_name".

See message.

thread_name the thread that is trying to create multiple contexts.

The operation requested by the current thread is not performed.

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

AWSJPL800W

The planner (ID = "planner_ID") that you are trying to stop is busy and cannot respond. It will be stopped as soon as it becomes active again.

You have issued a request to stop the planner, but the planner is busy (for example, performing an RDBMS query) and cannot stop immediately. It will stop as soon as it finishes its current operation.

The planner is identified by the ID planner_ID.

The planner stops as soon as it finishes its current operation.

None

AWSJPL801E

You cannot run the planner to update the production plan, as another planner (ID = "planner_ID") is currently updating the production plan.

Another planner is running and updating the production plan. It is not possible to run more than one planner that updates the production plan at the same time.

The running planner is identified by the ID planner_ID.

Wait until the other planner has finished, or stop it before restarting the new planner.

AWSJPL802W

You are trying to stop a planner (ID = "planner_id") that is not running.

You are trying to stop a planner, but no planner with the indicated ID is running.

The planner that you are trying to stop is identified by the ID planner_ID.

Check the planner ID. If the ID is correct, the planner has probably already completed, and you need take no further action.

AWSJPL804W

The start time of first not complete preproduction plan job stream instance is "property_name" and it is old. Please check it running planman showinfo command.

AWSJPL805E

The planner operation cannot continue. The database has been unlocked. Rerun the operation.

See message.

The planner stops.

Some operator run planman unlock and then interrupted this operation.

Rerun the planner command if needed.