Barbara,
Thanks. I just could not remember if I could condition all primary and secondary files. I cannot think of a reason (even remotely) where one would have to consider this method for full procedural tables since we can manually Open/Close those types of tables.
As far as the maintainability of the program, I guess that would vary. In this particular case it actually makes maintenance easier because it cuts down the number of programs that I have to maintain from two to one. Perhaps not a big deal, but I'm lazy. For example, an old package that we use has two data entry programs for manually entered orders: one to get pricing from our price tables and the other to allow manual overrides (this one is restricted to managers). Identical except for the manual price override field on the panel. I mean, even in RPG II (which these are) setting non-display on/off and maintaining only one program would have been real easy.
Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Barbara Morris
Sent: Thursday, August 21, 2008 4:18 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Cycling - MUltiple Input Files
Jerry Adams wrote:
...
What I would like to do is use the EXTIND(*INUx) keyword to condition
the two files; one as IPE the other as ISE. The CL that drives this
would set the appropriate switch. What I am not sure about is
whether or not this is permissible; can't recall ever doing this in
even RPG II, and the manual didn't answer the question. I can simply
make the changes and see what happens, but I thought if anyone knew
that this won't fly it was save me some time.
...
Jerry, that should work to use EXTIND on both files. What question were
you looking for an answer to? Are you wondering about the different
record length for the primary and secondary files, or are you wondering
about using EXTIND on the primary file?
There aren't any rules about the record length of the primary and
secondary files having to be the same. Even if you use matching
records, it's only the field lengths that matter.
And I don't think there are any rules on what type of file you can use
EXTIND with.
(Just as an aside, I find the whole EXTIND thing a bit creepy. I would
hate to maintain a program that used EXTIND.)
--
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.
midrange.com
