|
Yep -----Original Message----- From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com] On Behalf Of Richard B Baird Sent: Thursday, August 22, 2002 10:50 AM To: rpg400-l@midrange.com Subject: Re: Same prefixes (was Re: It's That Time Again! etc.) Thanks Barbara, that explains it. I hadn't thought of using the prefix as the qualifier. I probably should have looked at the example in the manual a little closer. so, after looking at that example, it appears that a 'drop prefix' already exists, you just have to replace it with something. for instance: file1 xxcust xxname file2 yycust yyname F file1 if e disk prefix('F1.Z':2) F file2 if e disk prefix('F2.Z':2) D F1 e ds qualified extname(file1) D prefix('Z':2) D F2 e ds qualified extname(file2) D prefix('Z':2) field names are now F1.ZCUST, F1.ZNAME, F2.ZCUST and F2.ZNAME - which would then enable a future evalc qualified move corresponding function, that the original poster (don't remember who) wanted. Right? Rick --original message------ Richard, if you want to read an ext-desc file into a qualified data structure, you use a qualified PREFIX on your F spec. Fmyfile IF E PREFIX('MYDS.') D MYDS E DS QUALIFIED EXTNAME(myfile) or Fmyfile IF E PREFIX('MYDS.XY') D MYDS E DS QUALIFIED EXTNAME(myfile) D PREFIX('XY') In V5R2, you can use a data structure in the result field for externally-described files. _______________________________________________ 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-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.