RE: CPF7354 Excessive Physical Members for a Logical

Someone ran a RSTLIB or RSTOBJ when the member level id differed, and 
specified MBROPT(*ALL) ALWOBJDIF(*ALL)- the system renamed the existing 
member with an '0001' '0002' etc. at the end, and restored the saved 
member under the original name.

          Allow object differences (ALWOBJDIF) - Help 

 o  If there is a file level mismatch and *ALL is specified on this 
    parameter and the Data base member option prompt (MBROPT 
    parameter), the existing version of the file is renamed and the 
    saved version of the file is restored.  If there is a member 
    level mismatch, the existing version of  the member is renamed 
    and the saved version of the member is restored. 


Neil Palmer      DPS Data Processing Services Canada Ltd.
50 Acadia Avenue, Ste.102                   AS/400~~~~~
Markham, Ontario, Canada.   ____________          ___  ~ 
Phone:(905) 474-4890 x303   |OOOOOOOOOO| ________  o|__||= 
Cell.:(416) 565-1682 x303   |__________|_|______|_|______) 
Fax:  (905) 474-4898         oo      oo   oo  oo   OOOo=o\ 
mailto:NeilP@DPSlink.com  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
http://www.DPSlink.com     iSeries 400  The Ultimate Business Server





"Richard Casey" <casey_r@popmail.firn.edu>
Sent by: owner-midrange-l@midrange.com
2001/04/10 10:54
Please respond to MIDRANGE-L

 
        To:     <MIDRANGE-L@midrange.com>
        cc: 
        Subject:        RE: CPF7354 Excessive Physical Members for a Logical


Chris,

I found my problem. The logical files had 2 members in them (even though
MAXMBRS for the file was 1). One member was the same name as the file and
the second one was the name of the file followed by 0001. My RMVM only
removed the first one so the ADDLFM failed. I changed my RMVM to remove 
*ALL
members and that solved the problem. Thanks for the pointers! Any idea 
where
the 0001 member could have come from? I've seen similar naming when doing 
a
restore, but I don't know if the renaming goes to the member level.

Richard


-----Original Message-----
From: owner-midrange-l@midrange.com
[mailto:owner-midrange-l@midrange.com]On Behalf Of Chris Bipes
Sent: Tuesday, March 27, 2001 3:03 PM
To: 'MIDRANGE-L@midrange.com'
Subject: RE: CPF7354 Excessive Physical Members for a Logical


Is there a process somewhere that is adding the members back for you?  Are
you basing the LFM back on the original member(s) all defaulting to *all?
If the LFM was based on one PFM then specify that member on the ADDLFM
command.  The outfile from DSPDBR has the member names of the 
dependencies.

Christopher K. Bipes    mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst  mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.        http://www.cross-check.com
6119 State Farm Drive   Phone: 707 586-0551 x 1102
Rohnert Park CA  94928  Fax: 707 586-1884

If consistency is the hobgoblin of little minds, only geniuses work here.
Karen Herbelin - Readers Digest 3/2000

-----Original Message-----
From: Richard Casey [mailto:casey_r@popmail.firn.edu]
Sent: Tuesday, March 27, 2001 10:08 AM
To: MIDRANGE-L@midrange.com
Subject: Re: CPF7354 Excessive Physical Members for a Logical


Chris,

I'm using this technique to remove/add logical files to speed up some file
maintenance tasks on the corresponding physical file. I remove the 
logicals,
perform my maintenance, and then add the logical members back. When I do 
the
ADDLFM, I get a CPF3213 (Members for file xxxx more than maximum allowed)
followed by CPF7306 (Member xxxx not added to file xxxx in xxxx). The
logical files appear to work fine after this happens. Is this ok, or am I
missing something?

Thanks for your help.
Richard
-


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