Re: Who's On *First?

["Crispin Bates" <cbates@xxxxxxxxxxx>]

The *First member is the first member added to the file. Not the first 
alphabetically...


----- Original Message ----- 
From: "Robert Munday" <rwmunday@xxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, April 24, 2008 12:12 PM
Subject: Who's On *First?


> Fellow Midrangers,
>
>
> In my current shop, they have a CL routine which makes backup copies of 
> the members in an output file leaving the original named member plus up to 
> nine copies.  Each time it runs, MEMBER9 is deleted, MEMBER8 becomes 
> MEMBER9, MEMBER7 becomes MEMBER8 and on and on.  At the end, MEMBER is 
> copied to MEMBER1, then MEMBER is cleared.  This clear member is used for 
> the next output operation.  Eventually there will be ten members in this 
> file.  How can I be certain that when I specify file FILEA, member *First 
> that I will be getting MEMBER and not MEMBER6 or some other undesired 
> member?  For now it looks as if I will need to include an override in my 
> CL to override FILEA to member MEMBER and not member *First.
>
> Is this my solution?  The CLs I am using appear to assume that the *First 
> member is the desired member.
>
> Thanks,
>
>
>
> Robert Munday
> Munday Software Consultants
> Montgomery, AL
> on assignment in Columbia, SC
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.