Problem Analysis

This chapter describes the information that will help you analyze problems with Z and I Emulator for Windows, and ways to report a problem to HCL. For detailed information about contacting HCL, refer to Quick Beginnings.

For information about Z and I Emulator for Windows and support, refer to the following Web sites:

Z and I Emulator for Windows provides several utilities to help you with problem analysis. They can be invoked by selecting their icons from the Programs -> HCL Z and I Emulator for Windows -> Administrative and PD Aids subfolder on the Windows Start menu.

The following sections describe these utilities and how to use them.

Log Viewer

The Z and I Emulator for Windows log viewer utility enables you to view, merge, sort, search, and filter information contained in message and trace logs. Use the log viewer during problem analysis to work with message and trace log entries. The default name of the message log output file is PCSMSG.MLG; its file extension must be .mlg. The file extension for trace logs must be .tlg.

To view message or trace logs:

  1. From the Administrative and PD Aids subfolder, click Log Viewer; or, from an active session, click Launch -> Log Viewer from the Actions menu.
  2. From the list of logged messages, double-click a message to display the message text.
Only one message log is created per machine. In simultaneous user environments such as WTS, all user messages are logged into that single instance of the log file. See Using Windows Terminal Services for more information about terminal services.

For more information about log viewer functions, see Log Viewer Functions.

Trace Facility

The Z and I Emulator for Windows trace facility enables you to log trace information for certain Z and I Emulator for Windows functions.

To start a trace, perform the following steps:

  1. From the Administrative and PD Aids folder, click Trace Facility; or, from an active session, select Launch -> Trace Facility from the Actions menu. The trace status on the title bar displays the current state:
    Trace data is being collected by the trace facility.
    No trace data is being collected.
  2. From the main dialog box, click Set Up to set the desired trace system parameters.
  3. Click OK to return to the main trace dialog box.
  4. From the main trace dialog box, select the type of data you want to trace from the Function Name, Component Name, and Trace Option list boxes.
    Function Name
    A specific set of Z and I Emulator for Windows features, such as 3270/5250 Emulator or User Services.
    Component Name
    The name of a specific part of a function, such as API data (for the 3270/5250 Emulator function) or Node Initialization (for the User Services function).
    Trace Options
    The options associated with a particular component, such as EHLLAPI (for the API component) or API trace (for the Node Initialization component).
  5. Start tracing data by clicking Start, or apply changes to the trace options by clicking Apply.
  6. Run the operation that you want to trace.
  7. Optionally, stop the trace by clicking Stop.
  8. Save the trace data to your hard disk by clicking Save.
  9. Click Format to specify a formatted trace file name and to format the trace data. The Information Bundler utility should be used immediately after the trace is complete to ensure that the correct information is gathered.
    If you have changed the default path setting for the formatted trace file, the Information Bundler will not find the trace information. Copy the trace files to the system-class application data directory.
  10. Click OK.
  11. Click Clear to clear the trace buffer where you saved a trace.
  12. Use the log viewer to view the formatted trace log.
Trace facility can capture only the application level (Ring 3) tracing, when logged on WTS environment, where the conso session ID is non-zero. If you want to trace the kernel level tracing (Ring 0), use the command line tracing options.

Information Bundler

The Z and I Emulator for Windows Information Bundler utility gathers system files, trace and log files, and registry information into a .ZIP file. This file can be sent to support personnel, using the Internet Service utility. The Information Bundler should be executed immediately after the trace is complete to ensure that the correct information is gathered.

Start Information Bundler using one of the following methods:

The X12345.ZIP file is created in the Z and I Emulator for Windows system-class application data directory. This file contains system and Z and I Emulator for Windows information. Refer to the installation documentation for the location of the system-class application data directory for each Windows operating system.

NOTE : Information Bundler utility requires dotnet version 4.6.1 to work.

Advanced Configuration, Management, and Operations