RE: EXTNAME questions... -- RPG400-L

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.

Christopher K. Bipes     mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst   mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.         http://www.cross-check.com
6119 State Farm Drive    Phone: 707 586-0551 x 1102
Rohnert Park CA  94928 Fax: 707 586-1884

*Note to Recruiters
Neither I, nor anyone that I know of, is interested in any new and/or
exciting positions. Please do not contact me.


-----Original Message-----
From: Dan Bale [mailto:dbale@genfast.com]
Sent: Friday, October 29, 1999 6:48 AM
To: RPG400-L@midrange.com
Subject: Re: EXTNAME questions...




Brad, Chris:

As someone else mentioned, RPG (all flavors) have more restrictions on names
than the operating system.  Hey, up until RPG IV, you were limited to 8-byte
file & record names and 6-byte field names.

Chris, how does the "S36 environment fail if you do not allow the dot in the
name"?  As I remember it, you were not allowed to use a dot in the file name
on
the F-spec in _any_ flavor of RPG.  You _had_ to use the OCL "FILE
NAME-ARCUST
LABEL-AR.CUST" to use dotted file names.  Am I mistaken on this?

Anyway, Brad, I'm sure you won't be banging your head on this one for too
long.
The RPG manual states that dots are not allowable and that's that!  You have
far
too many other important problems to solve.

- Dan Bale


Stone, Brad V (TC OASIS) wrote:

 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?


Chris Bipes wrote:

That's a bug to me.  Sort of like not being able to reference S36 flat files
i.e. AR.CUST.  I have questioned this for years....  But now for FTP or
other such programs the dot separates the file name from the member name.
Hmmm  What would be the best way to approach this?   If you do not allow the
dot in the name, S36 environment fails.  Also try to FTP the file
"library/file.name.memeber".  I set a shop standard to put a "V" where you
put the dot to specify the version of the file.  Why did IBM use a "." to
separate the member name for some actions and not bracket the (member)?
+---
| 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
+---