Using Caché ObjectScript - InterSystems Documentation

Command-line Routine Debugging
5. Start and enter Caché.
6. Issue your trace command:
ZBREAK /T:ON:"/dev/tty01"
7. Run your program.
If you have set breakpoints or watchpoints with the “T” action, you see trace messages appear in the window
connected to /dev/tty01.
• OpenVMS — To send trace messages to another device on OpenVMS platforms:
1. Log in on TTA1:.
2. Verify the device name by entering the following command at the DCL prompt:
$ WRITE sys$output f$getjpi("","TERMINAL")
TTA1:
3. Issue the PROTECTION command so you have write privileges to the terminal:
$SET PROT=W:rwlp TTA1:
4. Issue the following command to avoid contention for the device:
$WAIT 1
5. Return to your working window or to a terminal where you are logged in on your principal device.
6. Issue the following command to set your process privileges to share:
$SET PROC/PRIV=share
7. Start Caché.
8. Issue your trace command:
ZBREAK /T:ON:"TTA1:"
9. Run your program.
If you have set breakpoints or watchpoints with the “T” action, you will see trace messages appear on the window
connected to TTA1:.
14.1.7.1 Trace Message Format
If you set a code breakpoint, the following message appears:
Trace: ZBREAK at tag2^rou2
If you set a variable watchpoint, one of the following messages appears:
Trace: ZBREAK SET var=val at tag2^rou2
Trace: ZBREAK SET var=Array Val at tag2^rou2
Trace: ZBREAK KILL var at tag2^rou2
• var is the variable being watched.
• val is the new value being set for that variable.
154 Using Caché ObjectScript