Topology Server Message Help

IHS5001

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:

name
The user name entered as a command parameter or at the command prompt.

System Action: The program ends.

User Response: Correct the user name or the password.

IHS5002

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.

IHS5003

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:

name
The user name entered as a command parameter or at the command prompt.

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.

IHS5004

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.

IHS5005

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:

name
The user is already signed on to the command profile editor.

System Action: The program ends.

User Response: Wait until the instance currently running ends, and then try to sign on again.

IHS5006

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.

IHS5008

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.

IHS5011

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.

IHS5013

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:

name
The name of command set being used.
commands
The commands using the current command indicator.

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.

IHS5015

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.

IHS5016

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.

IHS5017

A command set cannot contain itself.

Explanation: You attempted to include a command set inside itself.

System Action: The addition is ignored.

IHS5018

Removal of object name failed - not found in the command set or profile.

Message Inserts:

object name
The name of the object being removed.

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.

IHS5020

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:

function
The name of the function that caused the error.
line
The line in which the error occurred.
exception name
The name of the exception generated.
errorid
The error ID of the exception.

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.

IHS5022

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:

log file
The name of the error log file.

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.

IHS5024

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:

response file
The name of the response file.
log file
The name of the log file.

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.

IHS5025

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:

response file
The name of the response file.

System Action: The program ends.

User Response: Ensure that enough free disk space exists to generate the response file. Run the utility again.

IHS5026

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:

response file
The name of the response file being processed.
log file
The name of the error log file being processed.

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.

IHS5027

Unable to open file file name.

Explanation: A file could not be opened for one of the following reasons:

Message Inserts:

file name
The path and file name of the file to be opened.

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.

IHS5028

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:

function
The function being performed when the error occurred.
rcode
The DOS return code.
file name
The name of the response file being processed.
line
The line in the response file that was being processed when the error occurred.

System Action: The program ends.

User Response: If the cause of the error cannot be determined, contact the IBM support center.

IHS5029

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:

response file
The response file being processed.
date
The start date.
time
The start time

System Action: The program continues running.

User Response: None

IHS5030

Utility completed processing on date at time.

Explanation: This message marks the date and time when the utility ended.

Message Inserts:

date
The end date.
time
The end time.

System Action: The program ends.

User Response: None

IHS5031

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.

IHS5032

Invalid file specification file name.

Explanation: The path, file name, or both are incorrectly specified on the command line.

Message Inserts:

file name
The path and file name of the file being opened.

System Action: The program ends.

User Response: Ensure that the path and file name are correctly specified on the command line.

IHS5033

Duplicate parameter parameter.

Explanation: A command line parameter was specified more than once.

Message Inserts:

parameter
The duplicated parameter.

System Action: The program ends.

User Response: Run the utility again without the duplicate parameter.

IHS5034

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:

parameter1
The first command line parameter.
parameter2
The second command line parameter.

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.

IHS5035

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.

IHS5036

Parameter parameter has invalid value value.

Explanation: A command line parameter has an incorrect value.

Message Inserts:

parameter
The command line parameter.
value
The incorrect value of the parameter.

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.

IHS5037

Unknown parameter parameter.

Explanation: An unrecognized command line parameter was specified.

Message Inserts:

parameter
The unknown command line parameter.

System Action: The program ends.

User Response: Refer to the syntax of the cpebatch command to determine the correct parameter. Run the utility again.

IHS5038

Missing parameter parameter.

Explanation: A required command line parameter is missing.

Message Inserts:

parameter
The missing command line parameter.

System Action: The program ends.

User Response: Refer to the syntax of the cpebatch command to determine the required parameter. Run the utility again.

IHS5039

Unable to locate response file response file.

Explanation: The input response file was not found in the specified path.

Message Inserts:

response file
The input response file name.

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.

IHS5040

Unmatched parenthesis detected in response file response file.

Explanation: The input response file has an unmatched parenthesis.

Message Inserts:

response file
The input response file name.

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.

IHS5041

