|
My guess is that it's not a valid symbolic name in RPG. The manual sez: The following rules apply to all symbolic names except for deviations noted in the description of each symbolic name: The first character of the name must be alphabetic. This includes the characters $, #, and @. The remaining characters must be alphabetic or numeric. This includes the underscore (_). Doesn't answer your real question though. Seems like you should be able to use a valid file name in a program. I notice it doesn't work on an F spec either. There must be some way around it. Ezview and DBU don't seem to have any trouble with files that have periods in their names. > -----Original Message----- > From: Stone, Brad V (TC OASIS) [mailto:bvstone@taylorcorp.com] > Sent: Thursday, October 28, 1999 11:31 AM > To: 'RPG400-L@midrange.com' > 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 +---
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.