Unable to sign on to the topology server.
User name: name.
Reason: User name and password not authorized to connect to the
topology server.
Explanation: The specified user name is not defined to the server, or the password is incorrect for the user name.
Message Inserts:
System Action: The program ends.
User Response: Correct the user name or the password.
Unable to sign on to the topology server.
Reason: Unable to communicate with host NetView.
Explanation: The topology server is unable to communicate with host NetView.
System Action: The program ends.
User Response: Ensure that the communications session between the topology server and host NetView is started. If necessary, issue the host NetView command NETCONV to establish the session.
Unable to sign on to the topology server.
User name: name
Explanation: An error occurred when you signed on to the topology server, but the specific reason cannot be determined.
Message Inserts:
System Action: The program ends.
User Response: Save the topology server error log file. The file name is defined by the EGVERRORFILE in the CONFIG.SYS file. Contact the IBM Support Center for assistance in examining this file.
Unable to sign on to the topology server.
Reason: Versions are not compatible.
Explanation: The version of the topology server is not compatible with this version of the command profile editor.
System Action: The program ends.
User Response: Ensure that the topology server and the command profile editor are running the same versions.
Unable to sign on to the topology server.
Reason: User name name already signed on to command
profile editor.
Explanation: The user specified in name is already signed on to the command profile editor. Only one user may be signed on to the command profile editor at a time.
Message Inserts:
System Action: The program ends.
User Response: Wait until the instance currently running ends, and then try to sign on again.
Unable to sign on the topology server.
Reason: The topology server is not available.
Explanation: This message is issued when the topology server does not reply at the given IP host name or address.
System Action: The program ends.
User Response: Contact the IBM Support Center.
The connection to the topology server has been lost.
Explanation: The command profile editor has lost connectivity with the topology server.
System Action: The command profile editor cannot continue to operate without the services of the topology server. The command profile editor program ends.
User Response: Note any other messages and see the "Diagnosis Guide" for more information regarding this error.
The topology server has not responded within the expected time period.
Explanation: The topology server failed to respond to a request from the command profile editor.
System Action: The command profile editor ends.
User Response: Contact the IBM Support Center.
The command indicator name cannot be deleted because it is in use by the following commands: commands
Explanation: Each command set name must be unique. During the creation of a new command set or the update of an existing command set, a name was entered that was already in use.
Message Inserts:
System Action: The command indicator description is reset to its original text.
User Response: If the command indicator must be deleted, first remove it from each command that is using it.
Unable to run the command profile editor. The command profile editor is already in use.
Explanation: Only one instance of the command profile editor can be run at one time.
System Action: The program ends.
User Response: Wait until the instance currently running ends, and then try to sign on again.
Unable to sign on to the topology server while view conversion is in progress.
Explanation: The topology server is currently converting views. A sign on is not allowed at this time.
System Action: The program ends.
User Response: Wait until topology server has completed converting views, and then try to sign on again.
A command set cannot contain itself.
Explanation: You attempted to include a command set inside itself.
System Action: The addition is ignored.
Removal of object name failed - not found in the command set or profile.
Message Inserts:
Explanation: The object specified was not removed.
System Action: The program continues processing the response file and updates the command database.
User Response: If the object to be removed is incorrect, update the response file with the correct information and run the utility again. Otherwise, no action is required.
An internal error has occurred.
Function: function
Line: line
Exception Name: exception name
Error ID: errorid
Explanation: Each command profile must have a unique name. The name of the command profile being created or updated is already in use.
Message Inserts:
System Action: The program ends.
User Response: Copy the information from the message and save a copy of the error log. The error log is specified in the CONFIG.SYS file in the EXQERRORFILE line. Contact the IBM support center.
Unexpected system error has occurred. See log log file for more information.
Explanation: An unexpected system error was encountered. The error log file will contain additional information, such as the system call that failed and the return code.
Message Inserts:
System Action: The program ends.
User Response: Examine the error log file to determine the cause of the system error. If the cause of the system error cannot be determined or corrected, save the log file and contact the IBM support center.
Response file response file has one or more syntax errors. See log log file for more information.
Explanation: The response file contains one or more syntax errors. The error log file lists each of the errors along with the line numbers in the response file where each was found.
Message Inserts:
System Action: The program ends.
User Response: Examine the error log file and correct each response file syntax error listed. Run the utility again with the modified response file.
Response file response file could not be generated. Possible disk write failure.
Explanation: An attempt to write the response file to the disk failed.
Message Inserts:
System Action: The program ends.
User Response: Ensure that enough free disk space exists to generate the response file. Run the utility again.
Response file response file could not be processed successfully. See log log file for more information.
Explanation: The response file contains errors which prevent the utility from properly updating the command database. These errors are listed in the error log file.
Message Inserts:
System Action: The program ends.
User Response: Examine the error log file and correct each response file error listed. Run the utility again with the modified response file.
Unable to open file file name.
Explanation: A file could not be opened for one of the following reasons:
Message Inserts:
System Action: The program ends.
User Response: Ensure that the path and file name are correctly specified on the command line. Ensure that the file is not being used by another process and is not protected. Examine the error log file for any system errors that might have been logged.
DOS error encountered, function=function, rc = rcode, file = file name, line = line.
Explanation: A DOS error was encountered while processing the response file.
Message Inserts:
System Action: The program ends.
User Response: If the cause of the error cannot be determined, contact the IBM support center.
Utility started processing response file response file on date at time
Explanation: This message marks the date and time when the utility began processing or generating a response file.
Message Inserts:
System Action: The program continues running.
User Response: None
Utility completed processing on date at time.
Explanation: This message marks the date and time when the utility ended.
Message Inserts:
System Action: The program ends.
User Response: None
Out of memory.
Explanation: There is not enough memory to run the utility program.
System Action: The program ends.
User Response: Stop any unnecessary processes to make more memory available. Run the utility again.
Invalid file specification file name.
Explanation: The path, file name, or both are incorrectly specified on the command line.
Message Inserts:
System Action: The program ends.
User Response: Ensure that the path and file name are correctly specified on the command line.
Duplicate parameter parameter.
Explanation: A command line parameter was specified more than once.
Message Inserts:
System Action: The program ends.
User Response: Run the utility again without the duplicate parameter.
The parameter1 and parameter2 parameters are mutually exclusive.
Explanation: Only one of the two listed command line parameters can be used in a single invocation of the utility program.
Message Inserts:
System Action: The program ends.
User Response: Refer to the syntax of the cpebatch command to determine which of the two parameters is required for the task. Run the utility again.
No input response file specified.
Explanation: The /I parameter was specified on the command line, but no response file name was specified.
System Action: The program ends.
User Response: Run the utility again with a valid response file path and name. See the syntax of the cpebatch command for more information.
Parameter parameter has invalid value value.
Explanation: A command line parameter has an incorrect value.
Message Inserts:
System Action: The program ends.
User Response: Refer to the syntax of the cpebatch command to determine the correct value for the parameter. Run the utility again.
Unknown parameter parameter.
Explanation: An unrecognized command line parameter was specified.
Message Inserts:
System Action: The program ends.
User Response: Refer to the syntax of the cpebatch command to determine the correct parameter. Run the utility again.
Missing parameter parameter.
Explanation: A required command line parameter is missing.
Message Inserts:
System Action: The program ends.
User Response: Refer to the syntax of the cpebatch command to determine the required parameter. Run the utility again.
Unable to locate response file response file.
Explanation: The input response file was not found in the specified path.
Message Inserts:
System Action: The program ends.
User Response: Ensure that the path and file name are correctly specified on the command line. Run the utility again.
Unmatched parenthesis detected in response file response file.
Explanation: The input response file has an unmatched parenthesis.
Message Inserts:
System Action: The program ends.
User Response: Determine the location of the unmatched parenthesis in the response file and correct the problem. Run the utility again with the modified response file.
Invalid keyword keyword.
Explanation: A keyword in the response file is unrecognized or contains an incorrect character.
Message Inserts:
System Action: The program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Correct the keyword, then run the utility again with the modified response file.
Unmatched right parenthesis.
Explanation: A right parenthesis does not have a corresponding left parenthesis.
System Action: The program ends.
User Response: Match the parenthesis, then run the utility again with the modified response file.
Line is too long.
Explanation: A line in the response file is too long.
System Action: The program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Shorten the line or, if possible, break it into multiple statements. Run the utility again with the modified response file.
Keyword keyword used improperly.
Explanation: A keyword is improperly used if the keyword is one of the following:
Message Inserts:
System Action: The program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Correct the keyword, then run the utility again with the modified response file.
Duplicate keyword keyword is not allowed.
Explanation: A keyword was encountered that is already in use.
Message Inserts:
System Action: The program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Remove the duplicate keyword, then run the utility again with the modified response file.
Required keyword keyword missing in stanza stanza.
Explanation: A stanza is missing a required keyword.
Message Inserts:
System Action: The program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Add the required keyword to the stanza, then run the utility again with the modified response file.
Keyword keyword does not belong in stanza stanza.
Explanation: A stanza contains a keyword that does not belong there.
Message Inserts:
System Action: The program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Remove the keyword from the stanza, then run the utility again with the modified response file.
Object object name is incomplete.
Explanation: An object being added to the command database with incomplete information.
Message Inserts:
System Action: The program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Ensure that the object has all required keywords correctly specified. Run the utility again with the modified response file.
Update is not allowed. Use /M option.
Explanation: The response file will cause the utility program to modify or delete existing information in the current command database. The /M option must be used to alter the database in this way.
System Action: The program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Run the utility again with the /M option.
Delete of object name failed.
Explanation: The DELETE keyword is improperly used to delete an object that was not found in a folder.
Message Inserts:
System Action: The program continues processing the response file and updates the command database.
User Response: If the object to be deleted is incorrect, update the response file with the correct information and run the utility again. Otherwise, no action is required.
Undefined object object name referenced.
Explanation: An object references another object which has not yet been defined.
Message Inserts:
System Action: The program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Ensure that the referenced object is defined before the current object in the response file. Run the utility again with the modified response file.
Field field name has invalid value value.
Explanation: An attempt to set a field was not successful because the value is incorrect. The value is incorrect for one of the following reasons:
Message Inserts:
System Action: If this message occurs while running the utility program, the program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Correct the field value. If this message occurs while running the utility program, run the utility again with the modified response file.
Field field name has too long a value.
Explanation: An attempt to set a field was unsuccessful because the value exceeds the maximum length for that field.
Message Inserts:
System Action: The program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Shorten the length of the field value, then run the utility again with the modified response file.
An object type with name object name already exists.
Explanation: An attempt to add an object to a menu was unsuccessful because the menu already contains that object.
Message Inserts:
System Action: If this message occurs while running the utility program, the program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: If this message occurs while running the utility program, remove the duplicate object from the MENU stanza, then run the utility again with the modified response file.
Field field name value value is out of range.
Explanation: An attempt to set a field was unsuccessful because the value is beyond the acceptable range of values.
Message Inserts:
System Action: The program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Correct the field value, then run the utility again with the modified response file.
Field field value value is not contiguous.
Explanation: An attempt to set a field was unsuccessful because the field value is not contiguous with existing values.
Message Inserts:
System Action: If this message occurs while running the utility program, the program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: If this message occurs while running the utility program, make the value contiguous, then run the utility again with the modified response file.
Keyword field name has already been set.
Explanation: A field which can only be set once has already been set.
Message Inserts:
System Action: The program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Remove the field from the stanza, then run the utility again with the modified response file.
Field field name value value is already being used.
Explanation: An attempt to set a field was unsuccessful because the same value is used elsewhere.
Message Inserts:
System Action: The program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Change the value to one that is unique, then run the utility again with the modified response file.
Add of object object name failed - folder is full.
Explanation: An attempt to add an object to a folder failed because the folder contains the maximum number of objects.
Message Inserts:
System Action: If this message occurs while running the utility program, the program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Remove unneeded objects from the folder, then try to add the new object.
Add of object object name failed - invalid position.
Explanation: An attempt to add an object to a menu was unsuccessful because it is being added at an incorrect position. This is an internal error.
Message Inserts:
System Action: The program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Contact the IBM support center.
Delete of object manager name failed - manager in use by the following commands: command list.
Explanation: The manager cannot be deleted because it is used by one or more commands.
Message Inserts:
System Action: If this message occurs while running the utility program, the program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Remove the dependency of each of the listed commands before deleting each of them.
Delete of command command name failed - command in use by the following profiles or command sets: object list.
Explanation: The command cannot be deleted because it is used by one or more profiles or command sets.
Message Inserts:
System Action: If this message occurs while running the utility program, the program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Remove the dependency of each of the listed profiles or command sets before deleting each of them.
Delete of profile profile name failed - profile in use by the following operators: operator list.
Explanation: The profile cannot be deleted because it is used by one or more operators.
Message Inserts:
System Action: If this message occurs while running the utility program, the program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Remove the dependency of each of the listed operators before deleting each of them.
Delete of command set command set name failed - command set in use by the following profiles: profile list.
Explanation: The command set cannot be deleted because it is used by one or more profiles.
Message Inserts:
System Action: If this message occurs while running the utility program, the program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Remove the dependency of each of the listed profiles on the command set before deleting each of them.
Field field name cannot be set - manager undefined.
Explanation: An attempt to set a field was unsuccessful because it references an undefined manager.
Message Inserts:
System Action: The program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Ensure that the referenced manager is defined earlier in the response file, then run the utility again with the modified response file.
Field field name cannot be set - command is resource independent.
Explanation: An attempt to set PAGE_ID or INDICATOR_LIST on a command page was unsuccessful because the command is resource independent. A resource independent command cannot specify command indicators.
Message Inserts:
System Action: The program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Remove this field from the command page stanza, then run the utility again with the modified response file.
Field field name cannot be set - command page has defined command indicators.
Explanation: An attempt to set a field was unsuccessful because the command has specified command indicators.
Message Inserts:
System Action: The program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Remove this field from the command page stanza, then run the utility again with the modified response file.
Field field name cannot be set - command applies to any manager.
Explanation: An attempt to set PAGE_ID or INDICATOR_LIST on a command page was unsuccessful because the command page has MANAGER_NAME = ANY. A command which applies to any manager cannot specify command indicators.
Message Inserts:
System Action: The program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Remove this field from the command page stanza, then run the utility again with the modified response file.
Field field name cannot be set - any manager not allowed.
Explanation: An attempt to set MANAGER_NAME to 'ANY' on a command page was unsuccessful because the command already has pages with indicators defined.
Message Inserts:
System Action: The program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Remove all pages with defined indicators from this command, then set MANAGER_NAME to ANY. Run the utility again with the modified response file.
Field field name cannot be set - command indicator undefined.
Explanation: An attempt to add a command indicator to a command page was unsuccessful because the command indicator is undefined.
Message Inserts:
System Action: The program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Define the command indicator to a manager in the response file, then run the utility again with the modified response file.
Unknown error.
Explanation: An unknown error was encountered. This is an internal error.
System Action: If this message occurs while running the utility program, the program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Contact the IBM support center.
The topology server has encountered an internal error.
Explanation: The topology server notified the command profile editor of an internal error in the server.
System Action: The command profile editor closes without saving any changes to your data.
User Response: See the "Diagnosis Guide" for more information regarding this error. Contact the IBM Support Center for further assistance.
Field field name has duplicate value value in the following profiles or command sets: object list.
Explanation: The listed fields have identical values. The values must be unique.
Message Inserts:
System Action: If this message occurs while running the utility program, the program continues processing the response file to find other possible errors, then ends without changing the command database.
User Response: Change the field to a unique value. If this message occurs while running the utility program, run the utility again with the modified response file.
object type object name has duplicate information in the following profiles or command sets: object list.
Explanation: An attempt to add a command or command set to a folder was unsuccessful because it creates duplicate information in one or more profiles or command sets.
Message Inserts:
System Action: If this message occurs while running the utility program, the program continues processing the response file and updates the command database.
User Response: None.
The resource description description is already in use for this resource manager
Explanation: Resource descriptions must be unique for each command indicator under a resource manager.
Message Inserts:
User Response: Change the resource description and run the utility again.
Field field name cannot be set to value - command indicators exist outside this boundary.
Explanation: You attempted to set a field to an incorrect value.
Message Inserts:
User Response: Correct the value.
Name or address hostname cannot be resolved to a valid IP address or an LU name.
Explanation: .
Message Inserts:
User Response: Correct the hostname.
(rc=return code)
Explanation: The Command Profile Editor utility has completed processing.
Message Inserts:
RC | Explanation |
0 | No errors. |
4 | Warning logged - processing continues and the database is updated. |
8 | Error logged - processing continues but the database is not updated. |
12 | Error logged - immediate termination. |
User Response: If there are errors, correct them and run the utility again. Check the ihsecped.log
file for more details on the errors.
Response file Response file already exists.
Explanation: The output response file already exists and will not be overwritten.
Message Inserts:
User Response: Remove the existing response file or specify a different file name for the output response file and run the utility again.
Command profile editor utility program.
usage: cpebatch filename -I | -O [-U:userID] [-P:password] [-L1:log file] [-G | -M] [-V]
Explanation: The utility was invoked without parameters or with the -? (help) parameter.
User Response: Invoke the utility using the syntax described in the message. See the syntax of the cpebatch command for more information.