This command is not installed at the host.
Explanation: The command issued interacts with modules on the host. Those modules could not be located.
System Action: The command is not issued.
Operator Response: Contact your system programmer.
System Programmer Response: Verify that the host NetView is at the proper level. Also, verify that the command CNMMIBBR is available on host Tivoli NetView.
SNMP is not installed on object objectname.
Explanation: A command was issued to start the MIB Browser, but the selected object does not have MIB Information defined in RODM.
Message Inserts:
System Action: The command is not issued.
Operator Response: Verify that you selected the correct object for this command and that it should have MIB information. Then, retry the command.
A message could not be delivered.
Reason: reason
Message: message
Explanation: An attempt to send a message using the Send Message dialog failed. The reason for the failure is specified in the reason message insert.
Message Inserts:
System Action: The message is not sent.
Operator Response: Verify that the operator identifier that you want to send the message to is correct and send the message again.
The requested status minutes are not valid.
Explanation: The value specified for the status minutes search criteria on the Find Advanced dialog is not valid.
System Action: None.
Operator Response: Change the status minutes search criteria and try the request again.
Error loading file filename from the server. A default set of wrappable characters will be used.
Explanation: The system could not find the specified file in the following directory:
The wraplabelbreaks.properties file defines the set of characters that is used to determine where to wrap labels.
Message Inserts:
System Action: The system uses the following default set of characters to determine where to wrap the labels:
Operator Response: Do one of the following:
System Programmer Response: Verify that the file has not been renamed. If it has not been renamed, reinstall the program.
Error attempting to launch external browser for help.
Explanation: This error occurs when the "Use my default Web browser" or the "Let me specify my own browser" command is chosen on the General tab of the Console Properties dialog, and the system encounters a problem starting the external browser.
System Action: The external browser did not start and the online help did not display.
Operator Response: Do one of the following:
System Programmer Response: Verify that the system has sufficient resources to start a program. If you cannot resolve the problem, contact IBM Customer Support.
Because this is the first instance of the component type component type in this business system, you must complete the component type settings. The Component Type Properties window will be opened for you.
Explanation: You must define each component type in a business system using the Component Type Properties window. Because this is the first instance of the specified component type you have added to this business system, the Component Type Properties window opens automatically for you.
Message Inserts:
Operator Response: Click OK to open the Component Type Properties window.
An error occurred opening the following file: file name
Explanation: An error occurred when trying to open the specified file.
Message Inserts:
System Response: The export operation terminates.
Operator Response: Verify that the file exists and can be read.
An error occurred creating the following file: file name
Explanation: An error occurred when trying to create the specified file.
Message Inserts:
System Response: The export operation terminates.
Operator Response: Verify that the specified subdirectory exists and that the user has write access to the specified subdirectory.
An error occurred deleting the following file: file name
Explanation: An error occurred when trying to delete the specified file.
Message Inserts:
System Response: The export operation terminates.
Operator Response: Verify that the specified file exists and that the user has write access to the specified subdirectory.
An error occurred closing the following file: file name
Explanation: An error occurred when trying to close the specified file.
Message Inserts:
System Response: The export operation terminates.
Operator Response: Verify that the specified subdirectory exists and that there is disk space available.
An error occurred adding the following file file name to the package file.
Explanation: An error occurred when trying to add the specified file to the package file (.pkg).
Message Inserts:
System Response: The export operation terminates.
Operator Response: Verify that there is disk space available.
An error occurred writing to the following directory: directory name.
Explanation: An error occurred when trying to write to the specified directory.
Message Inserts:
System Response: The export operation terminates.
Operator Response: Verify that the specified directory exists and that the user has write access to the specified subdirectory.
The Tivoli Module Builder or Tivoli Module Designer is already running.
Explanation: Only one instance of the Tivoli Module Builder or the Tivoli Module Designer can be launched from the Tivoli GEM Console at a time.
System Response: The Tivoli Module Builder or the Tivoli Module Designer is not launched.
Operator Response: Close the instance of the Tivoli Module Builder or the Tivoli Module Designer that is currently running.
The specified command to launch the Tivoli Module Designer is not valid.
Explanation: The Tivoli GEM Console failed to launch the Tivoli Module Designer using the command given by the user.
System Response: The Tivoli Module Designer is not launched.
Operator Response: Do the following:
The specified command to launch the Tivoli Module Builder is not valid.
Explanation: The Tivoli GEM Console failed to launch the Tivoli Module Builder using the command given by the user.
System Response: The Tivoli Module Builder is not launched.
Operator Response: Do the following:
There are no real components in the current subsystem.
Explanation: You can filter out instances of real component types from a subsystem, based on filter criteria that you specify. To use instance membership filtering, you must have at least one real component in the subsystem before you can specify the filter criteria.
Operator Response: Follow these steps:
You have requested to delete all instances of the component type type in the current view. You cannot undo this action. Do you want to continue?
Explanation: You have requested to delete all instances of the specified component type in the current view. You cannot undo this action.
Message Inserts:
Operator Response: Do one of the following:
The selected component cannot be included in an aggregate, because it has no component information tasks defined.
Explanation: To include a component in an aggregate, the component type must have component information tasks defined in the component definition file (CDF).
Operator Response: To include the component in the aggregate, do either of the following:
To define a connection, you must have two (and only two) components selected.
Note: To select multiple components, hold down the Ctrl key.
Explanation: To define a connection, you must first select two components before clicking the Connection button. To select multiple components, hold down the Ctrl key.
Operator Response: To define a connection, follow these steps:
The component component, which is an instance of the component type component type, has no connection types defined as part of its business definition.
Explanation: To define a connection between component types, the component types must have at least one connection type defined as part of their business definitions.
Message Inserts:
Operator Response: Do the following:
A connection cannot be made between the selected components, because they have no connection types in common.
Explanation: To make a connection between two components, the components must have a connection type in common.
Operator Response: To add the connection, follow these steps:
The connection connection type name between resource name and resource name in view view name has been deleted because it is no longer valid.
Explanation: One of the endpoints of a connection no longer supports that connection type. The connection has been deleted from the view. When component type properties are changed, such as deleting or renaming a connection type associated with that component type, any connections of that type in that view are no longer valid and are automatically deleted.
Message Inserts:
Operator Response: If you want to restore the connection between the two component types, do either of the following:
One or more resources have been changed to the Undefined Generic component type in the view name view.
Explanation: A component type has been deleted. Resources defined with that component type are no longer valid and have been changed to the "Undefined generic" component type.
Message Inserts:
Operator Response: Do the following:
User username has accessed Plan mode on the same Tivoli GEM server and might still be using it. If two people use Plan mode on the same Tivoli GEM server simultaneously, data might be lost. Select OK if you know that the above user is no longer using Plan mode. Select Read-only to use Plan mode in read-only mode.
Explanation: According to the PlanMode.user file, another user currently has Plan mode open on the same Tivoli GEM server. When you open a view in Plan mode in read/write mode, your username is stored in the PlanMode.user file.
If two people use Plan mode on the same Tivoli GEM server simultaneously, changes might be overwritten and data might be lost.
To ensure that no data is lost, open Plan mode in read-only mode until you can verify that no one else has Plan mode open.
Message Inserts:
Operator Response: Do one of the following:
The aggregate aggregate name is empty, and it will not be exported.
Explanation: The specified aggregate is empty. To export the aggregate to the Tivoli GEM server, you must have at least one real component in the aggregate.
Message Inserts:
System Action: Validation stops with an error.
Operator Response: Do one of the following:
There are no components in this business system.
Explanation: There are no components in the business system. To export the business system, at least one component must be defined.
System Action: Validation stops with an error.
Operator Response: Add at least one component to the business system and then export the business system again.
There are no real components in this business system.
Explanation: There are no real components in the business system. To export the business system to the Tivoli GEM server, you must define at least one real component.
System Action: Validation stops with an error.
Operator Response: Do the following:
There are some generic components in this business system that will not be exported.
Explanation: The business system contains generic components that will not be exported to the Tivoli GEM server. However, if you export the business system as a package file or to the Tivoli Module Designer, these generic components will be exported.
System Action: Validation continues with a warning.
Operator Response: Do one of the following:
The CDF file CDF filename has been changed on the Tivoli GEM server and might be inconsistent with the local version you are using.
Explanation: The CDF file has been changed on the Tivoli GEM Server and might be inconsistent with the local version you are using. To include the latest information from the CDF file on the Tivoli GEM server, you must make the corresponding changes in the component properties.
Message Inserts:
System Action: Validation continues with a warning.
Operator Response: Do the following:
The CDF file CDF filename does not exist.
Explanation: The CDF file for a component in the business system is missing.
Message Inserts:
System Action: Validation stops with an error.
Operator Response: Do one of the following:
The CDF CDF triplet is used in multiple levels of aggregation.
Explanation: The specified real component is used in multiple levels of aggregation. Components can only be used in one level of aggregation.
Message Inserts:
System Action: Validation stops with an error.
Operator Response: Do the following:
The generic component generic component name is used in multiple levels of aggregation.
Explanation: The specified generic component is used in multiple levels of aggregation. Components can only be used in one level of aggregation.
Message Inserts:
System Action: Validation stops with an error.
Operator Response: Do the following:
There are no real components in this business system.
Explanation: There are no real components in the business system. The business system can be exported as a package file or to the Tivoli Module Designer (TMD) for further definition.
Operator Response: Click the Ignore button and continue with validation.
The CDF file for the component type component type does not exist.
Explanation: The CDF file for this component type cannot be found on the local GEM console machine. The business system will not be exported.
Message Inserts:
System Action: The command is not issued.
System Programmer Response: Examine the NetView log for more details. The command issued could be trying to request a field in RODM that is not available for the resource selected. Correct the command in the server command response file and rerun CPEBATCH.
A failure occurred on NetView for z/OS while executing a command.
NetView message: netviewmessage
Explanation: A command was executed on NetView for z/OS and an error message was returned.
Message Inserts:
System Action: The topology server terminates.
Operator Response: For more information, enter HELP messagenumber on a host Tivoli NetView command line, where messagenumber is the message number in netviewmessage, or contact your system programmer.
System Programmer Response: For more information, enter HELP messagenumber on a host NetView command line, where messagenumber is the message number in netviewmessage.
An error occurred retrieving a variable from RODM.
Explanation: A command was issued that required information from RODM. Either RODM could not be contacted, or the information requested does not exist in RODM.
Operator Response: Do the following to export the business system:
Too many Service Points are selected. Only one selection is allowed when the global wild card is specified.
Explanation: The wild card "*.*.*.*" was entered in the Host name or IP address field, and more than one Service Point was selected in the list. Only a single selection is allowed for this wild card. This is restricted due to performance considerations.
Operator Response: Either specify a different host name or IP address, or only select a single service point in the list.
Wild card characters are not supported for TN3270 Service Points.
Deselect the TN3270 Service Points or do not use wild card characters.
Explanation: Wild card characters are not supported by TN3270 Service Points.
Operator Response: Either deselect the TN3270 Service Points, or specify the specific TCP/IP host name or IP address to collect IP session data for.
This AMP has been previously loaded. To reload the AMP, all clients connected to the server must be resynchronized. Do you want to continue? Select Yes to continue. Select No to cancel the operation.
Explanation: When you change an AMP and load the modified AMP, the clients connected to the server must be resynchronized. To synchronize the clients, no users can be logged on, so you might have to force users off of the clients.
System Action: The system responds based on the operator's response.
Operator Response: Do one of the following:
All clients are currently in the resynchronization process. No AMP can be loaded at this time.
Explanation: A previous request to load an AMP occurred and the clients are currently being resynchronized. The AMP cannot be loaded during a resynchronization process.
System Action: The AMP is not loaded.
Operator Response: When the resynchronization process completes, load the AMP again.
The server is currently resynchronizing. You can wait until the resynchronization process ends or cancel the sign on request. Click the Ok button to wait. Click the Cancel button to sign off.
Explanation: You cannot sign on to the server during a resynchronization process.
System Action: You are not signed on.
Operator Response: Do one of the following: