RE: CPF7354 Excessive Physical Members for a Logical

[Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>]

RMVM - on the LF will remove the logical file member and thus the dependency
on PF members.  The ADDLFM on the LF will rebuild it over the members you
specify.  This can be automated by displaying the data base relations to a
file to get a list of LFs over the PF for the specific member you wish to
delete.

Check out:
DSPDBR FILE(LIBR/PHYSICAL)     
       OUTPUT(*OUTFILE)       
       OUTFILE(QTEMP/DEPENDS) 
       MBR(EMPTYMBR) 

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: MacWheel99@aol.com [mailto:MacWheel99@aol.com]
Sent: Tuesday, March 27, 2001 8:25 AM
To: MIDRANGE-L@midrange.com
Subject: CPF7354 Excessive Physical Members for a Logical


from Al Macintyre

I'd like to get rid of empty members on work station addresses that are 
history, but I think this requires

a) kill all logicals on a physical
b) kill unwanted members
c) recompile logicals

Questions

Is there a simpler way to make unwanted members go away without having to 
kill / recompile logicals?
e.g. what is the function of EXPDATE parameter of a member?  Can I change 
that with CHGMBRPF or some such command, to cause a member to expire & go 
away quitely?

DSPFD & DSPDBR seem to show:
what logicals connect to the physical;
what formats & members the physical has.

What tells me which formats & members are in which logicals?
+---
| 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
+---