This chapter explains how to gather information and resolve or report problems that might appear when programming the IRIS 3270 Emulator.
The chapter includes information on using the trace utility to resolve HLLAPI errors.
To track errors and more easily troubleshoot problems, you can use 3270 Trace to record all data sent to and received by the 3270 emulation process, then use the Trace Display utility to display the recorded data.
To record the presentation space data, turn on the 3270 Trace option from the Miscellaneous box in the Set Up 3270 window, as described in “Selecting Miscellaneous Options,” in Chapter 1 of the IRIS 3270 Emulator User's Guide.
After you use 3270 Trace to record the presentation space, you can display the data using the Trace Display utility by entering:
display_3270trace |
The full-screen window in Figure 2-1 appears.
This section deals with the process for resolving errors. Error messages are listed in Appendix A, “Silicon Graphics HLLAPI Error Messages.”
Errors reported by the IRIS 3270 Emulator are logged in the file /var/opt/3270/file/t3279_log.PID. All errors in this file are also displayed in an error message window. Errors reported by the SGI 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 SGI HLLAPI interface has its own style of user interface.
For configuration errors, the error information in the log files should be enough. For other errors, additional information can be gathered by setting the 3270 Trace option to Yes using the Set Up 3270 window as described in Chapter 1 of the IRIS 3270 Emulator User's Guide.
For configuration errors, look up the error message and make the appropriate correction using the Set Up 3270 window. For ASCII terminal users, see Appendix B of the IRIS 3270 Emulator User's Guide 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.
If you are a developer working with the SGI HLLAPI, use the Trace Display option in the 3270 icon to display the data contained in the trace file /var/opt/3270/file/trace_log.
These types of information are traced: [BULLET LIST]
An image of the 3270 Presentation Space. The color code is blue.
An image of the 3270 Status Line. The color code is white.
“Line Change Bits.” 1 = changed and 0 = no change. The leftmost bit is for the status line. The other bits are for lines 1 to n with n being 24, 27, 32, or 43. The color code is yellow.
A hexadecimal display of all attributes with their row and column position. Row and column numbers start at 0, not 1. The color code is red.
Keyboard input. Use Appendix B to interpret the scan codes and shift state representation. The color code is green.
A hexadecimal display of structured field data read by hl_read_sf.c and written by hl_write_sf.c. The color code for received data is blue and for transmitted data, yellow. The characters are in EBCDIC.
A hex display of SGI Message Mode data read by hl_read_msg.c and written by hl_write_msg.c. The color code for received data is blue and for transmitted data, yellow. The characters are in 3270 buffer code.