You have to remove the logical file members before you can remove the physical file member. You can do this by deleting the logical files or removing the offending logical file members.
If the logical file is only for that physical file's member why not just delete it? It would not be usable once the physical file member is removed anyway.
If the logical file is over multiple physical file members you'll have to remove the LF member, remove the PF member, and add the LF member again.
If you want to do this programmatically you can use API QDBLDBR to build a list of member dependencies for the LF. The list created by this API has all you'll need to recreate the LF. You spin through it, build a ADDLFM and then run the command.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Essinger
Sent: Friday, October 24, 2014 11:21 AM
To: Midrange Systems Technical Discussion
Subject: Removing logical file members
I have looked and can't find any answer in info center, nor in the list archives. I may not be looking with the right search keywords.
I am on V7R1 TR8 and mostly up to date on PTFs.
Working with a multiple member physical file, with logical files built over it.
If you add a logical file member (ADDLFM) to point to specific physical file member, how do you remove, delete or otherwise blow away that logical file member so the physical file member can be deleted?
When I do a DSPDBR specifying a specific member name, I show 3 logical files that are based on that member name. The only way to see that on the logical file is to do a DSPFD with *ALL information.
Am I going to have to recompile the logical to free up that one physical file member for removal?
Thanks!
Jim Essinger
Western Power Sports
Boise ID
--
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.
midrange.com
