gtpm1m3v | TPF V4R1 Migration Guide: 3.1 to 4.1 |
Before this release, the TPF system did not support the register and S/370 branch trace facility The only way to use the functions of the program event recording (PER) trace facility was to run the TPF system under the IBM Virtual Machine (VM) system. All macros for a single I-stream were traced in the same table. As one ECB gave up control and disappeared, new trace entries were added for the currently active ECB. This meant that high activity levels by one ECB could age out the trace entries created by other ECBs. For performance reasons, only file-resident ENTxC or BACKC calls were traced.
The SNA I/O trace facility had one table for the entire system. When a device error occurred, the information was frequently aged out by other high-use devices.
Beginning with this release, the TPF 4.1 system supports the following hardware facilities:
The PER trace facility provides a hardware trace facility that traps a program event when a specific event occurs. In the TPF 4.1 system, you can use the PER trace facility to trap the following:
The new ZSPER command allows you to specify the events that you want to trap. See Using the Program Event Recording (PER) Trace Facility for more information about the ZSPER command. See ESA/370 Principles of Operation for more information about PER.
The following enhancements were made to the diagnostic capabilities in the TPF 4.1 system:
Provides a list of the last 1000 processed BALR, BASR, and BASSM branches using either the IBM ESA/370 or IBM ESA/390 architecture. This trace facility maintains, with minimal performance cost, a list of the last 1000 BALR, BASR, and BASSM instruction branches. See ESA/370 Principles of Operation for more information about the register and S/370 branch trace facility.
Has been improved to trace each device separately rather than as a single table for the entire system, allowing you to detect devices that are hung. The trace information is collated by time stamp.
See TPF Main Supervisor Reference for more information about the I/O trace facility.
Provides the following traces:
Each ECB has its own unique trace area. The trace is maintained for each ECB rather than on a system-wide basis. More data is being saved for most traced events. There is also a collated trace for all ECBs on the I-stream, sorted by time stamp.
Enables you to activate a dump data user exit to present ECB-controlled SERRC and SNAPC data.
Provides expanded PIU tracing with additional information. See TPF ACF/SNA Data Communications Reference for more information about the PIU trace facility.
Assists in determining the cause of errors by selectively monitoring the execution of ECB-controlled programs and producing a record of the system services macros processed and related data. See TPF Program Development Support Reference for more information about RTT.
Traces registers on every supervisor call instruction (SVC) and Enter/Back.
Provides a detailed I/O trace for SNA I/O interrupts that occur during Network Control Program (NCP) XID exchanges, adjacent link station (ALS) XID exchanges, and channel-to-channel (CTC) XID exchanges. The SNA I/O trace facility also provides a detailed I/O trace for NCP, ALS, and CTC asynchronous interrupts. See TPF ACF/SNA Data Communications Reference for more information about the SNA I/O trace facility.
Traces events formerly included in the macro trace that are not associated with a message or an I/O device.
The new ZSTRC command activates all of these system traces. The output of the traces is included in system error dumps. The ZSTRC command also activates block checking mode and virtual-equals-real (VEQR) mode. See Block Checking Mode for more information about block checking mode. See Testing the Migration (Virtual-Equals-Real (VEQR) Mode) for more information about VEQR mode. See System Log Trace Facility for more information about the parameters for the ZSTRC command.
The TPF 4.1 system provides the following improvements to the SNA communication trace facilities as well:
The PIU data stored in the PIU trace table now contains a time stamp, the procedure correlation identifier (PCID), and the origin and destination network identifier (NETID) and node name. Also stored in the PIU trace table is the 8-byte header included in all read and write channel programs during normal channel-to-channel (CTC) data transfer operations. The size of the PIU trace table is now defined by the TRACSZ parameter in the SNAKEY macro. See Path Information Unit (PIU) Trace Facility for more information about the PIU trace facility.
Enhancements were also made to the offline PIUPRT utility that is used to print the PIU trace table once it was written to the real-time tape. Support for the NAME, PCID, and TIME input parameters was added. Use these input parameters to print the PIU data for a specific resource name, procedure correlation identifier (PCID) or time stamp. In addition, support for new PIUPRT formatting keywords has been added. Use COMPACT, FORMAT, or LONG to specify the format of the PIU trace table.
The TPF 4.1 system no longer supports program test vehicle (PTV) phase I (unit test).