Invalid keyword keyword.

Explanation: A keyword in the response file is unrecognized or contains an incorrect character.

Message Inserts:

keyword
The incorrect keyword.

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.

IHS5042

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.

IHS5043

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.

IHS5044

Keyword keyword used improperly.

Explanation: A keyword is improperly used if the keyword is one of the following:

Message Inserts:

keyword
The improperly used keyword.

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.

IHS5045

Duplicate keyword keyword is not allowed.

Explanation: A keyword was encountered that is already in use.

Message Inserts:

keyword
The duplicate keyword.

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.

IHS5046

Required keyword keyword missing in stanza stanza.

Explanation: A stanza is missing a required keyword.

Message Inserts:

keyword
The required keyword.
stanza
The stanza requiring the keyword.

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.

IHS5047

Keyword keyword does not belong in stanza stanza.

Explanation: A stanza contains a keyword that does not belong there.

Message Inserts:

keyword
The incorrect keyword.

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.

IHS5048

Object object name is incomplete.

Explanation: An object being added to the command database with incomplete information.

Message Inserts:

object name
The name of the object being added.

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.

IHS5049

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.

IHS5051

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:

object name
The name of the object being deleted.

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.

IHS5052

Undefined object object name referenced.

Explanation: An object references another object which has not yet been defined.

Message Inserts:

object name
The name of the unknown object being referenced.

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.

IHS5053

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:

field name
The name of the field containing the incorrect value.
value
The incorrect value.

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.

IHS5054

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:

field name
The name of the field.

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.

IHS5055

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:

object type
The type of object being added to the menu.
object name
The name of object being added to the menu.

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.

IHS5057

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:

field name
The name of the field.
value
The incorrect value.

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.

IHS5058

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:

field name
The name of the field.
value
The incorrect value.

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.

IHS5059

Keyword field name has already been set.

Explanation: A field which can only be set once has already been set.

Message Inserts:

field name
The name of the field.

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.

IHS5060

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:

field name
The name of the field.
value
The value assigned to the field.

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.

IHS5061

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:

object name
The name of the object which cannot be added.

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.

IHS5062

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:

object name
The name of the object being added.

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.

IHS5064

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:

manager name
The name of the manager to be deleted.
command list
The list of commands using the manager.

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.

IHS5065

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:

command name
The name of the command being deleted.
object list
The list of profiles or command sets using the command.

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.

IHS5066

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:

profile name
The name of the profile being deleted.
operator list
The list of operators using the profile.

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.

IHS5067

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:

command set name
The name of the command set being deleted.
profile list
The list of profiles using the command set.

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.

IHS5068

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:

field name
The name of the field.

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.

IHS5069

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:

field name
The name of the field.

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.

IHS5070

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:

field name
The name of the field.

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.

IHS5071

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:

field name
The name of the field.

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.

IHS5072

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:

field name
The name of the field.

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.

IHS5073

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:

field name
The name of the field.

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.

IHS5074

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.

IHS5077

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.

IHS5078

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:

field name
The name of the field.
value
The duplicated value.
object list
The list of profiles or command sets.

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.

IHS5079

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:

object type
The type of object being added.
object name
The name of object being added.
object list
The list of profiles or command sets.

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.

IHS5083A

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:

description
The resource description which is not unique for this resource manager.

User Response: Change the resource description and run the utility again.

IHS5084

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:

field name
The name of the field containing the incorrect value.
value
The incorrect value.

User Response: Correct the value.

IHS5085A

Name or address hostname cannot be resolved to a valid IP address or an LU name.

Explanation: .

Message Inserts:

hostname
The invalid IP address or LU name.

User Response: Correct the hostname.

IHS5086I

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

IHS5087A

Response file Response file already exists.

Explanation: The output response file already exists and will not be overwritten.

Message Inserts:

response file
The name of the existing response file that cannot be overwritten.

User Response: Remove the existing response file or specify a different file name for the output response file and run the utility again.

IHS5088I

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.