Solve connection, authentication, emulator, and other problems when using Operations Console.
Problems can occur during an Operations Console session. The following topics contain some solutions to common problems that might be encountered during your initial setup and management of your configurations. If you have a console problem that you cannot overcome using the troubleshooting section and you need to change the console type, see Changing consoles, interfaces, and terminals.
The Operations Console client (PC) keeps a set of log files to be used only by IBM® development. These log files can help assist with user problems. If you report a problem to your service provider, you might be asked to send specific log files from the PC.
Operations Console has a built-in, hot-key-activated, Settings dialog window that has special options used to help troubleshoot problems. The Settings window is activated by pressing and holding the Alt, Shift, and s keys (Alt+Shift+s). The options to split the log files can be very helpful to your service provider, especially if you have many connection configurations. Splitting the logs so each configuration has its own log makes it easier to find problems. When only one connection has a problem, activity in other connections are not seen in the log.
There is also a hot-key-activated function to capture the screen data when the connection is not responding correctly. To capture the screen data, select the configuration and press and hold the Ctrl and c keys (Ctrl+c). This dumps the contents of the last ten screen buffers (three screens of data) and the timestamp they were received into the connection log. This log can be used by service and support to see what the last updates to the emulator were. Activating this process a again, without changes to the window, does not output any more data to the connection log.