z/TPF Program Management - IBM

Load z/TPF debugger information
When you run the offline build procedure by using the MakeTPF build solution,
source code is converted into an executable and link format (ELF) module to
produce a shared object. Debug data can be included in this shared object.
The offline loader writes two copies of each shared object to the desired storage
medium: in one of the copies, the debug data is removed; in the other copy, the
debug data remains intact. When running the offline loader, you can use the
@DEFINE control statement in the loader input file to specify whether to write the
shared object with debug data to the desired storage medium.
Note: No debug data is loaded when you use the loader general file loader.
The online load (performed by using the ZOLDR LOAD command or the ZTPLD
command) then writes the shared object containing the debug data to the z/TPF
collection support file system (TFS). The file will be written based on the following
directory structure:
/tpfdbgelf/ab/abcd/ts
Where:
/tpfdbgelf is the root directory
/ab is the first two letters of the program name
/abcd is the four-character program name
/ts is the timestamp given to the shared object by the post-processor.
User exit UELJ determines how many copies of the debug files are kept. You can
use the NODEBUG option in the online loader component to specify that the shared
object with debug data is not to be written to the z/TPF collection support file
system.
If you use the ZAPGM command to change a program that has debug data, the
z/TPF debugger might not display an accurate listing view of the program.
See z/TPF Debugger User's Guide for information about the z/TPF debugger. See
z/TPF Operations for information about the ZOLDR LOAD, ZTPLD, and ZAPGM
commands.
© Copyright IBM Corp. 2005, 2012 85