Hello all Proiv Persons out there!

Thanks to our Host Rob Donovan

I was wondering has anyone used the environment variables TRACEALL or FSITRACE
and been able to interpret the voluminous output for debugging/tracing purposes.
Is there any doco on it etc.

David Tuke

Hi,

Well there is no documentation, as I guess this is a 'unsupported / reserved for PRO-IV ltd' feature.

However, this is what I have found out....
TRACEALL

Set it to 1 - 15 to change the amount of detail that gets logged.

Also You can set TIMESTAMP to Y then line in the log also has the time attached.

If you grep 'procfun: entry' from the log it will show you all the function linkages you went through (including global functions).

If you want to reduce the amount of detail try using some of these instead of TRACEALL.

TRACEIO
TRACEMISC
TRACECRT
TRACEMFIN
TRACEMFOUT
TRACELGC
TRACEGEN
TRACEBLK
TRACEFILE
TRACEREC
TRACEGUI
TRACEMEM
TRACESQL
TRACEUSER
TRACEOFF
TRACEDISP


FISTRACE

Set it to DEBUG,ERROR

This is a more readable trace.

I find it usefull to use for those bugs that only happen every 1000000th time. I just set the log going and then look at it later. The only problem is that PRO-IV runs very slowly while the log is on and it creats a huge log file.
Rob

I needed to trace the function flow of an overnight process and keep the .TRC file to a minimum so this is what we used.
It is possible to limit the amount of stuff created by tracing by setting the individual pieces, see

# export TRACEALL=0
# export TRACEMISC=1
# export TRACECRT=1
# export TRACELGC=1
# export TRACEGEN=1
# export TRACEBLK=1
# export TRACEIO=1
# export TRACEFILE=1
# export TRACEREC=1
# export TRACEMFI=1 If you want to set only this one then use TRACEALL and unset the others
# export TRACEMFO=1 If you want to set only this one then use TRACEALL and unset the others
# export TRACEGUI=1
# export TRACEMEM=1
# export TRACESQL=1
# export TRACEUSER=2 allows function identification

As an example you can set the individual items or set TRACEALL say to 8 and then reset the ones you dont want to a zero value.

The trace settings are displayed in the .TRC output an example being :-

tr_init: trace initialised at 99/9/5 12:22:00
tr_env: levels: misc/crt/lgc/gen/blk/io/file/rec/mfi/mfo/gui/mem/sql/user
0 0 0 0 0 0 0 0 0 0 0 0 0 2
As for waht each one does I never found out I just experimented until I found the setting that gave me what I wanted.

Hi,

If you want to log function linkage then try using this...

in csh:

setenv PROSTAT A
setenv RUNSTAT fun_log.txt

Then run proiv and all the function linkages will be logged to the file fun_log.txt.

The file is buffered in memory, so you have to quit proiv before it is written to disk.

It only logs functions NOT global functions.

Also there is a bug in PRO-IV V4.0 and above if you use @TIMEOUT. The function log buffer does not get written to the log file if a timeout occurs and @TFUNCT links to OFF.

Hope this helps.

Rob

The error just mentioned:

Does it also issue forth a Dr. Watson error message about 10 - 25% of the time?

One of our client sites sets almost all of it users to time out (to OFF) after 20 minutes. They end up with Dr. Watson error messages regularly.

They're on 4.0 r 526 / NT 4.0 sp 5 (I believe)

Hi,

We don't have Dr Watson running and I'm guessing that your using the GUI PROIV and we use Green Screen.

After the timeout it links to OFF and then goes back into UNIX. Nothing else happens.

There is ANOTHER bug though. That if the user is in a Global Function (ie a window) and the timeout occurs then rather than going to @TFUNCT it just goes to the question mark!!!!
Rob

I am trying to get set up to find an intermittant divide by zero error in a very complex set of functions that include several multi-level global lscalls. I have set the TRACEALL to 15 and all of the others listed in the 'tr_env' list to zero except for: TRACEMISC=15, TRACEFILE=6, TRACEMFI=15, TRACEMFO=15, TRACESQL=1 and TRACEUSER=15. This seems to get me the most readable result. I have tried many combinations of settings but none gave me the 'procfun:' output and that's the one I'm really looking for. I do get an 'inpfun:' message for the main functions but nothing for the global functions. I'm going to have to infer a global lscall from the opening of GENFILE, I guess. We're using Chess 3.2 and the Pro-IV version is 4.0000, Rev. 5.2.5

Is the 'procfun:' message something from a later Pro-IV version, or have I not discovered the right combination of parameters?

Thanks,

Clare Owens

Hi,

If you set TRACEGUI to level 8 you get 'procfun'

As usuall it's nothing obvious from PROIV!!!, but then it is 'reserved for MSIS use only'.

It's a shame they dont make all these extra bits documented so that every one knows about them, but that would be too nice for us.... it's better to keep us guessing!!!

Also you could use PROSTAT env to get function entry lists, but there is a bug with that if you use @TIMEOUT anywhere, but the response I got from PROIV support was that PROSTAT is going to be removed as it is not supported, although it's in the manual. I have contested that!!

Rob