Capture parms passed in batch job

I have a program that when I test runs fine and gives correct results.  This
same job when called in our nightly processing gives incorrect results.  I
think (???) it may be a parameter getting "toasted" somewhere before program
is called.  The program that calls the program in question is a monster and
uses a LOT of files.  I could recreate all the files into a non-production
environment and debug but was I was looking for was:

Is there a quick and dirty way to capture the parms being passed to the
program in question and capture parms passed back into a file, etc. so I can
review after the nightly run

The only way I could think of was to insert a program to write records to a
new file (fields being parms passed) immediately before calling program in
question and again immediately after calling program in question.

Any better ideas...........

Mark Allen
IS Manager
Kelly's Kids
markallen@kellyskids.com

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---