How do you trace through an EG stored process?

[dbdinc]

I have written a stored process that works except for one piece, where it looks like a parameter does not get accepted. Is there a way to trace through the logic of a stored process, and if there is, would someone be kind enough to let me know how?

Thank you .... I appreciate the folks on this forum and your knowledge.

 

[ChrisW75]

Hiya,
As far as I'm aware there's not a specific tool for doing this, but then I've not had any opportunity to play with stored processes. Does a stored process still generate a log though? My usual method for debugging things which don't generate any useful information themselves is to put in lines of code to add useful messages. A put statement added to the code will write info out to the log, so you can tell it to write out the value or a variable, or a simple mesage to show the a certain piece of code is executing.
If the stored process is out of your control, then you might be able to increase the information you're getting out of it by setting some SAS options, try this:-

options symbolgen mprint mlogic notes source source2;

this should increase the amount of information being written out to the log. Symbolgen tells it to write out all the macro variable values as they are used, mprint and mlogic write out macro code as it is processed, notes and source are default settings, and write out the usual source code and notes ater each step, source2 writes out the source code of any code that has been %included into the program, this may include stored processes. I hope that this helps.

Chris
Business Analyst, Code Monkey, Data Wrangler.
SAS Guru.

 

[dbdinc]

Thanks for the information. I'm really surprised that there is not an "easy" trace mechanism to insert into code.

I'll try your symbolgen option and see what it reveals.

Thanks for responding....I appreciate it!