HCL Workload Automation messages
This part contains message help for many of the messages issued by the HCL Workload Automation engine and command line. The messages are organized in alphabetical order of message within alphabetical order of subcomponent (message set). Each subcomponent is in a separate section.
If the information does not sufficiently explain the situation you have encountered, see HCL Workload Automation: Troubleshooting Guide, which has extended error scenarios for many situations, as well as information about diagnostic tools and how to obtain support.
- HCL Workload Automation message format
HCL Workload Automation messages follow a standard message format. - AWKALR - Allocation repository messages
This section lists error and warning allocation repository messages that might be issued. - AWKALR001E
Cannot create the JSDL string from the SDO. - AWKALR002E
Unable to create the EPR string from the SDO. - AWKALR003E
No resources are available for deletion for allocation ID:"allocationID". - AWKALR004E
No allocation is available for deletion for allocation ID:"allocationID". - AWKALR005E
Unable to find any resources for allocation ID:"allocationID". - AWKALR006E
Unable to create the JSDL from the string. - AWKALR007E
Unable to create the EPR from the string. - AWKALR081E
Unable to create an allocation record in the allocation repository database. - AWKAUD - Audit service messages
This section lists error and warning audit service messages that might be issued. - AWKAUD050W
The audit property setting "property_name" is not specified or is blank in the auditing configuration file. Using the default value: "default_value". - AWKAUD051W
The directory name specified in the audit property "property_name" is not valid. Using default value: "default_value". - AWKAUD052W
The audit file prefix "prefix_value" is not valid or the auditing file path is too long. Using the default value "default_value". - AWKAUD053W
The audit file prefix is not specified or is blank. Using the default value "default_value". - AWKAUD054W
The audit property "property_name" is not valid, is negative, or exceeds the maximum supported value. Using the maximum value as default "default_value". - AWKAUD100E
Unable to find the audit configuration file "audit_file_path". Using the default configuration settings. - AWKAUD101E
Unable to instantiate the "audit_type" event type. - AWKAUD102E
Unable to instantiate the "provider_name" Auditing Event Provider. - AWKAUD103E
Unable to log the "event_type" audit event type. - AWKAUD104E
Unable to process the "event_type" audit event type. - AWKAUD105E
Unable to use the directory specified for audit logs. The specified path and the filename might exceed the maximum length for files in the current operating system. Using: "new_file_location". - AWKAZR - Job plug-in for Microsoft Azure messages
This section lists error and warning messages that might be issued by the job plug-in for Microsoft Azure. - AWKAZR001E
Test connection failed. Please check your credentials. - AWKAZR003E
Error. Please fill in at least one of these two sections: \"Manage Existing Virtual Server\" or \"Create New Virtual Server\". - AWKAZR004E
Error. Please fill in one of these two sections: \"Manage Existing Virtual Server\" or \"Create New Virtual Server\". - AWKAZR005E
Error. - AWKAZR006E
An error was encountered. A required field is missing. Private and Public primary IP values are optional. - AWKAZR007E
No Virtual Machines. - AWKAZR008E
Get Virtual Machines failed. - AWKAZR009E
No details. - AWKAZR010E
Get Virtual Machine Details failed. - AWKAZR011E
Select a Virtual Machine please. - AWKAZR012E
No Source Groups. - AWKAZR013E
Get Source Groups failed. - AWKAZR014E
No images. - AWKAZR015E
Get Images failed. - AWKAZR016E
No sizes. - AWKAZR017E
Get Sizes failed. - AWKAZR018E
The Azure operation "operation" failed. - AWKASP - Job plug-in for Apache Spark messages
This section lists error and warning messages that might be issued by the job plug-in for Apache Spark. - AWKASP002E
Unable to perform the test connection, please check your Spark master is up and running. - AWKASP004E
The spark job exited with state "". - AWKASP005E
The field "" must be a positive integer and its value must be lower than 9999999. - AWKASP006E
The field "" has not a valid value. - AWKASP007E
An error occurred during the execution of the job. The message is "". - AWKASP008E
Unable to reach the Apache Spark web UI at address "". - AWKASP009E
The field "" cannot contain illegal characters: "" - AWKASP010E
An error occurred during the submission of the job. The message is "". - AWKASP011E
The field "" cannot end with a '/' character - AWKASP012E
The field "" must contain one of the following values: "" - AWKBIG - Job plug-in for IBM BigInsights messages
This section lists error and warning messages that might be issued by the job plug-in for IBM BigInsights. - AWKBIG002E
Test connection failed. The error was "error" - AWKBIG003E
The application failed to run. - AWKBIG004E
The application cannot start. The error is "error" - AWKBIG005E
No elements available for the specified filter. - AWKBIG006E
An error occurred parsing the response. The error message is "error" - AWKBIG007E
The selected application is not a Workflow. - AWKBIG008E
The execution of the workbook "workbook" failed. - AWKBIG009E
The execution of the workbook "workbook" is stopped. - AWKBIG010E
The execution of the workbook "workbook" cannot start. The error is "error" - AWKBIG011W
The job was canceled by the user. - AWKBIG012E
The status of the workbook "workbook" cannot be retrieved. The error is "error" - AWKBIG013E
The status of the workbook cannot run, the following error was returned: "error". Additional details: "error details" - AWKBIG014E
The status of the workbook "workbook" is unknown. The error is "error" - AWKBIG015E
The status of the workbook "workbook" is unknown. - AWKBIG016E
The required workbook parameter is missing. - AWKBIG017E
The required application id parameter is missing. - AWKBIG018E
The required execution name parameter is missing. - AWKBIG019E
Incorrect application value. The application must be an identifier or ends with (aid:identifier) - AWKBIG020E
Incorrect value "name" in the application parameter list. The application parameter value must ends with (isRequired:boolean, paramtype:string, name:string) - AWKCAU - Centralized Agent Update messages
This section lists error and warning messages that might be issued by the Centralized Agent Update feature. - AWKCAU002E
Unable to connect to the engine. The error was "error" - AWKCAU005E
The Update operation failed for the workstation "workstation". The error is "error" - AWKCAU006E
The Update operation failed for the following workstations "failedWorkstations". - AWKCAU007E
An error occurred parsing the response. The error message is "error" - AWKCAU008E
Incorrect value "name" in the application parameter list. The application parameter value must ends with (isRequired:boolean, paramtype:string, name:string) - AWKCAU009E
Invalid authorization. Missing or wrong credentials. - AWKCAU010E
At least one workstation must be selected - AWKCAU011E
Cannot retry the list of workstations. The HTTP response code is "code" - AWKCAU012E
The maximum number of workstations that can be updated is "maxnumber" - AWKCAU013E
An error occurred while running the job. - AWKCAU015E
The required user name parameter is missing. - AWKCAU016E
The required user password parameter is missing. - AWKCAU017E
The required server address parameter is missing. - AWKCAU018E
The required server port parameter is missing. - AWKCAU019E
The required workstations parameter is missing. - AWKCAU020E
The required protocol parameter is missing. - AWKCDM - Change and configuration management database messages
This section lists error and warning change and configuration management database messages that might be issued. - AWKCDM001W
An error occurred while loading the user configuration file "config_file". The following error was returned: "error". The default values will be used. - AWKCDM002E
An error occurred while getting the configuration file "config_file". The following error was returned: "error". - AWKCDM003E
Unable to find the configuration file "config_file" . - AWKCDM005E
An exception occurred on the CCMDB server. The following error was returned: "error". - AWKCDM006E
The operation failed because the required parameter "parameter" is missing. Include it in the command or in the configuration file. - AWKCDM007E
The command failed because it included an unsupported parameter "parameter". - AWKCDM008E
The operation failed because the URL specified for the Dynamic Workload Broker server "URL"is not correct. - AWKCDM009E
A problem occurred while contacting the Dynamic Workload Broker server. The Dynamic Workload Broker service is not available. - AWKCDM010E
Unable to invoke Dynamic Workload Broker Web Services because an incorrect parameter was specified. - AWKCDM011E
Unable to invoke Dynamic Workload Broker Web Services. - AWKCDM012E
Unable to connect to the Dynamic Workload Broker server. The user credentials might be incorrect. - AWKCDM013E
The operation failed because the user is not authorized to perform it. - AWKCDM014E
An unexpected error occurred. - AWKCGE - Job plug-in for IBM Cognos messages
This section lists error and warning messages that might be issued by the job plug-in for IBM Cognos. - AWKCGE001E
You did not specify the report path. - AWKCGE002E
You did not specify the namespace. - AWKCGE003E
You did not specify the username. - AWKCGE004E
You did not specify the password. - AWKCGE005E
You did not specify the namespace and the username. - AWKCGE006E
You did not specify the namespace and the password. - AWKCGE007E
You did not specify the username and the password. - AWKCGE008E
An error occurred while attempting to retrieve the namespaces. - AWKCGE009E
An error occurred while attempting to retrieve the reports. - AWKCGE010E
No report was found on the Cognos server. - AWKCGE011E
No namespace was found on the Cognos server. - AWKCGE012E
An error occurred while attempting to connect to the IBM Cognos server. The IBM Cognos server connection parameters are incorrect: "error_msg". - AWKCGE013E
An error occurred retrieving the IBM Cognos report service. - AWKCGE014E
An Apache exception occurred communicating with the IBM Cognos server. The Apache error message is: "error_msg". - AWKCGE015E
An error occurred running the IBM Cognos report. - AWKCGE016E
The directory "file_path" you specified to save the report file does not exist. - AWKCGE017E
The server port is not valid. Specify a value in the 1 - 65535 interval. - AWKCGE018E
You did not specify either the output file or the email addresses to which you want to send the report. - AWKCGE019E
You did not specify the report format. - AWKCGE020E
The value "report_format" specified for the formatTypes is not valid. Specify a valid value. - AWKCGE021E
You did not specify the directory name for the output file. The output file must contain the fully qualified path. - AWKCGE022E
You did not specify the server address. - AWKCGE023E
You did not specify the port. - AWKCGE024E
An error occurred while attempting to retrieve the parameters. - AWKCGE026E
An error occurred during connection to the IBM Cognos report service. Verify your credentials. - AWKCGE027E
An error occurred during the connection to the IBM Cognos report service. The error is: "error_msg". - AWKCGE028E
The HCL Workload Automation agent cannot monitor the IBM Cognos report. - AWKCGE029E
An error occurred while retrieving the list of available IBM Cognos reports. - AWKCGE030E
You did not specify the file name for the output file. The output file must contain the fully qualified path. - AWKCGE031E
An error occurred while retrieving the report output. - AWKCGE032E
An error occurred when sending the report output by email. - AWKCGE033E
An error occurred when saving the report to the file "report_file". - AWKCGE034E
An error occurred when deleting the report. - AWKCGE035E
An error occurred when saving the report to the file "report_file". The error is: "error_msg". - AWKCGE036E
An error occurred when deleting the report. The error is: "error_msg". - AWKCGE037E
An error occurred when sending the report output by email. The error is: "error_msg". - AWKCGE038E
An error occurred when retriving the report output. The error is: "error_msg". - AWKCGE039E
An error occurred while running the IBM Cognos report. The error is: "error_msg". - AWKCGE040E
The report with path "report_path" was not found on the Cognos server. - AWKCGE041E
The user "user_name" does not have the "report_permission" permission on the report with path "report_path". - AWKCGE042E
You specified an invalid format "report_format" for the interactive report "report_path". Specify the HTML format. - AWKCGE056E
The IBM Cognos report completed with errors. - AWKCGE057E
The IBM Cognos report cannot be submitted. - AWKCLI - Command line messages
This section lists error and warning messages that might be generated by the dynamic workload broker Command Line Interface. - AWKCLI001E
An error occurred while getting the configuration file "config_file". The following error was returned: "error". - AWKCLI013E
The required variable "variable" is missing from the configuration file. - AWKCLI031E
The command failed because of a missing mandatory parameter "parameter". - AWKCLI032E
The command failed because of a missing value for a parameter: "parameter" - AWKCLI033W
Unable to read the configuration file "file_name" . The default configuration file will be used. - AWKCLI034E
Unable to read the default configuration file. - AWKCLI035E
Unable to read configuration files. - AWKCLI036E
The command failed because the variable "variable" is not present in the configuration file. - AWKCLI040E
The command failed because the parameter "VALUE_0" is not specified as a command parameter and the property "VALUE_1" is not present in the configuration file. - AWKCLI041E
The command failed because of a missing parameter. One of the following parameters is required: "parameter_1" , "parameter_2" . - AWKCLI042E
The command failed because the following mutually exclusive parameters were both included. "parameter_1" , "parameter_2" . - AWKCLI043E
The command failed because a variable has an incorrect format: "VALUE_0". - AWKCLI044E
The command failed because neither of the following affinity parameters was specified: "parameter_1" , "parameter_2" .. One of the parameters must be specified. - AWKCLI045E
The command failed because only one of the following affinity parameters can be specified: "parameter_1" , "parameter_2" . - AWKCLI046E
The command failed because of an incorrect affinity format: "VALUE_0". - AWKCLI047E
The command failed because parameter "parameter" is not applicable. - AWKCLI049E
Unable to find the address of a Dynamic Workload Broker server in the configuration file. - AWKCLI050E
The Dynamic Workload Broker server address "address"is not in a correct format. - AWKCLI051E
An unexpected error occurred while submitting the job. - AWKCLI052E
Unable to find the JSDL file "file_name". - AWKCLI053E
The JSDL file format is not correct: "VALUE_0" --- "VALUE_1". - AWKCLI054E
Dynamic Workload Broker server service is not available - AWKCLI055E
The operation failed because the input parameter is incorrect. "parameter" - AWKCLI056E
Dynamic Workload Broker server - operation failed. "VALUE_0" - AWKCLI057E
An unexpected error occurred. - AWKCLI059E
Unable to find job ID "jobID". - AWKCLI060E
The operation failed because the specified state is not a valid job state. - AWKCLI061E
The operation failed because job ID "jobID"is not correct. - AWKCLI063E
The operation failed because of an incorrect parameter and value: "parameter" , "value". This parameter does not support wildcards. - AWKCLI065E
The job definition file "file_name" contains errors. - AWKCLI066E
The job definition name "job_def"is not correct. - AWKCLI067E
Unable to find the job definition "job_def" . - AWKCLI068E
The command failed because of an incorrect query parameter. - AWKCLI069E
The specified job state "state"is not valid. - AWKCLI070E
One of the selection criteria must be specified. - AWKCLI072E
Unable to find job status "status". - AWKCLI073E
The command failed because the date "date" is in an incorrect format. The valid format is "date_format" - AWKCLI074E
You have specified an incorrect date: "date" - AWKCLI075E
The date from "date_1"to "date_2" is not valid. - AWKCLI087E
Unable to find JSDL file "file_name" . - AWKCLI088E
Unable to connect to the Dynamic Workload Broker server.. - AWKCLI089E
Unexpected exception received while submitting the job. - AWKCLI090E
An unexpected error occurred. Unable to contact the Dynamic Workload Broker server. - AWKCLI098E
The command failed because of a missing value for parameter "parameter" . - AWKCLI099E
The command failed because a mandatory parameter "parameter" is missing. - AWKCLI100E
The command failed because the value specified for the offset parameter "offset" is out of range. Specify a number between 0 and "Long_MAXVALUE". - AWKCLI101E
The command failed because the value specified for the sizePage parameter "page_size" is out of range. Enter a valid number between 0 and "Integer_MAXVALUE". - AWKCLI102E
A database error occurred. The internal error returned by the database manager is: "db_error". - AWKCLI105E
The command failed because the format of the Resource Definition file is incorrect. - AWKCLI109E
Incorrect JSDL file format "VALUE_0" --- "VALUE_1". - AWKCLI110E
The job ID "JobID" is not correct. - AWKCLI120E
The command failed because of incorrect input parameters "parameters" . - AWKCLI121E
Resource Advisor - Operation failed.. - AWKCLI122E
Job Dispatcher - Operation failed."VALUE_0". - AWKCLI129E
The specified date "date" is in an incorrect format. The valid format is "date_format". - AWKCLI130E
You have specified an incorrect date: "date". - AWKCLI132E
The Job Dispatcher service is unavailable. - AWKCLI134E
The job ID "jobID" is incorrect. - AWKCLI135E
The specified job state "state" is not correct. - AWKCLI150E
The job definition "JOB_NAME" cannot be updated. It is not present in the Job Repository. - AWKCLI151E
The "all_option" option cannot be used with other query filter options. - AWKCLI154E
The specified quantity "RESOURCE_QUANTITY" is not an integer. You can specify an integer within the 0 and 99999999 range. - AWKCLI155E
The specified quantity "RESOURCE_QUANTITY_RANGE" is outside the valid range. You can specify an integer within the 0 and 99999999 range. - AWKCLI156E
The specified resource name "RESOURCE_NAME" is not supported. - AWKCLI157E
The specified resource type "RESOURCE_TYPE" is not supported. - AWKCLI170E
Rollback failed with database error: "error". - AWKCLI176E
The specified value "port" for the connection port is not a number. Specify a valid number in the command line configuration file. - AWKCLI177E
The required server connection parameters are missing. Specify the hostname or the communication ports of the server in the command line configuration file. - AWKCLI179W
The broker server "server" is not responding. - AWKCLI183W
It is not possible to perform the requested operation. The connection failed with all the defined broker servers. - AWKCLI184W
Some required properties for the broker server "server" (backup server number "index") have not been correctly defined. The broker server "server" will be not added to the backup server list. - AWKCLI186E
An error occurred performing the requested operation. - AWKDBE - Database Job Executor messages
This section lists error and warning messages that might be generated by the routines that handle the Database Job Executor. - AWKDBE001E
The server address is missing. - AWKDBE002E
The server port is either missing or not valid. Specify a value in the 1..65535 interval. - AWKDBE003E
The database name is missing. - AWKDBE004E
The credentials are missing. - AWKDBE005E
The user name or the password is missing. - AWKDBE006E
Missing statements. - AWKDBE007E
Runtime Error "exception_message". - AWKDBE008E
Unable to create the output file "output_file". - AWKDBE009E
Unable to create the connection "exception_message". - AWKDBE010E
MSSQL Job Execution Error "error_message". - AWKDBE011E
SQL Job Execution Error "error_message". - AWKDBE012E
Rollback error "error_message". - AWKDBE013E
Connection close error "error_message". - AWKDBE014E
Output file close error "error_message". - AWKDBE015E
The DBMS value is either empty or not valid. - AWKDBE016E
Empty statement. - AWKDBE017E
The JDBC Driver jar classpath is missing. - AWKDBE018E
Cannot access required JDBC Driver folder - AWKDBE019E
The job type is not valid; it must be job or sql - AWKDBE020E
The driver class name is missing. - AWKDBE021E
The connection URL is missing. - AWKDBE023E
An error occurred while attempting to connect to the database. See the attached database message for more information: "exception_message". - AWKDBE025E
The job type is not valid; it must be sql. - AWKDBE026E
The number of arguments is invalid; they must be 4 (Procedure Variable Type, Variable Name, SQL Variable Type, Variable Position Index). - AWKDBE027E
IN or INOUT variable was not specified. - AWKDBE028E
The SQL type "sql_type" is not supported. - AWKDBE029E
The type "procedure_type" is not valid as stored procedure parameter type. - AWKDBE030E
The string "sql_string" doesn't match a supported SQL type. - AWKDBE031E
The string "procedure_string" doesn't match a valid stored procedure parameter. - AWKDBE032E
The stored procedure name provided doesn't match any stored procedure definition in the database. - AWKDBE033E
The stored procedure name provided matches more then one stored procedure definition in the database, to disambiguate specify also the schema. - AWKDBE035E
An error occured while impersonating the domain user. Return code "return_code". - AWKDBE036E
An error occured while acquiring credentials for the domain user. Return code "return_code". - AWKDBE037E
An error occured while freeing credentials for the domain user. Return code "return_code". - AWKDBE038E
An error occured while undoing impersonation for the domain user. Return code "return_code". - AWKDBE039E
Stored procedures are not supported for Big SQL. - AWKDBE040E
Stored procedures are not supported for Hive. - AWKDBE041E
You did not specify the directory name for the output file. The output file must contain the fully qualified path. - AWKDBE042E
You did not specify the file name for the output file. The output file must contain the fully qualified path. - AWKDBE043E
The directory "file_path" you specified to save the output file does not exist. - AWKDSE - Job plug-in for IBM InfoSphere DataStage messages
This section lists error and warning messages that might be issued by the job plug-in for IBM InfoSphere DataStage. - AWKDSE001E
You did not specify the project name. - AWKDSE002E
You did not specify the job name or job alias. The job name or the job alias is a mandatory parameter. - AWKDSE003E
You did not specify the user name or the password. The user name and the password are required parameters. - AWKDSE004E
You did not specify the remote file path. The remote file path is a mandatory parameter. - AWKDSE005E
An error occurred while attempting to retrieve the list of jobs. - AWKDSE006E
An error occurred while attempting to retrieve the list of parameters for the job. - AWKDSE007E
An error occurred while attempting to retrieve the list of projects. - AWKDSE009E
An error occurred while attempting to retrieve the list of projects. The return code is: "return_code". - AWKDSE010E
An error occurred while attempting to retrieve the list of jobs. The return code is: "return_code". - AWKDSE011E
An error occurred while attempting to retrieve the list of parameters for the job. The return code is: "return_code". - AWKDSE012E
You did not specify the domain name. The domain name is a mandatory parameter. - AWKDSE013E
You did not specify the server name. The server name is a mandatory parameter. - AWKDSE014E
You did not specified the DataStage installation directory in the DataStageJobExecutor.properties configuration file. - AWKDSE015E
An error occurred while running the job. - AWKDSE016E
The file "fileName" was not found in the directory "dirName". Verify that you have correctly specified the path in the DataStageJobExecutor.properties file. - AWKDSE017E
The row limit value "value" you specified is not valid for the DataStage job "job" in the project "project". - AWKDSE018E
The warning limit value "value" is not valid for the DataStage job "job" in the project "project". - AWKDSE019E
The command "fileName" cannot be run. Verify that you have the correct permissions to run the command. - AWKDSE020E
No object found with the filter "filter" you specified. - AWKDSE021E
The HCL Workload Automation agent cannot monitor the DataStage job. - AWKDSE022E
No parameter was found for the selected job. - AWKDSJ - Distributed shadow job validation messages
This section lists error and warning messages that could be generated by the distributed shadow job validation. - AWKDSJ001E
The value assigned to the application name is not coherent with the XML definition. - AWKDSJ002E
The XML namespace definition is unknown. - AWKDSJ003E
The range assigned to the matching criteria is not valid. - AWKDSJ004E
The value assigned to JobStream is not valid. - AWKDSJ005E
The value assigned to Workstation is not valid. - AWKDSJ006E
The value assigned to Job is not valid. - AWKDSJ007E
The value assigned to From or To attributes is not valid. - AWKDSJ008E
The value assigned to From or To attributes is not valid. - AWKEWL - Enterprise workload manager messages
This section lists error and warning enterprise workload manager messages that might be issued. - AWKEWL002E
The Enterprise Workload Manager plug-in configuration failed because of a problem accessing the configuration file. - AWKEWL004E
The Enterprise Workload Manager plug-in failed to start. - AWKEWL005W
The Enterprise Workload Manager plug-in is not configured and cannot be started. - AWKEWL007E
An internal error occurred while stopping the Enterprise Workload Manager plug-in - AWKEWL008W
No Enterprise Workload Manager Server configuration has been defined. - AWKEWL010E
The Enterprise Workload Manager plug-in failed to connect to the Enterprise Workload Manager Domain Manager "domain_manager_name". - AWKEWL012E
The Enterprise Workload Manager plug-in failed to initialize the internal cache for the Enterprise Workload Manager Domain Manager "domain_manager_name". - AWKEWL014E
The Enterprise Workload Manager plug-in failed to update the internal cache for the Enterprise Workload Manager Domain Manager "domain_manager_name". - AWKEWL017W
An error occurred while creating the new resource "resource_name" belonging to the group "resource_group_name". - AWKEWL020E
Unable to set the Load Balancer state for the Enterprise Workload Manager Domain Manager "domain_manager_name" . The following error was returned: "error". - AWKEWL022E
The Enterprise Workload Manager plug-in failed to register the following members "members" belonging to the group "resource_group_name"to the Enterprise Workload Manager Domain Manager "domain_manager_name" . The following error was returned:"error". - AWKEWL024E
The Enterprise Workload Manager plug-in failed to deregister from the Enterprise Workload Manager Domain Manager "domain_manager_name" the following members "members" belonging to the group "resource_group_name" . The following error was returned:"error". - AWKEWL028W
The connection with the EWLM Domain Manager "domain_manager_name" has been lost. The weights of all members will be reset until the connection is reestablished. - AWKEXE - Executable Job Executor messages
This section lists error and warning messages that might be generated by the routines that handle the Executable Job Executor. - AWKEXE001E
The script parameter is empty. - AWKEXE002E
The path parameter is empty. - AWKEXE003E
The error parameter is empty. - AWKEXE004E
The input parameter is empty. - AWKEXE005E
The output parameter is empty. - AWKEXE006E
The workingDirectory parameter is empty. - AWKEXE007E
The groupName parameter is empty. - AWKEXE008E
The password parameter is empty. - AWKEXE009E
The path or the script parameters is empty. - AWKEXE010E
You cannot specify both path and script parameters. - AWKEXE011E
The password parameter is empty. - AWKEXE012E
The user name parameter is empty. - AWKEXE013E
The arguments parameter is empty. - AWKEXE014E
The environment parameter is empty. - AWKEXE015E
There are one or more empty names in the environment parameter. - AWKEXE016E
The jsdle:executable element is missing in the job definition. - AWKEXE017E
Spaces are not allowed in the script extention - AWKFLX - License monitoring messages
This section lists error and warning messages that might be generated when using license monitoring. - AWKFLX001E
License information is corrupt. Contact support to correct the error. - AWKFLX002E
One or more job run numbers are missing in the job count. The last processed run number is "". - AWKFLX003E
License usage information was not sent to the license server for 14 days. Object creation is now blocked. - AWKFLX004E
No valid license was found for the product, or the trial license has expired. Contact product support at products-info@hcl.com to obtain a license. - AWKFLX005W
License usage information was not sent to the license server. If the communication problem is not solved, object creation will be blocked in two weeks' time. - AWKFLX006W
Your license is due to expire in two weeks from today. Contact products-info@hcl.com to purchase a full license. - AWKFLX007E
The license server url is: "" - AWKFTE - File transfer Job Executor messages
This section lists error and warning messages that might be generated by the routines that handle the file transfer job executor. - AWKFTE001E
The server address is missing. - AWKFTE002E
The path to the local file is missing. - AWKFTE003E
The path to the remote file is missing. - AWKFTE004E
The credentials are missing. - AWKFTE005E
The user name or the password is missing. - AWKFTE006E
The specified protocol is incorrect. - AWKFTE007E
An unexpected error has occurred. The following error message was returned:"exception_message" - AWKFTE008E
The specified transfer mode is incorrect. - AWKFTE009E
One or more mandatory parameters are missing. - AWKFTE010E
The user name or the password is incorrect. - AWKFTE011E
Cannot reach the specified server. - AWKFTE012E
Cannot find the specified protocol. - AWKFTE015E
Remote file not found or permission denied - AWKFTE016E
One or more codepages are empty. - AWKFTE017E
The port number specified in the server address is incorrect. - AWKFTE018E
The specified codepage "codepage" is not correct or is not supported. - AWKFTE019E
The operation is missing. - AWKFTE020E
Unable to perform the codepage conversion. - AWKFTE022E
An error occurred while transferring a file to or from the remote workstation. - AWKFTE023E
Connection refused. - AWKFTE024E
No conversion available between specified codepages. - AWKFTE025E
One or more port numbers of the ports range are empty or invalid. - AWKFTE026E
The specified value for the timeout is invalid. - AWKFTE027E
The specified value for the passive option is invalid. Only the values yes and no can be used. - AWKFTE028E
Connection not established due a timeout problem. - AWKFTE029E
The specified value for the certificates validity check option is invalid. Only the values yes and no can be used. - AWKFTE030E
The specified value for the cacerts certificates key store authentication option is invalid. Only the values yes and no can be used. - AWKFTE031E
The specified user and password are invalid. - AWKFTE032E
An error occurred submitting the job. - AWKFTE033E
The upload of the file "filename" failed. The following error message was returned:"exception_message" - AWKFTE034E
The upload of the file "filename" failed. The following error message was returned:"exception_message" - AWKFTE035E
An error occurred getting the list of the files in the "directory" directory. The following error message was returned:"exception_message" - AWKFTE036E
The directory "directory" is empty. - AWKFTE037E
The directory "directory" contains files that does not match the expression "expression". - AWKFTE038E
An error occurred contacting the remote file server "server". The following error message was returned:"exception_message" - AWKFTE039E
An error occurred getting the list of files in the "directory" directory on the remote server. The following error message was returned:"exception_message" - AWKFTE040E
The directory "directory" is empty. - AWKFTE041E
The directory "directory" contains files that does not match the expression "expression". - AWKFTE042E
An error occurred opening the file "file" directory on the remote server. The following error message was returned:"exception_message" - AWKFTE043E
An error occurred downloading the file "file". The following error message was returned:"exception_message" - AWKFTE044E
The specified permissions are incorrect. - AWKFTE045E
The specified delete on completion option is incorrect. - AWKFTE046E
The specified operation is incorrect. - AWKFTE047E
An error occurred deleting the file "file". The following error message was returned:"exception_message" - AWKFTE048E
Both keystore password and remote password can not be empty. - AWKHFS - Job plug-in for Hadoop Distributed File System messages
This section lists error and warning messages that might be issued by the job plug-in for Hadoop Distributed File System. - AWKHFS002E
Test connection failed. The error was "error" - AWKHFS004E
Update operation failed. The error was "error" - AWKHFS009E
The File on Hadoop FS parameter is missing. - AWKHFS010E
The file to be uploaded parameter is missing. - AWKHFS011E
The Save file as parameter is missing. - AWKHFS012E
An error occurred submitting the RESTFul Web Services job. The error message is "error" - AWKHFS013E
Keystore authentication failed. The error message is "error" - AWKHFS014E
The job cannot be saved because no input file has been specified. - AWKHFS016E
Error opening file "filename". The error message is "error" - AWKHFS017E
Error writing to file "filename". The error message is "error" - AWKHFS018E
Error opening file "filename". The error message is "error" - AWKHFS019E
Error reading file "filename". The error message is "error" - AWKHFS020E
An error occurred retrieving JSON result from response. The error message is "error" - AWKHFS021E
Unable to get valid response for server. The error message is "error" : "error" - AWKHFS022E
Cannot add parameters to a query string already defined in the URL. - AWKHFS023E
One of the header keys is empty. - AWKHFS024E
One of the query parameter keys is empty. - AWKHFS025E
The agent cannot monitor the RESTFul Web Services job. - AWKHFS026E
The file to be appended parameter is missing. - AWKHFS027E
The new file name parameter is missing. - AWKHFS028E
The permissions parameter must be a number. - AWKHFS029E
The UTF-8 encoding is not supported. The error message is "error" - AWKHFS030E
An error occurred establishing a connection to the remote service. The error message is "error". - AWKHFS031E
Error reading file "filename". The error message is access denied. - AWKHFS032E
Error writing file "filename". The error message is access denied. - AWKHFS033E
An empty string was specified as the content of the file. - AWKHFS034E
The name of the file to be uploaded is missing and an empty string was specified as the content of the file. - AWKHFS035E
An empty string was specified as the content of the file. - AWKHFS036E
The name of the file to be appended is missing and an empty string was specified as the content of the file. - AWKHFS037E
The input file was not found. The error message is "error". - AWKHFS038E
The output file was not found. The error message is "error". - AWKHFS039E
An error occurred creating the directory "error". The error message is "error". - AWKHFS040E
An error occurred deleting the file or directory "file". The error message is "error". - AWKHFS041E
An error occurred creating a file on "file". The error message is "error". - AWKHFS042E
An error occurred during the download of "file". The error message is "error". - AWKHFS043E
An error occurred updating the "file" file. The error message is "error". - AWKHFS044E
An error occurred renaming the file "file" to "new file name". The error message is "error". - AWKHFS045E
The file "file" was not renamed to "new file name". Check that the source file is present and that the destination file does not exist. - AWKHFS046E
An error occurred deleting the file or directory "file". - AWKHFS047E
An error occurred while monitoring the job. The error message is "error" - AWKHMR - Job plug-in for Hadoop Map Reduce messages
This section lists error and warning messages that might be issued by the job plug-in for Hadoop Map Reduce. - AWKHMR001E
The required Hadoop installation directory parameter is missing. Provide the required information in the Hadoop Map Reduce job definition or in the HadoopMapReduceJobExecutor.properties file. - AWKHMR002E
The required jar file parameter is missing. - AWKHMR003E
The Hadoop installation directory "installdir" you specified is not valid. - AWKHMR004E
The jar file "jarfile" you specified does not exist. - AWKHMR005E
The jar file "jarfile" you specified is not valid. - AWKHMR006E
An unexpected error has occurred. The following error message was returned: "error". - AWKHMR007E
Permission denied to execute the Hadoop command "command". - AWKHMR009E
The test of the Hadoop installation directory failed. The error message is "error" - AWKHMR010E
An unexpected error has occurred. Check the job log for futher details. - AWKHMR011E
No element is available for the specified "filter" filter. - AWKICA - Calendar messages
This section lists error and warning messages that might be issued by the Calendar. - AWKICA001E
Only one of the following values"var0" and "var1" is allowed for frequency "var2". - AWKICA002E
Rule "var0" is incompatible with frequency "var1". - AWKICA003E
Cannot add the day of week to the recurrence rule. The name for the day of week ("var0") is incorrect. - AWKICA004E
Cannot add the element to the recurrence list. The element cannot be less than the minimal value for the list ("var0"). The element value is "var1". - AWKICA005E
Cannot add element to the recurrence list. The element cannot be greater than the maximum value for the list ("var0"). The element value is "var1". - AWKICA006E
Cannot add element to the recurrence list because the element value is zero. - AWKICA007E
Cannot set the interval because the value "var0" is less than 0. - AWKIIE - IBM iconic Job Executor messages
This section lists error and warning messages that might be generated by the routines that handle the IBM iconic job executor. - AWKIIE001E
The command parameter is either missing or empty. - AWKIIE002E
The length of the command exceeds the maximum size of "max_size" characters. - AWKIIE003E
The message id field is either missing or empty. - AWKIIE004E
The message text field is either missing or empty. - AWKIIE005E
The length of the "field_name" field exceeds the maximum size of "max_size" characters. - AWKIIE006E
The value specified for the "field_name" field must be a valid non-negative integer. - AWKIIE007E
The value specified for the "field_name" field is out of range. The valid range is from "min_value" to "max_value". - AWKIPC - Job plug-in for Informatica PowerCenter messages
This section lists error and warning messages that might be issued by the job plug-in for Informatica PowerCenter. - AWKIPC001E
Missing required value for Repository Name. - AWKIPC002E
Missing required value for Service Name. - AWKIPC003E
Missing required value for Folder Name. - AWKIPC004E
Missing required value for Workflow Name. - AWKIPC005E
Failed to run workflow. - AWKIPC006E
Failed to cancel workflow. - AWKIPC007E
Failed to retrieve logon parameters. - AWKIPC008E
Missing configuration information related to the PowerCenter: "property". - AWKIPC009E
Missing both input and configuration information related to the PowerCenter: "property". - AWKIPC010E
Required parameter not provided. - AWKIPC011E
An error occurred retrieving repository list - AWKIPC012E
An error occurred retrieving service list - AWKIPC013E
An error occurred retrieving folder list - AWKIPC014E
An error occurred retrieving workflow list - AWKIPC015E
You do not specify the Repository Name. It is required to retrieve the Folder list. - AWKIPC016E
You do not specify the Folder Name. It is required to retrieve the Workflow list. - AWKIPC017E
The HCL Workload Automation agent cannot monitor the PowerCenter job. - AWKIPC018E
An error occurred retrieving the workflow parameter file list. - AWKIPC019E
The repository list is empty. - AWKIPC020E
The service list is empty. - AWKIPC021E
The folder list is empty. - AWKIPC022E
The workflow list is empty. - AWKIPC023E
The directory "dir", that should contain files with workflow parameter, appears to be empty. - AWKIPC024E
No files with the proposed filter in the directory "dir". - AWKIPC025E
The directory that should contain files with workflow parameter was not indicated in the configuration file or is not a valid directory. - AWKIPC026E
An error occurred during reconnect. - AWKIPC027E
Cannot indicate both a workflow parameter file and in-line parameters. - AWKIPC028E
Unable to contact the PowerCenter server. - AWKIPC029E
Failed to run workflow. The internal error is: "internal_error". - AWKIPC030E
Failed to submit the operation. The internal error is: "internal_error". - AWKIPC032W
The workflow content is empty due to one or more of the following conditions: no worklets or session tasks are running, worklets or session tasks are running but not with their original name, the workflow instance is related to a previous run. - AWKIPC033E
The job was stopped by the user. - AWKITM - ITM scanner messages
This section lists error and warning messages that might be generated by the routines that handle the ITM scanner. - AWKITM001W
An error occurred while loading the user configuration file "config_file". The following error was returned: "error". The default values will be used. - AWKITM002E
An error occurred while getting the configuration file "config_file". The following error was returned: "error". - AWKITM003E
Unable to find the configuration file "config_file" . - AWKITM004I
Usage:itmdataimport [? | [-usr <username> -pwd <password>] -v ] v - verbose - AWKITM005E
An exception occurred on the ITM server. The following error was returned: "error". - AWKITM006E
The operation failed because the required parameter "parameter" is missing. Include it in the command or in the configuration file. - AWKITM007E
The command failed because it included an unsupported parameter "parameter". - AWKITM008E
The operation failed because the URL specified for the Dynamic Workload Broker server "URL"is not correct. - AWKITM009E
A problem occurred while contacting the Dynamic Workload Broker server. The Dynamic Workload Broker service is not available. - AWKITM010E
Unable to invoke Dynamic Workload Broker Web Services because an incorrect parameter was specified. - AWKITM011E
Unable to invoke Dynamic Workload Broker Web Services. - AWKITM012E
Unable to connect to the Dynamic Workload Broker server. The user credentials might be incorrect. - AWKITM013E
The operation failed because the user is not authorized to perform it. - AWKITM014E
An unexpected error occurred. - AWKJBJ - JBJ JSR 352 Java Batch plug-in
This section lists error and warning messages that might be generated by JSR 352 Java Batch plug-in. - AWKJBJ002E
Test connection failed. The error was "error" - AWKJBJ004E
JSR 352 Java Batch job submit operation failed. The error was "error" - AWKJBJ005E
JSR 352 Java Batch job execution failed - AWKJBJ006E
The UTF-8 encoding is not supported. The error message is "error" - AWKJBJ007E
An error occurred establishing a connection to the remote service. The error message is "error". - AWKJBJ008E
The job was cancelled by the user. - AWKJBJ009E
An error occurred retrieving JSON result from response. The error message is "error" - AWKJBJ010E
An error code was returned invoking a RESTful method. The error message is "error" - AWKJBJ011E
Missing Application Name. - AWKJBJ013E
Invalid authorization. Missing or wrong credentials. - AWKJBJ014E
The Job XML is malformed. The error message is "error" - AWKJBJ015E
Error loading the file containing the XML job. The error message is "error" - AWKJBJ017E
Error loading the file containing the XML job. File "file" not found. - AWKJBJ018E
The port parameter is invalid. - AWKJBJ019E
The protocol parameter is invalid. - AWKJBJ021E
The server switch mode parameter is invalid. Valid values are "switchModes". - AWKJBJ023E
Unable to open the Workflow Details Panel. Please wait the job to reach a final state and try again. - AWKJBJ024E
Unable to open the Workflow Details Panel. The selected job does not exist on the JSR server. - AWKJBN - Job definition base notify service messages
This section lists error and warning job definition base notify service messages that might be issued. - AWKJBN081E
A notification was received with incorrect Topic: "topic" or Message: "message". - AWKJCL - Command line messages
This section lists error and warning messages that might be generated when using the command line. - AWKJCL001E
The job stream name value "invalid_job_stream_name_value" specified as jsdljcl:jobStreamName in the jsdl job definition is incorrect. It must be "valid_job_stream_value" - AWKJCL002E
The input arrival time value "invalid_input_arrival_time_value" specified as jsdljcl:inputArrival in the jsdl job definition is incorrect. It must be "valid_input_arrival_time_value" - AWKJCL009E
The MEMBER value is empty or not valid. - AWKJCL010E
The DATASET value is not valid. - AWKJCL011E
The MEMBER value exceeds the length of 8 bytes. - AWKJCL012E
The DATASET value exceeds the length of 44 bytes. - AWKJDB - Common objects messages
This section lists error and warning messages that might be generated by the routines that handle common objects. - AWKJDB101E
The specified object was not found. - AWKJDB102E
The specified global option was not found. - AWKJDB201E
The specified object cannot be locked, updated, or deleted because it is locked by user "user_name". - AWKJDB202E
The object cannot be unlocked or updated because it is not locked. - AWKJDB203E
The object cannot be unlocked or updated because it was not locked by you. you are logged on as user "user1_name"). The object is locked by user "user2_name". - AWKJDB204E
The object cannot be unlocked or updated because it is locked by you, logged on as "user_name" in another session. - AWKJDB205E
An error occurred when trying to lock multiple objects because at least one of the selected objects is already locked. - AWKJDB206E
An error occurred when trying to unlock multiple objects because at least one of the selected objects was not locked by you ("user_name"). - AWKJDB207E
An error occurred when trying to unlock multiple objects because at least one of the selected objects was locked by you ("user_name"), in another session. - AWKJDB301E
Unused message. - AWKJDB401E
Unused message. - AWKJDB402E
An internal error occurred while reading or writing a UUID in the database, or while generating a UUID for a new object. - AWKJDB403E
An internal error occurred. The operation "operation_name" cannot be performed because the Data Access Object (DAO) context state "context_state" is not correct. - AWKJDB404E
An internal error has occurred while parsing the Identifier. The internal error message is: "error". - AWKJDB501E
Unused message. - AWKJDB601E
An internal error occurred. A database integrity constraint has been violated. The internal error message is: "error". - AWKJDB602E
An internal error occurred. A database not null constraint has been violated. The internal error message is: "error". - AWKJDB603E
An internal error occurred. A database check constraint has been violated. The internal error message is: "error". - AWKJDB604E
An internal error occurred. A database unique constraint has been violated, the object already exists. - AWKJDB605E
An internal error occurred. A database foreign key constraint has been violated. The internal error message is: "error". - AWKJDB606E
An internal error occurred. A foreign key constraint prevents the remove operation. The internal error message is: "error". - AWKJDB607E
An internal error occurred. The value defined for a database field exceeds its column bounds. The internal error message is: "error". - AWKJDB801E
An internal error has been found while accessing the database. The internal error message is: "error". - AWKJDB802E
An internal error has occurred in the database connection. The internal error message is: "error". - AWKJDB803E
An internal deadlock or timeout error has occurred while processing a database transaction. The internal error message is: "error". - AWKJDB804E
The operation cannot be completed because a concurrent update has been detected. Completing the operation would lead to a database inconsistency. - AWKJDB805E
The requested operation cannot be performed because the database is locked by the planner process. - AWKJDD - Job definition service messages
This section lists error and warning job definition service messages that might be issued. - AWKJDD101E
The submission of the job definition failed because the submit parameters are null. - AWKJDD102E
The submission of the job definition failed because the job definition document is null. - AWKJDD103E
The job definition creation has failed because of the database error: "error" - AWKJDD104E
The Job Definition update failed because of the database error: "error" - AWKJDD105E
An error occurred when parsing JSDL. - AWKJDD106E
The request to remove a job definition failed because the job definition document is null. - AWKJDD107E
The job definition deletion failed because of the database error: "error" - AWKJDD108E
The get of a job definition has failed because of the database error: "error" - AWKJDD109E
The job definitions query failed because of the database error: "error" - AWKJDD110E
The request for the job definition failed because the Qname is null. - AWKJDE - Job dispatcher messages
This section lists error and warning Job dispatcher messages that might be issued. - AWKJDE005E
An error occurred accessing the job repository database while performing the "operation" operation. The internal error is: "error". - AWKJDE007W
An error occurred sending a client notification. The URL might not be accepting connections. The internal error is: "error". - AWKJDE008E
An error occurred connecting to the job manager session bean. The internal error is: "error". - AWKJDE011E
An error occurred accessing the job repository database. See the exception log for details. - AWKJDE012W
A job repository operation failed. See the exception log for details. Restart the database and try again. - AWKJDE013W
An error occurred sending a Job Notification. See the exception log for details. - AWKJDE014E
An error occurred creating failure or move history data alarm service. The following error was received: : "error". The Job Dispatcher cannot be started. - AWKJDE017E
An error occurred creating web service proxy. The following error was received: : "error". The Job Dispatcher cannot be started. - AWKJDE018E
An error occurred starting Job Dispatcher Queue Manager thread. The following error was received: "error". - AWKJDE019E
The Resource Advisor URL is not configured. The Job Dispatcher cannot be started. - AWKJDE020W
An error occurred sending a client notification. The URL might not be accepting connections. See the exception log for details. - AWKJDE021E
Incorrect input argument. Verify the input parameters JSDL and clientNotifyEPR. - AWKJDE022E
The input message header contains an inexistent job endpoint reference. - AWKJDE023W
A resource allocation request failed. Resource Advisor URL might be down or could not accept connections. See exception log for details. - AWKJDE024E
An error occurred submitting job ID "jobID" with name "name" to the endpoint URL "URL". The error message is: "error". - AWKJDE025E
An error occurred sending a cancel resource allocation for job ID "jobID". The error message is: "error". - AWKJDE027W
A job is in the wrong state for the specified operation. See exception description for job ID and incorrect state descriptor. - AWKJDE028E
A job interface is called with security authentication enabled but the job instance was created unauthenticated. - AWKJDE029E
A job interface is called with security authentication enabled but the calling user is not the job instance submitter or a member of the Job Administrator group. - AWKJDE030E
An error occurred while retrieving target job End Point Reference (EPR) after submitting job "jobID" with name "name" to the agent with URL "URL". The error message is: "error". - AWKJDE031E
The Job Dispatcher cannot be registered to the Agent Manager. The jobs cannot be submitted to agents. The following error occurred: "error". - AWKJDE032W
A job repository operation failed with an unexpected exception. - AWKJDE034E
An error occurred during job recovery. The following error was received: "error". - AWKJDE035E
An unknown job state was found: "state". - AWKJDE036E
An error occurred while processing the job actions queue for event "eventName" on . "eventScope". The error message is: "error". - AWKJDE038E
The Job Dispatcher could not save the last notified job state for the job "jobID" because of problems with the Job Repository. The following error was received: "error". - AWKJDE039E
An error occurred during job status notification recovery. The following error was received: "error". - AWKJDE042E
The resource allocation request for job "jobID" cannot be processed because of the following internal error: the Notify Service End Point Reference (EPR) cannot be found. - AWKJDE043E
Unable to retry the allocation request for job "jobID". Internal Error: Unsupported operation - AWKJDE044E
The Job Dispatcher failed the check on job status for job "jobID" because of the following internal error: "error". - AWKJDE045E
Error requesting resource allocation for job "jobID". The following error was received: "error". - AWKJDE048E
An error occurred canceling job ID "jobID" to the endpoint URL "URL" The error message is: "error". - AWKJDE055E
The Work Manager needed to schedule jobs is not configured. The Job Dispatcher cannot be started. - AWKJDE056E
An error occurred accessing the job repository database. The following error was received: : "error". The Job Dispatcher cannot be started. - AWKJDE057E
An error occurred during Job Dispatcher initialization. The following error was received: "error". The Job Dispatcher cannot be started. - AWKJDE058E
The affine job is in the wrong state for the specified operation. See the exception description for job ID and incorrect state descriptor. - AWKJDE059E
The affine job for job ID "jobID" is incorrect or cannot be found in the Job Repository. - AWKJDE060E
The affine job with alias "alias" is incorrect or cannot be found in the Job Repository. - AWKJDE061W
Error connecting to Resource Advisor. The cancel allocation for job "jobID" cannot be processed. The Job Dispatcher will retry the connection after "retry_time" seconds. The following error was received: "error". - AWKJDE062W
The Resource Advisor is unavailable, therefore the cancel allocation for job "jobID" cannot be processed. The Job Dispatcher will retry the connection in "retry_time" seconds. The following error was received: "error". - AWKJDE063W
The cancel allocation request to the Resource Advisor for job "jobID" failed because the specified allocation was not found. The following error was received: "error". - AWKJDE064E
The cancel allocation request to the Resource Advisor for job "jobID" failed because incorrect parameters were specified. The following error was received: "error". - AWKJDE065E
The cancel allocation request to the Resource Advisor for job "jobID" failed because of the following Resource Advisor error: "error". Check the Resource Advisor errors for further details. - AWKJDE068E
Unable to retry the cancel allocation request for job "jobID". The following error was received: "error". - AWKJDE069E
The allocation request for job "jobID" cannot be processed because of an error connecting to Resource Advisor. The Job Dispatcher will retry the connection in "retry_time" seconds. The following error was received: "error". - AWKJDE070W
The allocation request for job "jobID" cannot be processed because the Resource Advisor is unavailable. The Job Dispatcher will retry the operation in "retry_time" seconds. The following error was received: "error". - AWKJDE071E
The allocation request for job "jobID" to the Resource Advisor failed because incorrect parameters have been specified. The following error was received: "error". - AWKJDE072E
The allocation request for job "jobID" failed because of the following Resource Advisor error: "error". - AWKJDE075W
The reallocation of an allocation for job"jobID" cannot be processed because of an error connecting to the Resource Advisor. The Job Dispatcher will retry the connection in "retry_time" seconds. The following error was received: "error". - AWKJDE076W
The reallocation of an allocation for job"jobID" cannot be processed because the Resource Advisor is unavailable. The Job Dispatcher will retry to contact Resource Advisor in "retry_time" seconds. The following error was received: "error". - AWKJDE077E
The request to Resource Advisor for the reallocation of an allocation for job"jobID" failed because an incorrect allocation was requested. The following error was received: "error". - AWKJDE078E
The request to Resource Advisor for the reallocation of an allocation for job"jobID" failed because incorrect parameters were specified. The following error was received: "error". - AWKJDE079E
The request to Resource Advisor for the reallocation of an allocation for job"jobID" failed because of the following Resource Advisor error: "error". Check the Resource Advisor error log for further details. - AWKJDE082E
Unable to retry the reallocate allocation request for job "jobID". The following error was received: "error". - AWKJDE083E
Unable to submit the job because the following variables have not been resolved: "variable_name". - AWKJDE084E
Unable to submit the job because the following numeric variable value has an incorrect format "variable_name" for the expected number type "number_type". Specify the correct variable value in the appropriate format. - AWKJDE085E
Unable to submit the job because the following variable has incorrect syntax: "variable_name". Specify the variable values or define their values in the Job Definition. - AWKJDE086E
The Job Dispatcher cannot instantiate the Job Status Change Listener plug-in "plug-in". The following internal error occurred when loading the implementation "error": "error". - AWKJDE087E
An error occurred. The Alarm Manager is null. - AWKJDE100E
Rollback failed with database error: "error". - AWKJDE101E
The notification address is not valid. - AWKJDE102E
The job submission from JSDL for job"jobID" failed because of the following error: "error". - AWKJDE103E
Unable to parse an XML file. Check the JSDL, endpoint reference address, and other details for the job "jobID". - AWKJDE104E
Incorrect input argument. Verify the input parameters JSDL and clientNotifyEPR. - AWKJDE105E
A database error occurred when notifying a status change for job "jobID"The following error was received: "error".. - AWKJDE107E
The job query failed because of the database error: "error". - AWKJDE108E
Job "jobID" was not found. - AWKJDE109E
A database error occurred when processing job "jobID"The following error was received: "error". - AWKJDE110E
A database error occurred when processing the notification states of job "jobID". The following error was received: "error". - AWKJDE111E
Cannot cancel job"jobID" because the cancel operation is not supported. - AWKJDE120E
An internal service error occurred submitting job "jobID" with End Point Reference (EPR)"EPR" . The following error was received: "error". - AWKJDE121E
An internal invocation error occurred submitting job "jobID" with End Point Reference (EPR)"EPR" . The following error was received: "error". - AWKJDE122E
An error occurred while updating the job state of job "jobID" . The following error was received: "error". - AWKJDE123E
The Job execution request for job "jobID" failed because a null value was returned for the task End Point Reference (EPR). - AWKJDE124E
Unsupported error while processing ExecuteJobWork action for JobID: "jobID". The following error was received: "error". - AWKJDE125E
Error submitting execution request for job "jobID". The following error was received: "error". - AWKJDE127E
The configuration parameter "parameter" has the following incorrect number format "wrong_parameter_value". The default value "parameter_value" will be used. - AWKJDE128E
An internal error occurred while creating job history data. The following error was received: "error" . - AWKJDE129E
Cancel request denied. It is not compatible with the current state of job "jobname". The job might have already completed or have been previously cancelled. - AWKJDE130E
The job identifier returned from the endpoint is incorrect. The job cannot be processed. - AWKJDE131E
The job cannot be run because it has at least one incorrect parameter in the application section.Check the logs on the endpoint for further details. - AWKJDE132E
The target resource at address "address_url" cannot be reached. The following error occurred: "error"The system will try to submit to another available endpoint. - AWKJDE133E
The job cannot be submitted to "address_url". The following error occurred: "error" - AWKJDE135E
The job cannot be canceled on the target resource at address "address_url". The following error occurred: "message" - AWKJDE138E
The cancel request could not be sent to the address "address_url". The following error occurred: "error". The system will try to cancel the job later. - AWKJDE139E
The job allocation could not be canceled at the moment. The system will try to cancel the job later. - AWKJDE140E
The job allocation could not be canceled.The following error occurred: "error" - AWKJDE141E
The get execution log could not be requested from the address "address_url". The following error occurred: "error". Try again later. - AWKJDE142E
The get execution log could not be requested from the address "address_url"The following error occurred: "message" - AWKJDE143E
The job submission with job definition failed because the submit parameters are null. - AWKJDE144E
The job submission with job definition failed because the job definition document is null. - AWKJDE145E
The job submission with job definition "job_def_name" failed because it has an incorrect notify End Point Reference (EPR). - AWKJDE146E
The job submission with name definition failed because the submit parameters are null. - AWKJDE147E
The job submission with name failed because the job definition name is null. - AWKJDE148E
The job submission with name "job_def_name" failed because it has an incorrect notify End Point Reference (EPR). - AWKJDE149E
The job query failed because the query parameters are null. - AWKJDE150E
Unable to cancel job "jobID". The following error was received: "error". - AWKJDE151E
The status notification for job "jobID" cannot be completed. The client URL "URL" is malformed. - AWKJDE152E
The status notification for job "jobID" cannot be completed. Unable to contact the notification service at URL "URL". The following error was received: "error". - AWKJDE153W
Unable to connect to client URL "URL". The status notification for job "jobID" cannot be completed. The Job Dispatcher will retry the connection in "retry_interval" seconds. The following error was received: "error". - AWKJDE154E
The status notification to the client URL "URL" for job "jobID" failed because of the following error: "error". - AWKJDE155E
The job submission contains an incorrect input argument. Verify the input parameters JSDL and clientNotifyEPR. - AWKJDE156W
Unable to process status notification to client. The Job Dispatcher will retry to process the notification in "retry_interval" seconds. The following error was received: "error". - AWKJDE157W
Unable to process status notification to client. The following error was received: "message". - AWKJDE162W
Maximum number of status notification retry "max_retry" reached for job "jobID". - AWKJDE163E
Unable to cancel allocation for job "jobID". The following error was received: "error". - AWKJDE164E
Unable to reallocate resources for job "jobID". The following error was received: "error". - AWKJDE165E
Unable to cancel allocation on recovery for job "jobID". The following error was received: "error". - AWKJDE166E
Unable to process a job because the job identifier is not correct. - AWKJDE167E
The job "jobID"cannot be updated with the new status"job_status"The following error occurred: "error" The Job Dispatcher will try to update the database with the new status later. - AWKJDE168E
The job "jobID"cannot be updated with the new status"job_status"The following error occurred: "error" A serious outage might have affected the data integrity. Check the server error log for details about the failure. - AWKJDE169E
Get execution log request denied. It is not compatible with the current state of the job "jobID". - AWKJDE170E
The system received a resource allocation for a job with ID "jobID" , but the job was not found. - AWKJDE171E
The affine job with ID "jobID" does not have a target resource. - AWKJDE172E
The queue number "queue_number" for property "property_name" if is not in the range "min_value" - "max_value". - AWKJDE173E
The queue number "queue_number" for property "property_name" has an invalid number format. - AWKJDE174E
The action "action" for property "property_name" in not valid. - AWKJDE175E
The submission of the job definition failed because the submit parameters are null. - AWKJDE176E
The submission of the job definition failed because the job definition document is null. - AWKJDE177E
The job definition creation failed because of the database error: "DB_ERROR_MSG" - AWKJDE178E
The Job Definition update failed because of the database error: "DB_ERROR_MSG" - AWKJDE179E
The job definition deletion failed because of the database error: "DB_ERROR_MSG" - AWKJDE180E
The get job definition operation failed because of the database error: "DB_ERROR_MSG" - AWKJDE181E
The job definition query failed because of the database error: "DB_ERROR_MSG" - AWKJDE182E
The affine jobs are in wrong state for the specified operation. - AWKJDE184E
A network error occurred while trying to contact the target resource at address "address_url".The system will try to submit to another available endpoint. - AWKJDE185E
An unexpected error occurred while trying to decode the fault returned by the target resource at address "address_url".The original error occurred: "error". The following error occurred while decoding: "error" The system will try to submit to another available endpoint. - AWKJDE186E
An error occurred while submitting the job to the target resource at address "address_url". The following error occurred while submitting the job: "error" The system will try to submit to another available endpoint. - AWKJDE187E
An error occurred while submitting the job to the target resource at address "address_url". The following error occurred while submitting the job: "error" The system will not try to submit to any other endpoint. - AWKJDE188E
An error occurred while submitting the job to the target resource at address "address_url". The system will try to submit to another available endpoint. - AWKJDE189E
An error occurred while submitting the job to the target resource at address "address_url". The system will not try to submit to any other endpoint. - AWKJDE190E
An unexpected error occurred while submitting the job to the target resource at address "address_url". The following error occurred while submitting the job: "error" The system will try to submit to another available endpoint. - AWKJDE191E
A recoverable error occurred submitting job ID "jobID" with name "name" to the endpoint URL "URL". - AWKJDE192E
An unrecoverable error occurred submitting job ID "jobID" with name "name" to the endpoint URL "URL". The error message is: "error". - AWKJDE193E
An unrecoverable error occurred submitting job ID "jobID" to the endpoint URL "URL". - AWKJDE194E
A recoverable unexpected error occurred submitting job ID "jobID" with name "name" to the endpoint URL "URL". - AWKJDE195E
The target resource could not be contacted while submitting job ID "jobID" with name "name" to the endpoint URL "URL". The error message is: "error". - AWKJDE196E
The target resource could not be contacted while submitting job ID "jobID" with name "name" to the endpoint URL "URL". - AWKJDE197E
An unrecoverable error occurred canceling job ID "jobID" to the endpoint URL "URL". The error message is: "error". - AWKJDE198E
An unrecoverable error occurred canceling job ID "jobID" to the endpoint URL "URL". - AWKJDE199E
A recoverable unexpected error occurred canceling job ID "jobID" to the endpoint URL "URL". - AWKJDE200E
The target resource could not be contacted while canceling job ID "jobID" to the endpoint URL "URL". The error message is: "error". - AWKJDE201E
A recoverable error occurred canceling job ID "jobID" to the endpoint URL "URL". - AWKJDE202E
The target resource could not be contacted while submitting job ID "jobID" to the endpoint URL "URL". - AWKJDE203E
A network error occurred while trying to contact the target resource at address "address_url".The system will retry to cancel the job later. - AWKJDE204E
An unexpected error occurred while trying to decode the fault returned by the target resource at address "address_url".The original error occurred: "error". The following error occurred while decoding: "error" The system will retry to cancel the job at a later time. - AWKJDE205E
An error occurred while canceling the job to the target resource at address "address_url". The following error occurred while canceling the job: "error" The system will retry to cancel the job at a later time. - AWKJDE206E
An error occurred while canceling the job to the target resource at address "address_url". The following error occurred while trying to cancel: "error" The system will not retry to cancel the job. - AWKJDE207E
An error occurred while canceling the job to the target resource at address "address_url". The system will retry to cancel the job at a later time. - AWKJDE208E
An error occurred while canceling the job to the target resource at address "address_url". The system will not retry to cancel the job. - AWKJDE209E
An unexpected error occurred while canceling the job on the target resource at address "address_url". The following error occurred while canceling the job: "error" The system will retry to cancel the job. - AWKJDE210E
An unrecoverable error occurred requesting a job execution log page for job ID "jobID" to the endpoint URL "URL". The error message is: "error". - AWKJDE211E
An unrecoverable error occurred requesting a job execution log page for job ID "jobID" to the endpoint URL "URL". - AWKJDE212E
A recoverable unexpected error occurred requestinf a job execution log page for job ID "jobID" to the endpoint URL "URL". - AWKJDE213E
The target resource could not be contacted while requesting a job execution log page for job ID "jobID" to the endpoint URL "URL". The error message is: "error". - AWKJDE214E
A recoverable error occurred requesting a job execution log page for job ID "jobID" to the endpoint URL "URL". - AWKJDE215E
The target resource could not be contacted while requesting a job execution log page for job ID "jobID" to the endpoint URL "URL". - AWKJDE216E
A network error occurred while trying to contact the target resource at address "address_url".Please try again later. - AWKJDE217E
An unexpected error occurred while trying to decode the fault returned by the target resource at address "address_url".The original error occurred: "error". The following error occurred while decoding: "error" Please try again later. - AWKJDE218E
An error occurred while requesting a job execution log page to the target resource at address "address_url". The following error occurred while requesting a job execution log page: "error" Please try again later. - AWKJDE219E
An error occurred while requesting a job execution log page to the target resource at address "address_url". The following error occurred while trying to request the execution log page: "error" You can try again later, but likely fail. - AWKJDE220E
An error occurred while requesting a job execution log page to the target resource at address "address_url". Please try again later. - AWKJDE221E
An error occurred while requesting a job execution log page to the target resource at address "address_url". You can try again later, but likely fail. - AWKJDE222E
An unexpected error occurred while requesting a job execution log page to the target resource at address "address_url". The following error occurred while requesting the job execution log page: "error" Try again later. - AWKJDE223E
The execution log page is not present for the job that has been canceled before it was executed. - AWKJDE224E
The submission of the resource requirement failed because the resource requirement document is null. - AWKJDE225E
The resource requirement creation failed because of the database error: "DB_ERROR_MSG" - AWKJDE226E
The resource requirement deletion failed because of the database error: "DB_ERROR_MSG" - AWKJDE227E
The get resource requirement operation failed because of the database error: "DB_ERROR_MSG" - AWKJDE228E
The resource requirement update failed because of the database error: "DB_ERROR_MSG" - AWKJDE229E
The quantity of the logical resource "logical_resource" is incorrect - AWKJDE230E
An error occurred notifying the status of the job id "job_id" to the address "address" - AWKJDE231E
An unexpected error occurred: "error" - AWKJDE232E
Cannot complete the required command for job type "jobtype". The specified workstation might be unavailable or not compatible. - AWKJDE233E
The handler for the event "eventName" and scope "scope" was not found. - AWKJDE234W
The allocation request for job "jobID" cannot be processed because the Resource Advisor is unavailable. The Job Dispatcher will retry the operation in "retry_time" seconds. The following error was received: "error". - AWKJDE235W
A connection problem occurred submitting job ID "jobID" with name "name" to the endpoint URL "URL". The error message is: "error". - AWKJDE236E
An internal error occurred retrieving a job with alias "alias". The following error message is returned: "error_message". - AWKJDE237E
You have reached the maximum number of attempts to cancel "jobID" job. - AWKJDE238E
Get log header request denied. It is not compatible with the current state of the job "jobID". - AWKJDE239E
The log header is not present for the job that has been canceled before it was executed. - AWKJDE240E
Cannot complete the required command. The workstation might be unavailable or not compatible. - AWKJDE241E
A database error occurred when processing job "jobID"The following error was received: "error". - AWKJDE242E
The action cannot be performed because the job was not submitted to the agent. - AWKJDE243E
Cannot replace the variables in the job with alias "alias" because the syntax of a variable is not valid. The following error was received: "error". - AWKJDE244E
An unsupported value has been specified for one or more variables in the job with alias "alias". Expected value is numeric. The following error was received: "error". - AWKJDE245E
Cannot replace the variables in the job with alias "alias" because the syntax of a variable is not valid. The following error was received: "error". - AWKJDE246E
An unsupported value has been specified for one or more variables in the job with alias "alias". Expected value is numeric. The following error was received: "error". - AWKJDE247E
Cannot replace the variables in the job with alias "alias" because of a failure accessing the database. The following error was received: "error". - AWKJDE248E
The master at the address "address" cannot be contacted to get the variables for the job. The following error was received: "error". - AWKJDE249E
The master at the address cannot be contacted to get the variables for the job. The following error was received: "error". - AWKJDE250E
Unable to resolve the stduri variable "var_name". The following error was received: "error". - AWKJDE251E
Unable to resolve the stdlist variable "var_name". The following error was received: "error". - AWKJDE252E
Unable to resolve the property variable "var_name". The following error was received: "error". - AWKJDE253E
Unable to retrieve the job with alias "job_alias". The following error was received: "error". - AWKJDE254E
The job with alias "job_alias" used to resolve variables was not found. - AWKJDE255E
The database rollback failed. The following error was received: "error" - AWKJDE256E
Unable to retrieve the context of the job "job_id". The following error was received: "error". - AWKJDE500E
The job cannot be submitted to "address_url". The following error occurred: "error" - AWKJDE501E
The job cannot be submitted to "address_url". The following error occurred: "error" - AWKJDE502E
The job cannot be submitted to "address_url". The following error occurred: "error" - AWKJDE503E
The command cannot be executed by "address_url" - AWKJDE504E
The log header could not be requested from the address "address_url"The following error occurred: "message" - AWKJDE505E
The command cannot be executed on the agent at the address "address_url"The following error occurred: "message" - AWKJDE506E
The command cannot be executed on the agent at the address "address_url"The following error occurred: "message" - AWKJDE508E
An unexpected response was sent by the gateway on "gateway_address " while contacting the agent at the following address: "address_url"The following error occurred: "message" - AWKJDE509E
An invalid response was sent by the gateway on "gateway_address " while contacting the agent at the following address: "address_url"The following error occurred: "message" - AWKJDE518E
The action with id "action_id" on the gateway "gw_id" on "gateway_address " was not performed because the remote agent with this address "address_url" is down. The following error occurred: "message" - AWKJDE519E
The agent did not contact the server to manage this request. - AWKJDE520E
An unexpected response was sent by the gateway on "gateway_address " while contacting the agent at the following address: "address_url"The following error occurred: "message" - AWKJDE521E
An invalid response was sent by the gateway on "gateway_address " while contacting the agent at the following address: "address_url"The following error occurred: "message" - AWKJDE522W
There number of allowed gateways is reached. This gateway will attempt a new connection. - AWKJDE523E
The Job Dispatcher is not active. - AWKJEJ - WebSphere Java 2 Enterprise Edition job executor for CAS messages
This section lists error and warning messages that might be issued by the WebSphere Java 2 Enterprise Edition job executor for CAS. - AWKJEJ001E
The J2EEJobExecutorConfig.properties property file is missing. - AWKJEJ002E
The property file is incorrect. - AWKJEJ003E
The JMS action definition is either missing or empty - AWKJEJ004E
The JMS connection factory is either missing or empty. - AWKJEJ005E
The JMS destination queue is either missing or empty. - AWKJEJ006E
The JMS message is either missing or empty. - AWKJEJ007E
Cannot retrieve the following connection factory: "cf_name". - AWKJEJ008E
Cannot retrieve the following queue: "queue". - AWKJEJ009E
Cannot connect to WebSphere Application Server with address: "address". - AWKJEJ010E
Cannot send the message to "queue". - AWKJEJ012E
The user name or password is missing. - AWKJEJ013E
A generic error has occurred: "exception". - AWKJEJ014E
The operation is incorrect. - AWKJEJ015E
The connection URL value is empty. - AWKJEJ016E
The timeout is incorrect. - AWKJEJ017E
The job definition contains a double set of credentials. - AWKJEJ018W
The timeout has expired: no message was received from the specified queue. - AWKJEJ019E
One or more mandatory parameters are missing. - AWKJEJ020I
Test connection - AWKJEJ021I
The connection completed successfully. - AWKJEJ022E
The credentials are not valid. - AWKJEJ023I
The job was killed by the user. - AWKJEJ024E
The timeout is not supported for the SEND operation. - AWKJEJ025E
The message is not supported for the RECEIVE operation. - AWKJJE - Job plug-in for Java messages
This section lists error and warning messages that might be generated by the Job plug-in for Java. - AWKJJE001E
The jar path is not valid. - AWKJJE002E
The jar path is missing. - AWKJJE003E
The classname is missing. - AWKJJE004E
Runtime Error "exception_message". - AWKJJE005E
Cannot access required folders. - AWKJJE006E
The key attribute in the parameter tag is not valid. - AWKJJE007E
The jar path tag is empty - AWKJJE008E
The parameters tag is empty. - AWKJJE010E
No available information - AWKJJE011E
Unable to find class "exception_message". - AWKJMQ - Job plug-in for IBM WebSphere MQ messages
This section lists error and warning messages that might be generated when using the Job plug-in for IBM WebSphere MQ. - AWKJMQ001E
The target machine "server" is not reachable. The error message is "error" - AWKJMQ002E
The job execution failed. The error is "error" - AWKJMQ004E
The response was present in the queue. The error is "error" - AWKJMQ005E
The server address is missing. - AWKJMQ006E
The queue manager is missing. - AWKJMQ007E
The channel is missing. - AWKJMQ008E
The message is missing. - AWKJMQ009E
The request queue is missing. - AWKJMQ010E
The response queue is missing. - AWKJMQ011E
The publish topic is missing. - AWKJMQ012E
The publish queue is missing. - AWKJMQ013E
The server port is either missing or not valid. Specify a value in the 1 - 65535 interval. - AWKJMQ014E
The user name or the password is missing. - AWKJMQ015E
The specified value for the timeout is invalid. - AWKJMQ016E
The specified value for the QueueOrTopicCombo is either empty or not valid. - AWKJMQ018E
The topic "topic" was not found - AWKJMQ019E
An error occurred getting the list of the topics. The error message is "error". - AWKJMQ020E
An error occurred getting the list of the topics. The error message is "error". - AWKJMQ021E
An error occurred contacting the MQ manager. The error message is "error". - AWKJMQ022E
An error occurred contacting the request queue "requestQueue". The error message is "error". - AWKJMQ023E
An error occurred contacting the response queue "requestQueue". The error message is "error". - AWKJMQ024E
An error occurred getting the list of the topics. The error message is "error". - AWKJMQ025E
An error occurred contacting the queue "queue". The error message is "error". - AWKJMQ026E
An error occurred getting the list of the queues. The error message is "error". - AWKJMQ027E
An error occurred getting the list of the queues. The error message is "error". - AWKJMQ028W
There are no queue on this queue manager. - AWKJMQ029E
An error occurred getting the list of the queue managers. The error message is "error". - AWKJMQ030W
There are no queue managers. - AWKJMQ031E
An error occurred getting the list of the queue managers. The error message is "error". - AWKJMQ032E
An error occurred getting the list of the channels. The error message is "error". - AWKJMQ033E
An error occurred getting the list of the topics. The error message is "error". - AWKJMQ034W
There are no topics. - AWKJMQ035E
An error occurred contacting the MQ manager. The error message is "error". - AWKJMQ036E
An error occurred getting the list of the channels. The error message is "error". - AWKJMQ037W
There are no channels. - AWKJMQ038E
An unexpected error occurred. The error message is "error". - AWKJMQ039E
An error occurred contacting the MQ server. The error message is "error". - AWKJMQ040E
An error occurred contacting the MQ server. The error message is "error". - AWKJMQ041E
The subscribe topic is missing. - AWKJMQ042E
The subscribe queue is missing. - AWKJNT - Job definition notify service messages
This section lists error and warning job definition notify service messages that might be issued. - AWKJNT081E
A notification was received with an incorrect topic: "topic" or message: "message". - AWKJNT082E
A notification was received with an incorrect message type: "messageType". - AWKJMJ - Job plug-in for Job Management plug-in messages
This section lists error and warning messages that might be generated when using the Job Management plug-in. - AWKJMJ002E
Test connection failed. The error was "error". - AWKJMJ005E
The job execution failed. The error message is "error" - AWKJMJ006E
The UTF-8 encoding is not supported. The error message is "error" - AWKJMJ007E
An error occurred while establishing a connection to the remote service. The error message is "error". - AWKJMJ008W
The job was canceled by the user. - AWKJMJ010E
Invalid authorization. Missing or wrong credentials. - AWKJMJ011E
Parameter validation error. The error message is "error" - AWKJMJ012E
An error occurred while retrieving the JSON result from the response. The error message is "error" - AWKJMJ016E
The required variable table name parameter is missing. - AWKJMJ017E
The required variable list parameter is empty. - AWKJMJ030E
The Variable table job execution failed. Check the Engine logs. - AWKJMJ031E
The job cannot be saved because the number of retries is invalid. - AWKJMJ032E
The job cannot be saved because retry period is invalid. - AWKJMJ033E
Jobname is empty - AWKJMJ034E
Select a workstation - AWKJMJ035E
Jobstream ID is empty - AWKJMJ036E
Cannot find any workstations - AWKJMJ037E
Cannot retry the list of workstations. The HTTP response code is "code" - AWKJMJ038E
Job failed. The error is "error_message" - AWKJMJ039E
Job failed. The error is "error_message" - AWKJMJ041E
An error occurred during the Job submission. The error was "error". - AWKJMJ042E
Parameter validation error. Please enter a valid Method. - AWKJMJ043E
Unable to execute any kind of Rerun because it may lead to an inconsistent state. - AWKJSJ - Job Stream Submission plug-in messages
This section lists error and warning messages that might be issued by the Job Stream Submission plug-in. - AWKJSJ002E
Test connection failed. The error was "error". - AWKJSJ005E
The job execution failed. The error message is "error" - AWKJSJ006E
The UTF-8 encoding is not supported. The error message is "error" - AWKJSJ007E
An error occurred while establishing a connection to the remote service. The error message is "error". - AWKJSJ008W
The job was canceled by the user. - AWKJSJ010E
Invalid authorization. Missing or wrong credentials. - AWKJSJ011E
Parameter validation error. The error message is "error" - AWKJSJ012E
An error occurred while retrieving the JSON result from the response. The error message is "error" - AWKJSJ016E
The required variable table name parameter is missing. - AWKJSJ017E
The required variable list parameter is empty. - AWKJSJ027E
Url is empty - AWKJSJ028E
Password is empty - AWKJSJ029E
Username is empty - AWKJSJ030E
The job execution failed. Check the Engine logs. - AWKJSJ031E
The job cannot be saved because the number of retries is invalid. - AWKJSJ032E
The job cannot be saved because retry period is invalid. - AWKJSJ033E
Job Stream name is empty - AWKJSJ034E
Select a workstation - AWKJSJ035E
Job Stream ID is empty - AWKJSJ036E
Cannot find any Job Streams - AWKJSJ037E
Cannot retry the list of Job Streams. The response is "error" - AWKJSJ038E
Job failed. The error is "error_message" - AWKJSJ039E
Job failed. The error is "error_message" - AWKJSJ041E
An error occurred during the Job submission. The error was "error". - AWKJSJ042E
The field "error" must be between 00:00 and 23:59 - AWKJSJ043E
Cannot retry the list of workstations. The HTTP response code is "code" - AWKJSJ044E
Unable to get the Job Stream ID for the submission. "error" - AWKJSJ045E
Delay for days value must be between 0 and 99 - AWKJSJ046E
The field "error" must be between 00:00 and 99:59 - AWKJSJ047E
Cannot find any variable in the selected table - AWKJSJ048E
The specified job stream does not exist, or the search returned multiple matches, or you do not have the required permissions. - AWKJSJ049E
Alias cannot be longer than 16 characters. - AWKJSV - Job definition service messages
This section lists error and warning job definition service messages that might be issued. - AWKJSV081E
The job submission failed because the job definition is null. - AWKMSQ - MsSQL plug-in messages
This section lists error and warning messages that might be generated by the MsSQL plug-in. - AWKMSQ001E
The server address is missing. - AWKMSQ002E
The server port is either missing or not valid. Specify a value in the 1..65535 interval. - AWKMSQ003E
The database name is missing. - AWKMSQ004E
The credentials are missing. - AWKMSQ005E
The user name or the password is missing. - AWKMSQ006E
Missing statements - AWKMSQ007E
Runtime Error "exception_message" - AWKMSQ008E
Unable to create the output file - AWKMSQ009E
Unable to create the connection "exception_message" - AWKMSQ010E
MSSQL job run error "error_message" - AWKMSQ011E
SQL job run error "error_message". - AWKMSQ012E
Rollback error "error_message" - AWKMSQ013E
Connection close error "error_message" - AWKMSQ014E
Output file close error "error_message" - AWKMSQ015E
Empty DBMS - AWKMSQ016E
Empty statement - AWKMSQ017E
The JDBC Driver path is missing. - AWKMSQ018E
Cannot access required folders - AWKMSQ019E
The job type is not valid; it must be job - AWKMSQ020E
The driver class name is missing. - AWKMSQ021E
The connection URL value is missing. - AWKMSQ022E
The DBMS value is missing, only MSSQL is supported. - AWKMSQ023E
The polling interval format is not valid, the polling interval must be a positive integer. - AWKMSQ024E
The job type is not valid; it must be job - AWKMSQ025E
The type attribute for dbStatement element is missing. - AWKMSQ026E
More than one dbStatement element was specified. Only one dbStatement element of type job is allowed. - AWKNDE - Netezza plug-in messages
This section lists error and warning messages that might be generated by the Netezza plug-in. - AWKNDE001E
The hostame cannot be empty. - AWKNDE002E
The user cannot be empty. - AWKNDE003E
The password cannot be empty. - AWKNDE004E
The table cannot be empty. - AWKNDE005E
The database name cannot be empty. - AWKNDE006E
Null value should not exceed 4 characters. - AWKNDE007E
Decimal delimiter should not exceed 1 character - AWKNDE008E
Time delimiter should not exceed 1 character - AWKNDE009E
An error occurred loading the data. The error message is "error" - AWKNDE010E
The directory "directory" does not exist. - AWKNDE011E
An error occurred getting the list of files. The error message is "error" - AWKNDE012E
Test connection failed. The error message is "error" - AWKNDE013E
The directory "directory" is empty. - AWKOEB - Job plug-in for Oracle messages
This section lists error and warning messages that might be generated by the job plug-in for Oracle. - AWKOEB001E
The server address is missing. - AWKOEB002E
The server port is either missing or not valid. Specify a value in the 1..65535 interval. - AWKOEB003E
The database name is missing. - AWKOEB004E
The credentials are missing. - AWKOEB005E
The user name or the password is missing. - AWKOEB006E
Missing Application User. - AWKOEB007E
Runtime Error "exception_message". - AWKOEB008E
Unable to create the output file. - AWKOEB009E
Unable to create the connection "exception_message". - AWKOEB010E
Missing Application Identifier. - AWKOEB011E
Missing Responsibility Identifier. - AWKOEB012E
Job XML name, Job XML or Job XML file are missing. - AWKOEB013E
The JDBC Driver was not found. - AWKOEB014E
Output file close error "error_message". - AWKOEB015E
Missing Application Name. - AWKOEB016E
Empty statement. - AWKOEB017E
The JDBC Driver path is missing. - AWKOEB018E
Cannot access required JDBC Driver folder - AWKOEB019E
The job type is not valid; it must be job or sql - AWKOEB020E
The driver class name is missing. - AWKOEB021E
The connection URL is missing. - AWKOEB023E
An error occurred while attempting to connect to the database. See the attached database message for more information: "exception_message". - AWKOEB025E
The job type is not valid; it must be sql. - AWKOEB026E
The number of arguments is invalid; they must be 4 (Procedure Variable Type, Variable Name, SQL Variable Type, Variable Position Index). - AWKOEB027E
IN or INOUT variable was not specified. - AWKOEB028E
Error during the objects lookup: " " is not working. - AWKOEB029E
The type "procedure_type" is not valid as stored procedure parameter type. - AWKOEB030E
The string "sql_string" doesn't match a supported SQL type. - AWKOEB031E
The string "procedure_string" doesn't match a valid stored procedure parameter. - AWKOEB032E
The stored procedure name provided doesn't match any stored procedure definition in the database. - AWKOEB033E
The stored procedure name provided matches more then one stored procedure definition in the database, to disambiguate specify also the schema. - AWKOEB034E
All fields are mandatory. - AWKOEB035E
Validation failed. " " not found. - AWKOEB036E
An error occurred while monitoring the job. The error message is " " - AWKOEB037E
An error occurred while scheduling the OracleEBusiness resource " " - AWKOEB038E
Number of print copies is not valid - AWKOEB039W
Printer values have not been set. - AWKOEB040E
Missing number of print copies - AWKOEB041E
Number of parameters is not valid. - AWKOEB042W
Notification not set for the following users: " " - AWKOEB043W
Layout not set for the following template: " " - AWKOEB044E
The syntax for the layout " " is not valid. Valid syntax is Template application name, Template code, Language, Territory, Format. - AWKOEB045E
Missing Organization name. - AWKOOZ - Job plug-in for Apache Oozie messages
This section lists error and warning messages that might be generated by the job plug-in for Apache Oozie. - AWKOOZ002E
Test connection failed. The error was "error". - AWKOOZ004E
Oozie job submit operation failed. The error was "error" - AWKOOZ005E
The Oozie job execution failed. The error message is "error" - AWKOOZ006E
The UTF-8 encoding is not supported. The error message is "error" - AWKOOZ007E
An error occurred while establishing a connection to the remote service. The error message is "error". - AWKOOZ008W
The job was canceled by the user. - AWKOOZ010E
Invalid authorization. Missing or wrong credentials. - AWKOOZ011E
Parameter validation error. The error message is "error" - AWKOOZ012E
An error occurred while retrieving the JSON result from the response. The error message is "error" - AWKOOZ015E
An error occurred while monitoring the Oozie job or timeout reached. The Oozie job could be in suspended status. Check the Oozie job logs. - AWKOOZ016E
The required node name parameter is missing. - AWKOOZ017E
The required job tracker parameter is missing. - AWKOOZ018E
The required user name parameter is missing. - AWKOOZ019E
The required lib path parameter is missing. - AWKOOZ020E
The required job script or command parameter is missing. - AWKOOZ021E
The required job workflow path parameter is missing. - AWKOOZ022E
The required job mapper class parameter is missing. - AWKOOZ023E
The required job reducer class parameter is missing. - AWKOOZ024E
The required job mapper input directory parameter is missing. - AWKOOZ025E
The required job reducer output directory parameter is missing. - AWKOOZ026E
The required job type parameter is missing. - AWKOOZ027E
The Oozie job execution was killed. The error message is "error" - AWKOOZ028E
The Oozie job execution was killed. Check Oozie job logs. - AWKOOZ029E
Unable to reconnect to Oozie job. - AWKOOZ030E
The Oozie job execution failed. Check the Oozie job logs. - AWKOOZ031E
The job cannot be saved because the number of retries is invalid. - AWKOOZ032E
The job cannot be saved because retry period is invalid. - AWKPIC - SAP Process Integrator messages
This section lists error and warning messages that might be issued by the SAP Process Integrator component. - AWKPIC001E
You did not specify any value for the host name. This is required parameter. Specify a value. - AWKPIC002E
You did not specify any value for the port. This is required parameter. Specify a value. - AWKPIC003E
You specified a wrong value for the port. Specify a value in the 1..65535 interval. - AWKPIC004E
You did not specify any value for the service name. This is required parameter. Specify a value. - AWKPIC005E
You did not specify any value for the party. This is required parameter. Specify a value. - AWKPIC006E
You did not specify any value for the channel. This is required parameter. Specify a value. - AWKPIC007E
You did not specify any value for the user. This is required parameter. Specify a value. - AWKPIC008E
You did not specify any value for the password. This is required parameter. Specify a value. - AWKPIC009E
You did not specify any value for the protocol. This is required parameter. Specify a value. - AWKPIC010E
You specified a wrong value for the protocol. Specify http or https. - AWKPIC011E
An internal error occurred while writing to output file. The error message is: "error_message". - AWKPIC012E
An internal error occurred while parsing the response from the channel. The error message is: "error_message". - AWKPIC013E
An attempt to stop one or more channels has failed. - AWKPIC014E
An attempt to start one or more channels has failed. - AWKPIC015E
An error occurred while connecting to {0} . HTTP error code {1}. - AWKPIC016E
An error occurred while connecting to {0} on port {1}. - AWKPIC017E
An error occurred while connecting to {0} . User name or password incorrect. - AWKPIC018E
An error occurred while connecting to {0} . Is the ChannelAdmin servlet running?. - AWKPIC019E
An error occurred while connecting to {0} . Does channel {1} exist?. - AWKPRE - Provisioning plug-in messages
This section lists error and warning messages that might be generated by the Provisioning plug-in. - AWKPRE001E
The user name is a required parameter. - AWKPRE002E
The password is a required parameter. - AWKPRE003E
The host name is a required parameter. - AWKPRE004E
The port is a required parameter. - AWKPRE005E
The server port is not valid. Specify a value ranging from 1 - 65535. - AWKPRE006E
Managing an instance requires that you select an action to be performed on the instance. - AWKPRE007E
The action specified to be performed on the instance you want to manage is not a valid action. - AWKPRE008E
The instance ID is not valid. - AWKPRE009E
The cloud group ID is not valid. - AWKPRE010E
The virtual image ID is not valid. - AWKPRE011E
The instance name is a required parameter. - AWKPRE012E
The size specified is not valid. - AWKPRE013E
The size of the instance is required. - AWKPRE014E
One or more mandatory parameters are missing. - AWKPRE015E
There is no cloud group with the specified ID. - AWKPRE016E
There is no virtual image with the specified ID. - AWKPRE017E
There is no instance with the specified ID. - AWKPRE018E
The virtual machines number is not valid. Specify a number greater than zero. - AWKPRE019E
There was an error retrieving the data. - AWKPRE020E
There is no virtual machine with the specified ID. - AWKPRE021E
The virtual machine ID is not valid. - AWKPRE022E
The username or password is not valid. - AWKPRE023E
The server or port is not valid. - AWKPRE024E
There is no cloud group available. - AWKPRE025E
There is no cloud group with the specified ID. - AWKPRE026E
There is no virtual image available. - AWKPRE027E
There is no template with the specified ID. - AWKPRE028E
There is no instance available. - AWKPRE029E
There is no instance with the specified ID. - AWKPRE030E
There is no virtual machine available. - AWKPRE031E
There is no virtual machine with the specified ID. - AWKPRE032E
The HCL Workload Automation agent cannot monitor the Provisioning Job - AWKREA - Engine REST API messages
This section lists error and warning messages that might be issued by the Engine REST API messages. - AWKREA001E
Object of type "type" identified by "id" cannot be found. - AWKREA002E
Unknown action "action". - AWKSLY - Job plug-in for IBM SoftLayer messages
This section lists error and warning messages that might be issued by the job plug-in for IBM SoftLayer. - AWKSLY001E
Error during saving. Required field: - AWKSLY002E
Error during saving. Please complete all fields - AWKSLY003E
Test connection failed. Please check your credentials. - AWKSLY006E
Creation New Virtual Server failed. Please check your data. - AWKSLY008E
Change Power State failed. Please check your data. - AWKSLY010E
Error removing Virtual Server. - AWKSLY011E
Virtual Server : - AWKSLY012E
Data center : - AWKSLY013E
Operating system : - AWKSLY014E
No Virtual Server found. - AWKSLY015E
Get Virtual Server failed. - AWKSLY016E
Get Virtual Server Details failed. - AWKSLY017E
Error. Please select a Virtual Server. - AWKSLY018E
No Locations found. - AWKSLY019E
No Operating system found. - AWKSLY020E
Error. Please fill in at least one of these two sections: "Manage Existing Virtual Server" or "Create New Virtual Server". - AWKSLY021E
Error. Please fill in one of these two sections: \"Manage Existing Virtual Server\" or \"Create New Virtual Server\". - AWKSLY022E
Error. Virtual Server Hostname must contain only letters or numbers. - AWKQTE - Job plug-in for MQTT messages
This section lists error and warning messages that might be issued by the job plug-in for MQTT. - AWKQTE001E
An account name must be specified. Enter a valid account name. - AWKQTE002E
A password must be specified. Enter a valid password. - AWKQTE003E
A database name must be specified. Enter a valid database name. - AWKQTE004E
A user name must be specified. Enter a valid user name. - AWKQTE005E
Parameter validation error. The error message is "error" - AWKQTE006E
An action must be specified. Enter a valid action - AWKQTE007E
A document id must be specified. Enter a valid document id - AWKQTE008E
A document revision must be specified. Enter a valid revision - AWKQTE009E
A document must be specified. Enter a valid document file or content - AWKQTE010E
An error occurred updating the database "database". - AWKQTE011E
An error occurred updating the document "document". - AWKQTE012E
A document attachment revision must be specified. Enter a valid revision. - AWKQTE014E
An error occurred while attempting to connect to the Cloudant server. The error is: "exception_message". - AWKQTE015E
An attachment input file must be specified. Enter a valid input file. - AWKQTE016E
A content type must be specified. Enter a valid content type. - AWKQTE017E
An attach name must be specified. Enter a valid attach name. - AWKQTE018E
The user is not authorized to perform the action. Enter an authorized user. - AWKQTE019E
"document": document does not exist. - AWKQTE020E
Document "document" update conflict: wrong revision. - AWKQTE021E
Target database "database" does not exist. - AWKQTE044E
Error updating document "document". - AWKQTE046E
Error reading document "document". - AWKQTE048E
Error reading database "database". - AWKQTE050E
Error replicationg database "database". - AWKQTE051E
Error performing a GET database request. - AWKRAA - Resource advisor agent messages
This section lists error and warning messages that might be issued by the Resource advisor agent. - AWKRAA207E
The EMF framework is not initialized properly while starting Java Job. - AWKRAA208E
The application type "application_type" of job "jobId" is not valid. - AWKRAA209E
The job with advanced options with ID "application_type" was not found.The plug-in on the server is not compatible with the agent version. - AWKRAA210E
Incorrect user name or password - AWKRAE - Resource Advisor EJB messages
This section lists error and warning resource advisor EJB messages that might be issued. - AWKRAE009W
The optimization object is incorrect. Minimize and Maximize only apply to numeric property values. - AWKRAE010W
The priority value "priority_value" is not a valid value. - AWKRAE011E
A null value for argument "argument" was passed to method "method" . - AWKRAE012E
The argument "argument" passed to method "method" is not valid. - AWKRAE013E
Unable to perform operation "operation" . The following error was returned:"error_message". - AWKRAE014E
Unable to connect to resource management service. Internal exception message is "error_message". - AWKRAE015E
A requested resource is unknown. The following error was returned:"error_message". - AWKRAE016E
A resource repository exception has been returned. The following error was returned:"error_message". - AWKRAE017E
The requested operation failed. The following error was returned: "error_message". - AWKRAE018E
Unable to find a requested resource. The following error was returned: "error_message". - AWKRAE019E
A null parameter was passed to allocation resources. - AWKRAE020E
Unable to process a parameter passed to allocation resources. The following error was returned: "error_message". - AWKRAE021E
Unable to convert back to SDO. The following error was returned: "error_message". - AWKRAE022E
The resource allocation failed. The following resource repository error was received: "error_message". - AWKRAE023E
An allocation creation exception was caught. The following error was returned:"error_message". - AWKRAE024E
The resource allocation failed. The following error was returned:"error_message". - AWKRAE025E
The resource allocation failed. The following resource repository error was received: "error_message". - AWKRAE026E
Unable to allocate any resources. The following error was returned:"error_message". - AWKRAE027E
No resources matching the job requirements were found after waiting for "wait_time" seconds. - AWKRAE029W
Unable to find any resource matching the job requirements. The system will try to find appropriate resources for at least "wait_time" seconds. - AWKRAE030W
No currently available resources match the job requirements. The following resources that match the requirements cannot be contacted: "resource_list"The system will try to find appropriate resources for at least "wait_time" seconds. - AWKRAE031W
Waiting for currently allocated resource attributes. - AWKRAE032E
No currently available resources matching the job requirements have been found after waiting for"wait_time" seconds. The following resources matching the requirements cannot be contacted:"resource_list". - AWKRAE090E
Unable to cancel allocation"allocation_id" . The following error was returned:"error_message". - AWKRAE091E
Unable to process the reallocation of allocation"allocation_id" . The following error was returned:: "error_message". - AWKRAE092E
Unable to find allocation "allocation_id" . - AWKRAE093E
The query allocation failed. The following resource repository error has been received: "error_message". - AWKRAE094E
The resource allocation failed. The following error was returned: "error_message". - AWKRAE095E
The Resource Advisor cannot be started because an error occurred during Resource Advisor initialization. The following error was returned:"error_message". - AWKRAE099E
An error occurred during resources heartbeat check. The following error was returned: "error_message". - AWKRAE100E
The resource "resource_name" missed "missed_heartbeats" heartbeat counts. Setting the resource as inactive. - AWKRAE101E
An error occurred during allocation retry processing. The following error was returned:"error_message". - AWKRAE102E
An error occurred during notification processing. The following error was returned:"error_message". - AWKRAE103E
An error occurred during reallocation cancellation processing. The following error was returned:"error_message". - AWKRAE104E
An error occurred during allocation processing. The following error was returned:"error_message". - AWKRAE105W
The allocation request for job "job_name" cannot currently be satisfied because maximum number of allocations allowed: "max_allowed" has already been reached. - AWKRAE106E
An error occurred. Rollback failed with database error:"error_message". - AWKRAE107E
The database returned the following error: "error_message". - AWKRAE108E
An error occurred while the Dynamic Workload Broker was trying to restore the allocation for job "job_name".The following error was returned:"error_message". - AWKRAE109E
Cancel allocation was requested for allocation "allocation_id" during Resource Advisor start-up. The System will retry the operation later. - AWKRAE110E
The Resource Advisor failed to process the rebuilding of allocation "allocation_id" for job "job_name". The allocation will be canceled. - AWKRAE112E
An error occurred while connecting to the Job Dispatcher. The internal error is:"error". - AWKRAE113E
The Dynamic Workload Broker server cannot contact the Dynamic Workload Broker agent with url "url" while forcing the agent to send all the collected resources. - AWKRAE114E
The Dynamic Workload Broker server got an unexpected remote exception while contacting the Dynamic Workload Broker agent with url "url" to force a send of all the collected resources. The internal error is: "error". - AWKRAE115E
An unexpected error occurred while trying to decode the fault returned by the target resource at address "url". The original error is"error". The following error is returned while decoding "error". - AWKRAE116E
A recoverable error was returned by the agent with address "url" while forcing a send of all the collected resources. The internal error is:"error". - AWKRAE117E
A recoverable error was returned by the agent with address "url" while forcing a send of all the collected resources. No additional information is returned by the agent. - AWKRAE118E
An unrecoverable error was returned by the agent with address "url" while forcing a send of all the collected resources. The internal error is: "error". - AWKRAE119E
An unrecoverable error was returned by the agent with address "url" while forcing a send of all the collected resources. No additional information is returned by the agent. - AWKRAE120E
The Dynamic Workload Broker server could not contact the Dynamic Workload Broker agent with url "url" to force a send of all the collected resources. The internal error is: "error". - AWKRAE121E
An unexpected error occured while forcing the agent at address address "url" to send a all the collected resources. The internal error is"error". No additional information are sent to the server. - AWKRAE122E
The Dynamic Workload Broker server got an unexpected local exception while contacting the Dynamic Workload Broker agent with url "url" to force a send of all the collected resources. The internal error is: "error". - AWKRAE123E
Unexpected exception while forcing the send of all the collected resources. - AWKRAE124E
The Dynamic Workload Broker server cannot register to the Agent Manager. The error is: "error". - AWKRAE125W
A notification was received from the agent with URI "agent uri" and id "agent_id". This notification is for updating the agent properties but while the server was expecting a full notification. - AWKRAE126E
The Dynamic Workload Broker attempted to contact the agent at the URI "agent uri" and the following error occurred: "error_message". - AWKRAE127W
The Dynamic Workload Broker cannot submit a background process to manage the allocation request with allocation ID "allocation_id". The following error occurred: "error_message". - AWKRAE128W
The Dynamic Workload Broker cannot submit a background process to manage the allocation request with allocation ID "allocation_id". The following error occurred: "error_message". - AWKRCE - Remote command plug-in messages
This section lists error and warning messages that might be issued by the Remote command plug-in. - AWKRCE001E
The server name is a required parameter. - AWKRCE002E
The user name is a required parameter. - AWKRCE002I
An HCL Workload Automation kill action is performed on the job and an attempt is made to interrupt the command launched on the remote computer. - AWKRCE003E
A command must be specified. - AWKRCE004E
The password is a required parameter. - AWKRCE005E
One or more mandatory parameters are missing. - AWKRCE006E
Unable to contact the specified server. - AWKRCE0070E
Cannot find the specified protocol. The supported protocols are: rexec, windows, rsh, ssh, auto. - AWKRCE0080E
An error occurred while executing the command. - AWKRCE0090E
Cannot find the specified protocol or the server is unreachable. - AWKRCE0100E
The port range is invalid. Specify a value in the 1 - 65535 interval. - AWKRCE011E
The HCL Workload Automation agent cannot monitor the remote command job. - AWKRCE012E
Could not establish a connection to "server" target machine. - AWKRCE013E
Could not establish a connection to the target machine with the authorization credentials that were provided. - AWKRCE014E
Permissions denied to write the standard output or the standard error files. - AWKRRP - Resource repository messages
This section lists error and warning resource repository messages that might be issued. - AWKRRP001E
Unable to close the connection to the Resource Repository (RESREP) database. - AWKRRP002E
Unable to create connection to the Resource Repository (RESREP) database. - AWKRRP003E
Unable to perform query resources. - AWKRRP004E
The attribute name "attribute_name" for a computer system resource is incorrect. - AWKRRP005E
The attribute name "attribute_name" for an operating system resource is incorrect. - AWKRRP006E
The attribute name "attribute_name" for a file system resource is incorrect. - AWKRRP007E
The attribute name "attribute_name" for a network system resource is incorrect. - AWKRRP008E
The attribute name "attribute_name" for a software system resource is incorrect. - AWKRRP009E
The attribute value "attribute_value" for attribute name "attribute_name" for the"resource" resource is incorrect. - AWKRRP010E
A communication error occurred while connecting to the Resource Repository (RESREP) database table "table". The target database cannot be contacted. - AWKRRP011E
A communication error occurred while connecting to the Resource Repository (RESREP) database. The target database cannot be contacted. - AWKRRP012E
Unable to remove a record from table "table". - AWKRRP013E
Unable to initialize the Resource Repository. The following error was received: "error". - AWKRRP014E
Unable to initialize the JNDI context. The following error was received: "error". - AWKRRP015E
Unable to process an internal query for resources. The following error was received:"error". - AWKRRP016E
An unexpected null argument was found while deleting resources. - AWKRRP017E
An unexpected exception occurred while deleting resources. The following error was received:"error". - AWKRRP018E
Unable to find source or target resources for the creation or update of a relationship. - AWKRRP019E
Unable to create the relationship record. The following error was received: "error". - AWKRRP020E
A generic exception occurred while creating a relationship. The following error was received: "error". - AWKRRP021E
An unknown resource type "resource_type" was found while creating or updating a resource. - AWKRRP022E
A notification containing no data was received from the resource advisor agent "agentID". - AWKRRP023E
An error occurred during agent notification because the resource with name"resource_name"and resource type "resource_type" is incorrect. - AWKRRP024E
An error occurred during the processing of a relationship because the source with name "" or target with name "" does not exist. - AWKRRP025E
An error occurred during the processing of an agent notification. It was not possible to create a relationship. The following error was received:"error". - AWKRRP026E
An error occurred during the processing of an agent notification. The relationship specified for deletion does not exist. - AWKRRP027E
An error occurred during the processing of an agent notification. It was not possible to search for a source or target resource. The following error was received:"error". - AWKRRP028E
An error occurred during the processing of an agent notification. Unable to remove the relationship. The following internal error has been generated: "error_message". - AWKRRP029E
An error occurred during the processing of an agent notification. The resource with name"resource_name" and type "resource_type" could not be removed. - AWKRRP030E
An error occurred during the processing of an agent notification. The resource with name"resource_name" and type "resource_type"could not be found. - AWKRRP031E
Unable to create an resource advisor agent information record. The following error was received: "error". - AWKRRP032E
Unable to find the resource advisor agent with ID "agentID". The following internal error has been generated: "error_message". - AWKRRP033E
Unable to generate an internal identifier for the resource advisor agent with ID "agentID". The following error was received:"error". - AWKRRP034E
The JSDL mapper file "jsdlmapper"was not found. - AWKRRP035E
Unable to load the JSDL Mapper file"jsdlmapper". The following error was received:"error". - AWKRRP036E
Unable to create the resource advisor agent information entity with URI"URI". The following error was received:"error". - AWKRRP037E
The notification contains no data. - AWKRRP038E
Unable to create or remove a record for table "table_name". The following error was received:"error". - AWKRRP039E
Unable to query resources because the matching criteria set is empty. - AWKRRP040E
Unable to process SDO objects. - AWKRRP041E
Unable to find the resource with name"resource_name" and type"resource_type". - AWKRRP042E
A resource already exists with name "resource_name"and type"resource_type". - AWKRRP043E
Unable to find the target resource "resource_display_name" with ID "resource_id" and type "resource_type" for job "job_name". - AWKRRP045E
The job "job_name" cannot be processed because the resource table mapping file has not been loaded. - AWKRRP047E
No target resource has been specified for the job. - AWKRRP048E
The relationship for the resource ID: "resource_id" cannot be processed because no target or source is specified. - AWKRRP049E
The relationship for the resource ID: "resource_id" cannot be processed because the resource has not been defined in the JSDL. - AWKRRP051E
There must be at least one attribute defined in OperatingSystem element. - AWKRRP052E
The maximum CPU speed specified for the resource "target_type" is not a Double. Please check the value of maximum CPU speed and, if the value is a variable, check that values have been set for all variables. - AWKRRP053E
The exact CPU speed specified for the resource "target_type" is not a Double. Please check the value of exact CPU speed and, if the value is a variable, check that values have been set for all variables. - AWKRRP054E
The minimum CPU speed specified for the resource"target_type" is not a Double. Check the value for minimum CPU speed and, if the value is a variable, check that values have been set for all variables. - AWKRRP055E
The element CPURequirement cannot be null. - AWKRRP056E
At least one attribute must be defined for the cpu element. - AWKRRP057E
The exact physical memory specified for the resource "target_type" is not a Double. Check the value of exact Physical Memory and, if the value is a variable, check that values have been set for all variables. - AWKRRP058E
The maximum Physical Memory specified for the resource "target_type" is not a Double. Check the value of maximum Physical Memory and, if the value is a variable, check that values have been set for all variables. - AWKRRP059E
The minimum Physical Memory specified for the resource "target_type" is not a Double. Check the value of minimum Physical Memory and, if the value is a variable, check that values have been set for all variables. - AWKRRP060E
At least one attribute must be defined in PhysicalMemory element - AWKRRP061E
The exact Virtual Memory specified for the resource "target_type" is not a Double. Please check the value of exact Virtual Memory and, if the value is a variable, check that values have been set for all variables. - AWKRRP062E
The maximum Virtual Memory specified for the resource "target_type" is not a Double. Check the value of maximum Virtual Memory and if the value is a variable, check that values have been set for all variables. - AWKRRP063E
The minimum Virtual Memory specified for the resource "target_type" is not a Double. Check the value of minimum Virtual Memory and if the value is a variable, check that values have been set for all variables. - AWKRRP064E
At least one attribute must be defined in the VirtualMemory element - AWKRRP065E
The exact Disk Space specified for the resource "target_type" is not a Double. Check the value of exact Disk Space and if the value is a variable, check that values have been set for all variables. - AWKRRP066E
The maximum Disk Space specified for the resource "target_type" is not a Double. Check the value of maximum Disk Space and, if the value is a variable, check that values have been set for all variables. - AWKRRP067E
The minimum Disk Space specified for the resource "target_type" is not a Double. Check the value of minimum Disk Space and, if the value is a variable, check that values have been set for all variables. - AWKRRP068E
At least one attribute must be defined in the FileSystem element - AWKRRP069E
The quantity of the Logical Resource is not a Long. Check the value of the quantity of Logical Resources and, if the value is a variable, check that values have been set for all variables. - AWKRRP070E
At least one attribute must be defined in the LogicalResource element. - AWKRRP071E
The TDWB Server cannot find a table that is associated with the resource "resource_type". - AWKRRP072E
The Dynamic Workload Broker Server cannot find an attribute definition associated with the property "property_name" for the resource "resource_type". - AWKRRP073E
The specified unit "default_unit" is not valid. - AWKRRP074E
The HostName element cannot be null. - AWKRRP075E
At least one attribute must be defined in the Host element. - AWKRRP076E
The value assigned to the attribute "property_name"includes the characters "temp_value". Values for this attribute can include only integer values for the resource "target_type". - AWKRRP078E
The value assigned to the attribute "property_name"includes the characters "temp_value". Only Float values can be defined for attribute for the resource "target_type". - AWKRRP079E
The relationship for resource "resource_id" references source or target resources that do not exist or that are not defined in the JSDL. - AWKRRP081E
The property "property_name" specified for the resource "target_type" is not a Double. Check the value and, if it is a variable, check that values have been set for all variables. - AWKRRP082E
The resource type "resource_type" specified in the objective element has not been defined in the JSDL for the job "job_name". - AWKRRP083E
No database information have been provided for the resource type "resource_type". - AWKRRP084E
A resource already exists with display name "resource_name"and type"resource_type". - AWKRRP085E
The property "property_name" specified for resource "resource_type" in the Optimization element is not optimizable. - AWKRRP086E
The agent "agent_name" could not be created because the domain "domain_name" is not present. - AWKRRP087E
This resource group cannot be modified or deleted from the Dynamic Workload Broker web interface because it is linked to a workstation of type pool. - AWKRRP088E
The workstation name cannot be null. - AWKRSE - Resource advisor agent cache messages
This section lists error and warning resource advisor agent cache messages that might be issued. - AWKRSE081E
Unable to initialize the Resource Advisor allocation cache. The following error was returned: "error". - AWKRST - RESTful Web Services messages
This section lists error and warning messages that might be generated by the routines that handle the RESTful Web Services. - AWKRST001E
Send direct message failed. The error was "error" - AWKRST002E
The message was successfuly sent to the specified follower - AWKRST003E
The status was successfuly updated - AWKRST004E
Update message failed. The error was "error" - AWKRST005E
A message was received from "message". Message id: "message_id"; message text: "message_text". - AWKRST006E
An error occurred while getting a message from "sender". The error was "error" - AWKRST008E
An error occurred running the RESTFul Web Services job. - AWKRST009E
The required server address parameter is missing. - AWKRST010E
The specified method is incorrect. Supported values are: GET, POST, PUT, DELETE, HEAD - AWKRST011E
Invalid server URL syntax - AWKRST012E
An error occurred submitting the RESTFul Web Services job. The error message is "error" - AWKRST013E
Keystore authentication failed. The error message is "error" - AWKRST014E
The job cannot be saved because no input file for the post has been specified. - AWKRST016E
Error opening file "filename". The error message is "error" - AWKRST017E
Error writing to file "filename". The error message is "error" - AWKRST018E
Error opening file "filename". The error message is "error" - AWKRST019E
Error reading file "filename". The error message is "error" - AWKRST020E
An error occurred retrieving JSON result from response. The error message is "error" - AWKRST021E
Unable to get valid response for server. The error message is "error" : "error" - AWKRST022E
Cannot add parameters to query string already defined in the URL - AWKRST023E
One of the header keys is empty. - AWKRST024E
One of the query parameter keys is empty. - AWKRST025E
The HCL Workload Automation agent cannot monitor the RESTFul Web Services job. - AWKRST026E
The job cannot be saved because the number of retries is invalid. - AWKRST027E
The job cannot be saved because retry period is invalid. - AWKRST028E
The service URI is wrong. The error message is "error" - AWKRST029E
The UTF-8 encoding is not supported. The error message is "error" - AWKRST030E
An error occurred establishing a connection to the remote service. The error message is "error". - AWKRST031E
Error opening file "file_name". The error message is "error_message". - AWKRST032E
An error occurred while attempting to create the database "database". - AWKRST033E
An error occurred while attempting to delete the database "database". - AWKRST038E
"database": Invalid database name. - AWKRST039E
"database": Database name already exists. - AWKRST040E
Error creating document "document". - AWKRST041E
Error creating document: Document already exists. - AWKRST042E
Error creating document: Invalid document name - AWKRST043E
Error deleting document "document". - AWKRST052E
Error creating/updating attachment "attachment". - AWKRST055E
Error reading attachment "attachment". - AWKRST057E
Error deleting attachment "attachment". - AWKRST058E
Unexpected json structure. - AWKRST059E
Unable to reconnect to Cloudant job. - AWKRST060E
Write output file error. - AWKRST062E
An error occurred while monitoring the job. The error message is "error" - AWKSA - HCL Workload Automation Bridge messages
This section lists error and warning HCL Workload Automation Bridge messages that might be issued. - AWKSA002E
Unable to start the Dynamic Workload Bridge. - AWKSAF - Job plug-in for Salesforce messages
This section lists error and warning messages that might be issued by the job plug-in for Salesforce. - AWKSAF001E
An error occurred while connecting to the Salesforce site. The error message is "error" - AWKSAF002E
An error occurred while canceling the Salesforce job with the "identifier" identifier. The error message is "error" - AWKSAF003E
A connection error has occurred. The server identified by host name or URL is not reachable. - AWKSAF004E
A connection error has occurred. The user name or the password is incorrect. - AWKSAF005E
An error occurred while submitting the Salesforce job "apexClass". The error message is "error" - AWKSAF006E
An error occurred while monitoring the job. The error message is "error" - AWKSAF007E
The Salesforce job with "identifier" identifier failed. - AWKSAF008E
An error occurred while running the Salesforce job with "identifier" identifier. - AWKSAF009E
The required server address parameter is missing. - AWKSAF010E
The required user name parameter is missing. - AWKSAF011E
The required password parameter is missing. - AWKSAF012E
The required APEX batch class parameter is missing. - AWKSAF013E
The APEX batch classes were not found in Salesforce - AWKSAF014E
An error occurred while parsing the Salesforce response - AWKSBO - Job plug-in for SAP BusinessObjects BI messages
This section lists error and warning messages that might be issued by the job plug-in for SAP BusinessObjects BI. - AWKSBO001E
An error occurred while connecting to the SAP BusinessObjects site. The error message is "error" - AWKSBO002E
An error occurred while canceling the SAP BusinessObjects job with the "identifier" identifier. The error message is "error" - AWKSBO003E
A connection error has occurred. The server identified by host name or URL is not reachable. - AWKSBO004E
A connection error has occurred. The user name or the password is incorrect. - AWKSBO005E
An error occurred while submitting the SAP BusinessObjects job "BOResource". The error message is "error" - AWKSBO006E
An error occurred while monitoring the job. The error message is "error" - AWKSBO007E
The SAP BusinessObjects resource creation with "identifier" identifier failed. - AWKSBO008E
An error occurred while scheduling the SAP BusinessObjects resource "resource". Check error details on the SAP BusinessObjects console. - AWKSBO009E
The required server address parameter is missing. - AWKSBO010E
The required user name parameter is missing. - AWKSBO011E
The required password parameter is missing. - AWKSBO012E
The required SAP BusinessObjects resource parameter is missing. - AWKSBO013E
SAP BusinessObjects resource not found in SAP BusinessObjects - AWKSBO014E
An error occurred while parsing the SAP BusinessObjects response - AWKSBO016E
The required authorization type parameter is missing in the properties file. - AWKSBO018E
Incorrect server URL syntax - AWKSBO019E
Incorrect SAP BusinessObjects resource object parameter. The parameter must end with (rid:number) - AWKSBO020E
Incorrect authorization type parameter. Valid values are: secEnterprise, secLDAP, secWinAD and secSAPR3. - AWKSBO021W
Prompts not available for this report - AWKSBO022E
Incorrect SAP BusinessObjects webi report prompt name "name". The prompt name must end with (dpId:string, type:string) - AWKSBO023E
The required SAP BusinessObjects resource object format type is missing. - AWKSBO024E
Incorrect format type parameter. Valid values are: webi, pdf, xls, csv. - AWKSBO025E
Incorrect group ID. The ID must be a number. - AWKSED - Job repository data access object messages
This section lists error and warning job repository data access object messages that might be issued. - AWKSED101E
Unable to find Job with id_type ""jobID"" in the database. - AWKSED102E
Unable to find a Job definition with name ""jobName"" in the database. - AWKSED103E
Unable to create a resource related to the job with ID ""jobID"" because the resource list is empty. - AWKSED104E
Unable to update the job definition with name ""jobName"" and namespace ""namespace"" because it was not found in the database. - AWKSED105E
An error occurred when parsing JSDL while writing to the database. The following error was returned: ""operation_output"". - AWKSED106E
An error occurred when parsing JSDL while reading from the database. The following error was returned: operation_output. - AWKSED107E
Unable to create the job definition because a job definition with name ""jobName"" already exists. - AWKSED108E
An error occurred when parsing the EPR string while writing to the database. The following error was returned: error. - AWKSED109E
An error occurred when parsing the EPR string while reading from the database. The following error was returned: error. - AWKSED110E
Unable to create the requirement because a requirement with name ""reqName"" already exists. - AWKSED111E
Unable to find a requirement with name ""reqName"" and namespace namespace"" in the database. - AWKSED112E
Unable to update the requirement with name ""reqName"" and namespace ""namespace"" because it was not found in the database. - AWKSED113E
An error occurred when parsing the requirement while reading from the database. The following error was returned: operation_output. - AWKSPS - SPSS statistics subset messages
This section lists error and warning messages that might be generated by the routines that handle the SPSS statistics subset. - AWKSPS001E
The HCL Workload Automation agent cannot monitor the SPSS Job Duration Prediction job. - AWKSPS002E
The required IBM SPSS Modeler Solution Publisher directory name is missing. - AWKSPS003E
The required history input zip file name is missing. - AWKSPS004E
The required prediction output zip file name is missing. - AWKSPS005E
The required plot output zip file name is missing. - AWKSPS006E
Error using directory "directoryname". The directory does not exist. - AWKSPS007E
Error opening file "filename". The file does not exist. - AWKSPS008E
An error occurred while submitting the SPSS Job Duration Prediction job. The error message is "error" - AWKSRI - Job brokering definition console installation messages
This section lists error and warning messages that could be generated by the job brokering definition console installation process - AWKSRI001E
An error occurred while connecting to the DB2 instance. - AWKSRI002E
There is a database with the same name in the directory. - AWKSRI003E
Unable to create the database. - AWKSRI004E
An error occurred while processing the ddl file. - AWKSRI005E
The database is already present and cannot be created. - AWKSRI006E
An error occurred while connecting to the database. - AWKSRI007E
Unexpected error returned by the dbsetup script. - AWKSRI008E
An error is returned by InstallShield MultiPlatform while unloading files. - AWKSRI009E
An error occurred, see log files for details. - AWKSRI010W
The installation of "component" was cancelled. - AWKSRI011E
The installation of "component" failed. - AWKSRI012I
You must restart the system to continue the installation. - AWKSRI013I
The InstallShield wizard has successfully installed the selected components of "product". - AWKSRI014W
Unable to determine the installation status. - AWKSRI015E
You must have administrator privileges to run this installation. - AWKSRI016W
The "value" value must be specified. - AWKSRI017E
The deployment of WebSphere Application Server failed. Check the WebSphere Application Server trace and log files for details. - AWKSRI018E
"value"does not match the repeat password field. - AWKSRI019E
The specified path "path" is too long. - AWKSRI020E
The silent installation failed. Check the "log_file" file for details. - AWKSRI021E
The silent installation failed because an unsupported value "value" was specified for the installation type. Supported installation types are typical and custom. - AWKSRI023E
The database administrator does not have privileges to access the installation directory. - AWKSRI024E
The path name "path"is not valid because it contains incorrect characters. - AWKSRI025E
A value must be assigned to the installLocation attribute. - AWKSRI026E
You specified a read only directory "directory_name"for the installLocation attribute. - AWKSRI027E
An unexpected error occurred, check the trace files for details. - AWKSRI028E
The specified options file "filename"was not found. - AWKSRI029E
An internal error occurred. The options file type "type" is not supported. - AWKSRI030E
The mandatory parameter "parameter" is not present in the options file or in the command line arguments. - AWKSRI031E
No value is assigned to the mandatory parameter "parameter" in the options file or in the command line arguments. - AWKSRI032E
The specified value "value " is not valid for "parameter" Valid values are: "values". - AWKSRI033E
The specified installation path "path" is not a valid directory name. - AWKSRI034E
The version of the DB2 server installed on "DB2_location" is "DB2 version"{1}. This version is not supported by Tivoli Dynamic Workload Broker. - AWKSRI035E
The specified value "value " is not valid for "parameter". - AWKSRI036E
Unable to connect to the DB2 database. - AWKSRI037E
The specified value "value " is not valid for the port number parameter"parameter". - AWKSRI038E
Unable to connect to the DB2 server. Error details: "error". - AWKSRI040E
The enterprise application deployment failed with an unexpected error. Check the WebSphere Application Server trace and log files section for details. - AWKSRI041E
The version of the WebSphere Application Server installed on "WAS_location" is not supported by Tivoli Dynamic Workload Broker. - AWKSRI042E
The specified value "value " is not valid for the WebSphere Application Server location parameter"parameter" - AWKSRI046E
The post installation test failed. See below for details. - AWKSRI048E
The DB2 server is not listening on port "port"specified as the "parameter". - AWKSRI049E
The License Agreement was not accepted. - AWKSRI050E
The command failed. Check the error log section for details. - AWKSRI052E
The port "port" specified for the "portlabel_tovalidate" is not free. - AWKSRI053E
The specified value is too long. The "name" cannot be longer than 16 characters. - AWKSRI054E
The specified value is not correct. The first character of the "name" must be a letter. - AWKSRI055E
The Table Space name cannot exceed the 18 characters length. - AWKSRI056E
The Table Space name cannot start with a number. - AWKSRI057E
The specified name is too long. The names of the database instance and the database cannot exceed 8 characters in length. - AWKSRI058E
The database name cannot contain the following characters: @, $, and #. - AWKSRI060I
A reboot is required to continue the installation. - AWKSRI062E
The silent uninstallation failed. Check the log file "logfile"for details. - AWKSRI063I
The uninstallation in silent mode completed successfully. Uninstallation summary: "summary" - AWKSRI064E
The uninstallation of "product" failed. See the log file for more details. - AWKSRI065E
See DB2 error message. - AWKSRI066E
The profile "profile_name" specified for the "profilelabel_tovalidate" is not present on the WebSphere Application Server installed on "installation_path". The discovered profiles are: "profile_list". - AWKSRI067W
An error occurred while collecting information from the WebSphere Application Server profile. The return code is "return_code"and the error is "return_code" - AWKSRI068E
The server "server_name" specified for the "serverlabel" is not present on the WebSphere Application Server installed in "installation_path". The discovered servers are: "server_list". - AWKSRI069E
The cell "cell_name" for the "celllabel" is not present on the WebSphere Application Server installed in "installation_path". Existing cells are: "cell_list". - AWKSRI070E
The node "node_name" specified for the "nodelabel" is not present on the WebSphere Application Server installed in "installation_path". Existing nodes are: "node_list". - AWKSRI071E
The installation of the Tivoli Agent Manager failed. If it is partially installed, uninstall it before re-running this step. The Tivoli Agent Manager installation reported the following: - AWKSRI072E
The installation of the Tivoli Agent Manager failed. No error is returned running the {0} command. - AWKSRI073W
No feature is selected. Click Back and select a feature to install or Cancel to quit the installation. - AWKSRI074W
No feature to be installed is specified in the response file. - AWKSRI077E
The uninstallation of the Tivoli Agent Manager failed. - AWKSRI078E
The uninstallation of the Tivoli Agent Manager failed. No error is returned running the "command" command. - AWKSRI080E
Unable to connect to the DB2 server running on host "hostname" and listening on port "portnumber". - AWKSRI081E
Unable to connect to Connection to host"hostname" on port "portnumber"to check for the "value". - AWKSRI082E
The specified user ID"user_id" cannot be authenticated on the server "server_name" of the profile "profile_name" on the Web Application Server installed in "installation_path" with the supplied credentials. - AWKSRI083E
The command "command" with arguments "arguments" failed with error code: "error". Command output: "output" Error Message: "error_message" - AWKSRI084E
The value "value" is not a valid boolean value for the parameter "parameter". - AWKSRI085E
The value "value" is not a valid value for the parameter "parameter". - AWKSRI086E
The value "value" specified for the path parameter "path" is not a directory. - AWKSRI087E
The value "value"specified for the profile location parameter "location" is not a valid profile location - AWKSRI088W
The installation wizard cannot check the DB2 installation. Check that the DB2 is installed correctly. - AWKSRI089E
Feature "feature" is already installed at patch level "installed_level". You are trying to install it at a previous level: "prev_level"- - AWKSRI089W
The installation wizard cannot check the WebSphere Application Server installation. Check that the WebSphere Application Server is installed correctly. - AWKSRI091E
An error occurred during the installation. See the log file "file" for details. - AWKSRI092E
An error occurred during the installation. See the trace file "file" for details. - AWKSRI093W
No feature is selected. Click Back and select a feature to uninstall or Cancel to quit. - AWKSRI094E
This patch has been superseded. The installation exits. - AWKSRI095W
The Tivoli Agent Manager was not correctly installed or it is already uninstalled. - AWKSRI096W
The uninstaller cannot find file "file". - AWKSRI097E
The installation of the Common Agent Services failed. - AWKSRI099E
The installation of the Common Agent Services failed. No error is returned running the "command" command. - AWKSRI101E
The uninstallation of the Common Agent Services failed. - AWKSRI102E
The uninstallation of the Common Agent Services failed. No error is returned running the "command" command. - AWKSRI103E
The installation of the Tivoli Common Agent failed. The trace file "file" might contain additional information on the cause of this failure. - AWKSRI104W
A later version of the Tivoli Common Agent is already installed. - AWKSRI105W
The user did not allow the installation to upgrade the Tivoli Common Agent. The trace file "file" might have additional information on the cause of this failure. - AWKSRI106E
You provided a wrong password on Services. The trace file "file" might have additional information on the cause of this failure. - AWKSRI107E
An incorrect JRE was used to invoke the installer. The trace file "file"might have additional information on the cause of this failure. - AWKSRI108E
A file operation failed. Possible failures are: Cannot copy JRE Cannot change file directory permissions Cannot copy cert files The trace file "file" might have additional information on the cause of this failure. - AWKSRI109E
Unable to create, start, or stop a service. The trace file "file" might have additional information on the cause of this failure. - AWKSRI110E
One of the following utility failures occurred: Cannot encrypt or decrypt a password Cannot reset GUID Cannot update script files Cannot scrub file, e.g. of password values Cannot run system commands The trace file "file" might have additional information on the cause of this failure. - AWKSRI111E
A property failure occurred. Unable to update one or more of the following files: nonstop.properties endpoint.properties smfnonstop.properties The trace file "file" might have additional information on the root cause of this failure. - AWKSRI112E
The validation of the Tivoli Common Agent response file failed. The trace file "file" might have additional information on the cause of this failure. - AWKSRI113E
The Tivoli Common Agent installer returned an unexpected return code "return_code" The trace file "file" might have additional information on the cause of this failure. - AWKSRI114E
The deployment of the "bundle" bundle failed because the installer could not find the "file" file bundle. - AWKSRI115W
The bundle file for the bundle "bundle" is already present as "file". - AWKSRI116E
An error occurred while opening file "file" while deploying bundle "bundle". - AWKSRI117E
An error occurred while copying file "file" to "location". - AWKSRI118E
The deployment of the bundle "bundle" failed. Check the error message for additional information. - AWKSRI119E
The deployment of the bundle "bundle" failed. The following error is returned: "error" The following is reported on the Standard Error: "std_err" - AWKSRI121E
Bundle "bundle" failed to start. Check the error message for additional information. - AWKSRI122E
Bundle "bundle" failed to start. The following error was returned: "error" The following is reported on the Standard Error: "std_err" - AWKSRI123I
Bundle "bundle" started successfully. - AWKSRI124E
Bundle "bundle" failed to stop. Check the error message for additional information. - AWKSRI125E
Bundle "bundle" failed to stop. The following error was returned: "error" The following is reported on the Standard Error: "std_err" - AWKSRI126I
Bundle "bundle" stopped successfully. - AWKSRI127E
The "variable" variable could not be set. Check the error message for additional information. - AWKSRI128E
The "variable" variable could not be set. The following error was returned: "error" The following is reported on the Standard Error: "std_err" - AWKSRI129I
Variable "variable" is correctly set. - AWKSRI130E
The Tivoli Common Agent did not register to the Tivoli Agent Manager. - AWKSRI131E
The Tivoli Common Agent is not ready to accept requests on port "portnumber". - AWKSRI132E
The Tivoli Common Agent failed to stop. Check the error message for additional information. - AWKSRI133E
The Tivoli Common Agent failed to stop. The following error was returned: "error" The following is reported on the Standard Error: "std_err" - AWKSRI135E
An error occurred while copying file {0} to {1}. - AWKSRI136E
The installer cannot find the template property file that was expected to be on "file_path". - AWKSRI137E
An error occurred while opening the file "file_path" for writing. - AWKSRI138E
Unable to create directory "directory". - AWKSRI139E
The user "userID" cannot access the directory "directory" of the installation image. - AWKSRI140E
Unable to uninstall bundle"bundle". Check the error message for additional information. - AWKSRI141E
Unable to uninstall bundle"bundle". The following error was returned: "error" The following is reported on the Standard Error: "std_err" - AWKSRI143E
The Tivoli Common Agent failed to start. Check the error message for additional information. - AWKSRI144E
The Tivoli Common Agent failed to start. The following error was returned: "error" The following is reported on the Standard Error: "std_err" - AWKSRI145I
The Tivoli Common Agent started successfully. - AWKSRI146E
Unable to connect to Oracle Net Service. Error details: "error" - AWKSRI148E
The installation of each of the Extension features requires the installation of the Server feature. Select the Server for installation to install the Extension. - AWKSRI149E
The value "user_or_password"you specified is not compliant with the rules for "field_label". - AWKSRI150E
No Oracle instance is present in "path". - AWKSRI151E
Oracle server version "version" is installed in "path" This version is not supported by Tivoli Dynamic Workload Broker. - AWKSRI154E
The database "database" does not exist on the DB2 server or is not at the right level. The following error was returned: "error" Specify another database name or install the Tivoli Dynamic Workload Broker Database feature. - AWKSRI155E
User "userID" does not exist or the specified password is wrong. Specify another user, check the password or install the Tivoli Dynamic Workload Broker Database feature. - AWKSRI156E
The Tivoli Common Agent failed to start before the timeout expired. Check the error message for additional information. - AWKSRI157E
The Tivoli Common Agent failed to start before the timeout expired. The following error was returned: "error" The following is reported on the Standard Error: "std_err" - AWKSRI159E
The Agent Name contains an unsupported character. Valid characters are all alphanumeric characters and the following characters: ., -, _. - AWKSRI160E
Values specified for the isDB2 and isOracle parameters in the response file are inconsistent. You must set one of the parameters to true and the other parameter to false. - AWKSRI161E
The specified table space "table_space" does not exist on the Oracle server. - AWKSRI162E
Unable to resolve the fully qualified host name "hostname". - AWKSRI163I
The feature installation completed successfully. - AWKSRI164I
The feature uninstallation completed successfully. - AWKSRI165E
The feature installation failed. Error message is "error" - AWKSRI166E
The feature uninstallation failed. Error message is "error" - AWKSRI167E
The Table Space name cannot start with the underscore character. - AWKSRI168I
The update of the installed components is completed. Click Finish to exit the wizard. - AWKSRI169E
An error occurred while updating the database "database". - AWKSRI170E
The database "database" does not exist. - AWKSRI171E
The Tivoli Dynamic Workload Broker schema is not present in the "database" database. - AWKSRI172E
The Tivoli Dynamic Workload Broker schema present in the "database" database is not at the current level. - AWKSRI173E
An instance of Tivoli Dynamic Workload Broker Agent has been discovered in the selected installation path. It is at the same or a higher version than the one you are trying to install. Change the installation path if you want to install a new instance of version 8.5.1. - AWKSRI175E
User "userID" does not own an Oracle Tivoli Dynamic Workload Broker schema or its version is not valid. - AWKSRI176E
The upgrade of the Tivoli Dynamic Workload Broker Agent can not be performed in disconnected mode. Specify false for the DisconnectedMode property in the response file. - AWKSRI177E
The version of the Agent Manager you are trying to connect to is "amversion". The version required by Tivoli Dynamic Workload Broker server is "amsupportedversion" or higher. - AWKSRI178E
You are attempting to install the Tivoli Dynamic Workload Broker on an unsupported WebSphere Application Server flavour. The supported flavour is Embedded Express. - AWKSRI179E
No instance of Tivoli Dynamic Workload Broker Agent to apply the fix to has not been discovered in the selected installation path. - AWKSTE - Job plug-in for IBM Sterling Connect:Direct messages
This section lists error and warning messages that might be issued by the job plug-in for IBM Sterling Connect:Direct. - AWKSTE001E
One or more required parameters are missing. - AWKSTE002E
A connection error has occurred. - AWKSTE003E
For the specified Primary node, you cannot reach a Secondary Nodes. - AWKSTE004E
The Primary Node Address is a required parameter. - AWKSTE005E
A connection error has occurred. The Server Address or Port value is incorrect. - AWKSTE006E
A connection error has occurred. The user name or the password is incorrect. - AWKSTE007E
A Sterling KQV Error has occurred. - AWKSTE008E
An error occurred submitting the job. - AWKSTE009E
An error occurred monitoring the job. - AWKSTE010E
An unknown error occurred. - AWKSTE011E
For the Primary Node, the User ID is a required parameter. - AWKSTE012E
For the Primary Node, the Password is a required parameter. - AWKSTE013E
For the Secondary Node, the User ID is a required parameter. - AWKSTE014E
For the Secondary Node, the Password is a required parameter. - AWKSTE015E
For the Primary Node, the Port is a required parameter. - AWKSTE016E
The Primary Node Port is not valid value. Specify a value ranging from 1 - 65535. - AWKSTE017E
The Secondary Node Name is a required parameter. - AWKSTE018E
The Sterling Connect:Direct Process is a required parameter. - AWKSTE019E
The Local File Path for the Send action is a required parameter. - AWKSTE020E
The Remote File Path for the Send action is a required parameter. - AWKSTE021E
The Local File Path for the Receive action is a required parameter. - AWKSTE022E
The Remote File Path for the Receive action is a required parameter. - AWKSTE023E
The Check Point Restart value is a required parameter if you select ""Check"" type. - AWKSTE025E
An error occurred running the IBM Sterling job. - AWKSTE026E
The IBM Sterling process ended with errors. The IBM Sterling internal error is: error - AWKSTE027E
An error occurred deleting the IBM Sterling process. The error is: ""error_msg"". - AWKSTE029E
An error occurred when submitting the IBM Sterling process. The error is: ""error_msg"". - AWKSTE030E
The file name that identifies the process is a required parameter. - AWKSTE031E
The Check Point Restart value is invalid. It must be a positive integer. - AWKSTE032E
The platform value is invalid. Specify one of the following valid values: Unknown, Windows, OpenVMS, OS400 or Unix - AWKSTE033E
The destination disposition value is invalid. Specify one of the following valid values: RPL, MOD or NEW - AWKSTE034E
The compression type value is invalid. Specify one of the following valid values: NONE or EXTENDED - AWKSTE035E
The check point restart value is not valid. Specify one of the following valid values: Default, None or Check - AWKSTE036E
The action type value is not valid. Specify one of the following valid values: Send or Receive - AWKSUL - Utility messages
This section lists error and warning utility messages that might be issued. - AWKSUL001E
Unable to find the Dynamic Workload Broker path "path_label". - AWKSUL002E
An internal error occurred while finding the Dynamic Workload Broker "path_label" path. The following error was returned: "error". - AWKSUL003E
Unable to parse the job definition document. The following error was returned: "parsing_error_message". - AWKSUL004E
Unable to parsing the job definition document. The XML is not correct or an I/O error occurred. - AWKSUL005E
The application name "application_name" is not one of the following permitted values: "allowed_values_list". - AWKSUL006E
The optimization name "optimization_name" is not one of the following permitted values: "allowed_values_list". - AWKSUL007E
The recovery action name "recovery_action_name" is not one of the following permitted values: "allowed_values_list". - AWKSUL008E
Unable to convert the job definition to an XML document. - AWKSUL009E
An internal error occurred getting the configuration file "config_file". The following error was returned: "error". - AWKSUL010E
Unable to find the configuration file "config_file". - AWKSUL011W
An error occurred while loading the user configuration file "config_file". The following error was returned: "error". The default values will be used. - AWKSUL012W
Unable to find the user configuration file "config_file". The default values will be used. - AWKSUL013E
An error occurred while storing the user configuration file "config_file". The following error was returned: "error". - AWKSUL014E
The value "wrong_parameter_value" specified for configuration parameter "parameter" is too low.Specify a value in the range "minimum" to "maximum".The default value "default_parameter_value" will be used. - AWKSUL015E
The value "wrong_parameter_value" specified for configuration parameter "parameter" is too high.Please specify a value in the range "minimum" to "maximum".The default value "default_parameter_value" will be used. - AWKSUL016I
The configuration parameter "parameter" will be set to "parameter_value". - AWKSUL017E
The configuration parameter "parameter" has the following incorrect number format "wrong_parameter_value". The default value "parameter_value" will be used. - AWKSUL018E
The configuration parameter "parameter" has a wrong format "wrong_parameter_value". The default value "parameter_value" will be used. - AWKSUL019E
Unsupported attribute or element: "element" with value: "value". - AWKSUL020E
Unsupported element: "element". - AWKSUL021E
The value "uservariable" is not allowed in the password field "passwordfield". The use of a variable as user is not allowed in password fields. - AWKSUL022E
The value "tag_value" contains an invalid keyword. The keyword "password_syntax" is allowed only in password fields. - AWKSUL081W
An incorrect duration has been specified: "duration". - AWKTPM - Tivoli Provisioning Manager messages
This section lists error and warning Tivoli Provisioning Manager messages that might be issued. - AWKTPM001W
An error occurred while loading the user configuration file "config_file". The following error was returned: "error". The default values will be used. - AWKTPM002E
An error occurred while getting the configuration file "config_file". The following error was returned: "error". - AWKTPM003E
Unable to file the configuration file "config_file" . - AWKTSA - IBM Workload Scheduler Bridge messages
This section lists error and warning IBM Workload Scheduler Bridge messages that might be issued. - AWKTSA004E
Unable to stop the Dynamic Workload Bridge. - AWKTSA006E
Unable to configure the Dynamic Workload Bridge configuration. - AWKTSA008E
Unable to start Netman. - AWKTSA011W
The WRITER service is already started. - AWKTSA013W
The MAILMAN service is already started. - AWKTSA016W
The SCRIBNER service is already started. - AWKTSA018E
Unable to start the TWSAgent WRITER service. - AWKTSA020E
Unable to stop the TWSAgent WRITER service. - AWKTSA022E
Unable to start Mailman. There could be a problem with the uplink connection to Domain Manager. - AWKTSA023W
Unable to start Mailman. The TWSAgent CPU is not initialized. - AWKTSA025E
Unable to stop Mailman. - AWKTSA027E
Unable to start Jobman. The uplink connection might not be available. - AWKTSA029E
Unable to stop Jobman. - AWKTSA031E
Scribner failed to retrieve the job output for job""JobID"" (alias""Job_alias""). - AWKTSA033E
The Dynamic Workload Bridge CPU could not link to its parent. - AWKTSA035E
The Dynamic Workload Bridge CPU was not correctly initialized. - AWKTSA043E
The Dynamic Workload Bridge could not forward the new job status ""Job_status"" for the job ""Job_name"" and job ID""JobID"" to Dynamic Workload Broker. - AWKTSA047W
Unable to find the job with alias""Job_alias"" . - AWKTSA048E
An internal error occurred. Scribner could not retrieve job output for the job with job ID ""JobID"" and job alias""Job_alias""). - AWKTSA049E
The Dynamic Workload Bridge could not submit the job ""JobID"" and job alias""Job_alias"" to the Dynamic Workload Broker server. - AWKTSA050E
A problem with the JCL content, prevent Dynamic Workload Bridge from submitting the job ""Job_Name"" (alias""Job_alias"". The following error was returned:""error"". - AWKTSA051E
The Dynamic Workload Bridge Notification Service cannot contact Dynamic Workload Bridge. - AWKTSA052E
The Dynamic Workload Bridge Notification Service received a notification with an unknown format: ""format"". - AWKTSA053E
An authentication problem occurred contacting the Dynamic Workload Broker server. The UserId ""userId"" does not exist or the password is wrong. - AWKTSA054E
The Dynamic Workload Bridge was not started because it has been disabled. - AWKTSA055E
An error occurred sending the job output for job ""JobID"" (alias""Job_alias""). The error message is ""Error_Message"" - AWKTSA056E
An internal error occurred while getting the job output for job ""JobID"" (alias""Job_alias""). The error message is ""Error_Message"" - AWKTSA057E
An internal error occurred while getting the job output for job ""JobID"" (alias""Job_alias""). The error message is ""Error_Message"" - AWKTSA058E
The agent returned a wrong interval while getting the job output for job ""JobID"" (alias""Job_alias""). - AWKTSA059E
The following error was returned retrieving the job output of the job with alias ""Job_alias"": ""Error_Message"" - AWKTSA060E
The following error was returned was returned sending the job output of the job with alias ""Job_alias"": ""Error_Message"" - AWKTSA061E
An event for the workstation ""workstation"" was received but this workstation is no longer in the plan. The event is discarded. - AWKTSA062E
An error occurred saving the Launch Job message into the DB. - AWKTSA063E
An error occurred removing the Launch Job message from the DB. - AWKTSA064E
An error occurred opening the port ""port_number"". The error is ""Error_Message"". - AWKTSA065E
An error occurred creating the work manager of the broker workstation.The error is ""Error_Message"". - AWKTSA067E
Failed contacting workstation: ""workstation"" in order to perform centralized agent update with error: ""error"" - AWKTSA068E
JobMan cannot start. The error message is: ""error"" - AWKTSA069E
JobMan cannot start. The error message is: ""error"" - AWKTSA070E
The Job Status Notifier thread cannot start. The error message is: ""error"" - AWKTSA071E
The Job Status Notifier thread cannot start. The error message is: ""error"" - AWKTSA072E
The Job Status Notifier thread cannot start. The error message is: ""error"" - AWKTSA073E
The Job Status Notifier thread cannot start. The error message is: ""error"" - AWKTSA074E
An error occurred processing a job status change. The error message is: ""error"" - AWKTSA075E
An error occurred creating the thread that processes the job status change events. The error message is: ""error"" - AWKTSA076E
An error occurred creating the thread that processes the job status change events. The error message is: ""error"" - AWKTSA077E
An error occurred processing a job status change. The error message is: ""error"" - AWKTSA078E
An error occurred creating the work manager ""workmanager"". The error message is: ""error"" - AWKTSA079E
An error occurred creating the work manager ""workmanager"". The error message is: ""error"" - AWKTSM - Tivoli Storage Manager messages
This section lists error and warning Tivoli Storage Manager messages that might be issued. - AWKTSM001E
The Tivoli Storage Manager command "cmd" completed with an error. Analyze the messages in the Tivoli Storage Manager log file. - AWKTSM003E
The required command path parameter is missing."cmd". The error message is "error" - AWKTSM004E
The required command parameter is missing. - AWKTSM005E
The required password parameter is missing. - AWKTSM006E
An error occurred while running the command "cmd". The error message is "error" - AWKAWS - Job plug-in for Amazon EC2
This section lists error and warning audit service messages that might be issued by the Job plug-in for Amazon EC2. - AWKAWS001E
Error during saving. Required field: - AWKAWS002E
Error during saving. Please complete all fields - AWKAWS003E
Test connection failed. Please check your credentials and your network connection. - AWKAWS005E
No Instances. - AWKAWS006E
Error. Please fill in at least one of these two sections: \"Manage Existing Virtual Server\" or \"Create New Virtual Server\". - AWKAWS007E
Error. Please fill in one of these two sections: \"Manage Existing Virtual Server\" or \"Create New Virtual Server\". - AWKAWS008E
Get Instances failed. - AWKAWS009E
Get Instance Details failed. - AWKAWS010E
Error. Please select an Instance. - AWKAWS011E
No images. - AWKAWS012E
Get Image Details failed. - AWKAWS013E
Error. Please select an Image. - AWKAWS014E
No types. - AWKAWS015E
Unable to get region. - AWKAWS017E
Operation failed - AWKAWS018E
Operation unauthorized - AWKAWS019E
No networks. - AWKAWS020E
No subnets. - AWKAWS021E
No security groups. - AWKAWS022E
Start is not allowed. Instance must be in stopped status. - AWKAWS023E
Stop is not allowed. Instance must be in pending, running, shutting down or stopping status. - AWKAWS024E
Reboot is not allowed. Instance must be in running status. - AWKAWS025E
Remove is not allowed. Instance must be in pending, running, shutting down, stopped or stopping status. - AWKAWS026E
Error during saving. Please insert the AMI and the Instance Type - AWKWSE - Web services job executor messages
This section lists error and warning messages that might be generated by the routines that handle the web services job executor process. - AWKWSE001E
The Wsdl URL is missing. - AWKWSE002E
Missing operation - AWKWSE003E
The user name or the password is missing. - AWKWSE004E
Empty argument - AWKWSE005E
WebService invocation failed: "exception_message" - AWKWSE009E
The host "hostname" is unknown. - AWKWUJ - Dynamic Workload Console Broker common messages
This section lists error and warning messages that could be issued. - AWKWUJ016E
An error occurred while retrieving the job definitions from the Dynamic Workload Broker server. More details follow: "error details" - AWKWUJ017E
The format of the string "string" is incorrect. - AWKWUJ018E
An error occurred while retrieving the job definition. More details follow: "error details". - AWKWUJ019E
The job definition is not structurally correct. Some details follow: "error details". - AWKWUJ020E
An error occurred while saving the job definition. More details follow: "error details". - AWKWUJ021E
You must select at least one job for this operation. - AWKWUJ022E
Only one job can be selected for this operation. - AWKWUJ024E
An error occurred retrieving the job instances from the Dynamic Workload Broker server. More details follow: "error details" - AWKWUJ026E
The name of an existing job definition can only be changed using the Job Brokering Definition Console. Replace the new name "new name" with the previous name "old name". - AWKWUJ027E
The value "value" is not valid for this field. A numeric value is required. - AWKWUJ028E
The value "value" is not valid for this field. A positive integer numeric value is required. - AWKWUJ029E
A value for this field is required. - AWKWUJ030E
A variable with the same name "variable name" is already present. Provide a unique variable name. - AWKWUJ035W
The configuration file "configuration file name" cannot be found or is not readable. The default configuration will be used. - AWKWUJ036E
The Web service connections could not be initialized. More details follow: "error details" - AWKWUJ037E
The value "value" is not valid for this field. - AWKWUJ038W
No target resource for the job has been specified. The system will allocate the best available resource to the job. - AWKWUJ039E
An error occurred retrieving the list of computers matching the job requirements. More details follow: "error details" - AWKWUJ040E
An error occurred retrieving the output of the "job name" job instance. More details follow: "error details" - AWKWUJ041W
This operation may take a long time. Are you sure you want to continue? - AWKWUJ042W
No previous job has been specified. The system will allocate the best available resource to this job. - AWKWUJ044E
The operation failed because of a security problem. The user specified in the server connection does not have the required level of authorization on the Dynamic Workload Broker server. - AWKWUJ045E
You cannot define an affinity relationship with the selected job instance because the instance has not been successfully allocated to a computer. - AWKWUJ046E
The operation "operation name" failed because of an internal error. More details follow: "error details" - AWKWUJ047E
The Web service "web service name" cannot be found. - AWKWUJ048E
The operation failed because of a security problem: the user or the password specified in the server connection are incorrect. - AWKWUJ050E
The operation failed because of a syntax error in a variable expression in the JSDL. The following expression "variable expression" is incorrect. - AWKWUJ051E
The operation failed because of a syntax error in a variable expression in the JSDL. The following expression "variable expression" is incorrect. The expected type is "variable expression". - AWKWUJ052W
The following variables could not be replaced in the JSDL: "variable names". This might have limited the list of available resources for the job. If you cannot find the resource you were looking for, go back, provide values for any of these variables and try again. - AWKWUJ053E
There has been a communication failure with the server: either the host is not available, or the address or the port (or both) are not correct. - AWKWUJ054E
An error occurred retrieving the output of the job instance. More details follow: "error details" - AWKWUR - Dynamic Workload Console Broker resource messages
This section lists error and warning messages that could be issued. - AWKWUR001E
The format of the string "string" is incorrect. - AWKWUR002W
You must select at least one object for this operation. - AWKWUR003E
The resources have not been suspended because of a communication problem with the scheduling server. Check the console server configuration and make sure that the scheduling server and the database are running. - AWKWUR005E
The resources have not been resumed because of a communication problem with the scheduling server. Check the console server configuration and make sure that the scheduling server and the database are running. - AWKWUR007E
The operation could not be performed because of a problem with the scheduling server. Check the console server configuration and make sure that the scheduling server and the database are running. - AWKWUR008E
The operation failed because of internal error. More details follow: "error details" - AWKWUR009E
The following resources were not suspended because they are already in the suspended state: "resource names" - AWKWUR010E
The following resources were not resumed because they are not in the suspended state: "resource names" - AWKWUR011E
The following resources "resource names" have not been suspended because of a problem on the scheduling server. More details follow: "error details" - AWKWUR012E
The following resources "resource names" have not been resumed because of a problem on the scheduling server. More details follow: "error details" - AWKWUR013E
The following resources "resource names" have not been deleted because of a problem on the scheduling server. More details follow: "error details" - AWKWUR015E
An error occurred retrieving the computers from the scheduling server. More details follow: "error details" - AWKWUR016E
An error occurred retrieving the resources from the scheduling server. More details follow: "error details" - AWKWUR019E
You must select at least one computer for this operation. - AWKWUR020E
You can select only one computer for this operation. - AWKWUR021E
A problem on the scheduling server occurred while saving the "resource name" logical resource. More details follow: "error" - AWKWUR022E
A problem on the scheduling server occurred while saving the "resource name" logical resource. The "resource name" logical resource has been created in the database, but the following computers were not associated to it: "computers list". More details follow: "error" - AWKWUR023E
A problem on the scheduling server occurred while saving the "group name" group. More details follow: "error" - AWKWUR024E
A problem on the scheduling server occurred while saving the "group name" group. The "group name" group has been created in the database, but the following computers were not associated to it: "computers". More details follow: "error" - AWKWUR025E
A problem on the scheduling server occurred while saving the "group name" group. The "group name" group has been created in the database, but the following computers "computers" and logical resources "logical resources" were not associated to it:. More details follow: "error" - AWKWUR026E
A problem on the scheduling server occurred while saving the "group name" group. The "group name" group has been created in the database, but the following logical resources were not associated to it: "logical resources". More details follow: "error" - AWKWUR027E
An error occurred retrieving computer details. More details follow: "error details". - AWKWUR028E
An error occurred saving the user preferences. - AWKWUR029E
An error occurred saving the server connection. - AWKWUR032E
A password was specified without a user name. - AWKWUR033E
You must select an object for this operation. - AWKWUR034E
You can select only one object for this operation. - AWKWUR035E
A problem on the scheduling server occurred while updating the "resource name" logical resource. The "resource name" logical resource has been updated in the database, but the following computers were not removed from it: "computers list". More details follow: "error" - AWKWUR036E
A problem on the scheduling server occurred while updating the "group name" group. The "group name" group has been updated in the database, but the following computers were not removed from it: "computers list". More details follow: "error" - AWKWUR037E
A problem on the scheduling server occurred while updating the "group name" group. The "group name" group has been updated in the database, but the following logical resources were not removed from it: "logical resources list". More details follow: "error" - AWKWUR038E
A problem on the scheduling server occurred while updating the "group name" group. The "group name" group has been updated in the database, but the following computers: "computers" and logical resources: "logical resources" were not removed from it. More details follow: "error" - AWKWUR039I
The logical resource "logical resource name"was successfully updated. - AWKWUR040I
The group of resources "lgroup of resources name"was successfully updated. - AWKWUR041E
A problem on the scheduling server occurred while searching for resource groups. More details follow: "error details" - AWKWUR042E
A problem on the scheduling server occurred while searching for logical resources. More details follow: "error details" - AWKWUR043E
An error occurred retrieving group details. More details follow: "error details". - AWKWUR044E
The installation failed on the following agents: "list of agents". More details follow: "error details". - AWKWUR045I
The installation was successful on the following agents: "list of agents". - AWKWUR046E
The uninstallation failed on the following agents: "list of agents". More details follow: "error details". - AWKWUR048E
A problem on the scheduling server occurred while searching for agents. More details follow: "error details" - AWKWUR049E
A problem on the scheduling server occurred while retrieving the agents details. More details follow: "error details" - AWKWUR051W
The following agents cannot be installed because they are unavailable: "agents" - AWKWUR052W
The following agents cannot be uninstalled because they are unavailable: "agents" - AWKWUR053E
The operation failed because of a security problem: the user specified in the server connection does not have the required level of authorization on the Dynamic Workload Broker server. - AWKWUR054E
An error occurred retrieving logical resource details. More details follow: "error details". - AWKWUR055E
The operation failed because of a security problem: the user or the password specified in the server connection are incorrect. - AWKWUR056E
The operation "operation name" failed because of an internal error. More details follow: "error details" - AWKWUR058E
An error occurred retrieving information about the Dynamic Workload Broker server. More details follow: "error details". - AWKWUR059E
The following agents cannot be configured because they are unavailable: "agents" - AWKWUR060E
The configuration failed on the following agents: "list of agents". More details follow: "error details". - AWKWUR063E
The type " " specified for logical resource " " is incorrect because it is a reserved word. - AWKWUR064E
The host name or address is not valid. - AWKWUR065E
There has been a communication failure with the server: either the host is not available, or the address or the port (or both) are not correct. - AWKXAJ - Extended agent job executor messages
This section lists error and warning messages that might be generated by the routines that handle the extended agent job executor process. - AWKXAJ001E
The method parameter is empty. - AWKXAJ002E
The taskType parameter is empty. - AWKXAJ003E
The step parameter is empty. - AWKXAJ004E
The error parameter is empty. - AWKXAJ005E
The output parameter is empty. - AWKXAJ006E
The target parameter is empty. - AWKXAJ007E
The user name parameter is empty. - AWKXAJ008E
The taskString parameter is empty. - AWKXAJ009E
The jsdlxa:xajob element is missing in the job definition. - AWKZSJ - z/OS shadow job validation messages
This section lists error and warning messages that might be generated by the z/OS shadow job validation. - AWKZSJ001E
The value assigned to the application name is not coherent with the XML definition. - AWKZSJ002E
The XML namespace definition is unknown. - AWKZSJ003E
The value entered for JobStream is not valid. - AWS - R3Batch messages (twsinst)
This section lists error and warning messages that might be issued when using the R3Batch method. - AWKAWS001E
Error during saving. Required field: - AWKAWS002E
Error during saving. Please complete all fields - AWKAWS003E
Test connection failed. Please check your credentials and your network connection. - AWKAWS005E
No Instances. - AWKAWS006E
Error. Please fill in at least one of these two sections: \"Manage Existing Virtual Server\" or \"Create New Virtual Server\". - AWKAWS007E
Error. Please fill in one of these two sections: \"Manage Existing Virtual Server\" or \"Create New Virtual Server\". - AWKAWS008E
Get Instances failed. - AWKAWS009E
Get Instance Details failed. - AWKAWS010E
Error. Please select an Instance. - AWKAWS011E
No images. - AWKAWS012E
Get Image Details failed. - AWKAWS013E
Error. Please select an Image. - AWKAWS014E
No types. - AWKAWS015E
Unable to get region. - AWKAWS017E
Operation failed - AWKAWS018E
Operation unauthorized - AWKAWS019E
No networks. - AWKAWS020E
No subnets. - AWKAWS021E
No security groups. - AWKAWS022E
Start is not allowed. Instance must be in stopped status. - AWKAWS023E
Stop is not allowed. Instance must be in pending, running, shutting down or stopping status. - AWKAWS024E
Reboot is not allowed. Instance must be in running status. - AWKAWS025E
Remove is not allowed. Instance must be in pending, running, shutting down, stopped or stopping status. - AWKAWS026E
Error during saving. Please insert the AMI and the Instance Type - AWSEDW001E
The following value: "value" for the following netman command line option: "option" is not in the correct format. - AWSEDW002E
System error - AWSEDW003W
Not running with root permissions - AWSEDW004E
Message file already opened by another process: !1, !2 - AWSEDW005E
Netman was unable to open its configuration file: "file_name". The following error was given by the operating system: "system_error" - AWSEDW006E
Netman could not process the service information in its configuration file: "file_name". If the problem is with a specific entry, the details are as follows (if the following fields are blank the problem is a general one): "service_entry":"service_number". - AWSEDW007E
Unable to open both message file and net connection - AWSEDW008E
Error opening stdlist - AWSEDW009E
Error duping stdlist - AWSEDW010I
Stdlist duped to fd other than 1 - AWSEDW011E
Unable to create stdlist - AWSEDW012E
An internal error has occurred. Netman has stopped because the following non-valid unlink request has been received: "service_request ". The error message and number are as follows: "error_number": "error_message" - AWSEDW013E
An internal error has occurred. Netman received the following unlink request "service_request" from the following message file: "message_file". Unlink requests received from a message file are not allowed. - AWSEDW014E
Invalid request !3 on !1: !2 - AWSEDW015E
Netman received the following unknown service request: "service_request" - AWSEDW016I
Starting: !1 pin !2 - AWSEDW017E
Netman received a service request for the following service that has a service type of disabled : "service_request" - AWSEDW018E
Error building message file: !1, !2 - AWSEDW019E
An internal error has occurred. Netman was unable to open its message file, NetReq.msg, for reading. The following messages were given:Operating system error: "system_error"Events file library error: "library_error". - AWSEDW020E
An internal error has occurred. Netman was unable to set up its TCP/IP port to listen for service requests. The following operating system message was received: "error_message". - AWSEDW021E
Netman was unable to stop the following service as part of the child process cleanup procedures performed before exiting: "service". The following error message was given by the operating system: "error_message". - AWSEDW022E
An internal error has occurred. Netman encountered an IPC error when waiting for a service request to arrive or when reading a service request, from the following port: "port_number". The error message is as follows: "system_error" - AWSEDW023E
An internal error has occurred. Netman encountered an IPC error when trying to close the connection with the client process on the following port: "port_number", "system_error". - AWSEDW024E
An internal error has occurred. Netman encountered an error while it was trying to read a service request from the following message file: "message_file". The following operating system error message is given: "error_message". - AWSEDW025E
An internal error has occurred. Netman was unable to pass the circuit information as an argument to the program associated with the following service request: "service_request". The operating system error message is as follows: "error_message". - AWSEDW026E
Netman was unable to run the child process associated with the following service request: "service_request". The operating system error message is as follows: "error_message ". - AWSEDW027E
An internal error has occurred. Netman is unable to send an acknowledgment packet in response to the following service request: "service_request ". The following error message is given: "error_message" - AWSEDW028I
Received stop_netman: !3 - AWSEDW029E
Error closing net link: !1, !2 - AWSEDW030E
An internal error has occurred. Netman was unable to set the signal handler to ignore one of the following signals: SIGTTOU, SIGTTIN, and SIGTSTP. The signal number is as follows: "signal_number". The operating system error message is as follows: "system_error" - AWSEDW031E
An internal error has occurred. Netman was unable to create a new session when trying to become a daemon process. The operating system error message is as follows: "error_number", "error_message". - AWSEDW032E
An internal error has occurred. Netman was unable to change the current working directory to the root directory when trying to become a daemon process. The operating system error message is as follows: "error_number", "error_message". - AWSEDW033W
The following duplicate service request has been received: "service_request". The following is the error message: "error_message" - AWSEDW035W
The following request cannot be performed because netman is emptying its request cache: "service_request" - AWSEDW042I
Terminating, no sons active - AWSEDW043I
Terminating, no children active - AWSEDW044W
Son !1 pin !2 is gone, status: !3 - AWSEDW045W
Client pin !1 is gone, status: !2 - AWSEDW046I
Terminating, total cpu !1 - AWSEDW047I
Stdlists switched. Total cpu time !1 - AWSEDW048I
Command !1 is !2 options !3. - AWSEDW049I
Opened IPC successfully. - AWSEDW050E
An internal error has occurred. Netman, while attempting to launch itself as a daemon, cannot set the real group id (gid) to the HCL Workload Automation group id. The error occurred in the following source file: "file_name", at line: "line_number". The operating system error message is as follows: "error_message", !4. - AWSEDW051E
An internal error has occurred. Netman, while attempting to launch itself as a daemon, cannot set the real user id (uid) to the HCL Workload Automation user id. The error occurred in the following source file: "file_name", at line: "line_number". The operating system error message is as follows: "error_message", !4. - AWSEDW052W
IP address validation not performed for request: !1. Connection received from IP address: !2. !3. Service request accepted. - AWSEDW053E
Netman could not validate the IP address for a service.Service request: "service_request"IP address: "IP_address"Error type: "error_type"Error message: "validation_error". - AWSEDW056E
Netman was unable to retrieve its product group name from the components file. Netman might not have been installed correctly, or the components file might not be correct. - AWSEDW057I
Netman installed under group '!1'. - AWSEDW058E
Netman cannot find the program file associated with the following service number: "service_number" and action number: "action_number" in its configuration file"netman_configuration_file". - AWSEDW059E
Netman was unable to get information about its configuration file, "file_name". The operating system error message is as follows: "system_error" - AWSEDW060E
Netman found a non-valid service request in its configuration file. [ SEE AWSEDW058 FOR FORMATs , NetConf. "file_name":"ServiceEntry": "service_number" !4 !5 - AWSEDW061E
Netman was unable to create a new thread. Pipe connections are not supported. - AWSEDW062E
Netman cannot enable a named pipe server process to wait for a client process. The error occurred in the following source file: "file_name", at line: "line_number". The operating system error message is as follows: "error_number", from the following call: "system_call". - AWSEDW063E
An internal error has occurred. Netman was unable to identify the following user that is trying to start a service: "user_ID". - AWSEDW064I
Pipe Connections will be supported - AWSEDW065E
CreateEvent() failed: File !1 (line !4): Error !2 from !3 - AWSEDW066E
Netman encountered an error trying to write data to a pipe. The error occurred in the following source file: "file_name", at line: "line_number". The operating system error message is as follows: "error_number", from the following call: "system_call". - AWSEDW067E
Netman encountered an error trying to read data from a pipe. The error occurred in the following source file: "file_name", at line: "line_number". The operating system error message is as follows: "error_number", from the following call: "system_call". - AWSEDW068E
Netman encountered an error trying to create a named pipe. The error occurred in the following source file: "file_name", at line: "line_number". The operating system error message is as follows: "error_number", from the following call: "system_call". - AWSEDW069E
Netman was unable to create a handle for a new thread starting Service Client thread. The error occurred in the following source file: "file_name", at line: "line_number". The operating system error message is as follows: "error_number", from the following call: "system_call". - AWSEDW070E
An internal error has occurred. Netman could not write to the Windows event log. The operating system error message is as follows: "error_number". The error occurred in the following source code file: "file_name" at line"line_number". - AWSEDW073I
Alias !1 is !2 options !3. - AWSEDW074I
Invalid alias entry in !1:!2: !3 - AWSEDW075I
Netman (pid=!1 pgid=!2) was started by the starter process (pid=!3 pgid=!4) - AWSEDW080I
Opened SSL IPC successfully - AWSEDW081W
SSL port set to 0 - no SSL IPC opened - AWSEDW090E
An attempt has been made to perform a non-secure action from a remote workstation to the local workstation. The remote workstation does not have the correct security rights to access the local workstation. - AWSEDW091E
Netman was unable to start a new process. Your HCL Workload Automation license expired "exp_date". - AWSETO001E
An internal error has occurred. The HCL Workload Automation Object Monitor plug-in is unable to write the configuration for the agent "workstation_name", the reason is: "reason". - AWSETO002E
The event "event_name" of type "event_type" is not valid, because filters are not allowed on Stop reason when Running=true is specified. - AWSETO003E
The event "event_name" of type "event_type" is not valid, because filters are not allowed on Restarting when Running=true is specified. - AWSETO004E
The event "event_name" of type "event_type" is not valid, because filters are not allowed on No restart reason when Restarting=true is specified. - AWSETO005E
The event "event_name" of type "event_type" is not valid, because filters are not allowed on No restart reason when StopReason=Stop is specified. - AWSETO006E
The event "event_name" of type "event_type" is not valid, because filters are not allowed on Unlink reason when LinkStatus=Linked is specified. - AWSAEM - Event management messages
This section lists error and warning event management messages that might be issued. - AWSAEM001E
An internal error has occurred. The property com.ibm.tws.event.configuration.manager is not found in the TWSConfig.properties file. - AWSAEM002E
An internal error has occurred while loading or initializing the DAO factory class "factory_class". - AWSAEM003E
Unable to execute the operation because this workstation is not the Event Processor Manager. - AWSAEM005W
This workstation "workstation" is not the Event Processor Manager. - AWSAHL - Action helper messages
This section lists error and warning action helper messages that might be issued. - AWSAHL001E
The action plug-in "plug-in_name" is not valid. - AWSAHL007E
The action "action_type" of event rule instance "rule_name" ("time_stamp") has completed with errors: "msg" - AWSAHL008W
The event rule instance "rule_name" ("time_stamp") has completed with warnings. - AWSAHL009E
The event rule instance "rule_name" ("time_stamp") has completed with errors. - AWSAUT - Job plug-in for OSLC Automation messages
This section lists error and warning messages that might be issued by the job plug-in for OSLC Automation. - AWSAUT001E
The Registry Services URI was not specified. - AWSAUT002E
A password was provided without specifying the Registry Services user. Specify a user name or delete the password. - AWSAUT003E
The password associated with the specified Registry Services user was not provided. - AWSAUT004E
The Service Provider URI was not specified. - AWSAUT005E
A password was provided without specifying the Service Provider user. Specify a user name or delete the password. - AWSAUT006E
The password associated with the specified Service Provider user was not provided. - AWSAUT007E
The Template URI was not specified. - AWSAUT008E
An error occurred while attempting to go to the IBM OSLC server. The IBM OSLC server connection parameters are not correct: "error_msg". - AWSAUT010E
The syntax used for the Registry Services URI is not correct. Verify that you specified a valid string. - AWSAUT011E
The syntax used for the Registry Services URI is not correct. Verify that you specified a valid string. - AWSAUT012E
An error occurred while connecting to the IBM OSLC service. The error is "error message" - AWSAUT013E
The syntax used for the Automation Service Provider URI is not correct. Verify that you specified a valid string. - AWSAUT014E
The syntax used for the Automation Service Provider URI is not correct. Verify that you specified a valid string. - AWSAUT015E
The syntax of the Service Provider URI "provider URI" is not correct. The error is: "error message" - AWSAUT016E
The Service Provider at the address "provider URI" does not exist. - AWSAUT017E
The property file "plug-in property file" for the OSLC Automation job was not found. - AWSAUT018E
An error occurred while loading the property file "plug-in property file" for the OSLC Automation job. - AWSAUT019E
The following error occurred when retrieving the description of the Service Provider: "error message". - AWSAUT020E
The following error occurred when retrieving the list of the Service Providers: "error message". - AWSAUT021E
The property file "provider URI" for the OSLC Automation job is empty. - AWSAUT023E
The job did not complete successfully. For detailed information, go to the following address: "instance uri". - AWSAUT024E
The job did not complete successfully. For detailed information, go to the following address: "instance uri". - AWSAUT025E
The job did not complete successfully. For detailed information, go to the following address: "instance uri". - AWSAUT026E
The job did not complete successfully. For detailed information, go to the following address: "instance uri". - AWSAUT027E
The job did not complete successfully. For detailed information, go to the following address: "instance uri". - AWSAUT028E
The job did not complete successfully. For detailed information, go to the following address: "instance uri". - AWSAUT029E
The URI of the remote instance "instance uri" is not valid. - AWSAUT033E
The following error: "error message" was returned by the remote system. - AWSAUT034E
An internal error occurred. The location header is not present in the response sent by the remote system. - AWSAUT035E
The status of the job cannot be monitored. The status is set to unknown. - AWSAUT036E
The status of the job cannot be monitored after the agent restarted. The status is set to unknown. - AWSAUT038E
The syntax used for the Registry Services URI "registry services URI" is not correct. The error is: "error message". - AWSAUT039E
An error occurred while retrieving the list of service providers from the Registry Services with URI "Registry services URI". The error is: "error message". - AWSAUT040E
An error occurred while retrieving the list of service providers from the Registry Services with URI "Registry services URI". - AWSAUT041E
The syntax used for the Service Provider URI "provider URI" is not correct. Ensure that you specified a valid string. - AWSAUT042E
An error occurred while loading the user interface to configure the instance. The error is: "error message". - AWSAUT043E
The following error occurred when retrieving the creation dialog: "error message". - AWSAUT044E
The syntax used for the Service Provider URI "provider URI" is not correct. Ensure that you specify a valid string. - AWSAUT045E
An error occurred while retrieving the details of the Service Provider with URI "provider URI". The error is: "error message". - AWSAUT046E
The address discovered for the panel "creation dialog URI" is not correct. The error is: "error message". - AWSAUT047E
The address discovered for the panel "creation dialog URI" is not correct. The error is: "error message". - AWSAUT048E
The automation request was not defined. - AWSAUT049E
An error occurred while connecting to the IBM OSLC service. The error is "error message" - AWSAUT050E
An error occurred while connecting to the IBM OSLC service. The error is "error message" - AWSAUT051E
An error occurred while connecting to the IBM OSLC service. The error is "error message" - AWSBAT - Event counter messages
This section lists error and warning messages that might be issued by the event counter used by the fault-tolerant switch manager feature. - AWSBAT003E
The event counter failed to initialize for the following reason: "error_message" - AWSBAT004E
The event counter has failed after encountering the following problem: "error_message" - AWSBAT005E
The event counter failed to initialize while attempting to load its table with workstation names from the Symphony file. The following gives more details of the error: "system_error". - AWSBAT008E
The process could not retrieve a value from the event counter. - AWSBAT011W
The event counter received a message with a lower ID-number ("ID_number") than a message previously received from the same workstation. - AWSBAT012E
The process could not write the received ID-number to the event counter. - AWSBAT015E
The event counter could not be saved because the following error occurred: "error_message" - AWSBAT053E
The run-number in the Symphony file is higher than the current Symphony run-number. - AWSBAT054E
The saved event counter file could not be opened. - AWSBAT055E
A new event counter file could not be created, and there is no saved file. - AWSBAT056E
The following operating system error has affected the functionality of the process: "error_code". - AWSBAT057E
The event counter file is corrupt. - AWSBAT058E
The event counter failed to initialize. - AWSBAT059E
The event counter failed to initialize. - AWSBCS - Check health status messages
This section lists error and warning check health status messages that could be issued. - AWSBCS002E
The timeout value !1 is not valid. - AWSBCS003E
There is a syntax error. Too few parameters have been supplied. - AWSBCS026W
Node "node" is running with an old Symphony file. - AWSBCS027E
An internal error occurred while calculating the path between firewalls and prevents node "from_node" from connecting with node "to_node". - AWSBCS028E
An error occurred while communicating with node "node": "err_msg" - AWSBCS029W
The node "node" is not able to ping its Domain Manager. - AWSBCS030W
Message file "filename" on node "node" has reached "percentage"% of its maximum size. - AWSBCS031E
Message file "filename" on node "node" has reached its maximum size. - AWSBCS032W
The filesystem where HCL Workload Automation is installed on node "node" is almost full. Only "available" MBytes are available. - AWSBCS033E
The filesystem where HCL Workload Automation is installed on node "node" is full. - AWSBCS034E
The Symphony file on node "node" is corrupted. More details are available in the local HCL Workload Automation trace files. - AWSBCS040W
Workstation "ws_name" was not found in the Symphony file on node "node". - AWSBCS041W
Domain "dom_name" was not found in the Symphony file on node "node". - AWSBCS042W
Node "node" is not running. - AWSBCS043W
Nodes "node1" and "node2" are not linked. - AWSBCT - Utility program messages
This section lists utility program error and warning messages that might be issued. - AWSBCT002E
A jcl file is required. - AWSBCT003E
The jcl file path must be no more than !1 characters - AWSBCT004E
The -u option is available only for root users. - AWSBCT005W
The jcl is submitted as root, you must use -u <user>. - AWSBCT006E
No password entry for the user. Error: !1 - AWSBCT007E
The user name must not be more than 8 bytes. - AWSBCT008E
This user needs read and execute access for <jclfile> !1. Error: !2 - AWSBCT009E
No group entry for this user. Error: !1 - AWSBCT010W
Created !1 as a job stream from the group name. - AWSBCT011W
Only 8 byte schedule names supported, using: !1 - AWSBCT012W
Only 8 byte job names supported, using: !1 - AWSBCT013W
Used !1 as job name, from filename. - AWSBCT014E
An error occurred accessing the current work directory: !1 - AWSBCT015E
An error has occurred writing to !1, Error: !2 - AWSBCT016E
An error has occurred opening !1, Error: !2 - AWSBCT017E
An error has occurred reading stdin, Error: !2 - AWSBCT018E
Could not acquire a temporary file. - AWSBCT019E
An error has occurred closing !1, Error: !2 - AWSBCT021E
Could not assign a schedule name, use -s option. - AWSBCT022E
Could not assign a job name, use -j option. - AWSBCT023E
Must assign date/time in the format YYMMDDHHmm. - AWSBCT024E
Date/time must have 10 digits in the format YYMMDDHHmm. - AWSBCT025E
Priority must be a numeric value from 0 to 101, hi (= 100), or go (= 101). - AWSBCT026E
<!1> must be specified with a leading alphabetic character. - AWSBCT031E
You must start Netman manually on this system. - AWSBCT033E
An error occurred starting the local system, Type: !1, Error: !2 - AWSBCT034E
An error occurred starting the NS/DS system: !1, Error: !2 - AWSBCT035E
You specified an incorrect product. - AWSBCT036E
An error occurred starting the TCP system: !1, Error: !2 - AWSBCT037W
System names are limited to 8 characters. - AWSBCT038E
An error occurred accessing PROCINFO, Error1: !1, Error2: !2 - AWSBCT039E
Unknown service type !1 on !2 - AWSBCT040E
Service !1 already active on !2 - AWSBCT042E
Service !1 disabled on !2 - AWSBCT043E
Service !1, generated an unknown ack or error !3, on !2 - AWSBCT044E
Incorrect client on !2, service !1 denied. - AWSBCT045E
An error occurred accessing the mozart database. - AWSBCT046E
An error occurred initializing security. - AWSBCT047E
The user is not authorized to display the selected workstation. - AWSBCT048E
Router on !1 failed to connect to the service. - AWSBCT071W
Netman is already down. - AWSBCT072E
Stopping local Netman, Error: !1 - AWSBCT073W
No Netman. - AWSBCT074W
Netman is already down. - AWSBCT081E
Environment variable !1 was not found, not a HCL Workload Automation job. - AWSBCT091E
chmod error on !1, Error: !2 - AWSBCT092E
chown error on !1, Error: !2 - AWSBCT094E
No commands entered, the job has not been submitted. - AWSBCT105E
Unrecognized option !1. - AWSBCT107E
Databases not converted. Exiting. - AWSBCT108E
The globalopts file does not exist. - AWSBCT109E
The globalopts file needs read and write permission. Check the permissions. - AWSBCT111W
!1 is identical to !2. - AWSBCT112E
Databases not updated. Exiting. - AWSBCT113E
Unable to get inode info for !1. stat() failed. - AWSBCT116E
!1 is a special file. - AWSBCT119E
Failed to get current working directory. Exiting. - AWSBCT120E
Unable to create backup directory. Path name exceeds limit. Exiting. - AWSBCT121E
Cannot create backup directory !1. - AWSBCT122E
Backup directory !1 is not writeable. Check permissions and umask. - AWSBCT123E
Unable to open !1 for reading. - AWSBCT124E
Unable to open !1 for writing. - AWSBCT125E
An error has occurred reading file !1. - AWSBCT126E
An error has occurred writing file !1. - AWSBCT127E
Database !1 not backed up. - AWSBCT128E
Failed to convert !1. - AWSBCT129E
Failed to copy !1 to !2 directory. - AWSBCT200E
You must enter the user manually. - AWSBCT201E
Incorrect option. - AWSBCT202E
The path is limited to !1 characters. - AWSBCT203E
The filename is the only argument available. - AWSBCT212E
TokenService Error: %d in %s near %d - AWSBCT301E
You do not have permission to access !1: You must be root or the creator. - AWSBCT302E
An error has occurred with file !1: !2 - AWSBCT303E
Delete of !1 failed: !2 - AWSBCT305E
The delete utility is unable to continue because of the following unexpected Windows error accessing the user details: "error_description". - AWSBCT306E
Delete of !1 failed: !2. TWS processes must be stopped in order to delete file. - AWSBCT307E
Delete of !1 failed: Is a directory. - AWSBCT309E
Delete of !1 not performed: Invalid path. - AWSBCT401E
An error has occurred while opening the job table: type=!1, !2 - AWSBCT402E
No entry was found for this job number. - AWSBCT403E
Missing environment variable !1. - AWSBCT404E
Error: The value !2 for !1 is invalid. - AWSBCT405E
Keyword !1 not found. - AWSBCT406E
Keyword !1 is not unique. - AWSBCT407E
Keyword !1 is too long. - AWSBCT601E
Error on !1: !2 - AWSBCT602E
File !1 is nonexistent or unreadable. - AWSBCT651E
You must be on the master domain manager to run this program. - AWSBCT652E
You must have build access to the !1 database to run this program. - AWSBCT708E
Incorrect username. - AWSBCT709E
Unknown argument %c - AWSBCT710W
The -u and -d options cannot both be supplied. - AWSBCT711E
No files specified. - AWSBCT712E
Unable to get current directory file (error %d) - AWSBCT713E
Unable to get full path for file %s (error %d) - AWSBCT714E
Unable to set current directory to %s (error %d) - AWSBCT715E
Unable to get owner for file %s (error %d) - AWSBCT716E
Unable to get owner from security descriptor %s (error %d) - AWSBCT719E
Unexpected error finding files (error %d) - AWSBCT720E
Unexpected error closing find handle (error %d) - AWSBCT721E
Error finding files with pattern = %s Error %d - AWSBCT722E
Unable to get process token (error %d) - AWSBCT723E
Unable to initialize security descriptor (error %d) - AWSBCT724E
Unable to set security descriptor owner (error %d) - AWSBCT725E
Unable to set restore privilege (error %d) - AWSBCT727E
Unable to change owner for file %s (error %d) - AWSBCT728E
Unable to open file %s (error %d) - AWSBCT729E
Unable to reset restore privilege (error %d) - AWSBCT751E
Exception Message: !1 - AWSBCT756E
Cannot initialize. - AWSBCT764E
!1 server: Unknown error - AWSBCT765E
Unable to bind to exception message. - AWSBCT790E
!1 not installed on your system. Cannot execute. - AWSBCT791E
Framework has not been installed on this system. Cannot execute !1. - AWSBCT865E
Error opening SC Manager. error = %d. - AWSBCT866E
-s option requires a service name. - AWSBCT867E
-u option requires a user name. - AWSBCT868E
-D option requires a dependency spec. - AWSBCT869E
-d option requires a display name. - AWSBCT870E
-l option requires the executable location. - AWSBCT871E
-p option requires the password. - AWSBCT872E
Unknown argument %c. - AWSBCT873W
Only one of -i or -r must be specified. - AWSBCT874E
Service name must be specified. - AWSBCT875E
Service location must be specified. - AWSBCT876E
Username AND password both must be specified. - AWSBCT877E
Remove option requires only the service name. - AWSBCT878W
Extraneous arguments ignored. - AWSBCT879W
Username not given. Installing as System account service. - AWSBCT880W
Display name not given. Will use service name itself. - AWSBCT881E
No dependency given. - AWSBCT882E
Error creating service (%d). - AWSBCT884E
Error opening service %d. - AWSBCT885E
Service !1 is not stopped. Cannot remove. - AWSBCT886E
Unable to delete service (%d). - AWSBCT888E
Cpuinfo cannot show information about workstation "workstation" because is not included in the current Symphony file. - AWSBCU - SSL messages (symaccs)
This section lists symaccs error and warning messages that might be issued when using SSL. - AWSBCU001E
Opening "Variable", error: "Error" - AWSBCU002E
Locking "Variable", error: "Error" - AWSBCU003E
Unable to allocate comarea "Comarea" - AWSBCU004E
Could not set file options on "Variable", error "Error" - AWSBCU005E
Closing "Variable", error: "Error" - AWSBCU006E
Purging "Variable", error: "Error" - AWSBCU007E
An error has occurred in the common area used to access the Symphony file. - AWSBCU008E
Seeking "Variable", record "Record" ("Record2"), error: "Error" - AWSBCU009E
Reading "Variable", record "Record" ("Record2"), error: "Error" - AWSBCU010E
Writing "Variable", record "Record" ("Record2"), error: "Error" - AWSBCU011E
Trying to read a nonexistent record from "Variable", Record "Record" ("Record2"). - AWSBCU012E
Write called without update access on "Variable" - AWSBCU013E
Obtaining statistics on "Variable", error: "Error" - AWSBCU014E
End of file on "Variable", record "Record" ("Record2"). - AWSBCU015E
Error comarea isn't a symaccs comarea - AWSBCU016E
No write access to "Variable", record "Record" ("Record2"). - AWSBCU017E
Attempting to write NIL ("Variable") record to "Record". - AWSBCU018E
Write recnum disagreement on "Variable", recnum "RecNum" ("RecNum2"). - AWSBCU021E
Attempting to write past absolute limit on "Variable", record "Record" ("Record2"). - AWSBCU022E
No statistics available for record type, for "Variable2", on "Variable". - AWSBCU023W
Stats only kept on production transactions, not for "Variable" - AWSBCU024E
Procedure not implemented. - AWSBCU025E
Lock called and "Object" already locked, record "Record" ("Record2"), error: "Error" - AWSBCU026E
Unknown lock flag for lock on "Object", record "Record" ("Record2"), error: "Error" - AWSBCU027W
Unlock called for "Object", record "Record" ("Record2"), file not locked. - AWSBCU028E
Call to LOCK failed for "Object", record "Record" ("Record2"), error: "Error" - AWSBCU029E
Call to GETLOCK failed for "Object", record "Record" ("Record2"), error: "Error" - AWSBCU030E
Call to RENAME failed on "Object", error: "Error" - AWSBCU031E
Exclusive access needed to install "Object" as Symphony. - AWSBCU032E
File "File" already locked by another process, error: "Error" - AWSBCU035E
Opening "Object", error: "Error" - AWSBCU036E
Seeking "File", record type "RecordType", error: Record not found - AWSBCU037W
Filename "FileName" exceeds "Limit" byte limit, Warning: Filename truncated. - AWSBCU038E
Filepath "FilePath" exceeds "Limit" byte limit. Filepath unusable. - AWSBCU040E
%s:%d sym_e_2_i() unexpected Symphony record type: 0%o - AWSBCU041E
%s:%d sym_i_2_e() unexpected Symphony record type: 0%o - AWSBCU042W
OPENS dependency resolution could fail at runtime because of the syntax used. Action must be taken. - AWSBCU150W
SSL authorization is required to connect to the following workstation "workstation_name" - AWSBCV - Mailman messages
This section lists error and warning messages that might be issued by the mailman component. - AWSBCV001E
Batchman has failed with an internal error, producing the following status code: "status". - AWSBCV002E
Error building !1, Error !2 - AWSBCV003E
Mailman was unable to start one of the internal components ("program") of batchman. The system error message is "system_error" - AWSBCV004E
Mailman was unable to start one of its internal components ("program") due to an internal error. The operating system error message is "system_error". - AWSBCV005E
Mailman encountered an internal error opening the following file: "file_name". The operating system error message is "error_message". - AWSBCV006E
Workstation "workstation_name" cannot be added to the mailman table because there are more workstations than the maximum allowed. - AWSBCV007E
The workstation "workstation_name" cannot be accessed. - AWSBCV008E
A message file cannot be opened; the operating system gives the following error: "error_message" - AWSBCV009E
Mailman could not open the workstation message file: "file_name" in the PO box. The following gives more details of the error: "error_message". - AWSBCV010E
Error opening Symphony on !1 - AWSBCV011E
Error reading cpu records, Error !1 - AWSBCV012E
Mailman cannot read a message in a message file. The following gives more details of the error: "error_message". - AWSBCV013E
Error server jcw bad for !1 - AWSBCV014E
Mailman could not start the following mailman server: "server_name". The following gives more details of the error: "error_message". - AWSBCV015E
Mailman was unable to write a message to the PO box message file for workstation: "workstation_name". The following gives more details of the error: "error_message". - AWSBCV024W
Mailman has lost communication with the following workstation: "workstation_name". - AWSBCV025W
Mailman has unlinked from workstation: "workstation_name". - AWSBCV034W
Impossible branch taken: file: !1, line: !2 - AWSBCV035W
Mailman was unable to link to workstation: "workstation_name"; the messages are written to the PO box. - AWSBCV036W
Mailman cannot link to the following workstation: "workstation_name" because it has an incompatible Symphony file. - AWSBCV037E
Mailman encountered an internal error while it was reading the Sinfonia file. The following gives more details of the error: "error_message ". - AWSBCV038E
Mailman encountered a memory problem while downloading the Symphony file to workstation. Mailman failed to allocate the memory necessary to store the information that it needs to read from the Sinfonia file: "workstation_name" - AWSBCV040W
Mailman cannot link to the following workstation: "workstation_name". - AWSBCV045E
Error adding cpu !1 to Symphony, Error: !2 - AWSBCV047E
Error getting info on Sinfonia - AWSBCV048E
Error renaming Sinfonia on !1 - AWSBCV050E
Error writing Sinfonia on !1 - AWSBCV051E
Error purging Sinfonia on !1 - AWSBCV052E
Error closing Sinfonia on !1 - AWSBCV053E
Error closing Symphony on !1 - AWSBCV054E
Error closing mailbox on !1 - AWSBCV057E
Error writing to remote Mailbox on !1 - AWSBCV058E
Error opening remote Mailbox on !1 - AWSBCV059E
Error building remote Mailbox on !1 - AWSBCV060E
Error opening DSline to !1, Type !2, Error !3 - AWSBCV062E
Mailman encountered the following error when attempting to open the Symphony file: "error_message". - AWSBCV063E
Link to !1 failed - AWSBCV064E
Error attempting to lock Links, Error: !1 - AWSBCV065E
Error creating Start program !1, Error: !2 - AWSBCV066E
Mailman was not able to remove a record from the following message file: "message_file". The following gives more details of the error: "error_message". - AWSBCV067E
Mailman was not able to read a message from the following message file in the pobox directory: "message_file". The following gives more details of the error: "error_message" - AWSBCV068E
Mailman found a discrepancy when trying to delete a message from the Mailbox.msg message file. The following gives more details of the error: "error_message" - AWSBCV069E
Mailman cannot find the workstation: "workstation_name" in the Symphony file. - AWSBCV076E
Mailman could not add information about the following workstation: "workstation_name" to the Symphony file. The following gives more details of the error: "system_error" - AWSBCV078E
Error locking Straus - AWSBCV079E
Error unlocking Straus - AWSBCV080W
Warning link to !1 not found in Straus - AWSBCV081E
Error updating Straus - AWSBCV084E
Mailman could not link to the following workstation "workstation_name" because it encountered a non valid link type: "link_type_ID". - AWSBCV088E
Mailman could not write a mailbox record to the Intercom.msg file. The following gives more details of the error: "error_message". - AWSBCV089E
Error writing to remote !1, Error: !2 - AWSBCV095E
Mailman was unable to pass a message to the following mailman server: "server_name" because of the following internal error: "error_message". - AWSBCV097E
Mailman cannot access the batchman program file. - AWSBCV098W
Mailman has not received an acknowledgement for a message sent to workstation: "workstation_name". - AWSBCV099E
Mailman has lost communication with workstation: "workstation_name". - AWSBCV100W
Warn: DS remotes are invalid, assuming slave for !1. - AWSBCV101E
Error: TCP slaves are invalid, can not initialize !1. - AWSBCV107E
Mailman has encountered an internal error as it could not find a record for the following workstation in the Symphony file: "workstation_name". - AWSBCV110E
Mailman has verified that jobman has terminated unexpectedly. The exit status of jobman is: "exit_status". - AWSBCV111E
Error setting pgid: !1 - AWSBCV112E
Mailman encountered an error trying to start or restart a workstation. The following gives more details of the error: "error_message". - AWSBCV113E
The master mailman process has terminated unexpectedly because of an internal error. - AWSBCV114E
Mailman could not set the termination signal handling routines. The following gives more details of the error: "error_message". - AWSBCV115E
Mailman is unable to find the new manager workstation: "workstation_name" in the Symphony file. The following gives more details of the error: "error_message". - AWSBCV117E
Mailman encountered an internal error while attempting to switch domain managers in the following domain: "domain_name" - AWSBCV118E
Mailman encountered an internal error while attempting to update the Symphony file record header during the initialization process. - AWSBCV119E
Mailman encountered an internal error while attempting to find the workstation record for the workstation on which it is running in the Symphony file. - AWSBCV120E
Mailman encountered an internal error while attempting to find its own domain definition record in the Symphony file. - AWSBCV121E
Mailman cannot link to the following workstation: "workstation_name", which is a domain manager but is running a version prior to 6.0. - AWSBCV122E
Mailman cannot link to workstation: "workstation_name". - AWSBCV124E
Mailman is unable to connect to workstation "workstation_name" using SSL due to an inconsistency in the HCL Workload Automation network configuration. - AWSBCV125E
Mailman could not write to the following ftbox: "ftbox_name" for "workstation_name". The following gives more details of the error: "error_message". - AWSBCV126E
Mailman has stopped the event counter because it received the following error while processing it: "error_message". - AWSBCV127W
Mailman encountered the following error: "error_message" because an event with id-number 0 was sent from the workstation hosting an X-agent. - AWSBCV128E
Mailman cannot send an acknowledgement (ACK) to the writer on the following workstation: "workstation_name ". - AWSBCV129E
Mailman cannot send a message indicating that a communication problem had been encountered (NACK) to the writer on the following workstation: "workstation_name". - AWSBCV132E
Mailman could not create the replay file for "workstation_name". - AWSBCV133W
Mailman could not truncate the ftbox "ftbox_name". - AWSBCV134W
The replay table could not be passed to the following workstation: "workstation_name" because of an internal error. - AWSBCV135W
Mailman is in isolated state and cannot open any outbound connection. - AWSBCV136W
Event !1 from: !2 to: !3 on iteration !4 was canceled. - AWSBCV137W
A possible message loss was detected at the start of the replay protocol on the following event: "record_ID", from the following workstation: "workstation_name". - AWSBCV139E
An internal error has occurred while updating the Mailbox header. The error message is as follows: "error_message". - AWSBCV140W
An error has occurred while creating the Windows event object which signals the status of the HCL Workload Automation processes. The error message is as follows: "error_number". - AWSBCV143E
Mailman encountered an error trying to send switchmgr command to a workstation. The following gives more details of the error: "error_message". - AWSBCV144E
Mailman could not write a mailbox record to the auditbox.msg file. The following message contains more details of the error: "error_message". - AWSBCW - Writer messages
This section lists error and warning messages that might be issued by the writer component. - AWSBCW001W
Warning illegal option(s): !1 - AWSBCW002W
Writer cannot find a valid wr read value in the localopts file. The value found is as follows: "wr_read". The default value is used. - AWSBCW003E
Writer cannot connect to the remote mailman. The following gives more details of the error: "error_text". - AWSBCW004E
Error non numeric sockfd: !1 - AWSBCW008E
The following error has occurred while installing the Sinfonia file: "error_message". - AWSBCW010W
Writer has received and ignored the following unknown Symphony record type from the remote mailman: "record_type". - AWSBCW011E
An error occurred while converting a Symphony file record from network to host byte order. The following gives more details of the error: "error_text" - AWSBCW012E
Writer was unable to read a record from mailman. The following gives more details of the error: "error_text". - AWSBCW013E
Error building Mailbox.msg file: !1 - AWSBCW014E
Writer is unable to open the Mailbox.msg message file. The following gives more details of the error: "error_text" - AWSBCW015E
Writer is unable to write to the message file Mailbox.msg. The following gives more details of the error: "error_text" - AWSBCW016E
Writer is unable to send the initialization process LinkInit record to the remote mailman. The following gives more details of the error: "error_text". - AWSBCW017E
Writer is unable to send a LinkAck record to mailman to acknowledge that a packet has been received correctly. The following gives more details of the error: "error_text". - AWSBCW018E
Writer is unable to indicate to mailman with a LinkNack record that there was a communication error while receiving an initialization packet. The following gives more details of the error: "error_text". - AWSBCW019E
Writer, when exiting on error, is unable to send an unlink command record to mailman. The following gives more details of the error: "error_text". - AWSBCW020E
Writer received an incorrect command during workstation initialization. Writer expected a stop Symphony command after mailman downloaded the Symphony file, but did not receive it. The following message might be given: "error_text". - AWSBCW021E
Writer received a stop Symphony record when mailman was not downloading the Symphony file. The following error text might be given: "error_text". - AWSBCW023E
Error Unknown Rec Type !1 - AWSBCW024W
Writer encountered the following internal error: "error_message" - AWSBCW025E
Writer is started by netman with an incorrect number of arguments. - AWSBCW026E
Error incorrect caller info: !1 - AWSBCW027E
Writer is unable to create its stdlist file. - AWSBCW033E
Writer could not allocate memory for internal data structures (comarea). - AWSBCW036E
Writer has stopped, giving the following operating system error: "error_number". The total cpu time is as follows: "time " - AWSBCW037E
Writer cannot initialize this workstation because mailman is still active. - AWSBCW038E
Writer needs the exclusive access to the Symphony and Sinfonia files in order to initialize the workstation. Either batchman or mailman is using one or other of the files. - AWSBCW039E
Writer encountered an error opening the Mailbox.msg file. The total cpu time used is as follows: "time" - AWSBCW040E
Writer encountered an error while processing the Symphony file. The total cpu time is as follows: "time" - AWSBCW041E
Writer stops because it has not received any incoming messages during the period specified in the localopts file for the option wr unlink. The total cpu time is as follows: "time" - AWSBCW042E
Writer stops because it has encountered an error while sending an Ack message to the remote mailman. The total cpu time is as follows: "time" - AWSBCW043E
Writer stops because it has encountered an error while reading or waiting for a message from the remote mailman. The total cpu time is as follows: "time" - AWSBCW045E
Writer is unable to write an init synchronization message to the Mailbox.msg file. - AWSBCW047E
Writer encountered an error while launching the following command: "command_file_name". The following error was received from the operating system: "error_number" - AWSBCW051E
Writer was unable to find this workstation in the Symphony file during its initialization phase, or when it is trying to purge the Symphony file and rename Sinfonia file to Symphony. The following gives more details of the error: "error_text" - AWSBCW052E
During the exchange of the event counter table, it was not possible to transfer the table header correctly. The following gives more details of the error: "error_code". - AWSBCW053E
While transmitting the event counter table, it was not possible to transfer the table values correctly. The following gives more details of the error: "error_code". - AWSBCW054E
During the exchange of the event counter table, writer did not receive the confirmation message it was expecting from mailman. The following gives more details of the error: "error_code" - AWSBCW055E
Error during replay protocol, total cpu !1 - AWSBCX - Monman messages
This section lists error and warning monman messages that might be issued. - AWSBCX001E
An internal error has occurred. Monman cannot read a message in a message file. The following gives more details of the error: "error_message". - AWSBCX002E
An internal error has occurred. Monman could not set the termination signal handling routines. The following gives more details of the error: "error_message". - AWSBCX005E
An internal error has occurred. Monman encountered the following error when attempting to open the Symphony file: "error_message". - AWSBCX007E
A message file cannot be opened; the operating system gives the following error: "error_message" - AWSBCX011E
The Event Integration Facility configuration file ("file") cannot be written; the operating system gives the following error: "error_message" - AWSBCX012E
An internal error has occurred. The Event Integration Facility initialization has failed. - AWSBCX013E
An internal error has occurred. A parsing error has occurred reading the following event "event". - AWSBCX015E
An error has occurred opening the temporary file "file_name" for writing. - AWSBCX016E
An error has occurred opening the file "file_name" for reading. - AWSBCX017E
An error has occurred opening the file "file_name" for writing. - AWSBCX018E
An error has occurred writing the file "file_name". - AWSBCX019E
The zip file "file_name" was built incorrectly. The Unzip process is stopped with an error. - AWSBCX020E
An error has occurred extracting the file "file_name". The Unzip process is stopped with an error. - AWSBCX021E
An error has occurred before completing the unzip process. - AWSBCX022E
Monman encountered an error when attempting to open the Mailbox.msg file. The following gives more details of the error: "error_message" - AWSBCX023W
The Event Driven Workload Automation feature is disabled, Monman stops. - AWSBCX024W
The Agent is not able to send the Event Driven Workload Automation events to the Event Processor. - AWSBCY - messages
This section lists error and warning messages that might be issued. - AWSBCY001E
Could not allocate dbaccs comarea. - AWSBCY002E
Invalid comarea passed to dbaccs routines. - AWSBCY003E
Attempt to write to unopened file. - AWSBCY004E
Database not available or access not initialized. - AWSBCY005W
File newer than dbaccs. - AWSBCY007E
Record not found. - AWSBCY008E
Cannot make the temporary file. - AWSBCY009E
File system error. - AWSBCY010E
You cannot access the parameter. - AWSBCY011E
Bad access parameter passed to m_parm_access_allowed. - AWSBCY012E
Cannot get user's ID. - AWSBCY015E
Cannot open the database. - AWSBCZ - Dload messages
This section lists error and warning Dload messages that might be issued. - AWSBCZ001E
An error while opening !1: !2 - AWSBCZ003E
The object ID must start with an alphabetic character. - AWSBCZ004E
The object ID contains at least one character that is not valid. Valid characters are 0-9, a-z, dashes and underscores. - AWSBCZ005E
A database error occurred while writing the calendar data. - AWSBCZ006E
A database error occurred while writing the calendar dates. - AWSBCZ007E
A database error occurred while writing a parameter. - AWSBCZ008E
A database error occurred while writing a prompt. - AWSBCZ009E
A database error occurred while writing a resource. - AWSBCZ010E
The parameter value must be no more than !1 bytes. - AWSBCZ011E
The prompt value must be no more than !1 bytes. - AWSBCZ012E
A resource count was expected at this point. - AWSBCZ013E
The resource count must be in the range !1 to !2. - AWSBCZ014E
A valid object ID was expected at this point. - AWSBCZ015E
A valid date was expected at this point. - AWSBCZ016E
The date is not valid. - AWSBCZ021E
A definition keyword was expected at this point. - AWSBCZ023E
The command used is not supported for this definition. - AWSBCZ024W
The duplicate calendar definition !1 has been ignored. - AWSBCZ025W
The duplicate parameter definition !1 has been ignored. - AWSBCZ026W
The duplicate prompt definition !1 has been ignored. - AWSBCZ027W
The duplicate resource definition !1#!2 has been ignored. - AWSBCZ028E
Workstation !1 defined in cpudata: !2 does not exist. - AWSBCZ103E
The description exceeds the maximum length of "max_description" bytes. - AWSBCZ104E
The resource name exceeds the maximum length. The maximum for the workstation is "max_workstation" bytes and the maximum for the resource is "max_resource" - AWSBCZ105E
The parameter name exceeds the maximum length of "max_parameter" bytes. - AWSBCZ106E
The prompt name exceeds the maximum length of "max_prompt" bytes. - AWSBCZ107E
The variable table name exceeds the maximum length of "max_vartable" bytes. - AWSBCZ108E
The variable description exceeds the maximum length of "max_desc" bytes. - AWSBCZ109E
The variable name exceeds the maximum length of "max_var" bytes. - AWSBCZ110E
The variable value exceeds the maximum length of "max_value" bytes. - AWSBCZ111E
The syntax of the variable table is incorrect. The token "token" is expected at this point. - AWSBCZ112E
A syntax error was detected in the list of variables. - AWSBCZ113E
The value of the variable must be a string enclosed in quotation marks. - AWSBCZ114E
The variable table "variable_table" contains syntax errors. - AWSBCZ115E
The maximum number of errors that can be displayed for the variable table has been reached. - AWSBCZ116E
The variable "variable" is already present in the variable table "variable_table" - AWSBDA - messages
This section lists error and warning messages that might be issued. - AWSBDA001W
A host has been specified for the master domain manager, and has been ignored. - AWSBDA002W
The domain manager "domain_manager" is not defined as a fault-tolerant agent. - AWSBDA003W
The domain manager "domain_manager" does not have fullstatus set to on. - AWSBDA004W
The domain manager "domain_manager" is not in the same domain. - AWSBDA005W
The domain manager "domain_manager" was not found. - AWSBDA006W
**WARNING** For cpu !1 host !2 not defined YET. - AWSBDA007W
No host has been specified in the definition of an extended agent. - AWSBDA008W
The master domain manager "master_domain_manager" has been set as the host. - AWSBDA009W
The domain manager "domain_manager" has been set as the host. - AWSBDA010W
Domain "domain" was not found. The master domain manager "master_domain_manager" has been set as the host. - AWSBDA011W
The agent's domain "agent_domain" was changed to be the host's domain "host_domain". - AWSBDA012W
The host was not found in the Symphony file. The master domain manager was made the host. - AWSBDA013W
The parent domain "domain" does not exist. The master domain "master_domain" has been set as the parent domain. - AWSBDA014W
The domain "domain" was not found. The master domain "master_domain" has been set as the domain. - AWSBDA015E
The workstation record could not be written to the Symphony file. - AWSBDA016W
The host's domain "domain" was not found. The master domain "master_domain" has been set as the domain. - AWSBDA017W
Trying to recreate the master domain !1, ignored. - AWSBDA018W
The domain name "domain_name" is not valid. The master domain "master_domain" has been set as the domain. - AWSBDA019W
The master domain "master_domain" conflicts with global options value "global_options_master_domain". The global options value has been used. - AWSBDA020W
The manager of domain "domain" is the same as the master domain manager workstation "master_domain_manager". Ignoring domain "domain". - AWSBDA021W
Access method "access_method" cannot be found on your system. - AWSBDA022W
Time zones are not enabled in the global options. - AWSBDA023W
Time zones are enabled in the global options but have not been specified for the workstation. - AWSBDB - Scribner messages
This section lists error and warning scribner messages that might be issued. - AWSBDB001E
Error opening connection to conman, Error !1 - AWSBDB002E
Error unable to create stdlist - AWSBDB004W
The timeout value !1 is not valid. The default value has been used. - AWSBDB005E
There is a syntax error. Too few parameters have been supplied. - AWSBDB006E
Error in ntoh (Symphony rec): !1 - AWSBDB007E
Error sending scribner_response rec: !1 - AWSBDB008E
Error receiving scribner_response rec: !1 - AWSBDB009E
Error: Could not allocate storage for comarea - AWSBDB011E
Error reading stdlist file for job !1.!2: !3 - AWSBDB012E
Error opening stdlist file for job !1.!2: !3 - AWSBDB013E
Error getting stdlist file status information for job !1.!2: !3 - AWSBDB014E
Error closing stdlist file for job !1.!2: !3 - AWSBDC - NetView/OpenView messages
This section lists error and warning NetView and OpenView messages that might be issued. - AWSBDC001E
Error in !1, calling !2, for !3, error: !4 - AWSBDC002E
Error allocating space in !1, error: !2 - AWSBDC003E
Unknown parent for !1, id=!2 - AWSBDC004E
Unknown node for !1, ID=!2 - AWSBDC005E
Unknown network for !1, ID=!2 - AWSBDC006E
Unknown workstation for !1, ID=!2 - AWSBDC007E
Unknown owner for !1, ID=!2 - AWSBDC008E
Error in !1, calling !2, for !3, field !4, error: !5 - AWSBDC009E
Error unknown case in !1, line=!2, value=!3 - AWSBDC010E
Error in getpwuid in !1 - AWSBDC011E
Error in snmp call in !1, for !2, error: !3 - AWSBDC012E
Unknown proc !2 in !1: !2 - AWSBDC013E
Unknown field !1: !2 - AWSBDC101W
Openview is not running on this system: !1 - AWSBDC102E
HCL Workload Automation is not correctly installed on this system: "computer". - AWSBDC103E
Initialization failed. - AWSBDC104E
No object for !1. - AWSBDC105E
Non-valid state packet received: !1 - AWSBDC106E
Non-valid info packet received: !1 - AWSBDC107E
Non-valid info count, doing !1: !2 - AWSBDC108E
Non-valid info obj, doing !1, count !2: !3 - AWSBDC109E
Non-valid definition packet received: !1 - AWSBDC110E
Non-valid definition, doing !1: !2 - AWSBDC112E
Non-valid process !2(!3) in !1 - AWSBDC113E
Non-valid workstation !2(!3) in !1 - AWSBDC150E
Can not send request !1 to demon: !2 - AWSBDC205E
Initialization failed. - AWSBDC206E
Error opening !1, error: !2 - AWSBDC207E
Error returned from select operation: !1 - AWSBDC208E
Error opening snmp connection to !1: !2 - AWSBDC209E
Error in !1, invalid packet: !2 - AWSBDC210E
Error in sigact: !1 - AWSBDC211E
Invalid request: !1 - AWSBDC212E
Invalid packet, doing !1: !2 - AWSBDC213E
Invalid type, doing !1: !2 - AWSBDC214E
Invalid trap. - AWSBDC217E
Error adjusting oid for !1, oid=!2. - AWSBDC305E
Initialization failed. - AWSBDC306E
Error opening !1, error: !2 - AWSBDC307E
Error returned from select operation: !1 - AWSBDC308W
Process does not have a pid: !1 - AWSBDC309E
Process has a non-valid pid: !1 - AWSBDC310E
Error writing !2 to !1: !3 - AWSBDC311E
Error sigaction: !1 - AWSBDC312E
Non-valid trap: !1 - AWSBDC313E
Non-valid data for trap !1: !2 - AWSBDC314E
Unknown workstation !2 for trap !1 - AWSBDC315E
Error opening !1: !2 - AWSBDC316E
Timeout occurred while trying to check connection to !1 - AWSBDC500E
not string - AWSBDC501E
bad length - AWSBDC502E
not print %x - AWSBDC503E
need error message for work != node - AWSBDD - Bmevents messages
This section lists error and warning Bmevents messages that might be issued. - AWSBDD001E
BmEvents error allocating space for !1: !2 - AWSBDD002E
BmEvents option !1 is not supported. - AWSBDD003E
BmEvents error opening !1: !2 - AWSBDD004E
BmEvents error writing !1: !2 - AWSBDE - Chkstat messages
This section lists error and warning Chkstat messages that might be issued. - AWSBDE001E
Unable to open a connection to client: !1 - AWSBDE002E
Unable to create the stdlist - AWSBDE004E
A non-valid value for the timeout !1 has been supplied. - AWSBDE005E
The chkstat command has not been supplied with the correct number of parameters. - AWSBDE006E
Unable to send a response record. The error is: !1. - AWSBDE007E
Unable to receive a request record: !1 - AWSBDE008E
Could not allocate storage for comarea - AWSBDE011E
Unable to close the Symphony file: !1 - AWSBDF - messages
This section lists error and warning messages that might be issued. - AWSBDF001E
Unable to open a connection to the chkstat service: !1 - AWSBDF002E
Unable to start the chkstat service: !1 - AWSBDF003E
Error: !1 - AWSBDF004E
Cannot get a reply from the chkstat service: !1 - AWSBDF005E
Cannot send a request to the chkstat service: !1 - AWSBDF006E
Cannot allocate storage for communication - AWSBDF007E
Missing argument for option !1 - AWSBDF008E
Unknown option argument: !1 - AWSBDF009E
Missing -t task option - AWSBDF010E
Missing -c cpu,host,master option - AWSBDF011E
Missing -n node option - AWSBDF012E
Missing -p port option - AWSBDF013E
Unsupported task: !1 - AWSBDF015W
The task !1 passed to netmth contains the Schedule Time parameter that is not supported by the version of the remote network. It is removed. - AWSBDG - Downloader messages
This section lists error and warning messages that might be issued by the downloader component. - AWSBDG001E
Downloader cannot connect to the remote client. The socket descriptor passed to downloader by netman is not valid. The following gives more details of the error: "error_text". - AWSBDG002E
Downloader is unable to create the stdlist file. - AWSBDG004W
Incorrect timeout value: !1, using default - AWSBDG005E
Downloader is started by netman with an incorrect number of arguments. - AWSBDG006W
The download for file "file_name" has been stopped by the client (the domain manager on z/OS). - AWSBDG007E
Downloader was unable to send a record. The following gives more details of the error by the operating system: "error_text" - AWSBDG008E
Downloader could not read a record from the centralized script. The following gives more details of the error by the operating system: "error_text" - AWSBDG009E
Downloader could not allocate memory for internal data structures (comarea). - AWSBDG011E
Downloader cannot save the downloaded centralized script in the following temporary file: "file_name ". The following operating system error was received: "error_text". - AWSBDG012E
Downloader cannot open the following temporary file where the downloaded centralized script is saved: "file_name ". The following operating system error was received: "error_text". - AWSBDG013E
Downloader cannot change the access mode of the following temporary file where the downloaded centralized script is saved: "file_name ". The following operating system error was received: "error_text". - AWSBDG014E
Downloader cannot close the following temporary file where the downloaded centralized script is saved: "file_name ". The following operating system error was received: "error_text". - AWSBDG015E
Downloader cannot convert the temporary file where the downloaded centralized script is saved from UTF-8 to the local file format. The UTF-8 file is the following: "file_name1" and the local file that cannot be created is the following: "file_name2". - AWSBDG016E
Downloader is receiving a centralized script file, but a packet is too long for the buffer. - AWSBDG017E
Downloader cannot download a centralized script. The following operating system error was received: "error_text" - AWSBDG019E
Downloader cannot obtain file status information for the following file: "file_name". The following gives more details of the error: "error_text". - AWSBDG021E
Downloader cannot create the following directory where the downloaded centralized script is saved: "directory_name". The following operating system error was received: "error_text". - AWSBDG022E
Downloader cannot write the downloaded centralized script in a temporary file on the target workstation. - AWSBDH - Java native interface messages
This section lists error and warning messages that might be issued by the Java native interface. - AWSBDH001E
The action code !1 specified in the !2 native method is invalid - AWSBDH002E
The object type !1 specified in the !2 native method is invalid - AWSBDJ - Appserverman messages
This section lists error and warning appserverman messages that might be issued. - AWSBDJ003E
The application server has stopped unexpectedly or failed. - AWSBDJ005E
Cannot restart the application server. See the application server log for the reason. - AWSBDJ006E
Cannot stop the application server. See the application server log for the reason. - AWSBDJ007W
The auto-restart flag (see localopts) is set to false, so the application server is not restarted by the application server monitor. - AWSBDJ008E
The application server has been restarted more times than the configured maximum (see localopts), so the application server will not be restarted by the application server monitor. - AWSBDJ009E
The application server was up before failing for less time than the configured minimum (see localopts), so the application server will not be restarted by the application server monitor. - AWSBDJ010E
Cannot restart the dynamic workload broker application. For details, see the application server log. - AWSBDJ011E
Cannot stop the dynamic workload broker application. For details, see the application server log. - AWSBDJ012E
An internal error occurred while opening the Appserverbox message queue. - AWSBDJ013E
An internal error occurred while opening the Mailbox message queue. - AWSBDJ016E
An internal error occurred while reading the Appservrbox message queue. - AWSBDW - Jobman messages
This section lists error and warning messages that might be issued by the jobman component. - AWSBDW001E
Jobman cannot set the process group id to the group id of the logon user. The operating system error is: "system_message". - AWSBDW002E
The user ID used to launch this job is not valid. The operating system error is: "system_error_number". - AWSBDW003E
Jobman cannot change the current working directory to the home directory of the logon user. The operating system error is: "system_error". - AWSBDW004E
Jobman could not run the job because the system call used to launch the job failed. The operating system error is: "system_error". - AWSBDW005E
The JCL file "file_name" could not be launched. The operating system error is: "system_error_number". - AWSBDW006E
Jobman could not run a job or check an external dependency because an internal system call failed. The error number is: "error_number". - AWSBDW009E
The following operating system error occurred retrieving the password structure for either the logon user, or the user who owns a file or external dependency: "system_error". - AWSBDW010E
Jobman was unable to create the monitor process that runs and monitors a job. The operating system error is: "system_error". - AWSBDW011E
Jobman received unexpected signal !1. - AWSBDW012E
Jobman was unable to delete the following JCL file "file_name" because it cannot find it or does not have the rights to delete it. The operating system error is: "error_message". - AWSBDW013E
Unable to Launch job !1. - AWSBDW014E
Jobman found a mailbox record in the Courier.msg file in an unrecognizable format, and was unable to process it. - AWSBDW016E
Jobman was unable to end the following user job due to a system error: "job_name", #"job_number". The operating system error is: "system_error". - AWSBDW017E
Jobman cannot create a new session for the monitor daemon. The operating system error is: "system_error". - AWSBDW018E
Timeout on Courier. - AWSBDW020E
Error occurred opening stdin !1. - AWSBDW021E
Error occurred opening stdout !1. - AWSBDW022E
Error occurred opening stderr !1. - AWSBDW023E
A monitor process encountered an error while waiting for its child process to terminate. The operating system error is: "system_error". - AWSBDW024W
No Writers on Courier (Writers = !1). - AWSBDW026E
The file that jobman is trying to delete was expected to be a JCL file, but is not. - AWSBDW028E
Jobman encountered the following incorrect test condition when attempting to check an opens file dependency: "qualifier". The file being checked is the following: "file_name". - AWSBDW029E
Jobman is trying to end the following job: "job_name", but was unable to find it in the job table. - AWSBDW032E
Jobman is trying to perform an operation as root or Administrator which is not authorized. - AWSBDW033E
Jobman could not set the group access list for the user specified in the logon of the job. The operating system error is: "system_error". - AWSBDW034E
Jobman encountered an error processing the following command: "command" on the following file: "file_name". - AWSBDW036W
Jobman was unable to invoke the following method file: "method_file", because it was either not executable, unreadable or missing. - AWSBDW037E
Jobman cannot get the status of an external dependency because the timeout jm look specified in the localopts file has been exceeded. - AWSBDW038E
Jobman cannot resolve an external dependency because it cannot check the status of the following external job: "external_job". This is because the workstation where the job is running is not an X-agent. - AWSBDW039E
Jobman or jobmon could not resolve an external dependency on job "external_job". The operating system error is: "system_error". - AWSBDW040E
Jobman encountered a file descriptor problem while trying to resolve an external dependency. The operating system error is: "system_error". - AWSBDW041E
Jobman was unable to end the following user job: "job_name", #"job_number". This may happen when user kills jobs running on extended agents. - AWSBDW053E
Jobman was unable to open the stdlist file for either the job process or itself. The operating system error is: "system_error" - AWSBDW054E
Can not malloc environment array: !1 - AWSBDW055E
Can not malloc buffer for environment variables: !1 - AWSBDW057E
The job "job_name" was not launched for this reason: "error_message". - AWSBDW059E
Jobman cannot allocate sufficient memory to store its workstation table. - AWSBDW060W
Jobman was unable to add the following workstation: "workstation_name" to the workstation table, because the table is full. This is workstation record # "workstation_record_number". - AWSBDW061E
Jobman encountered an error trying to read workstation information from the Symphony file. - AWSBDW062E
Jobman was unable to invoke the following method file "method_file" for the extended agent. The operating system error is: "system_error". - AWSBDW063E
Jobman was unable to find the following workstation: "workstation_name" in the workstation table. - AWSBDW064E
A job that jobman is monitoring has returned the following unrecognizable message: "incorrect_message". The job identifier, monitor PID and method file are as follows: "job_name", #J"monitor_pid" using "method_file". - AWSBDW066E
The schedulr has asked jobman to run a task that is not supported on the targeted agent. The following method options file was used: "method_options_file". The job identifier and monitor PID are as follows: "job", #J"monitor_pid". - AWSBDW067E
The extended agent has returned an unrecognized state "invalid_state" for job "job", #J"monitor_pid". - AWSBDW068E
Jobman encountered a problem (getlogin failed) with the user name for a job. The operating system error is: "system_error" - AWSBDW069E
Jobman encountered a problem with the user name of the remote user that will launch a job on an extended agent. The operating system error is: "system_error" - AWSBDW070E
Jobman cannot start. It has tried to become a daemon, giving the following internal error: "error" and system error: "system_error". - AWSBDW071E
The following script or command name: "script_name" has exceeded the maximum number of characters allowed: "maximum_number". - AWSBDW072E
Jobman encountered an error when removing the following centralized script file: "file_name". The operating system error is: "error_text". - AWSBDW073E
Jobman encountered an error when changing the owner of the following centralized script file: "file_name". The operating system error is: "error_text". - AWSBDW074E
Jobman has exceeded the available memory while trying to allocate a buffer for the following centralized script file: "file_name". - AWSBDW075E
Jobman (UNIX) or jobmon (Windows) encountered an error opening the following centralized script file: "file_name". - AWSBDW076E
The content of the following centralized script file is too long: "file_name". - AWSBDW077E
The following centralized script file is empty: "file_name". - AWSBDW078W
The promotion value specified in the localopts file is greater than zero. Values that are greater than zero are not valid and are set to -1. - AWSBDW079E
Jobman could not run the job because the system call used to launch the job failed: Jobmon was unable to retrieve user information. - AWSBDW210W
The Realtime priority value specified in the localopts file is not supported. High priority will be used. - AWSBDW301E
Jobman was unable to successfully access a mailbox record in its Mailbox.msg file, Courier.msg, giving the following error type and number: "error_type" - "error_number". The problem was identified in the following source file: "source_file" and the function being performed is: "function_name". - AWSBDX - Jobtable access messages
This section lists jobtable access error and warning messages that might be issued. - AWSBDX001E
Jobman has found a problem with its internal job table. See the message help for details. - AWSBDX002E
You or jobman tried to perform an action on a job that is either not running or is not within jobman's internal job table. Probably the job has terminated. If it is still running, an internal error has occurred. The action that cannot be performed is the following: "action_number". - AWSBDX003E
Jobtable - Attempt to add duplicate entry !1. - AWSBDX004E
Jobman could not open the jobtable file. The operating system error is: "error_message". - AWSBDX005E
Jobman received the following operating system error while handling the jobtable file: "error_number". - AWSBDX006E
Jobtable - MPE system error !1. - AWSBDX007E
Jobman cannot add a new entry to the job table because the job does not have a valid job number. - AWSBDX008E
Jobman tried to perform the action "action_number" but the job table is not locked. This is an internal error. - AWSBDX009E
Jobman attempt to lock a file already locked. - AWSBDX010E
The file version is incorrect for this program version. - AWSBDY - Mailbox messages
This section lists mailbox error and warning messages that might be issued. - AWSBDY101E
Bad Mailbox record found. - AWSBDY102E
An internal error has occurred. The program cannot access the mailbox or ftbox common area in memory. The pointer to the mailbox common area is NULL or the area is not initialized. - AWSBDY118E
HCL Workload Automation encountered a nonexistent mailbox record type. The problem was encountered in the following source code file: "file_name" at line: "line_number". The call was mb_e_2_i_HDR() and the unexpected mailbox record type is as follows: "record_type". - AWSBDY119E
HCL Workload Automation received a mailbox record incompatible with the version of the product. The problem was encountered in the following source code file: "file_name" at line: "line_number". The call was mb_e_2_i() and the unexpected mailbox record type is as follows: "record_type". - AWSBDY122W
Mailbox cache temporarily disabled. - AWSBDY124W
The Mailbox.msg file in !1 is not read by Mailman. - AWSBDY125E
An error occurred reading the header of the Mailbox.msg file in !1. - AWSBDY126E
An error occurred opening the Mailbox.msg file in !1. - AWSBDZ - Fileaid messages
This section lists Fileaid error and warning messages that might be issued. - AWSBDZ001E
Record out of range. - AWSBDZ005E
The input was not valid. - AWSBDZ006E
No lists are possible for this file structure. - AWSBDZ007E
There are no children for this record type. - AWSBDZ008E
The file is not modifiable. - AWSBDZ011E
You cannot modify the selected item. - AWSBDZ012E
The value specified is not valid. - AWSBDZ019E
The jobtable is not accessible under MPE. - AWSBDZ026E
Unable to read the Symphony file. - AWSBDZ027E
No resources could be found. - AWSBDZ028E
No messages could be found. - AWSBDZ029E
No files could be found. - AWSBDZ030E
No string records could be found. - AWSBDZ031E
No calendars could be found. - AWSBDZ032E
No workstations could be found. - AWSBDZ033E
No Job records could be found in the header. - AWSBDZ034E
No job streams could be found. - AWSBDZ035E
An incorrect option was supplied. Valid options are a,c,f,g,j,m,r,s,'.'. - AWSBDZ036E
At String Record. - AWSBDZ037E
At Calendar Record. - AWSBDZ038E
At Purgeable Jobs Record. No list options. - AWSBDZ039E
At Message Record. - AWSBDZ040E
At Dependency Record. - AWSBDZ041E
At File Record. - AWSBDZ042E
At CPU Record. - AWSBDZ043E
No list options. - AWSBDZ047E
An error occurred when opening the file. - AWSBDZ048E
No record could be found. - AWSBDZ049E
An error occurred while opening the jobtable. error:!1 !2. - AWSBDZ050E
An error occurred while creating the file. Permission denied. Specify another path and filename, run as a different user with create permissions for the file, or add create permission for the file to this user. - AWSBDZ051E
Specify a valid option: J, D, or .. - AWSBDZ057E
No holders could be found. - AWSBDZ058E
No dependencies could be found. - AWSBDZ059E
No rerun jobs could be found. - AWSBEA - Report1 messages
This section lists Report1 error and warning messages that might be issued. - AWSBEA001E
Unable to open the mozart database. - AWSBEA002E
Unable to read from the mozart database. - AWSBEA003E
An error occurred while initializing the SORT routine. - AWSBEA004E
An error occurred in the SORTINPUT. - AWSBEA005E
An error occurred in the SORTOUTPUT. - AWSBEC - Report headers and subheaders messages
This section lists error and warning report headers and subheaders messages that might be issued. - AWSBEC110E
Cannot open file "file_name". - AWSBEC111E
An error occurred while writing file "file_name". - AWSBEC112E
An error occurred while reading file "file_name". - AWSBEC821E
The following database open error occurred: !1 - AWSBEC870E
The following database open error occurred: %s - AWSBEE - Parms messages
This section lists error and warning parms messages that might be issued. - AWSBEE001E
Parameter !1 does not exist. - AWSBEE002E
The following parameter name is not valid: !1. - AWSBEE003E
You cannot use the following parameter: !1. - AWSBEE007E
You do not have build permission for the parms -build command that creates and maintains the parameters database. - AWSBEE008E
A syntax error occurred. The parameter name exceeds the maximum length of "max_vartable" bytes. - AWSBEF - Symphony archiving messages
This section lists error and warning messages that might be issued by the Symphony archiving. - AWSBEF001E
Missing last archive run date. - AWSBEF002E
Archiver could not create a directory with the following path: !1. - AWSBEF004E
An error occurred while opening the Symphony file from schedlog !1. - AWSBEF005E
An error occurred reading workstation record !1 from the logged Symphony file !2. - AWSBEF006E
An error occurred reading job stream record !1 from the logged Symphony file !2. - AWSBEF007E
An error occurred reading job record !1 from the logged Symphony file !2. - AWSBEF009E
An error occurred while opening one or more output files. - AWSBEG - Ftbox messages
This section lists error and warning messages that might be issued by the routines that maintain the ftbox directory. - AWSBEG201E
The following directory could not be created: "directory_name". The following error was returned from the operating system: "error_code" - AWSBEG202E
Access rights to the following directory could not be set: "directory_name". The following error was returned from the operating system: "error_code" - AWSBEG203E
A change of ownership could not be made to the following directory: "directory_name". The following error was returned from the operating system: "error_code" - AWSBEH - Web library messages
This section lists error and warning messages that might be issued by the routines that use the Web library. - AWSBEH001E
The connection configuration file "file_name" containing the connection properties cannot be found. - AWSBEH002E
The target host computer is not defined in the connection configuration file or the supplied command parameters. - AWSBEH003E
The protocol is not defined in the connection configuration file or the supplied command parameters. - AWSBEH004E
The target host port is not defined in the connection configuration file or the supplied command parameters. - AWSBEH005E
The user is not defined in the connection configuration file or the supplied command parameters. - AWSBEH006E
The password is not defined in the connection configuration file or the supplied command parameters. - AWSBEH007W
The supplied protocol "protocol" is not valid. It must be http or https. - AWSBEH008E
The user options properties file "file_name" could not be opened or was not found. - AWSBEH009E
The connection configuration file "file_name" identified in the command by the -file keyword could not be opened or was not found. - AWSBEH010E
An internal error has occurred. A function has tried to initialize the HTTP libraries more than once. - AWSBEH011E
An error occurred while contacting the server "server_name" on port "port_number". - AWSBEH012E
The supplied file "file_name" could not be found or opened. - AWSBEH013E
An internal error has occurred. WebLib could not allocate memory for processing the supplied file. - AWSBEH014E
An error occurred while reading the supplied file "file_name". - AWSBEH015E
An internal error occurred while initializing the AXIS HTTP libraries. - AWSBEH016E
An error occurred while contacting the server using the AXIS HTTP libraries. - AWSBEH017E
An internal error has occurred "error" while using the AXIS HTTP libraries. - AWSBEH018E
An error occurred while setting the credentials for user ID "user". - AWSBEH019W
The format of the proxy server "proxy_server" and its port "port" is not valid. - AWSBEH021E
The user "user" is not authorized to access the server on host "host" using port "port". - AWSBEH022E
The server on host "host" cannot be contacted. - AWSBEH023E
Unable to establish communication with the server on host "host" using port "port". - AWSBEH024E
The connection with the server on host "host" has timed out. - AWSBEH025E
The server response cannot be understood. There is a probably a mismatch with language variables, codesets, codepages, or other configuration elements of the international communication environment. - AWSBEH026E
It was not possible to establish an SSL communication with the server on host: "host" using port "port" because of the following error: "error". - AWSBEH027E
The connection parameters were not specified completely in your useropts or localopts file. Correct the file, or submit the connection parameters as part of the command syntax. - AWSBEH028E
The SSL connection using GSKit (FIPS 140-2 mode active) with the server fails. - AWSBEH029E
The SSL connection using OpenSSL Toolkit with the server fails. - AWSBEH030E
The connection with the server fails. - AWSBEH100E
There is a syntax error in the connection parameters. - AWSBEH101E
An internal error occurred while initializing the WebLib HTTP libraries. - AWSBEH102E
No valid command was supplied. - AWSBEH103E
Too many commands have been supplied, or a command has been duplicated. - AWSBEH104E
The following HTTP communication failure has occurred: "HTTP_return_code". - AWSBEH105E
The following HTTP response failure was received from the server: "HTTP_return_code". - AWSBEH106E
There is a syntax error. The required value for keyword "keyword" is missing. - AWSBEH107E
There is a syntax error. The supplied date is not in the format specified in the useropts or localopts files. - AWSBEH108E
There is a syntax error. The format of the time in the date is incorrect. - AWSBEH109E
There is a syntax error. The time zone is not valid. - AWSBEH110E
There is a syntax error. A start or finish time in the format hhmm is required when you specify a time zone in the -from or -to options. - AWSBEH111E
The following internal error occurred while opening the Symphony file: "error". - AWSBEH112W
There is a syntax error. The -from parameter was ignored because you are trying to extend a plan. - AWSBEH113E
There is a syntax error. A keyword has been used more than once. - AWSBEH114E
There is a syntax error. The -to keyword has been specified, but also the -for or the -days keywords, which is not allowed. - AWSBEH115E
The file "file" does not exist or you do not have read access to the file. - AWSBEH116E
An error occurred while converting the globalopts option "globalopts_option" to the database global option "db_global_option". - AWSBEH118E
There is a syntax error. The time format for the -for value is not [h]hhmm. - AWSBEH144W
Unable to execute the Resync command because the Symphony file is not found. - AWSBEH145W
Unable to execute the Checksync command because the Symphony file is not found. - AWSBEI - Users program messages
This section lists error and warning users program messages that might be issued. - AWSBEI001E
User "user_name" does not exist. - AWSBEI002E
The file "file_name" is empty, or an error occurred during the conversion of the contents of the file to UNICODE. No user has been added to or updated in the local database. - AWSBEI003W
An internal error has occurred. Cannot open the audit log file. - AWSBEI007E
You are not authorized to run this command. - AWSBEI009E
An error has occurred. The user "user_name" has not been updated or added. - AWSBEI010E
Cannot open the file "file_name". Operating system error: "os_error". - AWSBEI011E
The Unicode (UTF-8) name of the workstation is too long to be stored. - AWSBEI012E
The Unicode (UTF-8) name of either the domain or the user is too long to be stored. - AWSBEI013E
The Unicode (UTF-8) password is too long to be stored. - AWSBEJ - Symphony check messages
This section lists error and warning messages that might be issued by Symphony check routines. - AWSBEJ010E
Error: Job stream record (#"recnum") has incorrect dependencies. - AWSBEJ011E
Error: Job record (#"recnum") has incorrect dependencies. - AWSBEJ012E
Error while reading record (#"recnum"): "reason" - AWSBEJ014E
Error: The job stream chain is corrupted. - AWSBEJ015E
Error: Record (#"recnum") is not a job stream record as expected. - AWSBEJ016E
Error: Record (#"recnum") is not a job record as expected. - AWSBHS - MVS method messages
This section lists error and warning messages that might be issued by the MVS method. - AWSBHS001E
Error: Unable to open connection to MVS gateway: !1 - AWSBHS002E
Error: Unable to start the MVS gateway: !1 - AWSBHS003E
Error: !1 - AWSBHS004E
Error: Cannot get reply from the MVS gateway: !1 - AWSBHS005E
Error: Cannot send request to MVS gateway: !1 - AWSBHS006E
Error: Could not allocate storage for communication - AWSBHS007E
Error: Missing argument for option !1 - AWSBHS008E
Error: Unknown option argument: !1 - AWSBHS009E
Error: Missing -t task option - AWSBHS010E
Error: Missing -c cpu,host,master option - AWSBHS011E
Error: Missing -n node option - AWSBHS012E
Error: Missing -p port option - AWSBHS013E
Error: Unsupported task: !1 - AWSBHS015E
Error: Mismatched TWS ID. Expected !1 got !2. - AWSBHS016E
Error: Missing response result code. Response: !1. - AWSBHS017E
Error: MAXTIME retries limit <!1> reached. - AWSBHT - Batchman messages
This section lists error and warning messages that might be issued by the batchman component. - AWSBHT001E
The job "job_name" in file "file_name" has failed with the error: "error_message" - AWSBHT002W
Job logs on differently than documentation indicates. - AWSBHT003E
Batchman is unable to allocate memory for its internal record table during initialization. - AWSBHT004E
Batchman has read a record in the message file which has the following destination workstation ("to_workstation") that cannot be found. The message originated at the following workstation: "from_workstation". - AWSBHT005E
Batchman has read a record in the message file which identifies a job which cannot be found in the Symphony file. - AWSBHT006E
Batchman has read a Job Terminate record in the message file for a job that is not in the execute state. - AWSBHT007W
Record type mismatch reading SYMPHONY file - AWSBHT008E
Batchman has read a record in the message file which has either an incorrect length, or the following unrecognized record type: "record_type". - AWSBHT009E
Batchman has found a non-valid dependency type in the Symphony file. - AWSBHT010E
Batchman has received a mailbox message that updates the state of a job, but the job cannot be found in the Symphony file. - AWSBHT011E
Batchman found corrupted job recovery information while it was attempting to determine the recovery action for a job that terminated with an ABEND state. - AWSBHT012E
The batchman internal job table or its extension area is full. - AWSBHT013E
Batchman has received a mailbox message that refers to the following job stream: "job_stream_name". However, the job stream does not exist in the Symphony file. - AWSBHT014E
Batchman has received a mailbox message that refers to the following job: "job_name". However, the job does not exist in the Symphony file. - AWSBHT015W
Batchman cannot release a job stream from its dependencies because the job stream is not in the holding state that is required to allow it to be updated. - AWSBHT016W
Batchman cannot release a job from its dependencies because the job is not in the holding state that is required to allow it to be updated. - AWSBHT017E
Batchman has received a mailbox message that refers to a job stream that cannot be found in the Symphony file. - AWSBHT018E
Batchman has received an event that refers to the following job that cannot be found in the Symphony file: "job_name". - AWSBHT019E
Batchman was unable to modify a job because it is not in the valid state to apply the modification. - AWSBHT020E
Batchman has received an event for a prompt that cannot be found in the Symphony file. - AWSBHT021E
Batchman has received an event to add a new job stream to the plan, but a job stream with that name already exists in the Symphony file. - AWSBHT022E
Batchman has received an event for a job stream or a job within a job stream, but the job stream cannot be found in the Symphony file. - AWSBHT023E
While responding to a submit schedule request, batchman has found a record in the message file which is not a job stream, job or dependency record. - AWSBHT024W
Batchman has received an end-event for a job stream, but the job stream is not in the correct status to receive an end-event. - AWSBHT025W
Batchman has received an end-event for a job, but the job is not in the correct status to receive an end-event. - AWSBHT026E
Batchman has received an event for the following resource, but the resource cannot be found in the Symphony file: "resource_name". - AWSBHT027W
Batchman has received an event to add a new job to a job stream, but a job with that name already exists in the job stream in the Symphony file. - AWSBHT028E
Batchman has received an event for a FILE dependency, but the dependency cannot be found in the Symphony file: - AWSBHT029E
Batchman was unable to allocate memory to hold the internal workstation table that contains the workstations for which batchman schedules jobs. The number of entries it wants to create is as follows: "table_entries". - AWSBHT038W
The internal workstation table used by batchman is full. Workstation record #"workstation_record_number" for "workstation_name", has been ignored. - AWSBHT044E
Batchman could not find the entry for the following resource: "resource_name" in the dependency list for the following job stream or job: "job_stream_or_job". - AWSBHT049E
Batchman could not find a job or job stream as a holder in the list of holders in the Symphony file resource record with the following record number: "record_number". - AWSBHT050E
An internal error has occurred. Batchman has received an event from a master domain manager, from which this event should not have been produced. - AWSBHT051W
The number of dependencies specified in the following resolve dependency record "resolve_dependency_record" exceeds the total dependencies defined in the Symphony file: "dependencies_in_symphony". The job is the following: "job_or_job_stream_name". - AWSBHT052W
Requested dependency type !1 is not equal to actual type of !2. - AWSBHT056E
Batchman was unable to add a dependency to a job stream or job, because the number of dependencies in the record is already equal to the maximum allowed (40). - AWSBHT057W
Batchman has found a non-valid run number in the Symphony file for the following record type: "record_type" and object: "object". - AWSBHT060W
CS record ignored !1 - AWSBHT061E
Batchman has received a mailbox record indicating that the following job has stopped unexpectedly: "job_name" ("job_number"). - AWSBHT069E
The following job stream is in the stuck state: "job_stream_name". - AWSBHT087E
Batchman has determined that jobman has failed with the following exit code: "exit_code". - AWSBHT089E
A resource cannot be allocated to a job or a job stream because the maximum number of resource holders (32) has been reached. - AWSBHT090E
Batchman could not start jobman. The following gives more details of the error: "error_text". - AWSBHT091E
Batchman could not open the Symphony file. The following gives more details of the error: "error_text". - AWSBHT092E
Batchman could not open the mailbox file Intercom.msg. The following gives more details of the error: "error_text". - AWSBHT093E
Batchman could not open the mailbox file Mailbox.msg. The following gives more details of the error: "error_text". - AWSBHT094E
Batchman could not open the mailbox file Courier.msg. The following gives more details of the error: "error_text" - AWSBHT095E
Batchman could not access the mailbox file Symphony.msg for reading or writing. The following gives more details of the error: "error_text" - AWSBHT096E
Batchman could not read from the mailbox file Intercom.msg. The following gives more details of the error: "error_text" - AWSBHT097E
Batchman could not write to the mailbox file Intercom.msg. The following gives more details of the error: "error_text" - AWSBHT098E
Batchman could not write to the mailbox file Courier.msg. The following gives more details of the error: "error_text" - AWSBHT099E
AAn internal error has occurred. Batchman could not write to the mailbox file Server.msg. The following error was generated: "error_text" - AWSBHT156E
Batchman could not open the mailbox file DeadMessage.msg. The following gives more details of the error: "error_message" - AWSBHT157E
Batchman could not read the mailbox file DeadMessage.msg. - AWSBHT158E
Batchman could not write to the mailbox file DeadMessage.msg. The message has been lost. - AWSBHT159E
Batchman could not write to the mailbox file DeadMessage.msg because the file is full. The message has been lost. - AWSBHT160E
The EvtLog message file is full, events will not be logged until a new Symphony is produced. Recovery with event reapply is no more possible until that time. - AWSBHT210E
Batchman encountered an error because the user name is not defined in the Symphony file. - AWSBHT212W
Batchman has determined a negative value for the run time for a job. The following error text contains useful information about the job: "error_text" - AWSBHT214E
Batchman could not create a new Sinfonia file during the network synchronization processing. - AWSBHT215E
Batchman could not open a new Sinfonia file during the network synchronization processing. - AWSBHT216E
Batchman could not access the Sinfonia file during the network synchronization processing. - AWSBHT217E
Batchman encountered an error while trying to allocate memory for its internal CPU table (calloc or realloc). - AWSBHT228W
The latest time that job stream "job_stream_name" can start has already passed. - AWSBHT230W
Warning: Dependency !1 not found in Symphony;ignored. - AWSBHT231W
A duplicated job termination (JT) record has been received for the following job: "job_name". - AWSBHT233W
An incorrect dependency has been detected for the following jobstream: "sched".Priority will be set to 0. - AWSBHT234W
An incorrect dependency has been detected for the following job: "job".Priority will be set to 0. - AWSBHT235E
An internal error has occurred. Batchman could not write to the mailbox file planbox.msg. The following error was generated: "error_text" - AWSBHT236E
An internal error has occurred. Batchman could not write to the mailbox file mirrorbox.msg. The following error was generated: "error_text" - AWSBHT237E
An internal error has occurred. Batchman is unable to extend the Symphony file and then it cannot manage the mailbox message queue. A possible cause is a full file system. - AWSBHU - Conman messages
This section lists error and warning messages that might be issued by the conman component. - 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". - 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". - 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" - AWSBHU004E
The job logon name you specified is not valid. - AWSBHU009E
Conman encountered a problem trying to read the Symphony file. The following gives more details of the error: "error_text" - 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". - AWSBHU016E
One of the values specified for a numeric argument is not numeric. - AWSBHU017E
A value specified for a range-limited numeric argument is below the minimum permitted value. The permitted range is from: "minimum" to "maximum". - AWSBHU018E
A value specified for a range-limited numeric argument is above the maximum permitted value. The permitted range is from: "minimum" to "maximum". - AWSBHU021E
The agent on workstation: "workstation_name" cannot be started because it has not got the latest Symphony file version. - AWSBHU022E
The time value specified as an argument is incorrect. It must be numeric, between 0000 and 2359. - AWSBHU023E
You have issued an opens job qualifier with incorrect syntax. - AWSBHU024E
The mozart directory cannot be accessed or is missing some files. - AWSBHU025E
Conman either cannot find the job stream in the Symphony file, or the specified workstation name is not correct. - AWSBHU028E
The recovery action is not correct. It must be one of the following: STOP, CONTINUE, RERUN. - 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. - AWSBHU032E
You have issued a rerun command that does not uniquely identify a workstation. - AWSBHU033E
You have supplied more instances of a dependency option than are permitted by the issued command. - AWSBHU034E
You have not supplied a mandatory selection argument (job, or job stream, for example). - AWSBHU035E
You have issued a command with a dependency keyword (follows, needs, opens, prompt), but the value associated with the keyword is not valid. - AWSBHU037E
Conman has stopped with the following internal error: Non-valid trap action. - AWSBHU038E
Conman cannot run the command because the command string has too many characters. - AWSBHU039E
You have issued a command containing an incorrect argument keyword. The acceptable keywords for this command are as follows: "keyword_list" - AWSBHU040E
You have issued a command containing an incorrect delimiter. The accepted delimiters are the following: "delimiters" - 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. - 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. - 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. - 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). - AWSBHU045E
You have issued the following command: "command " with one or more arguments, but this command does not have any 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". - AWSBHU047E
A command has been supplied without its required selector. - AWSBHU048E
A command has been supplied with an ambiguous selector. - AWSBHU049E
You have issued a command with a selector keyword, but the supplied selector keyword is not valid. - AWSBHU050E
You have issued a command with a selector keyword, but the supplied selector keyword is not valid for this command. - AWSBHU051E
You have issued a command with a valid selector keyword, but have omitted to identify the object. - 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. - 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). - AWSBHU054E
You have issued a show... command other than showjobs, and have used the argument "argument" without its associated ;deps argument. - 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. - 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. - AWSBHU058E
The command issued for workstation "workstation_name" cannot be performed, because the workstation is an extended agent, where the command is not supported. - AWSBHU059E
You have identified a file name that has a base name greater than "maximum_length" bytes. This file name is not permitted. - AWSBHU060E
You have issued a command that has attempted to modify or delete the EXTERNAL job stream. This is not permitted. - AWSBHU061E
The domain manager of this workstation cannot be found in the Symphony file. - AWSBHU062W
The MGR option is valid only on the local workstation. Ignoring it. - 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". - AWSBHU064E
The domain manager "new_manager" is not a fault-tolerant agent. - AWSBHU065E
The specified new domain manager is not full status. - AWSBHU066E
The domain you supplied to the switchmgr command is not in the Symphony file. - AWSBHU067E
A manager workstation has not been specified for the switchmgr command. - AWSBHU068E
The following workstation supplied to the switchmgr command is not in the Symphony file: "workstation_name". - AWSBHU069E
Too many parameters have been supplied to this switchmgr command. - AWSBHU070E
The following domain name could not be found in the Symphony file: "domain_name". - AWSBHU071E
An error was encountered accessing the following file: "file_name". The following gives more details of the error: "error" - AWSBHU072E
There are no objects that match the selection you have entered. - AWSBHU073E
The mozart database does not exist, or cannot be opened or accessed. The following gives more details of the error: "error_text". - AWSBHU075E
The following incorrect conman command has been used: "command". - AWSBHU076E
Conman cannot process the issued command. The following error occurred: "error_text"# - AWSBHU077E
The issued show command does not indicate the object or objects which you want the command to show. - 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". - AWSBHU079E
An internal error has occurred. CmdLink needs more workspace; it needs: "required_space", but only: "available_space" is available. - 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". - 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". - AWSBHU082E
Modification is not authorized. - AWSBHU083E
The issued command cannot be applied to the USERJOBS job stream. - AWSBHU084E
The issued command cannot be applied to the JOBS job stream. - AWSBHU085E
This job or job stream is not in the correct state to apply the issued command. - AWSBHU086E
You must be on the master to execute this command. - AWSBHU087E
The selected job stream has already been cancelled. - AWSBHU088E
You cannot rerun user jobs. - AWSBHU089E
This parameter is only valid when using the from parameter with the rerun command. - AWSBHU090E
The job indicated by the from parameter does not exist in the database. - AWSBHU091E
The alias or step name supplied for the job or job stream is not valid. - AWSBHU092E
This job or job stream has too many dependencies. - AWSBHU093E
The issued rerun command did not specify the step name to use after the ;step parameter. - 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". - AWSBHU095E
The job stream or job dependency "dependent_job_stream_or_job" was not found in the Symphony file. - AWSBHU096E
You have specified a range of values for a command qualifier that does not accept ranges. - AWSBHU097E
You have not specified a values for a command qualifier that requires one. - 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". - AWSBHU099E
The supplied path name exceeds the maximum size, which is: "maximum_size". - AWSBHU112E
The supplied job specification is not in the correct format. You can use only <workstation>#<job> or <job>. - AWSBHU114E
The supplied switchmgr command did not identify the domain, the new manager, or both. - 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". - 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". - 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". - 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. - AWSBHU121E
Conman could not identify the parent domain of the following workstation: "workstation_name". - AWSBHU122E
The supplied command includes both the options short and single, which are mutually exclusive. - AWSBHU123E
The supplied command includes the option single, which can only be used when a Job Number is supplied. - AWSBHU126E
A time zone has been specified in a time dependency, but time zone use has not been enabled for workstation: "workstation_name" - 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. - AWSBHU130E
The issued command cannot be used. It is not allowed by the centralized security option, which is enabled for this domain. - 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. - 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. - AWSBHU133E
You have supplied a return code condition expression that is longer than the maximum number of bytes permitted, which is: "number". - 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". - AWSBHU135E
You have supplied a return code condition expression that is enclosed in mismatched or missing quotes. - 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". - 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. - AWSBHU139E
The issued submit command includes a wait keyword, but you have not supplied the associated numeric wait value. - AWSBHU140E
The issued submit command includes a wait keyword, but the associated numeric wait value (seconds) is not between 0 and 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". - 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". - AWSBHU143E
The action associated with the onuntil attribute is not correct. It must be one of the following: suppr, cont, canc. - 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". - AWSBHU145E
There is a syntax error. The job stream ID can contain only alphanumeric characters. - AWSBHU146E
There is a syntax error. The job stream ID must be between 1 and 16 bytes long. - AWSBHU147E
The keywords "keyword_1" and "keyword_2" are mutually exclusive. You cannot supply both of them. - AWSBHU148E
The keyword "keyword" cannot be used because the Symphony file was created by a previous version of HCL Workload Automation. - AWSBHU149E
The job stream or job dependency "dependent_job_stream_or_job" with the specified schedule time was not found in the Symphony file. - AWSBHU150W
An internal error has occurred.The program is unable to initialize the GSKit libraries. - AWSBHU151E
The supplied date is not valid or is not in the correct format. The correct format is "localopts_date_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. - AWSBHU153E
The keyword "keyword_1" can only be supplied if the keyword "keyword_2" is specified. - AWSBHU154E
Either the nocheck argument or the schedid argument have been supplied without the required job stream ID. - AWSBHU155E
You have submitted a command to be scheduled as a job (submit docommand) but have not included the command. - AWSBHU156E
The workstation you specified is already the event processor. - AWSBHU157E
You have issued a command containing at least one incorrect argument keyword. - 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. - AWSBHU159E
The command issued for workstation "workstation_name" cannot be performed, because the workstation is broker agent, where the command is not supported. - AWSBHU160E
The command issued for workstation "workstation_name" cannot be performed, because of the following error: "error". - 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. - AWSBHU162E
"file_name" file cannot be moved on workstation "workstation_name" because it is being used by another process. - AWSBHU163E
An error has occurred while launching the script moveFTATargetFiles on workstation "workstation_name". - AWSBHU164E
The script moveFTATargetFiles is missing on workstation "workstation_name". - AWSBHU166E
A file cannot be removed from TWShome/pobox directory on workstation "workstation_name" because it is being used by another process. - AWSBHU168E
The agent on workstation "workstation_name" cannot be reset because it is still active. - AWSBHU169E
The number of hours must be an integer value between 0 and 500. - 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. - 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. - 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. - AWSBHU173E
Conman command is unable to start a new process. Your HCL Workload Automation license expired "exp_date". - 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. - AWSBHU175E
The selected job stream has already been suppressed. - 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. - AWSBHU181E
The conditional dependency expression specified cannot be validated by conman. - AWSBHU182E
The output condition expression specified cannot be validated by conman. - AWSBHU183E
The conditional dependency specified "conditional_dependency" does not exist in the Symphony file. - AWSBHU184W
The "keyword" variable value is longer than the maximum number of bytes and will be truncated. - AWSBHU185E
The logon or streamlogon value is empty or invalid. - AWSBHU186E
The docommand or script keyword is not compatible with the type of the job. Use this keyword only for native jobs. - AWSBHU187E
The supplied logon name exceeds the maximum size, which is: "maximum_size". - AWSBHU188E
The command or script name is empty or invalid. - AWSBHU189E
You have issued a command that has attempted to edit a job into an EXTERNAL job stream. This is not permitted. - AWSBHU410E
The workstation name parameter has not been specified for the "command_name" command. - AWSBHU411E
Wild cards are not permitted in the workstation name parameter of the "command_name" command. - AWSBHU412E
Too many parameters have been supplied to the "command_name" command. - 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. - AWSBHU504E
You have issued a command with a time-related dependency, but have omitted the keyword day[s]. - AWSBHU508E
You do not have access to this file or database object. - AWSBHU509E
The requested file cannot be found. - AWSBHU510E
The following job already exists: "workstation"#"job_stream"."job". Use the rerun command or supply an alias with the submit command. - 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. - AWSBHU513E
The following job stream already exists: "job_stream_name". Supply an alias with the submit command. - AWSBHU516E
You have not supplied a valid alias of the job you are trying to resubmit. - AWSBHU517E
The required information cannot be displayed. - 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. - 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. - AWSBHU523E
You have issued a link or an unlink command on a standalone workstation (on which mailman is not running). - AWSBHU524E
The issued command incorrectly ends with a delimiter. - AWSBHU526E
The following internal error occurred when conman attempted to display a JCL file: "error_message". - AWSBHU527E
A file-descriptor or disk-space error occurred when conman attempted to open a JCL file for display. - AWSBHU528E
A file-descriptor or disk-space error occurred when conman attempted to display a JCL file. - AWSBHU529E
The following error occurred while conman was displaying a JCL file: "error_number". - AWSBHU530E
The following error occurred while conman was writing a work file when displaying a JCL file: "error_number". - AWSBHU531E
Conman was unable to access the mozart database or was unable to find a parameter within the database. - AWSBHU532E
You have either entered too many parameters, or the expansion of the parameters you have entered has exceeded the internal parameter buffer. - 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. - AWSBHU534E
The workstation selected for this job is not a workstation but a workstation class. - AWSBHU535E
The following workstation is not in the Symphony file: "workstation_name". - AWSBHU536E
The following domain is empty: "domain_name". - 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. - 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": - AWSBHU540E
Conman cannot find any domains in the Symphony file. - 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". - AWSBHU542E
Conman has verified that the versions of the Symphony and Database files (Mastsked version) are different. - AWSBHU543E
You have supplied the interactive qualifier keyword to the submit jobs command, which is not valid. - AWSBHU544E
The supplied path name is longer than the maximum allowed: "maximum_bytes". - AWSBHU545E
You have supplied a path name that does not match the workstation type: "workstation_type". - AWSBHU546E
You have supplied either a tz or a timezone keyword but did not supply the time zone name. - AWSBHU547E
You have supplied a time zone name that is longer than 40 bytes. - AWSBHU548E
You have supplied a time zone name that is not valid. - AWSBHU549W
There is a logic error in the time-related dependencies. The until time occurs before the at time. - AWSBHU550W
There is a logic error in the time-related dependencies. The dependency is circular. - AWSBHU551E
You are trying to add the same dependency twice. - AWSBHU553E
An error has occurred while starting an internal component (clagent). - AWSBHU556E
The following error occurred while opening the clbox.msg file: "error_text". - AWSBHU557W
There is a logic error in the time-related dependencies. The deadline time occurs before the at or until time. - AWSBHU558W
There is a syntax error in the time-related dependencies. The onuntil keyword was specified but the until time was not supplied. - 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". - AWSBHU560E
The command startmon cannot be performed, because 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. - 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. - AWSBHU600E
There is a logic error in the follows dependencies. The dependency "circular_dep" is circular. - 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" - AWSBHU607E
The value specified for the -protocol connection parameter is not valid. It must be http or https. - 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. - AWSBHU610E
The credentials to connect to the remote server have not been specified. - AWSBHU611W
Conman could not initialize the HTTP or HTTPS connection. - AWSBHU612E
The port specified by the -port connection parameter is not numeric. - AWSBHU613E
There are insufficient units of resource "resource" available. The job requires "required_resources" units but only "available_resources" are available. - AWSBHU614E
No job stream was submitted to batchman. - AWSBHU615E
The submitted job refers to a recovery job which could not be found in the database. - AWSBHU616E
More than one job stream matches your selection.Uniquely identify the job stream by specifying its ID or schedule time. - AWSBHU618E
The bulk_discovery was not performed because no configuration file was found. - AWSBHU619E
The following error occurred obtaining the monitoring configuration file for workstation "workstation_name": "error_message". - AWSBHU624W
The application server on workstation "workstation_name" is already stopped. - AWSBHU625W
The option WAIT is not supported for remote workstations. It is ignored. - AWSBHU626W
The application server is not installed for the local workstation. - 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. - AWSBHU631E
The command issued for workstation "workstation_name" cannot be performed, because the workstation is a standard agent, where the command is not supported. - AWSBHU632E
The command issued for workstation "workstation_name" cannot be performed, because the command is not supported. - AWSBHU633W
The event processor workstation is set to ignore in the production plan. - AWSBHU634E
The command "command_name" cannot be performed, because the event processor workstation is set to ignore in the production plan. - 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. - AWSBHU636E
The Workload Service Assurance feature is not enabled. - AWSBHU638W
The dynamic workload broker application on workstation "workstation_name" is already stopped. - AWSBHU639W
The dynamic workload broker application is not installed on the local workstation. - AWSBHU640E
The submitted command cannot be performed. The error is: "error_msg" - AWSBHU700E
There is a syntax error. A job name, file name or keyword is missing in the submitted command. - AWSBHU701E
There is a syntax error. The submitted command appears to contain extra or duplicated characters, or unmatched brackets. - 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. - 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. - 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. - 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. - AWSBHU711E
There is a syntax error. The submitted command has a job as its object but the job name has not been supplied. - AWSBHU712E
There is a syntax error. The prompt name must be between 1 and 8 bytes long. - AWSBHU713E
There is a syntax error. The prompt name must start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores. - 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 - AWSBHU716E
There is a syntax error. The resource name must start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores. - AWSBHU719E
There is a syntax error. You cannot specify a priority higher that 99 (use hi (= 100), or go (= 101) instead. - 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 (). - 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. - 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. - AWSBHU726E
There is a syntax error in the specification of a network dependency. The Network ID has not been specified. - 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. - 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. - AWSBHU729E
There is a syntax error. The domain name must be between 1 and 16 bytes long. - AWSBHU730E
There is a syntax error. The domain name must immediately be followed by a 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. - 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. - 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. - AWSBHU737E
Conman encountered a system error when attempting to retrieve either the current input mode or the current output mode of the console. - AWSBHU738E
Conman encountered a system error when attempting to set either the console input mode or the console output mode. - AWSBHU739E
The supplied user is not in the Symphony file. - AWSBHU740E
The new password and the confirmation password do not match. - AWSBHU741E
Conman is unable to open the audit log file. - AWSBHU743E
There is a syntax error in the name. It must be between 1 and 16 bytes. - AWSBHU744E
There is a syntax error. The job stream name must be between 1 and 16 bytes. - AWSBHU745E
There is a syntax error. The job name must be between 1 and 40 bytes. - 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. - AWSBHU747E
There is a syntax error. The job alias name must be between 1 and 40 bytes. - AWSBHU748E
There is a syntax error. The job stream alias name must be between 1 and 16 bytes. - 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. - AWSBHV - Stageman messages
This section lists error and warning messages that might be issued by the stageman component. - AWSBHV001E
An unspecified error was encountered building the following message file "message_file" - AWSBHV002E
Unexpected error creating new SYMPHONY - AWSBHV003E
Unable to open CROSSREF help file - AWSBHV004E
An internal error has occurred. Stageman has found an incorrect record in the Symphony file. Stageman expected record number "record_number" to be of type "record_type", but it was not. - AWSBHV009E
Fatal error copying SYMPHONY to SINFONIA. - AWSBHV011E
Error occurred while switching managers in domain !1 from !2 to !3. - AWSBHV019E
There is not enough memory to run stageman. - AWSBHV020E
Stageman has exceeded the internal limit of 10 duplicate carry forward job stream instances. - AWSBHV021E
An internal error has occurred. Stageman has encountered an error while reading a record from the Symphony file. - AWSBHV022E
An internal error has occurred. Stageman has encountered a record of an unknown type while creating the Symphony file. - AWSBHV023E
The number of carryforward job streams exceeds the maximum allowed by the Symphony file. - AWSBHV024E
An internal error has occurred. Stageman has encountered a record from the old Symphony file that is neither a job stream nor a job record. Index: "sym_rec_array_index", type "record_type" - AWSBHV026E
The old Symphony file cannot be renamed to the following file name: "file_name" - AWSBHV027E
The old Symphony file cannot be saved as the following file name: "file_name" - AWSBHV028E
The new Symphony file cannot be renamed to the following file name: "file_name". - AWSBHV029E
The new Symphony file cannot be saved. - AWSBHV031W
User is not creator of !1, must logon as !1 - AWSBHV032E
Multiple runs of Stageman, recompile new Symphony first - AWSBHV034W
The following job has dependencies not carried forward: "workstation_name"#"job_name". - AWSBHV035W
The following job stream has dependencies not carried forward: "job_stream_name". - AWSBHV037W
The following job stream or job is in the adding state, and has not been carried forward: "workstation"#"job_stream_or_job". - AWSBHV038E
Stageman has been unable to get exclusive access to the Symphony file. You need to shutdown the HCL Workload Automation processes. - AWSBHV039W
No carry job states are specified in the global options. The default behavior of allowing all states has been used. - AWSBHV040W
Only jobs in the following states are carried forward: "job_states", as defined in the global options (carry job states). - AWSBHV041E
Error accessing mozart: !1 - AWSBHV042E
Error accessing Straus: !1 - AWSBHV043E
Stageman cannot create the new Symphony file because the settings in the global options or the localopts file indicate that this workstation is not the master domain manager. - AWSBHV044E
Stageman is unable to open the mailbox file Mailbox.msg. The following operating system error message was given: "error_number". - AWSBHV045E
An error occurred while opening the following file: "file_name". The following gives more details of the error: "error_text". - AWSBHV046E
An error occurred while writing the Symphony file. The following gives more details of the error: "error_text". - AWSBHV047W
The following job stream: "workstation"#"job_stream"was carried forward, even though its workstation is not present in the Symphony file. - AWSBHV048W
An invalid dependency has been detected for the following job stream: "workstation"#"job_stream".The priority has been set to 0. - AWSBHV049W
An invalid dependency has been detected for the following job: "workstation"#"job_stream"."job".The priority has been set to 0. - AWSBHV065E
In the options for stageman there is an option that has a required argument, but that argument has not been supplied. The option in question is as follows: "option". - AWSBHV066E
The following argument: "argument" is not valid for the "option" option; perhaps it has been typed incorrectly. - AWSBHV067E
The following option is not a valid option for this command: "option"; maybe it has been typed incorrectly. - AWSBHV068W
Stageman has been invoked with the "option" option, but other options or arguments have also been supplied. To use this option supply it without other options or arguments. - AWSBHV069W
The following logfile name begins with -: "log_file_name" - AWSBHV070E
Stageman has been submitted with both the -log and -nolog options, which are mutually exclusive. - AWSBHV073W
Globalopts file parsed only. No carryforward done. - AWSBHV074E
The previous Symphony file is expanded but the Symnew file is in non-expanded mode. They cannot be merged to form the new Symphony file. - AWSBHV076E
Unable to open the audit log. - AWSBHV080E
Stageman is trying to access a record in the old Symphony file which has a record number higher than the final record in the file. - AWSBHV081W
The pending predecessor "workstation_name"#"job_stream_name" has not been found in the new Production Plan as expected. The pending predecessor is marked as an orphan predecessor, which must be released or replaced before the job or job stream in which it was defined can be run. - AWSBHV082E
The previous Symphony file and the Symnew file have the same run number. They cannot be merged to form the new Symphony file. - AWSBHV083W
The job stream: "workstation"#"job_stream" has a conditional dependency on a predecessor that is not more in the plan.The priority has been set to 0. - AWSBHV084W
The job: "workstation"#"job_stream"."job" has a conditional dependency on a predecessor that is not more in the plan.The priority has been set to 0. - AWSBHW - Object parsing messages
This section lists object parsing error and warning messages that might be issued. - AWSBHW001E
A job name, file name or keyword is missing in the submitted command. - AWSBHW002E
The submitted command appears to contain extra or duplicated characters. - AWSBHW003E
There is a syntax error in the name. It must be between 1 and 16 bytes. - AWSBHW004E
There is a syntax error in the name. It must start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores. - AWSBHW005E
The delimiter of cpu name is a #. - AWSBHW006E
There is a syntax error in the workstation name. The # symbol was found more than once. - AWSBHW007E
There is a syntax error. The job stream name must be between 1 and 16 bytes. - AWSBHW008E
There is a syntax error. The job stream name must start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores. - AWSBHW009E
The delimiter of the schedule name is a period . - AWSBHW010E
The job name is either null, or longer than the maximum length of 40 bytes. - AWSBHW011E
There is a syntax error. The job name must start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores. - AWSBHW012E
There is a syntax error. The command has a job as its object but the job name has not been supplied. - AWSBHW013E
There is a syntax error. The prompt name must be between 1 and 8 bytes long. - AWSBHW014E
There is a syntax error. The prompt name must start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores. - AWSBHW015E
Prompt name or message number not supplied. - AWSBHW016E
There is a syntax error. The resource name must be between 1 and 8 bytes long. - AWSBHW017E
There is a syntax error. The resource name must start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores. - AWSBHW018W
Priority is either HI, GO, or 0-99. - AWSBHW019W
There is a syntax error. Priority must be a numeric value from 0 to 99, hi (= 100), or go (= 101). - AWSBHW020E
There is a syntax error. You cannot specify a priority higher that 99 (use hi (= 100), or go (= 101) instead. - AWSBHW021E
User domain length incorrect - AWSBHW022E
There is a syntax error. The supplied user name is not valid. The name can contain up to 47 bytes. If the name contains special characters the full name must be enclosed in quotes (). - AWSBHW023E
Duplicate user name given. - AWSBHW038E
There is a syntax error. The calendar name must be between 1 and 8 bytes long. It must also start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores. - AWSBHW039E
There is a syntax error. The parameter name must be between 1 and 8 bytes long. It must start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores. - AWSBHW040E
There is a syntax error. The prompt name must be between 1 and 8 bytes long. It must start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores. - AWSBHW041E
There is a syntax error. The date is not valid. - AWSBHW045E
There is a syntax error. You cannot specify both dates in a valid in argument using the @ wildcard. - AWSBHW046E
There is a syntax error. The required workstation name is missing. Specify a workstation name or remove the workstation delimiter. - AWSBHW047E
There is a syntax error. The event rule name must start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores. - AWSBHW048E
A syntax error occurred. The variable table name must not exceed 80 bytes. It must start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores. - AWSBHW049E
A syntax error occurred. The variable name must not exceed 16 bytes. It must start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores. - AWSBHW050E
A syntax error occurred. The character . is duplicated in the variable. - AWSBHW051E
A syntax error occurred. The value specified for the variable must start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores. - AWSBHW052E
There is a syntax error. The run cycle group name is not valid. It must be between 1 and 40 bytes long, start with an alphabetical character, and contain only alphanumeric characters, dashes, and underscores. - AWSBHW053E
There is a syntax error. The batch application name is not valid. It must be between 1 and 80 bytes long, start with an alphabetical character, and contain only alphanumeric characters, dashes, and underscores. - AWSBHW054E
There is a syntax error. The security domain name must be between 1 and 50 bytes long. It must also start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores. - AWSBHW055E
There is a syntax error. The security role name must be between 1 and 50 bytes long. It must also start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores. - AWSBHW057E
There is a syntax error. The folder name must be between 1 and 900 bytes long. It can contain alphanumeric characters, dashes, underscores, dots, slashes and backslashes. - AWSBHW058E
There is a syntax error. The folder name is incorrect: spaces are not supported before or after the path separator. - AWSBHW059E
There is a syntax error. The folder name is incorrect: wild cards are not permitted in the folder name. - AWSBHW060E
There is a syntax error. The folder name is incorrect: unable to process the path. - AWSBHX - Logman messages
This section lists error and warning messages that might be issued by logman. - AWSBHX011W
The job has negative elapsed time. Check the time parameters. - AWSBHX021E
An error occurred opening the temporary file "file_name". - AWSBHX022E
An internal error occurred while initializing the HTTP communication. The library returned this error "error_message". - AWSBHX023E
An internal error occurred while sending data to the server. The error message is "error_message". - AWSBHX024E
An internal error has occurred. The server has returned an error code. RC="server_return_code" - AWSBHX027W
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. - AWSBHX032W
The job with Workstation: "workstation" Job Name: "job_name" has a null started date. For this reason, it doesn't appear in any collected statistics. - AWSBHX033W
The count of jobs cannot be performed on the current production Symphony file. - AWSBHZ - Scheduler messages
This section lists error and warning messages that might be issued by the scheduler component. - AWSBHZ001E
Schedulr cannot be run on this workstation, because the settings in the global options or the localopts file indicate that this workstation is not the master domain manager. - AWSBHZ002E
There is not enough memory available to run schedulr. - AWSBHZ003W
The submitted job stream has not been found or the job stream name is too long. - AWSBHZ008E
Schedulr was unable to open the prodsked file for the following reason: "error_message". - AWSBHZ009E
You have supplied a date with the -date option, but the supplied date is not in the correct format. - AWSBHZ010E
Schedulr has encountered the following error when trying to find a job stream in the mastsked database: "error_text" - AWSBHZ011E
Schedulr encountered the following error while checking to see if a date is defined for a particular calendar in the calendars database: "error_text". - AWSBHZ012E
Schedulr encountered the following error while searching for a specific calendar in the calendars database: "error_text". - AWSBHZ013E
Schedulr encountered the following error while reading a job stream from the mastsked database: "error_message". - AWSBHZ014E
Schedulr encountered the following error while reading dates from the calendars database: "error_message". - AWSBHZ015E
Schedulr encountered the following error while trying to lock the mastsked or job.sched databases: "error_message" - AWSBHZ016E
An internal error has occurred. While processing the mastsked database, schedulr was unable to add a job stream dependency to the internal table used by the resolve dependencies functions. - AWSBHZ017E
An internal error has occurred. Schedulr was unable to add a job stream dependency to the internal table used by the resolve dependencies functions. - AWSBHZ023E
Schedulr encountered an error parsing the contents of the job streams in the mozart database. - AWSBHZ024E
Schedulr has encountered the following error while trying to initialize the Security file: "error_message". - AWSBHZ025E
The user that launched schedulr does not have the correct permissions for the schedulr actions. - AWSBHZ029E
Schedulr encountered the following error while trying to lock the calendars database: "error_message". - AWSBHZ030E
Schedulr is unable to find the "calendar" calendar specified in the following job stream: "workstation_name"#"job_stream". - AWSBIA - Composer messages
This section lists error and warning messages that might be issued by the composer component. - AWSBIA002E
The identifier "identifier" is required at this point,but has not been supplied. - AWSBIA003E
A parameter or identifier has been supplied where it is not required. - AWSBIA004E
The delimiter "delimiter" is required at this point, but has not been supplied. - AWSBIA005E
Expected a !1 here. - AWSBIA006E
Error on database access. - AWSBIA007E
Security error. - AWSBIA008E
The supplied job stream !1#!2 could not be found. - AWSBIA009E
Error opening database. - AWSBIA010E
Autodoc not allowed for this job. - AWSBIA014E
Someone else has changed schedule !1#!2. No update done. - AWSBIA017E
An internal error has occurred. Out of memory trying to allocate "internal_storage_item". - AWSBIA018E
Job "job_identifier" is already present in the job stream. - AWSBIA019E
For job stream !1#!2: errors !3, warnings !4. - AWSBIA020E
Mastsked not updated. - AWSBIA021E
Job "job_name" does not exist in job stream "workstation"#"job_stream_name". - AWSBIA022E
A file system error "error_message"occurred building the temporary file "temporary_file_name". - AWSBIA023E
Job !1#!2 not found in job master. - AWSBIA024E
Job master changed while trying to update job !1#!2. Update aborted. - AWSBIA030E
An error has occurred opening the redirected output file "file_name" identified by the MAESTROLP variable. - AWSBIA031E
An error has occurred writing the redirected output file "file_name" identified by the MAESTROLP variable. - AWSBIA032E
Error reading schedule. - AWSBIA034E
No job streams found in !1#!2 - AWSBIA037E
The only keyword allowed at this point is ;offline. - AWSBIA038E
No qualifying CPU's were found in !1. - AWSBIA043E
Validation for object "object_ID": errors: "error_count"; warnings "warning_count". - AWSBIA044W
Cpudata not updated. - AWSBIA045E
Error accessing cpudata. - AWSBIA046E
Error opening cpudata. - AWSBIA047E
An error occurred while accessing the definition file "file_name". - AWSBIA057E
No resources were found. - AWSBIA060E
Error modifying resources. - AWSBIA065E
No prompts were found. - AWSBIA068E
No prompts found in the database. - AWSBIA076E
No calendars found in the database. - AWSBIA081E
No parms were found. - AWSBIA084E
No parms found in the database. - AWSBIA085E
Circular dependency for !1#!2 and !3#!4. - AWSBIA086E
!1 is not a definition file. - AWSBIA087E
There is a syntax error in the command. - AWSBIA088E
An internal error "error" has occurred while trying to resolve dependencies. - AWSBIA089E
The keyword "keyword" was expected at this point. - AWSBIA092E
Resource !1#!2 doesn't exist. - AWSBIA093E
Prompt !1 doesn't exist. - AWSBIA094E
One of these keywords: !1 was expected at this point.# - AWSBIA095E
Schedule already exists. - AWSBIA096E
Cpu definition already exists. - AWSBIA097E
A file system error "error_message"occurred writing the temporary file "temporary_file_name". - AWSBIA098E
A file system error "error_message"occurred closing the temporary file "temporary_file_name". - AWSBIA100E
CPU !1 does not exist in cpudata: !2 - AWSBIA101E
Only SCHEDULE or CPU can be specified here. - AWSBIA105E
A file system error "file_system_error" has occurred opening the script or jcl file "file_name". - AWSBIA106W
The job stream definition has one or more warnings. - AWSBIA107W
The workstation definition has one or more warnings. - AWSBIA109E
Calendar !1 is not in the calendars database. - AWSBIA110E
You are not authorized to access schedule !1#!2. - AWSBIA111E
You are not authorized to access calendar !1. - AWSBIA112E
You are not authorized to access parm !1 on this cpu. - AWSBIA113E
You are not authorized to access resource !1#!2. - AWSBIA114E
You are not authorized to access cpu !1. - AWSBIA115E
You are not authorized to access prompt !1. - AWSBIA116W
Recovery job !3#!4 not found for job !1#!2. - AWSBIA117W
Job is hosted by cpu !4, resource !1#!2 is hosted by cpu !3. - AWSBIA118W
Schedule is hosted by cpu !4, resource !1#!2 is hosted by cpu !3. - AWSBIA119E
Error, schedule not updated. - AWSBIA120W
The host keyword has been supplied for the definition of a workstation of type fta, but is not required. It has been ignored. - AWSBIA121W
Order of interleaved dependencies will be lost when sched is written. - AWSBIA122W
Autodoc for !1 will be removed when schedule is written to mastsked. - AWSBIA123W
Autodoc for !1#!2 will be removed when schedule is written to mastsked. - AWSBIA124W
Dependency !1 does not exist in schedule !2#!3. - AWSBIA125W
The host cpu !1 is not a domain manager or the master. - AWSBIA126W
The domain name !1 is already used and managed by another workstation. - AWSBIA127W
The domain manager workstation !1 is not defined as an FTA. - AWSBIA128W
The domain manager workstation !1 must be in the same domain. - AWSBIA129W
The parent domain !1 not found. - AWSBIA130W
The parent domain !1 is not defined as a DOMAIN definition. - AWSBIA131E
!1 is reserved for the master domain name. - AWSBIA138E
You cannot specify both the domain and the host keywords for a standard agent or broker workstation. Use only one or the other. - AWSBIA139E
For a standard agent or broker workstation you must specify a domain. - AWSBIA140E
For an extended agent you must specify the host and the access method. - AWSBIA141W
The master domain has a parent: !1. It must have no parent domain. - AWSBIA142E
Domain !1 not found. - AWSBIA143W
!1 is not defined as a domain. - AWSBIA144E
Error: Incompatible database files, use dbexpand to update databases. - AWSBIA145W
Access method !1 does not exist on your system! - AWSBIA146W
A loop was found in the domain definition. - AWSBIA147E
The "first_time_zone_definition" differs from "second_time_zone_definition" for "job_or_job_stream". A time zone need be specified just once, or all instances of it must be equal. - AWSBIA148W
The until time is earlier than the at time for !1. Check the time definitions and ensure that this is what you intended. - AWSBIA149E
Time zones are not enabled on workstation !1. - AWSBIA150W
Domain manager !1 is a manager of another domain - AWSBIA151W
The deadline is earlier than the at time for !1. - AWSBIA152W
The deadline is earlier than the until time for !1. - AWSBIA153W
You must specify a domain when the host is $MANAGER. - AWSBIA198E
The domain definition already exists. - AWSBIA199E
The workstation class definition already exists. - AWSBIA201E
You are not authorized to access job !1#!2. - AWSBIA203E
No qualifying jobs were found in !1. - AWSBIA204W
For !1, errors !2, warnings !3. - AWSBIA211E
Job !1#!2 already exists. - AWSBIA213W
The job definition has warnings. - AWSBIA214E
Error, job not updated. - AWSBIA215E
Job Master not updated. - AWSBIA221E
Invalid composer command: !1 - AWSBIA222E
Modify command is not valid in gui mode. - AWSBIA223E
New command is not valid in gui mode. - AWSBIA224E
Edit command is not valid in gui mode. - AWSBIA225W
Workstation "workstation" is defined as a workstation class. - AWSBIA226W
Workstation "workstation" is not the master domain manager. The parameters are expanded from the master domain manager. - AWSBIA227E
The extended agent, standard agent or broker workstation "workstation" cannot host itself. - AWSBIA228E
!1 already exists and its type does not match what is being created. - AWSBIA229E
The master domain manager "workstation" is managing the domain "domain" as specified in the global options. - AWSBIA230E
The domain "domain" cannot be included in a cpuclass definition. - AWSBIA231E
The !1 entry type is unknown and cannot be included in a cpuclass definition - AWSBIA250E
No qualifying users were found in !1. - AWSBIA256E
Userdata not updated. - AWSBIA257E
Error accessing Userdata. - AWSBIA258E
Error opening Userdata. - AWSBIA264E
User definition already exists. - AWSBIA265E
User !1 does not exist in userdata: !2. - AWSBIA267W
The user definition has warnings. - AWSBIA268E
You are not authorized to access user !1. - AWSBIA269E
Error: !1 - AWSBIA270E
Command line arguments too long. - AWSBIA271E
Unexpected keyword before or at caret position. - AWSBIA272W
The specified tcpaddr value "TCP/IP_port" is not in the range 1 to 65535. The following value of !2 is used instead, calculated as the modulus of the input value divided by 65536. - AWSBIA273E
The offset value !1 is not in the range -32767 to 32767. - AWSBIA274E
Problems found while opening or acquiring the ShortID file - AWSBIA276W
The short ID is not generated for job names shorter than !1 bytes. - AWSBIA277E
Problems retrieving the ShortID Value from file - AWSBIA278E
Error using cpuclass !1 on a job stream whose workstations are !2 - AWSBIA279W
The Job !1 is for workstation !2 with Ignore State - AWSBIA280E
There is an error in the connection parameters for composer. The port specified by the -port connection parameter is not numeric. - AWSBIA281E
The composer command line client cannot connect to its server. The value specified for the -protocol connection parameter is not valid. It must be http or https. - AWSBIA282E
The composer command line client cannot connect to its server. 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. - AWSBIA283E
An internal error has occurred. Composer cannot open the temporary file "temporary_file". - AWSBIA284E
An internal error has occurred. Composer cannot open the temporary file "temporary_file" for writing. - AWSBIA285E
An internal error has occurred. Composer cannot open the temporary file "temporary_file" for reading. - AWSBIA286E
Total errors: "error_count". - AWSBIA287W
Total warnings: "warning_count". - AWSBIA293E
An internal error has occurred. Composer was not able to initialize the HTTP or HTTPS connection. - AWSBIA294E
An internal error has occurred. The composer command line server could not authenticate the client. - AWSBIA297E
The job stream, or the workstation on which it runs, cannot be renamed because another job stream already exists with the supplied name. Two job streams can only have the same name if one has been created, not renamed, as a version of the other (with different valid-from dates). - AWSBIA298E
If you want to rename a job, the associated workstation and job stream cannot be renamed in the same action. - AWSBIA301W
The scheduling language syntax check for object "object_ID" has produced the following number of warnings "warning_count". - AWSBIA303W
Total warnings in !1: !2. - AWSBIA304W
An inconsistency in the workstation definition has been ignored. The secure port identified in the secureaddr keyword has been ignored because the securitylevel keyword has not been supplied. - AWSBIA309E
The validto date must be greater than the validfrom date in run cycle "run_cycle" defined in job stream "job_stream". - AWSBIA310E
The validto date must be greater than the validfrom date in a run cycle defined in job stream "job_stream". - AWSBIA315E
There is a syntax error. The syntax of either the follows or the matching keywords is not correct. - AWSBIA316E
An internal error has occurred. The file "file" could not be read. - AWSBIA317E
An internal error has occurred. The file "file" could not be opened due to a memory allocation error. - AWSBIA320E
An error occurred while trying to save the user options file "file". - AWSBIA322W
The local prompt text in job stream "job_stream" exceeds the maximum length allowed of "max_prompt" bytes. It has been truncated. - AWSBIA323W
The total units for the resource "resource" in job stream "job_stream" is "resource_units" units, which exceeds the maximum number of resource units: "max_resource_units". - AWSBIA324E
The total units for the resource "resource" in job "job" is "resource_units" units, which exceeds the maximum number of resource units: "max_resource_units". - AWSBIA325W
The local prompt text in job "job" exceeds the maximum length allowed of "max_prompt" bytes. It has been truncated. - AWSBIA326W
The server field has been supplied for extended agent "agent", for which it is not required. It has been ignored. - AWSBIA327W
The fullstatus field has been supplied as on for extended agent "agent", for which it is not required. It has been set to off. - AWSBIA328W
The behindfirewall field has been supplied for extended agent "agent", for which it is not required. It has been ignored. - AWSBIA329W
The securitylevel field and the secureaddr fields have been supplied for extended agent "agent", for which they are not required. They have been ignored. - AWSBIA330W
The autolink field has been supplied as on for extended agent "agent", for which it is not required. It has been set to off. - AWSBIA331W
The fullstatus field has been supplied as on for standard agent "agent", for which it is not required. It has been set to off. - AWSBIA332W
The fullstatus field has been supplied as off for domain manager "domain_manager", which is not correct. It has been set to on. - AWSBIA333W
The server field has been supplied for domain manager "domain_manager", for which it is not required. It has been ignored. - AWSBIA334W
The resolvedep field has been supplied for workstation "workstation", for which it is not required. It has been ignored. - AWSBIA335W
The secureaddr field has been supplied for workstation "workstation", but the securitylevel field has not. It has been ignored. - AWSBIA336W
The method field has been supplied for workstation "workstation", for which it is not required. It has been ignored. - AWSBIA337W
The manager field has been supplied for domain "domain", for which it is not required as it is now obsolete. It has been ignored. - AWSBIA338W
The domain field has been supplied for extended agent "agent", for which it is not required. It has been ignored. - AWSBIA339W
The securitylevel field has been supplied for extended agent "agent", but the secureaddr field (SSL port) has not. The default value of 31113 is used for secureaddr. - AWSBIA340W
The host field has been supplied for standard agent "agent", for which it is not required. It has been replaced by the domain to which the workstation belongs. - AWSBIA341W
The host field has been supplied for workstation "workstation", for which it is not required. It has been ignored. - AWSBIA342E
The filter keyword "incorrect_keyword" cannot be used for the supplied object. - AWSBIA343E
The supplied filter criteria cannot be used twice. - AWSBIA344E
The supplied filter criteria is not valid for the supplied object of the command. The filter for the object of this command requires keyword "valid_keyword". - AWSBIA345E
The supplied filter criteria is not valid for the supplied object of the command. The filter for the object of this command requires one of the following keywords "valid_keywords_list". - AWSBIA346E
No filter criteria has been supplied after the filter keyword. Use the following criteria: "filter_criteria". - AWSBIA347E
No filter criteria has been supplied after the filter keyword. Use the following criteria: "valid_filter_criteria_list". - AWSBIA348E
The supplied keyword is not valid for the supplied object. The command on this object requires keyword "valid_keyword". - AWSBIA349E
The supplied keyword is not valid for the supplied object. The command on this object requires one of the following keywords "valid_keywords_list". - AWSBIA350W
The keywords schedtime and at can be specified only once. The last value is used. - AWSBIA351E
The rename command does not support the cpu keyword because it is ambiguous. To rename cpu objects use the specific keywords for workstation ws, workstation class wscl, or domain dom. - AWSBIA352W
The IPv6 address you entered is an IPv4-mapped address and might not be supported on some platforms. - AWSBIA353W
The IPv6 address you entered is an IPv4-compatible address and might not be supported on some platforms. - AWSBIA354W
The IPv6 address you entered is a Link Local address. Its scope is limited to the same data link and the interface is not portable. - AWSBIA355E
There is a syntax error in the XML file. The closing Eventrule tag has been found without a corresponding opening tag. - AWSBIA356E
There is a syntax error in the XML file. The closing comment tag has been found without a corresponding opening tag. - AWSBIA357E
There is a syntax error in the XML file. An opening tag for a comment tag has been found before the closing tag of the previously opened comment. - AWSBIA358E
There is a syntax error in the XML file. The encoding used is not that of the locale. - AWSBIA359E
There is a syntax error in the XML file. The XML version is missing from the header, so the file cannot be parsed. - AWSBIA360E
There is a syntax error. You can not change the vartable of a variable. You can change only the variable name. - AWSBIA361W
The domain keyword has been supplied for agent, or pool, or dynamic pool, or remote engine workstation "workstation", for which it is not required. It has been ignored. - AWSBIA362W
The server keyword has been supplied for agent, or pool, or dynamic pool, or remote engine workstation "workstation", for which it is not required. It has been ignored. - AWSBIA363W
The fullstatus keyword has been supplied for agent, or pool, or dynamic pool, or remote engine workstation "workstation", for which it is not required. It has been ignored. - AWSBIA364W
The behindfirewall keyword has been supplied for agent, or pool, or dynamic pool, or remote engine workstation "workstation", for which it is not required. It has been ignored. - AWSBIA365W
The autolink keyword has been supplied for agent, or pool, or dynamic pool, or remote engine workstation "workstation", for which it is not required. It has been ignored. - AWSBIA366W
The access keyword has been supplied for agent, or pool, or dynamic pool, or remote engine workstation "workstation", for which it is not required. It has been ignored. - AWSBIA367W
The securitylevel keyword has been supplied for agent, or pool, or dynamic pool, or remote engine workstation "workstation", for which it is not required. It has been ignored. - AWSBIA368W
The protocol keyword has been supplied for workstation "workstation", for which it is not required. It has been ignored. - AWSBIA369W
The protocol value is http for agent workstation "workstation", for which the secureaddr keyword has been supplied. The protocol keyword has been ignored. - AWSBIA370W
The protocol value is https for agent workstation "workstation", for which the secureaddr keyword has not been supplied. The protocol keyword has been ignored. - AWSBIA371E
The required node keyword is missing for workstation "workstation". - AWSBIA372E
The required members keyword is missing for pool workstation "workstation". - AWSBIA373E
The required requirements keyword is missing for dynamic pool workstation "workstation". - AWSBIA374E
The os keyword specified for workstation "workstation" is not set to a valid operating system type. ZOS type is valid only for agents, pools, dynamic pools and remote engine workstations. - AWSBIA375W
One or more invalid keywords have been supplied for workstation "workstation". These invalid keywords have been ignored. - AWSBIA376W
The requirements keyword has been supplied for workstation "workstation", for which it is not required. It has been ignored. - AWSBIA377W
The securitylevel value for workstation "workstation" is not NONE. It has been ignored. - AWSBIA378E
The supplied set criteria cannot be used twice. - AWSBIA379E
The "incorrect_keyword" attribute specified for the set criteria cannot be used for the supplied object. - AWSBIA380E
No set criteria was supplied after the set keyword. Use the following syntax to specify the attribute for the set criteria: "set_criteria". - AWSBIA381E
No set criteria was supplied after the set keyword. Use the following criteria: "valid_set_criteria_list". - AWSBIA382E
The attribute specified for the set criteria is not applicable for the supplied object. The set keyword for the object requires the following attribute "valid_keyword". - AWSBIA383E
The attributes specified for the set criteria are not applicable for the supplied object. The set criteria for the object requires one of the following attributes "valid_keywords_list". - AWSBIA386E
The submitted command cannot be performed. The error is: "error_msg" - AWSBIB - Scheduling language parser messages
This section lists scheduling language parser error and warning messages that might be issued. - AWSBIB001E
There is a syntax error. The time specified in the at, until, or deadline time definitions must be between 0000 and 2359 (hhmm). - AWSBIB002E
There is a syntax error. The job limit must be between 0 and 1024. - AWSBIB003W
The resource number must be between 1 and 32. - AWSBIB004W
There is a syntax error. Priority must be a numeric value from 0 to 99, hi (= 100), or go (= 101). - AWSBIB006E
There is a syntax error. The job stream name is not syntactically valid. The name must start with a letter, and can contain alphanumeric characters, dashes, and underscores. It can contain up to 16 bytes. - AWSBIB007E
There is a syntax error. The job name is not syntactically valid. The name must start with a letter, and can contain alphanumeric characters, dashes and underscores. It can contain up to 40 bytes. - AWSBIB008E
There is a syntax error. The resource name is not syntactically valid. The name must start with a letter, and can contain alphanumeric characters, dashes and underscores. It can contain up to 8 bytes. - AWSBIB009E
There is a syntax error. The prompt name is not syntactically valid. The name must start with a letter, and can contain alphanumeric characters, dashes and underscores. It can contain up to 8 bytes. - AWSBIB010E
There is a syntax error. The calendar name is not syntactically valid. The name must start with a letter, and can contain alphanumeric characters, dashes and underscores. It can contain up to 8 bytes. - AWSBIB011E
There is a syntax error. The recovery job name is not syntactically valid. The name must start with a letter, and can contain alphanumeric characters, dashes and underscores. It can contain up to 40 bytes. - AWSBIB012E
Recovery job lockword is not syntactically valid. - AWSBIB013E
Recovery job password is not syntactically valid. - AWSBIB014E
There is a syntax error in the job statement in the job stream definition. The required streamlogon <username> argument has not been supplied. - AWSBIB015E
Invalid logon for MPE job - AWSBIB016E
There is a syntax error in the job statement in the job stream definition. The streamlogon user name is not syntactically valid. The name must be no more than 47 bytes, and cannot contain periods or other special characters. - AWSBIB017E
Group name is not syntactically valid. - AWSBIB018E
Account name is not syntactically valid. - AWSBIB019E
User job name is not syntactically valid. - AWSBIB020E
File name is not syntactically valid. - AWSBIB021E
File group name is not syntactically valid. - AWSBIB022E
File account name is not syntactically valid. - AWSBIB023E
There is a syntax error in the job statement in the job stream definition. The user name associated with the streamlogon keyword is not syntactically valid. The name can contain up to 47 bytes. If the name contains special characters they must be enclosed in quotes (). - AWSBIB024E
Group name in streamed job's logon is not syntactically valid. - AWSBIB025E
Account name in streamed job's logon is not syntactically valid. - AWSBIB026E
There is a syntax error. A non-valid date has been specified. The date format is determined by the value in the useropts file. - AWSBIB027E
There is a syntax error. The at keyword can be specified for a job or its job stream (not both). - AWSBIB028E
There is a syntax error. The until keyword can be specified for a job or its job stream (not both). - AWSBIB029E
There is a syntax error. The needs keyword can be specified for a job or its job stream (not both). - AWSBIB030W
Resource CPU should match either job's or schedule's cpuid - AWSBIB032E
Internal Error - AWSBIB033E
The file "file_name" could not be opened. - AWSBIB034E
There is a syntax error in the job statement of the job stream definition. A duplicate keyword has been supplied. - AWSBIB035E
There is a syntax error. The required on keyword is missing. - AWSBIB036E
There is a syntax error. The job stream definition does not start with the schedule keyword. - AWSBIB037E
Expected a Job description - AWSBIB038E
There is a syntax error. An object identifier (for example, a job name) is missing. - AWSBIB039E
There is a syntax error. A numeric value (for example, the priority value) has not been supplied. - AWSBIB040E
There is a syntax error. An object identifier (for example, a job name) or the @ wildcard is missing. - AWSBIB041E
There is a syntax error. A date-related keyword has been supplied (for example, deadline) but it is not followed by a date or day specification, or a calendar or iCalendar name. - AWSBIB042E
There is a syntax error. A day, weekday, or workday keyword has been supplied, but it is not preceded by an offset value. - AWSBIB043E
There is a syntax error. A dependency specification or other keyword is missing, or an incorrect keyword has been supplied. - AWSBIB044E
There is a syntax error. A time-related keyword (for example, every) has been supplied, but its value is either missing or is not a valid time specification. - AWSBIB045E
There is a syntax error. An opens keyword has been supplied, but its value is either missing or is not a valid file name. - AWSBIB046E
Expected a day specification. - AWSBIB047E
There is a syntax error. An except keyword has been supplied, but its value is either missing or is not a valid date specification, day specification, calendar or iCalendar name. - AWSBIB048E
Expected a calendar name. - AWSBIB049E
Expected a job autodoc specification. - AWSBIB050E
Expected an autodoc option. - AWSBIB051E
There is a syntax error. The prompt keyword has been supplied, but is not followed by a prompt name or the prompt text enclosed in quotes. - AWSBIB052E
There is a syntax error. The end keyword has not been found to stop the job stream definition. - AWSBIB053E
There is a syntax error. A file name has been supplied with an incorrect syntax. - AWSBIB054E
There is a syntax error. The supplied fully qualified path name is longer than the maximum of "maximum_path_name_length" bytes. - AWSBIB055E
There is a syntax error. The supplied logon name is longer than the maximum of "maximum_logon_name_length" bytes. - AWSBIB056E
There is a syntax error. The supplied file name is longer than the maximum of "maximum_file_name_length" bytes. - AWSBIB057E
There is a syntax error. The supplied abendprompt is longer than the maximum of "abendprompt_length" bytes. - AWSBIB058E
There is a syntax error. The supplied Windows domain name is not syntactically valid. The name can contain up to 16 bytes (including the backslash), and the user name can contain up to 31 bytes. - AWSBIB059E
There is a syntax error. The supplied timezone keyword is not followed by valid time zone information. - AWSBIB060E
There is a syntax error. The supplied timezone keyword is not followed by a time zone name. - AWSBIB061E
There is a syntax error. The supplied time zone name is not a recognized time zone. - AWSBIB062E
There is a syntax error. The supplied time zone name is longer than 40 bytes. - AWSBIB063E
There is a syntax error. The scheduler has determined that a job statement has commenced but it is not preceded by the : character. - AWSBIB064E
There is a syntax error. The dates specified with the on and except keywords are not compatible. For example, you might have defined the same date or dates for both. - AWSBIB065E
There is a syntax error. The deadline offset can be specified for a job or its job stream (not both). - AWSBIB066E
There is a syntax error in the job statement in the job stream definition. The rccondsucc keyword defines a return code success condition expression which is longer than the maximum number of bytes allowed: "maximum_expression_length". - AWSBIB067E
There is a syntax error. The return code condition expression: "expression" is not syntactically valid. - AWSBIB068E
The time in the relative from <time> to <time> clause of the matching or follows keyword is not in the valid format [+/-][h]hhmm (where mm is between 00-59). - AWSBIB069E
The time in the from <time> to <time> clause of the matching or follows keyword must be between 0000-2359. - AWSBIB070E
There is a syntax error. An at or a schedtime keyword has been specified with a time specification, but is not followed by a timezone/tz or daykeyword, or a right bracket. - AWSBIB071E
An error has occurred due to either a syntax error or unacceptable value when specifying the time for either the maxdur or mindur keyword, or both. The correct format and acceptable values for the time specified for the keywords are: [h]hhmm (where, hhh represents the number of hours ranging from 000-500, and mm represents the number of minutes ranging from 00-59). - AWSBIB072E
The percentage specified for the maxdur or mindur keyword is either not in the valid format or an unacceptable value has been specified. The correct format and acceptable values are: percentage % (where percentage is a number ranging from 0-1000000). - AWSBIB200E
There is a syntax error. An object identifier (for example, a job name) is longer than the maximum number of bytes. - AWSBIB201E
There is a syntax error. An object identifier (for example, a job name) must begin with an alphabetic character. - AWSBIB202E
There is a syntax error. An object identifier (for example, a job name) contains non valid characters. - AWSBIB206E
There is a syntax error. More than one parameter was specified. - AWSBIB208E
There is a syntax error. The number of job stream dependencies exceeds the maximum number allowed. - AWSBIB209E
There is a syntax error. The number of job dependencies exceeds the maximum number allowed. - AWSBIB210E
Missing parameter ^^ was specified. - AWSBIB211W
The IN ORDER keyword must be the last keyword. - AWSBIB212E
No dependencies are allowed when IN ORDER is specified - AWSBIB213E
There is a syntax error. A blank name has been supplied. - AWSBIB214E
There is a syntax error. The onuntil keyword has a non-valid value. Valid values are suppr, cont or canc. - AWSBIB215E
There is a syntax error. Either the follows or matching keyword is not followed by one of the following keywords: previous, sameday, relative from, or from. - AWSBIB216E
There is a syntax error. Expected the keyword set: from <time> to <time>. - AWSBIB217E
There is a syntax error. Expected the keyword set: relative from <time> to <time> (<time> is expressed as HHMM, and the permitted values are between 0000 and 2359) - AWSBIB219E
There is a syntax error. More than one matching keyword has been supplied. - AWSBIB220E
There is a syntax error. A non-valid job alias has been supplied. - AWSBIB221E
There is a syntax error. A non-valid runcycle name has been supplied. - AWSBIB222E
Duplicated runcycle name. - AWSBIB223E
There is a syntax error. A value has been supplied for a description keyword that is longer than the maximum length of "maximum_description_length" bytes. - AWSBIB224E
There is a syntax error. An external string dependency has been supplied that is longer than the maximum length of "maximum_description_length" bytes. - AWSBIB225E
There is a syntax error. An iCalendar name has been supplied that is longer than the maximum length of "maximum_description_length" bytes. - AWSBIB226E
There is a syntax error. A day[s] offset for a relative from <time> to <time> or a from <time> to <time> clause has been supplied that is greater than the maximum of "maximum_offset" days. - AWSBIB227E
There is a syntax error. An day[s] offset for an at, until, or deadline clause has been supplied that is greater than the maximum of "maximum_offset" days. - AWSBIB228E
There is a syntax error. An every keyword has been supplied with a rate not in the range 0 - "maximum_rate". - AWSBIB229E
An iCalendar cannot be empty. - AWSBIB230E
There is a syntax error. The keyword "keyword" is not correct at this position. - AWSBIB231E
There is a syntax error. A relative from <time> to <time> or a from <time> to <time> clause has been supplied where the from time is later than the to time. - AWSBIB232E
There is a syntax error. The value specified for the onmaxdur keyword is not valid. Valid values are kill or cont. - AWSBIB233E
There is a syntax error. The value specified for the onmindur keyword is not valid. Valid values are confirm, abend or cont. - AWSBIB234E
There is a syntax error. A valid output condition name is required. - AWSBIB235E
Condition names must be unique. A duplicate output condition name was specified. - AWSBIB236E
Conditional dependency names must be unique. A duplicate conditional dependency name was specified. - AWSBIB237E
There is a syntax error. The conditional dependency name specified is not valid. - AWSBIB238E
There is a syntax error. The conditional dependency expression you specified is not in context with a conditional dependency based on an output condition. - AWSBIB239E
There is a syntax error. The conditional dependency you specified is not in context with a conditional dependency based on the final status of the predecessor. - AWSBIB240E
There is a syntax error. The conditional dependency expression you specified is not in consistent with a conditional dependency based on the provided precedessor. - AWSBIB241E
There is a syntax error. The conditional dependency expression you specified is not in context with a conditional dependency based on when the predecessor job starts. - AWSBIB315E
Either a job or job stream identifier is missing, or the matching criteria is not valid. - AWSBIB316E
There is a syntax error. A recovery action has been supplied that is not stop, continue, or rerun. - AWSBIB317E
The path of a filename in the opens dependencies and its qualifier cannot exceed "dependency_file_name_max_length" bytes. - AWSBIB318E
You cannot specify a time zone for the run cycle time dependencies. - AWSBIB319E
There is an error in the job definition. The sum of the docommand string and the rccondsucc string must not be greater than "maximum_length" bytes. - AWSBIB320W
The specified keyword is not allowed in a job definition outside a job stream. - AWSBIB321E
A variable table name is expected at this point, but was not supplied. - AWSBIB322E
The variable table name exceeds the maximum length of "maximum_variable_table_size" bytes. - AWSBIB323W
The tasktype keyword has been supplied for job definition "job_definition", for which it is not required. It has been ignored. - AWSBIB324W
The interactive keyword has been supplied for job definition "job_definition", for which it is not required. It has been ignored. - AWSBIB325E
The task definition supplied for job definition "job_definition" is not well formatted. - AWSBIB326E
There is a syntax error. The run cycle group name is not valid. The name must start with an alphabetical character, and can contain alphanumeric characters, dashes, and underscores. It can contain up to 40 bytes. - AWSBIB327E
There is a syntax error. A valid run cycle subset name was expected but was not found. The subset name must start with either an alphabetical character or number, and can contain alphanumeric characters, dashes, and underscores. It can contain a maximum of 40 bytes. - AWSBIB328E
There is a syntax error. The run cycle subset cannot be specified in the job stream definition. - AWSBIB329E
There is a syntax error. The run cycle group name is not valid. The name must start with an alphabetical character, and can contain alphanumeric characters, dashes and underscores. It can contain up to 40 bytes. - AWSBIB330W
The specified keyword cannot be defined in a run cycle group definition. - AWSBIB331E
There is a syntax error. The end keyword is missing from the run cycle group definition. - AWSBIB332E
There is a syntax error. The run cycle type run cycle group cannot be specified inside the run cycle group definition. - AWSBIB333E
There is a syntax error. A value has been supplied for the subset keyword that is longer than the maximum length of "maximum_subset_length" bytes. - AWSBIB334E
There is a syntax error. The runcyclegroup keyword is missing from the start of the run cycle group definition. - AWSBIB335E
There is a syntax error. The every keyword is not followed by the everyendtime keyword. - AWSBIB336E
There is a syntax error. The onoverlap keyword has a non-valid value. Valid values are parallel, donotstart or enqueue. - AWSBIB337E
There is a syntax error. The statisticstype keyword has a non-valid value. Valid values are automatic or custom. - AWSBIB338E
There is a syntax error. The number of joined conditional dependencies exceeds the maximum supported number. - AWSBIB339E
There is a syntax error. The name of the joined conditional dependencies is not syntactically valid. The name must start with a letter, and can contain alphanumeric characters, dashes, and underscores. It can contain up to 16 bytes. - AWSBIB340E
Joined conditional dependencies names must be unique. A duplicate name was specified. - AWSBIB341E
There is a syntax error. The name of the joined conditional dependencies is not followed by the number of dependencies to be met. - AWSBIB342E
There is a syntax error. The endjoin to close the joined conditional dependencies definition was not found. - AWSBIB343E
There is a syntax error. The number of dependencies to be met in the joined conditional dependencies is not syntactically valid. The value must be a number between 0 and the total number of subsequent predecessors, or all. - AWSBIB344E
There is a syntax error. The follows keyword was not found in the joined conditional dependencies definition. - AWSBIB345E
There is a syntax error. Internetwork dependencies are not supported in joined conditional dependencies definition. - AWSBIB346E
There is a syntax error. The description keyword has been specified, but the related text is not enclosed in quotes or is missing. - AWSBIB347E
There is a syntax error. The return code condition expression is missing or is not enclosed in quotes. - AWSBIB348E
The output condition name exceeds the maximum length of "maximum_output_cond_size" bytes. - AWSBIB349E
A syntax error has occurred at line "line_number": unexpected token "unexpected_token". The parsing operation has stopped at the token in error. - AWSBIB350E
A syntax error has occurred during the parsing operation of the object "object_name". The parsing operation has stopped. - AWSBIB351E
A syntax error has occurred during the parsing operation. The parsing operation has stopped. - AWSBIC - Scheduling language messages
This section lists scheduling language error and warning messages that might be issued. - AWSBIC001E
An error occurred opening the database: !1 - AWSBIC002E
An error occurred opening the file !1 for reading - AWSBIC003E
An error was returned from the parser. - AWSBIC004E
!1 line !2, error looking for !3#!4 job in database: !5 - AWSBIC005E
!1 line !2, error looking for !3 prompt in database: !4 - AWSBIC006E
!1 line !2, error looking for !3#!4 resource in database: !5 - AWSBIC007E
!1 line !2, bad symphony job stream record retrieved: !3 instead of !4 - AWSBIC008E
!1 line !2, bad symphony job record retrieved: !3 instead of !4 - AWSBIC009E
!1 line !2, Security error: !3 - AWSBIC010E
!1 line !2, Symphony access error: !3 - AWSBIC011E
Error accessing run-message number file : !1 - AWSBIC012E
Error finding workstation !1 in cpudata file: !2 - AWSBIC013W
Job !5 in job stream !4 is hosted by workstation !3, resource !1#!2 is hosted by workstation !1 - AWSBIC014W
Job stream !4 is hosted by workstation !3, resource !1#!2 is hosted by workstation !1 - AWSBIC015E
Error: Undefined parameter encountered - AWSBIC016E
Error: Parameter expansion causes buffer overflow - AWSBIC017E
Error: Parameter syntax error - AWSBIC018W
Warning: Duplicate job stream !1#!2 in class !3 , job stream ignored. - AWSBIC019E
!1 line !2, error using cpuclass !3 within a job stream whose workstation is !4 - AWSBIC020E
!1 line !2, error: could not get the workstation names in the cpuclass !3 - AWSBIC021E
Error: writing job stream to a temporary file - AWSBIC022E
Error: opening/creating a temporary file - AWSBIC023E
Error: getting workstation data from database - AWSBIC024W
!1 line !2, WARNING: filename base is longer than !3 bytes. The dependency is dropped and the priority is set to 0 - AWSBIC100W
!1 line !2, Warning: JOB Override !4#!5 is used instead of !3#!5 - AWSBIC101W
!1 line !2, Warning: RESOURCE Override !4#!5 is used instead of !3#!5 - AWSBIC102W
!1 line !2, Warning: Job !3#!4.!5 is not found in database. Added a dummy job in FAIL state. - AWSBIC103W
!1 line !2, Warning: Prompt !3 not found. Added prompt !3 in symphony. - AWSBIC104W
!1 line !2, Warning: Resource !4 for workstation !3 not found in database. Added resource !4 with 0 units. - AWSBIC106W
Warning: Workstation !1 does not exist in the cpudata database. Ignoring job stream !2. - AWSBIC107W
Time zones are not enabled in the global options and so are ignored on the job or job stream !1. - AWSBID - Compiler messages
This section lists error and warning messages that might be issued by the compiler component. - AWSBID001E
Compiler cannot find the thiscpu option in the local options file (localopts). - AWSBID002E
Compiler cannot find the master option in either the localopts file or the global options. - AWSBID003E
Compiler cannot be run on this workstation, because the settings in the global options or the localopts file indicate that this workstation is not the master domain manager. - AWSBID005E
There is a syntax error in the compiler command. An incorrect date specification ("date") has been found either in the production schedule file ("file_name"), or as an argument to the -date option. - AWSBID006E
Compiler was unable to open the production schedule file: "file_name". The following gives more details of the error: "system_error". - AWSBID007E
Compiler is unable to add the workstation records to the Symphony file. The following gives more details of the error: "error_message" - AWSBID008E
Compiler has found a database incompatibility (expanded/non-expanded) or is unable to allocate memory to access the databases. The following gives more details of the error: "error_message". - AWSBID009E
There is a syntax error in the compiler command. The -date option has been supplied, but the date that follows the option is not valid: "date" - AWSBID010E
Compiler was unable to read calendar information from the database. The following gives more details of the error: "error_message" - AWSBID011E
Compiler was unable to read date information from the following calendar in the "calendar" database. The following gives more details of the error: "error_message". - AWSBID012E
Compiler was unable to add the following calendar to the Symphony file: "calendar". The following gives more details of the error: "error_message" - AWSBID013E
Compiler did not find the definition for the master domain manager workstation in the cpudata database. - AWSBID014E
There is a syntax error in the compiler command. An incorrect number of options was supplied. - AWSBID015E
Compiler was unable to lock the jobs database. The following gives more details of the error: "error_message". - AWSBID016E
Compiler was unable to lock the resources database. The following gives more details of the error: "error_message". - AWSBID017E
Compiler was unable to lock the prompts database. The following gives more details of the error: "error_message". - AWSBID018E
Compiler was unable to lock the cpudata database. The following gives more details of the error: "error_message". - AWSBID019E
Compiler was unable to lock the calendars database. The following gives more details of the error: "error_message". - AWSBID020E
Compiler was unable to unlock the jobs database. The following gives more details of the error: "error_message". - AWSBID021E
Compiler was unable to unlock the resources database. The following gives more details of the error: "error_message". - AWSBID022E
Compiler was unable to unlock the prompts database. The following gives more details of the error: "error_message". - AWSBID023E
Compiler was unable to unlock the cpudata database. The following gives more details of the error: "error_message". - AWSBID024E
Compiler was unable to unlock the calendars database. The following gives more details of the error: "error_message". - AWSBID025E
Compiler was unable to lock the userdata database. The following gives more details of the error: "error_message". - AWSBID026E
Compiler was unable to unlock the userdata database. The following gives more details of the error: "error_message". - AWSBID027E
Compiler was unable to read the user information from the database and add it to the Symphony file. The following gives more details of the error: "error_message". - AWSBID029W
You cannot initialize the centralized security option because your database is in non-expanded mode. - AWSBID200E
Line !1: The !2 name is longer than 8 bytes. - AWSBID201E
Line !1: The !2 name must begin with an alphabetic character. - AWSBID202E
Line !1: The !2 name contains one or more character that is not allowed. - AWSBIE - BigInsights plug-in messages
This section lists error and warning messages that could be issued by the BigInsights plug-in. - AWSBIE013E
Error: input file !1 and output file !2 are identical - AWSBIF - messages
This section lists error and warning messages that could be issued. - AWSBIF002E
Couldn't malloc program globals. - AWSBIF003E
Couldn't open output, error is: !1 - AWSBIF004E
Error writing output, error is: !1 - AWSBIF006E
Error reading mastsked is: !1 - AWSBIF007E
Error finding next job stream is: !1 - AWSBII - General and miscellaneous messages
This section lists error and warning general and miscellaneous messages that might be issued. - AWSBII001E
Unable to write token control structure. - AWSBII002E
No tokens in list. - AWSBII003E
Non-valid token !1 in list (!2). - AWSBII004E
No read access to parameter in !1. - AWSBII005E
Undefined parameter !1 in string !2; not replaced. - AWSBII006E
Parameter expansion overflow in !1. - AWSBII007E
Parameter syntax error in !1. - AWSBII008E
Cannot deamonize. - AWSBII009E
An error has occurred. - AWSBII010W
Cannot update the file "old_file". A new file "new_file" was created. You must replace the old file with the new file. - AWSBII014E
Your command line interface settings cannot be modified to allow the input of the password. - AWSBII015E
The new password and the confirmation password do not match. - AWSBII016E
An internal error has occurred. The directory !1 cannot be created. - AWSBII017E
An internal error has occurred.The program is unable to initialize the GSKit libraries. - AWSBII018W
Online help is not available on Windows platforms. - AWSBIJ - Jobmon specific error messages
This section lists error and warning messages that could be issued by the routines that handle the Jobmon process. - AWSBIJ001E
An internal error has occurred. Jobmon is unable to create a socket for communication with jobman. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ002E
Unable to get hostname !1:!2 error = !3 : !4. - AWSBIJ003E
Unable to get host entries by name !1:!2 error = !3 : !4. - AWSBIJ004E
An internal error has occurred. Jobmon is unable to bind the socket to the address used for communication with jobman. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ005E
An internal error has occurred. Jobmon is unable to obtain the socket attributes for communication with jobman. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ006E
An internal error has occurred. Jobmon is unable to listen for connection requests from jobman. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ007E
An internal error has occurred. Jobmon is unable to accept a connection request from jobman. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ008E
An internal error has occurred. Jobmon is unable to unable to allocate sufficient memory to process requests from jobman. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ009E
An internal error has occurred. Jobmon is unable to select a data socket for a communication request from jobman. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ010E
An internal error has occurred. Jobmon is unable to read the data received from jobman. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ011E
An internal error has occurred. Jobmon either cannot generate a temporary file name, or is unable to retrieve a system configuration value. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ012E
Error changing directory !1:!2 error = !3 : !4. - AWSBIJ013E
Error opening file !1:!2 error = !3 : !4. - AWSBIJ100E
An internal error has occurred. Jobmon has received an error when using a Windows system call (API). The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ101E
An internal error has occurred. Jobmon was unable to create a new process and its primary thread. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ102E
An internal error has occurred. Jobmon cannot determine the state of an opens (check file) dependency. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ103E
An internal error has occurred. Jobmon cannot determine the status of the command used to determine the state of an opens (check file) dependency. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ104E
Error allocating storage local to thread !1:!2 error = !3 : !4. - AWSBIJ105E
An internal error has occurred. Jobmon cannot create the thread to read the output of the method that is used to resolve internetwork dependencies. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ106E
Error setting local thread value !1:!2 error = !3 : !4. - AWSBIJ107E
Error getting local thread value !1:!2 error = !3 : !4. - AWSBIJ108E
An internal error has occurred. Jobmon was unable to retrieve time information for the specified process. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ109E
An internal error has occurred. Jobmon was unable to log a user on to the local computer. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ110E
Error creating a mutex !1:!2 error = !3 : !4. - AWSBIJ111E
Error acquiring a mutex !1:!2 error = !3 : !4. - AWSBIJ112E
Error releasing a mutex !1:!2 error = !3 : !4. - AWSBIJ113E
An internal error has occurred. Jobmon cannot terminate the command that determines the state of an opens (check file) dependency. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ114E
An internal error has occurred. Jobmon was unable to duplicate an object handle because an API window has failed. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ115E
An internal error has occurred. Jobmon was unable to create the event to communicate with the threads that monitor active jobs. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ116E
An internal error has occurred. Jobmon could not create the security descriptor to change the access permissions for the stdlist file. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ117E
An internal error has occurred. Jobmon was unable to create temporary files to redirect the stdin/stdout of the command that resolves opens (check file) dependencies. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ118E
An internal error has occurred. Jobmon was unable to get the default process environment to launch jobs. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ119E
An internal error has occurred. Jobmon encountered an error looking up a security identifier (SID) for the account and the name of the domain on which the account was found. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ120E
An internal error has occurred. Jobmon was unable to obtain the name of the user associated with the current jobmon thread. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ121E
An internal error has occurred. Jobmon was unable to get a user's Security Identifier (SID) to set the stream logon to that user. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ122E
An internal error has occurred. Jobmon was unable to validate a security identifier (SID). The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ123E
An internal error has occurred. Jobmon was unable to initialize a security identifier (SID). The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ124E
An internal error has occurred. Jobmon encountered an error because the Access Control List buffer size is too small for the information needed to be stored in it (the buffer size is hard-coded). The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ125E
An internal error has occurred. Jobmon was unable to initialize a new Access Control List structure. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ126E
An internal error has occurred. Jobmon was trying to access the stdlist file, but was unable to add an access-allowed access control entry to an access control list. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ127E
An internal error has occurred. Jobmon was trying to access the stdlist file, but was unable to initialize a new security descriptor. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ128E
An internal error has occurred. Jobmon was trying to access the system desktop or the stdlist file, but was unable to set information in a discretionary access control list. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ129E
Error getting current process !1:!2 error = !3 : !4. - AWSBIJ130E
An internal error has occurred. Jobmon was unable to retrieve the handle for the window station associated with the calling process. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ131E
Error getting user object information !1:!2 error = !3 : !4. - AWSBIJ132E
An internal error has occurred. Jobmon was unable to retrieve the handle for the desktop associated with a specified thread. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ133E
An internal error has occurred. Jobmon was unable to create a window station object. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ134E
An internal error has occurred. Jobmon was unable to assign a window station to the calling process. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ135E
An internal error has occurred. Jobmon was unable to retrieve the handle to an existing desktop object. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ136E
Error in validating heap !1:!2 error = !3 : !4. - AWSBIJ137E
An internal error has occurred. Jobmon was unable to allocate system memory for internal data structures. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ138E
Error in freeing heap memory !1:!2 error = !3 : !4. - AWSBIJ139E
An internal error has occurred. Jobmon was unable to create a new desktop on the window station associated with the calling process. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ140E
An internal error has occurred. Jobmon was unable to create the Windows process environment to launch jobs. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ141E
Error in getting the domain controller name !1:!2 error = !3 : !4. - AWSBIJ142E
Error in getting the user information from system !1:!2 error = !3 : !4. - AWSBIJ143E
An internal error has occurred. Jobmon cannot open is own process token to set its process rights. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ144E
Error in setting user object information !1:!2 error = !3 : !4. - AWSBIJ145E
Error in getting any of the domain controllers name !1:!2 error = !3 : !4. - AWSBIJ146E
An internal error has occurred. Jobmon was unable to find the home directory of the user specified in the streamlogon field of the job. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ147E
An internal error has occurred. Jobmon was unable to retrieve a pointer to the discretionary access control list in a specified security descriptor. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ148E
One of the following internal errors has occurred:- Jobmon was unable to retrieve the handle of an existing window station- Jobmon was unable to retrieve the handle of the window station associated with the calling process- Jobmon was unable to assign a window station to the calling process.The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ149E
An internal error has occurred. Jobmon was unable to retrieve the security information for the HCL Workload Automation user object. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ150E
An internal error has occurred. Jobmon encountered an error because the user specified in the streamlogon field of the job does not have the rights either to log on locally or to log on as batch. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ151E
Error granting user rights for job logon !1:!2 error = !3 : !4. - AWSBIJ152E
An internal error has occurred. Jobmon encountered an error checking that the user specified in the streamlogon field of the job has access to the interactive desktop. The error occurred in the following source code file: "file_name" at line: "line_number". The error message and error number are as follows: "error_message" : "error_number". - AWSBIJ153E
An internal error has occurred. Jobmon was unable to retrieve time information for the specified process. - AWSBIJ154E
An internal error has occurred. Jobmon was unable to get a user's Security Identifier (SID) to set the stream logon to that user. - AWSBIJ201E
Incorrect usage. Correct usage is JOBMON pipehandle !1:!2 - AWSBIJ203E
An internal error has occurred. Jobmon encountered an error while trying to adopt a child process. The error occurred in the following source code file: "file_name" at line: "line_number". - AWSBIJ204W
An internal error has occurred. Jobmon has received a message from jobman that it is unable to interpret. The error occurred in the following source code file: "file_name" at line: "line_number". - AWSBIJ205W
An internal error has occurred. Jobmon has received a message from jobman that has a non-valid version. The error occurred in the following source code file: "file_name" at line: "line_number". - AWSBIJ206W
An internal error has occurred. Jobmon has received a message from jobman that contains a non-valid message type. The error occurred in the following source code file: "file_name" at line: "line_number". - AWSBIJ207E
An internal error has occurred. Jobmon was unable to read the user information from the Symphony file. The error occurred in the following source code file: "file_name" at line: "line_number". - AWSBIJ208E
An internal error has occurred. Jobmon was unable to retrieve user information. The error occurred in the following source code file: "user_name" at line: "file_name". - AWSBIJ209E
Unable to initialize the GSKit libraries. - AWSBIJ211E
An internal error has occurred. Jobmon could not find any existing or valid Windows sessions for user streamlogon that requires an interactive desktop. - AWSBIK - Jobmon messages
This section lists error and warning Jobmon messages that might be issued. - AWSBIK001E
Error creating socket !1:!2 error = !3. : !4. - AWSBIK002E
Unable to get host name !1:!2 error = !3. : !4. - AWSBIK003E
Unable to get host entries by name !1:!2 error = !3. : !4. - AWSBIK004E
Error binding socket to address !1:!2 error = !3. : !4. - AWSBIK005E
Error connecting socket to server !1:!2 error = !3. : !4. - AWSBIK006E
Error sending data !1:!2 error = !3. : !4. - AWSBIK007E
Error receiving data !1:!2 error = !3. : !4. - AWSBIK008E
Error allocating memory !1:!2 in = !3. : !4. - AWSBIK009E
Error opening OS file handle !1:!2 error = !3. : !4. - AWSBIK010E
Error reading data !1:!2 error = !3. : !4. - AWSBIK100E
Error performing NT system action !1:!2 error = !3. : !4. - AWSBIK101E
Error creating process !1:!2 error = !3. : !4. - AWSBIK102E
Error creating anon. pipe !1:!2 error = !3. : !4. - AWSBIK103E
Error setting information on handle !1:!2 error = !3. : !4. - AWSBIK104E
Error getting process time information !1:!2 error = !3. : !4. - AWSBIK105E
Error converting time information !1:!2 error = !3. : !4. - AWSBIK201E
Unable to connect to job monitor !1:!2. - AWSBIK202E
Error creating JOBMON !1:!2. - AWSBIK203E
Jobmon responded with failure !1:!2 - AWSBIM - Common library messages
This section lists error and warning common library messages that might be issued. - AWSBIM001E
The workstation type does not match the workstation type in the database. - AWSBIM002E
The workstation !1 is not a valid host. - AWSBIM003E
The domain name must be specified for this workstation definition. - AWSBIM004E
An extended agent !1 cannot host itself. - AWSBIM005E
The parent domain !1 is not defined as a domain definition. - AWSBIM006E
The master domain cannot have a parent domain. It is the top-level in the domain hierarchy. - AWSBIM007E
A loop was found in the domain definition. - AWSBIM008E
The domain manager !1 is not defined as an FTA. - AWSBIM009E
The master domain manager !1 cannot be the manager of this domain !2. - AWSBIM010E
The domain manager !1 must be in the same domain as the workstation. - AWSBIM011E
The host workstation !1 is not found in the database. - AWSBIM012E
A non-valid domain !1 has been specified for the master domain manager. - AWSBIM013E
The workstation !1 already exists in the database. - AWSBIM014E
The workstation class !1 already exists in the database. - AWSBIM015E
The domain !1 already exists in the database. - AWSBIM016E
The access method !1 does not exist on your system. - AWSBIM017E
An object named as master domain !1 cannot be created in the database. - AWSBIM018E
The number of levels of hosting cannot be greater than two. - AWSBIM019E
Error: !1 - AWSBIM020E
Non-valid syntax for MPE user ID: !1 - AWSBIM021E
Non-valid job recovery option. - AWSBIM022E
Workstation !1 does not support the task type !2. - AWSBIM030E
Error !1 occurred while resolving dependencies. - AWSBIM031E
Job !1 does not exist in job stream !2#!3 - AWSBIM032E
Job stream !1#!2 has been changed. No update done. - AWSBIM033E
A circular dependency has occurred for !1#!2 and !3#!4. - AWSBIM034E
Job !1 already exists in the job stream. - AWSBIM035E
The job is hosted by workstation !4, resource !1#!2 is hosted by workstation !3. - AWSBIM036E
Resource !1#!2 has !4 available; this requires !3. - AWSBIM037E
Job stream is hosted by workstation !4, resource !1#!2 is hosted by workstation !3. - AWSBIM041E
Job master changed while trying to update job !1#!2. Update aborted. - AWSBIM042E
Error !1 occurred in resolve dependencies. - AWSBIM043W
Workstation !1 is not the master domain manager. The parameters are expanded from the master domain manager. - AWSBIM045E
File system error opening script/jcl file !1. !2 - AWSBIM046W
Order of interleaved dependencies are lost when job stream is written. - AWSBIM048E
Mastsked not updated. - AWSBIM049E
Autodoc not allowed for this job. - AWSBIM050E
Non-valid time zone !1 specified for at time of job or job stream!2. - AWSBIM051E
Non-valid time zone !1 specified for until time of job or job stream !2. - AWSBIM052E
A non-valid time of !1 hours, !2 minutes has been specified for the every keyword in job !3. - AWSBIM053E
A job stream cannot follow itself. - AWSBIM054E
A job cannot follow itself. - AWSBIM055E
A job stream cannot follow one of its jobs. - AWSBIM056E
A job cannot follow its job stream. - AWSBIM057E
The until time occurs before the at time for job or job stream !1. - AWSBIM060E
Error inserting into list. - AWSBIN - Plan libraries messages
This section lists error and warning messages that might be issued by the plan libraries that are used by several components. - AWSBIN001E
The workstation: "workstation" has not been initialized yet. - AWSBIN002E
The workstation "workstation" is already active. - AWSBIN003E
The workstation "workstation" identified as the target for a switch manager operation is not a fault-tolerant agent. - AWSBIN004E
The domain manager does not have the fullstatus field set to on. - AWSBIN005E
The domain manager "domain_manager" is not in the same domain as the local workstation "workstation". - AWSBIN006E
An internal error occurred while starting workstation "workstation". - AWSBIN007W
The manager option is valid only on the local workstation. It has been ignored. - AWSBIN008E
The start command cannot be issued to workstation "workstation", because it is not hosted by "host_workstation". - AWSBIN009E
An error occurred while starting workstation: "workstation". - AWSBIN011W
Workstation "workstation" has already stopped. - AWSBIN014E
A link or unlink command has been issued on workstation "workstation" to link to or unlink from a peer workstation within the same domain, which is not allowed. - AWSBIN015E
A link or unlink command has been issued on workstation "workstation", but the domain of the workstation being linked to or unlinked from is not subordinate to the domain of the local workstation. - AWSBIN016E
Monitoring is already active for workstation "workstation". - AWSBIN017E
Monitoring is already stopped for workstation "workstation". - AWSBIN020E
An error occurred while running command: "command_name"# - AWSBIN030E
The command issued for workstation "workstation_name" cannot be performed because the workstation is an extended agent, on which the command is not supported. - AWSBIN031E
Workstation "workstation" is not in domain "domain". The domain manager cannot be switched. - AWSBIN032W
Workstation "workstation" is already the manager of domain "domain". - AWSBIN033E
The command issued for workstation "workstation_name" cannot be performed, because the workstation is extended agent, or agent, or pool, or dynamic pool, or remote engine workstation, where the command is not supported. - AWSBIN034E
The command issued for workstation "workstation_name" cannot be performed because the workstation is an extended agent, workload broker, dynamic agent, pool, dynamic pool, or remote engine workstation, on which the command is not supported. - AWSBIN035E
The command issued for workstation "workstation_name" cannot be performed because the workstation is a dynamic agent, pool, dynamic pool, or remote engine workstation, on which the command is not supported. - AWSBIN036E
The command issued for workstation "workstation_name" cannot be performed because the workstation is an extended agent, workload broker, pool, dynamic pool, or remote engine workstation, on which the command is not supported. - AWSBIN037E
The command issued for workstation "workstation_name" cannot be performed because the workstation is a pool, dynamic pool, or remote engine workstation, on which the command is not supported. - AWSBIN040E
Unable to obtain information about the remote workstation "workstation_name" because centralized security, which is enabled for this domain, does not allow it to. - AWSBIN050E
An internal error has occurred. An unexpected record type has been found in the Symphony file. - AWSBIN051E
This operation cannot be performed on job stream "workstation"#"job_stream". - AWSBIN052E
The job stream has already been cancelled. - AWSBIN053E
An error has been found in file "file_name" at line "line_number". The program could not obtain the workstation names in workstation class "workstation_class". - AWSBIN054E
The following internal error has occurred in the TRANS module: "error_message" - AWSBIN055E
Job stream "workstation"#"job_stream" was not found in the database. The job stream cannot be submitted. - AWSBIN056E
The job stream has already been suppressed. - AWSBIN070E
Parameter not defined. - AWSBIN071E
Parameter expansion overflowed. - AWSBIN072E
There is a syntax error in a parameter. - AWSBIN073E
An error occurred creating a valid job name. - AWSBIN074E
You cannot submit a job to a workstation class. - AWSBIN075E
The job has been cancelled. - AWSBIN076E
The operation cannot be performed. The job or the current instance of the job is in an incorrect state. - AWSBIN077E
User jobs cannot be rerun. - AWSBIN078E
The stdlist could not be accessed. The job cannot be run. - AWSBIN079E
An error occurred obtaining the stdlist file status information for job: "JobKey1"."JobKey2": "JobKey3" - AWSBIN080E
An internal error occurred processing scribner packets. - AWSBIN081E
The requested job log cannot be loaded because the workstation "workstation" is no longer present in the selected plan. - AWSBIN090E
The following error occurred while obtaining the monitoring configuration file for workstation "workstation_name": "error_message" - AWSBIN091E
An error occurred obtaining the monitoring configuration file for workstation "workstation_name": The workstation does not support monitoring. - AWSBIN092E
The following error occurred while getting the broker information: "error_message" - AWSBIN100E
An error occurred accessing the runmsg file: "file". - AWSBIN101E
The opens file dependency is too long. - AWSBIN102W
The specified dependencies are same as those in the Symphony file. - AWSBIN103E
The supplied command is not valid for theuserjobs job stream. - AWSBIN104E
Dependencies cannot be added to a job in an in order job stream. - AWSBIN105E
The number of dependencies specified is more than the maximum allowed. - AWSBIN106E
The dependency record is not an external job type. - AWSBIN107E
The dependency "dependency" cannot be added, because it was not found in the Symphony file. - AWSBIN108E
A fully qualified filename is required for an opens file dependency. - AWSBIN109E
There is a logic error in the follows dependencies. The dependency is circular. - AWSBIN110E
A confirm action cannot be performed on an external job with output conditions specified. - AWSBIN111E
The confirm action cannot be performed because invalid output conditions were specified. - AWSBIN200E
The Symphony file and the database have incompatible versions. - AWSBIO - Comm_api messages
This section lists error and warning comm_api messages that might be issued. - AWSBIO001E
The supplied parameter "parameter" is not valid. - AWSBIO002E
The supplied parameter "parameter" does not have a valid length. - AWSBIO003E
The supplied parameter "parameter" already exists. - AWSBIO004E
The supplied parameter "parameter" has a non-alphabetic first character. - AWSBIO005E
The supplied parameter "parameter" contains non-valid characters. - AWSBIO006E
Field "field" has a null value. - AWSBIO007E
An internal error has occurred. The MAE_CA comarea cannot be initialized. - AWSBIO008E
An internal error has occurred. The SEC_CA comarea cannot be initialized. The error was: !1. - AWSBIO009E
An internal error has occurred. The database could not be opened. The error was: !1. - AWSBIO010E
An internal error has occurred. The database files are not at the correct version. - AWSBIO011E
An internal error occurred allocating memory. - AWSBIO012E
The filter type "filter_type" is not valid. - AWSBIO013E
The specified HCL Workload Automation object is not valid. - AWSBIO014E
An incorrect time value "time" has been specified in the filter "filter". - AWSBIO015E
An incorrect time type "time_type" has been specified in the filter "filter". - AWSBIO016E
An incorrect priority value "priority" has been specified in a filter. - AWSBIO017E
An incorrect priority type "priority_type" has been specified in a filter. - AWSBIO018E
ID filter not found in filter array. - AWSBIO019E
File "file" could not be opened. The error was: "error". - AWSBIO020E
File "file" could not be closed. The error was: "error". - AWSBIO021E
File "file" could not be read. The error was: "error". - AWSBIO022E
File "file" could not be written. The error was: "error". - AWSBIO023E
TWS is not installed under group "Group" - AWSBIO024E
"Server" server is not installed. - AWSBIO025E
Error opening Symphony: "Symphony" - AWSBIO026E
Error opening Events files: "EventFile" - AWSBIO027E
The object "object" could not be found. - AWSBIO028E
An incorrect limit "limit" was specified in the filter. - AWSBIO029E
An incorrect limit type "limit_type" was specified in the filter. - AWSBIO030E
An incorrect status "status" was specified in the filter. - AWSBIO031E
An incorrect recovery option "recovery_option" was specified in the filter. - AWSBIO032E
An incorrect prompt status "prompt_status" was specified in the filter. - AWSBIO033E
An internal system error occurred. - AWSBIO034E
An incorrect limit "limit" was specified for the job stream "job_stream". - AWSBIO035E
Unable to initialize HCL Workload Automation Connector plan auditing. - AWSBIO036E
Unable to initialize HCL Workload Automation Connector database auditing. - AWSBIO037E
Workstation "workstation" does not support the task type "task_type". - AWSBIO038E
A method options file or jobdef keyword was not found for task type "task_type" on workstation "workstation". - AWSBIO039E
The parameter "parameter" could not be found in the local parameters file. - AWSBIO040E
The supplied job stream alias "alias" cannot be used, because another job stream has been submitted in this plan instance with the same alias. - AWSBIO041E
The job cannot be submitted because the job or job alias "job_name_or_alias" already exists. - AWSBIO044E
The conditional dependency expression specified for the predecessor "object" is not valid. - AWSBIP - Connector messages
This section lists error and warning messages that might be issued by the connector component. - AWSBIP001E
A general failure occurred in file: !1 at line: !2. - AWSBIP002E
The object of type !1 is represented by a non-valid ID or handle in method !2 - AWSBIP003E
Either the object does not exist or its properties cannot be displayed with this Dynamic Workload Console version. - AWSBIP004E
An incorrect filter was encountered for the object type "object_type" in method "method_name" - AWSBIP005E
An incorrect timer language expression was found for object type !1 in method !2 - AWSBIP006E
Could not generate the timer language expression for object type !1 in method !2 - AWSBIP007E
Expected a different timer language expression format type for object type !1 in method !2 - AWSBIP008E
An incorrect resource type !1 was encountered in method !2 - AWSBIP009E
A nonexistent object !1 was referenced by the object ID or handle for object type !2 in method !3 - AWSBIP010E
Unable to send data to object type !1 in method !2 - AWSBIP011E
Workstation !1 not found. Using UNKNOWN task type. - AWSBIP012E
Workstation !1 not found, cannot find task type for job !2. Returning UNKNOWN as the task type. - AWSBIP013E
Job !1#!2 not found. Returning empty string for task type. - AWSBIP014E
Error generating audit record - AWSBIP015E
Unable to switch Symphony file. - AWSBIP016E
Operation not allowed while Symphony file is switched. - AWSBIR - Libraries messages
This section lists error and warning libraries messages that might be issued. - AWSBIR001E
<unknown symphony record> - AWSBIR100E
option requires an argument -- %c - AWSBIR101E
illegal option -- %c - AWSBIR102E
Cannot open file '%s' - AWSBIS - Customize messages
This section lists error and warning messages that might be issued by the customize component. - AWSBIS002E
An internal error has occurred. Customize failed to run the following UNIX command during the installation: "command" Correct the problem and rerun customize. - AWSBIS003E
The following HCL Workload Automation configuration file does not exist: "file_name". - AWSBIS009E
Customize could not create a symbolic link to the following program: "program". - AWSBIS010E
Customize could not create a symbolic link to the following program, because a link already exists: "program". - AWSBIS012W
User %s not found in /etc/passwd. Trying Yellow Pages. - AWSBIS013E
The user ID cannot be found in /etc/passwd and Yellow Pages (NIS). Either it is not installed or it is not accessible from the PATH system variable. - AWSBIS014E
The following user ID cannot be found in either /etc/passwd or the Yellow Pages: "user_name". - AWSBIS015E
The user running customize is not logged in as root. - AWSBIS016E
Customize cannot use the chown command. - AWSBIS017E
The following user ID, for which you want to install HCL Workload Automation, does not exist or does not belong to any group: "user_name". - AWSBIS020E
The supplied HCL Workload Automation home directory does not exist. - AWSBIS021E
An error occurred running one of the commands required for the installation.Determine which command had failed by examining the error messages issued previous to this one. Correct the problem and resubmit the command. - AWSBIS023E
Unable to install %s properly. - AWSBIS024E
Customize has been launched with the '-m <module_name> option incorrectly specified more than once. - AWSBIS025E
Customize has been issued with the following incorrect option: "option". - AWSBIS026E
The HCL Workload Automation home directory does not exist. - AWSBIS033E
An error occurred while trying to extract HCL Workload Automation from the following tar file: "tar_file_name". - AWSBIS034E
Customize encountered an error while installing HCL Workload Automation. Determine the details of the error by examining the error messages issued previous to this one. Correct the problem and rerun customize. - AWSBIS035E
Tar file %s.Z not found. Continuing with installation... - AWSBIS038E
Customize script for module %s could not be found. exiting ... - AWSBIS042E
Customize failed to decompress the following tar file: "tar_file_name". - AWSBIS044E
There is a syntax error in the customize options: -noexp should be specified only with a -new install - AWSBIS045E
There is a syntax error in the customize options: the -uname option is not followed by a user ID, or the supplied user ID commences with a hyphen. - AWSBIS046E
There is a syntax error in the customize options: either the -update and -new options have both been specified, or one of them has been specified more than once. - AWSBIS047E
There is a syntax error in the customize options: the -thiscpu option cannot be used with the -update option. - AWSBIS048E
There is a syntax error in the customize options: the -thiscpu option is not followed by a workstation name, or the supplied workstation name commences with a hyphen. - AWSBIS049E
There is a syntax error in the customize options: the -master <workstation_name> option can only be specified with -new option. - AWSBIS050E
There is a syntax error in the customize options: you are running a fresh installation (with the -new option) but have not supplied either the -master <workstation_name> option or the -thiscpu <workstation_name> option, which are both mandatory for a fresh installation. - AWSBIS051E
There is a syntax error in the customize options: the -master option is not followed by a workstation name, or the supplied workstation name commences with a hyphen. - AWSBIS052E
There is a syntax error in the customize options: the -netman option is not followed by a directory name, or the supplied directory name commences with a hyphen. - AWSBIS053E
The following supplied netman home directory cannot be found or is not a directory: "netman_home_directory". - AWSBIS054E
There is a syntax error in the customize options: the -company option is not followed by a company name, or the supplied company name commences with a hyphen. - AWSBIS055E
There is a syntax error in the customize options: the -execpath option is not followed by a path name, or the supplied path name commences with a hyphen. - AWSBIS056E
Error: Invalid option, specify -m <module-name> - AWSBIS057E
Error: Invalid option, specify -group <install-group> - AWSBIS058E
There is a syntax error in the customize options: you are running a fresh installation (with the -new option) but have not supplied either the -master <workstation_name> option or the -thiscpu <workstation_name> option, which are both mandatory for a fresh installation. - AWSBIS059E
Customize failed to decompress the following tar file: "tar_file_name". - AWSBIS060E
The following components directory identified in the UNISON_COMPONENT_FILE variable is not a directory, or does not exist: "directory_name". - AWSBIS061W
No component group name was provided. Using the following default group name: %s. - AWSBIS062E
An entry was found in the components file for the specified group, but it contained incorrect data. - AWSBIS063E
More than one entry was found in the components file either for the following specified location: "directory_name" or the following group: "group_name". - AWSBIS064W
HCL Workload Automation is installed under a different component group %s.Changing the component group name to be %s. - AWSBIS065W
You are trying to install HCL Workload Automation in the following location: "directory_name" under the following group: "group_name". However, there is already an instance installed in that location and group. - AWSBIS066E
HCL Workload Automation is already installed in %s. You can only update this installation. - AWSBIS067E
There is more than one entry for Netman in the same group. - AWSBIS068W
Netman is already installed in this group %s at location %s. - AWSBIS070E
The netman directory was not found. Copy the netman directory and run customize again - AWSBIS071E
Netman customize failed during execution. Correct the problem and run again. - AWSBIS072E
An error occurred while creating or updating the components file. - AWSBIS201E
Calendar %s already exists - AWSBIS202E
Calendar type is required. - AWSBIS203E
Unable to find home directory for TWS user - AWSBIS204E
Unable to read calendars from database - AWSBIS205E
Type %s calendars require the use of the TWS datecalc utility. - AWSBIS206E
Type %s calendars require a HOLIDAYS calendar to be predefined. - AWSBIS207E
Type %s calendars require a -s parameter. - AWSBIS208E
Your HCL Workload Automation license has expired. - AWSBIS235E
Day %s is not in range 1-31. - AWSBIS236E
Argument %s must be greater than zero. - AWSBIS237E
Argument %s is not in range 1-3. - AWSBIS238E
Incorrect option %s. - AWSBIS239E
One or more errors occurred. Calendars database not modified. See below. - AWSBIS240E
Failed to add new calendar to the database. - AWSBIS242W
New production period takes effect now. Waiting 20 seconds. - AWSBIS257E
No argument was supplied with -d. - AWSBIS258E
No argument was supplied with -i. - AWSBIS259E
No argument was supplied with -f. - AWSBIS260E
No argument was supplied with -p. - AWSBIS261E
No argument was supplied with -s. - AWSBIS262E
No argument was supplied with -r. - AWSBIS263E
No argument was supplied with -w. - AWSBIS264E
Calendars of type %s require the %s non-working days (freedays) calendar to be predefined. - AWSBIS273E
More than one calendar option has been specified.Rerun the command, selecting only one option from (-d|-e|-f|-l|-m|-p|-r|-w). - AWSBIS274E
Environment variable TEMP is not set.Set a valid value for TEMP and rerun the command. - AWSBIS275E
No argument was supplied with -freedays. Specify a valid calendar name. - AWSBIS276E
Cannot understand the NLS/Unknown format. Exiting. - AWSBIS277E
The non-working days (freedays) calendar %s is not found in the Symphony file. Run JnextPlan to make it available. - AWSBIS278E
There is a syntax error in the command. See the User's Guide and Reference for the correct syntax. - AWSBIS279E
Cannot determine the remote shell program. - AWSBIS280E
Cannot connect to %s. - AWSBIS281E
There is a syntax error in the command.See the User's Guide and Reference for the correct syntax. - AWSBIS283E
Cannot determine the remote shell program. - AWSBIS286E
There is a syntax error in the command. See the User's Guide and Reference for the correct syntax. - AWSBIS287E
Cannot connect to %s - AWSBIS288E
There is a syntax error in the command. See the User's Guide and Reference for the correct syntax. - AWSBIS290E
No files were found in the file set. - AWSBIS291E
Jobstdl failed running: %s. - AWSBIS299E
No argument was supplied with -day. - AWSBIS300E
No argument was supplied with -name. - AWSBIS301E
No argument was supplied with -num. - AWSBIS303E
There is a syntax error in the command. See the User's Guide and Reference for the correct syntax. - AWSBIS310E
at: You are not authorized to use the at command. - AWSBIS311E
batch: You are not authorized to use the batch command. - AWSBIS319E
rep8 was not found. - AWSBIS320E
The command failed while running %s. - AWSBIS326E
No stdlist directory was found. - AWSBIS329E
No netman stdlist was found in %s. - AWSBIS332E
No manual entry was found for %s. - AWSBIS335E
JnextPlan failed while running: %s. - AWSBIS338E
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm. - AWSBIS339E
File %s does not exist. - AWSBIS340E
There is a syntax error in the command. See the User's Guide and Reference for the correct syntax. - AWSBIS345E
An internal error has occurred. ResetPlan failed while running: %s. - AWSBIS346W
No Symphony file was found. - AWSBIS348E
An internal error has occurred. MakePlan failed while running: %s. - AWSBIS349E
An internal error has occurred. SwitchPlan failed while running: %s. - AWSBIS350W
The application server is not running. - AWSBIS358E
JnextPlan was canceled by user. - AWSBIS502E
at: You are not authorized to use the at command. - AWSBIT - Customize messages
This section lists error and warning messages that might be issued. - AWSBIT502E
You must be root to install HCL Workload Automation OpC integration. - AWSBIT507E
Cannot locate the master domain manager. The following value for MASTER %s must be a valid host name or IP address, do not use the HCL Workload Automation workstation name. - AWSBIT508E
Operations center not present on this system. - AWSBIT509W
Installing only event recognition. - AWSBIT510W
If not already done, this script should be run on the OpC management platform. - AWSBIT513E
Incorrect choice %s - AWSBIT514E
OpC 1.x is not supported on HP-UX 10.x - AWSBIT515E
Cannot determine the operating system version. Unable to define the OpenView environment variables. Exiting. - AWSBIU - NetView messages
This section lists error and warning Netview messages that might be issued. - AWSBIU001W
Magent already running. - AWSBIU102E
You must be root to decustomize TWS. - AWSBIU103E
Cannot determine OS version. Unable to define OpenViewenvironment variables. Exiting. - AWSBIU105E
Error: Action is only valid for TWS events - AWSBIU106E
Error: Action not defined for TWS trap %s - AWSBIU502E
You must be root to customize TWS - AWSBIU503E
Cannot reach node manager = %s. This must be a valid host nameor IP Address, do not use the HCL Workload Automation workstation name. - AWSBIU504E
openview does not exist on this system.You must specify -manager <host> to perform theinstallation on a node to be managed. - AWSBIU506E
%s already exists - AWSBIU516E
You must run ovaddobj to add the local registration file %s or run magent and mdemon some otherway. - AWSBIU522W
%s/trapd.conf has replaced the old file the previous version is in %s/trapd.conf.old - AWSBIU525W
Be sure to add an appropriate entry to each workstation's rhost - AWSBIU528W
will be managing from the management station. - AWSBIU529W
see documentation on remsh and .rhosts for further information. - AWSBIU530W
will install the agent reporting to %s - AWSBIU531W
changing ownership and permissions on agent - AWSBIU533E
/tmp/snmpd.peers contains the new version of /etc/snmpd.peers this file needs to be installed by you before you can start the agent. - AWSBIU534W
/etc/snmpd.peers has been replaced the old file is /etc/snmpd.peers.old - AWSBIU535E
/tmp/snmpd.conf contains the new version of /etc/snmpd.conf this file needs to be installed by you before you can start the agent. - AWSBIU536W
/etc/snmpd.conf has been replaced the old file is /etc/snmpd.conf.old - AWSBIU538E
/tmp/mib.defs contains the new version of /etc/mib.defs this file needs to be installed by you before you can start the agent. - AWSBIU539W
/etc/mib.defs has been replaced the old file is /etc/mib.defs.old - AWSBIU540W
After you have installed the changes to the system files you should refresh snmpd: refresh -s snmpd - AWSBIU544W
/tmp/StartUp contains the new version of %s/StartUp On managed nodes this file needs to be installed by you before you can start the agent. It will restart the agent every time Netman is restarted. - AWSBIU545W
%s/StartUp has been replaced - AWSBIU546W
You should now restart Netview/Openview and TWS - AWSBIU549E
Invalid choice %s. - AWSBIU550E
ERROR: OpenView 3.3 is not supported on HP-UX 10.x - AWSBIU551E
-client option can only be specified on AIX - AWSBIU552E
The trap definition file <maehome>/OV/mae.traps.hp must be loadedwith the following commands before you can process the unison traps: - AWSBIU553E
The trap definition file <maehome>/OV/mae.traps.aix must be loadedwith the following command before you can process the unison traps: - AWSBIU554E
The file %s is missing. This file is needed to configure theTWS subagent. - AWSBIU557E
Cannot determine OS version. Unable to define OpenViewenvironment variables. Exiting. - AWSBIV - messages
This section lists error and warning messages that might be issued. - AWSBIV001E
Command too long. - AWSBIV002E
Remote aborted connection without initiating protocol: %d. - AWSBIV003E
Remote aborted connection: %s - AWSBIV004E
Failed to shutdown input socket - AWSBIV006E
Can't get user name. - AWSBIV008E
Fork for input passing failed - AWSBIV009E
Error writing input to socket - AWSBIV010E
Error reading from standard input - AWSBIV011E
Error shuting input socket down - AWSBIV012E
Fork for output passing failed - AWSBIV013E
Error writing standard output - AWSBIV014E
Error passing standard output from socket - AWSBIV015E
Error shutting down output socket - AWSBIV016E
Error writing to standard error - AWSBIV017E
Error passing standard error from socket - AWSBIV018E
Failed to shutdown standard error socket - AWSBIV019E
Could not register TCP/IP cleanup function. - AWSBIV020E
Lookup of server hostname failed - AWSBIV021E
I/O socket creation failed: error=%d. - AWSBIV022E
Failed to connect to host - AWSBIV023E
Error: socket creation failed - AWSBIV024E
Error: socket bind failed - AWSBIV025E
Error: socket listen failed - AWSBIV026E
Error: socket accept failed - AWSBIX - Netman messages
This section lists error and warning Netman messages that might be issued. - AWSBIX002E
Customize failed executing: %s. Please correct the problem and rerun customize. - AWSBIX003E
FILE:%s does not exist. - AWSBIX006W
User %s not found in /etc/passwd. Trying yellow pages. - AWSBIX007E
Yellow Pages not installed or not accessible in PATH. - AWSBIX008E
User %s not found in yellow pages. - AWSBIX009E
You must be root to customize Netman. - AWSBIX012E
ERROR: Reading components file. - AWSBIX013W
More than one Netman entry in components file for location %s or group %s. - AWSBIX014W
There is a netman is installed in %s under group %s. - AWSBIX015W
There is already a netman installed in %s. This netman is updated. - AWSBIX016E
Cannot determine the location of chown. - AWSBIX017E
The user %s must exist in order for the install to succeed. Please check the install instructions in the HCL Workload Automation User Manual. - AWSBIX018E
Netman home %s does not exist. - AWSBIX019E
'netman' directory tree exists partially or does not exist. Files have not been extracted from tape correctly. - AWSBIX020E
ERROR: Error occured while creating/updating product components file. - AWSBIX021E
An error occured executing commands.Please check the error condition and correct any problems and rerun customize. - AWSBIY - Demo scripts messages
This section lists error and warning Demo scripts messages that might be issued. - AWSBIY001W
Running the sample database setup deletes all job streams and jobs with the prefix SMPL from the database. - AWSBIZ - Batchup messages
This section lists error and warning Batchup messages that might be issued. - AWSBIZ001E
Error: CreateProcess failed. - AWSBIZ002E
Error: system failed. - AWSBIZ004E
%s does not exist. - AWSBJB - messages
This section lists router error and warning messages that might be issued. - AWSBJB006E
Error processing the message: !1 - AWSBJB008E
Adapter error: !1 - AWSBJB010E
Error opening stdlist and debug file - AWSBJB012E
Catalog error - AWSBJB013E
Error in COMAREA of Maestro - AWSBJB014E
Error openig clbox.msg - AWSBJB015E
Cannot open the Synphony file - AWSBJB016E
Cannot read the master CPU - AWSBJB019E
Error bulk discovery : !1 - AWSBJB022E
Adding job:!1, error: !2 - AWSBJB024E
Adding schedule:!1, error: !2 - AWSBJB026E
Modifying job:!1, error: !2 - AWSBJB028E
Modifying schedule:!1, error: !2 - AWSBJB029E
Send event error: !1 - AWSBJB030E
Error openig clevbox.msg - AWSBJB220E
Job !1 is in failed status - AWSBJG - Router messages
This section lists router error and warning messages that might be issued. - AWSBJG001E
Router cannot initialize the communication or set the connection type and file descriptor for the connected socket to make an SSL connection to conman. The following error message is given: "error_message" - AWSBJG002E
Router is unable to create the stdlist file. - AWSBJG004W
Warning illegal timeout value: !1, using default - AWSBJG005E
Router has been invoked with an incorrect number of arguments. - AWSBJG006E
Router cannot perform the data translation between network format and host format required for SSL communication. (ntoh). The following error message is given: "error_message" - AWSBJG007E
Router cannot send router packets on the network. The following error message is given: "error_message" - AWSBJG008E
Router cannot receive router packets from the network. The following error message is given: "error_message" - AWSBJG009E
Router ran out of memory allocating memory for internal data structures (comarea). - AWSBJG011E
Scribner, called by router, cannot read the standard list file (stdlist) for the following job: "workstation_name"."job_stream_name": "job_name" - AWSBJG012E
Router cannot open or read the Symphony file. - AWSBJG015E
The following error occurred opening the configuration file "file_name": "error_message". - AWSBJG016E
An error occurred reading the configuration file "file_name": "error_message". - AWSBJG017E
An error occurred while closing the configuration file "file_name": "error_message". - AWSBJH - Migration messages
This section lists error and warning migration messages that might be issued. - AWSBJH005E
The datamigrate parameter "parameter" has been supplied more than once. - AWSBJH006E
An incorrect value has been supplied for a parameter. - AWSBJH009E
More than one object type parameter has been supplied. - AWSBJH011E
The parameter "parameter" is not a recognized datamigrate parameter. - AWSBJH012E
One or more required parameters of the datamigrate command have not been supplied. - AWSBJH013E
Two or more incompatible parameters of the datamigrate command have been supplied. - AWSBJH014E
The supplied input file "input_file" does not exist. - AWSBJH016E
The supplied "prev_install_dir" does not identify a previous instance of HCL Workload Automation from which to import data. - AWSBJH018E
The temporary directory "temporary_directory" does not exist. - AWSBJH022E
The import of object type "object_type" has failed. - AWSBJH023W
The import of object type "object_type" has completed with one or more warnings. - AWSBJH024W
No object of type "object_type" has been found. - AWSBJH026E
The import of object type "object_type" has completed with one or more errors. - AWSBJH029E
The supplied input file !1 is not readable by the user !2 that is performing the data migration. - AWSBJH031E
The application server is not running. The import cannot continue. - AWSBJH035E
The migration was unable to export the data from the previous instance of HCL Workload Automation, because it could not copy the dataexporter program into the directory: "directory". - AWSBJH104E
The supplied object type "incorrect_object_type"is not a recognized object type. - AWSBSM - TBSM Event Forwarder plug-in messages
This section lists error and warning messages that might be issued. - AWSBSM102E
The HCL Workload Automation event "event" has not been forwarded to the IBM Business Services Manager Console server. The return code is: "return_code". - AWSBSM103E
The HCL Workload Automation event has not been forwarded to the IBM Business Services Manager Console server. The reason is: "reason". - AWSBSM104E
The action type "action_type" is not supported. - AWSBSM105E
The HCL Workload Automation event has been not forwarded to the IBM Business Services Manager Console server because the IBM Business Services Manager Console agent has not been initialized. - AWSBWX - Dataxtract messages
This section lists error and warning messages that might be issued by dataxtract. - AWSBWX002E
An error has occurred opening the file "file_name" for writing. - AWSBWX003E
An error has occurred opening the file "file_name" for reading. - AWSBWX004E
An error has occurred writing the file "file_name". - AWSBWX005E
An error has occurred renaming the file "file_name" in "file_name_renamed". - AWSBWX006W
An error occurred while creating the directory "directory". The book file is created in the default directory "default_directory". - AWSBWX007W
An error occurred opening the file "file_name" for writing. The book file is created in the default directory "default_directory". - AWSCCM - CCMDB integration messages
This section lists error and warning messages that might be issued by the CCMDB integration.. - AWSCCM002W
The workstation "workstation" has not been added in the book file. Cannot resolve the host name or host address. - AWSCCM003W
Zos workstation file "file" has not been found. - AWSCCM004W
Zos jobstreams file "file" has not been found. - AWSCCM005W
Zos jobs file "file" has not been found. - AWSCDW - Clustering messages
This section lists error and warning messages that might be issued when using the Windows clustering facility. - AWSCDW002E
The cluster service is installed and configured on the node "node_name", but is not currently running. - AWSCDW003E
The cluster service is not installed on the node. - AWSCDW004E
The cluster service is installed on the node but has not yet been configured. - AWSCDW005E
An internal error has occurred. The program cannot read the cluster information. - AWSCDW006E
An error has occurred opening the cluster "cluster_name". - AWSCDW007E
The program cannot identify the available nodes on the cluster. - AWSCDW010E
The program cannot install the remote service "service_name" on node : "node_name". - AWSCDW011E
The program cannot save the registry key on the node "node_name". - AWSCDW013E
The program cannot copy the file "file_name" to "dest_name". - AWSCDW015E
The program cannot register the cluster dll, and so cannot install the HCL Workload Automation resource. - AWSCDW017E
The program cannot open the cluster object "object_name". - AWSCDW018E
The program cannot add the HCL Workload Automation cluster resource to the group. - AWSCDW019E
An internal error has occurred. The program cannot convert a string to or from UNICODE characters. - AWSCDW020E
An internal error has occurred. The program cannot locate the Windows common directory. - AWSCDW021E
The program cannot obtain the <TWSHome> directory from the HCL Workload Automation Windows services. Check that the values for the domain and user parameters are valid. - AWSCDW022W
The program cannot add the "key_name" key into the localopts file. Add the key manually. - AWSCDW023W
The program cannot modify the local security policy on the target host. - AWSCDW026W
The program cannot remove the HCL Workload Automation cluster service on the node "host_name". - AWSCDW027W
The program cannot remove the HCL Workload Automation registry key on the node "host_name". - AWSCDW028W
The program cannot check whether the custom HCL Workload Automation cluster resource type is already installed. - AWSCDW029E
The program cannot determine the Windows boot disk from the remote registry on the node "host_name". - AWSCDW031E
The program cannot determine the version of the custom HCL Workload Automation cluster resource type dll. - AWSCDW034E
The program cannot determine the path to the custom HCL Workload Automation cluster resource type dll. - AWSCDW035E
The program cannot update the custom HCL Workload Automation cluster resource type dll. - AWSCDW036W
The program cannot delete the temporary file "dll_temp_file_name". - AWSCDW037W
The custom HCL Workload Automation cluster resource type dll to be installed is older than the dll currently installed. Press ESC to exit from the installation or any key to continue.Note: during the upgrade the custom HCL Workload Automation cluster resource might be restarted. - AWSCDW039W
The program cannot create the script to start or stop the HCL Workload Automation custom cluster resource instance. - AWSCDW042E
The command-line parameter "parameter" is not correct. - AWSCDW043E
The context of the supplied command line string "command_line"indicates that a pair of quotation symbols (') is required. However, the first of the pair is missing. - AWSCDW044E
The context of the supplied command line string "command_line" indicates that a pair of quotation symbols (') is required. However, the last of the pair is missing. - AWSCDW045E
The command-line parameter "parameter" is mandatory. - AWSCDW046E
The command-line parameter "parameter" has been supplied with a value "parameter_value" that is outside the permitted range "range_value". - AWSCDW047W
The password cannot be validated. Either you have specified an incorrect password or the program cannot validate it (probably because it does not have the correct permission to do so). - AWSCDW048E
You cannot install HCL Workload Automation in this cluster environment. The only supported environment is the Microsoft Cluster service on Windows Server 2003. - AWSCDW049W
The user "user_ID" was not found. Press ESC to exit from the installation or any key to continue. - AWSCDW050E
The operation cannot be completed because a HCL Workload Automation cluster resource called "cluster_resource_name" already exists, and also points to this HCL Workload Automation agent. - AWSCDW051E
A cluster resource with the name "cluster_resource_name" already exists. Choose a different resource name. - AWSCDW052E
The operation to rename the cluster resource "current_cluster_resource_name" in "new_cluster_resource_name" has failed. - AWSCDW054E
The program cannot obtain the HCL Workload Automation home directory from the "cluster_resource_name" cluster resource. - AWSCDW055E
You have not specified the parameter collect or deploy options. - AWSCDW056E
You did not provide data archive name. - AWSCDW057E
There was an error in generating data archive. - AWSCDW061E
Error deploying the data archive. - AWSCDW071E
You have specified a data archive name that does not exist. - AWSCDW072E
You have specified an incorrect parameter: "param_name" - AWSCDW075W
The agent cannot be installed because the combination of parameters specified is not supported. - AWSCDW077E
No agent is available for installation. - AWSCDW078E
Unable to install the dynamic agent: the agent was not found. - AWSDDW - Std utility messages
This section lists std utility error and warning messages that might be issued. - AWSDDW002E
Unable to build stdlist directory !2. Errno = !1. - AWSDDW008E
An I/O error occurred while accessing a file. A memory dump has been taken to aid HCL Software Support with problem determination. - AWSDDW051E
Unknown product id <!1> found. - AWSDDW052E
Product '!1' is not installed under the group '!2'. - AWSDDW053W
No '!1' found in components file installed under '!2'. - AWSDDW071E
You specified an invalid product. - AWSDEB - SSL messages
This section lists error and warning messages that might be issued when using SSL. - AWSDEB009E
Data transmission is not possible because the connection is broken. The following gives more details of the error: "error_message". - AWSDEB010E
An error occurred in gethostbyname: "error_message" (getting the host IP address using the host name). - AWSDEB011E
The socket descriptor is incorrect. The following gives more details of the error: "error_message". - AWSDEB016E
An internal error has occurred. The data structure area (comarea) cannot be initialized (is null). - AWSDEB017E
The internal data structure area (comarea) cannot be initialized (memory error). - AWSDEB024E
An internal error has occurred. The program could not access the internal data structure (comarea) while opening the socket or accepting a connection in the socket descriptor sockfd (part of comarea). The following gives more details of the error: "error_message". - AWSDEB025E
An internal error has occurred. The program cannot set the linger socket option. The following gives more details of the error: "error_message". - AWSDEB026E
An internal error has occurred. Cannot set the reuseaddr socket option. The following gives more details of the error: "error_message". - AWSDEB027E
Error setting close on exec/uninherit flag: !1 - AWSDEB028E
Error opening os handle: !1 - AWSDEB045E
An error has occurred during the creation of the local SSL context. The following gives more details of the error: "error_message". - AWSDEB046E
An error has occurred during the SSL handshaking. The following gives more details of the error: "error_message". - AWSDEB047E
The program could not access the localopts local options file. - AWSDEB048E
An internal error has occurred. HCL Workload Automation network processes (mailman, writer, netman or scribner) are unable to use the previously allocated SSL context. - AWSDEB049E
The counterparty workstation did not present an SSL peer certificate, or no connection was established. - AWSDEB051E
The program cannot authenticate the SSL peer certificate: the requested level is not matched. - AWSDEB052E
An error occurred in getaddrinfo: "error_message" (getting the host IP address using the host name). - AWSDEB053E
FIPS cannot be enabled. The connection is not possible. - AWSDEB054E
An error occurred during an SSL connection using the OpenSSL Toolkit. - AWSDEB055E
An error occurred during an SSL connection using the GSKit libraries. - AWSDEB056E
An error occurred a SSL connection using the OpenSSL Toolkit. The connection can not be accepted. - AWSDEB057E
An error occurred a SSL connection using the GSKit libraries.The connection can not be accepted. - AWSDEB058E
An error occurred during the initialization of the ICC module in FIPS mode. Encryption is not possible. - AWSDEB059E
An error occurred during the initialization of the GSKit module in FIPS mode. The configuration is not correct. Check the configuration in the localopts file. - AWSDEB060E
An error occurred during the initialization of the OpenSSL Toolkit. The configuration is not correct. Check the configuration in the localopts file. - AWSDEC - Events file messages
This section lists events file error and warning messages that might be issued. - AWSDEC001E
File system error !1 on events file. - AWSDEC002E
An internal error has occurred. The following UNIX system error occurred on an events file: "error_number" at line = "line". - AWSDEC004E
IPC error !1 on events file. - AWSDEC005E
DB error !1 on events file. - AWSDEC006E
The program was unable to allocate an internal data structure area (comarea). - AWSDEC008E
An event file was created by a newer version of HCL Workload Automation than this version, and is not compatible. - AWSDEC009E
An event file cannot be opened because it has been already opened by another process. - AWSDEC010E
An internal error has occurred. The open access mode is not valid: "access_mode". - AWSDEC011W
The time-out interval for messages arriving in an event file has elapsed. - AWSDEC012E
An internal error has occurred. The internal data structure area (comarea) for event file processing could not be initialized. - AWSDEC014E
The event file or the directory containing the event file does not exist or cannot be found. - AWSDEC015E
An internal error has occurred. The length ("record_length") of a record read from or written to the event file is not correct. - AWSDEC018E
An internal error occurred while attempting to compact the file "event_file". The file is unusable. - AWSDEC019W
The supplied maximum size of the file "event_file" is "max_size" bytes, which is too small. A higher value will be allocated. - AWSDEC020W
The maximum size of the file "event_file" has been changed to "max_size" bytes. - AWSDEC100E
An internal error has occurred. While processing an event file an error ("error_number") of type ("error_type") occurred. - AWSDED - Date calculation messages
This section lists error and warning messages that might be issued by the date calculation. - AWSDED001E
internal error: time() failed - AWSDED002E
An internal error has occurred: mktime() failed. - AWSDED003E
An internal error has occurred: localtime() failed. - AWSDED004E
An internal error has occurred: gmtime() failed. - AWSDED005E
An internal error has occurred: strftime() failed. - AWSDED006E
SCHEDDATE contains a non-valid date. - AWSDED007E
SCHEDDATE is null. - AWSDED008E
The date specification is not correct. - AWSDED009E
The time specification is not correct. - AWSDED010E
The date specification is ambiguous. - AWSDED011E
The input is too long. - AWSDED012E
The number is too long. - AWSDED013E
The identifier name is too long. - AWSDED014E
The output format string is too long. - AWSDED015E
No date or time has been specified. - AWSDED016E
An internal error has occurred: malloc() failed. - AWSDED017W
Warning: setlocale() has failed...continuing with the C language. - AWSDED018E
The offset specification is not valid. - AWSDED019E
The output format specification is not valid. - AWSDED020E
The input specification is not valid. - AWSDED022E
Calendar name !1 is too long - AWSDED023E
An error occurred while opening the Symphony file. - AWSDED024E
An internal problem has occurred. - AWSDED025E
An error has occurred reading dates from the calendar !1: !2. - AWSDED026E
The offset expression exceeds the first date in the calendar !1. - AWSDED027E
The offset expression exceeds the last date in the calendar !1. - AWSDED028E
The month is not valid. The date must conform to the input format !1 specified in unison.msg. [0-YMD, 1-MDY, 2-DMY]. - AWSDED029E
The day is not valid. The date must conform to the input format !1 specified in unison.msg. [0-YMD, 1-MDY, 2-DMY]. - AWSDEF - messages
This section lists error and warning messages that might be issued. - AWSDEF001E
Can not acquire heap. - AWSDEF002E
On IPCDEST: !1 - AWSDEF003E
On IPCONNECT: !1 - AWSDEF004E
On IPCRECV: !1 - AWSDEF005E
On setting timeout: !1 - AWSDEF006E
On IPCREVCVCN: !1 - AWSDEF007E
On IPCGIVE: !1 - AWSDEF008E
On IPCGET: !1 - AWSDEF009E
This is not an IPC comarea. - AWSDEF011E
On IPCSEND: !1 - AWSDEF012E
On IPCCREATE: !1 - AWSDEF013E
Unknown call: !1 - AWSDEF014E
On IPCRECV: !1 - AWSDEF015E
Timed out. !1 - AWSDEJ - Security messages
This section lists security error and warning messages that might be issued. - AWSDEJ001E
The Security file is not valid. - AWSDEJ002E
The internal data structure area (comarea) could not be initialized. - AWSDEJ003E
Doing !1 on !2, action not defined. - AWSDEJ004E
An internal error occurred performing the following action: "action" on the following object type: "object_type". - AWSDEJ005E
You do not have permission to perform the following action: "action" on the following object type: "object_type". - AWSDEJ007E
A system error occurred while performing the following action: "action" on the following object type: "object_type". The Security file might be corrupt. - AWSDEJ008E
A system error occurred while performing the following action: "action" on the following object type: "object_type". The Security file might be corrupt. - AWSDEJ009E
An internal error occurred while performing the following action: "action" on the following object type: "object_type". The Security file might be corrupt. - AWSDEJ010E
A system error occurred while performing the following action: "action" on the following object type: "object_type". The Security file might be corrupt. - AWSDEJ011E
A decryption error occurred while performing the following action: "action" on the following object type: "object_type". The Security file might be corrupt. - AWSDEJ012E
An internal error occurred while performing the following action: "action" on the following object type: "object_type". - AWSDEJ013E
A non-valid keyword was encountered in the Security file while performing the following action: "action" on the following object type: "object_type". The Security file might be corrupt. - AWSDEJ014E
The following user: "user_name" could not be found in the Security file while performing the following action: "action" on the following object type: "object_type". The Security file might be corrupt. - AWSDEJ015E
The record for the following user: "user_name" could not be read in the Security file while performing the following action: "action" on the following object type: "object_type". The Security file might be corrupt. - AWSDEJ016E
An internal error occurred while performing the following action: "action" on the following object type: "object_type". - AWSDEJ017E
Doing !1 on !2, testing user found invalid object in security file. - AWSDEJ018E
The following user: "user_name" could not be found in the Security file while performing the following action: "action" on the following object type: "object_type". The Security file might be corrupt. - AWSDEJ019E
An error occurred while reading the header in the Security file for the following user: "user_name". The Security file might be corrupt. - AWSDEJ020E
An error occurred while setting the initial position in the Security file for the following user: "user_name". The Security file might be empty or corrupt. - AWSDEJ021E
The Security file is not valid (incorrect magic number). - AWSDEJ022E
The Security file is not valid (incorrect version). - AWSDEJ023E
The Security file is not valid (header record size is incorrect). - AWSDEJ024E
The program could not allocate sufficient memory (heap size). - AWSDEJ025E
The Security file is missing. As the user is not root, the file cannot be created by the program. - AWSDEJ026E
An error occurred while seeking the start position of the Security file. The following operating system error was returned: "error_number". The Security file might be corrupt. - AWSDEJ027E
Either the user for which authorization is being sought is not defined in the Security file, or it is defined but no associated access rights are defined. The Security file is probably either empty or corrupt. - AWSDEJ028E
An error has occurred while retrieving the password structure from the Security file. The file might be corrupt. - AWSDEJ029E
The following action cannot be performed in an end-to-end HCL Workload Automation network: "action" on the following object type: "object_type". - AWSDEJ101E
Error writing user: !4 - AWSDEJ102W
While running makesec, a syntax error was found in the following file: "file_name", at line: "line_number". An incorrect delimiter has been used after the following keyword: "keyword". - AWSDEJ103W
While running makesec, a possible issue was found in the following file: "file_name", at line: "line_number". The tilde delimiter (~) has been used before the first attribute for the following user: "user_name". This means that all physical users of all workstations in the HCL Workload Automation network, except that or those indicated in the attribute, now belong to the indicated user, and have the rights and restrictions of the indicated user. If this was your intention, take no action, otherwise correct the syntax and remake the security file. - AWSDEJ104E
!1, line !2: Error writing begin for !3: !4 - AWSDEJ105E
!1, line !2: Error writing end for !3: !4 - AWSDEJ106E
An internal user-seek error has occurred while writing the Security file. The error occurred while reading from the following file: "file_name", at line: "line_number", for the following user: "user_name". The following gives more details of the error: "error_message". - AWSDEJ107E
An internal user-update error has occurred while writing the Security file. The error occurred while reading from the following file: "file_name", at line: "line_number", for the following user: "user_name". The following gives more details of the error: "error_message". - AWSDEJ108E
While running makesec, a wrong exit state was found in the following file: "file_name", at line: "line_number". Either there is a syntax error in the Security.conf file or an internal error has occurred. - AWSDEJ109E
!1, line !2: Unknown variable: !3. - AWSDEJ110E
While running makesec, a syntax error was found in the following file: "file_name", at line: "line_number". The following incorrect keyword was used: "keyword". Contextually valid keywords are as follows: "keyword_list". - AWSDEJ111E
An internal security-buffer error has occurred while writing the Security file. The error occurred while reading from the following file: "file_name", at line: "line_number", for the following user: "user_name". The following gives more details of the error: "error_message". - AWSDEJ112W
An internal error has occurred while writing the Security file. The error occurred while reading from the following file: "file_name", at line: "line_number". One of the following keywords is missing: "keyword_list". - AWSDEJ113E
An internal error has occurred while writing the Security file. The error occurred while reading from the following file: "file_name", at line: "line_number". An non-valid parse state occurred while processing the following keyword: "keyword". - AWSDEJ114E
While running makesec, a syntax error was found in the following file: "file_name", at line: "line_number". The following keyword is not being used in the correct context: "keyword". - AWSDEJ115E
The same user ("user_name") is defined more than once in the following file: "file_name", at line: "line_number". - AWSDEJ116E
The following user name "user_name" is not valid in the following file: "file_name", at line: "line_number". - AWSDEJ117E
An internal error occurred while writing the Security file header record for the following user: "user_name" and the following action: "action". - AWSDEJ201E
The Security file is not valid. An error occurred reading the user at the following byte: "byte". - AWSDEJ202E
The Security file is not valid. An error occurred reading the block at the following byte: "byte" - AWSDEJ203E
The Security file is not valid. The object keyword at the following byte is not valid: "byte" - AWSDEJ204E
The Security file is not valid. The user attribute at the following byte is not valid: "byte" - AWSDEJ205E
The Security file is not valid. The variable at the following byte is not valid: "byte" - AWSDEJ206E
The Security file is not valid. The action keyword at the following byte is not valid: "byte" - AWSDEJ207E
An internal error has occurred while writing the Security file. The error occurred while reading from the following file: "file_name", at line: "line_number", for the following user: "user_name". The following gives more details of the error: "error_message". - AWSDEK - Miscellaneous command messages
This section lists miscellaneous command error and warning messages that might be issued. - AWSDEK051E
Options must precede arguments, use -- to close options. - AWSDEK052E
An option was not valid. - AWSDEK053E
An option was ambiguous. - AWSDEK054E
An option was not found. - AWSDEK101E
Error accessing !1: !2 - AWSDEK102E
An error occurred while rebuilding !1: !2. - AWSDEK301E
Error opening work file !1: !2 - AWSDEK302W
Warning verify over rides other options. - AWSDEK303W
Warning output over rides other options. - AWSDEK304W
Warning local over rides network option. - AWSDEK305E
Error opening security file !1: !2 - AWSDEK306E
Error writing header: !1 - AWSDEK308E
Error renaming !1 to !2: !3 - AWSDEK310E
Conversion of !1 from native format to utf8 failed. - AWSDEK401E
Error reading header: !1 - AWSDEK402E
Can not access current security file: !1 - AWSDEK404E
Unable to open utf8 temporary file !1. - AWSDEK405E
Unable to read utf8 security output file !1. - AWSDEK406E
Error writing security file !1 to the screen. - AWSDEK701E
Cannot open file %s, error: %s. - AWSDEK704E
The message queue "event_file" cannot be resized without being compacted. Make a backup copy and then compact the file by running evtsize -compact "event_file" . Refer to the documentation for more details. - AWSDEK705E
An error occurred while processing the file "event_file". The error is: "error_message". - AWSDEK706E
An error occurred while attempting to processing the file "event_file". The error is: "error_message". The original event file has been recovered. - AWSDEK708E
The message queue "event_file" cannot be re-sized without corrupting the contents. - AWSDEK709E
The supplied value for the size parameter is greater than the maximum allowed by the operating system: "max_size" - AWSDEK710W
The evtsize command has been issued with too many parameters. Additional parameters are ignored. - AWSDEK711E
The minimun size of a message queue must be "min_size" - AWSDEK904E
Unable to open the following Security file to initialize centralized security: "security_file". The file does not exist or cannot be found. - AWSDEK905E
Unable to read the following Security file for centralized security: "security_file". - AWSDEK906E
Unable to write the following Security file for centralized security: "security_file". - AWSDEM - Workstation parsing messages
This section lists workstation parsing error and warning messages that might be issued. - AWSDEM001E
There is an error in the workstation definition. The workstation definition for the cpuname keyword is not syntactically correct. It must start with an alphabetic character, followed by up to 15 alphanumeric bytes, including dashes and underscores. The Reference Manual lists certain reserved words that must be avoided. - AWSDEM002E
There is an error in the workstation definition. The workstation name for the host keyword is not syntactically correct. It must start with an alphabetic character, followed by up to 15 alphanumeric bytes, including dashes and underscores. The Reference Manual lists certain reserved words that must be avoided. - AWSDEM003E
LINK cpuid is syntactically invalid - AWSDEM004E
There is an error in the workstation definition. The server ID is not syntactically correct. It must be a single letter or number (A-Z and 0-9). - AWSDEM007E
There is an error in the workstation definition. The required os keyword is missing. - AWSDEM008E
There is an error in the workstation definition. The required node keyword is missing. - AWSDEM009E
There is an error in the workstation definition. The required os keyword has been specified more than once. - AWSDEM010E
There is an error in the workstation definition. The optional description keyword has been specified more than once. - AWSDEM011E
There is an error in the workstation definition. The required node keyword has been specified more than once. - AWSDEM012E
There is an error in the workstation definition. The optional tcpaddr keyword has been specified more than once. - AWSDEM013E
There is an error in the workstation definition. The host keyword has been specified more than once. - AWSDEM014E
There is an error in the workstation definition. The ignore keyword has been specified more than once. - AWSDEM015E
There is an error in the workstation definition. The autolink keyword has been specified more than once. - AWSDEM016E
There is an error in the workstation definition. The fullstatus keyword has been specified more than once. - AWSDEM017E
There is an error in the workstation definition. The resolvedep keyword has been specified more than once. - AWSDEM018E
There is an error in the workstation definition. The server keyword has been specified more than once. - AWSDEM019E
Duplicate alternative NODE keyword - AWSDEM020E
Duplicate alternative TCPADDR keyword - AWSDEM021E
Duplicate COMMAND keyword - AWSDEM022E
There is an error in the workstation or the workstation class definition. The context suggests that you are trying to define a workstation or a workstation class, but the cpuname or cpuclass keyword is missing. - AWSDEM023E
There is an error in the object definition. The supplied description keyword was not followed by a description enclosed in double quotes. - AWSDEM024E
There is an error in the workstation definition. The supplied os keyword was not followed by a valid operating system type. Valid options are UNIX, WNT, ZOS, IBM_i, or OTHER. - AWSDEM025E
There is an error in the workstation definition. The supplied node keyword was not followed by a valid host name or IP address. - AWSDEM026E
There is an error in the workstation definition. The supplied tcpaddr keyword is not set to a valid TCP port number. - AWSDEM027E
There is an error in the workstation definition. A maestro-type keyword has been included, but the for maestro keyword has not been supplied. - AWSDEM028E
There is an error in the workstation definition. The supplied host keyword was not followed by a valid workstation name. - AWSDEM029E
There is an error in the workstation definition. The supplied autolink keyword was not followed by either on or off. - AWSDEM030E
There is an error in the workstation definition. The supplied fullstatus keyword was not followed by either on or off. - AWSDEM031E
There is an error in the workstation definition. The supplied resolvedep keyword was not followed by either on or off. - AWSDEM032E
There is an error in the workstation definition. The supplied server keyword was not followed by a valid server ID. The server ID must be a single letter or number (A-Z and 0-9). - AWSDEM033E
Missing or invalid LINKTO cpuid - AWSDEM034E
Expected LINKTO cpu details - AWSDEM035E
Expected command(s) enclosed in quotes. - AWSDEM036E
There is an error in the workstation definition. One or more of the following keywords has not been supplied: description, licensetype, os, node, tcpaddr, timezone or vartable. - AWSDEM037E
There is an error in the workstation definition. The end keyword has been found but no for maestro parameters have been included. - AWSDEM038E
There is an error in the workstation definition. A new workstation definition has started or the end of file has been reached, but the end keyword for the previous definition is missing. - AWSDEM039E
There is an error in the workstation class definition. The workstation class name for the cpuclass keyword is not syntactically correct. It must start with an alphabetic character, followed by up to 15 alphanumeric bytes, including dashes and underscores. The Reference Manual lists certain reserved words that must be avoided. - AWSDEM040E
There is an error in the workstation class definition. A workstation name in the members keyword is not syntactically correct. All workstation names must start with an alphabetic character, followed by up to 15 alphanumeric bytes, including dashes and underscores. Alternatively, the @ wildcard must be used to indicate all workstations. - AWSDEM041E
There is an error in the workstation class definition. The supplied cpuclass keyword is not followed by the required members keyword. - AWSDEM042E
There is an error in the workstation class definition. All workstation names in the members keyword must start with an alphabetic character, followed by up to 15 alphanumeric bytes, including dashes and underscores. Alternatively, the @ wildcard must be used to indicate all workstations. - AWSDEM043E
There is an error in the workstation class definition. After the workstation class name definition, one or more member workstations have been supplied without the required members keyword. - AWSDEM044E
There is an error in the workstation class definition. The required members keyword has been specified more than once. - AWSDEM045E
There is an error in the workstation definition. The access keyword was not followed by a valid method. Valid methods correspond with the name of a file in the <TWShome>/methods directory (the file need not be present when the access method is defined). - AWSDEM046E
There is an error in the workstation definition. The access keyword has been specified more than once. - AWSDEM047E
There is an error in the workstation definition. The access keyword was not followed by a valid method. Valid methods correspond with the name of a file in the <TWShome>/methods directory (the file need not be present when the access method is defined). - AWSDEM048E
There is an error in the domain definition. The context suggests that you are trying to define a domain, but the domain keyword is missing. - AWSDEM049E
There is an error in the workstation or domain definition. The domain keyword has been specified more than once. - AWSDEM051E
There is an error in the workstation or domain definition. The domain keyword was not followed by a valid domain name. - AWSDEM052E
There is an error in the domain definition. Neither the manager nor the parent keywords have been found. - AWSDEM053E
There is an error in the domain definition. The parent keyword has been supplied more than once. - AWSDEM054E
There is an error in the domain definition. The manager keyword was not followed by a valid manager name. - AWSDEM055E
There is an error in the domain definition. The manager keyword has been supplied more than once. - AWSDEM056E
There is an error in the domain definition. The manager keyword was not followed by a valid manager name. Manager name must be a valid workstation name, which must start with an alphabetic character, followed by up to 15 alphanumeric bytes, including dashes and underscores. - AWSDEM057E
There is an error in the domain definition. The parent keyword was not followed by a valid parent name. Parent name must be a valid workstation name, which must start with an alphabetic character, followed by up to 15 alphanumeric bytes, including dashes and underscores. - AWSDEM058E
There is an error in the domain definition. The required manager keyword has not been supplied. - AWSDEM059E
There is an error in the workstation definition. The type keyword is not followed by a valid workstation type. Valid values are fta, manager, s-agent, x-agent, and broker. - AWSDEM060E
There is an error in the workstation definition. The type keyword has been supplied more than once. - AWSDEM061E
There is an error in the workstation definition. The type keyword is not followed by a valid workstation type. Valid values are manager, fta, s-agent, x-agent, broker, agent, pool, d-pool, and rem-eng. - AWSDEM062E
There is an error in the domain definition. The parent keyword is not followed by a valid parent domain name. - AWSDEM063E
There is an error in the domain definition. The description keyword is not followed by a valid description. - AWSDEM064E
There is an error in the workstation definition. The timezone keyword has been supplied more than once. - AWSDEM065E
There is an error in the workstation definition. The timezone keyword is not followed by a valid timezone name. Valid timezone names are listed in the Reference Guide. - AWSDEM066E
There is an error in the workstation definition. The timezone name is too long (maximum 40 bytes). Valid timezone names are listed in the Reference Guide. - AWSDEM067E
There is an error in the workstation definition. The timezone keyword is not followed by a valid timezone name. Valid timezone names are listed in the Reference Guide. - AWSDEM068E
There is an error in the workstation definition. The timezone keyword is not followed by a valid timezone name. Valid timezone names are listed in the Reference Guide. - AWSDEM069E
There is an error in the workstation definition. The timezone keyword is not followed by a valid timezone name. Valid timezone names are listed in the Reference Guide. - AWSDEM070E
There is an error in the workstation definition. The behindfirewall keyword is not followed by a valid value. Valid values are on or off. - AWSDEM071E
There is an error in the workstation definition. The behindfirewall keyword is supplied more than once. - AWSDEM072E
There is an error in the workstation definition. The securitylevel keyword is supplied more than once. - AWSDEM073E
There is an error in the workstation definition. The securitylevel keyword is not followed by a valid value. Valid values are enabled, on, or force. - AWSDEM074E
There is an error in the workstation definition. The secureaddr keyword is supplied more than once. - AWSDEM075E
There is an error in the workstation definition. The supplied secureaddr keyword is not set to a valid SSL port number. - AWSDEM076E
There is an error in the workstation definition. The protocol keyword is not followed by a valid value. Valid values are http or https. - AWSDEM077E
There is an error in the workstation definition. The protocol keyword is supplied more than once. - AWSDEM078E
There is an error in the workstation definition. The required members keyword is missing for pool workstation definition. - AWSDEM079E
There is an error in the workstation definition. The members keyword must be supplied only for workstation class or pool workstation definition. - AWSDEM080E
There is an error in the workstation definition. The required members keyword has been specified more than once. - AWSDEM081E
There is an error in the workstation definition. All workstation names in the members keyword must start with an alphabetic character, followed by up to 15 alphanumeric bytes, including dashes and underscores. - AWSDEM082E
There is an error in the workstation definition. A workstation name in the members keyword is not syntactically correct. All workstation names must start with an alphabetic character, followed by up to 15 alphanumeric bytes, including dashes and underscores. - AWSDEM083E
There is an error in the workstation definition. The requirements definition in the requirements keyword is not well formatted. - AWSDEM084E
There is an error in the workstation definition. The $MANAGER keyword is supplied more than once. - AWSDEM185E
There is an error in the domain definition. You have supplied the ismaster keyword to indicate the domain is the master domain, but you have also supplied the parent keyword which is not valid for a master domain. - AWSDEM186E
There is an error in the domain definition. A domain cannot reference itself as its parent. - AWSDEM187E
There is an error in the workstation definition. The supplied node name exceeds the maximum length of 51 bytes. - AWSDEM188E
There is an error in the workstation definition. The ismaster keyword is followed by a value, rather than by another keyword. This keyword has no value. - AWSDEM202W
%s line %d: %s %d: %s - AWSDEM203E
%s line %d: %s %d: %s - AWSDEM206E
There is an error in an object definition. The description of the object is too long (maximum 120 bytes). - AWSDEM207E
The IPv6 address has too many colons. - AWSDEM208E
The IPv6 address is too long. - AWSDEM209E
There is a syntax error. The variable table name must not exceed 80 bytes. It must start with an alphabetic character and contain only alphanumeric characters, dashes, and underscores. - AWSDEM210E
There is a syntax error. The keyword VARTABLE is duplicated. - AWSDEM211E
There is a syntax error. The keyword VARTABLE is not included in the command. - AWSDEM212E
There is an error in the workstation definition. The supplied ENGINEADDR keyword is not set to a valid TCP port number. - AWSDEM213E
There is a syntax error. The keyword ENGINEADDR is duplicated. - AWSDEM214E
There is a syntax error. The supplied TCP or SSL port must be in the range 1..65535. - AWSDEM215E
There is an error in the workstation definition. The licensetype keyword is not followed by a valid license type. Valid values are perjob and perserver. - AWSDEM216E
There is an error in the workstation definition. The licensetype keyword has been supplied more than once. - AWSDEU - Utilities library list messages
This section lists utilities library list error and warning messages that might be issued. - AWSDEU001E
**ERROR** Adding domain !1 would cause a loop in the domain hierarchy. - AWSDEU004E
Attempt to add item to list pointed to by null pointer. - AWSDEU005E
Attempt to delete from a list pointed to by null pointer. - AWSDEU006E
Attempt to delete from empty list. - AWSDEU007E
Attempt to find last position in list pointed to by null pointer. - AWSDEU008E
Attempt to find length of list pointed to by null pointer. - AWSDEU009E
Attempt to find position at or before zeroth list element. - AWSDEU010E
Attempt to find position in list pointed to by null pointer. - AWSDEU011E
Attempt to free list pointed to by null pointer. - AWSDEU012E
Attempt to insert a null pointer into list. - AWSDEU013E
Attempt to insert after a null pointer. - AWSDEU014E
Attempt to insert before a null pointer. - AWSDEU015E
Attempt to insert before list header. - AWSDEU016E
Attempt to insert into list pointed to by null pointer. - AWSDEU017E
Attempt to insert list header into list. - AWSDEU018E
Attempt to move element down empty list. - AWSDEU019E
Attempt to move element in list pointed to by null pointer. - AWSDEU020E
Attempt to move element up empty list. - AWSDEU021E
Attempt to move header node of list. - AWSDEU022E
Attempt to print list pointed to by null pointer. - AWSDEU023E
Attempt to traverse list pointed to by null pointer. - AWSDEU024E
Attempt to unvisit list pointed to by null pointer. - AWSDEU025E
List is empty. - AWSDEU026E
List to search for visited nodes is empty. - AWSDEU027E
Master domain name is a null pointer. - AWSDEU028E
Master domain name is a null string. - AWSDEU029E
Move element down: failed. - AWSDEU030E
Move element up: failed. - AWSDEU031E
Null pointer supplied for delete. - AWSDEU032E
Null pointer supplied for move. - AWSDEU033E
Not enough elements in list. - AWSDEU034E
Null domain pointer supplied. - AWSDEU035E
Null input list node pointer supplied. - AWSDEU036E
Null list node pointer supplied. - AWSDEU037E
Null parent pointer supplied. - AWSDEU038E
Null string pointer supplied. - AWSDEU039E
Pointer to node is not in list. - AWSDEU040W
Testing for empty list pointed to by null pointer. - AWSDEU041E
Unable to allocate list node. malloc() failed. - AWSDEU042E
Unable to create HM list node. malloc() failed. - AWSDEU043E
Unable to create list node. malloc() failed. - AWSDEU044E
Unable to initialize list. - AWSDEU045W
WARNING: domain !1 has no parent. - AWSDEU046E
Domain is a null pointer, not a string. - AWSDEU047E
Domain not found in list. - AWSDEU048E
Input list is empty. - AWSDEU049E
List pointed to by null pointer. - AWSDEU050E
Parent is a null pointer, not a string. - AWSDEU051E
String to search pointed to by null pointer. - AWSDEU052E
Null pointer supplied instead of string. - AWSDEU053E
Attempt to find domain index in list pointed to by null pointer. - AWSDEU054E
The domain loop would be: !1. - AWSDEU056E
The name of a domain manager in the Symphony file is not valid. The file might be corrupt. - AWSDEV - TIS library messages
This section lists error and warning messages that might be issued by the TIS library, that converts files to UTF-8 format. - AWSDEV001E
Unable to open input file !1 for reading. - AWSDEV002E
Unable to examine input file !1. - AWSDEV003E
Unable to allocate input buffer. - AWSDEV004E
Unable to allocate output buffer. - AWSDEV005E
Unable to read input file !1. - AWSDEV006E
The user ID that is using HCL Workload Automation does not have the right ownership or access permissions to create the following output file: "file_name" for writing. - AWSDEV007E
Unable to write to output file !1. - AWSDEV009E
Conversion not supported. - AWSDFH - Condition expression parsing messages
This section lists condition expression parsing error and warning messages that might be issued. - AWSDFH001E
The following success condition comparison expression is missing one of a pair of parentheses: "expression" - AWSDFH002E
The success condition comparison expression either contains an unsupported operator or an operator used incorrectly: "operator".Note that = < > != <> >= <= are comparison operators and they can be used for comparison expressions. AND OR NOT are logical operators and they can be used for boolean expressions, however, NOT is a unary operator. - AWSDFH003E
The following output condition comparison expression is incorrect: "expression". - AWSDFH004E
The success condition comparison expression contains the following non-valid operand: "operand". The operand must be an integer between -2147483647 and 2147483647. - AWSECM - Event Configuration messages
This section lists error and warning messages that might be generated by event configuration. - AWSECM001E
The general attributes for this workstation in the thiscpuvariable have not been found in the localopts file. - AWSECM002E
The Event Manager definition has not been found. - AWSECM003E
The Event Manager workstation is not in the Symphony file. - AWSEDW - Netman messages
This section lists error and warning messages that might be generated by the netman component. - AWSEDW001E
The following value: "value" for the following netman command line option: "option" is not in the correct format. - AWSEDW002E
System error - AWSEDW003W
Not running with root permissions - AWSEDW004E
Message file already opened by another process: !1, !2 - AWSEDW005E
Netman was unable to open its configuration file: "file_name". The following error was given by the operating system: "system_error" - AWSEDW006E
Netman could not process the service information in its configuration file: "file_name". If the problem is with a specific entry, the details are as follows (if the following fields are blank the problem is a general one): "service_entry":"service_number". - AWSEDW007E
Unable to open both message file and net connection - AWSEDW008E
Error opening stdlist - AWSEDW009E
Error duping stdlist - AWSEDW011E
Unable to create stdlist - AWSEDW012E
An internal error has occurred. Netman has stopped because the following non-valid unlink request has been received: "service_request ". The error message and number are as follows: "error_number": "error_message" - AWSEDW013E
An internal error has occurred. Netman received the following unlink request "service_request" from the following message file: "message_file". Unlink requests received from a message file are not allowed. - AWSEDW014E
Invalid request !3 on !1: !2 - AWSEDW015E
Netman received the following unknown service request: "service_request" - AWSEDW017E
Netman received a service request for the following service that has a service type of disabled : "service_request" - AWSEDW018E
Error building message file: !1, !2 - AWSEDW019E
An internal error has occurred. Netman was unable to open its message file, NetReq.msg, for reading. The following messages were given:Operating system error: "system_error"Events file library error: "library_error". - AWSEDW020E
An internal error has occurred. Netman was unable to set up its TCP/IP port to listen for service requests. The following operating system message was received: "error_message". - AWSEDW021E
Netman was unable to stop the following service as part of the child process cleanup procedures performed before exiting: "service". The following error message was given by the operating system: "error_message". - AWSEDW022E
An internal error has occurred. Netman encountered an IPC error when waiting for a service request to arrive or when reading a service request, from the following port: "port_number". The error message is as follows: "system_error" - AWSEDW023E
An internal error has occurred. Netman encountered an IPC error when trying to close the connection with the client process on the following port: "port_number", "system_error". - AWSEDW024E
An internal error has occurred. Netman encountered an error while it was trying to read a service request from the following message file: "message_file". The following operating system error message is given: "error_message". - AWSEDW025E
An internal error has occurred. Netman was unable to pass the circuit information as an argument to the program associated with the following service request: "service_request". The operating system error message is as follows: "error_message". - AWSEDW026E
Netman was unable to run the child process associated with the following service request: "service_request". The operating system error message is as follows: "error_message ". - AWSEDW027E
An internal error has occurred. Netman is unable to send an acknowledgment packet in response to the following service request: "service_request ". The following error message is given: "error_message" - AWSEDW029E
Error closing net link: !1, !2 - AWSEDW030E
An internal error has occurred. Netman was unable to set the signal handler to ignore one of the following signals: SIGTTOU, SIGTTIN, and SIGTSTP. The signal number is as follows: "signal_number". The operating system error message is as follows: "system_error" - AWSEDW031E
An internal error has occurred. Netman was unable to create a new session when trying to become a daemon process. The operating system error message is as follows: "error_number", "error_message". - AWSEDW032E
An internal error has occurred. Netman was unable to change the current working directory to the root directory when trying to become a daemon process. The operating system error message is as follows: "error_number", "error_message". - AWSEDW033W
The following duplicate service request has been received: "service_request". The following is the error message: "error_message" - AWSEDW035W
The following request cannot be performed because netman is emptying its request cache: "service_request" - AWSEDW044W
Son !1 pin !2 is gone, status: !3 - AWSEDW045W
Client pin !1 is gone, status: !2 - AWSEDW050E
An internal error has occurred. Netman, while attempting to launch itself as a daemon, cannot set the real group id (gid) to the HCL Workload Automation group id. The error occurred in the following source file: "file_name", at line: "line_number". The operating system error message is as follows: "error_message", !4. - AWSEDW051E
An internal error has occurred. Netman, while attempting to launch itself as a daemon, cannot set the real user id (uid) to the HCL Workload Automation user id. The error occurred in the following source file: "file_name", at line: "line_number". The operating system error message is as follows: "error_message", !4. - AWSEDW052W
IP address validation not performed for request: !1. Connection received from IP address: !2. !3. Service request accepted. - AWSEDW053E
Netman could not validate the IP address for a service.Service request: "service_request"IP address: "IP_address"Error type: "error_type"Error message: "validation_error". - AWSEDW056E
Netman was unable to retrieve its product group name from the components file. Netman might not have been installed correctly, or the components file might not be correct. - AWSEDW058E
Netman cannot find the program file associated with the following service number: "service_number" and action number: "action_number" in its configuration file"netman_configuration_file". - AWSEDW059E
Netman was unable to get information about its configuration file, "file_name". The operating system error message is as follows: "system_error" - AWSEDW060E
Netman found a non-valid service request in its configuration file. [ SEE AWSEDW058 FOR FORMATs , NetConf. "file_name":"ServiceEntry": "service_number" !4 !5 - AWSEDW061E
Netman was unable to create a new thread. Pipe connections are not supported. - AWSEDW062E
Netman cannot enable a named pipe server process to wait for a client process. The error occurred in the following source file: "file_name", at line: "line_number". The operating system error message is as follows: "error_number", from the following call: "system_call". - AWSEDW063E
An internal error has occurred. Netman was unable to identify the following user that is trying to start a service: "user_ID". - AWSEDW065E
CreateEvent() failed: File !1 (line !4): Error !2 from !3 - AWSEDW066E
Netman encountered an error trying to write data to a pipe. The error occurred in the following source file: "file_name", at line: "line_number". The operating system error message is as follows: "error_number", from the following call: "system_call". - AWSEDW067E
Netman encountered an error trying to read data from a pipe. The error occurred in the following source file: "file_name", at line: "line_number". The operating system error message is as follows: "error_number", from the following call: "system_call". - AWSEDW068E
Netman encountered an error trying to create a named pipe. The error occurred in the following source file: "file_name", at line: "line_number". The operating system error message is as follows: "error_number", from the following call: "system_call". - AWSEDW069E
Netman was unable to create a handle for a new thread starting Service Client thread. The error occurred in the following source file: "file_name", at line: "line_number". The operating system error message is as follows: "error_number", from the following call: "system_call". - AWSEDW070E
An internal error has occurred. Netman could not write to the Windows event log. The operating system error message is as follows: "error_number". The error occurred in the following source code file: "file_name" at line"line_number". - AWSEDW081W
SSL port set to 0 - no SSL IPC opened - AWSEDW090E
An attempt has been made to perform a non-secure action from a remote workstation to the local workstation. The remote workstation does not have the correct security rights to access the local workstation. - AWSEDW091E
Netman was unable to start a new process. Your HCL Workload Automation license expired "exp_date". - AWSERB - Event rule builder messages
This section lists error and warning messages that might be generated by the rule builder component. - AWSERB001E
An internal error has occurred. The rule builder is not inizialized. - AWSERB002E
An internal error has occurred during the build configuration. - AWSERB003E
An internal error has occurred when the rule builder loaded the workstation in the plan. - AWSERB004E
An internal error has occurred. During the build of an event rule of type sequence or set, it has been verified that the rule has only an event condition. - AWSERB005E
An internal error occurred when the rule builder tried to get the workstation configuration. - AWSERB006W
The plug-in "plug-in" that impacts the event rule "eventrule" does not exist. - AWSERP - Event rule parser messages
This section lists error and warning messages that might be generated by the event rule parser component. - AWSERP001E
An internal error has occurred. A field of the AttributeFilter object in the input to the event rule parser is null. - AWSERP002E
An internal error has occurred. A condition object in the input to the event rule parser is null. - AWSERP003E
An internal error occurred while configuring the event rule parser properties and features. - AWSERP004E
An internal error occurred while parsing the string in input. It is not a valid XML string. - AWSERP005E
An internal error occurred while parsing the XML file created by the XML Formatter component. - AWSERP006E
An internal error occurred while loading the Filtering Predicate XML Schema file used by the XML parser. - AWSERP007E
An internal error has occurred. An incorrect number of conditions has been supplied for the range operator. It requires two. - AWSERP008E
An internal error has occurred. The operator in the input is not valid. - AWSERP009E
An internal error has occurred. An incorrect number of conditions has been supplied for either the le or the ge operator. Both require only one condition. - AWSETO - Object monitor plug-in messages
This section lists error and warning messages that might be generated by the object monitor plug-in. - AWSETO001E
An internal error has occurred. The HCL Workload Automation Object Monitor plug-in is unable to write the configuration for the agent "workstation_name", the reason is: "reason". - AWSETO002E
The event "event_name" of type "event_type" is not valid, because filters are not allowed on Stop reason when Running=true is specified. - AWSETO003E
The event "event_name" of type "event_type" is not valid, because filters are not allowed on Restarting when Running=true is specified. - AWSETO004E
The event "event_name" of type "event_type" is not valid, because filters are not allowed on No restart reason when Restarting=true is specified. - AWSETO005E
The event "event_name" of type "event_type" is not valid, because filters are not allowed on No restart reason when StopReason=Stop is specified. - AWSETO006E
The event "event_name" of type "event_type" is not valid, because filters are not allowed on Unlink reason when LinkStatus=Linked is specified. - AWSEVP - Event processing messages
This section lists error and warning messages that might be generated by the event processor. - AWSEVP002E
The event processor is not running. - AWSEVP010W
The event processor started with the internal persistence feature enabled. A problem occurred while recovering the state of the event rule instances, which have been rebuilt. - AWSEVP014W
The event processor stopped with the internal persistence feature enabled. A problem occurred while storing the state of the event rule instances, which will be rebuilt at the next start. - AWSFAB - Installation messages (twsinst)
This section lists error and warning messages that might be issued when using the twsinst script to install the product. - AWSFAB003E
The twsinst script cannot run on this operating system: "operating_system". - AWSFAB004E
Only the user root can run the twsinst script. - AWSFAB005E
No parameters have been specified for twsinst. - AWSFAB007E
The supplied installation type parameter is not correct. It must be one of the following: -new, -update, -uninst, -modify, -restore. - AWSFAB008E
You supplied more than one installation type parameter. Supply only one of the following: -new, -update, -uninst, -modify, -restore. - AWSFAB009E
A parameter to twsinst has been supplied that is not appropriate for the supplied installation type. Specify the "installation_parameter" parameter only when "installation_type" installation type is specified. - AWSFAB010E
An incorrect value has been supplied for a parameter. The parameter must be as follows: "installation_parameter". - AWSFAB011E
The following parameter has been supplied more than once:"installation_parameter". - AWSFAB012E
The installation parameter specified, "installation_parameter", is not supported for the installation type "installation_type". - AWSFAB014E
The following is not a recognizable installation parameter "installation_parameter". - AWSFAB015E
The "parameter_name" option is missing. - AWSFAB016E
The following user account has been supplied that does not exist on the local computer: "user_account". You must create the user account before running twsinst. - AWSFAB017E
The script was unable to locate the home directory of the specified user: "user_account". - AWSFAB018E
The script was unable to locate the home directory of the specified user, and the installation directory has not been supplied. Supply the installation directory explicitly using the following parameter: "parameter_name". - AWSFAB019E
The supplied target installation directory "directory_name" does not exist. - AWSFAB020E
You are upgrading HCL Workload Automation, but the twsinst script cannot locate the configuration file "configuration_file"of the version you are upgrading. - AWSFAB021E
You are trying to run an "installation_type" installation but the installation script has not found the HCL Workload Automation configuration files belonging to the existing instance. - AWSFAB022E
You are running a fresh installation but the installation script has found a previous instance of HCL Workload Automation, or at least one previously installed HCL Workload Automation configuration file, in the following directory: "directory_name". - AWSFAB023E
You are trying to run a fresh installation but the installation script has found one or both of the HCL Workload Automation configuration files in the following directory: "directory_name". - AWSFAB024E
You are performing a fresh installation, but the installation script has found a previous instance of HCL Workload Automation in the registry file. The instance belongs to the following user:"user_name" and is in the registry file: "registry_file_name". - AWSFAB025E
You are updating or uninstalling, but the installation script cannot find an instance of the product in the HCL Workload Automation registry file. The registry file: "registry_file_name" must contain an entry belonging to the following user: "user_name". Try to regenerate the installation registry running the command with the -recovInstReg option. - AWSFAB026E
The following parameter: "first_parameter" cannot be used with the following parameter: "second_parameter". - AWSFAB027E
The installation was unable to retrieve the following parameter: "parameter" from the following HCL Workload Automation configuration file: "configuration_file". - AWSFAB029W
The supplied port number "port_number" is normally used by other services, such as ftp, or telnet, but will be used. - AWSFAB030E
The supplied company name too long. The limit is 40 bytes. - AWSFAB031E
You can not promote an agent from "original_agent_type" to "promoted_agent_type". - AWSFAB032E
The installation script was unable to obtain the name of the TWSuser group from the following component file of the existing instance of HCL Workload Automation: "component_file_name". - AWSFAB035E
The installation has failed. For more details see the log file: "log_file_name". - AWSFAB036E
The uninstallation has failed. For more details see the log file: "log_file_name". - AWSFAB037E
The twsinst script is being run from the wrong directory. - AWSFAB039E
The installation script was not able to locate the following file needed set up the installation environment: "file_name." - AWSFAB040E
The installation script has been run from the wrong directory. Rerun the script from the following directory:"directory_name". - AWSFAB041E
The installation script has detected that at least one HCL Workload Automation process is running. No processes can be running when you perform an installation, upgrade, promotion, restore or uninstallation. - AWSFAB042E
The installation script has detected that at least one HCL Workload Automation process is running. No processes can be running when you perform an installation, upgrade, promotion, restore or uninstallation. - AWSFAB043W
At least one warning message has been issued during the installation. - AWSFAB044W
At least one warning message has been issued during the uninstallation. - AWSFAB046E
An inconsistent parameter has been used. You cannot specify the "parameter1" parameter when the "parameter2" parameter has been specified. - AWSFAB047E
An inconsistent parameter has been used. When the parameter -cputype "agent_type" is specified, the <cpuname> provided with the -thiscpu and the -master parameters must be different. - AWSFAB048E
The company name cannot contain blank characters (spaces). - AWSFAB049E
The installation directory cannot contain blank characters (spaces). - AWSFAB050E
The following parameter: "parameter" cannot contain more than "number"bytes. - AWSFAB055E
The supplied installation type parameter is not correct. It must be one of the following: -new, -uninst, -update. - AWSFAB094E
The -restore parameter cannot be used either because the previous instance of HCL Workload Automation has not yet been modified or because the new installation has completed successfully. - AWSFAB095E
A parameter is missing. Rerun the installation script, adding the following parameter: "parameter_name". - AWSFAB098E
The values specified for -master and -thiscpu cannot be the same. - AWSFAB099E
You have identified an instance of HCL Workload Automation that is a master domain manager, a backup master domain manager, a dynamic domain manager, a backup dynamic domain manager, an agent with a distributed connector, an agent integrated with a Dynamic Workload Console or a HCL Workload Automation for z/OS connector. You cannot upgrade or install any of these using twsinst. - AWSFAB100E
The script was unable to copy the file maestro.tar.gz to the HCL Workload Automation home directory (TWSHome). - AWSFAB101E
The script was unable to copy the file maestro.tar.z to the HCL Workload Automation home directory (TWSHome). - AWSFAB102E
The script was unable to expand the file maestro.tar.gz in the HCL Workload Automation home directory (TWSHome). - AWSFAB103E
The script was unable to expand the file maestro.tar.z in the HCL Workload Automation home directory (TWSHome). - AWSFAB104E
The script was unable to untar the file maestro.tar.gz in the HCL Workload Automation home directory (TWSHome). - AWSFAB105E
The script was unable to untar the file maestro.tar.z in the HCL Workload Automation home directory (TWSHome). - AWSFAB106E
An incorrect value has been supplied for the parameter -thiscpu. - AWSFAB107E
An incorrect value has been supplied for the parameter -master. - AWSFAB108E
The option -restore is not allowed on operating system "operating_system". - AWSFAB109E
You are performing an upgrade to version "version", but the installation script has found a previous instance of HCL Workload Automation, with the same version in the registry file "registry_file", belonging to the same TWSUser: "TWSUser_name". - AWSFAB111W
The supplied Job Manager port number "port_number" is normally used by other services, such as FTP or Telnet. The twsinst script proceeds using the Job Manager port number that you supplied. - AWSFAB112E
The supplied Job Manager port number is equal to the same as the netman port number. Specify a different value. - AWSFAB121W
The supplied DWB port number "port_number" is normally used by other services, such as FTP or Telnet. The twsinst script proceeds using the DWB port number that you supplied. - AWSFAB122E
The supplied DWB port number is the same as the netman port number. Specify a different value. - AWSFAB123E
The supplied TDWB port number is the same as the jmport number. Specify a different value. - AWSFAB124E
The value you specified for the "parameter" is incorrect. Valid values are true and false. - AWSFAB128E
The value you specified for the -addjruntime is incorrect for the agent that you are installing.You can add the runtime for Java job plug-ins only to HCL Workload Automation for z/OS agents (z-centric) or to dynamic agents. - AWSFAB132E
The uninstallation process failed for one of these reasons:\n You logged into the system with an incorrect user\n You specified an incorrect username\n You are running the twsinst script from the wrong directory. - AWSFAB133E
Either the -password parameter is missing, or an incorrect value has been supplied for a parameter. The parameter must be as follows: "installation_parameter". - AWSFAB134E
You specified an incorrect password for the user "username". - AWSFAB135E
The "user_account" user account you supplied does not exist on the local computer. The operation cannot proceed. - AWSFAB136E
An error occurred when creating the "user_account" user on the local computer. The twsinst installation cannot proceed. - AWSFAB141E
An instance of HCL Workload Automation is already installed for another user in the "directory" directory you specified as installation directory. - AWSFAB142E
The directory "directory" you specified is incorrect or is not a fully qualified path. - AWSFAB143W
The user "user" is a domain user. Verify if he has all the required permissions to perform the installation. - AWSFAB151E
The specified parameter "parameter" must have an integer value or -1. - AWSFAB154E
The following processes are still running "processes". Close them before running the operation again. - AWSFAB155E
The following processes are still running "processes". Either close them or wait for their completion before running the operation again. - AWSFAB161E
There are still jobs running. The twsinst operation cannot continue. Use the coman sj @#@.@ command to verify which jobs are still running. - AWSFAB162E
The following processes are still running. Close them before running the operation again. - AWSFAB163E
The following processes are still running. Either close them or wait for their completion before running the operation again. - AWSFAB164E
The values specified for "parameter1" and "parameter2" cannot be the same. - AWSFAB165E
You are trying to install the standard agent or the fault-tolerant agent, from the wrong eImage. - AWSFAB166E
You are trying to add the runtime for Java job plugins, but the eImage you downloaded does not contain the appropriate installation files. - AWSFAB167E
You are trying to upgrade or modify a standard agent or a fault-tolerant agent, but the eImage you downloaded does not contain the related installation files. - AWSFAB168E
You are trying to upgrade or modify the runtime for Java job plugins, but the eImage you downloaded does not contain the related installation files. - AWSFAB169E
Operating system not supported. - AWSFAB170E
Linux distribution is not supported. - AWSFAB171E
The Linux version: "operating_system" "major_version" "minor_version"; is not supported. - AWSFAB172E
The Linux service pack: "operating_system" "major_version" "minor_version"; is not supported.Update the Operating system to service pack: "operating_system" "major_version" "correct_minor_version". - AWSFAB173E
Operating system version is not supported. - AWSFAB174E
AIX operating system maintanance package is not supported. - AWSFAB175E
Found library "library" but not "softlink". Softlink "softlink" to "library". - AWSFAB176E
Library libXp.so.6 and libXmu.so.6 are not found.The graphical installation process cannot work. - AWSFAB177E
Required libraries are not installed on the running system. - AWSFAB178E
32-bit AIX operating system is not supported.Only AIX 64-bit system are supported by HCL Workload Automation. - AWSFAB179E
The AIX maintanance package "maintanance_package" is not supported.Update the running operating system to the manteinance package "maintanance_package". - AWSFAB180E
The AIX fix "fix" was not found on the running system. - AWSFAB181E
C++ runtime level "runtime_level" not supported.Update the C++ runtime level to "required_runtime_level". - AWSFAB193E
The library "library" must be installed on the running system. - AWSFAB194E
The 64 bit library "library" must be installed on the running system. - AWSFAB196E
The patch "patch" must be installed on the running system. - AWSFAB197E
Upgrade patch "patch" "bundle" to version "version". - AWSFAB198E
Operating system required patches are missing. - AWSFAB199E
Required cluster patch "patch" is missing. - AWSFAB200E
Required security patch is missing. - AWSFAB201W
WebSphere recommended patches are missing. - AWSFAB203E
Unsupported quality pack.Update the quality pack to "var1" "var2" or December 2004. - AWSFAB205E
The operating system release level is not supported.Update the release level "release_level" to "required_release_level". - AWSFAB211W
The minimum required patch "patch" was not found on the running system. - AWSFAB212E
Operating system release "os_release" not supported. - AWSFAB213E
Not enogh free disk space on file system "fs". "disk_space" "ds_measure_unit" are required. - AWSFAB214E
Not enough free disk space on swap file system. - AWSFAB215E
The directory "dir" is not found. - AWSFAB216E
You specified a non existing installation path. - AWSFAB218E
Hardware "hw" not supported.The required hardware is "hw_required". - AWSFAB219E
Hardware model "model" not supported.The required hardware model is "model_required". - AWSFAB220W
Recommended memory requirements are not satisfied. - AWSFAB221E
The Memory requirements are not satisfied.The minimum requirement is "min_mem" Kbytes and recommended is "rec_mem" Kbytes. - AWSFAB224W
Kernel parameter "kparam" not defined. - AWSFAB225E
Kernel parameter "kparam" not defined. - AWSFAB228E
Required kernel parameter(s) not defined. - AWSFAB229W
Recommended kernel parameters are not defined. - AWSFAB230W
Some prerequisites were not satisfyed during the check, look at the log for more details. - AWSFAB231E
The prerequisites scan detected missing prerequisites. Check the prerequisites scan logs, precheck_result.txt and result.txt, located in the "installation_log" folder, for details. Install the missing prerequisites and rerun the installation command. If no prerequisites are missing, rerun the installation command with the -skipcheckprereq option. - AWSFAB233W
The free disk space available on the swap file system does not meet the recommended requirements. - AWSFAB236E
You are trying to install or upgrade a HCL Workload Automation instance from the wrong eImage for the target operating system. - AWSFAB237E
You are trying to upgrade or modify the HCL Workload Automation for z/OS agent (z-centric), but the images on the workstation do not contain the related installation files. - AWSFAB238E
You are trying to install the HCL Workload Automation dynamic agent, but you did not specify the -tdwbport <port_number> installation parameter with a <port_number> value different from 0. - AWSFAB239W
You are installing a dynamic agent but you provided some parameters that are not necessary for the dynamic agent installation. These parameters are ignored. - AWSFAB240W
You are installing a fault-tolerant agent but you provided some parameters that are not necessary for a fault-tolerant agent installation. These parameters are ignored. - AWSFAB243E
An error occurred running the option that recreates the HCL Workload Automation installation on the specified path "twa_path". Check the installation log for details. - AWSFAB246E
The value you specified for the -addjruntime is incorrect for the fault-tolerant agent that you are upgrading.You can add the runtime for Java job plug-ins only to dynamic agents.To install and configure a dynamic agent during upgrade you must specify the -tdwbport <port_number> parameter with a <port_number> value different from 0. - AWSFAB247E
The user account you specified: "user_account" is a reserved IBM i User Profile. You cannot use a reserved account. Specify an existing user account different from the following reserved accounts: QDBSHR, QDFTOWN, QDOC, QLPAUTO, QLPINSTALL, QRJE, QSECOFR, QSPL, QSYS, QTSTRQS. - AWSFAB248E
There is already the IBM i "user_account" library in the system. You must rename or remove the library, or you must specify a different user account. - AWSFAB249E
32-bit "os" operating system is not supported.Only "os" 64-bit system are supported by HCL Workload Automation. - AWSFAB284E
The Linux "operating_system" service pack "minor_version" is not supported. Update the Operating system to service pack "correct_minor_version". - AWSFAB286E
The eImage on your workstation is corrupt. You must run the TAR command on QP2TERM or AIXTERM shell to untar the eImage otherwise your "script_name" script fails. - AWSFAB287E
The current shell is not supported for "script_name" script. Use QSH shell to run the "script_name" script. - AWSFAB289W
The Java extension is already installed for the user "user_name" that you specified. - AWSFAB290E
You are modifying a product version different from "version". The modify action can be applied only to a HCL Workload Automation, version "version" instance. - AWSFAB294E
The value you specified for -addjruntime is incorrect for the agent that you are modifying.You can add the runtime for Java job plug-ins only to dynamic agents or HCL Workload Automation for z/OS agents with dynamic capabilities.For fault-tolerant agents and HCL Workload Automation for z/OS agents you must enable the dynamic capabilities before performing a modify. - AWSFAB295W
You can add the runtime for Java job plug-ins only to dynamic agents or HCL Workload Automation for z/OS agents with dynamic capabilities.For fault-tolerant agents and HCL Workload Automation for z/OS agents you must enable the dynamic capabilities before running the upgrade. The step to add the runtime for Java job plug-ins is ignored. - AWSFAB296E
The operation -restore for the user "user_name" cannot be performed, because the instance you want to restore is not at version "version" or later. - AWSFAB303E
The parameter "parameter_name" is invalid. - AWSFAB304E
You cannot specify the -passwords parameter if you do not specify the -groups parameter. - AWSFAB305E
You specified an invalid path. The specified path "path_name" is not valid either because it does not exist or because it does not contain the file twsinst.vbs. - AWSFAB306E
If you specify the "par1_name" parameter, you must also specify the "par2_name". - AWSFAB307E
You cannot specify the "par1_name" parameter, because this image is the General Availability version image. - AWSFAB308E
This is the General Availability image, you must specify the "par1_name" parameter. - AWSFAB309E
You supplied the parameter "par1_name" more than once. - AWSFAB310E
You did not specify any values for the parameter "par1_name". Specify a value for the parameter "par1_name". - AWSFAB311E
The syntax you specified for the parameter "par1_name" value is incorrect. - AWSFAB312E
An error occurred while using the Windows Management Instrumentation (WMI) service. Error code: "err_code". - AWSFAB314W
The group named "group_name" is not upgraded because it contains more than one HCL Workload Automation resource. - AWSFAB315E
The group named "group_name" is not upgraded because it does not contain a HCL Workload Automation resource. - AWSFAB316E
The group named "group_name" is not upgraded because it contains more than one HCL Workload Automation resource. - AWSFAB317E
An error occurred while running the cluster.exe command. - AWSFAB318E
An internal error occurred while parsing the node names. - AWSFAB320E
The product cannot pause the node "node_name" because it is in the incorrect status "status". - AWSFAB321W
The resume of the node "node_name" is not performed because it is in the status "status". - AWSFAB322W
The resume of the nodes is not performed, because some groups were not upgraded successfully. - AWSFAB324E
An error occurred while pausing the node "node_name" - AWSFAB326E
The product cannot retrieve the status of the node "node_name". - AWSFAB327E
The node "node_name" was not paused within the timeout period. - AWSFAB329E
An error occurred while resuming node "node_name" - AWSFAB330E
The node "node_name" was not resumed within the timeout period. - AWSFAB331E
An internal error occurred while parsing the nodes and the group lists. - AWSFAB332E
An internal error occurred while parsing the nodes and the resource lists. - AWSFAB333E
The product cannot find the HCL Workload Automation resource DLL path. - AWSFAB337E
An error occurred while setting the resource "resource_name" to offline. - AWSFAB338E
The product cannot retrieve the status of the resource "resource_name". - AWSFAB339E
The resource "resource_name" was not set to offline within the timeout period. - AWSFAB341E
An error occurred while setting the resource "resource_name" to online. - AWSFAB342E
The resource "resource_name" was not set to online within the timeout period. - AWSFAB343E
An internal error occurred while parsing resources and group lists. - AWSFAB346E
The cluster group "group_name" was not upgraded successfully. - AWSFAB349E
The file "file_name" does not exist, the tool cannot upgrade the resource "resource_name". - AWSFAB350E
The product cannot find the version of the HCL Workload Automation resource DLL "file_name". - AWSFAB352E
The upgrade to version "version" is impossible because the version of the product present in the instance is incorrect. - AWSFAB356E
The number of passwords ("pws_num") that you specified, is not equal to the number of groups ("grp_num") that must be upgraded. Check the -groups and -passwords parameters. - AWSFAB357E
None of the groups you specified contain HCL Workload Automation resources. - AWSFAB374E
JM port is already used in some other instance. Please specify some other port value. - AWSFAB375E
An error occurred when creating the "directory" folder on the local computer. The operating system error is: "error". The twsinst installation cannot proceed. - AWSFAB379E
The "user_account" user account you supplied does not have the right security policies. The operation cannot proceed. - AWSFAB380E
A parameter to twsinst has not been supplied. The "installation_parameter" parameter must be specified when "installation_parameter2" parameter is supplied. - AWSFAB381E
An instance of HCL Workload Automation is already installed for same user in the "directory" directory you specified as installation directory. - AWSFAB382E
Accept the license and terms conditions before proceeding with the installation. - AWSFAB383E
An incorrect value has been supplied for the parameter gwid. The accepted values must start with either a letter or underscore (_) and may contain only letters, digits, underscores (_), hyphens (-), and periods (.). - AWSFAB384E
It is not possible to retrieve the domain name for the user "user". Check user rights and permissions. - AWSFAB385E
If you specify the -domain parameter you cannot specify the username in the format domain\\username. - AWSFAB386E
It is not possible to retrieve the domain name for the user "user". Check user rights and permissions. - AWSFAB389E
You can specify the "parameter1" parameter only when the "parameter2" parameter has been specified. - AWSFAB403W
You upgraded PeopleSoft method. In order to continue schedule PeopleSoft jobs you have to copy psjoa.jar file under "parameter1" folder. - AWSFAB404E
The installation cannot run because the user running the twsinst installation script must either be the root user or the same user specified for the uname parameter. - AWSFAB405E
No root installation is supported only for dynamic agent installation. - AWSFAB406E
HCL Workload Automation dynamic agent instance can be updated only by the same user who previously installed it. - AWSFAB407W
You are proceeding with the installation process in spite of missing prerequisites being detected by the prerequisites scan. - AWSFAB408W
The prerequisites scan detected missing prerequisites. Check the prerequisite scan logs, precheck_result.txt and result.txt, located in the installation log folder, for details. Installation will continue because the missing prerequisites do not affect the installation process. - AWSFAB409E
Home directory for the user "user" does not exist. Please create it and then run the installation procedure again. - AWSFAB411E
gateway_eif_port port is already used by another process. Please specify some other port value. - AWSFAB416E
A parameter to twsinst has been supplied that is not appropriate for the supplied installation type. Specify the -password parameter only when new installation type is specified, or when upgrading from 8.5.1. - AWSFAB417E
An incorrect value has been supplied for the parameter -password. - AWSFAB418E
The value specified for the port number by parameter "installation_parameter" is not valid. The value must be numeric and in the range 1 - 65535. - AWSFAB419E
This script must be run from a command prompt that is running as Administrator. Open the command prompt window as administrator, and run the script again. - AWSFAB436E
The agent update failed. The files of the previous version will be restored. After restoring the previous version, the agent will continue to work normally. - AWSFAB437E
The restore operation of the previous version completed with errors: rc. - AWSFAB441E
The specified value is incorrect. The value for the "installation_parameter" parameter cannot start with a number. - AWSFAB442E
The agent version is "agent_version". This patch can be installed only on agents at the following level: "expected_version" . - AWSFAB443E
The file "file" is not found. - AWSFAB444E
Missing property "property" in file "file". - AWSFAF - Installation messages (fix pack)
This section lists error and warning messages that might be issued when using the script to install a fix pack for the product. - AWSFAF003E
The twspatch script cannot run on this operating system: "operating_system". - AWSFAF004E
Only the user root can run the twspatch script. - AWSFAF005E
No parameters have been specified for twspatch. - AWSFAF007E
The supplied installation type parameter is not correct. It must be one of the following: -install, -undo, -commit, -remove, -repair. - AWSFAF008E
More than one installation type parameter has been supplied. Supply only one of the following: -install, -undo, -commit, -remove, -repair. - AWSFAF009E
A parameter to twspatch has been supplied that is not appropriate for the supplied installation type. Specify the "installation_parameter" parameter only when "installation_type" installation type is specified. - AWSFAF010E
An incorrect value has been supplied for a parameter. The parameter must be as follows: "installation_parameter". - AWSFAF011E
The following parameter has been supplied more than once: "installation_parameter". - AWSFAF012E
The twspatch fix pack installation cannot be used because the HCL Workload Automation registry file is missing. - AWSFAF014E
The following is not a recognizable installation parameter "installation_parameter". - AWSFAF015E
The -uname option is missing. - AWSFAF016E
You supplied a user account that does not exist on the local computer or that contains an invalid character: "user_account". Create the user account before running twsinst, or verify that it does not contain an invalid character. - AWSFAF017E
The script was unable to locate the home directory of the specified user: "user_account". - AWSFAF019E
The script was unable to determine the installation type from the HCL Workload Automation registry file "file". - AWSFAF020E
The script was unable to find the configuration file "configuration_file" of the HCL Workload Automation instance to which you want to apply the fix pack. - AWSFAF021E
The script has located an entry for the user in the HCL Workload Automation registry, but the directory that the entry points to does not contain an instance of a previous version of HCL Workload Automation. Check that a previous installation of HCL Workload Automation exists in the directory "directory". If the instance for the supplied user exists, but in a different directory, modify the entry in the HCL Workload Automation registry file to identify the correct installation directory and rerun the script. - AWSFAF022E
The script was unable to determine the installation directory from the HCL Workload Automation registry file "file". - AWSFAF023E
The installed component (workstation type) "installed_component" in the HCL Workload Automation registry file "file" is not valid. - AWSFAF025E
No previous instances of HCL Workload Automation belonging to the supplied user "user" have been detected in the HCL Workload Automation registry file "file". - AWSFAF027E
The "installation_type" fix pack installation has failed. For more details see the log file "file". - AWSFAF028W
At least one warning message was issued during the "installation_type" fix pack installation. - AWSFAF030E
The twspatch script is being run from the wrong directory. - AWSFAF032E
The installation script was not able to locate the file "file" needed set up the operation environment "operation_environment". - AWSFAF033E
The installation script has been run from the wrong directory. You must run the script from the following directory:"directory_name". - AWSFAF034W
The remove operation has been completed successfully. The HCL Workload Automation instance belonging to the user "user" is now unusable. You must recover the previous installation from backup. - AWSFAF037E
The twspatch script is being run from the wrong directory. - AWSFAF046E
The "user_account" user account you supplied does not exist on the local computer. The patching cannot proceed. - AWSFAF047E
You specified an incorrect password for the user "username". - AWSFAF132E
The uninstallation failed. Either you specified an incorrect username or you are running the twspatch script from the wrong directory. - AWSFAF161E
There are still jobs running. The twspatch operation cannot continue. Use the coman sj @#@.@ command to verify which jobs are still running. - AWSFMP - File monitor plug-in messages
This section lists error and warning messages that might be generated when using the file monitor plug-in. - AWSFMP001E
The filtering value "expression" is not valid for the filtering attribute "attribute" for the event "event" defined in the plug-in "plug-in". - AWSFMP002E
Only one instance of the filtering attribute "attribute" is supported for the event "event" defined in the plug-in "plug-in". - AWSFWD - Event forwarder plug-in messages
This section lists error and warning messages that might be generated when using the event forwarder plug-in. - AWSFWD102E
The HCL Workload Automation event "event" has not been forwarded to the IBM Enterprise Console server. The return code is: "return_code". - AWSFWD103E
The HCL Workload Automation event has not been forwarded to the IBM Enterprise Console server. The reason is: "reason". - AWSFWD104E
The action type "action_type" is not supported. - AWSFWD105E
The HCL Workload Automation event has been not forwarded to the IBM Enterprise Console server because the IBM Enterprise Console agent has not been initialized. - AWSGAP - Generic action messages
This section lists error and warning messages that might be generated when using the generic action processing. - AWSGAP002E
An error occurred performing the action. The reason is: "reason". - AWSGAP003E
The action cannot be performed because a valid command has not been supplied (it is null or empty). - AWSGAP004E
The action type is not valid. It must be: GeneralAction. - AWSGAP005E
The plug-in name is not valid. It must be GenericActionPlugin. - AWSGAP006E
The command argument is not valid. It must not be empty. - AWSGAP007E
The value "env_var_value" specified for the environment variable "env_var_key" in the Generic action plug-in exceeds the maximum allowed size of "max_size" KBytes. - AWSGEP - Generic event plug-in messages
This section lists error and warning messages that might be generated when using the generic event plug-in. - AWSGEP001E
A security error has occurred. The user "user_name" is not allowed to modify the event plug-in configuration. - AWSGEP002E
The following error in the XML format of the event plug-in configuration has been verified: "parser_message". - AWSGEP003E
Event name "event_name" is duplicated in the event plug-in configuration. - AWSGEP004E
Incorrect plug-in name: "current_plug-in_name". The name of the plug-in specified in the configuration must be "expected_plug-in_name". - AWSGEP005E
The specified configuration is null or empty. - AWSGEP006E
An internal error has occurred. The schema referenced in the event plug-in configuration is null or empty. - AWSGEP007E
Parameter "parameter_name" is duplicated in the event definition. - AWSGEP008E
The following internal error has occurred: "error_message" - AWSGTW - Gentwsevn messages
This section lists error and warning messages that might be generated when using the gentwseven program that generates events. - AWSGTW101E
The specified parameter "parameter" is not valid. - AWSGTW102E
The arguments exceed the maximum input size. - AWSGTW103E
The parameter "parameter" has been specified more than once. - AWSGTW104E
The parameters "parameter1" and "parameter2" are specified in the wrong order. - AWSGTW105E
The value specified for the parameter "parameter" is not valid. - AWSGTW106E
The mandatory parameters "parameter1" and "parameter2" are missing. - AWSGTW107E
The format of the argument "argument" is not valid. - AWSGTW108E
Parameter "parameter" has a missing value. - AWSGTW109E
The following error occurred while opening the configuration file "file_name": "error_message". - AWSGTW110E
The following error occurred while writing the configuration file "file_name": "error_message". - AWSGTW111E
An internal error has occurred. An error occurred while initializing the IBM Enterprise Console agent. - AWSGTW112E
An internal error has occurred. An error occurred while creating the Event Integration Facility handle. - AWSGTW114E
An error occurred while sending the event. - AWSGTW116E
The mandatory parameter "parameter" is missing. - AWSGTW117E
An internal error has occurred. Sendevent encountered the following error when attempting to open the Symphony file: "error_message". - AWSGTW118W
An internal error has occurred. The event has not been sent. Instead it has been cached in the file "cache_file". - AWSGTW120E
The following error occurred while opening the template configuration file "file_name": "error_message". - AWSGTW121E
The parameters "parameter_1" and "parameter_2" cannot both be specified. - AWSITA - Job management messages
This section lists error and warning messages that might be generated by the routines that handle job management. - AWSITA001E
The command is incorrect and cannot be processed. - AWSITA002E
Cannot save the job with ID "job_id" in the job store. - AWSITA003E
Cannot cancel the job with ID "job_id" because it is not present in the agent job store. - AWSITA004E
Cannot find the executor for the job with ID "job_id". - AWSITA005E
Unable to create the spool directory "spool_direcory" to store the output data of the job. The error is "error_message". - AWSITA007E
Cannot get the output of the job with ID "job_id" because it is not available in the agent job store. - AWSITA008E
Cannot find the executor for the job with ID "job_id". - AWSITA009E
Unable to start the task launcher "task_launcher_binary" to store the output data of the job. The error is "error_message". - AWSITA010W
The job has completed or was previously cancelled. - AWSITA011E
The job definition is missing from the job submit operation. - AWSITA012E
The job cancel task failed while it was getting the information to connect to the job monitor. The error is "error_message". - AWSITA013E
The job cancel task failed while it was creating a connection to the job monitor. The error is "error_message". - AWSITA014E
The job cancel task failed while it was connecting to the job monitor. The error is "error_message". - AWSITA015E
The job cancel task failed while it was contacting the job monitor. The error is "error_message". - AWSITA016E
The job cancel task failed to reconnect to the job monitor. The error is "error_message". - AWSITA017E
The job cancel task failed while it was sending the cancel command to the job monitor. The error is "error_message". - AWSITA018E
Unable to get the job output because of a a problem while reading the "output_file" output file . The error is "error_message". - AWSITA019E
The get job output task failed while it was opening the output file. The error is "error_message". - AWSITA020E
The get job output task failed because the start parameter value looks higher than the output length. The error is "error_message". - AWSITA021E
The get job output task failed because it ran into an error as it was reading the output file. The error is "error_message". - AWSITA022E
Unable to get the job output because the "output_file" output file does not exist. - AWSITA023E
Cannot get the output of the job with ID "job_id" because the job has not started yet. - AWSITA024E
The job failed to start because the error "error_message" was returned while preparing the process attributes of the task launcher. - AWSITA025E
The job failed to start because the error "error_message" was returned while setting the process attributes of the task launcher. - AWSITA026E
The job failed to start because the error "error_message" was returned while setting the command type of the task launcher. - AWSITA027E
The job failed to start because the error "error_message" was returned while creating the arguments to drive the task launcher. - AWSITA028E
The job failed to start. The following error has been generated: "error_description". - AWSITA029E
The job has terminated with signal "signal_number". - AWSITA030E
The job failed. - AWSITA032E
The job with ID "job_id" failed to start. The error is "error_message". - AWSITA033E
The job with ID "job_id" completed with error: "error_message". - AWSITA036W
Cannot get the status of the job with ID "job_id". The error is "error_message". - AWSITA037E
Failed to create the memory pool of the thread that will execute the job. The error is "error_message". - AWSITA038E
Failed to schedule the thread that will execute the job. The error is "error_message". - AWSITA039E
Cannot find the executor for application "application_name". - AWSITA040E
Cannot save the job with ID "job_id" in the job store. - AWSITA041E
Unable to get the list of the jobs because the error: "error_message" was returned while reading the job store file with key"key". - AWSITA042E
Failed to create the memory pool of the job manager thread. The error is "error_message". - AWSITA043E
The job manager failed schedule the thread needed to reconnect the task launcher to the jobs. The error is "error_message". - AWSITA044E
Failed to create the memory pool for the thread that will reconnect to the task launcher of the job with ID "job_id". The error is "error_message". - AWSITA045E
Failed to create the thread that will reconnect to the the job with ID "job_id". The error is "error_message". - AWSITA046E
Cannot find the executor for the job with ID "job_id" while reconnecting to the task launcher. - AWSITA048E
The subagent cannot be created. The error is "error_message". The error code is "error_code". - AWSITA049E
Cannot create the memory pool to handle the connection. The error is "error_message". The error code is "error_code". - AWSITA051E
The agent failed to accept connections. The error is "error_message". The error code is "error_code". - AWSITA053E
The agent failed to create the thread needed to handle the request. The error is "error_message". The error code is "error_code". - AWSITA054E
The task type "task_type" specified within the definition of the extended agent job with ID "job_id" is either unknown or unsupported. - AWSITA055E
An error occurred while waiting to receive the IP address from where the task launcher will listen when it communicates with the job manager. The error is "error_message". - AWSITA056E
An error occurred while waiting to receive the IP port where the task launcher will listen when it communicates with the job manager. The error is "error_message". - AWSITA057E
A request was made to reconnect to job "job_id" that is not running. - AWSITA058E
Reconnection to job "job_id" failed while getting the information to connect to the job monitor. The error is "error_message". - AWSITA059E
Reconnection to job "job_id" failed while creating the connection to the job monitor. The error is "error_message". - AWSITA060E
Reconnection to job "job_id" failed while connecting to the job monitor. The error is "error_message". - AWSITA061E
The access method specified to launch "job_id" is unknown. Check either the JobManager.ini file on the agent or the job definition. - AWSITA062E
The options file of extended agent "target_name" includes option UTF8cmdline set to 1, which is not supported. Set it to 0 and rerun the job. - AWSITA063E
Could not change to the specified working directory. - AWSITA064E
The "execuser" login user specified in the job definition could not authenticate on the agent - AWSITA065E
The group name is incorrect. - AWSITA066E
Privileged user is not allowed to run jobs on this executor. - AWSITA067E
An error occurred setting the process group ID. - AWSITA068E
An error occurred impersonating the user specified in the job definition. - AWSITA069E
Job monitor internal error (return code "error_code") - AWSITA070E
Cannot open the specified input file. - AWSITA071E
Cannot open the internal output log file. - AWSITA072E
Cannot open the internal error log file. - AWSITA073E
Cannot open the specified output file. - AWSITA074E
Cannot open the specified error file. - AWSITA075E
Error creating the job process (return code "error_code"). - AWSITA077E
Abnormal end of job (the exit code is the termination signal number). - AWSITA079E
Unable to convert a specified parameter to the local codeset. - AWSITA080E
The Job Executor Agent cannot find the executable file specified in the JSDL definition. - AWSITA081E
The agent can not send the resource information to "server_uri". The error is: "error_message". - AWSITA082E
The agent got an error response while sending the resource information to the server. The error code is "error_code" and the error message is "error_message". - AWSITA084W
The Resource Advisor Agent is disabled and will not start. Check the ResourceAdvisorUrl property in the JobManager.ini file. - AWSITA085E
Failed to create the memory pool of the command handler thread. The error is "error_message". - AWSITA086E
Failed to create the thread pool of the Job Manager. The error is "error_message". - AWSITA087E
Failed to create the memory pool of the Job Status Notification Manager. The error is "error_message". - AWSITA088E
Failed to create the thread pool of the Job Status Notification Manager. The error is "error_message". - AWSITA089E
The thread of the Job Status Notification Manager failed to start. The error is "error_message". - AWSITA091W
The Job Status Notification Manager is already running. - AWSITA093W
The thread of the Job Status Notification Manager is already stopped. - AWSITA094E
Failed to schedule the thread that will send notification for the job status changes. The error is "error_message". - AWSITA095E
Unable to change the following configuration properties: "error_message". - AWSITA096E
An error occurred while waiting to receive the local job process id. The error is "error_message". - AWSITA097E
Unable to cancel the job because the specified job ID is not valid. - AWSITA098E
Unable to get the job output because the specified job ID is not valid. - AWSITA099E
Unable to get the job properties because the specified job ID is not valid. - AWSITA100E
Unable to get the job(s) properties because the specified job alias "job_alias" is not valid. - AWSITA101E
Unable to get the job(s) properties because the specified job status "job_status" is not valid. - AWSITA102E
Unable to change the configuration properties because the specified XML request "xml_request" is not valid. - AWSITA103E
Unable to perform the dynamic resources scan. The error is "error_message". - AWSITA104E
Unable to perform the system resources scan. The error is "error_message". - AWSITA105E
Unable to notify scan results to the server because of a resources scanner error. - AWSITA106E
The agent failed to accept a connection. - AWSITA107E
Could not load the library "library name". The error is "error_message". - AWSITA108E
Unable to get port information from URI "uri_value". - AWSITA110E
Unable to send the notification of status of the job with ID "job_id" to the URI "uri_value". - AWSITA114E
The job cannot start since the user is missing in the job definition. - AWSITA117E
The Java method call request is not correct: "elem" is missing. - AWSITA118E
A Java Exception occurred while running job "job". "error" - AWSITA119E
A Java exception occurred while retrieving the output of job "job". "error" - AWSITA120E
A Java exception occurred while retrieving the length of the output of job "job". "error" - AWSITA121E
An error occurred while calling a Java method: "elem" is null. - AWSITA122E
A Java exception occurred while calling the command "command". "error" - AWSITA123E
A Java Exception occurred while canceling job "job". "error" - AWSITA124E
A Java Exception occurred in "method". "error" - AWSITA125E
Cannot find a suitable application job plug-in for "plug-in". - AWSITA126E
Malformed JSON string: error "error" at position "position". - AWSITA127E
Access Method field is empty. - AWSITA128E
No method found. - AWSITA129E
No option file found for the method "string". - AWSITA130E
The option file "string" does not exist. - AWSITA131E
The option file "string" is too big. - AWSITA132E
Unable to access to the option file "string". - AWSITA139E
The requested operation cannot be completed. The error is: "error_msg" - AWSITA140E
Option File field is empty. - AWSITA141E
The job cannot start because the job definition does not include either the executable or the script field. - AWSITA142E
Missing variable name after "string" option. - AWSITA143E
Unexpected command argument(s) found. - AWSITA145E
The value cannot be empty. - AWSITA147E
Unknown option "string". - AWSITA150E
Cannot set variable "string" to value "string" because of this error: "string" - AWSITA151E
Cannot get the value of variable "string" because of this error: "string" - AWSITA152E
Cannot remove variable "string" because of this error: "string" - AWSITA153E
Unable to load the "string" variables file because of this error: "string" - AWSITA154E
Unable to update the "string" variables file because of this error: "string" - AWSITA155E
Cannot get the namespace details for variable "string". - AWSITA156E
Cannot find variable "string"."string"."string". - AWSITA157E
Cannot find section "string" within file "string". - AWSITA158E
Cannot get a list of the sections of file "string". - AWSITA159E
Cannot encrypt variable "string"."string"."string". - AWSITA160E
Cannot decrypt the variable "string"."string"."string". - AWSITA161E
Unable to create directory "string" to store the variables file. The error is: "string" - AWSITA162E
Cannot create variable "string"."string"."string". - AWSITA163E
Cannot create variable "string" because the '*' and/or '?' characters are included in its name. - AWSITA164E
Cannot remove variable "string"."string"."string". - AWSITA165E
Variable syntax error. End tag "string" not found. - AWSITA166E
Cannot set the following variables:"string" - AWSITA167E
Cannot set the variables because the specified XML request "string" is not valid or is empty. - AWSITA172E
The value you entered does not match the previous value. - AWSITA173E
Cannot update the specified trace property value because of this error: "string" - AWSITA174E
Cannot obtain the trace properties values because of this error: "string" - AWSITA177E
The value specified for command argument "string" must be a valid positive integer. - AWSITA178E
The value specified for variable "string" exceeds the allowed maximum size. - AWSITA179E
Cannot find variable "string". - AWSITA180E
Cannot obtain a valid date from variable "string" value. - AWSITA181E
Cannot obtain the value of parameter "string" from url. - AWSITA182E
Unable to fill the job header because the specified job ID is not valid. - AWSITA184E
Cannot invoke the rerun or restart command for the job with ID "jobId" because it is not available in the agent job store. - AWSITA185E
Malformed JSON string restarting the job: error "error" at position "position".The json string with the error is "jsonString" - AWSITA186E
Malformed JSON string restarting the job: the parameter "parameter" is missing.The json string with the error is "jsonString" - AWSITA187E
Malformed JSON string invoking a job command: error "error" at position "position".The json string with the error is "jsonString" - AWSITA188E
The rerun action cannot be performed because the job is still running or did not start yet. - AWSITA189E
The rerun action cannot be performed because of errors accessing the agent job store. - AWSITA190E
The rerun action cannot be performed because there was an error saving the job with ID "job_id" in the job store. - AWSITA191E
You specified the parameter "parameter_name" without the required argument. - AWSITA192E
You specified the same parameter "parameter_name" twice. - AWSITA193E
You specified two mutually exclusive parameters. - AWSITA194E
The .ini file "property_file" cannot be loaded. The error is: "error_message". - AWSITA195E
You specified an invalid port number "port_number". - AWSITA196E
You specified an invalid protocol "protocol". Valid values are http and https. - AWSITA197E
The property "file"."section"."property" cannot be loaded from the .ini file"iniFile". - AWSITA198E
You did not specify a value for the port number, either in the command line arguments or in the .ini file. - AWSITA199E
An internal error occurred when configuring the open SSL communication. - AWSITA200E
An error occurred when contacting the agent at the following address: "protocol"://"hostname":"port". The error is: "error_message". - AWSITA201E
An error occurred when allocating memory. The error is: "error_message". - AWSITA202E
An error occurred when opening the zip file "zip_file". The error is: "error_message". - AWSITA203E
An error occurred when writing the zip file "zip_file". The error is: "error_message". - AWSITA205E
You specified an invalid port number "port_number" for the protocol "protocol" in the .ini file "ini_file". The valid range is from 1 to 65535. - AWSITA206E
The following error was returned by the agent: "error_message". - AWSITA207E
An unexpected error was returned by the agent. The following error message has more details: "error_message". - AWSITA208E
An error occurred trying to establish the connection to the agent using the following address: "protocol"://"hostname":"port". The agent is down or the port is incorrect. - AWSITA209E
The agent can not send the resource information to "server_uri" for a network connection problem. The error is: "error_message". - AWSITA211W
Failed to set the stack size of command handler thread pool. The error is "error_message". - AWSITA212E
Failed to create the thread pool of the command handler. The error is "error_message". - AWSITA229E
The wappman command cannot run because one or more input arguments are missing. - AWSITA230E
An error was encountered processing the properties file "property_file_name". - AWSITA231E
The connection property "property_name" must be specified. - AWSITA236E
An error was encountered reading the file "file_name". - AWSITA237E
The protocol must be either HTTP or HTTPS. - AWSITA238E
The user is not authorized to access the server. - AWSITA241E
An error occurred creating the file "file_name" that stores the result of the HTTP request. The error is "error_message". - AWSITA242E
An error occurred writing the file "file_name" that stores the result of the HTTP request. The error is "error_message". - AWSITA243E
An error occurred writing the file "file_name" that stores the result of the HTTP request. The error is "error_message". - AWSITA244E
An error occurred closing the file "file_name" that stores the result of the HTTP request. The error is "error_message". - AWSITA245E
An error occurred getting the response of the HTTP request. The error is "error_message". - AWSITA246E
An error occurred getting the response of the HTTP request. The error is "error_message". - AWSITA247E
An error occurred invoking a POST HTTP request. The error is "error_message". - AWSITA248E
An error occurred invoking a GET HTTP request. The error is "error_message". - AWSITA249E
An error occurred getting the response of the HTTP request. The error is "error_message". - AWSITA250E
An error occurred connecting to "hostname". The error is "error_message". - AWSITA251E
Cannot connect to "hostname" because the protocol "protocol" is not supported. - AWSITA252E
An error occurred connecting to "hostname". The error is "error_message". - AWSITA253E
An error occurred connecting to "hostname". - AWSITA255E
The Event Driven Workload Automation component cannot start because an error occurred creating a thread. The error message is "error_message". - AWSITA256E
The Event Driven Workload Automation component cannot start because an error occurred allocating a memory pool. The error message is "error_message". - AWSITA258E
The active rules output task failed while opening the configuration file. The error is "error_message". - AWSITA259E
The active rules output task failed because the start parameter value looks higher than the output length. The error is "error_message". - AWSITA260E
The active rules output task failed because it encountered an error reading the configuration file. The error is "error_message". - AWSITA261E
Unable to return the active rules output because the "output_file" configuration file does not exist. - AWSITA262E
The user cannot launch this job because he does not have the required permissions. - AWSITA264E
The parameter, "parameter", has been specified more than once. - AWSITA265E
The parameters, "parameter_1" and "parameter_2", cannot both be specified. - AWSITA266E
The value specified for the parameter "parameter" is not valid. - AWSITA267E
The sendevent command cannot run because one or more input arguments is missing. - AWSITA268E
A value has not been specified for parameter "parameter". - AWSITA269E
The specified parameter, "parameter", is not valid. - AWSITA270E
The format of the argument, "argument", is not valid. - AWSITA271E
The mandatory parameters, "parameter1" and "parameter2", are missing. - AWSITA272E
The mandatory parameter, "parameter", is missing. - AWSITA273E
The template configuration file, "file_name", does not exist. - AWSITA274E
The template configuration file "file_name" cannot be read. - AWSITA275E
The sendevent command was not executed because an error occurred allocating a memory pool. The error message is "error_message". - AWSITA276E
The sendevent command was not executed because an error occurred locking the file "file_name". - AWSITA277E
An internal error has occurred. An error occurred while creating the Event Integration Facility handle. - AWSITA278E
An internal error has occurred. An error occurred while reading the value for "key_value" from the configuration file "onfiguration_file". Either the key is not present, or the configration file cannot be read - AWSITA279E
An internal error has occurred. The event was not sent and was instead cached in the file "cache_file". - AWSITA282E
The event was filtered out and not sent. - AWSITA283E
An error occurred while sending the event. The error code is "error_code". - AWSITA284E
The configuration file "file_name" does not exist. - AWSITA285E
The configuration file "file_name" cannot be read. - AWSITA286E
An internal error has occurred. An error occurred while initializing the environment to send the event. - AWSITA288E
The JobManagerGW subagent cannot be created. The error is "error_message". The error code is "error_code". - AWSITA289E
The JobManagerGW subagent cannot be created. The error is "error_message". The error code is "error_code". - AWSITA291E
The main component of the gateway process cannot start because an error occurred creating a thread. The error message is "error_message". - AWSITA292E
The main component of the gateway process cannot start because an error occurred allocating a memory pool. The error message is "error_message". - AWSITA295E
Cannot create the memory pool to handle the connection. The error is "error_message". The error code is "error_code". - AWSITA297E
The gateway failed to accept connections. The error is "error_message". The error code is "error_code". - AWSITA298E
The gateway failed to create the thread needed to handle the request. The error is "error_message". The error code is "error_code". - AWSITA299E
The gateway failed to accept a connection. - AWSITA300E
Failed to create the memory pool of the command handler thread. The error is "error_message". - AWSITA301W
Failed to set the stack size of command handler thread pool. The error is "error_message". - AWSITA302E
Failed to create the thread pool of the command handler. The error is "error_message". - AWSITA304E
The command is incorrect and cannot be processed. - AWSITA305E
The http method returned the following error code: "error_code" and with the following error message "error_message". - AWSITA306E
Unable to get port information from URI "uri_value". - AWSITA308E
The gateway got an error response while sending the resource information to the server. The error code is "error_code" and the error message is "error_message". - AWSITA309E
The gateway can not send the resource information to "server_uri". The error is: "error_message". - AWSITA310E
The gateway can not send the resource information to "server_uri" for a network connection problem. The error is: "error_message". - AWSITA311E
The gateway can not send the resource information due to Basic Authentication conversion problem. - AWSITA312E
Unable to get address information in payload. - AWSITA313E
Unable to get resource EPR information in payload. - AWSITA314E
Unable to get Resource Advisor URI information in payload. - AWSITA315E
The gateway failed to create the thread needed to handle the request. The error is "error_message". The error code is "error_code". - AWSITA317E
Unable to get port information from URI "uri_value". - AWSITA320E
The gateway was not able to contact the broker server at the address "server_uri" to obtain the list of actions to execute. The error is: "error_message". - AWSITA321E
The gateway was not able to contact the broker server at the address "server_uri" to obtain the list of actions to execute for a network connection problem. The error is: "error_message". - AWSITA322E
The gateway can not send the polling broker action queue information request due to Basic Authentication conversion problem. - AWSITA323E
The gateway got an error response while processing a submit request to "server_uri". The error is: "error_message". - AWSITA324E
The gateway can not send the submit request to "server_uri" for a network connection problem. The error is: "error_message". - AWSITA325E
The gateway got an error response while processing a Job log request to "server_uri". The error is: "error_message". - AWSITA326E
The gateway can not send the Job log request to "server_uri" for a network connection problem. The error is: "error_message". - AWSITA327E
Unable to get port information from URI "uri_value". - AWSITA329E
The gateway got an error response while sending the result to "server_uri". The error is: "error_message". - AWSITA330E
The gateway can not send the result to "server_uri" for a network connection problem. The error is: "error_message". - AWSITA331E
Unable to get port information from URI "uri_value". - AWSITA333E
The gateway got an error response while sending Job Status to agent. The error code is "error_code" and the error message is "error_message". - AWSITA334E
The gateway can not send the Job Status information to "server_uri". The error is: "error_message". - AWSITA335E
The gateway can not send the Job status information to "server_uri" for a network connection problem. The error is: "error_message". - AWSITA336E
The gateway can not send Job status information due to Basic Authentication conversion problem. - AWSITA340E
The command "action" is not supported. - AWSITA342E
The PUT method was not executed on the uri "uri". The error is: "error_message". - AWSITA343E
The kill of the job with the uri "uri" failed. The error is: "error_message". - AWSITA345E
The executor command on the agent with the uri "uri" failed. The error is: "error_message". - AWSITA347E
The executor command on the agent with the uri "uri" failed. The error is: "error_message". - AWSITA349E
The component command on the agent with the uri "uri" failed. The error is: "error_message". - AWSITA350E
Cannot able to decrypt gateway password. - AWSITA351E
Cannot able to encrypt gateway password. - AWSITA352E
Cannot able to update gateway password in file. - AWSITA353E
Cannot able to retrive gateway password from file. - AWSITA354E
The gateway could not poll the broker action queue on "server_uri". The error code is: "error_code" and the error message is "error_message". - AWSITA355E
Error while preparing URI's of gateway. - AWSITA356E
An error occurred setting the http proxy. The error is "error_message". - AWSITA357E
The Event Driven Workload Automation file download failure from "event processor address". The error message is "error_message". - AWSITA358E
The Event Driven Workload Automation file download failure, retry requested from "event processor address". The error message is "error_message". - AWSITA360E
Unable to send Event Driven Workload Automation file download request on "event processor address" for a network connection problem. The error is: "error_message". - AWSITA361E
An error occurred parsing the following JSON string "string". - AWSITA362E
An error occurred processing the action. The error is "error_message". - AWSITA364E
The reset command on the agent with the uri "uri" failed. The error is: "error_message". - AWSITA366E
The POST method was not executed on the uri "uri". The error is: "error_message". - AWSITA368E
Failed to download agent zip file from master with the following error: "error". - AWSITA369E
Reached timeout waiting for running jobs: Agent centralized update aborted. - AWSITA371E
Failed to unzip agent package file: "zipfile". - AWSITA373E
Failed to send status to server. The errorcode is: "exitcode". Command output is "output". - AWSITA374E
Centralized agent update DownloadDir path not valid: "path". - AWSITA375E
An internal error has occurred. An error occurred while initializing the environment to receive the event. - AWSITA376E
The Event Driven Workload Automation component of the gateway process cannot start because an error occurred allocating a memory pool. The error message is "error_message". - AWSITA377E
The required "space" megabytes of disk space are not available in the "directory" directory. - AWSITA378E
This agent was installed with a user that does not have the required permissions to impersonate the job user. - AWSITA379E
Reached timeout waiting for update job to start: Agent centralized update aborted. - AWSITA380E
Cannot retrieve the job with ID "job_id" because the agent job store is corrupted. The job instance is removed from the job table. - AWSITA381E
The jobprop command has to be invoked by a job. - AWSITA383E
The post job execution script "script" for the job with id "job_id" cannot be started because an error occurred. The error message is "error_message". - AWSITA384E
The post job execution script "script" cannot be found. - AWSITA386E
Unable to send a reply to the message with ID "message_id" for the job with ID "job_id". The error is "error_message". - AWSITA390E
Unable to read the message properties file for the job with ID "job_id". The error is "error_message". - AWSITA391E
The message with ID "message_id" for the job with ID "job_id" cannot be found. - AWSITA392E
The message properties file for the job with ID "job_id" contains invalid data. - AWSITA395E
Cannot invoke command for the job with ID "job_id" because it is not available in the agent job store. - AWSITA396E
Failed to unzip Workload Application Template export file: "wat_export_zip_file". - AWSITA397E
Unable to create the Workload Application Template export file: "wat_export_zip_file". - AWSITA399E
The connection with the server fails. - AWSITA400E
The submitted command cannot be performed. The error is: "error_msg" - AWSITA401E
The server cannot find the requested service or the server configuration does not support providing the requested service. - AWSITA403E
The filemonitor command cannot run because one or more input arguments are missing. - AWSITA404E
Incorrect event. Supported events are fileCreated and fileModified. - AWSITA405E
The job properties file cannot be updated if the file monitor is not invoked by a job. - AWSITA406E
The value specified for command argument "string" must be a valid non-negative integer. - AWSITA407E
The path specified for command argument "string" must be a valid path. - AWSITA408E
The path specified for command argument "string" does not support wildcards. - AWSITA409E
The path specified for command argument "string" must point to a file. - AWSITA410E
The path specified for command argument "string" must point to a directory. - AWSITA411E
The value specified for command argument repository_name must contain only a valid file name. - AWSITA413E
No folders were found matching the "search_path" search path. - AWSITA414E
Unable to retrieve the files in "search_path" because the path does not exist. - AWSITA415E
The timeout has expired. - AWSITA416E
You do not have read and/or write permission(s) on path "full_path_name". - AWSITA417E
Cannot create or operate on "output_file" file. The error is "error_message". - AWSITA418E
Cannot obtain exclusive access to the repository "repository_full_path_name". - AWSJCL - Command line messages
This section lists error and warning messages that might be generated when using the command line. - AWSJCL001E
The object "object_key" cannot be updated because it is locked by you in another session or by another user. - AWSJCL002E
An internal error has occurred. The command "command" passed to the server from the command line client is not a recognizable HCL Workload Automation command. - AWSJCL004E
The command "command" completed with errors on object "object_key". The reason is "reason". - AWSJCL005E
The server could not encrypt the user password. - AWSJCL006E
The object "object_key" cannot be locked because it is already locked by the following user "user" in another session. - AWSJCL007E
The object "object_key" cannot be locked because it is already locked by the following user "user". - AWSJCL008E
The server has encountered an unexpected error communicating with the client. - AWSJCL010W
You have attempted to delete the master domain ("domain"), which is not allowed. - AWSJCL011E
An internal error has occurred. The expected parameter "parameter" was missing for the command "command". - AWSJCL012E
The object "object_key" cannot be unlocked because you have no UNLOCK authorization for this object in the security file or because it is locked by the user "user" in a different session. - AWSJCL013E
The object "object_key" cannot be updated because it is not locked. - AWSJCL014W
The object "object_key", which you locked using the lock command, is no longer locked. The lock might have been removed by another user or it could have been remove by your own process. This can happen when the modify command fails to update some of the selected objects and you choose to re-edit failed objects. - AWSJCL015W
The object "object_key" already exists. - AWSJCL017W
No objects have been found that match the criteria in the command. - AWSJCL019E
An internal error has occurred. The parameter "parameter" is not in the correct format. - AWSJCL020E
The master domain manager workstation has not been defined in the database. - AWSJCL021E
An internal error has occurred. Unable to retrieve the master domain manager workstation name. The reason is as follows: "reason". - AWSJCL022E
An internal error has occurred. Unable to retrieve a global option "option" from the database. The reason is as follows: "reason". - AWSJCL023E
The object "object_key" cannot be unlocked because you have no UNLOCK authorization for this object in the security file or because it is locked by the following user "user". - AWSJCL024W
You have included one or more time zone definitions in the command but time zone support is not enabled. - AWSJCL025W
The job "job" defined in job stream "job_stream" has a schedtime time that is later than its until time. - AWSJCL026W
The runcycle "run_cycle" defined in job stream "job_stream" has a schedtime time that is later than its until time. - AWSJCL027W
The job "job" defined in job stream "job_stream" has an until time that is later than its deadline time. - AWSJCL028W
The runcycle "run_cycle" defined in job stream "job_stream" has an until time that is later than its deadline time. - AWSJCL029W
The job "job" defined in job stream "job_stream" has a schedtime time that is later than its deadline time. - AWSJCL030W
The runcycle "run_cycle" defined in job stream "job_stream" has a schedtime time that is later than its deadline time. - AWSJCL031W
The job "job" defined in job stream "job_stream" has a dependency in which its from time is later than its to time. - AWSJCL032W
The job stream "job_stream" defines a matching criteria definition in which its from time is later than its to time. - AWSJCL033W
The job stream "job_stream" has a dependency on the job "job"in which its from time is later than its to time. - AWSJCL034W
Insufficient resource units are available.Resource "resource" has "available_units" units available, but the job stream "job_stream" requires "required_units" units. - AWSJCL035W
Insufficient resource units are available.The resource "resource" has "available_units" units available, but the job "job" defined in the job stream "job_stream" requires "required_units" units. - AWSJCL036W
The resource is not defined for the same workstation or workstation class as the job stream.Job stream "job_stream" is defined for workstation or workstation class "job_stream_target"; resource "resource" is defined for workstation or workstation class "resource_target". - AWSJCL037W
The resource is not defined for the same workstation or workstation class as the job.Job "job" is defined for workstation or workstation class "job_target"; resource "resource" is defined for workstation or workstation class "resource_target". - AWSJCL038W
The job stream "job_stream" has a schedtime time that is later than its until time. - AWSJCL039W
The job stream "job_stream" has an until time that is later than its deadline time. - AWSJCL040W
The job stream "job_stream" has a schedtime time that is later than its deadline time. - AWSJCL041E
The object "object" does not exist. - AWSJCL042E
The object "object" cannot be deleted because it is referenced by the following object or objects: - AWSJCL043W
The job stream "job_stream" contains the following critical jobs "job_name_list" but the database property "db_property_name" is set to "db_property_value". - AWSJCL044W
You have attempted to delete the default variable table ("variable_table"), which is not allowed. - AWSJCL045E
The default variable table has not been defined in the database. - AWSJCL046E
An internal error has occurred. Unable to retrieve the default variable table name. The reason is as follows: "reason". - AWSJCL047W
You have defined "new_table" to become the default variable table: "old_table", which is the current default, will be modified to become an ordinary variable table. - AWSJCL048W
The run cycle group "run_cycle_group" has a schedtime time that is later than the until time. - AWSJCL049W
The run cycle group "run_cycle_group" has an until time that is later than the deadline time. - AWSJCL053E
An internal error has occurred. The command passed one or more parameters to this program that are not valid. - AWSJCL054E
The command "command" has failed, for the following reason: "reason". - AWSJCL075E
Symphony file load has failed. Check the application server logs for additional information. - AWSJCL080W
The run cycle group "run_cycle_group" has a schedtime time that is later than the deadline time. - AWSJCL081W
The run cycle "run_cycle" defined in the run cycle group "run_cycle_group" has a schedtime time that is later than the until time. - AWSJCL082W
The run cycle "run_cycle" defined in the run cycle group "run_cycle_group" has an until time that is later than the deadline time. - AWSJCL083W
The run cycle "run_cycle" defined in the run cycle group "run_cycle_group" has a schedtime time that is later than the deadline time. - AWSJCL084E
The object "object" cannot be deleted because it is referenced by the following object or objects: "object_name_list" - AWSJCL086W
The run cycle "run_cycle" defined in the run cycle group "run_cycle_group" has an every end time that is later than the until time. - AWSJCL087W
The run cycle group "run_cycle_group" has an every end time that is later than the until time. - AWSJCL088W
The run cycle "run_cycle" defined in the run cycle group "run_cycle_group" has an every end time that is later than the deadline time. - AWSJCL089W
The run cycle group "run_cycle_group" has an every end time that is later than the deadline time. - AWSJCL090W
The runcycle "run_cycle" defined in job stream "job_stream" has a every end time that is later than its deadline time. - AWSJCL091W
The runcycle "run_cycle" defined in job stream "job_stream" has a every end time that is later than its until time. - AWSJCL092W
The polling interval value "interval" defined for start condition "start_condition" in job stream "job_stream" is not divisible by 60. The value will be approximated to "rounded_interval". - AWSJCL093W
The polling interval value "interval" for job "job" defined in job stream "job_stream" is not divisible by 60. The value will be approximated to "rounded_interval". - AWSJCL100E
The option short name "option_short_name" is not valid. Valid short names are as follows: "option_short_name_list". - AWSJCL101E
The option long name "option_long_name" is not valid. Valid long names are as follows: "option_long_name_list". - AWSJCL102E
An internal error has occurred. The internal option database name "option_database_name" is not valid. Valid option database names are: "option_database_name_list". - AWSJCL103E
The input format of the option "option_input_format" is not valid. Valid option input formats are as follows: "option_input_format_list". - AWSJCL105E
The property "Property name" is empty. - AWSJCL106E
The provider URI " " is malformed. - AWSJCL300E
An internal error occurred while loading the XML Schema file "schema_file_name" used by the XML parser. - AWSJCL301E
An internal error occurred while configuring the HCL Workload Automation parser properties and features. - AWSJCL302E
An internal error occurred while parsing the XML file created by the XML Formatter component. - AWSJCL303E
An internal error has occurred with the syntax of the created XML file. The object type "object_type" with key "key" is not valid. - AWSJCL305E
A date format is not valid. - AWSJCL306E
The following error has occurred with the syntax of the created XML file: "reason" - AWSJCL307E
The value "attribute_value" specified for the attribute "attribute_name" is not allowed. - AWSJCL308E
The following error occurred while parsing the value "attribute_value" specified for the attribute "attribute_name": "reason" - AWSJCL309E
The attribute "attribute_name" is not allowed inside the tag: "tag_name". - AWSJCL310E
The tag name "tag_name" is not allowed. - AWSJCL311E
The required attribute "attribute_name" is missing inside the tag "tag_name". - AWSJCL312E
The line "line", in the created XML file, contains the following error: "reason" - AWSJCL500W
The workstation "workstation" was not migrated because it has the same name as the master workstation in the version 8.4 database. - AWSJCL501W
The workstation "workstation" has been created as full status because it is a domain manager. - AWSJCL502W
The domain "domain" referenced by workstation "workstation" does not exist. The workstation has been created as belonging to the master domain. - AWSJCL503W
The host "host_workstation" referenced by workstation "workstation" does not exist. The workstation has been created with the master domain manager as its host. - AWSJCL504W
The parent domain "parent_domain" referenced by domain "domain" does not exist. The domain has been created with the master domain as it parent. - AWSJCL505W
The workstation "workstation" referenced by workstation class "workstation_class" does not exist. The workstation class has been created omitting the workstation. - AWSJCL506E
The workstation or workstation class "workstation_or_workstation_class" referenced by job stream "job_stream" does not exist. The job stream is not migrated. - AWSJCL507W
The calendar "calendar" referenced by job stream "job_stream" does not exist. The calendar reference is not migrated with the job stream. - AWSJCL508W
The calendar "calendar" referenced by a run cycle in job stream "job_stream" does not exist. The run cycle reference is not migrated with the job stream. - AWSJCL509W
The job definition "job_definition" referenced by job "job" in job stream "job_stream" does not exist. A dummy job definition is created and the job is modified to refer to it. - AWSJCL510W
The prompt "prompt" referenced as a dependency by job stream "job_stream" does not exist. A dummy prompt is added and the migrated job stream is modified to refer to it. - AWSJCL511W
The resource "resource" referenced as a dependency by job stream "job_stream" does not exist. The resource is created and the job stream is migrated. - AWSJCL512W
The workstation "workstation" referenced in a file dependency by job stream "job_stream" does not exist. A dummy file dependency is created and the migrated job stream is modified to refer to it. - AWSJCL513W
The job stream "dependent_job_stream" referenced in an external dependency by job stream "job_stream" does not exist. This dependency has been removed in the migrated job stream. - AWSJCL514W
The job "dependent_job" referenced in an external dependency by job stream "job_stream" does not exist. This dependency has been removed in the migrated job stream. - AWSJCL515W
The workstation "workstation" referenced in a network dependency by job stream "job_stream" is not an extended agent. A dummy extended agent is created and the migrated job stream is modified to refer to it. - AWSJCL516W
The workstation "workstation" referenced in a network dependency by job stream "job_stream" does not exist. This dependency has been removed in the migrated job stream. - AWSJCL517E
The workstation or workstation class "workstation_or_workstation_class" referenced by job definition "job_definition" does not exist. The job definition has not been migrated - AWSJCL518W
The recovery job "recovery_job" referenced by job "job" does not exist. The job is migrated without its recovery job. - AWSJCL519E
The workstation or workstation class "workstation or workstation class" referenced by resource "resource" does not exist. The resource is not migrated. - AWSJCL520E
The workstation "workstation" referenced by Windows user "Windows_user" does not exist. The user is not migrated. - AWSJCL521E
The password specified for the Windows user "Windows_user" does not comply with password security policy requirements. - AWSJCL522W
The file dependency referenced in job stream "job_stream" is incorrect. The file name "filename" exceeds the maximum length of "max_length" bytes. This dependency has been removed from the migrated job stream and the priority is set to 0. - AWSJCL523W
The file dependency referenced in the job stream "job_stream" is incorrect. The concatenation of the file path "path" and the file qualifier "qualifier" exceeds the maximum length of "max_length" bytes. This dependency has been removed from the migrated job stream and the priority is set to 0. - AWSJCL524E
The job definition "job" contains a null value for one or more of the following keywords: docommand , scriptname , or streamlogon . The job definition has not been migrated. - AWSJCL525E
The server was unable to load the requested objects within the timeout period of "timeout" seconds - AWSJCL526W
The workstation "workstation" (previously defined as MANGER) has been imported as a fault-tolerant agent because the domain manager already exists. - AWSJCL531E
The event rule "event_rule" contains a duplicate action parameter: "parameter_name". - AWSJCL533E
The operating system value, "osType", specified for the workstation "ftaName" being defined, is not a supported operating system value for a fault-tolerant agent workstation. Valid values are: UNIX, WNT or OTHER - AWSJCL534E
An error occurred when encoding the request. The following error message has additional details: "errorMsg" - AWSJCL535E
An error occurred when encoding the request. The following error message has additional details: "errorMsg" - AWSJCL536E
An error occurred when encoding the request. The following error message has additional details: "errorMsg" - AWSJCL537E
An error occurred when encoding the request. The following error message has additional details: "errorMsg" - AWSJCL538E
An error occurred when encoding the request. The following error message has additional details: "errorMsg" - AWSJCL539E
An error occurred when parsing the request. The following error message has additional details: "errorMsg" - AWSJCL540E
An error occurred when initializing the connection for plan. The following error message has additional details: "errorMsg" - AWSJCL541E
An error occurred when initializing the connection for plan. The following error message has additional details: "errorMsg" - AWSJCL542E
An error occurred when initializing the connection for plan. The following error message has additional details: "errorMsg" - AWSJCL543E
An error occurred when processing the request. The following error message has additional details: "errorMsg" - AWSJCL544E
An error occurred when processing the request. The following error message has additional details: "errorMsg" - AWSJCL545E
An error occurred when processing the request. The following error message has additional details: "errorMsg" - AWSJCL546E
An error occurred when processing the request. The following error message has additional details: "errorMsg" - AWSJCL547E
An error occurred when processing the request. The following error message has additional details: "errorMsg" - AWSJCL548E
An error occurred when processing the request. The following error message has additional details: "errorMsg" - AWSJCL549E
An error occurred when processing the request. The following error message has additional details: "errorMsg" - AWSJCL550E
There is an error in the URI syntax. The following error message has additional details: "errorMsg" - AWSJCL553W
Centralized agent update not perfomed on workstation "agentZip" since its version: "agentVersion" is greater than or equal to agent version available on the master: "masterVersion" - AWSJCL554E
Agent zip file not found in depot folder: "depot" for operating system: "arch" and version: "agentVersion" - AWSJCL555W
The "keyword" variable is longer than the maximun number of bytes and will be truncated. - AWSJCL556W
A logman report is already running. Any other requests are skipped until the current operation completes. - AWSJCL557W
The edit job action was not applied because the job was in a not supported status. The job instance changes were not applied. - AWSJCO - Connectors messages
This section lists error and warning messages that might be generated by the connectors. - AWSJCO001E
An internal error has occurred. The properties "missing_properties" that are needed to initialize the connection factory internal component are missing. - AWSJCO002E
An internal error has occurred. The properties "unsupported_properties" that are needed to initialize the connection factory internal component are not supported. - AWSJCO003E
An internal error has occurred. The connection properties that are needed to initialize the connection factory internal component are null. - AWSJCO004E
The WebSphere Application Server is down. - AWSJCO005E
WebSphere Application Server has given the following error: "error_message". - AWSJCO006E
An internal error has occurred. The method "method" is not supported. - AWSJCO007E
An internal error has occurred. An incorrect parameter "parameter" was used in API "API". The reason for the error is "reason". - AWSJCO008E
The name specified for the workstation host "incorrect_workstation_host" is not allowed. You cannot, in the same action, change the workstation name and use the previous workstation name as the workstation host. - AWSJCO009E
An internal error has occurred. The method "method" has been called with an object of an unsupported class "class". - AWSJCO010E
An internal error has occurred. A null parameter "parameter" was used in API "API" called by module "module". - AWSJCO011E
An internal error has occurred. The parameters "parameter1" and "parameter2" used in API "API" called by module "module" are inconsistent. An object cannot be unlocked if it is not already locked. - AWSJCO012E
An internal error has occurred. The parameters "parameter1" and "parameter2" used by API "API" called by module "module" are inconsistent. It is not possible to specify an empty context when the object is expected to be locked. - AWSJCO013E
An internal error has occurred. The parameter how many used in API "API" called by module "module" must be zero or a positive integer. - AWSJCO014E
The database has been locked by the planner process. - AWSJCO015E
An internal error has occurred. Java class "class" could not be found. - AWSJCO016E
The object "object" cannot be created or updated because it already exists or overlaps with an existing one. - AWSJCO017E
The domain "domain" cannot be created or modified because to do so would create the following looped domain chain "looped_domain_chain", where the domain "domain" (the first in the list) is linked in one or more child-parent relationships to itself. - AWSJCO018E
The job stream cannot be created or modified as the job "job" contains a dependency that would create the following looped dependency chain within the job stream "looped_job_dependency_chain". - AWSJCO019E
The name specified for the parent domain "incorrect_parent" is not allowed. You cannot, in the same action, change the domain name and use the previous domain name as its parent. - AWSJCO020E
The parent domain "parent_domain" referenced by domain "domain" does not exist. - AWSJCO021E
The object "object" cannot be deleted because it is referenced by the following objects: "referencing_objects". - AWSJCO022E
The workstation "workstation" cannot become the domain manager of the domain "domain" because the domain already has a domain manager: "domain_manager". - AWSJCO023E
The string used to identify the session "session_string" is longer than 36 bytes. - AWSJCO024E
Task type "non-valid_task_type" is not valid for job definition "job_definition". For this job definition the only valid task type is: "valid_task_type". - AWSJCO025E
A master domain manager cannot be created. It must be installed. - AWSJCO026E
User "user" is not authorized to perform the action "action" on an object "object_type" and key "object". - AWSJCO028E
The object cannot be accessed because the user "user" is not defined in the Security file. - AWSJCO029E
The name specified for the workstation "workstation" is not allowed. A workstation and its host cannot have the same name as its host. - AWSJCO030E
The host "host" supplied for workstation "workstation" cannot be used because it is an extended agent. - AWSJCO031E
The host "host" supplied for workstation "workstation" cannot be used because it is a workstation class. - AWSJCO032E
The workstation "workstation" referenced by job definition "job_definition" does not exist. - AWSJCO033E
The host "host" supplied in the definition of workstation "workstation" does not exist. - AWSJCO034E
The workstation "workstation" referenced by user "user" does not exist. - AWSJCO035E
The Windows user "Windows_user" cannot be added for workstation "workstation" because the workstation operating system is not Windows. - AWSJCO036E
The workstation type of workstation "workstation" cannot be changed to extended agent (XA) as the workstation is the host of the extended agent workstation "extended_agent_workstation", and extended agents cannot be hosts of other extended agents. - AWSJCO037E
The recovery job "recovery_job" referenced by a job definition "job_definition" does not exist. - AWSJCO038E
The domain "domain" referenced by workstation "workstation" does not exist. - AWSJCO039E
The value specified for the parent domain "parent_domain_name" is not allowed. A domain and its parent cannot have the same name. - AWSJCO040E
The job definition"job_definition" of job "job" in job stream "job_stream_name" does not exist. - AWSJCO041E
The time zone "time_zone" is not valid in the definition of the object type "object_type" with the following key "object_key". - AWSJCO042E
An internal error has occurred. The specified key type "key_type" is not valid. The expected key type is: "expected_key_type". - AWSJCO043E
An error occurred decrypting the Windows user password. The decryption key (the domain name concatenated with the user name) might be incorrect. - AWSJCO044E
An error occurred encrypting the Windows user password. The encryption key (the domain name concatenated with the user name) might be incorrect. - AWSJCO045E
While trying to lock multiple objects as the result of the use of a wildcard in the selection criteria, one or more of the objects could not be locked. - AWSJCO046E
The workstation "workstation" defined in job stream "job_stream" does not exist. - AWSJCO047E
The name specified for the recovery job "recovery_job_name" is not allowed. A job and its recovery job cannot have the same name. - AWSJCO048E
The name specified for the recovery job "recovery_job_name" is not allowed. You cannot, in the same action, change the job definition name and use the old job definition name as the recovery job name. - AWSJCO049E
The host "host" supplied for workstation "workstation" cannot be used because it must be a workstation of type broker. - AWSJCO050E
User "user" is not authorized to perform the action "action" on object type "object_type" with key "object". - AWSJCO051E
The length of the specified Windows user password, "supplied_password_length" bytes, exceeds the maximum length of "max_password_length" bytes. - AWSJCO052E
User "user" is not authorized to perform the action "action" on the file "file_name". - AWSJCO053E
User "user" is not authorized to perform the action "action" on the report "report_name". - AWSJCO054E
The option "option" does not exist. - AWSJCO055E
User "user" is not authorized to perform the action "action" on the line of business "lob_name". - AWSJCO056E
You cannot specify the plan ID for the operation "operation". - AWSJCO057E
The job stream "job_stream" cannot be created or modified as the workstation "workstation" is not an extended agent, and only extended agents can have internetwork dependencies. - AWSJCO058E
The dependency for the job "job" cannot be added to the job stream "job_stream" as the workstation "workstation" is not an extended agent, and only extended agents can act as network agents. - AWSJCO059E
The workstation "workstation_name" is of type "workstation_type", it cannot be manually created. - AWSJCO060E
A job definition cannot have a different workstation class than the workstation class of its job stream. Job stream "job_stream" runs on workstation class "job_stream_workstation_class", but workstation class "workstation_class" is defined in job definition "job_definition" of job "job" in that job stream. - AWSJCO061E
A job cannot be defined for a workstation class if the job stream to which it belongs runs on a workstation. Job stream "job_stream" runs on workstation "job_stream_workstation", but a workstation class ("workstation_class") has been defined in job definition "job_definition" of job "job"of that job stream. - AWSJCO062E
A resource cannot have a different workstation class than the workstation class of its job stream. Job stream "job_stream" runs on workstation class "job_stream_workstation_class", but workstation class "workstation_class" is defined in the dependency on resource "resource" in that job stream. - AWSJCO063E
A resource dependency of a job cannot have a different workstation class than the workstation class of the job stream to which the job belongs. Job stream "job_stream" runs on workstation class "job_stream_workstation_class", but workstation class "workstation_class" is defined in the dependency on resource "resource" of job "job" in that job stream. - AWSJCO064E
A resource dependency cannot be defined for a workstation class if the job stream to which it belongs runs on a workstation. Job stream "job_stream" runs on workstation "job_stream_workstation", but a workstation class ("workstation_class") has been defined in the dependency on resource "resource" in that job stream. - AWSJCO065E
A resource dependency of a job definition cannot be defined for a workstation class if the job stream to which the job belongs runs on a workstation. Job stream "job_stream" runs on workstation "job_stream_workstation", but a workstation class ("workstation_class") has been defined in the dependency on resource "resource" of job "job" in that job stream. - AWSJCO066E
A file dependency cannot be for a different workstation class than the workstation class of its job stream. Job stream "job_stream" runs on workstation class "job_stream_workstation_class", but workstation class "workstation_class" is defined in the dependency on file "file" in that job stream. - AWSJCO067E
A file dependency of a job cannot have a different workstation class than the workstation class of the job stream to which the job belongs. Job stream "job_stream" runs on workstation class "job_stream_workstation_class", but workstation class "workstation_class" is defined in the dependency on file "file" of job "job" in that job stream. - AWSJCO068E
A file dependency cannot be defined for a workstation class if the job stream to which it belongs runs on a workstation. Job stream "job_stream" runs on workstation "job_stream_workstation", but a workstation class ("workstation_class") has been defined in the dependency on file "file" in that job stream. - AWSJCO069E
A file dependency of a job definition cannot be defined for a workstation class if the job stream to which the job belongs runs on a workstation. Job stream "job_stream" runs on workstation "job_stream_workstation", but a workstation class ("workstation_class") has been defined in the dependency on file "file" of job "job" in that job stream. - AWSJCO070E
An external dependency cannot be created on a job stream with a different workstation class than the workstation class of the job stream to which the dependency belongs. Job stream "job_stream" runs on workstation class "job_stream_workstation_class", but the external job stream on which you want it to be dependent "external_job_stream" runs on a different workstation class "external_job_stream_workstation_class". - AWSJCO071E
An external dependency cannot be created on a job with a different workstation class than the workstation class of the job stream to which the dependency belongs. Job stream "job_stream" runs on workstation class "job_stream_workstation_class", but the external job on which you want it to be dependent "external_job" in external job stream "external_job_stream" runs on a different workstation class "external_job_workstation_class". - AWSJCO072E
An external dependency cannot be created on a job stream defined for a workstation class if the job stream to which the dependency belongs runs on a workstation. Job stream "job_stream" runs on workstation "job_stream_workstation", but the external job stream on which you want it to be dependent "external_job_stream" runs on a workstation class: "external_job_stream_workstation_class". - AWSJCO073E
An external dependency cannot be created on a job defined for a workstation class if the job stream to which the dependency belongs runs on a workstation. Job stream "job_stream" runs on workstation "job_stream_workstation", but the external job on which you want it to be dependent "external_job" in external job stream "external_job_stream" runs on workstation class "external_job_workstation_class". - AWSJCO074E
The job definition in the action with plug-in name "plug-in_name" and action type "action_type" does not exist. - AWSJCO075E
The job stream in the action with plug-in name "plug-in_name" and action type "action_type" does not exist. - AWSJCO080E
The workstation "workstation" referred to in a job stream internetwork dependency does not exist. - AWSJCO081E
The resource "resource" referred to in a resource dependency in job stream "job_stream" does not exist. - AWSJCO082E
The resource "resource" referred to in a resource dependency in job "job" in job stream "job_stream" does not exist. - AWSJCO083E
The object "object" cannot be found. - AWSJCO084E
The user "user" is not authorized to work with the planner process. - AWSJCO085E
The workstation "workstation" referenced by object "object" does not exist. - AWSJCO086E
The list of TWSObjects passed in input to the validateTWSObjects connector API cannot be null or empty. - AWSJCO087E
The name and workstation of job stream "job_stream" cannot be changed because another job stream already exists with the supplied name and workstation. Two job streams can only have the same name and workstation if one has been created, not updated, as a version of the other. - AWSJCO090E
An external dependency cannot be created on a job stream with a different workstation class than the workstation class of the job to which the dependency belongs. Job "job" in job stream "job_stream" runs on workstation class "job_workstation_class", but the external job stream on which you want it to be dependent "external_job_stream" runs on a different workstation class "external_job_stream_workstation_class". - AWSJCO091E
An external dependency cannot be on a job with a different workstation class than the workstation class of the job to which the dependency belongs. Job "job" in job stream "job_stream" runs on workstation class "job_workstation_class", but the external job on which you want it to be dependent "external_job" in external job stream "external_job_stream" runs on a different workstation class "external_job_workstation_class". - AWSJCO092E
An external dependency cannot be on a job stream defined for a workstation class if the job to which the dependency belongs runs on a workstation. Job "job" in job stream "job_stream" runs on workstation "job_workstation", but the external job stream on which you want it to be dependent "external_job_stream" runs on a workstation class: "external_job_stream_workstation_class". - AWSJCO093E
An external dependency cannot be on a job defined for a workstation class if the job to which the dependency belongs runs on a workstation. Job "job" in job stream "job_stream" runs on workstation "job_workstation", but the external job on which you want it to be dependent "external_job" in external job stream "external_job_stream" runs on workstation class "external_job_workstation_class". - AWSJCO094E
Job stream "job_stream" has an external dependency that refers to itself, but the dependency resolution criteria is not closest preceding (previous). - AWSJCO095E
The number of output lines must be greater than zero. - AWSJCO096E
The job key "key" is not in the correct format, which is: workstation_name#job_name. - AWSJCO097E
The job stream key "key" is not in the correct format, which is: workstation_name#job_stream_name. - AWSJCO098E
The job stream cannot be submitted because no job stream with key "key" and valid on "scheduled_date" at "scheduled_time" was found. - AWSJCO099E
The supplied Web Service parameter "parameter" is not a valid parameter. - AWSJCO100E
The value "value" specified for the supplied Web Service parameter "parameter" is not valid. - AWSJCO101E
The specified filter "filter" is not a valid filter. - AWSJCO102E
The value specified for filter "filter" is not valid. - AWSJCO103E
The value specified for filter "filter" is not valid for the following reason: "reason". - AWSJCO104E
The required service "service" can only be run on a domain manager or backup domain manager, as it requires a server configuration that can access the modelling information. - AWSJCO105E
The job cannot be submitted because no job with key "job_key" was found in the database. - AWSJCO106E
The chosen object was created or modified with a version of the engine, Dynamic Workload Console, or application that is later than the version of the Dynamic Workload Console or application you are currently using.To view or modify the object, upgrade the Dynamic Workload Console or the application. - AWSJCO107E
Message GJS0073E is not completely accurate. The chosen object can be viewed but not modified because it was created or modified with a version of the engine, Dynamic Workload Console, or application that is later than the version of the Dynamic Workload Console or application you are currently using.To modify the object, upgrade the Dynamic Workload Console or the application. - AWSJCO108E
An internal error has occurred. - AWSJCO109E
Unable to create an instance of the action plug-in "plug-in_name". - AWSJCO110E
Unable to create an instance of the event plug-in "plug-in_name". - AWSJCO111E
An internal error occurred when the event processor was attempting to create an instance of the plug-in "plug-in_name". - AWSJCO112E
An internal error occurred when the event processor was attempting to access the event rule "rule_name". - AWSJCO117E
The event rule "rule_name" contains two or more event conditions having the same name: "event_name". - AWSJCO118E
An error occurred while event processor was attempting to get the basename for an event condition of type "event_type" inside the event rule "rule_name". - AWSJCO120W
It is not possible to build the event rule "rule_name". The rule status is set to ERROR. - AWSJCO121E
The active start offset and end offset must differ by at least 1 second. - AWSJCO122E
The valid to value must be greater than the valid from value. - AWSJCO123E
The user "user" is not authorized to perform the action "action" on an object "object_type" with attributes: "attributes". - AWSJCO124E
The user "user" is not authorized to perform the action "action" on an object "object_type" with name "rule_name". - AWSJCO127E
The event processor (rule builder) has stopped because the timeout has expired. When the event processor is restarted all rules will be rebuilt. - AWSJCO128E
The rule builder cannot build the rules because the event processor is not running. - AWSJCO131E
User "user" is not authorized to perform the action "action" on the variable with key "key" because the user is not authorized to perform the action "variable_table_action" on the VariableTable with key "variable_table_key". - AWSJCO132E
User "user" is not authorized to perform the action "action" on the variable with key "key" because the user is not authorized to perform the action "variable_table_action" on the default VariableTable with key "default_variable_table_key". - AWSJCO133E
You cannot add "variable" variable because the variable table is locked, probably by different user. - AWSJCO134E
You cannot modify the object "object_key" because it contains functions that are not supported by current client. - AWSJCO135W
The global option "option" cannot be obtained from the database. The default value "value" is used instead. - AWSJCO136E
No more than "max_users" users can perform this operation at the same time. The maximum number of concurrent requests was reached: try again later. - AWSJCO137E
The workstation "memeber" supplied in the definition of workstation "workstation" cannot be used because it must be a workstation of type agent. - AWSJCO138E
The workstation "member" supplied in the definition of workstation "workstation" does not exist. - AWSJCO139E
The workstations "members" specified as jsdl:orderedCandidatedWorkstations in the dynamic pool with key "dpool" are not agents or remote engines. - AWSJCO140E
The workstation "workstation" referenced by job definition "job_definition" is not agent, pool, dynamic pool, or remote engine. - AWSJCO141E
For the workstation "workstation", the OS value in not valid. For remote engine workstations, the OS value must be different from OTHER. - AWSJCO142E
You cannnot use the reserved keyword "keyword" as a value in a workstation definition. - AWSJCO143E
The workstation "workstation" referenced by job definition "job_definition" is not of type broker. - AWSJCO144E
There was an error getting the address of the workstation "workstation". - AWSJCO145E
The workstation "workstation" cannot be defined on the domain "domain" because another workstation with type broker "broker" is defined on the same domain. - AWSJCO146E
The workstation "workstation" with type agent cannot be created because the already existing workstation "agent" of type agent has the same agent identifier. - AWSJCO147E
A file dependency cannot be defined on a workstation "workstation" of type remote engine, or broker. - AWSJCO148E
The calendar "calendar" referenced by object "object" does not exist. - AWSJCO149E
The host "host" supplied for workstation "workstation" cannot be used because it is either a pool or dynamic pool. - AWSJCO150E
The workstation "workstation" cannot be removed from the plan. - AWSJCO151E
The specified workstation: "workstation" cannot be used because it is either a pool or dynamic pool. - AWSJCO152E
Output condition names must be unique. The output condition name "output_condition_name" specified already exists. - AWSJCO153E
The output condition name "output_condition_name" is not valid. - AWSJCO154E
The output condition name or the output condition mapping expression is empty. - AWSJCO155E
An internal error has occurred. A incorrect status condition was provided in the conditional dependency. When the predecessor is a job, valid status conditions are: started, fail, error, succ, and suppress. When instead the predecessor is a job stream, valid status conditions are: error, succ, and suppress. - AWSJCO156E
An internal error has occurred. The started status conditional dependency is defined with another conditional dependency. - AWSJCO157E
An internal error has occurred. The internal dependency is not allowed for the job stream definition. - AWSJCO158E
An internal error has occurred. For the joined conditional dependencies "joinname", referenced by object "objkey", the number of dependencies to be met "joinqnt" is incorrect. It must be zero or a positive integer, and cannot be greater than the total number of subsequent predecessors. - AWSJCO159E
The output condition name "output_condition_name" is not valid. The name "output_condition_name" is valid for successful output conditions only. - AWSJCO160E
You cannot define conditional dependencies on the object "obj_key" because the workstation "workstation_name" is at version "workstation_version". The minimum supported workstation version for conditional dependencies is "minimum_version". - AWSJCO161E
You cannot define output conditions on the job "job_key" because the workstation "workstation_name" is at version "workstation_version". The minimum supported workstation version for output conditions is "minimum_version". - AWSJCO162E
An internal error has occurred. For the joined conditional dependencies "joinname", referenced by object "objkey", the dependencies to be met are not defined. At least one dependency must be provided. - AWSJCO163E
An internal error has occurred. You cannot define conditional dependencies containing both status and output conditions. - AWSJCO164E
An internal error has occurred. Conditional dependencies with output conditions are not allowed when the predecessor is a job stream. - AWSJCO165E
You cannot execute a centralized agent update because the workstation "workstation_name" is at version "workstation_version". The minimum supported workstation version for centralized agent update is "minimum_version". - AWSJCO166E
You cannot execute a centralized agent update because the workstation "workstation_name" has a wrong type. Only Fault Tolerant Agents and Dynamic Agents are supported for centralized agent update. - AWSJCO167E
You cannot execute a centralized agent update because the workstation "workstation_name" is not running and linked. - AWSJCO168E
The definition of the job stream internetwork dependency "dependency" is invalid. - AWSJCO169E
You cannot import or replace the object "wat_name" because the referenced objects already exist in this environment and are identical. - AWSJCO170E
The value specified for the recovery rerun interval option "recovery_value" for job definition "job_name" is not allowed. This value can be specified only if recovery rerun option is specified. - AWSJCO171E
The value specified for the recovery rerun occurrence option "recovery_value" for job definition "job_name" is not allowed. This value can be specified only if the recovery rerun option is specified. - AWSJCO172E
The value specified for the recovery rerun same workstation option "recovery_value" for job definition "job_name" is not allowed. This option is valid only if the recovery rerun option is specified. - AWSJCO173E
The value specified for the recovery rerun occurrences option "recovery_value" for job definition "job_name" is not allowed. This option is valid only if the recovery rerun interval value is specified. - AWSJCO174E
The value specified for the rerun on same workstation option "recovery_value" for job definition "job_name" is not allowed. This option is valid only if the type of workstation where the job runs is a pool or a dynamic pool. - AWSJCO175E
The value specified for the abend prompt option "abend_prompt" for job definition "job_name" is not allowed. This option is valid only if the recovery rerun interval and occurrences options are not specified. - AWSJCO176E
The repeatevery and for options are not supported for the recovery rerun feature on job "job_key" because workstation "workstation_name" is at version "workstation_version". The minimum supported workstation version for supporting the repeatevery and for options for the recovery rerun feature is "minimum_version". - AWSJCO177E
The maximum number of jobs that can be retrieved from the job successors query is "max_jobs". You have reached the maximum number of retrieved jobs: increase the maximum supported number and try again. - AWSJCO178E
Cannot complete the requested action on job successors. The status of successor job "job_name" is not supported by the rerun feature. The status of the job is "job_status". - AWSJCO179E
The job internal successors query cannot be completed. One of the successor jobs "job_name" has an external dependency. Try again later, after removing any external dependencies. - AWSJCO180E
The Job Successors Rerun action cannot be completed. The successor jobs of the job "job_id" are changed after the last Job Successors Preview was performed. Wait for the job successors completion, reload the successor jobs before perform again the Job Successors Rerun action. - AWSJCO181E
The job successor list is empty. There are no jobs which match the Job Successors query. - AWSJCO182E
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. - AWSJCO183E
Cannot complete the requested action on job successors. The status of job stream "job_stream_name" containing one or more successor jobs is not supported by the rerun feature. The status of the job stream is "job_stream_status". - AWSJCO184E
Cannot complete the requested action on job successors. The definition of successor job "job_name" is not compatible with the rerun successors feature. The job definition specifies that the job is to be launched repeatedly at the specified interval. - AWSJCO185E
Cannot complete the requested action on job successors. The definition of successor job "job_name" is not compatible with the rerun successors feature. The job definition specifies that the job is a recovery job. - AWSJCO186E
You cannot define a file start condition on the job stream "jobstream_key" because the workstation where the files to be monitored are located "workstation_name" is at version "workstation_version". The minimum required workstation version for defining start conditions is "minimum_version". - AWSJCO187E
You cannot use job "job_key" as start condition in the job stream "jobstream_key" because the workstation "workstation_name" is at version "workstation_version". The minimum required workstation version for defining start conditions is "minimum_version". - AWSJCO188E
You cannot define a file start condition in the job stream "jobstream_key" because the workstation where the start condition is defined "workstation_name" is of type "workstation_type". Supported workstation types for file start conditions are "allowed_types". - AWSJCO189E
You cannot define a start condition for a workstation class if the job stream to which the start condition belongs runs on a workstation. Job stream "job_stream" runs on workstation "job_stream_workstation", but a workstation class ("workstation_class") has been defined as start condition of that job stream. - AWSJCO191E
No name is specified for file start condition in job stream "jobstream_key" and the default value "startcond_name" is used. User "user" is not authorized to perform the action "action" on an object "object_type" and key "object". - AWSJCO192E
The license type cannot be defined on a workstation "workstation" of type broker, pool, dynamic pool, remote engine, or extended agent. - AWSJCO193E
The parent folder identifier "parent_folder_id" referenced by folder "folder" does not exist. - AWSJCO194E
The value specified for the parent folder "parent_folder_name" is not supported. A folder and its parent cannot have the same name. - AWSJCO195E
The parent folder identifier "parent_folder_id" referenced by folder "folder" is not valid. - AWSJCO201E
The logon is empty. - AWSJCO203E
The objects you are attempting to replace cannot be replaced because one or more of them are referenced from a workload application in this environment. - AWSJCS - Common services messages
This section lists error and warning messages that might be generated by the routines that handle common services. - AWSJCS001E
The message catalog "catalog_file" does not exist. - AWSJCS002E
A format error has been found in the message catalog "catalog_file". - AWSJCS003E
An internal error has occurred. The message "message_ID" was not found in the message catalog "catalog_file". - AWSJCS004E
An internal error has occurred. The configuration file "configuration_file" does not exist. - AWSJCS005E
An internal error has occurred. The configuration file "configuration_file" cannot be read. - AWSJCS006E
An internal error has occurred. The required property "property" cannot be found in the configuration file: "configuration_file". - AWSJCS007W
An internal error has occurred. The value of the required property "property" in the configuration file: "configuration_file" is not numeric, as expected. The default value stored in the program code is used. - AWSJCS008E
An internal error has occurred. The value of the required property "property" in the configuration file "configuration_file" is outside the permitted range. - AWSJCS009E
An internal error has occurred. The default value (stored in the program code) of the required property "property" in the configuration file "configuration_file" must be one of the following values: "permitted_values". - AWSJCS010E
An internal error has occurred. The value of the required property "property" in the configuration file "configuration_file" must be one of the following values: "permitted_values". - AWSJCS011E
An internal error has occurred. The error is the following: "exception_message". - AWSJCS012E
The value of the property "property" is not correct. It must be between "minimum_value" and "maximum_value". - AWSJCS013E
The value of the property "property" is not correct. It must be no more than the following length: "maximum_length". - AWSJCS014E
The value of the property "property" is not correct. It must be not less than the following length: "minimum_length". - AWSJCS015E
The value of the property "property" is not in the correct format. - AWSJCS016E
The value of the property "property" is not correct. It must be one of the following values: "permitted_values". - AWSJCS017E
The value of the property "property"is not correct. It must contain one or more of the following: "permitted_values". Multiple values must be separated by the separator: "separator". - AWSJCS018E
The value of the property "property" must be in the HHMM format, where the hour must be in the range "min_HH"to "max_HH" and the minutes must be in the range "min_MM" to "max_MM". - AWSJCS019E
An internal error has occurred in Java class "class". - AWSJCS020E
An internal error has occurred. The required property "property" cannot be found. - AWSJCS021E
The application job plug-in with ID "plugin_id" cannot be found. - AWSJCS022E
The JobExecutor class for application job plug-in with ID "plug-in_ID" cannot be found. - AWSJCS023E
Unable to create the JSDL for application job plug-in with ID "plug-in_ID" because of the following error: "exception". - AWSJCS024E
Unable to extract parameters from JSDL for application job plug-in with ID "plugin_ID"because of the following error: "exception". - AWSJCS025E
The JSDL validation for application job plug-in with ID "plugin_ID" returns the following error: "exception". - AWSJCS026E
An internal error has occurred. One or more parameters provided by the Dynamic Workload Console to the application job plug-in with ID "plugin_ID" are incorrect. - AWSJCS027E
The command cannot be run on the workstation with name "workstation_name" because it is of type "workstation_type". The supported workstation types are: "supported_workstation_type". - AWSJCS028E
The command cannot be run on the workstation with name "workstation_name" because the operating system installed on it is of type "os_type". The supported operating systems are "supported_os". - AWSJCS029E
The XML definition is incorrect. The following XML error was returned: "xml_error". - AWSJCS030E
You specified an incorrect value for the "property" property. The value must be alphanumeric. - AWSJCS031E
The operation cannot be performed because the job was not submitted to the agent yet. - AWSJCS032E
You specified an incorrect value for the "property" property. The value must start with an alphabetic character. Valid characters are "valid_characters". - AWSJCS033E
The value of the property "property" cannot be equal to 0000. - AWSJCS034E
The value of the property "property" is not in the correct format: workstation#jobname - AWSJCS035E
The value of the string "string" in property "property" is not correct. The maximum supported length is: "maximum_length". - AWSJCS036E
The value of the string "string" in property "property " is not correct. The minimum supported length is: "minimum_length". - AWSJCS037E
The value of the string "string" in property "property " is not correct. The value must be alphanumeric. - AWSJCS038E
The value of the string "string" in property "property " is not correct. The value must start with an alphabetic character. Valid characters are "valid_characters". - AWSJDB - Common objects messages
This section lists error and warning messages that might be generated by the routines that handle common objects. - AWSJDB101E
The object "object" was not found. - AWSJDB102E
The global option "property" was not found. - AWSJDB201E
The object "object" cannot be locked, updated, or deleted because it is locked by user "user_name". - AWSJDB202E
The object "object" cannot be unlocked or updated because it is not locked. - AWSJDB203E
The object "object" cannot be unlocked or updated because it was not originally locked by you ("user1_name"), and is currently locked by user "user2_name". - AWSJDB204E
The object "object" cannot be unlocked or updated because it is locked by you ("user_name"), but in another session. - AWSJDB205E
While trying to lock multiple objects (for example, as the result of the use of a wildcard in the selection criteria), at least one of the objects could not be locked, because it was already locked. - AWSJDB206E
While trying to unlock multiple objects (for example, as the result of the use of a wildcard in the selection criteria), at least one of the objects could not be unlocked because it was not originally locked by you ("user_name"). - AWSJDB207E
While trying to unlock multiple objects (for example, as the result of the use of a wildcard in the selection criteria), at least one of the objects could not be unlocked because it was locked by you ("user_name"), but in another session. - AWSJDB301E
Unused message. - AWSJDB302E
The job "job_key" referenced by object "object_key" does not exist. - AWSJDB303E
The job definition "job_definition_key" referenced by object "object_key" does not exist. - AWSJDB304E
The job stream "job_stream_key" referenced by object "object_key" does not exist. - AWSJDB305E
The workstation "workstation_key" referenced by object "object_key" does not exist. - AWSJDB306E
The workstation class "workstation_class_key" referenced by object "object_key" does not exist. - AWSJDB307E
The workstation or workstation class "workstation_or_workstation_class_key" referenced by object "object_key" does not exist. - AWSJDB308E
The calendar "calendar_key" referenced by object "object_key" does not exist. - AWSJDB309E
The domain "domain_key" referenced by object "object_key" does not exist. - AWSJDB310E
The resource "resource_key" referenced by object "object_key" does not exist. - AWSJDB311E
The prompt "prompt_key" referenced by object "object_key" does not exist. - AWSJDB312E
A master domain manager cannot be created, it must be installed as such. - AWSJDB313E
A master domain cannot be modified to become a lower level domain. - AWSJDB314E
A lower level domain cannot be modified to become the master domain. - AWSJDB315E
The master domain cannot be deleted. - AWSJDB316E
The supplied job stream definition contains a duplicate run cycle name: "run_cycle_name". - AWSJDB317E
The supplied job stream definition contains a duplicate job name: "job_name". - AWSJDB318E
A prompt with name "prompt_name" already exists. - AWSJDB319E
A resource with name "resource_name" defined for workstation or workstation class "workstation_or_workstation_class" already exists. - AWSJDB320E
The supplied variable table definition contains a duplicate variable name: "variable_name". - AWSJDB321E
The object "variable_key" already exists. - AWSJDB322E
The variable table "variable_table_key" referenced by object "object_key" does not exist. - AWSJDB323E
The default variable table cannot be found or it is being updated by another user, and cannot be modified to become an ordinary variable table. - AWSJDB324E
The default variable table cannot be deleted. - AWSJDB325E
The default variable table cannot be modified to become an ordinary variable table. - AWSJDB326E
The availability calendar "calendar_key" referenced by object "object_key" does not exist. - AWSJDB327E
The run cycle group "run_cycle_group_key" referenced by object "object_key" does not exist. - AWSJDB328E
The folder "folder_key" referenced by object "object_key" does not exist. - AWSJDB329E
The parent folder "parent_key" referenced by object "object_key" does not match the parent identifier "identifier". - AWSJDB330E
The new folder "new_folder_key" already exist. The folder "folder_key" cannot be renamed. - AWSJDB331E
The root folder "folder_key" cannot be renamed. - AWSJDB401E
Unused message. - AWSJDB402E
An internal error occurred while reading or writing a UUID in the database, or while generating a UUID for a new object. - AWSJDB403E
An internal error has occurred. The operation "operation_name" cannot be performed because the DAO context state "context_state" is not correct. - AWSJDB404E
An internal error has occurred while parsing the Identifier. The internal error message is: "error_message". - AWSJDB501E
Unused message. - AWSJDB601E
An internal error has occurred. A database integrity constraint has been violated. The internal error message is: "error_message". - AWSJDB602E
An internal error has occurred. A database not null constraint has been violated. The internal error message is: "error_message". - AWSJDB603E
An internal error has occurred. A database check constraint has been violated. The internal error message is: "error_message". - AWSJDB604E
An internal error has occurred. A database unique constraint has been violated. The internal error message is: "error_message". - AWSJDB605E
An internal error has occurred. A database foreign key constraint has been violated. The internal error message is: "error_message". - AWSJDB606E
An internal error has occurred. A foreign key constraint prevents the remove operation. The internal error message is: "error_message". - AWSJDB607E
An internal error has occurred. The value defined for a database field exceeds its column bounds. The internal error message is: "error_message". - AWSJDB801E
An internal error has been found while accessing the database. The internal error message is: "error_message". - AWSJDB802E
An internal error has occurred while connecting to the database. The database connection is not available. - AWSJDB803E
An internal deadlock or timeout error has occurred while processing a database transaction. The internal error message is: "error_message". - AWSJDB804E
The operation cannot be completed because a concurrent update has been detected that would lead to a database inconsistency. - AWSJDB805E
The requested operation cannot be performed because the database is locked by the planner process. - AWSJDB806W
The collection of database statistics on the pre-production plan tables has failed. The production plan will be generated using the current database statistics. - AWSJDB807E
An internal error occurred while checking that all the global options and internal global settings are stored in the database. The internal error message is: "error_message". - AWSJDB808E
An internal error has occurred while connecting to the database. The database server may be down or unreachable. - AWSJDB809E
An internal error has occurred while connecting to the database. The requested database was not found. - AWSJDB810E
An internal error has occurred while connecting to the database. The requested table was not found or cannot be accessed. - AWSJDB811E
An internal error has occurred while connecting to the database. The supplied user name and password are not valid. - AWSJDB812E
Multiple threads are trying to access the database using the same transaction. The names of the threads are: "thread_name_list". - AWSJDB813E
Multiple threads are trying to access the database using the same DAO module. The names of the threads are: "thread_name_list". - AWSJDB814E
The input file "file_path" cannot be found or accessed for reading. - AWSJDB815E
The output file "file_path" cannot be created or accessed for writing. - AWSJDB816E
A property with name "property_name" and object identifier "object_id" already exists. - AWSJDB817E
The object "object" cannot be accessed. - AWSJDB818E
An internal error has occurred while connecting to the database. The internal error message is: "error_message". - AWSJDB819E
An internal error has occurred while connecting to the database. The resource allocation ends with error. - AWSJDB820E
The security domain "domain_key" referenced by access control list does not exist. - AWSJDB821E
One or more output conditions "outputconditions" cannot be deleted or modified because they are referenced by one or more jobs or job streams "references". - AWSJIS - Installation messages
This section lists error and warning messages that could be issued. - AWSJIS002E
An internal error has occurred. The command or script "command_or_script" has failed. The exit code is as follows: "exit_code".If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.. - AWSJIS004E
The version of the Tivoli Workload Scheduler instance selected to upgrade is neither 8.1 nor 8.2.Click Back and select a different, valid instance. - AWSJIS005E
The version of the Tivoli Workload Schedulerinstance selected is not 8.2.Click Back and select a different, valid instance. - AWSJIS006E
No valid instance of Tivoli Workload Scheduler has been found to upgrade.Select a valid instance or make a fresh installation. - AWSJIS007E
An error occurred reading file. - AWSJIS008E
The passwords do not match.Retype the password and the verification password, ensuring that they are both the same. - AWSJIS009E
The following field: "field_name" is longer than the maximum of "max_length" bytes. - AWSJIS010E
The following field: "field_name" is either not a number or outside the following range: "from_value" - "to_value". - AWSJIS011E
The supplied installation path is not valid. - AWSJIS012E
There is insufficient disk space available in the directory "directory" to complete the installation. The installation requires "required_space" megabytes, but only "available_space" megabytes are available. Either make more space available or change the installation directory. - AWSJIS013E
The specified installation path doesn't exist. - AWSJIS017E
You are correcting an installation parameter by editing the parameters of an installation step, but an incorrect parameter has been supplied during the correction. - AWSJIS018E
An internal error has occurred. The directory specified as the location of the existing Tivoli Workload Scheduler instance does not exist. - AWSJIS019E
An internal error has occurred. The directory to be used for the install directory of the embedded WebSphere Application Server does not exist. - AWSJIS020E
The directory specified as the location of the existing DB2 instance does not exist. Specify the correct location of the DB2 instance. - AWSJIS021E
An internal error has occurred. The application server profile "profile" for the embedded WebSphere Application Server could not be created. - AWSJIS022E
An internal error has occurred. The application server profile archive "profile_archive" for the embedded WebSphere Application Server could not be read. - AWSJIS023E
An internal error has occurred. The update of the configuration of the embedded WebSphere Application Server has failed. - AWSJIS024E
The application server "application_server" could not be started. - AWSJIS025E
An internal error has occurred. The script "script" used by the installation wizard has failed. - AWSJIS029E
An internal error has occurred. The directory where the installation expected to find the JRE files does not exist. - AWSJIS030E
An internal error has occurred. The build file that the installation program expected to find does not exist. - AWSJIS031E
An internal error has occurred. An internal program has failed. - AWSJIS032E
An internal error has occurred. An internal program has not been supplied with a required parameter. - AWSJIS036W
The temporary directory created previously by the Tivoli Workload Scheduler installation does not exist. - AWSJIS037W
Message not used. - AWSJIS038E
An internal error has occurred. An unspecified internal error has occurred during the installation process. - AWSJIS039E
Tivoli Workload Scheduler cannot be started.Start it manually. - AWSJIS041E
The installation cannot add the following key to the Windows registry: "registry_key". - AWSJIS042E
The installation cannot add the following key to the Windows registry: "registry_key" with values "registry_key_values". - AWSJIS043E
The installation cannot delete the following key from the Windows registry: "registry_key". - AWSJIS044E
The installation cannot install the following Windows service: "service_name". - AWSJIS045E
The installation cannot delete the following Windows service: "service_name". - AWSJIS046E
The installation could not find an operating system dll to complete the user verification tasks. - AWSJIS047E
The installation encountered an error running the Tivoli Workload Scheduler Windows configuration script. - AWSJIS048E
The installation cannot read the following file: "file_name". - AWSJIS049E
The installation cannot write the following file: "file_name". - AWSJIS050E
The installation cannot move the following file: "file_name". - AWSJIS052E
Composer could not update the database. - AWSJIS053E
The installation could not create the Security file. - AWSJIS054E
The installation could not run the final installation commit phase. - AWSJIS056E
The directory that contains the embedded WebSphere Application Server installation files cannot be found. - AWSJIS057E
The tar file that contains the embedded WebSphere Application Server installation files cannot be found. - AWSJIS058E
The script db2profile used to create the DB2 environment cannot be found in the DB2 installation directory. - AWSJIS059E
The fully qualified domain name of this computer is null. The installation requires the fully qualified domain name to configure Tivoli Workload Scheduler correctly. - AWSJIS060E
The supplied TWS_user could not be created. - AWSJIS061W
The supplied TWS_user exists on the local computer but does not have the correct rights. The installation is attempting to modify the rights. - AWSJIS063E
The supplied password is incorrect for the supplied TWS_user. - AWSJIS064E
The supplied TWS_user account cannot be verified automatically. This is because the user running the installation program does not have the Act as part of the operating system privilege, or the password of the user has expired. - AWSJIS065E
The user running the installation does not have the correct privileges to verify the privileges of the supplied TWS_user. - AWSJIS066E
The installation was unable to check the existence of the supplied TWS_user. - AWSJIS067E
The installation could not modify the privileges of the supplied TWS_user. - AWSJIS068E
The installation could not add the supplied TWS_user to the Administrators group. - AWSJIS069E
The installation could not find an operating system dll to complete the TWS_user verification tasks. - AWSJIS070E
The supplied TWS_user could not be created. - AWSJIS071E
The supplied TWS_user name incorrectly contains a period. - AWSJIS072E
The supplied TWS_user ID is longer than the maximum length of "maximum_length" bytes. - AWSJIS073E
The supplied TWS_user "TWS_user_ID" does not exist on the local computer, but the installation cannot create this user, because another object exists with the supplied name. - AWSJIS074E
The supplied TWS_user ID incorrectly contains a period. - AWSJIS075E
The supplied TWS_user does not exist. On UNIX platforms the user chosen for the TWS_user must exist with the correct permissions before starting the installation program. - AWSJIS076E
The supplied port: "port_number" is already in use. - AWSJIS077E
The user running the installation is not in the Administrator group, or does not have Administrator rights. - AWSJIS078E
The user running the installation is not root. - AWSJIS079E
The supplied ports are not unique. Specify a different value for each port. - AWSJIS080E
The directory "directory" cannot be created. - AWSJIS081E
The directory "directory" does not have write permission. - AWSJIS082E
The following fields "field1" and "field2" cannot contain the same value. - AWSJIS083E
The directory "directory" is not a valid directory. - AWSJIS084E
The command line client for Tivoli Workload Scheduler, version 8.6 is already installed in the specified installation location. - AWSJIS085E
The connection to the database has failed. Check that the DB2 server is running and that the user and password are correct. - AWSJIS086W
The credentials for using the Tivoli Workload Scheduler command line client are already present on this computer (in the useropts file), but they are overwritten by this installation. - AWSJIS088E
An error occurred while stopping the embedded WebSphere Application Server. - AWSJIS090E
An error occurred while uninstalling the Tivoli Workload Scheduler instance. - AWSJIS091E
The uninstall wizard could not find any instances of Tivoli Workload Scheduler on this computer to uninstall. - AWSJIS092E
An error has occurred while uninstalling the Tivoli Workload Scheduler command line client. - AWSJIS098E
An internal error has occurred. A program has failed unexpectedly. - AWSJIS099E
The DB2 response file does not exist: - AWSJIS100E
You have supplied a path to identify the supported DB2 installation: "DB2_path" but either no installation exists at that location, or the installation that exists is not a supported version. Supported versions are 9.5 and 9.7. Versions 8.2 (8.1 with Fix Pack 7) and 9.1 are supported during the installation, but you are advised to migrate it to a supported version after completing the installation. For the HP-UX operating system the supported version is 9.1. Version 8.2 is supported during the installation, but you are advised to migrate it to a supported version after completing the installation. See the System Requirements document in the Information Center for a detailed explanation of the supported versions. Check the help for this message (in the Messages manual) to determine the correct path to supply. - AWSJIS101E
The supplied existing DB2 installation cannot be used because the version is lower than the minimum supported version: 9.5. Versions 8.2 (8.1 with Fix Pack 7) and 9.1 are supported during the installation, but you are advised to migrate it to a supported version after completing the installation. For the HP-UX operating system the supported version is 9.1. Version 8.2 is supported during the installation, but you are advised to migrate it to a supported version after completing the installation. see the System Requirements document in the Information Center for a detailed explanation of the supported versions). Check the help for this message (in the Messages manual) to determine the correct path to supply. - AWSJIS102E
The port specified for the DB2 instance is not in use. - AWSJIS103E
The installation could not create the backup directory with the supplied name: "backup_directory" - AWSJIS104E
The installation could not read the file "backup_program_files_list_file" containing a list of the files that need to be backed up. - AWSJIS105E
The installation could not read the file "backup_config_files_list_file" containing the names of the configuration files that need to be backed up. - AWSJIS106E
The path "backup_directory" supplied for the backup directory is too long. - AWSJIS107E
The installation cannot rename the file "file". - AWSJIS109E
You are trying to install Tivoli Workload Scheduler on a workstation where one or more agent processes are still running.You must stop all Tivoli Workload Scheduler processes before installing another instance or upgrading an existing instance. - AWSJIS110E
The installation cannot read the file "installation_program_files_list_file" that contains the names of the installation programs. - AWSJIS111E
The installation was unable to access one or more Windows processes. - AWSJIS112E
The installation cannot start the process "process_name". - AWSJIS113E
Either the userdata or the userdata.KEY file, required for the migration of the user information, was not found in the Tivoli Workload Scheduler instance to be upgraded. - AWSJIS114E
There is insufficient disk space available in the directory "directory" to perform the installation of the DB2 component.The installation requires "required_space" megabytes, but only "available_space" megabytes are available. Either make more space available or change the installation directory. - AWSJIS115E
There is insufficient disk space available in the directory "directory" to complete the installation of the DB2 programs.The installation requires "required_space" megabytes, but only "available_space" megabytes are available. Either make more space available or change the installation directory. - AWSJIS116E
There is insufficient disk space available in the directory "directory" to complete the installation of the Tivoli Workload Scheduler database.The installation requires "required_space" megabytes, but only "available_space" megabytes are available. Either make more space available or change the installation directory. - AWSJIS117E
The supplied port: "port_number" is registered for use by another application in the Services file. - AWSJIS119W
The specified user is a domain user. Check that it has the required rights. See Planning and Installation for details. - AWSJIS120E
The TWS_user ID of the previous instance of Tivoli Workload Scheduler is longer than the maximum of "max_length" bytes. You cannot upgrade this instance of Tivoli Workload Scheduler. - AWSJIS122W
The user specified for the DB2 installation "user" already exists.You must be absolutely certain that this user was created by a previous installation of DB2 to go ahead. If in any doubt, either go back and choose another user, or delete the user before continuing with the installation, and let the wizard create it for you. - AWSJIS123E
Unable to find the selected instance to uninstall in the Tivoli Workload Scheduler registry file. You cannot uninstall this instance using the wizard. - AWSJIS124E
Unable to find the selected instance of the command line client to uninstall in the Tivoli Workload Scheduler registry file. You cannot uninstall this instance using the wizard. - AWSJIS125E
There is insufficient disk space available in the temporary directory "directory" to complete the installation. The installation requires "required_space" megabytes, but only "available_space" megabytes are available. Make more space available in the temporary installation directory. - AWSJIS126E
The user ID "user_ID" must not begin with sys, ibm, or sql, as these are reserved terms. - AWSJIS127E
The user ID"user_ID" must not be: admins, guests, local, public, or users, nor any SQL key word, as these are reserved terms. - AWSJIS128E
You specified a TWS_user that already owns an existing Tivoli Workload Scheduler instance.Click Back and specify a different user for the TWS_user. - AWSJIS129E
The field "field_name" is required. - AWSJIS130E
The field "field_name" must contain a valid value. - AWSJIS131E
The character "character" is not valid. - AWSJIS132E
The field "field_name" must not contain blank characters. - AWSJIS133E
There is not enough space in the directory "directory_name". The required space is "required_space" MB. The available space is "available_space" MB. - AWSJIS134E
No feature has been selected. Click Back and select a feature to install. - AWSJIS135E
Unable to establish a connection to host "host_name" on port "port". Check that the DB2 server is up and running and that it is listening on this port. - AWSJIS136E
The supplied password for the user "user" that the wizard must create does not match the security policy of the computer on which you are performing the installation. - AWSJIS137E
The supplied password for the DB2 Administrator "DB2_administrator" is incorrect. - AWSJIS138E
The specified instance name "instance_name" does not exist on the DB2 server. - AWSJIS139E
No Oracle Database installation exists at the location "oracle_path". The Oracle path must be a search path that includes the Oracle home directory. - AWSJIS140E
The Oracle Database installation that you identified is not a supported version. Supported versions are: Oracle Database 10g Release 2 - Enterprise Edition (10.2.0.x) or later, and Oracle Database 11g Release 2 - Enterprise Edition (11.2.0.0) or later. Version 9 Release 2 is supported during the installation, but you are advised to migrate it to a supported version after completing the installation (see the System Requirements document in the Information Center for a detailed explanation of the supported versions). - AWSJIS141E
The value supplied for the input text field "input_field" is not valid.Ensure that the value entered complies with Oracle naming rules. - AWSJIS142E
The listener on the Oracle Database server is not responding to the connection test. This might be caused by:an incorrect value specified for the net service name, or the unavailability of the Oracle server listener. - AWSJIS143E
The version of the indicated Oracle Database server is not supported. Supported versions are: Oracle Database 10g Release 2 - Enterprise Edition (10.2.0.x) or later, and Oracle Database 11g Release 2 - Enterprise Edition (11.2.0.0) or later. Version 9 Release 2 is supported during the installation, but you are advised to migrate it to a supported version after completing the installation (see the System Requirements document in the Information Center for a detailed explanation of the supported versions). - AWSJIS144E
The specified table space "tablespace_name" does not exist. - AWSJIS145E
The supplied credentials for user "user_ID" are not correct. - AWSJIS146E
The DB2 Administrator user name "user_name" can not start with an underscore character _. - AWSJIS147E
The DB2 Administrator user name "user_name" can not start with a number. - AWSJIS148E
No instances of Tivoli Workload Scheduler version 8.6 was found to upgrade to Fix Pack 02. - AWSJIS149E
One or more errors have occurred during the migration. Check the troubleshooting information in the directory: "directory". - AWSJIS150E
The specified user does not exist. - AWSJIS151E
The specified password for the user is wrong. - AWSJIS152E
The supplied database schema "schema_name" must already exist when installing a backup master domain manager. - AWSJIS153E
The input fields "field_name1" and "field_name2" must have the same value. - AWSJIS154E
The connection to the DB2 database failed. Verify that the following fields are correct: "database_name", "db2_admin_user", "db2_admin_password". If you are using a DB2 Administration Client, verify also that the "db2_client_user" is correct. - AWSJIS155E
An error occurred unzipping the archive in the specified directory. Verify that you have the required permissions in the destination directory. - AWSJIS157E
An internal error has occurred. The application server profile "profile" for the embedded WebSphere Application Server could not be upgraded. - AWSJIS158E
No additional feature is available for the selected instance. Click Back and select another instance. - AWSJIS159E
The port "port_num" has been already specified for the "port_name". Specify a different value. - AWSJIS160E
The supplied Oracle Database installation does not have the Partitioning Feature enabled. Install and enable this feature on the selected Oracle installation and then continue or rerun the Tivoli Workload Scheduler installation. - AWSJIS161E
The field "field" with value "value" contains national characters.National characters are not supported for this field. - AWSJIS162E
The supplied password contains an unsupported character.The supported characters are as follows: "characters" - AWSJIS164E
The supplied installation path is already being used by another instance ofTivoli Workload Automation or the Tivoli Workload Scheduler command-line client. Choose another path. - AWSJIS165E
No valid instance of Tivoli Workload Automation has been specified.Specify a valid instance or install the component in a new instance. - AWSJIS166E
No valid action can be performed on the Tivoli Workload Automation instance that has been selected.Select another valid instance in which to install the product or component, or create a new instance. - AWSJIS167E
The embedded WebSphere Application Server user was not retrieved. Insert it manually. - AWSJIS168E
You cannot upgrade Tivoli Workload Scheduler when it is installed in the root directory. - AWSJIS169E
No instances of type "type" can be found. Close the Wizard and restart the installation. - AWSJIS170E
No instance of a Tivoli Workload Scheduler component has been found that can be upgraded. The wizard closes when you close the message pop-up. - AWSJIS171W
You specified a Tivoli Workload Scheduler user name different from the embedded WebSphere Application Server administrator user name.To allow successful connections to the integrated engine,modify the Tivoli Workload Scheduler Security file addingthe embedded WebSphere Application Server administrator user name. - AWSJIS172E
The Tivoli Workload Scheduler Oracle database administrator user password must start with an alphabetic character. - AWSJIS173E
One or more prerequisite library is missing, as follows: "list_of_missing_libraries". Obtain and install the library, and then rerun the installation. - AWSJIS174W
If you have a job stream called FINAL in the database, it has been backed up to the file Sfinal.extract and then overwritten. If your old final job stream was customized, or is not called FINAL , you must perform some customization steps. See the message help in the Messages manual, or the Planning and Installation Guide, for details. - AWSJIS175W
The table space path "path" already exists and is not empty.Check if the selected path contains table space data of a Tivoli Workload Scheduler database.If yes, continue, otherwise choose another table space path. - AWSJIS176E
The selected table space paths are either equal or one is a subpath of the other:"path1""path2". The paths must be different and one cannot contain the other. - AWSJIS177E
Authentication failure. The supplied user name or password is incorrect. - AWSJIS178E
It is not possible to check the specified credentials. embedded WebSphere Application Server stops. - AWSJIS179W
Unable to establish a connection with the host "host_name" on the "port" port. Verify that the Dynamic Workload Broker is up and running and that it is listening on this port.Click Yes to continue. - AWSJIS180W
You are activating the dynamic scheduling capability on this master domain manager.This feature requires that all backup master domain managers in the network are at the minimum supported level.See the Planning and Installation Guide for details.Do you want to continue? - AWSJIS181W
Upgrading this instance changes its installation path.Be sure that all file dependencies and jobs running on this instance either do not use the installation path or use it as a variable.Do you want to continue? - AWSJIS185E
There are jobs still running. The operation cannot proceed. - AWSJIS186E
The following processes are still running. Close them before running the operation again. - AWSJIS187E
The following processes are still running. Either close them or wait for their completion before running the operation again. - AWSJIS189E
Tivoli Workload Scheduler could not retrieve the job fence value on the workstation for the selected instance. - AWSJIS190E
Tivoli Workload Scheduler could not reset the job fence value on the workstation for the selected instance. - AWSJIS192E
An incorrect value has been supplied for the parameter: checkJobsLoop.wait. Valid values are integers or -1 to have the product wait indefinitely. - AWSJIS193E
You cannot install the Tivoli Workload Scheduler "component" component using this eImage. - AWSJIS194E
You cannot install the runtime for Java jobs using the current eImage. - AWSJIS195E
You cannot upgrade the selected Tivoli Workload Automation instance; the Java extensions eImage is required.Copy the required eImage into the current eImage directory and proceed. - AWSJIS196E
No valid action can be performed on the selected Tivoli Workload Automation instance from the current eImage.Select a valid instance in which to install the product or component or use a different eImage. - AWSJIS197E
You cannot install the dynamic agent only on a Tivoli Workload Automation instance. - AWSJIS198W
A problem was found during the check of prerequisites. Are you sure you want to continue with the installation process? - AWSJIS199E
An error occurred running the option that recreates the Tivoli Workload Scheduler installation registries on the specific path "twa_path". Check the installation log for details. - AWSJIS202W
Unable to establish a connection with the host "host_name" on the "port" port. Verify that the master domain manager is up and running and that it is listening on this port.Click Yes to continue. - AWSJIS203W
The upgrade process cannot upgrade the embedded WebSphere Application Server security to Federated Repository. If you do not enable the embedded WebSphere Application Server Federated Repository security mechanism on the Tivoli Workload Automation instance, you cannot install a Tivoli Dynamic Workload Console on the same Tivoli Workload Automation instance. See the message help in the Messages manual, or the Administration Guide, for details. - AWSJIS204E
The eImage on your workstation is corrupt. You must use the UNZIP command to extract the eImage otherwise your fix pack installation fails. - AWSJMR - Job management for REST services messages
This section lists error and warning messages that might be generated by the routines that handle job management for REST services. - AWSJMR001E
The following fault message was received from the agent as a result of a scheduling request: "fault_message". - AWSJMR002E
The requested service has ended with a fault. The internal error message is: "error_message". - AWSJMR003E
A transport problem was found while running a REST service. The internal error message is: "error_message". - AWSJMR004E
There was an error retrieving the job id from the alias. The internal error message is: "error_message". - AWSJMR005E
There was an error retrieving the job id from the alias because of problems accessing the database. The internal error message is: "error_message". - AWSJMR006E
The notification address list is empty. - AWSJMR007E
An error occurred while getting the requirement description of the dynamic pool with id "pool_id". The error message is: "error_message" - AWSJMR008E
An unexpected error occurred while getting the requirement description of the dynamic pool with id "pool_id". The error message is: "error_message" - AWSJMR009E
An error occurred while getting the computer systems belonging to the dynamic pool with id "pool_id". The error message is: "error_message" - AWSJMR010E
An unexpected error occurred while getting the computer systems belonging to the dynamic pool with id "pool_id". The error message is: "error_message" - AWSJMR011E
You are not authorized to perform the requested operation. - AWSJMR012E
The user "username" is not registered on the gateway. - AWSJMR013E
Basic authentication is required to access this servlet. - AWSJMR014E
The gateway ID "gwID" does not start with the prefix "prefix". - AWSJMR015E
The display name "displayName" does not start with a valid prefix for the user "username". - AWSJMR016E
The gateway ID "gateway id" does not start with a valid prefix for the user "username". - AWSJMR017W
The plugin "plugin" has version "plugin version" that is newer than "plugin version". - AWSJMR018W
The plugin "plugin" cannot be updated because the new version requires the agent version "required agent version" while the current version is "agent version". - AWSJMR019E
The plugin "plugin" was not found on the server. The error is "error" - AWSJMR020E
The plugin "plugin" was not found on the server. The error is "error" - AWSJOM - Object management messages
This section lists error and warning messages that might be generated by the routines that handle object management. - AWSJOM001E
A null value was specified for field "field_name". Only not-null values are allowed. - AWSJOM002E
Null values were specified for field "field_name_1" and field "field_name_2". At least one of these values must be not-null. - AWSJOM003E
Null values were specified for the following fields: "field_name_1", "field_name_2" and "field_name_3". At least one of these values must be not null. - AWSJOM004E
Null values were specified for the following fields: "field_name_1", "field_name_2", "field_name_3" and "field_name_4". At least one of these values must be not null. - AWSJOM011E
The value "field_value" specified for field "field_name" is outside the allowed range. Values must be between "range_start" and "range_end". - AWSJOM012E
The value "field_value" specified for field "field_name" exceeds the maximum length, which is "max_length". - AWSJOM013E
The value "field_value" specified for field "field_name" contains the following character "non-valid_char", which is not allowed. - AWSJOM014E
The value "field_value" specified for field "field_name" does not start as expected. Values cannot start with the following character: "non-valid_start". - AWSJOM015E
The value "field_value" specified for field "field_name" is not allowed or reserved for future use. - AWSJOM016E
The value "field_value" specified for field "field_name" does not contain a valid internet address. - AWSJOM017E
The value "field_value_too_low" specified for field "field_name_too_low" cannot be lower than the value "reference_field_value" specified for field "reference_field_name". - AWSJOM018E
The object specified for field "field_name" is an instance of the object class "wrong_class_name". Only instances of the object class "correct_class_name" are allowed. - AWSJOM019E
The instance of object class "wrong_class_name" is not allowed for filter "filter_name". Only instances of object class "correct_class_name" are allowed. - AWSJOM020E
A null value is not allowed for filter "filter_name". Only instances of object class "correct_class_name" are allowed. - AWSJOM021E
The value "field_value" specified for field "field_name" contains the following character "non-valid_char", which is not allowed before and after the character "validation_char". - AWSJOM051E
The value "incorrect_field_value" specified for field "incorrect_field_name" is not allowed, because field "reference_field_name" has the value "reference_field_value" and these values for these fields are incompatible. - AWSJOM052E
The value "incorrect_field_value" specified for field "incorrect_field_name" is not allowed, because field "reference_field_name_1" has the value "reference_field_value_1" and field "reference_field_name_2" has the value "reference_field_value_2", and these values for these fields are incompatible. - AWSJOM053E
The value "incorrect_field_value" specified for field "incorrect_field_name" is not allowed, because field "reference_field_name_1" has the value "reference_field_value_1", field "reference_field_name_2" has the value "reference_field_value_2", and field "reference_field_name_3" has the value "reference_field_value_3". These values for these fields are incompatible. - AWSJOM101E
The required job stream has not been supplied for job "job_name". - AWSJOM102E
The required job definition has not been supplied for job "job_name". - AWSJOM103E
The required calendar has not been supplied for run cycle "run_cycle_name" of type calendar. - AWSJOM104E
A calendar has been incorrectly supplied for run cycle "run_cycle_name" of type simple or rule. - AWSJOM105E
The required host workstation has not been supplied for a workstation that has a workstation type of extended agent, agent, pool, dynamic pool or remote engine. - AWSJOM106E
A host workstation has been incorrectly supplied in the definition of a workstation of type fault-tolerant agent or domain manager. - AWSJOM107E
A host workstation has been incorrectly supplied for a workstation definition, where the workstation is hosted by the master domain manager. - AWSJOM108E
A domain has been incorrectly supplied for the definition of a workstation of type extended agent, agent, pool, dynamic pool or remote engine. - AWSJOM109E
A parent domain has been incorrectly supplied for the definition of a domain because the domain is the master domain, which cannot have a parent. - AWSJOM110E
The required workstation or workstation class has not been supplied in this object definition. - AWSJOM111E
The required workstation has not been supplied for a workstation link definition. - AWSJOM112E
The required valid network agent has not been supplied for the inter-network dependency defined for job or job stream "object_name". - AWSJOM113E
The required resource has not been supplied for the resource dependency defined for job or job stream "object_name". - AWSJOM114E
The required prompt has not been supplied for the prompt dependency defined for job or job stream "object_name". - AWSJOM115E
The required workstation or workstation class has not been supplied for the file dependency defined for job or job stream "object_name". - AWSJOM116E
The required job has not been supplied for the internal dependency defined for job "job_name". - AWSJOM117E
The required job or job stream has not been supplied for the external dependency defined for job or job stream "object_name". - AWSJOM118E
The job "target_job_key" supplied as an internal dependency for job "job_name" does not exist in the job stream "job_stream_key". - AWSJOM119E
The external dependency defined for job or job stream "object_name" cannot be on both a job and a job stream. - AWSJOM120E
The value specified for the parent domain "parent_domain_name" is not allowed. A domain and its parent cannot have the same name. - AWSJOM121E
A list of workstations cannot be specified for a workstation class if the class already includes all workstations. - AWSJOM122E
The required valid time interval has not been supplied in the definition of dependency resolution "resolution". - AWSJOM123E
A time interval has been incorrectly supplied in the definition of dependency resolution "resolution". - AWSJOM124E
A variable table has been incorrectly supplied for run cycle "run_cycle_name", which is exclusive. - AWSJOM125E
An action has not been supplied with the latest start time definition for the following job stream, job or run cycle: "object_name". - AWSJOM126E
A latest start time has not been supplied with the action definition for the following job stream, job or run cycle: "object_name". - AWSJOM127E
The required calendar offset type has not been supplied in the definition of run cycle "run_cycle_name" of type calendar. - AWSJOM128E
A calendar offset has been incorrectly supplied in the definition of run cycle "run_cycle_name" of type simple or rule. - AWSJOM129E
The required iCalendar definition has not been supplied in the definition of run cycle "run_cycle_name" of type simple or rule. - AWSJOM130E
An iCalendar definition has been incorrectly supplied in the definition of run cycle "run_cycle_name" of type calendar. - AWSJOM131E
The required access method has not been supplied in the definition of a workstation of type extended agent. - AWSJOM132E
An access method has been incorrectly supplied in the definition of a workstation of type domain manager, fault-tolerant agent, standard agent, or workload broker. - AWSJOM133E
The required security level has not been supplied in the definition of a workstation of type domain manager, fault-tolerant agent, standard agent, or workload broker. - AWSJOM134E
A security level has been incorrectly supplied in the definition of a workstation of type extended agent, pool, or dynamic pool. - AWSJOM135E
The required field "field_name" has not been supplied with the definition of Windows user name "full_name". - AWSJOM136E
The field "field_name" in the definition of Windows user name "full_name" exceeds the maximum length of "max_length" bytes. - AWSJOM137E
The job stream "job_stream_key" contains a job with a dependency that would create the following looped dependency chain of jobs: "looped_job_dependency_chain". - AWSJOM138E
The dependencies defined for job or job stream "object_name" are incorrect because they would give a total number of dependencies generated in the plan "total_dependencies" that exceeds the maximum of 40. - AWSJOM139E
A resource dependency has been incorrectly defined for both the job stream and for job "job_name". - AWSJOM140E
The file dependency defined for job or job stream "object_name" is incorrect, because the concatenation of the file path "file_path" and the file qualifier "file_qualifier" is longer than the maximum length of "max_length" bytes. - AWSJOM141E
The identified job definition is incorrect because it is an instance of a z/OS job definition (ZOSJobDefinition). Only instances of distributed job definitions (DistJobDefinition) are allowed. - AWSJOM142E
The identified job definition is incorrect, because the concatenation of the task string "task_string" and the return code mapping "return_code_mapping" is longer than the maximum length of "max_length" bytes. - AWSJOM143E
One or more lines in the comment entered for job or job stream "object_name" exceeds the maximum length, which is "max_length". - AWSJOM144E
Event rule "object_name" does not define any event condition. At least one event condition must be defined. - AWSJOM145E
Event rule "object_name" of type "event_rule_type" defines multiple event conditions. No more than one event condition must be defined. - AWSJOM146E
Event rule "object_name" of type "event_rule_type" defines only one event condition. At least two event conditions must be defined. - AWSJOM147E
Event rule "object_name" of type "event_rule_type" cannot contain actions with response type "rule_response_type". - AWSJOM148E
The timezone "timezone_name" specified for the workstation "workstation_name" is not valid. - AWSJOM149E
The timezone "timezone_name" specified for the job or job stream "job_or_job_stream_name" is not valid. - AWSJOM150E
Timezone "timezone_name" specified for the event rule "erule_name" is not valid. - AWSJOM151E
The job stream "job_stream_key" contains the following critical jobs that have neither specific deadline definitions nor inherited deadline definitions from the job stream or the job stream run cycles: "critical_jobs_without_deadlines" - AWSJOM152E
The job stream "job_stream_key" contains a duplicate run cycle name: "run_cycle_name". - AWSJOM153E
The job stream "job_stream_key" contains a duplicate job name: "job_name". - AWSJOM154E
The variable table "variable_table_key" contains a duplicate variable name: "variable_name". - AWSJOM155E
The availability calendar "calendar_key" contains a duplicate run cycle name: "run_cycle_name". - AWSJOM156E
Too many availability calendar intervals. - AWSJOM157E
Malformed availability calendar interval. - AWSJOM158E
Missing run cycle type. - AWSJOM159E
Unexpected exception type definition. - AWSJOM160E
Negative availability run cycle priority. - AWSJOM161E
Unexpected job strem related field definition. - AWSJOM162E
Availability calendar validation failed. - AWSJOM163E
Availability calendar iCalendar validation failed. - AWSJOM164E
Availability calendar timezone error. - AWSJOM165W
Warning: property has a time part. This part will be ignored. - AWSJOM166E
The required protocol has not been supplied in the definition of a workstation of type agent. - AWSJOM167E
A protocol has been incorrectly supplied, it is supported only for the definition of a workstation of type agent. - AWSJOM168E
The property "property" of the workstation "workstation" cannot be modified. - AWSJOM169E
The dependency resolution "resolution" has been incorrectly supplied in the remote job request "request". - AWSJOM170E
The type of the application "application" has been incorrectly supplied in the definition of the job "job". - AWSJOM171E
The workstation "workstation" of type "workstation_type" is not supported by the selected job definition type. The supported workstation types are: "supported_workstation_type". - AWSJOM172E
The operating system "os_type" of workstation "workstation" is not supported by the selected job definition type. The supported operating systems are: "supported_os". - AWSJOM173E
Unable to find the application job plug-in with ID "plug-inID". - AWSJOM174E
The COMPLETE_IF_BIND_FAILS return code mapping string is allowed for shadow jobs only. - AWSJOM175E
An incorrect security level has been supplied in the definition of a workstation of type workload broker. Only NONE value is allowed. - AWSJOM176E
An error occurred defining the workstation "workstation". The workload broker server is currently unreachable. - AWSJOM177E
An error occurred getting the definition of the workstation "workstation". The workload broker server is currently unreachable. - AWSJOM178E
An error occurred getting the definition of the workstation "workstation". The workload broker server is currently unreachable. - AWSJOM179E
An error occurred deleting definition of the workstation "workstation". The workload broker server is currently unreachable. - AWSJOM180E
An error occurred defining the workstation "workstation". The workload broker server is currently unreachable. - AWSJOM181E
An error occurred updating the workstation "workstation". The workload broker server is currently unreachable. - AWSJOM182E
An error occurred updating the workstation "workstation". The workload broker server is currently unreachable. - AWSJOM183E
An error occurred updating the workstation "workstation". The workload broker server is currently unreachable. - AWSJOM184E
The value "incorrect_field_value" specified for field "incorrect_field_name" in job "job_key" is not allowed. The pattern "invalid_pattern" is allowed only in password fields. - AWSJOM185E
The value you specified for the field "field_name" exceeds the maximum length, which is "max_length". - AWSJOM186E
The action to be performed when the maximum duration is exceeded has not been specified for the following job: "object_name". - AWSJOM187E
The action "action_name" to be performed when the maximum duration of the job: "object_name" is exceeded is not a valid action. - AWSJOM188E
The action to be performed when the minimum duration is reached has not been specified for the following job: "object_name". - AWSJOM189E
The action "action_name" to be performed when the minimum duration of the job: "object_name" is reached is not a valid action. - AWSJOM190E
The workstation class specified in the start condition and the workstation class specified in the job stream "job_stream" do not match. - AWSJOM191E
The maximum duration was specified using an expression that is not valid "type_name" for the job: "object_name". - AWSJOM192E
You must specify how to express the minimum duration for the job: "object_name". - AWSJOM193E
The minimum duration was specified using an expression that is not valid: "type_name" for the job: "object_name". - AWSJOM194E
An error occurred while parsing the mapping file at line: "incorrect_line". - AWSJOM195E
The workload application "batch_application_key" contains a duplicate job stream name: "job_stream_name". - AWSJOM196E
The required run cycle group has not been supplied for run cycle "run_cycle_name". - AWSJOM197E
The run cycle group "runcycle_group_key" must contain at least one run cycle. - AWSJOM198E
A repeat end time has not been supplied with the repeat interval definition for the following job stream, job or run cycle: "object_name". - AWSJOM199E
A repeat interval has not been supplied with the repeat end time definition for the following job stream, job or run cycle: "object_name". - AWSJOM200E
The supplied sched time is later than the supplied repeat end time definition for the following job stream, job or run cycle: "object_name". - AWSJOM201E
The value "incorrect_field_value" specified for field "incorrect_field_name" in job "job_key" is not allowed. The error is: "error_msg". - AWSJOM202E
A repeat interval has been incorrectly supplied in the definition of run cycle group "rcg". - AWSJOM203E
A repeat end time has been incorrectly supplied in the definition of run cycle group "rcg". - AWSJOM204E
A repeat interval has been incorrectly supplied in the definition of run cycle "rc". - AWSJOM205E
A repeat end time has been incorrectly supplied in the definition of run cycle "rc". - AWSJOM206E
A conditional dependency for job stream "js" refers to an output condition that is not defined in the database. - AWSJOM207E
The set of joined conditional dependencies defined for job or job stream "object_name" is incorrect because the resulting number of joined conditional dependencies in the plan "total_dependencies" exceeds the maximum supported value of "supported_dependencies". - AWSJOM208E
The name of a set of joined conditional dependencies must be unique. The specified name "object_name" already exists. - AWSJOM209E
Conditional dependency predecessors must be unique. The conditional dependency predecessor "predecessor_key" specified for "object_name" already exists. - AWSJOM210E
A conditional dependency for job stream "js" refers to an output condition "out_cond" that is not defined in the job "job". - AWSJOM211E
The access control list "acl" cannot be empty. - AWSJOM212E
The following success condition comparison expression is missing one of a pair of parentheses: "expression". - AWSJOM213E
The success condition comparison expression either contains an unsupported operator or an operator used incorrectly: "operator".Note that = < > != <> >= <= are comparison operators and they can be used for comparison expressions. AND OR NOT are logical operators and they can be used for boolean expressions, however, NOT is a unary operator. - AWSJOM214E
The following output condition comparison expression is incorrect: "expression". - AWSJOM215E
The success condition comparison expression contains the following non-valid operand: "operand". The operand must be an integer between -2147483647 and 2147483647. - AWSJOM216E
Syntax error in job key "job key". - AWSJOM217E
The string specified for the object definition to be created does not contain a properly formed object definition. - AWSJOM218E
The string specified for the object definition to be created does not contain a properly formed workload application template definition. - AWSJOM219E
The following error occurred: "parser error message" - AWSJOM220E
The value "field_value" specified for field "field_name" is outside the allowed range. Values must be between "range_start" and "range_end". - AWSJOM221E
The string specified for the object definition to be created does not contain a properly formed job stream definition. - AWSJOM222E
The string specified for the object definition to be created does not contain a properly formed job definition. - AWSJOM223E
The string specified for the object definition to be created does not contain a properly formed runcycle group definition. - AWSJOM224E
The string specified for the object definition to be created does not contain a properly formed one. - AWSJOM225E
Conditional dependency output conditions must be unique. The output condition "outcond_name" specified for "object_name" already exists. - AWSJOM226E
The string specified for the object definition to be created contains an incorrect folder definition. - AWSJOM227E
The value specified for the parent folder identifier "parent_folder_id" is incorrect. A folder and its parent cannot have the same identifier. - AWSJOM228E
The access control list item "acl_item" is incorrect: you must specify a user or group followed by a list of one or more rules. - AWSJOM900E
The workstation "workstation" provided for the start condition of type file does not exist. - AWSJOM901E
Login information is mandatory for the selected workstation "workstation_name". - AWSJOM902E
Workstation information is mandatory in the definition of file start condition in job stream "job_stream". - AWSJOM903E
The interval specified in the definition of job start condition in job stream "job_stream" must be greater than 0. - AWSJOM905E
The interval specified in the definition of job "job" in job stream "job_stream" must be greater than 0. - AWSJOM906E
The job "target_job_key" specified in the start condition of type job in "job_stream" does not exist. - AWSJOM907E
The job start condition "job_start_condition" does not contain a value for the mapping condition. - AWSJOM908E
The job start condition "job_start_condition" contains mapping condition longer than 256 character. - AWSJOM911E
You have specified a deadline action for job "job_name" but the related deadline offset is empty. - AWSJOM912E
You have specified a deadline offset for job "job_name" but the related deadline action is different from SUPPRESS. - AWSJOM913E
The job "job_name" contains polling condition longer than "max_length" character. - AWSJOM914E
The value "number_value" exceeds the maximum allowed size. - AWSJOM915E
Syntax error at line "line_number", starting from position "start_position" to "end_position": "error_msg"unexpected token "unexpected_token" found. - AWSJOM916E
Syntax error at line "line_number", starting from position "start_position" to "end_position": "error_msg"unexpected token found. - AWSJOM917E
Syntax error at line "line_number", starting from position "start_position": "error_msg"missing token. - AWSJOM918E
Syntax error at line "line_number", starting from position "start_position": "error_msg"missing token, found "missing_token". - AWSJOM919E
The "first_time_zone_definition" differs from "second_time_zone_definition" for "job_or_job_stream". A time zone need be specified just once, or all instances of it must be equal. - AWSJPL - Planner messages
This section lists error and warning messages that might be generated by the planner component. - AWSJPL001E
An internal error has occurred. The creation of the plan "plan" plan has failed. - AWSJPL002E
An internal error has occurred. The workstation "workstation" cannot be added to the plan. - AWSJPL003E
An internal error has occurred. The domain "domain" cannot be added to the plan. - AWSJPL004E
The workstation is not the master domain manager. The workstation name in the this_cpu option: "workstation" in the localopts file does not match the workstation name of the master domain manager in the database. The plan can be managed only on the master domain manager. - AWSJPL005E
The specified end time is not valid or is earlier than the start time. - AWSJPL006E
An internal error has occurred. A database object "object" cannot be loaded from the database. - AWSJPL008E
An internal error has occurred. The database cannot be locked. - AWSJPL009E
An internal error has occurred. The database cannot be unlocked. - AWSJPL010E
An internal error has occurred. One or more of the parameters to planman are null or missing. - AWSJPL011E
An internal error has occurred. The class "class" has given an exception. - AWSJPL012E
An internal error has occurred. The object "object" cannot be added to the plan. - AWSJPL013E
An internal error has occurred. The object "object" is not now in the database. - AWSJPL014E
An internal error has occurred. The plan cannot be closed. - AWSJPL015E
The production or trial plan cannot be extended because it does not exist. - AWSJPL016E
An internal error has occurred. A global option "option" cannot be set. - AWSJPL017E
The production plan cannot be created because a previous action on the production plan did not complete successfully. See the message help for more details. - AWSJPL018E
The database is already locked. - AWSJPL019E
An internal error has occurred. The native libraries cannot be loaded. - AWSJPL020E
An internal error has occurred. The Windows user "Windows_user" cannot be added to the plan. - AWSJPL021W
A date in calendar "calendar" is not in ISO format. - AWSJPL022E
An internal error has occurred. The calendar "calendar" cannot be added to the plan. - AWSJPL023E
An internal error has occurred. The internal global option "option" cannot be obtained from the database, or is incorrect. - AWSJPL024E
An internal error has occurred. The preproduction plan is not valid. - AWSJPL025E
The application job plug-in with ID "plug-in_ID" cannot be found. - AWSJPL026E
The job stream instance "job_stream" cannot be added to the plan. Either the plan has been temporarily locked by the database because of excessive activity (for example during the creation of a trial plan), or an internal error has occurred. - AWSJPL027E
An internal error has occurred. The trial plan extension has failed because the production plan either does not exist in the database or is not valid. - AWSJPL029E
An internal error has occurred. The job "job" cannot be added to the plan. - AWSJPL030E
The specified end time for the plan extension is not valid or is earlier than the current end time. - AWSJPL031E
The specified plan extension period must be greater than zero. - AWSJPL032E
An internal error has occurred. The internal file "file" could not be created. - AWSJPL033E
The required object "object" could not be found in the database. - AWSJPL034E
The supplied file name "file_name" is a reserved word and cannot be used. Alternatively, you might have omitted the file name and planman is treating the succeeding keyword as the file name. - AWSJPL035E
The planner encountered the following problem while changing the properties of the database to manage its state: "error" - AWSJPL036E
The planner did not find the definition for the master domain manager workstation in the database, or the workstation has the ignore attribute set. - AWSJPL037E
A plan with the same name is already running. If you are submitting the production plan, wait until it completes on the server before submitting another plan. If you are submitting a trial or a forecast plan, wait until the first request to create the plan completes, or submit another request using a different plan name. - AWSJPL200W
The password for the Windows user "Windows_user" is not valid. It is reset to null in the plan. - AWSJPL201W
The planner process is waiting to lock the database. - AWSJPL202W
The timeout configuration value for locking or unlocking the database is not valid. The planner process is using the default value. - AWSJPL203W
The workstation "workstation" belongs to a domain that has no manager. For the current plan only it has been moved to the master domain. - AWSJPL204W
Time zone-related information has been found for one or more workstations. However, time zones are not enabled in the global options. The time-zone-related information is ignored. - AWSJPL205W
Time zone-related information has been found for job stream "job_stream". However, time zones are not enabled in the global options. The time-zone-related information is ignored. - AWSJPL206W
Time zones are enabled in the database but the master domain manager definition does not include a time zone. The default time zone of the system where the master domain manager is running is used. - AWSJPL207W
The production plan does not exist and the planner creates it. - AWSJPL208W
The job stream "job_stream" has not been added to the production plan because the workstation "workstation" has the ignore attribute set. - AWSJPL209W
The job "job" has not been added to the production plan because the workstation "workstation" has the ignore attribute set. - AWSJPL505E
The ad-hoc job stream cannot be submitted because the production plan does not exist. - AWSJPL506E
The job stream "job_stream" cannot be submitted because the specified scheduled time "job_stream_scheduled_time" on the master domain manager is later than the end time of the production plan "production_plan_end_time" on the master domain manager. - AWSJPL507E
The submitted ad hoc job stream does not exist. - AWSJPL508E
The submitted ad hoc job stream cannot be processed because it is a draft. - AWSJPL509E
The submitted ad hoc job cannot be processed because it is defined for a workstation class, which is not allowed. - AWSJPL510E
The submitted ad hoc job stream cannot be processed because it is defined for a workstation class which has the ignore flag set. - AWSJPL511W
The job or job stream "job_or_job_stream" has an external dependency on itself without the explicit matching criteria Closest preceding (previous). The planner process assumes the matching criteria to be closest preceding (previous) which is the only valid matching criteria for this type of dependency. - AWSJPL512W
The job statistics have been reset for the following job "job", because the maximum values were exceeded. - AWSJPL513E
The ad hoc job cannot be submitted because the query filters are not valid. - AWSJPL514E
The ad-hoc job stream cannot be submitted because its start time "job_stream_start_time" is later than the value of the valid to argument in the job stream definition. - AWSJPL515E
The ad-hoc job stream cannot be submitted because its start time "job_stream_start_time" is earlier than the value of the valid from argument in the job stream definition. - AWSJPL516E
The ad-hoc job stream instance cannot be viewed or modified before submission because the job stream definition on which it is based contains one or more external dependencies on a job stream defined for a workstation class. - AWSJPL517E
The time extension specified for the creation of the production plan is not valid. - AWSJPL518E
An internal error has occurred. A previous job history cannot be removed from the database. - AWSJPL519E
An internal error has occurred. A job history cannot be created in the database. - AWSJPL521W
The workstation of a job is different to the workstation of its resource.Job "job" in job stream "job_stream" is for workstation "workstation". Resource "resource" is for workstation "workstation_resource" - AWSJPL522W
The workstation of a job stream is different to the workstation of its resource.Job stream "job_stream" is for workstation "workstation". Resource "resource" is for workstation "workstation_resource" - AWSJPL523W
The variable "variable" was not found in the database and so could not be resolved. - AWSJPL524E
The parameter "parameter" has been resolved, but the subsequent resolution makes the command string too long. - AWSJPL525W
The fully-qualified file name is longer than the maximum of "maximum" bytes. The dependency is ignored and the priority is set to 0. - AWSJPL526W
An external dependency in job stream "job_stream", or a job belonging to it, cannot be resolved because the matching criteria could not be satisfied. - AWSJPL527E
The specified date "date" exceeds the maximum value of 00:00:00 January 1, 2038 GMT. - AWSJPL528E
The job stream cannot be submitted because either another job stream has previously been submitted to this plan instance with the same alias, or you are trying to submit two or more job streams with the same alias. - AWSJPL529E
You have requested an extension of the existing production plan, but have supplied the -from parameter, which is only used for the creation of a plan. Use the -for or -to or -days parameters to extend the production plan. - AWSJPL530E
The trial plan cannot be created because the production plan already exists. - AWSJPL531E
An internal error has occurred. The symphony ID cannot be updated in the preproduction plan. - AWSJPL532E
An internal error occurred while loading the HTTPS port from the JMXBrowser. - AWSJPL533E
An internal error occurred while loading the HTTP port from the JMXBrowser. - AWSJPL534W
The event processor workstation is set to ignore in the production plan. The master domain manager workstation is used as the event processor, instead. - AWSJPL535W
The Workload Service Assurance feature is not enabled but at least one critical job was found in the plan. - AWSJPL536W
On the remote engine the production plan was deleted by a user command. - AWSJPL537W
The remote preproduction plan was deleted by a user command. - AWSJPL540E
Cleanup of old job history has failed due to the following error: "exception_message". - AWSJPL550E
Cleanup of detailed statistics has failed due to the following error: "exception_message". - AWSJPL551E
An internal error has occurred. A detailed statistic cannot be removed from the database. - AWSJPL552W
A cleanup operation of old job history is already running. Any other requests are skipped until the current operation completes. - AWSJPL553W
The resubmit job is not added to the job stream because the pool workstation "exception_message" cannot be found in the database. Verify the value of the resubmitJobName optman property, providing the name of a valid pool workstation. - AWSJPL601E
The date string "date_string" in the date list expression "date_list_expression" is not a valid date in ISO format (yyyymmdd). - AWSJPL602E
An internal error has occurred. The recur expression "recur_expression" is not compliant with the ICalendar standard. - AWSJPL603E
An internal error has occurred. A run cycle has a non-valid ICalendar parameter: "ICalendar_parameter". - AWSJPL604E
An internal error has occurred while evaluating the run cycles. The calendar "calendar_name" ("calendar_id") is not available. - AWSJPL605E
The ICalendar recur expression "recur_expression" used in the run cycle is not supported . - AWSJPL606E
The ICalendar recur expression "recur_expression" used in the run cycle, contains the unsupported token "token". - AWSJPL607E
The ICalendar recur expression "recur_expression" used in the run cycle, contains a value for the frequency which is not supported by HCL Workload Automation. - AWSJPL608E
The ICalendar recur expression "recur_expression" used in the run cycle, contains two or more interval tokens. Only one token is permitted per expression. - AWSJPL609E
The ICalendar recur expression "recur_expression" used in the run cycle is not valid. In rules that use the byfreeday or byworkday tokens, only the daily frequency is supported. - AWSJPL610E
The ICalendar recur expression "recur_expression" used in the run cycle, is not valid. An interval has been supplied that is not a positive integer. - AWSJPL611E
The ICalendar recur expression "recur_expression" used in the run cycle, is not valid. The following token is not valid when using a byfreeday or a byworkday token: "token". - AWSJPL612E
The ICalendar recur expression "recur_expression" used in the run cycle, is not valid. You can use only one byfreeday token or one byworkday token. You cannot use both, or more than one of either. - AWSJPL613E
An internal error has occurred. The following error message was given by the call to the ICalendar library: "error_message". - AWSJPL614E
An internal error occurred when attempting to create the following ICalendar token "token". This token cannot be added to a recur expression using a byfreeday token or a byworkday because an expression of this type including this token is not supported by HCL Workload Automation. - AWSJPL615E
The following run cycle "run_cycle" in the following job stream "job_stream" is not valid because the from date and time have not been specified. - AWSJPL616E
The ICalendar recur expression "recur_expression" used in the run cycle, contains an interval value greater than the maximum allowed: "value". - AWSJPL617E
The ICalendar recur expression "recur_expression" used in the run cycle, has the following missing token or tokens: "token_or_tokens". - AWSJPL618E
The ICalendar recur expression "recur_expression" used in the run cycle, contains an invalid interval value. The value must be not less than 1. - AWSJPL619E
The ICalendar recur expression "recur_expression" used in the run cycle, specifies a week number in the byday token. This is not allowed in a weekly rule. - AWSJPL620E
The ICalendar recur expression "recur_expression" used in the run cycle, has a non-valid value for the week number in the byday token. Week number can be from -5 to -1 or from 1 to 5. - AWSJPL621E
The ICalendar recur expression "recur_expression" used in the run cycle has been specified with two mutually exclusive tokens for the frequency "frequency".The tokens are"token1" and "token2". - AWSJPL622E
The ICalendar recur expression "recur_expression" used in the run cycle has been defined with a value "value" for the list-type token "list" which is less than the minimum allowed value: "minimum". - AWSJPL623E
The ICalendar recur expression "recur_expression" used in the run cycle has been defined with a value "value" for the list-type token "list" which is greater than the maximum allowed value: "maximum". - AWSJPL624E
The ICalendar recur expression "recur_expression" used in the run cycle has been defined with a value of zero for the list-type token "list" which is not allowed for that token. - AWSJPL625E
The ICalendar recur expression "recur_expression" used in the run cycle has been specified with an interval value "value" which is not greater than zero. - AWSJPL626E
The ICalendar recur expression "recur_expression" used in the run cycle is specified with an incorrect weekday "weekday" in the day list. - AWSJPL627E
The ICalendar recur expression "recur_expression" used in the run cycle has been specified with three mutually exclusive tokens for the frequency "frequency".The tokens are"token1", "token2", and "token3". - AWSJPL628E
The ICalendar recur expression "recur_expression" used in the run cycle is defined with a token "token" that cannot be used in a rule with the frequency "frequency". - AWSJPL629E
An internal error has occurred while evaluating the run cycles. The run cycle group "run_cycle_group_name" ("run_cycle_group_id") is not available. - AWSJPL630E
The following run cycle "run_cycle" in the following run cycle group "run_cycle_group" is not valid because the from date and time have not been specified. - AWSJPL701E
An internal error has occurred in the planner while creating a UUID. The error message is: "error_message". - AWSJPL702E
An internal error has occurred. The planner is unable to load the status of the preproduction plan from the database because the property: "property_name" has the following incorrect value: "property_value". - AWSJPL703E
An internal error has occurred. The planner is unable to load the status of the preproduction plan because of a problem accessing the database. - AWSJPL704E
An internal error has occurred. The planner is unable to extend the preproduction plan. - AWSJPL705E
An internal error has occurred. The planner is unable to create the preproduction plan. - AWSJPL706E
An internal error has occurred. The planner is unable to confirm the preproduction plan. - AWSJPL707E
An internal error has occurred. The planner is unable to save the status of the preproduction plan because of a problem accessing the database. - AWSJPL718E
An internal error has occurred. The planner is unable to delete the preproduction plan. - AWSJPL719W
An error occurred when the planner tried to update the preproduction plan statistics. - AWSJPL720E
An error occurred when the planner tried to remove completed and obsolete instances from the preproduction plan. - AWSJPL721E
An internal error has occurred. An error occurred when the planner tried to resolve the dependency in the preproduction plan. - AWSJPL722E
An internal error has occurred. An error occurred when the planner was evaluating the run cycles of job stream "job_stream". The error message is: "error_message". - AWSJPL723E
An internal error has occurred. An internal error has occurred when the planner was evaluating the runcycles of the job stream "job_stream". - AWSJPL724E
An internal error has occurred. The same thread is trying to create multiple contexts. The name of the thread is: "thread_name". - AWSJPL800W
The planner (ID = "planner_ID") that you are trying to stop is busy and cannot respond. It will be stopped as soon as it becomes active again. - AWSJPL801E
You cannot run the planner to update the production plan, as another planner (ID = "planner_ID") is currently updating the production plan. - AWSJPL802W
You are trying to stop a planner (ID = "planner_id") that is not running. - AWSJPL804W
The start time of first not complete preproduction plan job stream instance is "property_name" and it is old. Please check it running planman showinfo command. - AWSJPL805E
The planner operation cannot continue. The database has been unlocked. Rerun the operation. - AWSJPU - Plan replication on database messages
This section lists error and warning messages that might be generated by the plan replication on database routines. - AWSJPU001E
An internal error has occurred. A plan object "object" cannot be loaded from the database. - AWSJPU002E
The required object "object" could not be found in the plan. - AWSJPU003E
An internal error has occurred. The error is the following: "exception_message". - AWSJPU004E
The following error has occurred while applying a "event_type" event for "object_name": "error_message". - AWSJPU005E
An internal error occurred while accessing the database. The internal error message is: "error". - AWSJPU006E
An internal error occurred in the database connection. The internal error message is: "error". - AWSJPU007E
An unrecoverable error occurred while applying an event to the RDBMS plan. The internal error message is: "error". - AWSJPU008E
An unrecoverable error occurred while applying an event to the RDBMS plan. The record read is of unexpected type "type". - AWSJPU103E
Symphony file load has failed due to the following error: "exception_message". - AWSJPU113E
Delete of plan "plan_name" has failed due to the following error: "exception_message". - AWSJPU121W
The Resync action is not performed because the local Workstation is not the current master. - AWSJPU122W
The object "key" has negative elapsed time. Using default value: "default". - AWSJPU123E
The creation of the output conditions of the job definition in plan "job" failed due to the following error: "exception_message". - AWSJPU124E
An internal error occurred closing a database connection, reason: "reason". - AWSJPU125E
An internal error occurred opening a DatabaseConnection. - AWSJSY - Symphony file processing messages
This section lists error and warning messages that might be generated by the routines that process the Symphony file. - AWSJSY101E
The Symphony plan operation "operation" could not be completed because the requested Symphony plan object was not found. The internal error message is: "error_message". - AWSJSY102E
The Symphony plan operation "operation" could not be completed because the supplied variable was not found. The internal error message is: "error_message". - AWSJSY103E
The Symphony plan operation "operation" could not be completed because the dependency "dependency" of type "dependency_type" was not found. - AWSJSY401E
The Symphony plan operation "operation" could not be completed because an internal error has occurred while accessing the Symphony plan. The internal error message is: "error_message". - AWSJSY402E
An internal error has occurred. The Symphony plan operation "operation" could not be completed because an internal problem was found while accessing the configuration file. Either the file does not exist or it is corrupted. - AWSJSY403E
The Symphony plan operation "operation" could not be completed because a timeout occurred while connecting to the workstation containing the job output file.. - AWSJSY404E
The Symphony plan operation "operation" could not be completed because an error has occurred while accessing the Symphony plan. The error message is: "error_message". - AWSJSY405E
The Symphony plan operation "operation" could not be completed because an error has occurred while accessing the requested file. The error message is: "error_message". - AWSJSY501E
Incorrect data was detected while performing the Symphony plan operation "operation". The internal error message is: "error_message". It identifies the incorrect data and the problem. - AWSJSY502E
The Symphony plan operation "operation" cannot be performed because the filter "filter" is not valid. - AWSJSY503E
The Symphony operation "operation" cannot be performed because two incompatible filters have been specified for the same operation. The incompatible filters are: "filter1" and "filter2". - AWSJSY504E
A null value was specified for object "object" while performing the operation "operation". The value cannot be null. - AWSJSY505E
A null value was specified for object "object1" and object "object2" while performing the "operation" operation. They cannot both be null. - AWSJSY506E
A null value was specified for object "object1", object "object2", object "object3" and object "object4" while performing the "operation" operation. They cannot all be null. - AWSJSY507E
The "operation" operation cannot be performed because a non-valid object instance has been specified for field "field_name". - AWSJSY508E
You do not have permission to perform the operation "operation" on the following object type "object_type" with object key: "object_key". - AWSJSY509E
An incorrect value "value" was specified for the variable "variable" while performing the "operation" operation.. - AWSJSY510E
The "operation" operation cannot be performed because a date or time range is not valid. The value specified for date or time field "field_1" is later than the value specified for date or time field "field_2". - AWSJSY512E
The Symphony plan operation "operation" cannot be performed because the value "value" is not valid for the filter "filter". - AWSJSY513E
The Symphony plan operation "operation" cannot be performed because the connection timed out. - AWSJSY514E
The Symphony plan operation "operation" cannot be performed because the Symphony file "symphony_file" cannot be opened. - AWSJSY515E
The Symphony plan operation "operation" cannot be performed because you are adding a self-dependency to the job "job_key", which is not allowed. - AWSJSY516E
The Symphony plan operation "operation" cannot be performed because the value "value" is not valid for the field "field". - AWSJSY517E
The Symphony plan operation "operation" cannot be performed because you are adding a self-dependency to the job stream "job_stream_key", which is not allowed. - AWSJSY518E
The Symphony plan operation "operation" cannot be performed because the date "date" exceeds the maximum of 00:00:00 January 1, 2038 GMT. - AWSJSY519E
The variable "variable"cannot be specified while performing the operation "operation". - AWSJSY520E
The Symphony plan operation "operation" could not be completed because more than one dependency "dependency" of dependency type "dependency_type" exists. - AWSJSY521E
The Symphony plan operation "operation" could not be completed because you do not have permission to perform the operation DISPLAY on the supplied local variable. - AWSJSY522E
The plan operation "operation" cannot be performed because the current plan does not exist. - AWSJSY523E
The Symphony plan operation "operation" cannot be performed because the date "date" is invalid. - AWSMSCD - Smart Cloud Control Desk plug-in messages
This section lists error and warning messages. - AWSMSCD102E
The ticket has not been successfully opened for following reason: "reason". - AWSMSCD103E
The action type "action_type" is not supported. - AWSMSCD104E
SmartCloud Control Desk url not defined. - AWSMSCD105E
SmartCloud Control Desk username not defined. - AWSMSCD106E
SmartCloud Control Desk password not defined. - AWSMSCD107E
Wrong SmartCloud Control Desk username and/or password. - AWSMSCD108E
The SmartCloud Control Desk Url "url" is malformed. - AWSMSCD109E
The TWS windows user was not found. - AWSMSCD110W
Skip configuration item "cinum" beacause was not found on SmartCloud Control Desk. - AWSMSCD111W
Skip affected person " affperson" because not found on SmartCloud Control Desk. - AWSMSL - Message logger plug-in messages
This section lists error and warning messages that might be generated by the message logger plug-in. - AWSMSL102E
The message "message_ID" has been not logged. Reason: "reason" - AWSMSL103E
The action type "action_type" is not supported. - AWSMSP - Mail sender plug-in messages
This section lists error and warning messages that might be generated by the mail sender plug-in. - AWSMSP101E
The To(recipient) address is not valid or is blank. - AWSMSP102E
The mail subject is not valid or is blank. - AWSMSP104E
The mail "subject" has not been successfully delivered to "recipient" for the following reason: "reason". - AWSMSP105E
The action type "action_type" is not supported. - AWSPMG - Plug-in manager messages
This section lists error and warning messages that might be generated by the plug-in manager. - AWSPMG001E
No plug-in with name "plug-in_name" was found. - AWSPMG002E
No custom configuration file has been specified in the plug-in properties file for plug-in "plug-in_name". - AWSPMG003E
Cannot validate configuration file for plug-in "plug-in_name". - AWSPMG004E
An I/O error occurred while writing the configuration file for plug-in "plug-in_name". - AWSPRO - Job plug-in for OSLC Provisioning messages
This section lists error and warning messages that might be generated by the job plug-in for OSLC Provisioning. - AWSPRO001E
You did not specify the Catalog Uri. - AWSPRO002E
You did not specify the username for Catalog. - AWSPRO003E
You did not specify the password for Catalog. - AWSPRO004E
You did not specify the Service Provider Uri. - AWSPRO005E
You did not specify the username for Service Provider. - AWSPRO006E
You did not specify the password for Service Provider. - AWSPRO007E
You did not specify the Template Uri. - AWSPRO008E
An error occurred while attempting to connect to the IBM OSLC server. The IBM OSLC server connection parameters are incorrect: "error_msg". - AWSPRO009E
An error occurred during connection to the IBM OSLC service. Verify your credentials. - AWSPRO011E
It is not possible to monitor the status of this job after the restart of the agent. The status is set to unknown. - AWSPRO012E
It is not possible to monitor the status of the job. The status is set to unknown. - AWSPRO013E
The syntax of the Service Provider URI "provider URI" is not correct. The error is: "error message". - AWSPRO014E
The creation factory was not found for the service provider "provider URI". - AWSPRO015E
There was a failure contacting the Service Provider at the URI "provider URI". The error is: "error message". - AWSPRO016E
The provisioning action failed with an error on the remote system. The error is: "error message". - AWSPRO017E
The syntax of specified for the Registry Services URI is not correct. Verify that you specified a valid string. - AWSPRO018E
The syntax specified for the Registry Services URI is not correct. Verify that you specified a valid string. - AWSPRO019E
The syntax specified for the Provisioning Service Provider URI is not correct. Verify that you specified a valid string. - AWSPRO020E
The syntax specified for the Provisioning Service Provider URI is not correct. Verify that you specified a valid string. - AWSPRO021E
The property file "provider URI" is empty. - AWSPRO022E
The property file "plug-in property file" was not found. - AWSPRO023E
An error occurred loading the property file "plug-in property file". - AWSPRO024E
The syntax specified for the service provider URI "provider URI" is not correct. Verify that you specified a valid uri. - AWSPRO025E
An error occurred while retrieving the details of the service provider with the URI "provider URI". The error is: "error message". - AWSPRO026E
The syntax specified for the service provider URI "provider URI" is not correct. Verify that you specified a valid string. - AWSPRO027E
An error occurred while retrieving the list of the templates for the service provider with the URI "provider URI". The error is: "error message". - AWSPRO028E
The syntax specified for the service provider URI "provider URI" is not correct. Verify that you specified a valid string. - AWSPRO029E
An error occurred while loading the user interface to configure the instance. The error is: "error message". - AWSPRO030E
The syntax specified for the service provider URI "provider URI" is not correct. Verify that you specified a valid string. - AWSPRO031E
An error occurred while loading the user interface to configure the instance. The error is: "error message". - AWSPRO032E
The address discovered for the panel "creation dialog URI" is not correct. The error is: "error message". - AWSPRO033E
The syntax specified for the Registry Services URI "registry services URI" is not correct. The error is: "error message". - AWSPRO034E
An error occurred while retrieving the list of service providers from the Registry Services with the URI "Registry services URI". The error is: "error message". - AWSPRO035E
An error occurred while retrieving the list of the service provider from the Registry Services with the URI "Registry services URI". - AWSPRO036E
The address discovered for the panel "creation dialog URI" is not correct. The error is: "error message". - AWSPRO037E
The address discovered for the panel "creation dialog URI" is not correct. The error is: "error message". - AWSPRO038E
The address discovered for the panel "creation dialog URI" is not correct. The error is: "error message". - AWSPRO039E
The address discovered for the panel "selection dialog URI" is not correct. The error is: "error message". - AWSPRO040E
The address discovered for the panel "selection dialog URI" is not correct. The error is: "error message". - AWSPRO041E
The address discovered for the panel "creation dialog URI" is not correct. The error is: "error message". - AWSPRO042E
The following error occurred when contacting the service provider: "error message". - AWSPRO043E
An error occurred while retrieving the list of service providers from the Registry Services with the URI "Registry services URI". The error is: "error message". - AWSPRO044E
An error occurred while connecting to the service "Instance URI". The error is "error message" - AWSPRO045E
You cannot modify an empty instance - AWSPRO046E
A generic error retrieving service provider has occurred. - AWSREP - Plan extractor messages
This section lists error and warning messages that might be generated by the plan extractor. - AWSREP001E
An internal error has occurred. There are no output streams available to send the response. - AWSREP002E
The requested report type "report_type" is unknown. - AWSREP003E
The mandatory parameter "parameter" is missing. - AWSREP004E
If you specify "parameter1" you must also specify "parameter2". - AWSREP005E
You cannot specify both "parameter1" and"parameter2". - AWSREP006E
An internal error has occurred. The output channel cannot write the report. - AWSREP007E
An internal error has occurred. The command "command" passed to the server is not a recognizable HCL Workload Automation command. - AWSREP008E
An internal error has occurred. The expected parameter "parameter" was missing for the command "command". - AWSREP009E
The parameter "parameter" has been specified twice. - AWSREP010E
The report format "report_format" is not supported. - AWSREP011E
You cannot specify the "parameter" parameter with the "format" format. - AWSREP012E
The specified symphony files do not exist. - AWSRES - Common REST messages
This section lists error and warning action helper messages that might be issued by the common REST process. - AWSRES001E
The following fault message was received from the agent as a result of a scheduling request: "fault_message" - AWSRES002E
The requested service has ended with a fault. The internal error message is: "error_message". - AWSRES003E
The REST service cannot be contacted. Check if the service is running or the existence of firewall rules or some issues on the dns side resolving the server hostname that could prevent contacting the service. The internal error message is: "error_message". - AWSRES004E
An invalid response was returned. - AWSRES005E
The service at the address "error_message" cannot be contacted because the address is invalid. - AWSRES006E
Unable to find the configuration file "config_file". - AWSRES007E
Unable to find the configuration file "config_file". - AWSRES008E
You are not authorized to perform the requested operation. - AWSRES009E
The following unexpected reply was returned: "error_message". - AWSRES010E
The requested service is not available. - AWSRJM - Remote job manager messages
This section lists error and warning messages that might be generated by the remote job manager. - AWSRJM002E
The job stream instance matching the criteria was not found in the preproduction plan on the remote engine. - AWSRJM004E
The job matching the criteria was not found in the production plan on the remote engine. - AWSRJM020E
The remote job has been removed from the remote plan. - AWSRJM021E
An error has occurred on the remote engine during the binding process. - AWSRJM023E
An incomplete job stream instance matching the criteria was found in the preproduction plan, but it was removed from the production plan. - AWSRJM024E
There was an error while binding the remote job to the local job instance. The error message returned by the fault is "error_message". - AWSRST - Distributed REST messages
This section lists error and warning messages that might be generated by the routines that handle the distributed REST process. - AWSRST001E
A fault was generated processing a shadow job request. The error message returned by the fault is "error_message". - AWSRST002E
There was an error while binding the remote job to the local job instance. The error message returned by the fault is "error_message". - AWSRST003I
The monitoring of the remote job was stopped by a user request - AWSRST004E
An internal error occurred while canceling monitoring of the job "alias". The error returned by the exception is "error_message" - AWSRST005E
An internal error occurred while canceling the job "alias". The error returned by the exception is "error_message" - AWSRST006E
An internal error occurred while canceling the job "alias". The error returned by the exception is "error_message" - AWSRST007E
An internal error occurred while canceling the job "alias". The error returned by the exception is "error_message" - AWSRST008E
There was an error while binding the remote job to the local job instance. - AWSRST009E
A fault was generated adding the workstation "wks_name" to the plan. The error message returned by the fault is "error_message". - AWSRST010E
There was an error while adding the workstation "wks_name" to the plan. The error message returned by the fault is "error_message" - AWSRST011E
There was an error while loading the definition of the workstation "wks_name" from the database. The error message returned is "error_message" - AWSRST012E
A fault was generated adding the user "user_name" to the plan. The error message returned by the fault is "error_message". - AWSRST013E
There was an error while adding the user "user_name" to the plan. The error message returned by the fault is "error_message" - AWSRST014E
There was an error while loading the definition of the user "user_name" from the database. The error message returned is "error_message" - AWSSAM - IBM System Automation for Multi Platform - Installation messages
This section lists error and warning messages that might be issued when you install script for the integration with Tivoli System Automation for Multi Platform. - AWSSAM002E
Only the user ""root"" can run the createResources script. - AWSSAM003E
The createResources script is being run from the wrong directory. - AWSSAM027E
The IBM System Automation for Multiplatforms configuration for IBM Workload Scheduler has failed. - AWSSMS - SAP Solution Manager messages
This section lists error and warning messages that might be issued by SAP Solution Manager. - AWSSMS001E
The priority is out of the range(1-100). - AWSSMS002E
The operation is not supported by the external scheduler. - AWSSMS003E
The job definition is missing in the Workload Scheduler database. - AWSTAP - Action plug-in messages
This section lists error and warning messages that might be generated by the action plug-in. - AWSTAP500E
Only one instance of the filtering attribute ""attribute"" is supported for the ""event"" event defined in the ""plug-in"" plug-in. - AWSTAP501E
Only one instance of the filtering value ""value"" is allowed for the filtering attribute ""attribute"" for the event ""event"" defined in the plug-in ""plug-in"". - AWSTEL - EIF event management messages
This section lists error and warning messages that might be generated by the EIF event management processes. - AWSTEL101E
The event ""event_name"" has been not processed. - AWSTEL102W
The event sequence numbers sent by the client with ID ""client_id"" are out of synch with those on the server. Event numbers between ""previous_number"" and ""last_number"" were not received and could be missing. - AWSTEL103W
Some event numbers sent by the client with ID ""client_id"" are missing in the sequence on the server. The event number sequence ranges from ""1"" to ""max_number"". The latest event received by the server is ""current_number"" and the event previous to that is ""last_number"". Therefore, the events between ""last_number"" and ""current_number"" were not received and are missing. - AWSTSI - SAP Solution Manager messages
This section lists error and warning messages that might be issued by SAP Solution Manager. - AWSTSI001E
An internal error occurred while creating a runcycle. The error message is: "error_message". - AWSTSI002E
The scheduled job cannot start because the HCL Workload Automation current plan has expired or is not available. - AWSTSI003E
The external job is created but the scheduled job cannot start because the HCL Workload Automation current plan has expired or is not available. - AWSTSI004E
The external job is created but the scheduled job cannot start because it is not in the HCL Workload Automation current plan range. - AWSTSI005E
Error:"error_message" - AWSTSI006W
The external job is created but the scheduled job cannot start because the input date and time: "object" is before to the current date and time: "object". - AWSTSI007E
The scheduled job cannot start because the agent is not included in the current plan. - AWSTSI008E
The "object" is missing in the Workload Scheduler database. - AWSTSI009E
The scheduled jobs cannot be found because HCL Workload Automation current plan is not available. - AWSTSI010E
The external job cannot created and scheduled because it is not in the HCL Workload Automation current plan range. - AWSTMB - Mailbox messages
This section lists error and warning messages that might be generated by the mailbox processing. - AWSTMB001E
The mailbox is full. - AWSTMB002E
An error occurred when reading the content of the "mailbox_name" mailbox. The record read is of unexpected type "type". - AWSTOE - Object exporter messages
This section lists error and warning messages that might be generated by the object exporter. - AWSTOE001E
The workload application template is empty. - AWSTOE002E
An errror occurred while exporting the workload application template to XML format. - AWSTPL - Time planner messages
This section lists error and warning messages that might be generated by the time planner module. - AWSTPL001E
The critical jobs predecessors network table is not available. - AWSTPL002E
The planned start time was not reloaded. - AWSTPL003E
A loop condition was detected in the critical job predecessors network. - AWSTPL005E
An error occurred while persisting the planned start times in the database. - AWSTPL006E
An inconsistency is present in the critical jobs predecessors network table. - AWSVAL - Plug-in validator messages
This section lists error and warning messages that might be generated by the plug-in validator. - AWSVAL001E
The rule action must not be null. - AWSVAL002E
The rule action type must not be null or empty. - AWSVAL003E
The plug-in name must not be null nor empty. - AWSVAL004E
The action "action_name" is not supported by the specified "plug-in_name" plug-in. - AWSVAL005E
The parameter "parameter_name" is not valid for the "action_name" action in the "plug-in_name" plug-in. - AWSVAL006E
The mandatory parameter "parameter_name" is not specified for the "action_name" action using the "plug-in_name" plug-in. - AWSVAL007E
The parameter "parameter_name" for the "action_type" action type defined in the "plug-in_name" plug-in, is not a valid type. - AWSVAL008E
The value of parameter "parameter_name", for the "action_type" action type defined in the "plug-in_name" plug-in, is not between "minimum" and "maximum". - AWSVAL009E
The event condition cannot be null. - AWSVAL010E
The event condition type must not be null or empty. - AWSVAL011E
The event condition "condition_name" is not supported by the specified "plug-in_name" plug.in. - AWSVAL012E
The parameter "parameter_name" is not valid for the event "event_name" using the plug-in "plug-in_name". - AWSVAL013E
The mandatory filtering attribute "attribute_name" was not specified for the "event_name" event defined in the "plug in_name" plug-in. - AWSVAL014E
The filtering attribute "attribute_name" has too many filtering values for the "event_name" event defined in the "plug-in_name" plug-in. Only one is permitted. - AWSVAL015E
The specified plug-in "plug-in_name" does not exist. - AWSVAL016E
The attribute "attribute_name" cannot have a blank operator. - AWSVAL017E
The operator "operator_name" is not valid for the attribute "attribute_name" in the "event_type" event type defined in the "plug-in_name" plug-in. - AWSVAL018E
The value "value" is not valid for the attribute "attribute_name" in the "action_type" action type defined in the "plug-in_name" plug-in. - AWSVAL019E
You are not permitted to modify the attribute "attribute_name" for the "event_type" event type defined in the "plug-in_name" plug-in. - AWSVAL020E
The operator "operator_name" is not valid for type "type_name" in "event_type" event type defined in the "plug-in_name" plug-in. - AWSVAL021E
The condition "condition_name" for type "event_type", defined in the "plug-in_name" plug-in, contains at least one wildcard character (asterisk * or question mark ?, or both). Wildcards are not allowed. - AWSVAL022E
The value of parameter "parameter_name", for the "action_type" action type defined in the "plug-in_name" plug-in, must not be less than "minimum_length" characters. - AWSVAL023E
The value "value" is not valid for the attribute "attribute_name" in the "event_type" event type defined in the "plug-in_name" plug-in. - AWSVAL024E
The filtering attribute "attribute_name", for the "event_type" event type defined in the "plug-in_name" plug-in, is not of a valid type. - AWSVAL025E
The value of filtering attribute "attribute_name", for the "event_type" event type defined in the "plug-in_name" plug-in, is not between "minimum" and "maximum". - AWSVAL026E
The value of filtering attribute "attribute_name", for the "event_type" event type defined in the "plug-in_name" plug-in, must be not less than "minimum". - AWSVAL027E
An internal error has occurred while parsing the regular expression used for the attribute "attribute_name" in the event type "event_type" defined in the plug-in "plug-in_name". - AWSVAL028E
An internal error has occurred while parsing the regular expression used for the parameter "parameter_name" in the action type "action_type" defined in the plug-in "plug-in_name". - AWSVAL029E
You cannot specify the attribute "attribute_name" more than once for the event type "event_type" defined in the plug-in "plug-in_name". - AWSVAL030E
The range "value" is not valid for the attribute "attribute_name" in the "event_type" event type defined in the "plug-in_name" plug-in. - AWSVAL031E
The value for the attribute "attribute_name" in the "event_type" event type defined in the "plug-in_name" event provider cannot be empty. - AWSVAL032E
The value for the attribute "attribute_name" in the "event_type" event type defined in the "plug-in_name" event provider must have at least "min" characters. - AWSVAL033E
The value for the attribute "attribute_name" in the "event_type" event type defined in the "plug-in_name" event provider must not exceed "max" characters. - AWSWUI - Dynamic Workload Console messages
This section lists error and warning messages that could be issued. - AWSWUI1010E
Cannot create log. "VALUE_0" is not supported. - AWSZAP - Action plug-in for z/OS messages
This section lists error and warning messages that might be issued by the action plug-in for z/OS component. - AWSZAP002E
Submission of job stream "job_stream_name" was not successful.Reason: "reason" - AWSZAP003E
The parameter value "parameter_value" is not in the correct format of: key=value. - AWSZAP004E
The "parameter_field" "value" in the parameter "parameter_value" is not between 1 and "maximum". - AWSZAP005E
The deadline offset value "offset_value" is not in the form HHmm or between 1 and 9959. - AWSZAP006E
Triggered action "action_type" was not completed successfully. Reason: "reason" - EEL - HCL Workload Automation agent for z/OS messages
This section lists error and warning messages that might be issued by HCL Workload Automation agent for z/OS. - EELF000E
DATA ROUTER TASK HAS IGNORED AN INVALID QUEUE ELEMENT: DQE. - EELF002E
DATA ROUTER TASK INITIALIZATION FAILED. - EELF004E
DATA ROUTER TASK ABENDED WHEN PROCESSING THE FOLLOWING QUEUE ELEMENT DQE. - EELF005E
DATA ROUTER TASK QUEUE POINTERS ARE DESTROYED, RTRQ IS LOST. - EELF017E
THE HTTP CLIENT TASK QUEUE IS FULL. NO EVENTS WILL BE SENT TO SERVER. - EELF018E
DATA ROUTER TASK HAS IGNORED THE FOLLOWING DQE ELEMENT BECAUSE IT CONTAINS INVALID DATA: DQE. - EELH003E
SEND GENERIC ALERT TO NETVIEW FAILED WITH RC=RC - EELHM21E
APPLICATION NAME NOT VALID. - EELHM22E
MISSING PARAMETER. - EELHM23E
INCORRECT PARAMETER. - EELHM24E
GENERIC ERROR. - EELHM25E
JOB LOG NOT AVAILABLE. - EELHM27E
INCORRECT JCL MEMBER NAME OR DATA SET NAME. - EELHM28E
JCL TOO LONG. - EELHT03E
THE HTTP CLIENT COMMUNICATION TASK FAILED TO INITIALIZE THE C PROCESS. - EELHT04E
THE HTTP CLIENT COMMUNICATION TASK HAS ENDED BECAUSE NO HTTP OR HTTPS DESTINATIONS ARE DEFINED. - EELHT05E
THE HTTP CLIENT COMMUNICATION TASK HAS IGNORED THE FOLLOWING QUEUE ELEMENT: DQE. - EELHT06E
A SEVERE ERROR IN THE HTTP CLIENT COMMUNICATION TASK HAS CAUSED ONE OR MORE REQUESTS TO BE LOST. - EELHT07E
THE HTTP CLIENT COMMUNICATION TASK ABENDED WHILE PROCESSING THE FOLLOWING REQUEST: DQE. - EELHT13E
THE HTTP SERVER COMMUNICATION TASK FAILED TO INITIALIZE THE C PROCESS. - EELHT14E
THE HTTP SERVER COMMUNICATION TASK HAS ENDED BECAUSE NO HTTP OR HTTPS DESTINATIONS ARE DEFINED. - EELHT15E
THE HTTP CLIENT FAILED TO PROCESS A REQUEST FOR BROKER. - EELHT16W
THE HTTP CLIENT FAILED TO SET THE TCP/IP JOB NAME TO TCPNAME. THE DEFAULT TCPIP HAS BEEN USED. - EELHT17W
THE HTTP SERVER FAILED TO SET THE TCP/IP JOB NAME TO TCPNAME. THE DEFAULT TCPIP HAS BEEN USED. - EELHT20E
THE HTTP SERVER WAS UNABLE TO OPEN THE EVENT DATA SET WITH DDNAME EELHTDS. - EELHT21E
THE HTTP SERVER OUTPUT DATA SET IS TOO SMALL. - EELHT25E
THE HTTP SERVER FAILED TO BIND ON PORT PORT. ERROR: ERRNO. - EELHT26E
THE HTTP SERVER IS NOT LISTENING ON SSL PORT PORT BECAUSE IT FAILED TO INITIALIZE THE SSL CONTEXT. ERROR: SSL_ERR. - EELHT27E
THE HTTP SERVER FAILED TO ACCEPT A NEW CONNECTION. ERROR: ERRNO. - EELHT29E
THE HTTP SERVER FAILED TO INITIALIZE THE SSL CONTEXT FOR A NEW CONNECTION. ERROR: SSL_ERR. - EELHT30E
THE HTTP SERVER FAILED TO RECEIVE DATA ON A SOCKET. ERROR: ERRNO. - EELHT31E
THE HTTP SERVER FAILED TO MANAGE A STATUS CHANGE REQUEST. - EELHT32E
THE HTTP SERVER FAILED TO SEND DATA ON A SOCKET. ERROR: ERRNO. - EELHT34E
ERROR RESERVING A BLOCK OF STORAGE OF N BYTES. MODULE: MODULE - LINE: LINE. - EELHT39E
ERROR CONVERTING CHARACTERS. MODULE MODULE - LINE: LINE. ERR_STRING - EELHT40E
EVENT DATASET ERROR: HTTP SERVER COMMUNICATION TASK HAS ENDED. - EELHT46E
THE HTTP SERVER RECEIVED A JOB NOTIFICATION MESSAGE WITH NO VALUE SPECIFIED FOR THE PARM PARAMETER - EELHT64W
A REQUEST WITH AN UNSUPPORTED JOB STREAM NAME WAS RECEIVED. THE REQUEST WAS DISCARDED. - EELIT01E
THE TDWBHOSTNAME PARAMETER FOR THE Dynamic Workload Console HOSTNAME IS MISSING. THE PARAMETER IS MANDATORY. - EELIT02E
SSLKEYRING SSL key ring parameter is missing. The SSL key ring parameter is mandatory when SSL is activated. - EELIT03E
SSLKEYRINGPSW SSL key ring psw parameter is missing. The SSL key ring psw parameter is mandatory when SSL is activated and the key ring file is a key database USS file. - EELMH13E
THE MONITORING TASK WAS UNABLE TO OPEN DATASET WITH DDNAME DDNAME - EELSU03E
THE SUBMIT TASK HAS ENDED DUE TO PROCESSING ERRORS - EELSU04E
THE SUBMIT TASK INITIALIZATION FAILED, THE TASK IS TERMINATED - EELSU05E
THE INTERNAL READER FILE, DDNAME = EELBRDS, COULD NOT BE OPENED - EELSU06E
A SEVERE ERROR IN THE SUBMIT TASK HAS CAUSED ONE OR MORE REQUESTS TO BE LOST - EELSU07E
THE SUBMIT TASK ABENDED WHILE PROCESSING THE FOLLOWING REQUEST: REQUEST - EELSU09W
JOB JOBNAME(JOBNUM) COULD NOT BE RELEASED. REPEATED RETRIES HAVE FAILED. JOB NAME IS: JOBALIAS - EELSU10E
JOB JOBNAME COULD NOT BE SUBMITTED BECAUSE THE SUBMIT EXIT RETURNED A SUBMITTING USER ID, USER, WHOSE AUTHORITY COULD NOT BE DETERMINED. JOB NAME IS: JOBALIAS - EELSU11W
DDNAME EELEVDS IS MISSING OR SPECIFIES DD DUMMY - EELSU13E
THE STARTED TASK FILE, DDNAME = EELSTC, COULD NOT BE OPENED FOR OUTPUT - EELSU14W
THE SUBMIT TASK IS IN TERMINATION PHASE, JOB JOBNAME (JOBNUM) COULD NOT BE RELEASED - EELSU20E
UNABLE TO READ EELEVDS HEADER RECORD FOR REQUEST TYPE DQETYPE. - EELSU21E
UNABLE TO UPDATE EELEVDS HEADER RECORD FOR REQUEST TYPE DQETYPE. - EELSU22E
UNABLE TO ACCESS THE EELEVDS FILE FOR REQUEST TYPE DQETYPE. - EELSU23E
NO FREE SPACE IN EELEVDS HEADER RECORD FOR REQUEST TYPE DQETYPE. - EELSU24W
WORKSTATION IS NOT PRESENT IN THE EELEVDS HEADER RECORD - EELSU25E
SUBMISSION CANNOT BE EXECUTED BECAUSE THE SUBMISSION SEQUENCE NUMBER SSEQ IS NOT A SUCCESSOR OF THE EVTSSEQ SEQUENCE NUMBER. THE JOB NAME IS JOBALIAS. - EELSU30W
JOB CARD NOT FOUND OR INVALID. SPIN PREVENTION NOT POSSIBLE FOR: TYPJOB NAME. JOB NAME IS: JOBALIAS - EELSU32W
GETMAIN FAILED. SPIN PREVENTION NOT POSSIBLE FOR TYPJOB NAME. JOB NAME IS: JOBALIAS - EELSU33W
TAILORING FAILURE. SPIN PREVENTION NOT POSSIBLE FOR: TYPJOB NAME. JOB NAME IS: JOBALIAS - EELSU34E
JOB CARD NOT FOUND OR INVALID. SCHEDULING ENVIRONMENT TAILORING NOT POSSIBLE FOR: TYPJOB NAME. JOB NAME IS: JOBALIAS - EELSU35W
SCHEDULING ENVIRONMENT SCHE NOT AVAILABLE FOR JOB: NAME IN JPLEX. JOB NAME IS: JOBALIAS - EELSU36W
SCHEDULING ENVIRONMENT SCHE NOT DEFINED FOR JOB: NAME. JOB NAME IS: JOBALIAS - EELSU37E
SCHEDULING ENVIRONMENT SCHE CHECK FAILED FOR JOB: NAME. JOB NAME IS: JOBALIAS - EELSU38E
GETMAIN FAILED: TAILORING OF SCHEDULING ENVIRONMENT SCHE CHECK NOT POSSIBLE FOR JOB: NAME. JOB NAME IS: JOBALIAS - EELSU39E
TAILORING OF SCHEDULING ENVIRONMENT SCHE FAILED FOR JOB: NAME. JOB NAME IS: JOBALIAS - EELW012E
THE EVENT WRITER TERMINATED BECAUSE OF UNRECOVERABLE ERRORS - EELW016E
AN UNRECOVERABLE I/O ERROR OCCURRED. SYNAD MESSAGE FOLLOWS: SYNMSG - EELW017E
THE EVENT WRITER WAS UNABLE TO OPEN THE EVENT DATA SET - EELW021E
THE EVENT WRITER OUTPUT DATA SET IS TOO SMALL - EELW024E
THE EVENT WRITER ABENDED WHILE PROCESSING THE FOLLOWING EXIT RECORD: EXITREC - EELW025W
THE EVENT WRITER HAS IGNORED THE FOLLOWING INVALID EXIT RECORD: EXITREC - EELW044E
UNEXPECTED ERROR SUBMITTING JOB JOBNAME TO THE JES INTERNAL READER - EELW046E
SEQUENCE NUMBER SEQNO IS ALREADY IN USE BY AN EVENT READER SUBTASK - EELW048E
THE EVENT FILTERING EXIT, EELUX004, ABENDED AND HAS BEEN DISABLED - EELW049E
UNABLE TO FORMAT DATA SET WITH DDNAME DDNAME BECAUSE THE DATA SET IS NOT A SINGLE EXTENT, DISK RESIDENT, DATA SET - EELW052E
THE EVENT DATASET, DDNAME DDNAME, LRECL BLKSZ IS INVALIDLY DEFINED. DATASET IS NOT USABLE - EELW061W
THE EVENT FILTERING EXIT LOAD MODULE, MODULE, COULD NOT BE LOADED - EELW062E
EVENT WRITER INITIALIZATION FAILED - EELW067E
A SEVERE ERROR IN THE EVENT WRITER HAS CAUSED LOSS OF CSA EVENT BUFFERS - EELW075W
THE HEADER RECORD IN FILE DDNAME IS INCOMPATIBLE WITH THE DEVICE TYPE - EELW076W
NO SERVER PULSE. EVENT WRITER WILL STOP PULSE DETECTION - EELW520E
JOB COULD NOT BE SUBMITTED BECAUSE THE JOB CARD IS NOT TERMINATED CORRECTLY. THE JOB NAME IS: JOBALIAS - EELW521E
JOB COULD NOT BE SUBMITTED BECAUSE THE JOB CARD ACCOUNT PARAMETER IS NOT TERMINATED CORRECTLY. THE JOB NAME IS: JOBALIAS - EELW522E
JOB COULD NOT BE SUBMITTED BECAUSE THE JOB CARD PROGRAMMER NAME IS TOO LONG (MAX 19 CHARS). THE JOB NAME IS: JOBALIAS - EELW523E
JOB COULD NOT BE SUBMITTED BECAUSE THE JOB CARD PROGRAMMER NAME IS NOT TERMINATED CORRECTLY. THE JOB NAME IS: JOBALIAS - EELW524E
JOB NAME COULD NOT BE SUBMITTED BECAUSE THE JOB CARD JOB NAME PARAMETER CONTAINS INVALID CHARACTERS. THE JOB NAME IS: JOBALIAS - EELW525E
JOB COULD NOT BE SUBMITTED BECAUSE OF AN ERROR IN THE JOB CARD. THE JOB NAME IS: JOBALIAS - EELW526E
JOB COULD NOT BE SUBMITTED BECAUSE NO JOB CARD COULD BE FOUND. THE JOB NAME IS: JOBALIAS - EELW527E
JOB NAME COULD NOT BE SUBMITTED BECAUSE THE JOB CARD ACCOUNT INFORMATION PARAMETER HAS THE LAST CHARACTER IN COLUMN 71. THE JOB NAME IS: JOBALIAS - EELW528E
JOB NAME COULD NOT BE SUBMITTED BECAUSE THE JOB CARD ACCOUNT INFORMATION HAS A CHARACTER IN COLUMN 72. THE JOB NAME IS: JOBALIAS - EELW766W
THE EVENT CREATION ROUTINE DETECTED THAT THE JES2 EXIT7 (EELEXIT) IS ON A LOWER RDMID LEVEL THAN THE SCHEDULER SUBSYSTEM MODULE EELZEV2X - EELW773W
THE EVENT CREATION ROUTINE DETECTED THAT JES2 EXIT51 (EELEXIT) IS ON A LOWER RMID LEVEL EXITL THAN THE SCHEDULER SUBSYSTEM MODULE EELZEV2Y WHOSE LEVEL IS J2LVL - EELW774W
THE EVENT CREATION ROUTINE DETECTED THAT JES2 EXIT51 (EELEXIT) IS ON A HIGHER RMID LEVEL EXITL THAN THE SCHEDULER SUBSYSTEM MODULE EELZEV2Y WHOSE LEVEL IS J2LVL - EELW777W
THE EVENT CREATION ROUTINE DETECTED THAT THE JES2 EXIT7 (EELEXIT) IS ON A HIGHER RMID LEVEL (EXITL) THAN THE SCHEDULER SUBSYSTEM MODULE EELZEV2X WHOSE LEVEL IS J2LVL - EELZ001E
JES IS NOT ACTIVE. THE SCHEDULER CANNOT START - EELZ002E
THE EELSSCMJ TIVOLI WORKLOAD SCHEDULER SUBSYSTEM IS ALREADY ACTIVE. IT CANNOT START AGAIN. - EELZ003E
INVALID JOBNAME JOBNAME. NAME MUST BE 4 CHARACTERS OR LESS - EELZ004E
UNABLE TO ATTACH SUBTASK SUBTASK - EELZ007E
JOBNAME JOBNAME IS NOT A VALID SUBSYSTEM NAME - EELZ008E
THE INITIALIZATION PROGRAM, EELINITJ, HAS NOT BEEN SUCCESSFULLY EXECUTED. THE PRODUCT SUBSYSTEM IS UNABLE TO START. - EELZ010E
MEMBER MEMBER CANNOT BE FOUND IN PARAMETER LIBRARY - EELZ011E
PARAMETER LIBRARY MEMBER MEMBER IS EMPTY - EELZ012E
I/O ERROR READING PARAMETER LIBRARY MEMBER MEMBER - EELZ018E
INITIALIZATION STATEMENT SPECIFICATION IS LONGER THAN 455 RECORDS - EELZ022W
THE SSCM LOAD MODULE SPECIFIED, SSCM, COULD NOT BE LOADED - EELZ023W
THE SSCMNAME LOAD MODULE SPECIFIED, SSCM, IS NOT VALID - EELZ030E
THE AGENT WAS UNABLE TO OPEN THE MESSAGE LOG DATA SET. - EELZ031E
THE AGENT WAS UNABLE TO OPEN THE MESSAGE LIBRARY FILE. - EELZ032E
SIZE OF AGENT MESSAGE LIBRARY RECORDS MUST BE 80 BYTES - EELZ033E
THE AGENT IS ENDING. MESSAGE ROUTINE COULD NOT BE INITIALIZED - EELZ035E
MAXIMUM QUEUE SIZE (MAXNUM) WAS REACHED ON THE QNAME QUEUE. NUMLOST EVENTS HAVE BEEN LOST - EELZ036E
ERROR RETRIEVING INFORMATION FOR DDNAME = DDNAME DYNALLOC RETCODE = RC, INFO CODE = INFO, REASON CODE = RSN - EELZ037E
A REQUIRED DD-CARD IS MISSING. DDNAME = DDNAME - EELZ039E
DATA SET CONFLICT. THE DATA SET DEFINED BY DDNAME DDNAME IS USED BY ANOTHER PRODUCT SYSTEM. DSNAME IS DSNAME - EELZ045E
SUBTASK SUBTASK ENDED UNEXPECTEDLY - EELZ049W
AN INCORRECT MODIFY COMMAND HAS BEEN IGNORED. MODIFY SSNAME,FPARAM - EELZ050W
THE PRODUCT SUBSYSTEM HAS BEEN CANCELLED - EELZ051E
THE PRODUCT SUBSYSTEM MOTHER TASK HAS ABENDED - EELZ052E
THE PARAMETER LIBRARY FILE, DDNAME = EELPARM OR DDNAME = EELYPARM, COULD NOT BE OPENED. - EELZ053E
LOGICAL RECORD SIZE FOR THE PARAMETER LIBRARY, DDNAME EELPARM, IS NOT VALID - EELZ054E
ERRORS DETECTED PROCESSING PRODUCT PARAMETERS. THE SCHEDULER IS ENDING - EELZ058E
THE BEX INTERFACE MODULE, EELBEX, COULD NOT BE LOADED - EELZ062W
THE START/STOP USER EXIT MODULE COULD NOT BE LOADED - EELZ066W
THE SCHEDULER HAS NOT BEEN ABLE TO DETERMINE THE JES TYPE. JES2 IS ASSUMED. - EELZ067E
COMMAND SYNTAX ERROR: CARD FURTHER STATEMENT PROCESSING STOPPED - EELZ068E
CMD IS AN UNKNOWN COMMAND AND WILL NOT BE PROCESSED FURTHER STATEMENT PROCESSING IS STOPPED - EELZ070E
THE SSCMNAME KEYWORD SPECIFIES AN OPTION THAT IS NOT RECOGNIZED - EELZ071E
OPTION PERMANENT FOR THE SSCMNAME KEYWORD REQUIRES THE BUILDSSX KEYWORD - EELZ072W
OPTION PERMANENT FOR THE SSCMNAME KEYWORD REQUIRES STEPLIB DD-STATEMENT - EELZ074W
THE SCHEDULER HAS NOT BEEN ABLE TO DETERMINE NJE NODE NAME FOR THIS SYSTEM - EELZ075W
THE JES2 COMMAND CHARACTER MAY BE INCORRECT - EELZ096W
OBSOLETE PARAMETER SPECIFIED:keyword. THE PARAMETER IS IGNORED - EELZ097W
OBJ LOAD MODULE COULD NOT BE LOADED - EELZ106W
PERCENT % OF QUEUE QNAME IN USE - EELZ125E
CANNOT CONTINUE PROCESSING DUE TO FULL QUEUE: QNAME THE SUBSYSTEM IS TERMINATING - EELZ132W
THE FOLLOWING INBOUND QUEUE ELEMENT HAS BEEN DISCARDED DUE TO MISSING EXTENSION BUFFER SEGMENTS: DQE - EELZ133W
THE FOLLOWING INBOUND QUEUE ELEMENT WITH MISSING EXTENSION BUFFER SEGMENTS HAS BEEN DISCARDED DUE TO DATA ROUTER TERMINATION: DQE - EELZ140E
YEAR, MONTH, AND DAY MUST ALL BE TWO-DIGIT NUMBERS - EELZ141E
YEAR MUST BE IN THE RANGE 00 TO 99 - EELZ142E
MONTH MUST BE IN THE RANGE 1 TO 12 - EELZ143E
DAY MUST BE IN THE RANGE 1 TO 31 - EELZ144E
DAY DD IS NOT VALID IN FEBRUARY - EELZ145E
MONTH MM DOES NOT HAVE 31 DAYS - EELZ146E
YEAR YY DOES NOT HAVE 29 DAYS IN FEBRUARY - EELZ147E
HOUR AND MINUTE MUST BOTH BE TWO-DIGIT NUMBERS - EELZ148E
HOUR MUST BE IN THE RANGE 0 TO 23 - EELZ149E
MINUTE MUST BE IN THE RANGE 0 TO 59 - EELZ170E
CODE LEVEL VERIFICATION FAILED CODE LEVEL OF THE SSX CONTROL BLOCK IS SSXLEV CODE LEVEL OF THE EELMAJOR MODULE IS MCALEV CODE LEVEL OF THE SSCM MODULE IS SSCMLEV - EELZ171E
MERGE PARAMETER IS NOT SUPPORTED. OLD SSX AND NEW SSX ARE NOT FOR THE SAME FMID CODE LEVEL OF THE NEW SSX CONTROL BLOCK IS SSXLEV CODE LEVEL OF THE OLD SSX CONTROL BLOCK IS OLDLEV - EELZ174W
OLD AND NEW SSX CONTROL BLOCK ARE ON THE SAME LEVEL, SSXLEV - EELZ182E
SUBSTRING EXCEEDS BOUNDS OR LENGTH ZERO WAS FOUND IN PARMREC - EELZ183E
UNEXPECTED ERROR DURING SYMBOL SUBSTITUTION - EELZ188E
UNEXPECTED RETURN CODE DURING SYMBOL SUBSTITUTION - EELZ190E
THE FMID FILEFMID OF DATASET FILENAME DOES NOT MATCH CODE FMID TWSFMID - EELZ192E
THE VERSION FILEVER OF DATASET FILENAME DOESN'T MATCH CODE VERSION TWSVER - EELZ213W
THE THRESHOLD MUST BE IN THE RANGE FROM 0 TO 100 - EELZ215E
WLM SCHEDULING ENVIRONMENT DEFINITIONS COULD NOT BE DETERMINED. RETURN CODE: RETC REASON CODE: RSNC - EELZ246E
CODEPAGE KEYWORD IS NOT PRESENT IN TWSOPTS STATEMENT. THIS KEYWORD IS MANDATORY. - EELZ247E
CODEPAGE KEYWORD DOES NOT HAVE A VALID VALUE. - EELZ250W
KEYWORD KEYWD IN STATEMENT STMT IS NOT VALID. THE VALUE IS OUTSIDE THE VALID RANGE. WILL USE DEFAULT DEFAULT. - EELZ263W
COMMAND IS NOT VALID ON AGENT. - EELZ410W
PARAMETER KEYWORD IGNORED. NOT USABLE FOR THIS AGENT TYPE.