× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: S/36 F-spec allowed dotted names? was: EXTNAME questions...
  • From: "Dan Bale" <dbale@xxxxxxxxxxx>
  • Date: Mon, 1 Nov 1999 16:20:55 -0500



Chris,

I would agree that, if you _were_ once allowed to use a dot in the filename in
an F-spec in any flavor of RPG, then you should be able to today.

However, if my memory serves correctly (and I'll be the first to admit that it's
not always so), dots were never allowed in the F-spec filename, not in RPG-II,
RPG-III, or RPG-IV.  Got a syntax error from both SEU and the compiler when I
specified a dotted file name in RPG36, RPG, & RPGLE on a V4R2 box.

>From the "System/36-Compatible RPG II User's Guide and Reference" which, in the
V4R2 softcopy, indicates that it has not changed since V3M0R5 (June 1994), the
following rules for the File specification:

   Every file used in a program must have a separate name.  The
   first character must be alphabetic.  The remaining characters
   can be any combination of alphabetic and numeric characters;
   however, special characters are not allowed.  Blanks cannot
   appear between characters in the filename.  The filename can be
   from one to eight characters long and must begin in column 7.

Barbara mentioned the fix for EXTNAME that Brad mentions.  Wierd that Hans &
company would allow a dotted file name for that but not for F-spec filenames.  I
agree that it would make sense to allow any legitimate AS/400 object name to be
used on the F-spec.  But to call it a bug would imply that you once had that
feature.  Hans, Barbara?

- Dan Bale

Chris Bipes wrote:

Actually with a S36 RPG II program you must have the OCL file statement for
all files, even if the object name is the same in the F spec and does not
contain the dot.  And no the S36 will not fail, but all S36 applications I
have ever seen us the dot to separate the system from the file name.  i.e.
AR.CUST is the customer file for Accounts Receivable.  If IBM said today,
You can not put a dot in an object name, all S36 applications, I have ever
seen, would have to have their files renamed and the ocl file statements
update to the new file names.  That is what I meant by the S36 environment
would fail.  I just wish that IBM would be more consistent on object naming
rules.  If the object can have a dot, all applications that reference the
object should be allowed to use it with the dot.  That is what bugs me.





+---
| 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 thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.