gtpm1m3xTPF V4R1 Migration Guide: 3.1 to 4.1

System Log Trace Facility

Table 53 compares the system traces that are supported in the TPF 3.1 system and the TPF 4.1 system. You can activate the TPF 4.1 traces by using the new ZSTRC command.

Table 53. System Log Trace Summary

Type of Trace TPF 3.1 System TPF 4.1 System ZSTRC Keywords
Macro Trace Facility Was a stand-alone trace, activated by modifying a keypoint or adding code to the macro decoder user exit. Only file resident Enter/Back macros were included in the trace. Traces all SVC macros associated with an ECB. There are two tables in the dump:
  • A dump of the ECB virtual memory, which includes all the macros (SVC calls) issued by the ECB. This is a wraparound trace; when it runs out of space, it writes over the oldest entries.
  • A collated trace that contains all macros called by all ECBs on the I-stream, sorted by time stamp.
Macro

NOMacro

System Log Trace Facility Included in the macro trace facility. This was on whenever the macro trace facility was on. This is a subset of the macro trace and I/O trace facilities that you can turn on and turn off. SYslog

NOSYslog

Enter/Back Trace Facility Included in the macro trace facility. This was on whenever the macro trace facility was on. This is a subset of the macro trace facility that you can turn on and turn off. Enter

NOEnter

I/O Trace Facility Was a stand-alone trace, handled by the common I/O routine or the common I/O handler. There was one table for the entire TPF system. This trace was always active. The trace is maintained separately for each device. A collated trace appears at the beginning of the dump (similar to collated macro trace). IO

NOIO

Register Trace Facility Not provided. This new option traces register contents on every SVC call. REGS

NOREGS

Register and S/370 Branch Trace Facility Not supported. Provides a list of the last 1000 processed BALR, BASK, and BASSM branches using either the IBM ESA/370 or IBM ESA/390 architecture. Branch

NOBranch