At 09:04 10/13/1999 , David Leland wrote: >I was afraid that this was the route I'd have to end up going. It's gonna >be a long arduous task as there are probably a hundred or more potentially >called programs/service programs/subprocedures in this job. What you could do (quick fix, but effective), is to define all of your output parameters with some amount of padding, like an extra 64 or 128 bytes. That way if another program has a parm declared incorrectly, it won't corrupt storage that's actually being used. Obviously, it's better to find the real culprit, but this could help while you're looking... Pete Hall email@example.com http://www.execpc.com/~pbhall +--- | 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: firstname.lastname@example.org +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.