|
Couldn't you just use the same DS for calling different APIs? That's what I do. Check the error after the call, then you don't need it any more. Brad > -----Original Message----- > From: rob@dekko.com [mailto:rob@dekko.com] > Sent: Thursday, May 10, 2001 9:53 AM > To: RPG400-L@midrange.com > Subject: Re: Another V5R1 query... Qualified DSs > > > > And I have lot's of uses for the new qualified keyword. For > example, I > have programs I've designed to function like API's: output to a user > space, pass back the error structure - that sort of rot. In > these programs > I'll have multiple copies of the error code data structure. > One to return > back to whom called my program and one or more to use when > calling various > API's. Now instead of having to redefine each subfield, or > COPY/PASTE, > COPY/PASTE, I can use the LIKEDS. > > With this, /free, and many other fine features of V5R1, I > can't wait to get > my production machines up to V5R1. > > Rob Berendt > > ================== > Remember the Cole! > > > > > Jon.Paris@hal.it > > Sent by: To: > RPG400-L@midrange.com > owner-rpg400-l@mi cc: > > drange.com Subject: Re: > Another V5R1 query... Qualified DSs > > > > > 05/09/01 03:07 PM > > Please respond to > > RPG400-L > > > > > > > > > > > >> What's the difference between: > > >> 1. using the QUALIFED keyword on a DS > >> 2. specifying PREFIX('dsname.')? > > >> Wouldn't they do exactly the same thing? > > No not really. In the first case the field name does not > change - it can > be identical in multiple DSs. It is referenced via qualification > CurrentRec.PhoneNo and PreviousRec.PhoneNo. > > In the second case the field name is changed by sticking the prefix in > front of it e.g. PhoneNo becomes CPhoneNo and PPhoneNo. > > Effectively it comes out to the same thing (effectiely two differently > named fields) until you consider that with the qualified > option you can now > say that the PreviousRec DS is LIKEDS(CurrentRec) and all the > fields and > their sizes and names come along for the ride! > > > > +--- > | This is the RPG/400 Mailing List! > | To submit a new message, send your mail to RPG400-L@midrange.com. > | To subscribe to this list send email to RPG400-L-SUB@midrange.com. > | To unsubscribe from this list send email to > RPG400-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: > david@midrange.com > +--- > > > > +--- > | This is the RPG/400 Mailing List! > | To submit a new message, send your mail to RPG400-L@midrange.com. > | To subscribe to this list send email to RPG400-L-SUB@midrange.com. > | To unsubscribe from this list send email to > RPG400-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: > david@midrange.com > +--- > +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.
midrange.com
