AWSBID - Compiler messages

This section lists error and warning messages that might be issued by the compiler component.

The message component code is BID.

AWSBID001E

Compiler cannot find the thiscpu option in the local options file (localopts).

See message.

Compiler stops.

Add the thiscpu option to the localopts file.

AWSBID002E

Compiler cannot find the master option in either the localopts file or the global options.

See message.

Compiler stops.

Add the master option to the global options, using optman.

AWSBID003E

Compiler 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.

Compiler does not start.

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 compiler 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 compiler.

AWSBID005E

There is a syntax error in the compiler command. An incorrect date specification ("date") has been found either in the production schedule file ("file_name"), or as an argument to the -date option.

The production schedule file name is either the default prodsked or the file specified with the -input option.

date is the date string that is not correct.

file_name is the name of the production schedule file.

Compiler does not start.

Locate whether the error was in the supplied -date option or in the indicated file.

  • If the error was in the -date option, resubmit the command with a valid date argument in the format .
  • If the error was in the file, edit it. Make sure that the date specified in the first line that contains the following string Production Schedule for <date> is correct and in the following format: <mm>/<dd>/<[yy]yy>. Then resubmit the command.

AWSBID006E

Compiler was unable to open the production schedule file: "file_name". The following gives more details of the error: "system_error".

file_name is the name of the production schedule file. system_error contains the operating system error message.

Compiler stops.

