I'm curious. Do you ever use the NaviQuest SMS test facility? ddk
But first I must trigger some trace data. I found there is an SMS trace, but I wonder if this produces much more than I need. I found a replacement for the WRITE-trace mechanism: I defined a Storage Class that is not used and at the point that I needed the WRITE trace info, I set the SC to this specific SC. By moving this piece of code to different decision points in the SC routine, I found the place where it made the wrong decision. I could define several trace-SCs and at point 1 set SC1, at point 2 set SC2 etc. Thus one can determine which code was executed. A little bit complicated, but an adequate replacement for the missing WRITE information. Kees. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
