AWSBHU - Conman messages
This section lists error and warning messages that might be issued by the conman component.
The message component code is BHU.
AWSBHU001E
Conman encountered an error when attempting to open the Symphony file: the file does not exist or conman could not find it. The following gives more details of the error: "error_text".
See message.
error_text is the error message. It supplies you with more details about the error causes.
The command is not processed.
If the Symphony file exists verify that the owner is the HCL Workload Automation user and that the user has permission to access and modify it. If the program is not able to read the Symphony file or the Symphony file is not present, follow the procedure described in the section in this guide on Symphony file corruption.
AWSBHU002E
Conman encountered an error when attempting to open either the Mailbox.msg file or the Intercom.msg file. The following gives more details of the error: "error_text".
The file might not exist, or conman might not have permission to access it.
error_text contains more details about the causes of this error.
The command is not processed.
Check that both of these files exist, and that conman has permission to access them. To recreate these files, follow this procedure:
- Run the conman stop command with a wait argument
- Run the conman start command.
If the problem occurred on z/OS, a memory dump has been taken to aid HCL Software Support with problem determination. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm., supplying the following information:
- A tar file of the HCL Workload Automation work directory (<TWS_home>)
- The memory dump.
AWSBHU003E
Conman encountered an error while initializing because the Security file does not exist or could not be found. The following gives more details of the error: "error_text"
See message.
error_text is an error message.
Conman stops.
Verify if this file exists. If it does not, try to recreate it, as follows:
- Run the wmaeutil command to stop the connectors.
- Run the makesec command to create the Security file. On Windows you must use the wmaeutil command before using the makesec command, while on UNIX they can be performed in either sequence.
- Restart conman.
AWSBHU004E
The job logon name you specified is not valid.
You have issued a command that includes the job parameter logon or streamlogon. The value for this parameter includes the string \\, which is not valid in a user id.
The command is not processed.
Modify the value of the job parameter logon or streamlogon, and resubmit the command.
AWSBHU009E
Conman encountered a problem trying to read the Symphony file. The following gives more details of the error: "error_text"
See message.
error_text is the error message, which provides you with more details about the error causes.
Conman stops.
Check if the Symphony file exists. If it does, verify that the owner is the HCL Workload Automation user and that the user has the rights to access and modify it. If the program is not able to read the Symphony file or the Symphony file does not exist, follow the procedure described in the chapter in this guide on Symphony file corruption.
AWSBHU010E
For record # "record_number", conman found an incorrect Symphony file record type: "record_type_found". It was expecting the following type: "record_type_expected".
See message.
record_number is the record number.
record_type_expected is the record type expected.
record_type_found is the record type found.
Conman stops.
Try to recreate the Symphony file. Follow the procedure described in the chapter in this guide on Symphony file corruption. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU016E
One of the values specified for a numeric argument is not numeric.
You have specified a non-numeric value to an argument of a command that is expected to be numeric.
The command is not processed.
Check the syntax of the issued command and verify that the values supplied for all the arguments are syntactically correct. Then re-issue the command.
AWSBHU017E
A value specified for a range-limited numeric argument is below the minimum permitted value. The permitted range is from: "minimum" to "maximum".
See message.
minimum is the minimum permitted value. maximum is the maximum permitted value.
The command is not processed.
Check the syntax of the issued command and verify that the values of any range-limited arguments are within the indicated range. Then re-issue the command.
AWSBHU018E
A value specified for a range-limited numeric argument is above the maximum permitted value. The permitted range is from: "minimum" to "maximum".
See message.
minimum is the minimum permitted value. maximum is the maximum permitted value.
The command is not processed.
Check the syntax of the issued command and verify that the values of any range-limited arguments are within the indicated range. Then re-issue the command.
AWSBHU021E
The agent on workstation: "workstation_name" cannot be started because it has not got the latest Symphony file version.
This error occurs when you use the start command to start an agent on a remote workstation that has not been linked for some reason.
workstation_name is the remote workstation name.
The command is not processed.
Use the conman link command to initialize the workstation.
AWSBHU022E
The time value specified as an argument is incorrect. It must be numeric, between 0000 and 2359.
See message. HCL Workload Automation uses a form of the 24-hour clock without a separator between minutes and hours, so that, for example, 9:30 a.m. is written as 0930 and 3 p.m. as 1500.
The command is not processed.
Check the syntax of the issued command and verify that the values of any time arguments are between 0000 and 2359. Then re-issue the command.
AWSBHU023E
You have issued an opens job qualifier with incorrect syntax.
See message.
The command is not processed.
Check the syntax of the issued command and verify that the values of opens job qualifiers are syntactically correct. Then re-issue the command.
AWSBHU024E
The mozart directory cannot be accessed or is missing some files.
Usually this error happens when the mozart database on the master domain manager is not accessible to the workstation where you issued the command, and in one of the following situations:
- You have tried to add a prompt dependency to a job or job stream.
- You have tried to submit a job or job stream that has a prompt dependency.
The command is not processed.
Verify the mozart directory properties. If you want to manage a prompt dependency, the mozart directory (<TWSHome>/mozart) on the master domain manager must be accessible, either mounted or shared. If the mozart directory is shared and mounted, verify that the HCL Workload Automation user has the rights to access its files.
If you have found an error, correct it and re-issue the command.
If you cannot find any error, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU025E
Conman either cannot find the job stream in the Symphony file, or the specified workstation name is not correct.
See message.
The command is not processed.
Take the following steps:
- Look in the Symphony file and verify if the job stream exists and if its name has been correctly specified.
- If the job stream details are correct, verify that the workstation name identifies an existing workstation.
- If an error is found, correct it and re-issue the command.
- If no error is found, the Symphony file might be corrupt. In this case follow the procedure described in the chapter in this guide on Symphony file corruption.
If the problem persists, this is an internal error, and search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU028E
The recovery action is not correct. It must be one of the following: STOP, CONTINUE, RERUN.
You have supplied a recovery action that is incorrectly typed, or not supported. Only the following are permitted:
- recovery=STOP
- recovery=CONTINUE
- recovery=RERUN
The command is not processed.
Reissue the command, supplying one of the permitted recovery actions.
AWSBHU029E
Fatal: Should not be here: !1 [#!2].
AWSBHU030E
DCM Pak required to use this feature.
AWSBHU031E
The number of minutes must be an integer value between 0 and 59.
The number of minutes must be an integer value between 0 and 59.
The command is not processed.
Specify the number of minutes as an integer number between 0 and 59 and retry the operation.
AWSBHU032E
You have issued a rerun command that does not uniquely identify a workstation.
Conman shows this error when the rerun command you issued does not identify a unique workstation name in the from argument. This command cannot be applied to more than one workstation at one time.
The command is not processed.
Specify the correct workstation name in the from argument, without the use of wildcards, and rerun the command.
AWSBHU033E
You have supplied more instances of a dependency option than are permitted by the issued command.
See message.
The command is not processed.
Rerun the command specifying the correct number of dependency options.
AWSBHU034E
You have not supplied a mandatory selection argument (job, or job stream, for example).
You have issued a command that has a mandatory selection argument (to select a job, or job stream, for example) and you did not specify one. The selection specifies the object or set of objects the command acts on.
The command is not processed.
Rerun the command specifying a valid selection argument.
AWSBHU035E
You have issued a command with a dependency keyword (follows, needs, opens, prompt), but the value associated with the keyword is not valid.
See message.
The command is not processed.
Check that the value associated with the dependency keyword is syntactically correct, and that any object it refers to exists. Correct the error and re-issue the command.
AWSBHU037E
Conman has stopped with the following internal error: Non-valid trap action.
See message.
Conman stops.
Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU038E
Conman cannot run the command because the command string has too many characters.
See message. The number of characters accepted by the command line is operating system-dependent.
The command is not processed.
Check your operating system documentation to determine the maximum acceptable length. Change the command to conform to this restriction. You might need to divide the command into two or more commands.
AWSBHU039E
You have issued a command containing an incorrect argument keyword. The acceptable keywords for this command are as follows: "keyword_list"
See message.
keyword_list is the list of accepted argument keywords.
The command is not processed.
Correct the argument keyword to one shown in the list , and re-issue the command.
AWSBHU040E
You have issued a command containing an incorrect delimiter. The accepted delimiters are the following: "delimiters"
See message.
delimiters is a list of accepted delimiters or qualifiers for this command.
A delimiter or qualifier is a special character that separates two commands, selection items, parameters, or values in an argument. There are several types:
- The command delimiter: $ - separates one command from the next command.
- The argument delimiter: ; - separates arguments.
- The repetition delimiter: , - separates different values, for example range values.
- The value delimiter: = - separates a keyword and its value.
- The selection qualifier: - separates selection items
- + - indicates additional selection criteria
- ~ - indicates exclusion criteria.
The command is not processed.
Correct the delimiter you have used to conform to the supplied list and to correspond to the indicated usage.
AWSBHU041E
You have entered the following command: "command ", which requires access to the Symphony file. However, either the Symphony file does not exists or conman cannot find it.
See message.
command is the conman command requiring the Symphony file.
The command is not processed.
If you have previously stopped a conman command by using the Control+C key combination, close the conman session and open a new one, otherwise follow this procedure:
- Look for the Symphony file
- If the Symphony file exists verify that the owner is the HCL Workload Automation user and that the user has the rights to access and modify it
- If the Symphony file exists, and the access permissions are correct, it means that it is corrupted. Follow the procedure described in the chapter in this guide on Symphony file corruption.
- If the Symphony file is not present, follow the procedure described in the chapter in this guide on Symphony file corruption.
When you have completed the corrective action, retry the command.
AWSBHU042E
You have entered the following command: "command", which requires access to the current (latest) Symphony file. However, the Symphony file that conman has found does not contain the latest production plan.
See message.
command is the conman command requiring the Symphony file.
The command is not processed.
Set the production plan (Symphony file) to the current, using the conman setsym command.
AWSBHU043E
You have issued a command that specifies a dependency. However, either conman cannot find the dependency in the Symphony file, or the command has an invalid dependency argument.
See message.
The command is not processed.
Follow this procedure:
- Check the dependency argument that you supplied is valid and correctly formed.
Verify if the object on which the dependency relies exists in the Symphony file.
AWSBHU044E
You have issued a command with a file dependency, but the path name of the file you have supplied is not fully qualified (absolute).
See message.
The command is not processed.
Re-issue the command using a fully qualified filename.
AWSBHU045E
You have issued the following command: "command " with one or more arguments, but this command does not have any arguments.
See message. For example, use the command redo to edit and re-issue the previous command, but it does not have any arguments. If you type redo showjobs, this message is displayed.
command is a conman command.
The command is not processed.
Reissue the command without arguments.
AWSBHU046E
Conman has encountered an internal error; encountering the following incorrect selection type: "selection_type". The problem was encountered in the following source file "file_name", at line "line_number".
See message.
selection_type is the selection type found.
file_name and line_number identify the line of source code where the problem was found.
Conman stops.
Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU047E
A command has been supplied without its required selector.
Conman commands have the following structure:
- The command name
- A selector that identifies the object or objects on which the command acts. The selector might or might not use a keyword. For example, the showjobs command has no keyword; you just enter the identifier of the job you want to look at. However, the adddep command uses the keywords: job and sched, to identify whether it is acting on a job or a job stream.
- One or more arguments that control the action of the command on the object or objects
You have not supplied an identifiable selector.
The command is not processed.
Re-issue the command, adding a valid selector after the command name and before the arguments.
AWSBHU048E
A command has been supplied with an ambiguous selector.
Conman commands have the following structure:
- The command name
- A selector that identifies the object or objects on which the command acts. The selector might or might not use a keyword. For example, the showjobs command has no keyword; you just enter the identifier of the job you want to look at. However, the adddep command uses the keywords: job and sched, to identify whether it is acting on a job or a job stream.
- One or more arguments that control the action of the command on the object or objects
The selector supplied does not unambiguously identify the object on which the command must act. The command might require a selector keyword that you have not supplied.
The command is not processed.
Re-issue the command, ensuring that the selector contains a keyword, if required, and that the syntax indicated in the Reference Manual has been followed.
AWSBHU049E
You have issued a command with a selector keyword, but the supplied selector keyword is not valid.
Conman commands have the following structure:
- The command name
- A selector that identifies the object or objects on which the command acts. The selector might or might not use a keyword. For example, the showjobs command has no keyword; you just enter the identifier of the job you want to look at. However, the adddep command uses the keywords: job and sched, to identify whether it is acting on a job or a job stream.
- One or more arguments that control the action of the command on the object or objects
The selector supplied is not a valid selector keyword.
The command is not processed.
Re-issue the command, adding a valid selector after the command name and before the arguments.
AWSBHU050E
You have issued a command with a selector keyword, but the supplied selector keyword is not valid for this command.
Conman commands have the following structure:
- The command name
- A selector that identifies the object or objects on which the command acts. The selector might or might not use a keyword. For example, the showjobs command has no keyword; you just enter the identifier of the job you want to look at. However, the adddep command uses the keywords: job and sched, to identify whether it is acting on a job or a job stream.
- One or more arguments that control the action of the command on the object or objects
The selector keyword supplied is not a valid selector keyword for this command.
The command is not processed.
Re-issue the command, adding a valid selector after the command name and before the arguments.
AWSBHU051E
You have issued a command with a valid selector keyword, but have omitted to identify the object.
Conman commands have the following structure:
- The command name
- A selector that identifies the object or objects on which the command acts. The selector might or might not use a keyword. For example, the showjobs command has no keyword; you just enter the identifier of the job you want to look at. However, the adddep command uses the keywords: job and sched, to identify whether it is acting on a job or a job stream.
- One or more arguments that control the action of the command on the object or objects
You have probably issued a command with its selector keyword, but have not included the object identifier. For example, issuing adddep job without identifying which job.
The command is not processed.
Re-issue the command, adding a valid selector after the command name and before the arguments.
AWSBHU052E
You have issued a command with the job qualifier state, but the identified state is not appropriate for the object identified in the command.
See message. For example, stuck is not a valid state for a job and pend is not a valid state for a job stream.
The command is not processed.
Change the value of the state argument to a valid state for the object of the command, and re-issue the command.
AWSBHU053E
You have issued a command that identifies a file, but the path name of the file you have supplied is not fully qualified (absolute).
See message.
The command is not processed.
Re-issue the command using a fully qualified file name.
AWSBHU054E
You have issued a show... command other than showjobs, and have used the argument "argument" without its associated ;deps argument.
The ;info argument is only used on its own in the showjobs command. In all other commands where it appears, it is one possible value of the ;deps argument.
The command is not processed.
Correct the syntax and re-issue the command.
AWSBHU055E
You have used one of the limit commands, but did not supply a value for the limit, or you supplied it with an incorrect syntax.
See message.
The command is not processed.
Re-issue the limit command providing a value for the limit. You can enter 0 through 1024.
AWSBHU056E
You have used the fence command, but did not supply a value for the new priority level, or you supplied it with an incorrect syntax.
See message.
The command is not processed.
Re-issue the fence command providing a value for the priority level. You can enter a numeric value from 0 to 101, hi (= 100), or go.
AWSBHU058E
The command issued for workstation "workstation_name" cannot be performed, because the workstation is an extended agent, where the command is not supported.
See message.
workstation_name is the extended agent workstation name.
The command is not processed.
You cannot use this command on the selected workstation. If you have selected the extended agent workstation in error, change the command to identify a different workstation and re-issue the command. If you have selected the wrong command, issue a different command.
AWSBHU059E
You have identified a file name that has a base name greater than "maximum_length" bytes. This file name is not permitted.
The file base name is the name of the file, including the extension and the dot separator, but excluding the directory names in the full path. For example, myfilename.txt is 14 bytes.
maximum_length is the longest file base name accepted.
The command is not processed.
Shorten the name of the file so that it is no greater than the value of the maximum_length indicated and re-issue the command.
AWSBHU060E
You have issued a command that has attempted to modify or delete the EXTERNAL job stream. This is not permitted.
The EXTERNAL job stream is used to monitor the status of internetwork dependencies, and cannot be modified or deleted.
The command is not processed.
To modify an internetwork dependency for a given job you have to use the conman adddep and deldep commands on that job.
AWSBHU061E
The domain manager of this workstation cannot be found in the Symphony file.
The circumstances are one of the following:
- You issued a switchmgr command specifying a domain and a new manager.
- You issued a start command with the mgr option on this workstation.
In either case, you tried to switch to a domain manager that conman cannot find in the Symphony file.
The command is not processed.
If HCL Workload Automation is running several switchmgr or start commands from several workstations, it is possible that it has not completed one or more of the commands, and until those commands are completed cannot successfully run this command. Wait until it has completed these activities.
If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU062W
The MGR option is valid only on the local workstation. Ignoring it.
A command has been issued remotely using the MGR option, which is valid only on the local workstation.
The command is processed, ignoring the MGR option.
None.
AWSBHU063E
The domain manager "current_manager" is not in the same domain as the workstation that you want to become the new domain manager: "new_manager".
There are two possibilities:
- You are using the switchmgr command to switch the domain manager of your domain to a fault-tolerant agent not belonging to your domain.
- You issued a start command with the ;mgr option on the local workstation, to make it exchange roles with its current domain manager (this method of switching domain managers is deprecated - use the switchmgr command).
If this error arises from this activity, an internal error has occurred.
current_manager is the name of the current domain manager. new_manager is the workstation that you want to become the new domain manager.
The command is not processed.
The response depends on what you were doing when the error occurred:
- If you were using switchmgr, repeat the command selecting as new_manager a fault-tolerant agent belonging to your domain. Alternatively, if the new_manager workstation is in the domain of the current_manager, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
- If you were using the start ;mgr command, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU064E
The domain manager "new_manager" is not a fault-tolerant agent.
There are two possibilities:
- You are using the switchmgr command to switch the domain manager of your domain to a workstation that is not a fault-tolerant agent.
- You issued a start command with the ;mgr option on a workstation which is not a fault-tolerant agent (this method of switching domain managers is deprecated - use the switchmgr command).
new_manager is the workstation that you want to become the new domain manager.
A backup domain manager has to be a fault-tolerant agent that operates in full status mode, because it has to be updated with the status of jobs and job streams running on all other workstations in its domain and in subordinate domains.
The command is not processed.
The response depends on what you were doing when the error occurred:
- If you were using switchmgr, repeat the command selecting as new_manager a fault-tolerant agent operating in full status mode. Alternatively, if the new_manager workstation is operating in full status mode, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
- If you were using the start ;mgr command, you cannot run it on this workstation. You must either choose a different fault-tolerant agent, or promote this agent to be fault-tolerant (see the Planning and Installation Guide for details.)
AWSBHU065E
The specified new domain manager is not full status.
There are two possibilities:
- You are using the switchmgr command to switch the domain manager of your domain to a fault-tolerant agent that is not full status.
- You issued a start command with the ;mgr option on a fault-tolerant agent that is not full status (this method of switching domain managers is deprecated - use the switchmgr command).
A backup domain manager has to operate in full status mode, because it has to be updated with the status of jobs and job streams running on all other workstations in its domain and in subordinate domains.
The command is not processed.
The response depends on what you were doing when the error occurred:
- If you were using switchmgr, repeat the command either selecting a fault-tolerant agent operating in full status mode or first setting the mode of the chosen workstation to full status.
To do this, run the composer mod command with the 'cpu=<workstation>' option. When the editor displays the workstation definition, set the fullstatus option to on. Then run JnextPlan. See the Reference Manual for more details.
- If you were using the start ;mgr command, either choose a different fault-tolerant agent operating in full status mode on which to run the command, or change the mode of this workstation, as described for the switchmgr command, above.
AWSBHU066E
The domain you supplied to the switchmgr command is not in the Symphony file.
See message.
The switchmgr command is not processed.
The procedure to follow is as follows:
- Verify if the supplied domain is correct and exists. If it is not, select a valid domain and rerun the command.
- If the supplied domain name is correct and the domain must have been found in the Symphony file, the user who issued the command might not have access rights to the Symphony file. Verify that the owner of the file is the HCL Workload Automation user and that this user has the rights to access and modify it. If any of these are not true, correct the problem and rerun the command.
- If the program is not able to read the Symphony file or the Symphony file is not present, see the chapter in this guide on Symphony file corruption. If the problem persists, an internal error has occurred, and search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU067E
A manager workstation has not been specified for the switchmgr command.
See message.
The switchmgr command is not processed.
Rerun the switchmgr command ensuring that you supply a domain and a manager workstation.
AWSBHU068E
The following workstation supplied to the switchmgr command is not in the Symphony file: "workstation_name".
See message. The workstation that you want to become the domain manager must be a fault-tolerant agent operating in full status mode.
workstation_name is the workstation not found in the Symphony file.
The command is not processed.
The procedure to follow is as follows:
- Verify if the supplied workstation name is correct and is a fault-tolerant agent operating in full status mode. If it is not, either select a different workstation that satisfies these criteria, or modify the selected workstation to satisfy them; then rerun the command.
- If the supplied workstation name is correct and the workstation must have been found in the Symphony file, the user who issued the command might not have access rights to the Symphony file. Verify that the owner of the file is the HCL Workload Automation user and that this user has the rights to access and modify it. If any of these are not true, correct the problem and rerun the command.
- If the program is not able to read the Symphony file or the Symphony file is not present, see the chapter in this guide on Symphony file corruption. . If the problem persists, an internal error has occurred, and search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU069E
Too many parameters have been supplied to this switchmgr command.
See message.
The command is not processed.
Rerun the command with the correct syntax.
AWSBHU070E
The following domain name could not be found in the Symphony file: "domain_name".
You have issued a command referring to a domain name that is not in the Symphony file.
domain_name is the domain not found in the Symphony file.
The command is not processed.
The procedure to follow is as follows:
- Verify if the supplied domain is correct and exists. If it is not, select a valid domain and rerun the command.
- If the supplied domain name is correct and the domain ought ot have been found in the Symphony file, the user who issued the command might not have access rights to the Symphony file. Verify that the owner of the file is the HCL Workload Automation user and that this user has the rights to access and modify it. If any of these are not true, correct the problem and rerun the command.
- If the program is not able to read the Symphony file or the Symphony file is not present, see the chapter in this guide on Symphony file corruption. If the problem persists, an internal error has occurred, and search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU071E
An error was encountered accessing the following file: "file_name". The following gives more details of the error: "error"
Conman encountered an error during the retrieving of the selected file or file list. If you used the setsym command, conman cannot access the list of archived Symphony files or the Symphony file you selected.
error is either a Symphony file access error message or a system error, or an error number. file_name is the file conman is trying to open. If the object is a file list, this field is blank.
The command is not processed.
Verify that the owner of the files or the directory selected is the HCL Workload Automation user, and that that user has the right to access it. Change the user permissions if needed. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU072E
There are no objects that match the selection you have entered.
See message.
The command is not processed.
Check if the object you are trying to select exists. If it exists, you might be using an incorrect selection format. For example if you use the selection format wkstation#jobstream.job to select jobs, the workstation has to be the workstation where the job stream exists, not the workstation where the job is run. On the other hand, if you use the format wkstation#job, the workstation refers to the workstation where the job is run. Verify you are using the right selection format for the object the command acts on and rerun the command.
AWSBHU073E
The mozart database does not exist, or cannot be opened or accessed. The following gives more details of the error: "error_text".
See message.
error_text is an optional error message. It provides you with more details about the cause of the error.
Conman stops if it requires the mozart database to continue. If it can continue in the absence of the file it does so.
Check that the mozart database exists, is in the correct directory, and that the user has the right to open it. Check also that there is sufficient disk space for the file to be opened.
AWSBHU075E
The following incorrect conman command has been used: "command".
See message.
command is the incorrect command.
The command is not processed.
Check the correct format of the command you want to use in the Reference Manual.
AWSBHU076E
Conman cannot process the issued command. The following error occurred: "error_text"#
error_text indicates the reason for the problem.
The command is not processed.
Check the error_text for more details about the problem.
AWSBHU077E
The issued show command does not indicate the object or objects which you want the command to show.
See message.
The command is not processed.
Reissue the command using the correct syntax.
AWSBHU078E
An internal error has occurred. The following command number is not correct for the show command: "command_number". The problem was encountered in the following source file "file_name", at line "line_number".
command_number is an internal code identifying the command that is not valid.
file_name and line_number identify the line of source code where the problem was found.
Conman stops.
Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU079E
An internal error has occurred. CmdLink needs more workspace; it needs: "required_space", but only: "available_space" is available.
Conman cannot allocate enough space for a work buffer.
required_space is the required space. available_space is the available space.
Conman stops.
Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU080E
An internal error has occurred. The following keyword is not correct: "keyword_number". The problem was encountered in the following source file "file_name", at line "line_number".
Conman does not recognize a keyword.
keyword_number is an internal code identifying the keyword that conman does not recognize.
file_name and line_number identify the line of source code where the problem occurred.
Conman stops.
Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU081E
An internal error has occurred. The following record type is not a valid mailbox record type: "record_type". The problem was encountered in the following source file "file_name", at line "line_number".
Conman does not recognize a record type in a mailbox file.
record_type is the internal record type that conman does not recognize.
file_name and line_number identify the line of source code where the problem occurred.
Conman stops.
Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU082E
Modification is not authorized.
AWSBHU083E
The issued command cannot be applied to the USERJOBS job stream.
The USERJOBS job stream is a special job stream that includes all the jobs that are not in the job stream CARRYFORWARD started in the previous Production Plan. In the USERJOBS job stream you cannot run commands like cancel, altpri, limit, or rerun.
The command is not processed.
Check that you have used the correct command and have not identified the USERJOBS job stream by mistake.
AWSBHU084E
The issued command cannot be applied to the JOBS job stream.
The JOBS job stream is a special job stream that includes all the Ad-Hoc jobs you submit without specifying a target job stream (argument INTO). On this job stream you cannot run commands like cancel.
The command is not processed.
Check that you have used the correct command and have not identified the JOBS job stream by mistake.
AWSBHU085E
This job or job stream is not in the correct state to apply the issued command.
See message.
The command is not processed.
Check that you have correctly identified the job or job stream. Check which states are acceptable for running commands. Wait until the job or job stream is in the correct state and reissue the command.
AWSBHU086E
You must be on the master to execute this command.
AWSBHU087E
The selected job stream has already been cancelled.
You cannot add a dependency to, submit a job to, or kill a job in a cancelled job stream.
The command is not processed.
Check that you have correctly identified the job stream and have issued the correct command.
AWSBHU088E
You cannot rerun user jobs.
See message.
The command is not processed.
Select a valid job to rerun.
AWSBHU089E
This parameter is only valid when using the from parameter with the rerun command.
You tried to rerun the job using an at or a pri dependency without specifying the from keyword.
The command is not processed.
The at and pri dependencies can only be used if you specify the from parameter.
AWSBHU090E
The job indicated by the from parameter does not exist in the database.
See message.
The command is not processed.
Reissue the rerun command, selecting a valid job name for the from parameter.
AWSBHU091E
The alias or step name supplied for the job or job stream is not valid.
You have either specified an alias name in a submit command or a step name in a rerun command. The name supplied is not valid. It must start with an alphabetic character, and must contain only alphanumeric characters, dashes, and underscores.
The command is not processed.
Rerun the command, supplying a valid alias.
AWSBHU092E
This job or job stream has too many dependencies.
The maximum number of dependencies that you can add to a job or a job stream is 40.
The job or job stream is not processed.
Rerun the job or job stream, defining fewer than 40 dependencies. Note: you might find that removing some dependencies to replace them with others does not work. For example, if you want to add 2 dependencies and you have reached the limit of 40, deleting 5 dependencies to add 2 might not work. In these cases replan your job dependencies.
AWSBHU093E
The issued rerun command did not specify the step name to use after the ;step parameter.
See message.
The command is not processed.
Reissue the rerun command, supplying the parameter ;step=<step_name> if you want to rename the job.
AWSBHU094E
The following dependency keyword is an unknown dependency: "dependency_keyword". The problem was encountered in the following source file "file_name", at line "line_number".
Conman does not recognize the dependency keyword.
dependency_keyword is an internal code.
file_name and line_number identify the line in the source code where the problem was found.
Conman stops.
Probably the HCL Workload Automation keyword you are using is not valid for the current command. See the Reference Manual for more details about the valid keywords that you can pass to the command.
If you are using valid syntax and the error persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU095E
The job stream or job dependency "dependent_job_stream_or_job" was not found in the Symphony file.
dependent_job_stream_or_job is the dependent job stream or job name identified by the follows dependency keyword.
The command is not processed.
Select a valid job name and rerun the command. You must select a job using the complete format (<workstation_of_the_job_stream>#<job_stream>.<job> or <job_stream>.<job>).
You can use the 'nocheck' option. In this case, conman does not check for the existence of the <job_stream>.<job> in the Symphony file. However, batchman does check its existence, and shows an error message in the stdlist if the <job_stream>.<job> does not exist.
AWSBHU096E
You have specified a range of values for a command qualifier that does not accept ranges.
Conman gives this error when the command string includes a range (a value followed by a comma) and the command itself or the qualifier used in this command does not accept ranges of values.
The command is not processed.
Correct the command syntax and rerun the command.
AWSBHU097E
You have not specified a values for a command qualifier that requires one.
See message.
The command is not processed.
Correct the command syntax and rerun the command.
AWSBHU098E
An internal error has occurred. The following internal command is not a valid command: "command_number". The problem was encountered in the following source file "file_name", at line "line_number".
Conman has encountered an internal error.
command_number is an internal code. It represents the command that conman does not recognize.
file_name and line_number identify the line in the source code where the problem was found.
Conman stops.
Retry the command. If the error persists search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU099E
The supplied path name exceeds the maximum size, which is: "maximum_size".
See message.
maximum_size is the maximum number of bytes accepted in the path name.
The command is not processed.
Verify if the file name that you inserted is correct. If it is, move it to a shorter path name or rename directories in the path to have shorter names. Rerun the command using the shorter path.
AWSBHU112E
The supplied job specification is not in the correct format. You can use only <workstation>#<job> or <job>.
See message.
The command is not processed.
A job specification is normally one of the following:
- <workstation>#<job_stream>.<job>
- <job_stream>.<job>
- <workstation>#<job>
- <job>
However, for this command conman only accepts the latter two formats (highlighted).
AWSBHU114E
The supplied switchmgr command did not identify the domain, the new manager, or both.
See message.
The command is not processed.
Reissue the switchmgr command, ensuring to identify the domain name and the new manager name.
AWSBHU115E
The user that has issued a start ;mgr or a switchmgr command does not have stop rights to the current domain manager: "current_manager". Conman therefore cannot start the new manager: "proposed_manager".
See message.
current_manager is current domain manager.
proposed_manager is the proposed domain manager.
The command is not processed.
Either the Security file must be modified to give the user the required access, or a different user that has this access must issue the command.
AWSBHU116E
The user that has issued a start ;mgr or a switchmgr command does not have start rights to the new domain manager: "proposed_manager".
See message.
proposed_manager is the proposed domain manager.
The command is not processed.
Either the Security file must be modified to give the user the required access, or a different user that has this access must issue the command.
AWSBHU117E
The switchmgr command cannot be completed. The workstation proposed as the new domain manager: "proposed_manager" is not in the supplied domain: "domain_name".
See message.
proposed_manager is the proposed domain manager identified in the command.
domain_name is the domain where you want to switch the manager.
The command is not processed.
Reissue the command, selecting as proposed_manager a fault-tolerant agent operating in full-status mode and belonging to the domain.
AWSBHU118W
Workstation !1 is already the manager of domain !2.
AWSBHU119E
Wild cards are not permitted in the domain name parameter of the switchmgr command.
You have used one or more wildcards (such as: '@' or '?') in the specification of the domain name.
The command is not processed.
Rerun the command, supplying a fully qualified domain name.
AWSBHU121E
Conman could not identify the parent domain of the following workstation: "workstation_name".
See message.
workstation_name is a workstation for which the parent domain could not be found.
The command is not processed.
Verify the JnextPlan stdlist file to discover if there was a problem during the creation of the plan (Symphony file). Solve the problem and create a new plan.
Alternatively, it could be possible that the Symphony file is corrupted. See the chapter in this guide on Symphony file corruption.
If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU122E
The supplied command includes both the options short and single, which are mutually exclusive.
See message.
The command is not processed.
Correct the syntax to include either the short or the single option, but not both, and rerun the command.
AWSBHU123E
The supplied command includes the option single, which can only be used when a Job Number is supplied.
See message.
The command is not processed.
Reissue the command, identifying the job by means of its job number (the number that follows the #J in the output of the show job command).
AWSBHU126E
A time zone has been specified in a time dependency, but time zone use has not been enabled for workstation: "workstation_name"
See message.
workstation_name is the name of the workstation where the time dependency is to be resolved.
The command is not processed.
Either rerun the command without specifying a time zone or enable time zone use at the indicated workstation.
AWSBHU127W
Submitted !1 to batchman as !2# but workstation !3 not present in the Symphony file.
AWSBHU128W
Dependency !1 might not be present in the Symphony file.
AWSBHU129E
The issued submit command includes more than one nocheck keyword after a follows keyword, which is not permitted.
See message.
The command is not processed.
Rerun the command, supplying not more than one nocheck keyword after each follows keyword.
AWSBHU130E
The issued command cannot be used. It is not allowed by the centralized security option, which is enabled for this domain.
See message.
The command is not processed.
Check that it is correct that centralized security is enabled for the domain:
- If it is not, disable the enable centralized security global option using optman. However, note that this change is not effective until next JnextPlan.
- If it is, check if the security options on the master domain manager permit this command to be used:
- If the security options do not permit the command to be used, consider changing them. However, any changes that you make are not effective until the next JnextPlan.
- If the security options permit the command to be used, the local Symphony file might be corrupt. See the chapter in this guide on Symphony file corruption.
AWSBHU131E
Conman has been unable to obtain information about the remote workstation "workstation_name" because centralized security, which is enabled for this domain, does not allow it to.
See message.
The command is not processed.
Check that it is correct that centralized security is enabled for the domain:
- If it is not, disable the enable centralized security global option using optman. However, note that this change is not effective until next JnextPlan.
- If it is, check if the security options on the master domain manager permit information to be obtained from remote workstations:
- If the security options do not permit such information to be obtained, consider changing them. However, any changes that you make are not effective until the next JnextPlan.
- If the security options permit such information to be obtained, the local Symphony file might be corrupt. See the chapter in this guide on Symphony file corruption.
AWSBHU132E
You have issued a show jobs command, but the information you are requesting can only be supplied if the keyword keys is specified in the command.
See message.
The command is not processed.
Re-issue the command using the correct syntax.
AWSBHU133E
You have supplied a return code condition expression that is longer than the maximum number of bytes permitted, which is: "number".
See message.
The command is not processed.
Re-issue the command, supplying a return code condition expression that is within the maximum number of bytes permitted.
AWSBHU134E
You have supplied a script path name and a return code condition expression, which are together longer than the maximum number of bytes permitted, which is: "number".
See message.
The command is not processed.
Re-issue the command, supplying a script path name and a return code condition expression that are together within the maximum number of bytes permitted.
AWSBHU135E
You have supplied a return code condition expression that is enclosed in mismatched or missing quotes.
The return code condition expression must be enclosed (preceded and followed) by the double quotes character ().
The command is not processed.
Re-issue the command, supplying a return code condition expression that is enclosed by the double quotes character ().
AWSBHU136E
You have supplied a return code condition expression that could not be validated by Conman. The following gives more details of the error: "error_text".
See message.
The command is not processed.
Check the syntax of the expression, correct it and re-issue the command.
AWSBHU137W
The user is not authorized to display the selected objects.
AWSBHU138E
The issued submit command includes more than one wait keyword after a follows keyword, which is not permitted.
See message.
The command is not processed.
Rerun the command, supplying not more than one wait keyword after each follows keyword.
AWSBHU139E
The issued submit command includes a wait keyword, but you have not supplied the associated numeric wait value.
See message.
The command is not processed.
Rerun the command, supplying a numeric value for the wait keyword in the format wait=<number>, where <number> is the wait period in seconds, between 0 and 1200.
AWSBHU140E
The issued submit command includes a wait keyword, but the associated numeric wait value (seconds) is not between 0 and 1200.
See message.
The command is not processed.
Rerun the command, supplying a numeric value for the wait keyword in the range 0 to 1200.
AWSBHU141E
The issued submit command includes a non-numeric or incorrect value for a time parameter. The valid values are from: "minimum_value" to "maximum_value".
See message.
minimum_value to maximum_value is the valid range of numeric values.
The command is not processed.
Rerun the command, supplying a valid numeric value for the time parameter that is within the indicated range.
AWSBHU142E
The issued submit command includes a date which is not valid or is not in the correct format. The accepted format is: "date_format".
See message.
date_format is the permitted format.
The command is not processed.
Rerun the command, supplying a valid date in the indicated format.
AWSBHU143E
The action associated with the onuntil attribute is not correct. It must be one of the following: suppr, cont, canc.
See message.
The command is not processed.
Rerun the command, supplying a valid action for the onuntil attribute.
AWSBHU144E
There is a syntax error. The schedule time is not valid or is not in the correct format. The correct format is hhmm or hhmm "localopts_date_format".
See message.
date_format is the permitted format for the date from the localopts file, for example, yymmdd.
The command is not processed.
Rerun the command, supplying a valid date in the indicated format.
AWSBHU145E
There is a syntax error. The job stream ID can contain only alphanumeric characters.
See message.
The command is not processed.
Resubmit the command, specifying a valid job stream ID.
AWSBHU146E
There is a syntax error. The job stream ID must be between 1 and 16 bytes long.
See message.
The command is not processed.
Resubmit the command, specifying a valid job stream ID.
AWSBHU147E
The keywords "keyword_1" and "keyword_2" are mutually exclusive. You cannot supply both of them.
See message.
keyword_1 and keyword_2 are the mutually exclusive keywords.
The command is not processed.
Verify the syntax of command. Resubmit the command specifying only one of the two indicated keywords.
AWSBHU148E
The keyword "keyword" cannot be used because the Symphony file was created by a previous version of HCL Workload Automation.
keyword is the keyword that cannot be used with a Symphony file created by a previous version of HCL Workload Automation.
The command is not processed.
Verify the syntax of command. Resubmit the command, omitting the indicated keyword, or upgrade the workstation where the Symphony file was created to the latest version.
AWSBHU149E
The job stream or job dependency "dependent_job_stream_or_job" with the specified schedule time was not found in the Symphony file.
dependent_job_stream_or_job is the dependent job stream or job name identified by the follows dependency keyword.
The command is not processed.
Select a valid job stream or job name and rerun the command.
You can use the 'nocheck' option. In this case, conman does not check for the existence of the <job_stream>.<job> in the Symphony file. However, batchman does check its existence, and shows an error message in the stdlist if the <job_stream>.<job> does not exist.
AWSBHU150W
An internal error has occurred.The program is unable to initialize the GSKit libraries.
A problem has occurred with the installation or configuration of the GSKit libraries, or both, and they cannot be initialized.
The program cannot commence a secure connection, so stops.
This is an internal error. Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU151E
The supplied date is not valid or is not in the correct format. The correct format is "localopts_date_format".
See message.
date_format is the permitted format for the date from the localopts file, for example, yymmdd.
The command is not processed.
Rerun the command, supplying a valid date in the indicated format.
AWSBHU152E
There is more than one job stream instance with the given name. You must refer to a single instance by specifying either the job stream ID or the scheduled start time.
See message.
The command is not processed.
Rerun the command, supplying also either the job stream ID or the scheduled start time, to uniquely identify the instance of the job stream in the plan.
AWSBHU153E
The keyword "keyword_1" can only be supplied if the keyword "keyword_2" is specified.
See message.
keyword_1 must be supplied only with keyword keyword_2.
The command is not processed.
Verify the syntax of command. Resubmit the command specifying the indicated keywords correctly.
AWSBHU154E
Either the nocheck argument or the schedid argument have been supplied without the required job stream ID.
See message.
The command is not processed.
Rerun the command, supplying a valid job stream ID with both the nocheck and the schedid arguments when they are used.
AWSBHU155E
You have submitted a command to be scheduled as a job (submit docommand) but have not included the command.
See message.
The command is not processed.
Rerun submit docommand , supplying a the command to be scheduled.
AWSBHU156E
The workstation you specified is already the event processor.
You have tried to set a workstation as the new event processor, but it is already the event processor.
The command is not processed.
Check why the selected workstation is already the event processor. It might be because another person has performed the operation you are trying to perform, or because you typed the workstation name incorrectly. Correct the error and retry the operation.
AWSBHU157E
You have issued a command containing at least one incorrect argument keyword.
The command contains at least one unsupported keyword.
The command is not processed.
Correct the syntax and retry the command.
AWSBHU158E
The command issued for workstation "workstation_name" cannot be performed, because the workstation is agent, or pool, or dynamic pool, or remote engine, or broker workstation, where the command is not supported.
See message.
workstation_name is the agent, or pool, or dynamic pool, or remote engine, or broker workstation name.
The command is not processed.
You cannot use this command on the selected workstation. If you have selected the agent, or pool, or dynamic pool, or remote engine, or broker workstation in error, change the command to identify a different workstation and re-issue the command. If you have selected the wrong command, issue a different command.
AWSBHU159E
The command issued for workstation "workstation_name" cannot be performed, because the workstation is broker agent, where the command is not supported.
See message.
workstation_name is the broker agent workstation name.
The command is not processed.
You cannot use this command on the selected workstation. If you have selected the broker agent workstation in error, change the command to identify a different workstation and re-issue the command. If you have selected the wrong command, issue a different command.
AWSBHU160E
The command issued for workstation "workstation_name" cannot be performed, because of the following error: "error".
See message.
The command is not processed.
This command failed on the selected workstation.
AWSBHU161E
The command issued for workstation "workstation_name" cannot be performed, because the workstation is master domain manager, or domain manager, where the command is not supported.
See message.
workstation_name is the master domain manager, or domain manager name.
The command is not processed.
You cannot use this command on the selected workstation. If you have selected the master domain manager, or domain manager in error, change the command to identify a different workstation and re-issue the command. If you have selected the wrong command, issue a different command.
AWSBHU162E
"file_name" file cannot be moved on workstation "workstation_name" because it is being used by another process.
See message.
file_name is the file that cannot be moved because it is being used by another process.
workstation_name is the workstation to reset.
The operation is not performed.
Stop any HCL Workload Automation process that might be using the file and re-issue the command.
AWSBHU163E
An error has occurred while launching the script moveFTATargetFiles on workstation "workstation_name".
See message.
workstation_name is the workstation to reset.
The operation is not performed.
If you have customized the script, check that it does not contain syntax error. If any errors are present, correct them and re-issue the command.
AWSBHU164E
The script moveFTATargetFiles is missing on workstation "workstation_name".
See message.
workstation_name is the workstation to reset.
The operation is not performed.
If the script was deleted, copy it in the %HOME%/bin directory from another agent. Customize the %HOME% variable in the script according to the installation directory on the agent.
AWSBHU166E
A file cannot be removed from TWShome/pobox directory on workstation "workstation_name" because it is being used by another process.
See message.
workstation_name is the workstation to reset.
The operation is not performed.
Stop any HCL Workload Automation process that might be using the file and re-issue the command.
AWSBHU168E
The agent on workstation "workstation_name" cannot be reset because it is still active.
See message.
workstation_name is the workstation to reset.
The operation is not performed.
Stop any HCL Workload Automation process that might be using the files to reset and re-issue the command.
AWSBHU169E
The number of hours must be an integer value between 0 and 500.
The number of hours must be an integer value between 0 and 500.
The command is not processed.
Specify the number of hours as an integer number between 0 and 500 and retry the operation.
AWSBHU170E
The action to be performed when the value of the onmaxdur attribute is exceeded, is not a valid action. Specify one of the following: kill, cont.
See message.
The command is not processed.
Specify a valid action to be performed when the value for the onmaxdur attribute is exceeded, and then retry the operation.
AWSBHU171E
The action to be performed when the value of the onmindur attribute is reached, is not a valid action. Specify one of the following: abend, cont, confirm.
See message.
The command is not processed.
Specify a valid action to be performed when the value for the onmindur attribute is reached, and then retry the operation.
AWSBHU172E
The command issued for workstation "workstation_name" cannot be performed, because the workstation is pool, or dynamic pool, or remote engine workstation or broker, where the command is not supported.
See message.
workstation_name is the pool, or dynamic pool, or remote engine workstation name.
The command is not processed.
You cannot use this command on the selected workstation. If you have selected the pool, or dynamic pool, or remote engine workstation in error, change the command to identify a different workstation and re-issue the command. If you have selected the wrong command, issue a different command.
AWSBHU173E
Conman command is unable to start a new process. Your HCL Workload Automation license expired "exp_date".
Conman cannot start a new process because the HCL Workload Automation license has expired
The command can continue but it is not able to start new processes.
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.
AWSBHU174E
The command issued for workstation "workstation_name" cannot be performed, because the workstation is remote engine, or broker workstation, where the command is not supported.
See message.
workstation_name is the remote engine, or broker workstation name.
The command is not processed.
You cannot use this command on the selected workstation. If you have selected the remote engine, or broker workstation in error, change the command to identify a different workstation and re-issue the command. If you have selected the wrong command, issue a different command.
AWSBHU175E
The selected job stream has already been suppressed.
You cannot rerun a job in a suppressed job stream.
The command is not processed.
Check that you have correctly identified the job stream and have issued the correct command.
AWSBHU176E
The value specified for rerunning the job on the same workstation is not allowed. This option is valid only if the type of workstation where the job runs is a pool or a dynamic pool.
See message.
The command is not processed.
Check that you have correctly identified the job or job stream. Check which workstation types are supported by the rerun command with the same workstation option. Specify a different rerun option and reissue the command.
AWSBHU181E
The conditional dependency expression specified cannot be validated by conman.
See message.
The command is not processed.
Determine the correct syntax of the expression and resubmit the command using the correct syntax.
AWSBHU182E
The output condition expression specified cannot be validated by conman.
See message.
The command is not processed.
Determine the correct syntax for the output condition expression and resubmit the command using the correct syntax.
AWSBHU183E
The conditional dependency specified "conditional_dependency" does not exist in the Symphony file.
conditional_dependency is the conditional dependency identified by the follows dependency keyword. You have either specified the conditional dependency incorrectly or it does not exist in the Symphony file.
The command is not processed.
Specify a valid conditional dependency and rerun the command. Ensure you specify the conditions contained in the conditional dependency in the same order as they were originally defined..
You can use the 'nocheck' option. In this case, conman does not check for the existence of the conditional dependency in the Symphony file. However, batchman does check its existence, and shows an error message in the stdlist if the conditional dependency does not exist.
AWSBHU184W
The "keyword" variable value is longer than the maximum number of bytes and will be truncated.
See message.
Reduce the lenght to avoid that the variable is truncated.
AWSBHU185E
The logon or streamlogon value is empty or invalid.
See message.
AWSBHU186E
The docommand or script keyword is not compatible with the type of the job. Use this keyword only for native jobs.
See message.
AWSBHU187E
The supplied logon name exceeds the maximum size, which is: "maximum_size".
See message.
maximum_size is the maximum number of bytes accepted in the logon name.
The command is not processed.
Verify if the logon name that you inserted is correct.
AWSBHU188E
The command or script name is empty or invalid.
See message.
AWSBHU189E
You have issued a command that has attempted to edit a job into an EXTERNAL job stream. This is not permitted.
The EXTERNAL job stream is used to monitor the status of internetwork dependencies, and a job into this job stream cannot be edited.
AWSBHU410E
The workstation name parameter has not been specified for the "command_name" command.
See message.
The operation is not performed.
Rerun the command ensuring that you specify a workstation.
AWSBHU411E
Wild cards are not permitted in the workstation name parameter of the "command_name" command.
You have used one or more wildcards (such as: '@' or '?') while specifying the workstation name.
The operation is not performed.
Rerun the command, specifying a fully qualified workstation name.
AWSBHU412E
Too many parameters have been supplied to the "command_name" command.
See message.
The operation is not performed.
Rerun the command with the correct syntax.
AWSBHU503E
You have included one or more keywords that are not required for this command. The point beyond which the keywords are not required is indicated.
See message.
The command is not processed.
Re-issue the command using the parameters and keywords only up to the indicated position.
AWSBHU504E
You have issued a command with a time-related dependency, but have omitted the keyword day[s].
You have issued a command with an at, until, or deadline dependency. You have also entered a + delimiter and a numeric value, which can only be used if accompanied by the keyword day[s].
The day[s] qualifier is optional, but if it is present it must be preceded by the + delimiter and a numeric value. Similarly, if the delimiter and value are present, so must the qualifier.
For example, +5 days.
The command is not processed.
Re-issue the command, with the following correction
- If you intended to supply a day[s] qualifier, add the keyword to the command string.
- If you did not intend to supply a day[s] qualifier, remove the + delimiter and the numeric value.
AWSBHU508E
You do not have access to this file or database object.
See message.
The command is not processed.
If you are using the display command, verify that the current user has the rights to access the file that the user is trying to display.
In other cases, verify that the object name selected is correct and that the current user has the HCL Workload Automation Security rights to apply the command action for the object.
When you have identified and corrected the problem re-issue the command.
AWSBHU509E
The requested file cannot be found.
See message.
The command is not processed.
Verify the name of the file you want to access. Re-issue the command, ensuring that the file is specified as fully or partially qualified, as required by the command syntax.
AWSBHU510E
The following job already exists: "workstation"#"job_stream"."job". Use the rerun command or supply an alias with the submit command.
See message.
workstation#job_stream.job is the job name that already exists.
The command is not processed.
If you intended to run a new job, select a different job name. Use the sj command to list the current jobs in the Symphony file.
If you intended to rerun an existing job, use the rerun command or the submit command with the alias option.
AWSBHU511E
You have no access to the recovery job (!1#!2).
AWSBHU512E
The issued command operates on an existing job. However, conman cannot find the indicated job in the Symphony file, and it is not an external job.
See message.
The command is not processed.
Re-issue the command, identifying an existing job by its job name or number.
Use the sj command to list the current jobs in the Symphony file.
AWSBHU513E
The following job stream already exists: "job_stream_name". Supply an alias with the submit command.
See message.
job_stream_name is the job stream name.
The command is not processed.
If you intended to run a new job stream, select a different job stream name. Use the sc command to list the current job streams in the Symphony file.
If you intended to rerun an existing job stream, use the submit command with the alias option.
AWSBHU516E
You have not supplied a valid alias of the job you are trying to resubmit.
You are trying to resubmit a job. A resubmitted job cannot have the same name as the original job; it must instead be supplied with an alias that has a different value from the original job name.
The command is not processed.
Resubmit the command, using the ;alias option with a valid new job name. See the Reference Manual for more details.
AWSBHU517E
The required information cannot be displayed.
Conman gives this error because it cannot display a file. There are two possibilities:
- No job file: You are trying to display a job file, but the job was defined by a command and not in a file.
- Remote job: You are trying to display a job scheduled on another workstation for which the definition file is not available locally.
The command is not processed.
Use the command sj; info to see how the job is defined, whether as a command or in a file. This also tells you whether the job is locally or remotely defined.
AWSBHU518E
You cannot add dependencies to a job or job stream in the adding status, or to a job in an in order job stream.
You tried to add dependencies to a job or job stream but either the job or job stream status is adding or this job belongs to an in order job stream.
An in order job stream is one where the definition specifies, by use of the in order keyword, that jobs must be run in their definition order.
The command is not processed.
If you need to add dependencies to an in order job stream, you need to redefine the job stream.
AWSBHU520W
Dependency !1 was not found in the database; it has been ignored.
AWSBHU521W
Dependency !1 was not found in the Symphony file ; it has been ignored.
AWSBHU522E
The supplied job name is not in the database.
See message.
The command is not processed.
Select a valid job name and rerun the command.
AWSBHU523E
You have issued a link or an unlink command on a standalone workstation (on which mailman is not running).
See message.
The command is not processed.
Check that it is correct that the workstation is standalone. If so, do not use the command.
AWSBHU524E
The issued command incorrectly ends with a delimiter.
The last character in the command string ends with a delimiter (for example: ; or =). This implies that a keyword or value is missing, because all delimiters must be followed by a keyword or value.
The command is not processed.
Re-issue the command, either omitting the delimiter or supplying the keyword or value that is required by the syntax to follow it.
AWSBHU526E
The following internal error occurred when conman attempted to display a JCL file: "error_message".
See message.
error_message is an operating system error message returned by the function pipe().
The command is not processed.
Re-issue the command. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU527E
A file-descriptor or disk-space error occurred when conman attempted to open a JCL file for display.
Conman could not open a JCL file. Either the process has opened too many file descriptors or there is insufficient storage space available.
This is an operating system error given by the I/O Library function fdopen.
The command is not processed.
Increase the number of file descriptors a process can open or verify that there is enough space available on the file system.
If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU528E
A file-descriptor or disk-space error occurred when conman attempted to display a JCL file.
Conman could not open a work file to display a JCL file. Either the process has opened too many file descriptors or there is insufficient storage space available.
This is an operating system error given by the I/O library function fdopen.
The command is not processed.
Increase the number of file descriptors a process can open or verify that there is enough space available on the file system.
If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU529E
The following error occurred while conman was displaying a JCL file: "error_number".
Conman gave this error because a system error occurred while it was reading the JCL file.
error_number is the operating system error number, returned from I/O library function ferror, issued by the function fgets().
The command is not processed.
Verify that the file system is working properly and is not full.
If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU530E
The following error occurred while conman was writing a work file when displaying a JCL file: "error_number".
See message.
error_number is the system error number, returned from I/O Library function fprintf.
The command is not processed.
Verify that the file system is working properly and is not full.
If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU531E
Conman was unable to access the mozart database or was unable to find a parameter within the database.
See message.
The command is not processed.
Verify that all parameters used in the command have been defined in the mozart database, and that the database itself is available and viable. Re-issue the command.
AWSBHU532E
You have either entered too many parameters, or the expansion of the parameters you have entered has exceeded the internal parameter buffer.
You can supply a maximum of 20 parameters to this command, and when the parameters are fully expanded they must not occupy more than 4095 bytes.
The command is not processed.
Re-issue the command, reducing the number of parameters, or re-specify the parameters to be shorter.
AWSBHU533E
Conman has found a problem with the syntax of the issued command, but is unable to determine more precisely the nature of the problem.
See message.
The command is not processed.
Check the syntax of the command. If it is incorrect, re-issue the command with the correct syntax.
If the command syntax seems to be correct, an internal error has occurred. Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU534E
The workstation selected for this job is not a workstation but a workstation class.
The syntax <workstation_class>#<job> is not correct. You cannot submit a job to run on a workstation class.
The command is not processed.
Re-issue the command, defining the job to run on a workstation.
AWSBHU535E
The following workstation is not in the Symphony file: "workstation_name".
See message.
workstation_name is the name of the workstation not found.
The command is not processed.
Re-issue the command, selecting a valid workstation name.
AWSBHU536E
The following domain is empty: "domain_name".
See message.
domain_name is the name of the empty domain.
The command is not processed.
This is an internal error. Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU537E
You have issued the link or unlink command to the following workstation within the same domain and neither is the domain manager: "workstation_name". This is not allowed.
The link or unlink commands can only be issued to a workstation in the same domain which is a parent or a child of the workstation where the command is issued, not to a peer workstation.
workstation_name is the local workstation that you cannot link to or unlink from.
The command is not processed.
If you intended to link to or unlink from the domain manager, re-issue the command, identifying the domain manger workstation. See the Reference Manual
AWSBHU538W
!1: The domain of the workstation being linked or unlinked is not subordinate to the domain of the local workstation.
AWSBHU539E
An internal error has occurred while linking to or unlinking from the following workstation: "workstation_name":
The internal message is the following: Unknown link case encountered.
workstation_name is the workstation name that cannot be linked to or unlinked from.
The command is not processed.
This is an internal error. Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU540E
Conman cannot find any domains in the Symphony file.
See message.
The command is not processed.
This normally indicates a problem with the Symphony file.
If the Symphony file exists, verify that the owner is the HCL Workload Automation user and that this user has the permissions to access and modify the Symphony file. If you find a problem, correct it and re-issue the command.
If the Symphony file is not present or is unreadable, follow the instructions in the chapter in this guide on Symphony file corruption.
AWSBHU541E
You have tried to issue a start command to the following workstation: "remote_workstation", which is not a child of the local workstation: "local_workstation".
You cannot start or stop a workstation which is not at a lower point in the HCL Workload Automation hierarchy than the local workstation.
local_workstation is the local workstation name.
remote_workstation is the workstation name you were trying to start.
The command is not processed.
If you need to start the remote_workstation, issue the start command from its domain manager, or from any other workstation which is at a higher point in the hierarchy, or from the remote_workstation itself.
AWSBHU542E
Conman has verified that the versions of the Symphony and Database files (Mastsked version) are different.
See message.
The command is not processed.
This is an internal error. Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU543E
You have supplied the interactive qualifier keyword to the submit jobs command, which is not valid.
See message.
The command is not processed.
The interactive option is only valid with sbf and sbd commands. If you want to submit a job as interactive and this job is defined in the mozart database, you have to run composer and modify the job stream containing the job.
AWSBHU544E
The supplied path name is longer than the maximum allowed: "maximum_bytes".
See message.
The command is not processed.
Re-issue the command using a path name shorter than the maximum indicated.
AWSBHU545E
You have supplied a path name that does not match the workstation type: "workstation_type".
See message.
workstation_type is the workstation type of the workstation.
The type of path to be supplied depends on the type of workstation, as follows:
- UNIX: the path must be specified as a Posix path.
- WNT: the path must be specified as a DOS path.
The command is not processed.
Re-issue the command, supplying the path in the correct format.
AWSBHU546E
You have supplied either a tz or a timezone keyword but did not supply the time zone name.
See message.
The command is not processed.
Re-issue the command, supplying a time zone name after the tz or timezone keyword.
AWSBHU547E
You have supplied a time zone name that is longer than 40 bytes.
See message.
The command is not processed.
Re-issue the command, supplying a valid time zone name, shorter than 40 bytes.
AWSBHU548E
You have supplied a time zone name that is not valid.
See message.
The command is not processed.
Re-issue the command, supplying a valid time zone name.
AWSBHU549W
There is a logic error in the time-related dependencies. The until time occurs before the at time.
See message.
The job to which this warning relates is added to the plan. However, it can never run. Conman proceeds.
The simplest way to deal with this problem is to resubmit the job with an alias, correcting the dependency logic problem so that the job can run.
AWSBHU550W
There is a logic error in the time-related dependencies. The dependency is circular.
See message.
The job to which this warning relates is added to the plan. However, it can never run. Conman proceeds.
The simplest way to deal with this problem is to resubmit the job with an alias, correcting the dependency logic problem so that the job can run.
AWSBHU551E
You are trying to add the same dependency twice.
See message.
The command is not processed.
Re-issue the command, omitting the duplicated dependency.
AWSBHU553E
An error has occurred while starting an internal component (clagent).
See message.
The command is not processed.
This is an internal error. Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU556E
The following error occurred while opening the clbox.msg file: "error_text".
See message.
error_text is an error message. It supplies you with more details about the error causes.
The error is probably one of the following:
- The clbox.msg file already exists but the HCL Workload Automation user does not have write access to the file.
- There is insufficient space to create the file.
- The process has exceeded the maximum number of file descriptors.
The command is not processed.
- Verify from the error message where the problem is.
- Fix the problem and re-issue the command.
AWSBHU557W
There is a logic error in the time-related dependencies. The deadline time occurs before the at or until time.
See message.
The job to which this warning relates is added to the plan. However, it can never run. Conman proceeds.
The simplest way to deal with this problem is to resubmit the job with an alias, correcting the dependency logic problem so that the job can run.
AWSBHU558W
There is a syntax error in the time-related dependencies. The onuntil keyword was specified but the until time was not supplied.
See message.
The job to which this warning relates is added to the plan. However, it can never run. Conman proceeds.
The simplest way to deal with this problem is to resubmit the job with an alias, correcting the syntax error so that the job can run.
AWSBHU559E
The following workstation "remote_workstation" cannot be stopped, because it is in a peer or parent domain of the following local workstation, which is not a domain manager: "local_workstation".
A workstation which is not a domain manager can only stop workstations in child domains.
The command is not processed.
To stop the indicated workstation, issue the stop command from the workstation itself, its domain manager, or any workstation in a parent domain.
AWSBHU560E
The command startmon cannot be performed, because the Event Driven Workload Automation feature is disabled.
The Event Driven Workload Automation feature has been disabled by optman, which set the enEventDrivenWorkloadAutomation option to NO.
Monman cannot be started.
The command is not processed.
You cannot use this command when the Event Driven Workload Automation feature is disabled.
AWSBHU561W
A syntax error has occurred in the specifications for the time-related dependencies. The onmaxdur keyword was specified but the maxdur time was not supplied.
See message.
The job for which the keyword is specified is added to the plan, but it cannot run. Conman proceeds.
Specify the maxdur time for the onmaxdur keyword and then resubmit the job with an alias.
AWSBHU562W
A syntax error has occurred in the specifications for the time-related dependencies. The onmindur keyword was specified but the mindur time was not supplied.
See message.
The job for which the keyword is specified is added to the plan, but it cannot run. Conman proceeds.
Specify the mindur time for the onmindur keyword and then resubmit the job with an alias.
AWSBHU600E
There is a logic error in the follows dependencies. The dependency "circular_dep" is circular.
See message.
circular_dep is the dependency which refers directory or indirectly to itself.
The command is not processed.
Check the details of the supplied command. Check the indicated dependency and determine why it is circular. It might be directly circular, in that you have erroneously made the scheduled object dependent on itself, or it might be more complex with, for example, job A dependent on job B, which is dependent on job C, which is dependent on job A. Correct the error and resubmit the command.
AWSBHU601E
Cannot create semaphore, Error number: !1
AWSBHU602E
Cannot create thread, Error number: !1
AWSBHU603E
Cannot release thread, Error number: !1
AWSBHU604E
Wait for semaphore failed, Error number: !1
AWSBHU605E
Conman timed out - Closing Symphony.
AWSBHU606E
An error occurred while saving the user options file:"file"
See message.
The operation is not performed.
Verify that there is sufficient space in the indicated file system, and that the user of HCL Workload Automation has permission to write files in the indicated directory.
AWSBHU607E
The value specified for the -protocol connection parameter is not valid. It must be http or https.
See message.
The operation is not performed.
Correct the -protocol connection parameter and reissue the command.
AWSBHU609E
The value specified for the -timeout connection parameter is not valid. It must be the number of seconds that the command line client is to wait for a connection before timing out.
The -timeout parameter is one of the connection parameters, supplied as part of the command, in a file of connection parameters, or by default from the useropts or localopts file. It must be expressed as a number (of seconds). For example, the value for 30 seconds must be 30, not 30s or 30 secs.
The operation is not performed.
Retry the command, changing the value of the timeout parameter to be a number of seconds.
AWSBHU610E
The credentials to connect to the remote server have not been specified.
When you use the command line client, it needs to connect to the remote server at the master domain manager. For this it requires connection parameters that are supplied as part of the command, in a file of connection parameters, or by default from the useropts or localopts file.
conman could not find a set of these parameters to establish a connection.
The operation is not performed.
- Edit the useropts or localopts file and insert the communication parameters. Save the file and rerun the command.
- Reissue the command, supplying the connection parameters as command options, or in a file.
AWSBHU611W
Conman could not initialize the HTTP or HTTPS connection.
Conman is running on a fault-tolerant agent using the command line client. If the connection fails to the command line server on the master domain manager, conman can continue with limited functionality, but the connection must be remade before too much time elapses.
conman continues.
Check to have the right access permits on all files that contain the connection parameters (for example useropts, localopts, dynamic agent configuration file, etc.).
You can continue using conman, especially if you think that the connection problem is temporary.
However, you must take steps before too long to re-establish the connection.
AWSBHU612E
The port specified by the -port connection parameter is not numeric.
See message.
The operation is not performed.
Locate where you have supplied the connection parameters, correct the port, and reissue the command.
AWSBHU613E
There are insufficient units of resource "resource" available. The job requires "required_resources" units but only "available_resources" are available.
See message.
resource identifies the resource.
required_resources is the number of requested units of the specified resource.
available_resources is the number of available units of the specified resource.
Conman does not proceed.
Check the job requirements. Determine why the number of available resource units is inadequate. Try and increase the number of available units or decrease the number of required units, or both. See if it is possible to modify the job so that it uses fewer resources. Perhaps you can divide into two or more separate jobs, each of which uses fewer resources. Perhaps you can schedule the job to run on a different workstation with more resources.
Make whatever modifications you think are necessary and rerun the job.
AWSBHU614E
No job stream was submitted to batchman.
No job stream was received by the server, so no job stream could be submitted to batchman.
The conman submit sched command cannot be processed.
Check that there is nothing in the job stream definition that would prevent it from being scheduled. In particular, check that the scheduled time is with in the range of the current plan. Correct any errors you find and resubmit the job stream.
AWSBHU615E
The submitted job refers to a recovery job which could not be found in the database.
See message.
The submitted command cannot be performed.
Check the details of the job you have submitted. You might have made a mistake when identifying the recovery job. Check that the job you want to use as the recovery job is available in the database. Resubmit the job, specifying an existing recovery job.
AWSBHU616E
More than one job stream matches your selection.Uniquely identify the job stream by specifying its ID or schedule time.
See message.
The submitted command cannot be performed.
Resubmit the command, uniquely identifying the job stream to be submitted using the related job stream ID or schedule time.
AWSBHU618E
The bulk_discovery was not performed because no configuration file was found.
The bulk discovery command was not forwarded to batchman because the integration configuration file was not found.
The submitted command cannot be performed.
Verify that the BmEvents.conf file is in the TWS home directory. Rerun the bulk discovery command.
AWSBHU619E
The following error occurred obtaining the monitoring configuration file for workstation "workstation_name": "error_message".
See message.
The operation is not performed.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU624W
The application server on workstation "workstation_name" is already stopped.
See message.
The operation is not performed.
None.
AWSBHU625W
The option WAIT is not supported for remote workstations. It is ignored.
See message.
The operation is not performed.
Choose a supported option and retry the operation.
AWSBHU626W
The application server is not installed for the local workstation.
A command to start or stop the application server has been run, but the application server is not installed, probably because it is not part of the current configuration.
The application server is normally installed on the master domain manager and backup master domain manager. The application server is installed on other domain managers and fault-tolerant agents only if the Connector has been installed.
The operation is not performed.
You cannot use this command on the selected workstation. If you have selected the workstation in error, change the command to identify a different workstation and re-issue the command. If you have selected the wrong command, issue a different command.
AWSBHU630E
The command issued for workstation "workstation_name" cannot be performed, because the workstation is a fault tolerant agent, where the command is not supported.
See message.
workstation_name is the fault tolerant agent workstation name.
The submitted command cannot be performed.
You cannot use this command on the selected workstation. If you have selected the fault tolerant agent workstation in error, change the command to identify a different workstation and re-issue the command. If you have selected the wrong command, issue a different command.
AWSBHU631E
The command issued for workstation "workstation_name" cannot be performed, because the workstation is a standard agent, where the command is not supported.
See message.
workstation_name is the standard agent workstation name.
The submitted command cannot be performed.
You cannot use this command on the selected workstation. If you have selected the standard agent workstation in error, change the command to identify a different workstation and re-issue the command. If you have selected the wrong command, issue a different command.
AWSBHU632E
The command issued for workstation "workstation_name" cannot be performed, because the command is not supported.
See message.
workstation_name is the workstation name.
The submitted command cannot be performed.
You cannot use this command on the selected workstation. If you have selected the workstation in error, change the command to identify a different workstation and re-issue the command. If you have selected the wrong command, issue a different command.
AWSBHU633W
The event processor workstation is set to ignore in the production plan.
See message.
The operation is not performed.
Change the workstation setting to a value other than ignore. You can perform this operation using either the composer command or the Job Scheduling Console.
AWSBHU634E
The command "command_name" cannot be performed, because the event processor workstation is set to ignore in the production plan.
See message.
command_name is the issued command.
The submitted command cannot be performed.
Change the workstation setting to a value other than ignore. You can perform this operation using either the composer command or the Job Scheduling Console.
AWSBHU635E
A syntax error occurred. The variable table name must start with an alphabetic character and contain only alphanumeric characters. The maximum length is 80 bytes.
See message.
The submitted command cannot be performed.
Change the name of the variable table to conform to the rules indicated in the message and resubmit the command.
AWSBHU636E
The Workload Service Assurance feature is not enabled.
See message.
Workload Service Assurance is a feature which can be enabled or disabled. At present it is disabled.
The submitted command cannot be performed.
Use optman to enable the Workload Service Assurance feature.
AWSBHU638W
The dynamic workload broker application on workstation "workstation_name" is already stopped.
See message.
The operation is not performed.
If you want to stop the dynamic workload broker application, but are not certain if it has already stopped, run the command stopBrokerApplication -user <user_name> -password <password>. This stops the dynamic workload broker application, bypassing appservman. If you receive a message that the dynamic workload broker application is stopping, it means that appservman is stopped.
AWSBHU639W
The dynamic workload broker application is not installed on the local workstation.
You issued a command to start or stop the dynamic workload broker application, but the dynamic workload broker application is not installed, probably because it is not part of the current configuration.
The dynamic workload broker application is normally installed on the master domain manager, backup master domain manager, dynamic domain manager and backup dynamic domain manager.
The operation is not performed.
You cannot use this command on the selected workstation. If you have selected the workstation in error, change the command to identify a different workstation and re-issue the command. If you have selected the wrong command, issue a valid command.
AWSBHU640E
The submitted command cannot be performed. The error is: "error_msg"
See message..
The composer command line client cannot connect to its server. The submitted command cannot be performed.
Verify the connection parameters.
AWSBHU700E
There is a syntax error. A job name, file name or keyword is missing in the submitted command.
See message.
The command is not processed.
Check the syntax of the command in the Reference Manual and resubmit it, adding the missing item.
AWSBHU701E
There is a syntax error. The submitted command appears to contain extra or duplicated characters, or unmatched brackets.
Conman has verified that additional characters appear to be attached to a valid keyword or other parameter. For example, you might have duplicated a character in a keyword, or the dot in a file name.
Alternatively, you have used a pair of brackets in the command, but the opening bracket does not match the closing bracket. For example, you have put an opening round bracket ( and a closing square bracket ].
The command is not processed.
Check the syntax of the command in the Reference Manual and resubmit it, omitting the extra character or characters.
AWSBHU702E
There is a syntax error. The workstation name must be between 1 - 16 bytes.
AWSBHU703E
There is a syntax error. The workstation name must start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores.
See message.
The command is not processed.
Check the syntax of the command in the Reference Manual and resubmit it, supplying a correctly formatted workstation name.
AWSBHU704E
There is a syntax error. The delimiter of a workstation name is a #.
AWSBHU705E
There is a syntax error in the workstation name. The # symbol was found more than once.
See message.
The command is not processed.
Check the syntax of the command in the Reference Manual and resubmit it, omitting the additional # character.
AWSBHU706E
There is a syntax error. The job stream name must be between 1 - 40 bytes.
AWSBHU707E
There is a syntax error. The job stream name must start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores.
See message.
The command is not processed.
Check the syntax of the command in the Reference Manual and resubmit it, supplying a correctly formatted job stream name.
AWSBHU708E
There is a syntax error. The delimiter of the schedule name is .
AWSBHU709E
There is a syntax error. The job name must be between 1 - 40 bytes.
AWSBHU710E
There is a syntax error. The job name must start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores.
See message.
The command is not processed.
Check the syntax of the command in the Reference Manual and resubmit it, supplying a correctly formatted job name.
AWSBHU711E
There is a syntax error. The submitted command has a job as its object but the job name has not been supplied.
See message.
The command is not processed.
Check the syntax of the command in the Reference Manual and resubmit it, supplying a correctly formatted job name.
AWSBHU712E
There is a syntax error. The prompt name must be between 1 and 8 bytes long.
See message.
The command is not processed.
Resubmit the command, supplying a correctly formatted prompt name.
AWSBHU713E
There is a syntax error. The prompt name must start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores.
See message.
The command is not processed.
Resubmit the command, supplying a correctly formatted prompt name.
AWSBHU714E
Prompt name or message number not supplied.
AWSBHU715E
There is a syntax error. The resource name must be between 1 and 8 bytes long and workstation name must be between 1 and 16 bytes
See message.
The command is not processed.
Resubmit the command, supplying a correctly formatted resource name.
AWSBHU716E
There is a syntax error. The resource name must start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores.
See message.
The command is not processed.
Resubmit the command, supplying a correctly formatted resource name.
AWSBHU719E
There is a syntax error. You cannot specify a priority higher that 99 (use hi (= 100), or go (= 101) instead.
See message.
The command is not processed.
Resubmit the command, supplying a correctly formatted priority specification.
AWSBHU720E
User domain length incorrect
AWSBHU721E
The supplied user name is too long. The name can contain up to 47 bytes. If the name contains special characters it must be enclosed in quotes ().
See message.
The command is not processed.
Resubmit the command, supplying a correctly formatted user name.
AWSBHU722E
Duplicate user name given.
AWSBHU723E
There is a syntax error in the specification of a network dependency. The syntax of the command indicates that you wanted to enter a Network ID to identify a workstation in a different network, but the ID is blank.
See message.
The command is not processed.
Rerun the command, entering a valid Network ID before the network delimiter ::.
AWSBHU724E
The Network ID must be between 1 - 40 bytes.
AWSBHU725E
There is a syntax error in the specification of a network dependency. You have submitted a Network ID enclosed in quotes, but either the quote characters that you used before and after the ID are mismatched, or one of them is missing.
See message.
The command is not processed.
Rerun the command, ensuring that if you need to use quotes to enclose the ID, that you use the same type of quote character both before and after the ID.
AWSBHU726E
There is a syntax error in the specification of a network dependency. The Network ID has not been specified.
See message.
The command is not processed.
Rerun the command, specifying the Network ID before the network delimiter ::
AWSBHU727E
There is a syntax error in the specification of a network dependency. You have defined a network dependency which requires the use of quotes, but either the quote characters that you used are mismatched, or one of them is missing.
See message.
The command is not processed.
Rerun the command, ensuring that if you need to use quotes that you use the same type of quote character, and enter both of them.
AWSBHU728E
You have issued a command that includes an exclamation point (!), which is the delimiter for a domain name. However, the exclamation point is not preceded by a valid domain name.
See message.
The command is not processed.
Re-issue the command ensuring that the domain name immediately precedes the exclamation point (there must be no space between them).
AWSBHU729E
There is a syntax error. The domain name must be between 1 and 16 bytes long.
See message.
The command is not processed.
Resubmit the command, supplying a correctly formatted domain name.
AWSBHU730E
There is a syntax error. The domain name must immediately be followed by a workstation name.
See message.
The command is not processed.
Resubmit the command, identifying the workstation as <domain>!<workstation>, without any spaces between the exclamation point and the workstation name.
AWSBHU731E
There is a syntax error. The domain name must start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores.
See message.
The command is not processed.
Resubmit the command, supplying a correctly formatted domain name.
AWSBHU732E
The delimiter of domain name is an exclamation point.
AWSBHU733E
There is a syntax error in the domain name. The delimiter ! has been typed more than once.
See message.
The command is not processed.
Resubmit the command, with just one exclamation point delimiter separating the domain from the workstation.
AWSBHU734E
The job alias name must be between 1 - 40 bytes.
AWSBHU735E
The job stream alias name must be between 1 - 16 bytes.
AWSBHU736E
There is a syntax error. The alias name must start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores.
See message.
The command is not processed.
Resubmit the command, supplying a correctly formatted alias name.
AWSBHU737E
Conman encountered a system error when attempting to retrieve either the current input mode or the current output mode of the console.
The following internal error has occurred: Operating system error given on termios.h Library function tcgetattr or console function GetConsoleMode.
Conman stops.
This is an internal error. Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU738E
Conman encountered a system error when attempting to set either the console input mode or the console output mode.
The following internal error has occurred: Operating system error given on termios.h Library function tcsetattr or console function SetConsoleMode.
Conman stops.
This is an internal error. Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU739E
The supplied user is not in the Symphony file.
See message.
The command is not processed.
If an incorrect user name has been used, resubmit the command, supplying a valid user name.
If the user name supplied is correct, the Symphony file might be corrupt. See the chapter on Symphony file corruption in this guide.
If the problem persists, there is an internal error. In this case, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHU740E
The new password and the confirmation password do not match.
You are trying to change your password, but the two versions of the new password that you supplied are not the same.
The command is not processed.
Resubmit the command, ensuring to type the new password correctly, twice.
AWSBHU741E
Conman is unable to open the audit log file.
Conman is unable to open the audit log file because the open() system call failed for some unspecified reason.
The command you entered has not been executed. Conman continues accepting commands
Verify the following before resubmitting the command:
- Verify that the user has write access to the audit directory: (<TWS_home>/audit).
- Ensure that there is sufficient space in the file system of the audit directory.
AWSBHU743E
There is a syntax error in the name. It must be between 1 and 16 bytes.
See message.
The command is not processed.
Resubmit the command, ensuring to specify a valid workstation name.
AWSBHU744E
There is a syntax error. The job stream name must be between 1 and 16 bytes.
See message.
The command is not processed.
Resubmit the command, ensuring to specify a valid job stream name.
AWSBHU745E
There is a syntax error. The job name must be between 1 and 40 bytes.
See message.
The command is not processed.
Resubmit the command, ensuring to specify a valid job name.
AWSBHU746E
There is a syntax error in the specification of a network dependency. Either the Network ID is missing or it is longer than 40 bytes.
See message text.
The command is not processed.
Resubmit the command, ensuring that the network dependency is correctly specified.
AWSBHU747E
There is a syntax error. The job alias name must be between 1 and 40 bytes.
See message.
The command is not processed.
Resubmit the command, ensuring to specify a valid job alias name.
AWSBHU748E
There is a syntax error. The job stream alias name must be between 1 and 16 bytes.
See message.
The command is not processed.
Resubmit the command, ensuring to specify a valid job stream alias name.
AWSBHU749E
Alias name must start with an alpha and contain only alphanumeric characters.
AWSBHU753E
Not found
AWSBHU758E
The command cannot be performed because one or more successor jobs cannot be rerun. Check the Messages column for details.
See the Messages column for details.
The command is not performed.
Resubmit the command after examining and solving the issues listed in the Messages column.