Re: Things that would prevent the deletion of a PF

[Rob Berendt <robertowenberendt@xxxxxxxxx>]

Related objects as Birgitta mentioned is what you probably want.
However, there are other ways of thwarting even QSECOFR from deleting a
table (file).
ALTER TABLE MYLIB.MYFILE ADD RESTRICT ON DROP
Then to delete that file you have to run the following first
ALTER TABLE MYLIB.MYFILE DROP RESTRICT ON DROP
See:
SELECT SYSTEM_TABLE_SCHEMA, SYSTEM_TABLE_NAME, RESTRICT_ON_DROP
FROM QSYS2.SYSTABLES
WHERE RESTRICT_ON_DROP = 'YES'
ORDER BY SYSTEM_TABLE_SCHEMA, SYSTEM_TABLE_NAME

On Wed, Jun 19, 2024 at 1:46 PM <smith5646midrange@xxxxxxxxx> wrote:

> I need to programmatically find everything that would prevent the deletion
> of a PF such as LFs, indexes, etc.  Is there a table or function that I can
> look at to find this information?  I don't want to do a DSPDBR to an
> outfile,  Are there other things that will prevent the deletion of the PF
> that I am not thinking of and where do I look for them to determine if they
> exist (again looking for a table or function not a command to an outfile).
> I'm not worried about object locks.  These will all be obsolete PFs and if
> someone has a lock on it, it needs to fail.
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.