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

Explanation

See message.

error_text is the error message. It supplies you with more details about the error causes.

System action

The command is not processed.

Operator response

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.

The chapter 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".

Explanation

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.

System action

The command is not processed.

Operator response

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.

The Reference Manual for more details about start and stop commands.

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"

Explanation

See message.

error_text is an error message.

System action

Conman stops.

Operator response

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.

The chapter on setting security in the Reference Manual for more details.

AWSBHU004E The job logon name you specified is not valid.

Explanation

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.

System action

The command is not processed.

Operator response

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"

Explanation

See message.

error_text is the error message, which provides you with more details about the error causes.

System action

Conman stops.

Operator response

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.

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

Explanation

See message.

record_number is the record number.

record_type_expected is the record type expected.

record_type_found is the record type found.

System action

Conman stops.

Operator response

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.

The chapter in this guide on 'Symphony file corruption'.

AWSBHU024E The mozart directory cannot be accessed or is missing some files.

Explanation

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.

System action

The command is not processed.

Operator response

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.

Explanation

See message.

System action

The command is not processed.

Operator response

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.

The Reference Manual for 'Selecting job stream in commands'. See also the chapter in this guide on 'Symphony file corruption'.

AWSBHU028E The recovery action is not correct. It must be one of the following: STOP, CONTINUE, RERUN.

Explanation

You have supplied a recovery action that is incorrectly typed, or not supported. Only the following are permitted:

recovery=STOP
recovery=CONTINUE
recovery=RERUN

System action

The command is not processed.

Operator response

Reissue the command, supplying one of the permitted recovery actions.

The Reference Manual for full details of the command syntax.

