RE: Efficient Code

Thanks for the follow-up, Walden.  I still wonder if this is a new "feature"
or not, but icbw.  However, that is inefficient design no matter what.  I
can't imagine it would be ALL that difficult, when LF_B is created to switch
the *ACCPTH for LF_A to use LF_B.  Yeah, locks, but it could be done at IPL
time if necessary.

What do you mean "see the indexes"??

Good point about FIFO, etc.  I've never tried, but would READE on LF_B and
LF_C be retrieved in FIFO or in order by Field2 (which is what I would
guess)??

| -----Original Message-----
| [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Walden H. Leverich
| III

| Nope, just double checked on V5R2. If you create them in the
| wrong order (A,
| A+B, A+B+C) there is no sharing.


| I wonder if there is a way to see the indexes on a system.
|
| Also, remember FIFO, LIFO, FCFO are all considered "keys", to get sharing
| you need to leave the ordering unspecified.