RE: Using Members within a PF

I've seen multi membered work files as one way to handle concurrent access.

It kind of sounds like that's what's going on in your case. With each plant
having its own member,
the member for one plant can be cleared without affecting the others.

Remember, it's Clear Physical File Member (CLRPFM) not Clear Physical File.

It's old style. But if the order of the records in the PF matter, or the
files/programs can't process
by PLANTID it's the easiest way. Otherwise instead of doing a CLRPFM, you'd
have to just delete the
records as you process them and then you'd want REUSEDLT(*YES) or you'd end up
with lots of deleted
records and need a RGZPFM.

HTH,
Charles

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Brian Piotrowski
Sent: Tuesday, July 10, 2007 10:09 AM
To: Midrange Systems Technical Discussion
Subject: RE: Using Members within a PF

Ok, thanks for the clarification.

Now does it make sense to have multiple members attached to a
work file?
This PF that has the three members attached - the original
member, and one for each of the plants (P1 and P2). There
are several programs that run that will clear write to and
clear out of this PF several times a day. Based on what
Nathan mentioned in his response, it would make sense if the
data was to be retained, but in this case it is only retained
until the report is printed and then it is nuked.
Furthermore the number of records written is not substantial
enough to warrant the additional layer of filtering. I
really don't see any advantage in this case.

Any advice?

Thanks!

/b;

-----Original Message-----
From: Wilt, Charles [mailto:WiltC@xxxxxxxxxx]
Sent: Tuesday, July 10, 2007 9:21 AM
To: Midrange Systems Technical Discussion
Subject: RE: Using Members within a PF

Uh, no. <grin>

A file doesn't contain data records.

A file contains members. Members contain data records.

Every PF has at least one member, (if you want to store any
records anyway).

Logical file members point to one or more PF members.

HTH,
Charles

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Brian

Piotrowski

Sent: Tuesday, July 10, 2007 9:04 AM
To: Midrange Systems Technical Discussion
Subject: Using Members within a PF

Hi All,



I've been going through the code with a fellow programmer here at
work, and we've noticed that the original programmers

created physical

files and then added members to the file.
The programmers have then created a logical file on top of the
original physical file and use these members within the RPG code.



Can some please explain what advantage there is to this practice?
Wouldn't the logical file negate the need for the members

within the

physical file?



The practice of adding members to physical files does not

appear to be

the case for most of the PFs in our system - only a few of the work
files exhibit this trait. Would we be better off to eliminate the
members and just use the straight LFs for our work?



Thanks,



/b;



-=-=-=-=-=-=-=-=-=-=-=-=-=-
Brian Piotrowski
Assistant Mgr. - I.T.
Simcoe Parts Service, Inc.
Ph: 705-435-7814 x343
Fx: 705-435-6746
-=-=-=-=-=-=-=-=-=-=-=-=-=-



--
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.

This e-mail transmission contains information that is
intended to be confidential and privileged. If you receive
this e-mail and you are not a named addressee you are hereby
notified that you are not authorized to read, print, retain,
copy or disseminate this communication without the consent of
the sender and that doing so is prohibited and may be
unlawful. Please reply to the message immediately by
informing the sender that the message was misdirected. After
replying, please delete and otherwise erase it and any
attachments from your computer system.
Your assistance in correcting this error is appreciated.

--
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.



--
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.

This e-mail transmission contains information that is intended to be
confidential and privileged. If you receive this e-mail and you are not a
named addressee you are hereby notified that you are not authorized to read,
print, retain, copy or disseminate this communication without the consent of
the sender and that doing so is prohibited and may be unlawful. Please reply
to the message immediately by informing the sender that the message was
misdirected. After replying, please delete and otherwise erase it and any
attachments from your computer system. Your assistance in correcting this
error is appreciated.