z/OS MVS Program Management: User's Guide and Reference
z/OS MVS Program Management: User's Guide and Reference
Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Interpreting the contents of IEWTRACE z/OS MVS Program Management: User's Guide and Reference SA23-1393-00 |
|
The contents of this data set represent cumulative tracing entries issued by the binder's modules during their processing sequence. Trace entries are produced at entry to and exit from each module, as well as at other points deemed important for diagnosis purposes. For instance, most binder modules produce trace entries whenever they request a system service. This information proves useful to IBM® when servicing the binder. All the entries in a trace data set are numbered, as can be seen in the sample trace in Figure 1. The numbers are normally sequential for each binder dialog. However, when the binder API is being used, there might be one or more entries beginning with sequence 0 at the point of each new service call before the normal sequence resumes. Each entry begins with a sequence number and consists of one or more lines. The four alpha characters following the sequence numbers represent the last four letters in a binder's module name, all of which begin with "IEWB". For instance, the module name in trace entry 0 is "IEWBOGET". Horizontally, the next eight numeric (hexadecimal) digits represent internal codes which signify the events taking place in a module (the coined term to refer to these codes is "event codes", or "ecodes", for short). So, for example, the ecode in trace entry 0 means "entry to module IEWBOGET", and the ecode in entry 1 means "exit from IEWBOGET". In entry 1, the ecode at the far right means that the "processing in IEWBOGET was successful." A complete list of ecodes and their definitions is available to the organization servicing the binder, but a general guideline for interpreting such ecodes is given below, under Interpreting binder ecodes. One or more lines in a trace entry provides all the pertinent diagnosis information at the time the trace was issued. For instance, most module exit entries print the return and reason codes returned to the calling module. In entry 9, module IEWBXIOP exited (ecode D2A1A100) with a return code of 12, in comparison to entry 10, where IEWBXR00 exited (ecode 409FA100) with a return code of 4. Finally, the characters between the two parenthesis in each entry is an internal time-stamp. Figure 1. Trace sample
|
 Copyright IBM Corporation 1990, 2014 |
