|
Rob, I understand your point, but in this case the DDS is simply for an external data structure, so I don't have to worry about doing an SQL on it. It's for an internal method of EDI. We version by record so for the ITM02 record, if a new version comes out I simply tack it onto the end so my program knows which one to use when the data comes in. I see a few more emails so I'll look for an answer there. Bradley V. Stone BVS/Tools http://www.bvstools.com > -----Original Message----- > From: Rob Berendt [mailto:rob@dekko.com] > Sent: Thursday, October 28, 1999 2:39 PM > To: RPG400-L@midrange.com > Subject: Re: EXTNAME questions.... > > > I feel your pain, however... > Do not get in the habit of using periods in object names. > For many reasons. > > One, in SQL you'll have to quote the object. Instead of: > SELECT * FROM FILENAME you'll see SELECT * FROM "FILE.NAME" > > Two, SQL naming convention may be set up to use LIB.FILE. > This can be confusing. > > When you start to use IFS commands to access an object imagine: > CPY OBJ('/qsys.lib/rob.lib/aaarob.file') > TOOBJ('/qsys.lib/rob.lib/aaarob2.file') > becoming > CPY OBJ('/qsys.lib/rob.lib/aaarob.file') > TOOBJ('/qsys.lib/rob.lib/aaa.rob2.file') > > > > > > bvstone@taylorcorp.com on 10/28/99 02:25:38 PM > Please respond to RPG400-L@midrange.com@Internet > To: RPG400-L@midrange.com@Internet > cc: > Fax to: > Subject: EXTNAME questions.... > > I have a physical file that I created to be used as an external data > structure. The file is named the following: > > ITM02_1.01 > > Compiled fine, and all. > > Now, when I reference this file in the EXTNAME keyword of my > D Spec, as > shown here: > > D ITM02 E DS EXTNAME(ITM02_1.01) INZ > > It tells me the parameter is invalid. I removed the period, > and it accepts > it. This tells me that it doesn't like the period. > > Now, why can I create a file with that name, but I can't > reference it in the > EXTNAME keyword? > > Bradley V. Stone > BVS/Tools > http://www.bvstools.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 > +--- > +--- | 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.