|
|
|
|
The Message action field for a logged message describes the recommended action. In some cases, no action is required. For example, an exception message may not indicate an error, but it may provide background information that helps to identify the cause of a later problem message.
Common recommended actions include the following:
Check the SNAP-IX TN3270 configuration, and add or modify resources.
Check the Solaris computer's resources, such as memory or hard disk space.
Check for a link outage between SNAP-IX TN3270 and the host, using the ping application.
Contact support personnel for the host system with which SNAP-IX TN3270 is communicating to resolve configuration mismatches between SNAP-IX TN3270 and the host system configuration.
Contact the developer of a HLLAPI application if the application is making invalid API calls.
Report the error condition to your SNAP-IX TN3270 supplier if the Cause type field indicates an internal error in the SNAP-IX TN3270 software.
The following sections provide more information about some of these actions.
The Message action field may recommend that you contact one of the following types of support personnel:
Support personnel at the host system with which SNAP-IX TN3270 is communicating
Support personnel at the company from which you bought SNAP-IX TN3270
If the recommended action for a message includes sending the log files and trace files to support services, provide the error and audit log files created when the error occurred. If tracing was enabled, provide the trace files as well.
If you were running SNAP-IX TN3270 with audit logging or exception logging (or both) disabled, attempt to reproduce the problem with all categories of logging enabled. If you reproduce the problem, provide the new log files that include all event categories.
Your configuration files may contain information that you do not want to make available to a third party. If the recommended action asks you to send the configuration file to third-party support services, you may want to remove some information before sending the file. Modify or blank out the parameters instead of removing them completely, and provide a note explaining which parameters have been modified when you send the file.
The return code from an operating system call is sometimes returned in the Message text field. The return code may be shown either as a symbolic name or as a numeric value. Check numeric values in the errno.h file on the computer where the error occurred to find the corresponding symbolic name. The symbolic names are listed in your operating system documentation.
|
|
|
 |
|