Micro Focus Visual COBOL 2.3 Update 2 for Eclipse (Windows) > Deployment > Deploying to Enterprise Server > Enterprise Server configuration and administration > Troubleshooting > Using a Diagnostics Server > Viewing a System Trace: Diagnostics Example

Viewing a System Trace: Diagnostics Example

Restriction: This topic applies only when the Enterprise Server feature is enabled.

This subject is covered in the help topic To view a system trace. However, the options are complex and it is worth looking at an example.

To obtain a trace of the system trace table:

In the Enterprise Server Administration screen, click the diagnostic server's Details button to access the server's Details screen.
On the Details screen, click the ES Monitor & Control button to access the diagnostic server's ESMAC screen.
In the Diagnostics area in the left pane, select the Trace radio button, and select either the A or B radio button to select the A or B dataset. (Don't select C, since the in-memory trace table belongs to the diagnostics server).
In the Blocks field, specify the number of trace blocks that are to be aggregated into one trace index entry.
Click Display.

Figure 1. Trace Index Page

Each block is the same size as the system trace table, that is, it contains the number of trace entries specified in Trace Table Size on the Edit Server page for the server. The index entries are displayed with a timestamp against each one. This is the timestamp of the first trace entry in each set of blocks. These timestamps help you narrow down your search to particular events.

To view the actual trace, go to one of the index entries, and make selections in the following fields:

In Blocks (immediately to the right of Details), specify how many blocks you want to be included in the trace. This defaults to the value you entered in Blocks in the Diagnostics group of the menu. You can change it to any value you want. Having two Blocks controls helps you control what is displayed in the formatted trace more precisely.

In Level, (the next control to the right), specify the level of detail that you want to see in the formatted trace. The options are:

0	Service start, module start, module end, service end. This is the default.
1	Enterprise server API entries and exits
2	Subsystem trace entries
3	All entries where it is possible to provide some formatting of the data
4	All trace entries

In PIDs (next to the right), check the check boxes for the process IDS of the processes in which you are interested. Check boxes are provided for all the processes that have trace entries in the blocks represented by this trace index entry. Process IDS are prefixed with a letter or number indicating the function of the process. The following letters are used:

C	communications process (MFCS)
F	Fileshare server (internal)
J	journal control
M	server manager
R	recovery
S	service execution process (SEP)
U	unknown
Z	generic terminal or client

In Task IDs (next to the right), check the check boxes for the task IDS of the tasks in which you are interested. Check boxes are provided for all the tasks that have trace entries in the blocks represented by this trace index entry.

The Level, PIDs and Task IDs controls are filters that help you select just the specific information of interest. If you leave the level as 0, the default, and don't check any process IDs or task IDs, you will see the minimum level of information for all processes and tasks that have entries in the block represented by the trace index entry. Note that it is possible to make selections such that no trace information is generated. This happens if you select both processes and tasks, and none of the selected tasks ran on the selected processes; a task cannot run on more than one process. If a task requires communications work, that work has its own process and task, and there is no automated way of relating the two task IDs. You always see the first trace entry in the block, irrespective of filtering.

Here is an example of how you can use the controls to select the information you want to see. Suppose you specify 10 in Blocks in the Diagnostics group of the menu. There are actually 60 blocks of information in the dataset, so 6 index entries are displayed. Suppose you were interested in a particular SEP, which you can see listed in the third and fourth index entries. You might then specify 20 in Blocks for the third index entry, check the box next to the process ID for the SEP, then click Details. Now you can only see trace entries for that SEP, in all the blocks that contain them, starting with the first block of the third index entry.

Each trace entry contains the following information:

Heading	Contents
None	An interpretation of the traced event, if one can be supplied
Seq	Sequence number of the entry in ascending order
Task-Nbr	The five-digit task number
ProcessID	The five-digit process ID
ID	the ID of the event, command, or instruction that was traced. This is a four-byte hexadecimal number.
hhmmsshh	A time stamp that indicates when the trace entry was written. The time stamp is in hours, minutes, seconds, and hundredths of a second.
aaaa bbbb	Eight bytes of entry-specific data

When you have finished viewing a trace, click Back to return to the trace index page.