×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Hi Ken,
Yes, that is one way of doing things. It is the way we are stuck doing it
today. I just don't happen to enjoy it.
-Bob

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Ken Sims
Sent: Monday, January 24, 2005 3:21 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: RNX1011 Error

Hi Bob -

>I hate having to code:
>   CustNo  Chain CustRec
>           If         NOT %Found(CUSTMAST)
>
>...coding the format name on the CHAIN and then the file name on the
%FOUND.
>What a crazy, crazy design. It should all be file name.
>I would go so far as to say that RPG IV should give a warning message
>whenever a format name is used anywhere for single-format database files.

I don't think so.  Personally I detest using the file name on I/O 
statements.  If I change to different logical file, all I want to have to 
change is the F-spec.

I only reference the file BIFs immediately after the operation so I don't 
put in the file name.  If I'm going to want the value later on, I eval it 
into a named indicator.

--
Ken
http://www.ke9nr.net/
Opinions expressed are my own and do not necessarily represent the views of 
my employer or anyone in their right mind.

-- 
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
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 thread ...

Replies:

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

This mailing list archive is Copyright 1997-2026 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.