when someone creates a library and tables via SQL remotely on IBM i, and decides to get rid of that some soon after, deletion (drop schema) fails for mainly two reasons.
First, there is a shared lock being held on the library from a spawned qzdasoinit. The ODBC client seems stuck. Qzdasoinit stays for prolonged time even if the remote side has closed the connection due to being impatient.
Second, creation of libraries via SQL automatically creates objects for journaling. If there was no save in the meantime, the OS posts messages if it's okay to delete any unsaved receiver. This isn't visible for ODBC clients, and again, the client seems stuck.
I guess others have observed this behavior before. Is there anything I can do to not intervene as an admin, ending qzdasoinit manually, and afterwards deleting the library, while answering "ignore" to not saved journal receivers being deleted?
Thanks!
:wq! PoC
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
