This chapter explains how to gather information and resolve or report problems that might appear when using the IRIS 3270 Emulator.
If you have difficulty installing or running the Silicon Graphics File Transfer software on your IBM host, refer to your release notes for product support information. To help diagnose the problem, you might be asked to create a dump of your session. This section describes how to create such a dump.
When you are through, mark the tape with your name, company address, and telephone number, and refer to your release notes for instructions on where to mail the tape of the dump.
To create a vmdump, follow these steps:
Log in to your account from another terminal. Make certain that you are in the CP READ state. (Press <return> to toggle to CP READ.) Enter:
VMDUMP 0.END DSS |
Verify that vmdump exists. Enter:
RL |
Get the four-digit file identification (spoolid) of the vmdump. Enter:
Q RDR ALL * |
Mount a tape on an available tape drive noting the reel address. At the operator's console, or from a privileged account, enter:
SPT DUMP reeladdress rdr spoolid |
This tells you the spool ID address. Write this address down and include it when you send in the tape.
The IRIS 3270 Emulator maintains a log file of all file transfer operations. During file transfer, the file transfer software creates a file called /usr/3270/file/t3279_log.pid. In the actual file name, pid is the process-ID number of the specific t3279 process. View this file by displaying it on the IRIS terminal or printing it on a local printer.
Here is an example of log file information:
ULOAD JVW.DOC3 Size: 490070 Time info: 4743 18 7 DLOAD VM10.DATA Size: 330000 Time info: 2312 76 83 |
The words ULOAD and DLOAD indicate an upload or download file transfer.
The next string is the file name. Size is the file size in bytes.
The Time info, presented in 10-millisecond units (100 units = 1 second), is organized in three fields:
the time taken to perform the file transfer
user time spent on the process
system time spent on the process
For details about these values, refer to the times(2) online man page.
This information helps determine the throughput of the IRIS 3270 Emulator software on your network.
In addition to throughput information, the log file prints messages about errors that occur during file transfer. If an error occurs, the error message appears above the log file information for the transfer. For example:
Read call failed: errno = N DLOAD VM100.3300 Size: 330000 Time Info: 1912 51 66 |
This section deals with the process for resolving errors. Error messages are listed in Appendix A, “Error Messages.”
Errors reported by the IRIS 3270 Emulator are logged in the file /var/opt/3270/file/t3279_log.pid, where pid is the process-ID number of the specific t3279 process. All errors in this file are also displayed in an error message window. Errors reported by the Silicon Graphics HLLAPI library are logged in /usr/adm/SYSLOG. These errors are not visually displayed, since it is expected that each 3270 emulator coded on top of the Silicon Graphics HLLAPI interface has its own style of user interface.
For configuration errors, the error information in the log files should be enough to deduce the problem. For other errors, additional information can be gathered by setting the 3270 Trace option to Yes. See Chapter 1, “Configuring the IRIS 3270 Emulator,” for information about setting the 3270 Trace option.
For configuration errors, look up the error message and make the appropriate correction using the Set Up 3270 window. If you are using an ASCII terminal, see Appendix B, “Editing the Emulator Configuration File,” for more information on editing the configuration file.
If the error does not go away, refer to your release notes for product support information.
To find and correct errors that are not related to configuration problems, perform these steps:
Set the 3270 Trace option to Yes using the Set Up 3270 window.
Start the terminal emulator from the icon.
Re-create the problem.
Report the problem. Refer to your release notes for instructions on where to send the files below:
all executable files from your /opt/3270/bin directory
/var/opt/3270/file/*_log* (all log files)
If the Silicon Graphics 3270 Emulator is terminated by program error, a core file is saved in /usr/var/opt/spool. Send this file in addition to those mentioned in step 4.
If the problem occurs during a file transfer using IRISXFR, enter sgixfr versions while logged in to your host ID. Report the returned information along with the information collected in steps 1-3.