Troubleshooting

Segment and field exits can generate trace entries that are useful for troubleshooting.

Enabling Trace

You enable the generation of segment and field exit trace entries from Server Enterprise Edition Administration as follows:

1. From the Server Enterprise Edition Administration Home page, start the enterprise server that runs your application.
2. Click Edit for the started enterprise server.
3. Click Server > Control > ES Monitor & Control.
4. Click Control.
5. Under Trace Points > Server, check exits.

Viewing Trace Entries

MSS writes trace information for Trace diagnostics A and B datasets to the files casauxta.rec and casauxtb.rec respectively. By default, both are located in the System directory, %USERPROFILE%\Documents\Micro Focus\Net Express x.x\WORKAREA \es-name (where es-name is the name of the enterprise server). However, you can view trace entries in real time, including C/x trace information, by clicking Display.

Trace IDs

Trace entries are generated in entry and exit pairs using six-digit hexadecimal IDs as follows:

• Digits one and two are 39. These indicate that the entry is for MFS.
• Digits three and four are unique to the emitting source module.
• Digit five is a 0 (zero).
• Digit six indicates the type of trace entry, as follows:

  3	entry
  4	exit
  9	error

The following lists MFS trace IDs along with their significance and the variable content of each.

x'390103', Segment exit entry, exit number, vector
x'390204', Segment exit exit, return code, segment number
x'390303', Field exit entry, exit number, vector
x'390404', Field exit exit, return code, max return code
x'390509', Segment exit missing, exit number, intended vector
x'390609', Field exit missing, exit number, intended vector

Example

In this example, the first field exit is for exit number 100 and vector 100. However, Server Enterprise Edition has failed to load the module. In this case, the error is simply recorded and processing continues. The second trace entry reveals that exit 5 was given control for vector 5. The third trace entry records the return code and the running maximum return code for the field exits at the return of exit 5. Processing continues on to the next to the last trace entry where segment exit 126 is called with vector 14. The return from the segment exit is 0 (zero) and the current segment is 1.

Note: In trace output, the trace ID includes a prepended "39 " indicating that the entry is from casmfs.dll, and digit five is shown as 8 instead of 0 (zero).

                                  Seq  Task-Nbr  ProcessID +---ID--+ hhmmsshh
mfsFldExitER(  100 )v(   100 )    654      6652      12312 39 390689 22105958
mfsFldExit(      5 )v(     5 )    655      6652      12312 39 390383 22105958
mfsFldExitRC(    0 )max(   0 )    656      6652      12312 39 390484 22105958
mfsFldExit(      5 )v(     1 )    657      6652      12312 39 390383 22105958
mfsFldExitRC(    8 )max(   0 )    658      6652      12312 39 390484 22105958
mfsFldExit(      5 )v(     1 )    659      6652      12312 39 390383 22105958
mfsFldExitRC(    0 )max(   8 )    660      6652      12312 39 390484 22105958
mfsFldExit(      5 )v(     1 )    661      6652      12312 39 390383 22105958
mfsFldExitRC(    0 )max(   8 )    662      6652      12312 39 390484 22105958
mfsSegExit(    126 )v(    14 )    663      6652      12312 39 390183 22105958
mfsSegExitRC(    0 )seg(   1 )    664      6652      12312 39 390284 22105958