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.
>> I appreciate the reply. Unfortunately, I'm not sure which program to
"add the padding" to. There's one program in particular that, when it gets
called, the calling >> program receives the MCH3402 (but only sometimes).
The called program never gets executed. And this program is called from
many different programs. So, I >>c an't debug the called program and the
calling programs - well I'm not sure. As others have mentioned regarding
this, it's likely that the corruption occured in >> some other program well
before this one particular program gets called. There are just so many
different programs in this job.
Dave is it possible to recompile them in a test library (Their RPGIV right?
if not convert them first) with DBGVIEW(*Source).
Start debug and just Step (F10) or step into the called programs(F22) and
follow it one time.
Do a DSPPGMREF to an outfile of each program. That will tell you which
ones call which ones. Match the parms in
Caller/Called programs. It's tedious, but either Debugging (Stepping
into F22) or visibly matching the parms is
the only way.
| 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.