Read the error message and see if you can identify the error and correct it, resubmitting the command. If the error message is not sufficiently explanatory, make the following checks:

  1. Verify that you have supplied the correct name for the production schedule file (the default name is prodsked when submitting the command. If you made an error, resubmit the command with the corrected file name.
  2. If the file name has been correctly supplied, check that this file exists, in the correct directory. If you find an error, rename or move the file and resubmit the command.
  3. If the file is present, check that the user running compiler has read permission for the file. If it does not, either change the permissions for the user or for the file, and resubmit the command. Alternatively, log off and log on again as a user with the correct permissions and resubmit the command.
  4. If the user is correct, check that there is sufficient space in the fileset of the file. If there is not, make more space and resubmit the command.
  5. If the file space is sufficient, check that the processes running on the workstation have not exceeded the maximum number of available file descriptors (see your operating system documentation for more information). Close any applications that are holding open large numbers of files, or use the operating system tools to enable a larger number of descriptors, and resubmit the command.

AWSBID007E

Compiler is unable to add the workstation records to the Symphony file. The following gives more details of the error: "error_message"

error_message contains the reason for the error.

The following is a list of possible reasons why this error could occur:

  • Compiler encounters an error when it accesses the cpudata database.
  • Compiler encounters an error when it writes to the Symphony file.
  • Compiler could not find a definition for the master workstation on the cpudata database.

Compiler stops.

When compiler cannot access the cpudata database or write to the Symphony file, the error_message can be used to determine the cause and the appropriate response.

When compiler cannot find the master workstation in the cpudata database, add the master workstation definition to the database. The name of the master workstation must match the names specified in the localopts file and the global options maintained by optman. Then rerun compiler.

AWSBID008E

Compiler has found a database incompatibility (expanded/non-expanded) or is unable to allocate memory to access the databases. The following gives more details of the error: "error_message".

error_message contains the reason for the error.

Compiler stops.

Use the dbinfo all command to make sure that all databases are either all non-expanded (0) or all expanded (1). Use the dbexpand command to convert all databases to the expanded version.

If the database cannot be opened because of a failure to allocate memory, use the operating system tools to determine how much memory compiler is using and whether it is leaking memory. If it is leaking memory, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBID009E

There is a syntax error in the compiler command. The -date option has been supplied, but the date that follows the option is not valid: "date"

date is the date specified with -date option, that is not valid.

Compiler cannot start.

Resubmit the command with a valid date argument in the format: -date <mm>/<dd>/<[yy]yy>.

AWSBID010E

Compiler was unable to read calendar information from the database. The following gives more details of the error: "error_message"

error_message contains the reason for the error.

Compiler stops.

Check the error message and resolve the error that is described. Then rerun compiler.

If the error seems to be a problem with the calendar data itself, rebuild the calendars database. To do this run composer and issue the build calendars command. Rerun compiler. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBID011E

Compiler was unable to read date information from the following calendar in the "calendar" database. The following gives more details of the error: "error_message".

calendar is the name of the calendar, the dates of which compiler is trying to read.

error_message contains the reason for the error.

Compiler stops.

Check the error message and resolve the error that is described. Then rerun compiler.

If the error seems to be a problem with the calendar data itself, rebuild the calendars database. To do this run composer and issue the build calendars command. Rerun compiler. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBID012E

Compiler was unable to add the following calendar to the Symphony file: "calendar". The following gives more details of the error: "error_message"

calendar is the name of the calendar you are trying to add.

error_message contains the reason for the error.

Compiler stops.

This is an internal error. Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBID013E

Compiler did not find the definition for the master domain manager workstation in the cpudata database.

Compiler reads workstation records from the cpudata database and adds them to the Symphony file.

Compiler stops.

Add the master domain manager workstation definition to the database with composer. If the definition is already in the database, make sure that the entries for thiscpu in the localopts file and master in the global options match the name of the master domain manager workstation in the database.

When you have found and resolved the problem, rerun compiler.

AWSBID014E

There is a syntax error in the compiler command. An incorrect number of options was supplied.

See message text.

Compiler cannot start.

To see the correct syntax for compiler, run the command: compiler -U, or look up the command in the Reference Manual.

The Reference Manual for details of the compiler syntax.

AWSBID015E

Compiler was unable to lock the jobs database. The following gives more details of the error: "error_message".

It is possible that another process has locked the database.

error_message contains the reason for the error.

Compiler stops.

Determine if another process has locked the jobs database using the tools of your operating system. Wait till that process has finished, or stop it, if you are sure it is safe to do so. Rerun compiler. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBID016E

Compiler was unable to lock the resources database. The following gives more details of the error: "error_message".

It is possible that another process has locked the database.

error_message contains the reason for the error.

Compiler stops.

Determine if another process has locked the resources database using the tools of your operating system. Wait till that process has finished, or stop it, if you are sure it is safe to do so. Rerun compiler. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBID017E

Compiler was unable to lock the prompts database. The following gives more details of the error: "error_message".

It is possible that another process has locked the database.

error_message contains the reason for the error.

Compiler stops.

Determine if another process has locked the prompts database using the tools of your operating system. Wait till that process has finished, or stop it, if you are sure it is safe to do so. Rerun compiler. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBID018E

Compiler was unable to lock the cpudata database. The following gives more details of the error: "error_message".

It is possible that another process has locked the database.

error_message contains the reason for the error.

Compiler stops.

Determine if another process has locked the cpudata database using the tools of your operating system. Wait till that process has finished, or stop it, if you are sure it is safe to do so. Rerun compiler. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBID019E

Compiler was unable to lock the calendars database. The following gives more details of the error: "error_message".

It is possible that another process has locked the database.

error_message contains the reason for the error.

Compiler stops.

Determine if another process has locked the calendars database using the tools of your operating system. Wait till that process has finished, or stop it, if you are sure it is safe to do so. Rerun compiler. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBID020E

Compiler was unable to unlock the jobs database. The following gives more details of the error: "error_message".

error_message contains the reason for the error.

Compiler stops.

This is an internal error. Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBID021E

Compiler was unable to unlock the resources database. The following gives more details of the error: "error_message".

error_message contains the reason for the error.

Compiler stops.

This is an internal error. Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBID022E

Compiler was unable to unlock the prompts database. The following gives more details of the error: "error_message".

error_message contains the reason for the error.

Compiler stops.

This is an internal error. Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBID023E

Compiler was unable to unlock the cpudata database. The following gives more details of the error: "error_message".

error_message contains the reason for the error.

Compiler stops.

This is an internal error. Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBID024E

Compiler was unable to unlock the calendars database. The following gives more details of the error: "error_message".

error_message contains the reason for the error.

Compiler stops.

This is an internal error. Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBID025E

Compiler was unable to lock the userdata database. The following gives more details of the error: "error_message".

It is possible that another process has locked the database.

error_message contains the reason for the error.

Compiler stops.

Determine if another process has locked the userdata database using the tools of your operating system. Wait till that process has finished, or stop it, if you are sure it is safe to do so. Rerun compiler. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBID026E

Compiler was unable to unlock the userdata database. The following gives more details of the error: "error_message".

error_message contains the reason for the error.

Compiler stops.

This is an internal error. Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBID027E

Compiler was unable to read the user information from the database and add it to the Symphony file. The following gives more details of the error: "error_message".

error_message contains the reason for the error.

Compiler stops.

This is an internal error. Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBID029W

You cannot initialize the centralized security option because your database is in non-expanded mode.

See message text.

Compiler stops.

Use the composer dbexpand command to convert all databases to the expanded version, or use the normal security model (non-centralized).

AWSBID200E

Line !1: The !2 name is longer than 8 bytes.

AWSBID201E

Line !1: The !2 name must begin with an alphabetic character.

AWSBID202E

Line !1: The !2 name contains one or more character that is not allowed.