AWSBHU029E Fatal: Should not be here: !1 [#!2].

AWSBHU038E Conman cannot run the command because the command string has too many characters.

Explanation

See message. The number of characters accepted by the command line is operating system-dependent.

System action

The command is not processed.

Operator response

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.

The Reference Manual for details of the command syntax, and to find ways of reducing the number of characters in the command.

AWSBHU039E You have issued a command containing an incorrect argument keyword. The acceptable keywords for this command are as follows: "keyword_list"

Explanation

See message.

keyword_list is the list of accepted argument keywords.

System action

The command is not processed.

Operator response

Correct the argument keyword to one shown in the list , and re-issue the command.

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

AWSBHU040E You have issued a command containing an incorrect delimiter. The accepted delimiters are the following: "delimiters"

Explanation

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.

System action

The command is not processed.

Operator response

Correct the delimiter you have used to conform to the supplied list and to correspond to the indicated usage.

The Reference Manual..

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.

Explanation

See message.

command is the conman command requiring the Symphony file.

System action

The command is not processed.

Operator response

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.

The chapter in this guide on 'Symphony file corruption'.

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.

Explanation

See message.

command is the conman command requiring the Symphony file.

System action

The command is not processed.

Operator response

Set the production plan (Symphony file) to the current, using the conman setsym command.

The Reference Manual.

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.

Explanation

See message.

System action

The command is not processed.

Operator response

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.

The Reference Manual for more details.

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

Explanation

See message.

System action

The command is not processed.

Operator response

Re-issue the command using a fully qualified filename.

The Reference Manual.

AWSBHU045E You have issued the following command: "command " with one or more arguments, but this command does not have any arguments.

Explanation

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.

System action

The command is not processed.

Operator response

Reissue the command without arguments.

The Reference Manual.

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

Explanation

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.

System action

Conman stops.

Operator response

Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBHU047E A command has been supplied without its required selector.

Explanation

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.

System action

The command is not processed.

Operator response

Re-issue the command, adding a valid selector after the command name and before the arguments.

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

AWSBHU048E A command has been supplied with an ambiguous selector.

Explanation

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.

System action

The command is not processed.

Operator response

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.

The Reference Manual for more details.

AWSBHU049E You have issued a command with a selector keyword, but the supplied selector keyword is not valid.

Explanation

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.

System action

The command is not processed.

Operator response

Re-issue the command, adding a valid selector after the command name and before the arguments.

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

AWSBHU050E You have issued a command with a selector keyword, but the supplied selector keyword is not valid for this command.

Explanation

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.

System action

The command is not processed.

Operator response

Re-issue the command, adding a valid selector after the command name and before the arguments.

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

AWSBHU051E You have issued a command with a valid selector keyword, but have omitted to identify the object.

Explanation

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

See message.

workstation_name is the extended agent workstation name.

System action

The command is not processed.

Operator response

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.

Explanation

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.

System action

The command is not processed.

Operator response

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.

The Reference Manual.

AWSBHU060E You have issued a command that has attempted to modify or delete the EXTERNAL job stream. This is not permitted.

Explanation

The EXTERNAL job stream is used to monitor the status of internetwork dependencies, and cannot be modified or deleted.

System action

The command is not processed.

Operator response

To modify an internetwork dependency for a given job you have to use the conman adddep and deldep commands on that job.

The Reference Manual for more details about the adddep and deldep commands.

AWSBHU061E The domain manager of this workstation cannot be found in the Symphony file.

Explanation

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.

System action

The command is not processed.

Operator response

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.

Explanation

A command has been issued remotely using the MGR option, which is valid only on the local workstation.

System action

The command is processed, ignoring the MGR option.

Operator response

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

Explanation

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.

System action

The command is not processed.

Operator response

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.

Explanation

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.

System action

The command is not processed.

Operator response

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.

Explanation

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.

System action

The command is not processed.

Operator response

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.

The Reference Manual.

AWSBHU066E The domain you supplied to the switchmgr command is not in the Symphony file.

Explanation

See message.

System action

The switchmgr command is not processed.

Operator response

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.

The Reference Manual for details of the switchmgr command, and this guide for a description of how to solve a corruption of the Symphony file.

AWSBHU067E A manager workstation has not been specified for the switchmgr command.

Explanation

See message.

System action

The switchmgr command is not processed.

Operator response

Rerun the switchmgr command ensuring that you supply a domain and a manager workstation.

The Reference Manual for details of the switchmgr command.

AWSBHU068E The following workstation supplied to the switchmgr command is not in the Symphony file: "workstation_name".

Explanation

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.

System action

The command is not processed.

Operator response

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.

The Reference Manual for details of the switchmgr command, and this guide for a description of how to solve a corruption of the Symphony file.

AWSBHU069E Too many parameters have been supplied to this switchmgr command.

Explanation

See message.

System action

The command is not processed.

Operator response

Rerun the command with the correct syntax.

The Reference Manual for the correct syntax of this command.

AWSBHU070E The following domain name could not be found in the Symphony file: "domain_name".

Explanation

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.

System action

The command is not processed.

Operator response

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.

The Reference Manual for details of the switchmgr command, and this guide for a description of how to solve a corruption of the Symphony file.

AWSBHU071E An error was encountered accessing the following file: "file_name". The following gives more details of the error: "error"

Explanation

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.

System action

The command is not processed.

Operator response

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.

Explanation

See message.

System action

The command is not processed.

Operator response

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.

TheReference Manual for details of the syntax and descriptions and examples of how to select objects.

AWSBHU073E The mozart database does not exist, or cannot be opened or accessed. The following gives more details of the error: "error_text".

Explanation

See message.

error_text is an optional error message. It provides you with more details about the cause of the error.

System action

Conman stops if it requires the mozart database to continue. If it can continue in the absence of the file it does so.

Operator response

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

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

Explanation

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.

System action

Conman stops.

Operator response

Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

Explanation

You cannot add a dependency to, submit a job to, or kill a job in a cancelled job stream.

System action

The command is not processed.

Operator response

Check that you have correctly identified the job stream and have issued the correct command.

The Reference Manual.

AWSBHU088E You cannot rerun user jobs.

Explanation

See message.

System action

The command is not processed.

Reissue the rerun command, supplying the parameter ;step=<step_name> if you want to rename the job.

The Reference Manual for details of the rerun command.

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

Explanation

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.

System action

Conman stops.

Operator response

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.

The Reference Manual.

AWSBHU095E The job stream or job dependency "dependent_job_stream_or_job" was not found in the Symphony file.

Explanation

dependent_job_stream_or_job is the dependent job stream or job name identified by the follows dependency keyword.

System action

The command is not processed.

Operator response

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

Conman stops.

Operator response

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

Explanation

See message.

maximum_size is the maximum number of bytes accepted in the path name.

System action

The command is not processed.

Operator response

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.

The Reference Manual.

AWSBHU112E The supplied job specification is not in the correct format. You can use only <workstation>#<job> or <job>.

Explanation

See message.

System action

The command is not processed.

Operator response

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

The Reference Manual for full details.

AWSBHU114E The supplied switchmgr command did not identify the domain, the new manager, or both.

Explanation

See message.

System action

The command is not processed.

Operator response

Reissue the switchmgr command, ensuring to identify the domain name and the new manager name.

The 'switchmgr' command syntax in the Reference Manual.

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

Explanation

See message.

current_manager is current domain manager.

proposed_manager is the proposed domain manager.

System action

The command is not processed.

Operator response

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.

The Planning and Installation Guide.

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

Explanation

See message.

proposed_manager is the proposed domain manager.

System action

The command is not processed.

Operator response

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.

The Planning and Installation Guide.

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

Explanation

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.

System action

The command is not processed.

Operator response

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.

Explanation

You have used one or more wildcards (such as: '@' or '?') in the specification of the domain name.

System action

The command is not processed.

Operator response

Rerun the command, supplying a fully qualified domain name.

The Reference Manual for more details about domain selection.

AWSBHU121E Conman could not identify the parent domain of the following workstation: "workstation_name".

Explanation

See message.

workstation_name is a workstation for which the parent domain could not be found.

Explanation

See message.

workstation_name is the name of the workstation where the time dependency is to be resolved.

System action

The command is not processed.

Operator response

Either rerun the command without specifying a time zone or enable time zone use at the indicated workstation.

The Planning and Installation Guide for more details.

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.

Explanation

See message.

System action

The command is not processed.

Operator response

Rerun the command, supplying a numeric value for the wait keyword in the range 0 to 1200.

The Reference Manual for a description of the 'submit' command.

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

Explanation

See message.

minimum_value to maximum_value is the valid range of numeric values.

System action

The command is not processed.

Operator response

Rerun the command, supplying a valid numeric value for the time parameter that is within the indicated range.

The Reference Manual for a description of the 'submit' command.

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

Explanation

See message.

date_format is the permitted format.

System action

The command is not processed.

Operator response

Rerun the command, supplying a valid date in the indicated format.

The Reference Manual for a description of the 'submit' command.

AWSBHU143E The action associated with the onuntil attribute is not correct. It must be one of the following: suppr, cont, canc.

Explanation

See message.

System action

The command is not processed.

Operator response

Rerun the command, supplying a valid action for the onuntil attribute.

The Reference Manual for a description of the 'submit' command.

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

AWSBHU147E The keywords "keyword_1" and "keyword_2" are mutually exclusive. You cannot supply both of them.

The Reference Manual.

AWSBHU150W An internal error has occurred.The program is unable to initialize the GSKit libraries.

Explanation

A problem has occurred with the installation or configuration of the GSKit libraries, or both, and they cannot be initialized.

System action

The program cannot commence a secure connection, so stops.

Operator response

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

Explanation

See message.

date_format is the permitted format for the date from the localopts file, for example, yymmdd.

System action

The command is not processed.

Operator response

Rerun the command, supplying a valid date in the indicated format.

The Reference Manual for a description of the 'submit' command.

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.

Explanation

See message.

System action

The command is not processed.

Operator response

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.

The Reference Manual for a description of the 'submit' command.

AWSBHU153E The keyword "keyword_1" can only be supplied if the keyword "keyword_2" is specified.

AWSBHU156E The workstation you specified is already the event processor.

Explanation

You have tried to set a workstation as the new event processor, but it is already the event processor.

System action

The command is not processed.

Operator response

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.

Explanation

The command contains at least one unsupported keyword.

System action

The command is not processed.

Operator response

Correct the syntax and retry the command.

The User's Guide and Reference for details of the syntax of 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.

Explanation

See message.

workstation_name is the agent, or pool, or dynamic pool, or remote engine, or broker workstation name.

System action

The command is not processed.

Operator response

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.

Explanation

See message.

workstation_name is the broker agent workstation name.

System action

The command is not processed.

Operator response

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

Explanation

See message.

System action

The command is not processed.

Operator response

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.

Explanation

See message.

workstation_name is the master domain manager, or domain manager name.

System action

The command is not processed.

Operator response

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.

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.

Explanation

See message.

workstation_name is the pool, or dynamic pool, or remote engine workstation name.

System action

The command is not processed.

Operator response

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

Explanation

Conman cannot start a new process because the HCL Workload Automation license has expired

System action

The command can continue but it is not able to start new processes.

Operator response

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.

The chapter on 'Symphony file corruption' in the Troubleshooting guide.

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.

Explanation

See message.

workstation_name is the remote engine, or broker workstation name.

System action

The command is not processed.

Operator response

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.

Explanation

You cannot rerun a job in a suppressed job stream.

System action

The command is not processed.

Operator response

Operator response

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.

The User's Guide and Reference.

AWSBHU184W The "keyword" variable value is longer than the maximum number of bytes and will be truncated.

Explanation

See message.

System action

Operator response

Reduce the lenght to avoid that the variable is truncated.

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.

System action

The command is not processed.

Operator response

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.

The Reference Manual for full details of the command syntax.

AWSBHU508E You do not have access to this file or database object.

Explanation

See message.

System action

The command is not processed.

Operator response

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.

The 'Security Notes' section of the Planning and Installation Guide for more information about security.

AWSBHU509E The requested file cannot be found.

Explanation

See message.

System action

The command is not processed.

Operator response

If you intended to rerun an existing job stream, use the submit command with the alias option.

The Reference Manual for details of the indicated commands and options.

AWSBHU516E You have not supplied a valid alias of the job you are trying to resubmit.

Explanation

Explanation

See message.

System action

The command is not processed.

Operator response

Select a valid job name and rerun the command.

The Reference Manual.

AWSBHU523E You have issued a link or an unlink command on a standalone workstation (on which mailman is not running).

Explanation

See message.

System action

The command is not processed.

Operator response

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.

Explanation

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.

System action

The command is not processed.

Operator response

Re-issue the command, either omitting the delimiter or supplying the keyword or value that is required by the syntax to follow it.

The Reference Manual for full details of the syntax for commands.

AWSBHU526E The following internal error occurred when conman attempted to display a JCL file: "error_message".

Explanation

See message.

error_message is an operating system error message returned by the function pipe().

System action

The command is not processed.

AWSBHU535E The following workstation is not in the Symphony file: "workstation_name".

Explanation

See message.

workstation_name is the name of the workstation not found.

System action

The command is not processed.

Operator response

Re-issue the command, selecting a valid workstation name.

The Reference Manual for information on how to identify workstations.

AWSBHU536E The following domain is empty: "domain_name".

Explanation

See message.

domain_name is the name of the empty domain.

System action

The command is not processed.

Operator response

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.

Explanation

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.

System action

The command is not processed.

Operator response

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

The Reference Manual for more details about using the link and unlink commands.

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":

Explanation

The internal message is the following: Unknown link case encountered.

workstation_name is the workstation name that cannot be linked to or unlinked from.

System action

The command is not processed.

Operator response

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.

Explanation

See message.

System action

The command is not processed.

Operator response

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.

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

Explanation

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.

Explanation

See message.

System action

The command is not processed.

Operator response

Re-issue the command using a path name shorter than the maximum indicated.

The Reference Manual.

AWSBHU545E You have supplied a path name that does not match the workstation type: "workstation_type".

Explanation

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.

System action

The command is not processed.

Re-issue the command, omitting the duplicated dependency.

AWSBHU553E An error has occurred while starting an internal component (clagent).

Explanation

See message.

System action

The command is not processed.

Operator response

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

Explanation

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.

System action

The command is not processed.

Operator response

Verify from the error message where the problem is.
Fix the problem and re-issue the command.

Explanation

The Event Driven Workload Automation feature has been disabled by optman, which set the enEventDrivenWorkloadAutomation option to NO.

Monman cannot be started.

System action

The command is not processed.

Operator response

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.

Explanation

See message.

System action

The job for which the keyword is specified is added to the plan, but it cannot run. Conman proceeds.

Operator response

Specify the maxdur time for the onmaxdur keyword and then resubmit the job with an alias.

The User's Guide and Reference for more details about time dependencies.

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.

Explanation

See message.

System action

The job for which the keyword is specified is added to the plan, but it cannot run. Conman proceeds.

Operator response

Specify the mindur time for the onmindur keyword and then resubmit the job with an alias.

The User's Guide and Reference for more details about time dependencies.

AWSBHU600E There is a logic error in the follows dependencies. The dependency "circular_dep" is circular.

Explanation

See message.

circular_dep is the dependency which refers directory or indirectly to itself.

System action

The command is not processed.

Operator response

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.

The Reference Manual for more details about dependencies.

AWSBHU601E Cannot create semaphore, Error number: !1

AWSBHU602E Cannot create thread, Error number: !1

AWSBHU603E Cannot release thread, Error number: !1

Operator response

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.

Explanation

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.

System action

The operation is not performed.

Operator response

Do one of the following:

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.

The Reference Manual for details of the syntax of the connection parameters.

AWSBHU611W Conman could not initialize the HTTP or HTTPS connection.

Explanation

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.

System action

conman continues.

Operator response

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.

Explanation

See message.

System action

The operation is not performed.

Operator response

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.

Explanation

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.

System action

Conman does not proceed.

Operator response

Explanation

See message.

System action

The operation is not performed.

Operator response

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.

The Reference Manual for full details of the parameters for the composer command line client.

AWSBHU634E The command "command_name" cannot be performed, because the event processor workstation is set to ignore in the production plan.

Explanation

See message.

command_name is the issued command.

System action

The submitted command cannot be performed.

Operator response

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.

The Reference Manual for full details of the parameters for the composer command line client.

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.

Explanation

See message.

System action

The submitted command cannot be performed.

Operator response

Change the name of the variable table to conform to the rules indicated in the message and resubmit the command.

The User's Guide and Reference for full details of the variable table.

AWSBHU636E The Workload Service Assurance feature is not enabled.

Explanation

See message.

Workload Service Assurance is a feature which can be enabled or disabled. At present it is disabled.

System action

The submitted command cannot be performed.

Operator response

Use optman to enable the Workload Service Assurance feature.

The User's Guide and Reference for full details of the Workload Service Assurance feature.

AWSBHU638W The dynamic workload broker application on workstation "workstation_name" is already stopped.

Explanation

See message.

System action

The operation is not performed.

Operator response

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.

Explanation

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.

System action

The operation is not performed.

Operator response

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"

Explanation

See message..

System action

The composer command line client cannot connect to its server. The submitted command cannot be performed.

Operator response

Verify the connection parameters.

Resubmit the command, supplying a correctly formatted domain name.

The Reference Manual for details of how to identify a domain.

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.

Explanation

See message.

System action

The command is not processed.

Operator response

Resubmit the command, with just one exclamation point delimiter separating the domain from the workstation.

The Reference Manual for details of how to identify a domain.

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.

Explanation

See message.

System action

The command is not processed.

Operator response

Operator response

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.

See the chapter on 'Symphony file corruption' in this guide.

AWSBHU740E The new password and the confirmation password do not match.

Explanation

You are trying to change your password, but the two versions of the new password that you supplied are not the same.

System action

The command is not processed.

Operator response

Operator response

Resubmit the command after examining and solving the issues listed in the Messages column.

The User's Guide and Reference for more information.

AWSBHU - Conman messages

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

Explanation

System action

Operator response

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

Explanation

System action

Operator response

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"

Explanation

System action

Operator response

AWSBHU004E The job logon name you specified is not valid.

Explanation

System action

Operator response

AWSBHU009E Conman encountered a problem trying to read the Symphony file. The following gives more details of the error: "error_text"

Explanation

System action

Operator response

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

Explanation

System action

Operator response

AWSBHU016E One of the values specified for a numeric argument is not numeric.

Explanation

System action

Operator response

AWSBHU017E A value specified for a range-limited numeric argument is below the minimum permitted value. The permitted range is from: "minimum" to "maximum".

Explanation

System action

Operator response

AWSBHU018E A value specified for a range-limited numeric argument is above the maximum permitted value. The permitted range is from: "minimum" to "maximum".

Explanation

System action

Operator response

AWSBHU021E The agent on workstation: "workstation_name" cannot be started because it has not got the latest Symphony file version.

Explanation

System action

Operator response

AWSBHU022E The time value specified as an argument is incorrect. It must be numeric, between 0000 and 2359.

Explanation

System action

Operator response

AWSBHU023E You have issued an opens job qualifier with incorrect syntax.

Explanation

System action

Operator response

AWSBHU024E The mozart directory cannot be accessed or is missing some files.

Explanation

System action

Operator response

AWSBHU025E Conman either cannot find the job stream in the Symphony file, or the specified workstation name is not correct.

Explanation

System action

Operator response

AWSBHU028E The recovery action is not correct. It must be one of the following: STOP, CONTINUE, RERUN.

Explanation

System action

Operator response

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.

Explanation

System action

Operator response

AWSBHU032E You have issued a rerun command that does not uniquely identify a workstation.

Explanation

System action

Operator response

AWSBHU033E You have supplied more instances of a dependency option than are permitted by the issued command.

Explanation

System action

Operator response

AWSBHU034E You have not supplied a mandatory selection argument (job, or job stream, for example).

Explanation

System action

Operator response

AWSBHU035E You have issued a command with a dependency keyword (follows, needs, opens, prompt), but the value associated with the keyword is not valid.