Unable to create a Monitor view due to missing or corrupt data in the filename file.
Explanation: The file used to store resource information has missing or corrupt information. This could be the result of manual editing of the file.
Message Inserts:
System Action: The monitor view will not be shown.
Operator Response: The original file will need to be restored for monitor views to be available in Plan mode.
Unable to launch bean due to invalid bean name name.
Explanation: The bean name is not specified correctly.
Message Inserts:
Operator Response: Verify that the name of the bean was specified correctly in the command profile editor.
Unable to instantiate bean name.
Explanation: The bean could not be instantiated by the Java Virtual Machine.
Message Inserts:
Operator Response: Verify the following:
Non-visual bean loaded name.
Explanation: The bean that was launched does not have a window.
Message Inserts:
System Action: Processing continues.
Operator Response: Check the log for any output.
The entered task arguments are not valid.
Task: task name
Reason: reason code
Explanation: The values entered in the entry fields for the bean are not valid.
Message Inserts:
Operator Response: Close the message window and re-enter the values in the entry fields for the bean.
Aggregate thresholds are not valid.
Explanation: The value of the aggregate thresholds not correct.
Operator Response: Close the message window and specify valid aggregation threshold values.
Aggregation priority is not valid.
Explanation: The value of the aggregation priority is outside the accepted range.
Operator Response: Close the message window and specify a valid aggregation priority.
Flag is not valid.
Explanation: One of the flags that has been changed cannot be set on the Resource Properties window.
Operator Response: Close the message window and set the flag correctly.
Polling interval is not valid.
Explanation: The value for the polling interval is outside the permitted range.
Operator Response: Close the message window and specify a valid polling interval.
Resource name is not valid.
Explanation: The name of the resource is not valid.
Operator Response: Close the message window and specify a valid resource name.
You have requested to delete the application name.
This will also delete any software components defined for the application.
Do you want to continue?
Explanation: You have requested to delete an application. Deleting an application also deletes all information about any software components that have been defined as part of this application.
Message Inserts:
System Action: If you select Yes, the application and any associated software components are deleted. If you select No, the application is not deleted.
Operator Response: Select Yes to delete the Application and all associated software components. Select No if you do not want to delete this application.
You have requested to delete the software component name.
This will also delete all information about the component.
Do you want to continue?
Explanation: You have requested to delete a software component. Deleting this component will delete all information about the component.
Message Inserts:
System Action: If you select Yes, the software component is deleted. If you select No, it is not deleted.
Operator Response: Select Yes to delete the software component. Select No if you do not want to delete this software component.
\"{0}\" field must be greater than the \"{1}\" field.
Explanation: Field {0} can not be less than field {1}.
Message Inserts:
Operator Response: Ensure that the value in field {0} is greater than the value in field {1}.
On the Web Server page, the default value for the port number cannot be restored without first stopping the web server.
Explanation: To restore the default value for the web server port number, you must first stop the web server.
System Action: The default port number could not be restored.
Operator Response: To restore the port number to its default value, follow these steps:
The specified port port number is already in use. On the Web Server page of the Console Properties notebook, select a different port number. Apply the change and then restart the web server.
Explanation: This console currently uses a port number that is already in use by another web server. Multiple web servers cannot use the same port number.
Message Inserts:
System Action: The web server was not started.
Operator Response: To specify a unique port number, follow these steps:
You are about to stop your web server. Doing this will result in all servable files being deleted.
Explanation: When you stop the web server, all views that are serviced by the web server for this console are deleted so that another client on this machine cannot obtain that same port number and serve the views you have opened.
System Action: Any views which have already been created for the web server will be removed from the servable list.
Operator Response: Do one of the following:
All ports in the specified range (startportnum to endportnum) are already in use. On the Web Server page of the Console Properties notebook, select a different start of port range or end of port range. Apply the change and then restart the web server.
Explanation: All the ports defined for the Web server in the Console Properties notebook are currently in use.
Message Inserts:
System Action: The Web server was not started.
Operator Response: Specify a different port number range as follows:
The web server has been successfully started using port portnum.
Explanation: The Web server was started using the port number indicated.
Message Inserts:
System Action: None
Operator Response: None
The AMP packaging file should end with ".amp" or ".pkg"
Do you want to continue processing file filename?
Select Yes to continue.
Select No to choose another file.
Explanation: The file you selected does not end with one of the preferred extensions: ".amp" or ".pkg". You can continue processing, but this indicates that the file is not a valid package file.
Message Inserts:
System Action: If you select Yes, the system tries to process the file. If you select No, you can choose another file.
Operator Response: Do one of the following:
An AMP was added to the server by user user name.
The console log has additional details.
Explanation: The AMP was successfully loaded by the specified user.
Note: If you have used the Verify function in this console session (this would have been indicated in the message) your verification business tree and views might not accurately represent the newly added AMP. To see the new AMP information, sign off and back onto the console.
Message Inserts:
System Action: The AMP is now available for use.
Operator Response: Check the console log for more information about the specific entities that were added.
The AMP was not successfully processed.
Please check the console log for details.
Explanation: There was a failure in loading the selected AMP package file.
System Action: The system could not load the selected AMP package file. The AMP is not available for use.
Operator Response: Check the console log for specific failure information.
The same JAR file is being loaded more than once.
Please check the console log for details.
Explanation: You tried to load a JAR file that has already been loaded and processed.
System Action: The system will not load the JAR file if it has already been loaded.
Operator Response: Make sure that duplicate JAR files are not present in multiple AMPs.
Problems were encountered in loaded JAR files.
One or more applications might fail.
Please check the console log for details.
Explanation: The JAR files could not be loaded and processed successfully.
System Action: The system will not process the JAR file if there was any error while loading it.
Operator Response: Make sure that duplicate JAR files are not present in multiple AMPs or that the same fully-qualified class names are not stored in more than one JAR file.
Multiple definitions of the same class name occur in different JAR files.
One or more applications might fail.
Please check the console log for details.
Explanation: You tried to load the more than one JAR file, each of which contains the same fully-qualified class name.
System Action: The system will not load the JAR files.
Operator Response: Make sure that the JAR files do not contain the same fully-qualified class names.
File filename does not exist.
Explanation: The file you specified in the file selection dialog does not exist.
Message Inserts:
System Action: The system is not able to load the specified file.
Operator Response: Specify another file or cancel the operation.
Command exit exitname on the server has timed out. numresponses command responses were received. The command responses might not be complete.
Command String: stringname
Time out value: value
Explanation: The topology console started a command exit on the topology server, but the topology server timed out while waiting on the command responses. It is very likely that the command responses are not complete.
Message Inserts:
System Action: It is likely that the command responses were processed by the console; however, this depends on what program started the server command exit on the console. This could have been a customer-provided console command exit, which might or might not process the available command responses.
Operator Response: Try the request again. If the same failure occurs, increase the request timeout on the General page of the Console Properties dialog. If this does not resolve the problem, contact your system programmer.
System Programmer Response: Do one or more of the following:
If you cannot resolve the problem, contact IBM Customer Support.
Command exit exitname on the server failed.
Return Code: 0xreturncode
Command String: stringname
Explanation: The topology console invoked a command exit on the topology server, but the topology server received a non-zero return code from the command exit. The return code came from the IhsiSend API on the server.
Message Inserts:
System Action: The server command exit failed. The command did not complete.
Operator Response: Contact your system programmer.
System Programmer Response: Look up this return code in the Tivoli NetView for z/OS: NetView Management Console User's Guide, and take the appropriate action. If you cannot resolve the problem, contact IBM Customer Support.
The URL variable is not defined in the command string.
Explanation: You attempted to connect to a web page, but no web page address was provided.
System Action: The request for a web page will not be completed.
Operator Response: Contact the system programmer.
System Programmer Response: Using the CPE utility to ensure that there is a %url% entry in the command string for this command.
The process invoked returned a non-zero return code.
Explanation: The selected command invoked a process on this workstation. The launched application process returned a non-zero return code to the operating system. This might or might not be an error, depending on the process invoked.
System Action: The system continues.
Operator Response: Contact the system programmer to see if this message is expected.
System Programmer Response: Look in the error log to see the name of the process and the return code. Verify that this return code is acceptable for this process.
The system could not invoke the process process
Explanation: The selected command attempted to invoke a process on this workstation, but that process could not be started.
Message Inserts:
System Action: The command cannot be completed. The system continues.
Operator Response: Contact your system programmer.
System Programmer Response: Verify that the command specified in the message is executable from the command line of this system in any directory. Also verify that security is configured properly.
No match for operating system operating_system and a program type of program_type could be found in the properties file.
Explanation: The command invoked attempted to start a process on this workstation, but an entry for this program type and operating system could not be found in the properties file.
Message Inserts:
System Action: Since this operating system and program type could not be resolved in the properties file, no action is taken. The system continues.
Operator Response: Contact your system programmer.
System Programmer Response: Edit the usercmdinv.properties or defaultcmdinv.properties file and add an entry for this program type and operating system. The properties files are located in the settings directory of the current server database.
Unable to retrieve session data from session monitor because a required task on Tivoli NetView for z/OS is not active.
Explanation: The session monitor task AAUTSKLP was not activated or failed to initialize on the Tivoli NetView that the console has logged onto. This prevents retrieval of session data from this and any other Tivoli NetView domain.
Operator Response: Start the session monitor task on host NetView by entering STARTCNM NLDM on a host Tivoli NetView command line. For more information, enter HELP AAU923 on a host Tivoli NetView command line, or contact your system programmer.
System Programmer Response: On a host Tivoli NetView command line, enter HELP AAU923 for more information on what actions to take.
No data exists for the resources specified.
Resource: resourcename
Partner resource: partnername
Domain ID: domainID
Explanation: There is no data in the session monitor VSAM database or in session monitor storage for the resources specified at the specified view domain. The resource name might not be valid or there might not be any data for that resource.
Message Inserts:
Operator Response: If a partner resource name was entered in the Session Data window, verify that this resource name was entered correctly. For more information, enter HELP AAU925 on a host Tivoli NetView command line, or contact your system programmer.
System Programmer Response: On a host Tivoli NetView command line, enter HELP AAU925 for more information on what actions to take.
Unable to retrieve data from Tivoli NetView for z/OS domain domainID.
Reason: Tivoli NetView cannot establish a cross-domain session at the adjacent Tivoli NetView domain.
Explanation: The session monitor in the Tivoli NetView which the console is logged onto, cannot communicate with the session monitor in the specified domain. A cross-domain session cannot be established.
Message Inserts:
Operator Response: If you entered a domain ID in the Session Data window, ensure that you specified the correct domain identifier, Verify that the session monitor is active in the specified domain. For more information, enter HELP AAU926 on the host Tivoli NetView command line or contact your system programmer.
System Programmer Response: On a host Tivoli NetView command line, enter HELP AAU926 for information on what actions to take.
The SSCP name could not be translated into a Tivoli NetView for z/OS domain ID.
Resource: resourcename
Partner resource: partnername
NetID: netid
SSCP name: sscpname
Explanation: The Tivoli NetView that the console has logged onto could not translate the NETID and the SSCP name to a Tivoli NetView domain ID. The session monitor does not have any internal information to map the SSCP name into a Tivoli NetView domain ID.
Message Inserts:
Operator Response: If the Tivoli NetView domain ID is known, provide this information in the Session Data window. For more information, enter HELP AAU974 on a host Tivoli NetView command line, or contact your system programmer.
System Programmer Response: On a host Tivoli NetView command line, enter HELP AAU974 for more information on what actions to take.
A failure occurred on Tivoli NetView for z/OS while retrieving session data.
Resource: resourcename
Partner resource: partnername
Domain ID: domainid
NetView message: netviewmessage
Explanation:
Message Inserts:
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.
The system could not invoke the process: process or the process returned a non-zero return code: return code
Explanation: The selected command attempted to invoke a process on this workstation, but either the process could not be started or the process returned a non-zero return code to the operating system.
Message Inserts:
System Action: The command cannot be completed.
Operator Response: Contact your system programmer. This message might or might not be expected.
System Programmer Response: Do either of the following: