|
> -----Original Message----- > From: rpg400-l-bounces@xxxxxxxxxxxx > [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Malchow, Grizzly > Sent: Thursday, April 28, 2005 3:55 PM > To: rpg400-l@xxxxxxxxxxxx > Subject: PSDS as parm > Is it possible to pass the PSDS as a parm? If so can anyone tell me how > I would map out the *PROC, *STATUS, *ROUTINE, *PARMS subfields? > I was hoping I could do something like this > D MyPSDS SDS > (pretend I have all of the subfields defined) > D ErrProto PR 10I 0 > D ErrDS Like(MYPSDS) > D RC S 10I 0 > /Free > RC = ErrProto(MYPSDS); > /End-Free > P ErrProto B > D ErrProto PI > D ErrDS 353A > D ProcDS * Inz(%addr(ErrDS)) > D ProcDS_1 DS Based(ProcDS) > This is about as far as I got when I realized I don't know if I can map > out the fields I listed above. > Any ideas? My intention is to call a different program when an exception error is, so I want to keep the integrity of the PSDS in the new program. Also when the new program is called the PSDS from the program with the exception isn't visible. I debugged my program and I was able to get the lengths of the *PROC, *STATUS, *ROUTINE, and *PARMS fields. I think I'll be ok from here. Thanks everyone.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.