Re: [7.3, ODBC] Problem with deleting SQL created libraries

Hello,

thanks to a friendly off-list answer, solutions have been established as follows…


Am 06.03.2025 um 14:47 schrieb Patrik Schindler <poc@xxxxxxxxxx>:

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.

chgsysval sysval(qliblcklvl) value('0')

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.

Allow the deletion of unsaved receivers to be answered with the default answer. See wrkmsgd msgid(cpa7025).

Create a duplicate of the existing job description for qzdasoinit, and change the duplicate to use the default reply entry of a message, instead of requesting an answer

crtdupobj obj(qdftsvr) fromlib(qgpl) objtype(*jobd) newobj(qzdasoinit)
chgjobd qzdasoinit inqmsgrpy(*dft)

End the SBS running qzdasoinit, and change the prestart job entry to use the new job description.

endsbs sbs(qusrwrk) option(*immed)
chgpje sbsd(qusrwrk) pgm(qsys/qzdasoinit) jobd(qgpl/qzdasoinit)
strsbs sbs(qusrwrk)

:wq! PoC