![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
EQU ANS1 TO PARAM(1) (Will not display the data 'Symbol not > found'.) |
|
PS. I can't use RAID on a SUBROUTINE. I get the following error 'Cannot RUN a subroutine that has arguments.' |
|
What can I do the view the data in ANS1? |
#3
| |||
| |||
|
|
EQU ANS1 TO PARAM(1) (Will not display the data 'Symbol not > found'.) so true! you have to call it "PARAM(1)" when talking to RAID. I'm sorry. By the way, in recent releases of UV they now let us examine individual elements of a dynamic array: e.g.: CUST.REC<30,6,2>/ That's nice, but I digress. PS. I can't use RAID on a SUBROUTINE. I get the following error 'Cannot RUN a subroutine that has arguments.' You need a harness that you can run and fill in the input arguments. RAID that. Or for complicated cases, stick DEBUG statement in the sub or right before the call you care about & run the program that normally calls it. What can I do the view the data in ANS1? the command is "PARAM(1)/" Likewise to assign a new value ("!" comand), or setting breakpoints. E.g.: :: PARAM(1)/ STRING: T r L=4 `'NO'' :: PARAM(1)!'YES' PARAM(1) was STRING: T r L=4 `'NO'' . Now is STRING: T r L=5 `'YES'' :: Have you tried the UniDebugger on the UV client CD? Last fall's IBM conference had a really slick demo of a pgmr tool they are developing, but it was definitely not even beta yet. It includes a debugging interface, completely separate from unidebugger. The s/w engineer was wanting feedback & took suggestions. I believe the EQU irritant was mentioned. But that doesn't help today, does it? cds |
![]() |
| Thread Tools | |
| Display Modes | |
| |