|
Or make it a based DS and Eval pDataStr = %Addr(buffer) Eric DeLong Sally Beauty Company MIS-Sr. Programmer/Analyst 940-898-7863 or ext. 1863 -----Original Message----- From: Joel Fritz [mailto:JFritz@sharperimage.com] Sent: Wednesday, March 27, 2002 1:35 PM To: 'rpg400-l@midrange.com' Subject: RE: Should be data structure as Parm to procedure Should have mentioned that the work around in the more primitive releases of the OS that some of us are working with is to give the data structure in the procedure a different name, assign it the value of the parm, and then assign the data structure back to the parm when you're done. I don't like it either. <g> > -----Original Message----- > From: Joe Pluta [mailto:joepluta@PlutaBrothers.com] > Sent: Wednesday, March 27, 2002 11:27 AM > To: rpg400-l@midrange.com > Subject: RE: Should be data structure as Parm to procedure > > > Duh. Should have changed the subject. > > > Howdy folks! > > > > I'm trying to pass a data structure to a procedure, and I'm > having some > > trouble defining the parameter in the procedure: > > > > P CX_GENERATE b > > D pi > > D buffer 2000A > > > > D buffer DS 2000 > > D bufary 8A > overlay(buffer:1) dim(250) > > D bufwmk 16A overlay(buffer:1) > > > > Basically, I want to pass in a 2000 byte buffer, which is > redefined as a > > data structure. The compiler says I'm defining the name > "buffer" twice. > > Can this be done? > > > > Joe > _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l or email: RPG400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
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.