Re: Multi-membered file question?

        A small note,    When ever displaying what members are in what file,
(Dspfd, etc)  the list will be sorted alphabetically.

        If you do a OVRDBF  MBR(*ALL)   and process the file sequential,
You will go thru the members chronologically.    This
        can be viewed by displaying the MEMBER name in the File Information
Feedback Data Structure or by viewing your
        joblog  (ie  "CPFxxxx   Moving from member  xxxxxx to member yyyyyy"
)


        John Carr

        (Ya,  I'm back)




        From:   Don@dr2 on 07/11/99 11:40 AM
        To:     Al Barsa@barsa2@ibm.net@SMTP@EXCHCONNECT
        cc:     MIDRANGE-L@MIDRANGE-L@midrange.com@SMTP@EXCHCONNECT 

        Subject:        Re: Multi-membered file question?



        Al,

        I would also add that a vanilla ovrdbf isn't the cureall it used to
be.
        They should also check the job scope parameters as in MOST cases
you're
        going to find that the ovr is for that stack level and that one must
        specify *job for both scope parms...

        Don in DC

        On Sun, 11 Jul 1999, Al Barsa, Jr. wrote:

        > At 07:31 AM 7/11/99 -0400, you wrote: 
        > 
        > >>>>
        > 
        > <excerpt>Hi fellow listers,
        > 
        > If a program processes a multi-membered file (without first
setting
        > OVRDBF to point to the member to process) what member will be
processed? 
        > If it is the first member?  Do I determine the first via DSPFD
        > xxxxlib/filename *MBRLIST?
        > 
        > </excerpt>
        > 
        > The AS/400 multi-membered file implementation is not as god as we
would
        > like.  The answer to your question is that the member that will be
        > processed is the member that was added first.  The simple solution
is to
        > *ALWAYS use an OVRDBF command before processing a multi-membered
file.
        > 
        > 
        > Al
        > 
        > 
        > 
        > 
        > 
        > 
        > 
        > +--------------------------------------------------+
        > 
        > | Please do not send private mail to this address. |
        > 
        > | Private mail should go to barsa@ibm.net.         |
        > 
        > +--------------------------------------------------+
        > 
        > 
        > Al Barsa, Jr. - Account for Midrange-L
        > 
        > Barsa Consulting, LLC.        
        > 
        > 400 > 390
        > 
        > 
        > Phone:        914-251-1234
        > 
        > Fax:  914-251-9406
        > 
        > http://www.barsaconsulting.com
        > 
        > http://www.taatool.com
        > +---
        > | This is the Midrange System Mailing List!
        > | To submit a new message, send your mail to
MIDRANGE-L@midrange.com.
        > | To subscribe to this list send email to
MIDRANGE-L-SUB@midrange.com.
        > | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
        > | Questions should be directed to the list owner/operator:
david@midrange.com
        > +---
        > 

        +---
        | This is the Midrange System Mailing List!
        | To submit a new message, send your mail to
MIDRANGE-L@midrange.com.
        | To subscribe to this list send email to
MIDRANGE-L-SUB@midrange.com.
        | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
        | Questions should be directed to the list owner/operator:
david@midrange.com
        +---



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---