Browse Prior Art Database

Productivity Tool for Online Tracing of an Assembly LISTING Using a PER TRACE File

IP.com Disclosure Number: IPCOM000040485D
Original Publication Date: 1987-Nov-01
Included in the Prior Art Database: 2005-Feb-02
Document File: 3 page(s) / 55K

Publishing Venue

IBM

Related People

Telford, RD: AUTHOR

Abstract

This article describes a program called PERAID. PERAID is a tool used for online tracing of an Assembly LISTING file. PERAID is also a good educational tool for stepping through a System 370 Assembly language program. PERAID requires the VM/SP Release 3 or later operating system. This release of VM contains the PER trace facility. PER is a program which monitors events during program execution in a user's virtual machine. For example, each instruction of a program that is executed can be traced by PER. This trace can be captured in an output file. The idea is to relate this output file to the Assembly LISTING file so that the data in the PER file can be used to interactively step through the LISTING online. This can be done using the XEDIT macro called PERAID. XEDIT is the system editor for VM.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 56% of the total text.

Page 1 of 3

Productivity Tool for Online Tracing of an Assembly LISTING Using a PER TRACE File

This article describes a program called PERAID. PERAID is a tool used for online tracing of an Assembly LISTING file. PERAID is also a good educational tool for stepping through a System 370 Assembly language program. PERAID requires the VM/SP Release 3 or later operating system. This release of VM contains the PER trace facility. PER is a program which monitors events during program execution in a user's virtual machine. For example, each instruction of a program that is executed can be traced by PER. This trace can be captured in an output file. The idea is to relate this output file to the Assembly LISTING file so that the data in the PER file can be used to interactively step through the LISTING online. This can be done using the XEDIT macro called PERAID. XEDIT is the system editor for VM. The user calls XEDIT to display his program LISTING file. He then executes PERAID from the command line of XEDIT. Below is an example of how PERAID could be useful. A user has written an Assembler program and wishes to step through the execution of the program to ensure that all the proper instructions are being executed. Normally, a user would print out his LISTING file, and look at the printout while stepping through the program online using PER. This method is cumbersome and is made obsolete by PERAID. Using PERAID, the user would do the following: 1. Produce a PER TRACE file. A PER TRACE file is a log of a particular PER run. For example, if a user wants a

record of every instruction executed during the running

of a program, he could issue the command 'PER I R

xxxxxx.yyyy P RUN', and then execute the program

(xxxxxx = the load origin of the program, and yyyy =

length in bytes of the program). While the program is

running, PER will output a line to the virtual printer

for every instruction in the range xxxxxx.yyyy. Each

line contains the memory offset location, the

instruction op code, related storage locations, and the

condition code. Once the program has finished

executing, the user can transfer this print file to his

reader, and read it in as a permanent file. 2. XEDIT the

LISTING file and execute PERAID from the XEDIT command line. PERAID will first prompt for the

name of the PER TRACE file. Next, PERAID will ask for

the offset of the program when it was executed. The

reason for this is because LISTING files always are

produced with the offset from 000000. This offset

value is located in the first column of the LISTING

file. Once the value of the true memory off...