AWSBHZ - Scheduler messages
This section lists error and warning messages that might be issued by the scheduler component.
The message component code is BHZ.
AWSBHZ001E
Schedulr cannot be run on this workstation, because the settings in the global options or the localopts file indicate that this workstation is not the master domain manager.
See message.
A common reason for this problem is that the procedure for switching to the backup master domain manager has not been followed correctly.
The program stops.
Verify that this workstation is the master domain manager by checking that the master variable in the global options identifies this workstation.
- If it does not, run schedulr from the master domain manager.
- If this is the master domain manager, the probable cause is that the workstation specified by the thiscpu variable in the localopts option file and the workstation specified by the master variable in the global options, are not the same. Change the localopts file so that they are the same, save the file, stop all HCL Workload Automation processes, and rerun schedulr.
AWSBHZ002E
There is not enough memory available to run schedulr.
See message.
The program cannot start.
Check the following:
- Verify if the workstation has enough memory available. Information about the memory requirements of HCL Workload Automation is provided in the Release Notes. If not, you might need to increase the memory of the workstation or make changes in memory management and paging to make more memory available to schedulr. Rerun schedulr.
- If the workstation memory is adequate, try closing all the applications that you do not need, and then rerun schedulr.
- If the problem persists, reboot the workstation, and then rerun schedulr.
- If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHZ003W
The submitted job stream has not been found or the job stream name is too long.
See message.
The program proceeds.
Resubmit the command, ensuring that all job streams that you ask schedulr to use exist, and have correctly-formed valid names.
AWSBHZ008E
Schedulr was unable to open the prodsked file for the following reason: "error_message".
Some possible reasons are that the file has been locked, or the user running schedulr does not have the rights to open it.
error_message describes the error and includes the operating system error message.
The program stops.
Attempt to correct the error given in the message. In any case it is worthwhile removing the old prodsked file if it exists, and verifying that the user of HCL Workload Automation has access rights to the HCL Workload Automation home directory.
AWSBHZ009E
You have supplied a date with the -date option, but the supplied date is not in the correct format.
See message.
Schedulr prompts you for a new date.
Provide a date in the correct format: <mm>/<dd>/<[yy]yy>.
AWSBHZ010E
Schedulr has encountered the following error when trying to find a job stream in the mastsked database: "error_text"
See message.
error_text is the message indicating why the error occurred. The mastsked database might be corrupted.
Schedulr stops.
To rebuild the mastsked database, run composer and issue the build mastsked command. Rerun schedulr. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHZ011E
Schedulr encountered the following error while checking to see if a date is defined for a particular calendar in the calendars database: "error_text".
See message.
error_text is the message indicating why the error occurred. The calendars database might be corrupted.
Schedulr stops.
To rebuild the calendars database, run composer and issue the build calendars command. Rerun schedulr. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHZ012E
Schedulr encountered the following error while searching for a specific calendar in the calendars database: "error_text".
See message.
error_text is the message indicating why the error occurred. The calendars database might be corrupted.
Schedulr stops.
To rebuild the calendars database, run composer and issue the build calendars command. Rerun schedulr. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHZ013E
Schedulr encountered the following error while reading a job stream from the mastsked database: "error_message".
See message text.
error_message contains the reason for the error and includes the operating system error message. The mastsked database might be corrupted.
Schedulr stops.
To rebuild the mastsked database, run composer and issue the build mastsked command. Rerun schedulr. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHZ014E
Schedulr encountered the following error while reading dates from the calendars database: "error_message".
See message.
error_message contains the reason for the error and includes the operating system error message. The calendars database might be corrupted.
Schedulr stops.
To rebuild the calendars database, run composer and issue the build calendars command. Rerun schedulr. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHZ015E
Schedulr encountered the following error while trying to lock the mastsked or job.sched databases: "error_message"
See message. These databases are locked before schedulr starts selecting the job streams that are to be included in the production period. Schedulr might not be able to lock the mastsked and job.sched databases because the databases might be locked by another process.
error_message contains the reason for the error and includes the operating system error message.
Schedulr stops.
Determine if another process has locked the databases, using the operating system tools (for example, fuser). Wait till that process has finished, or stop it if you are certain that you can safely do so. Rerun schedulr. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHZ016E
An internal error has occurred. While processing the mastsked database, schedulr was unable to add a job stream dependency to the internal table used by the resolve dependencies functions.
The internal error is: Not allowed to call resolve function.
Schedulr stops.
This is an internal error. Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHZ017E
An internal error has occurred. Schedulr was unable to add a job stream dependency to the internal table used by the resolve dependencies functions.
The internal error is: Bad dependencies passed to resolver.
Schedulr stops.
This is an internal error. Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHZ023E
Schedulr encountered an error parsing the contents of the job streams in the mozart database.
A previous message has given details of the error.
Schedulr stops.
Solve the problem as described in the previous error message. Rerun schedulr.
AWSBHZ024E
Schedulr has encountered the following error while trying to initialize the Security file: "error_message".
See message.
error_message describes the error and includes the operating system error message.
Schedulr stops.
Check if the Security file exists. If it does, delete it and then recreate it.
If it does not exist, create it.
Create or recreate the Security file as follows:
- Run the wmaeutil command to stop the connector.
- Run the makesec command to create the Security file.
AWSBHZ025E
The user that launched schedulr does not have the correct permissions for the schedulr actions.
To run schedulr, the user must have build access to the file object in the HCL Workload Automation Security file.
Schedulr stops.
Do one of the following:
- Edit the Security file to give the user the correct rights, stop all HCL Workload Automation processes and rerun schedulr.
- Log off and log on again as a user with the rights to run schedulr.
AWSBHZ029E
Schedulr encountered the following error while trying to lock the calendars database: "error_message".
The calendars database is locked before schedulr starts selecting the job streams that are to be included in the production period.
error_message contains the reason for the error and includes the operating system error message.
Schedulr stops.
Determine if another process has locked the calendars database. Wait till that process has finished, or stop it. Rerun schedulr. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHZ030E
Schedulr is unable to find the "calendar" calendar specified in the following job stream: "workstation_name"#"job_stream".
See message text.
workstation_name is the name of the workstation where the job stream is defined. job_stream is the name of the job stream. calendar is the name of the calendar that cannot be found.
Schedulr stops.
Confirm that the calendar specified in the job stream does not exist in the calendars database:
- If it does not exist, either remove the reference to the calendar from your job stream, change the reference to an existing calendar, or create the calendar with composer. Then rerun schedulr.
- If it does exist, there is an internal error; search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.