RE: ACS -> Run SQL Script reconnects to same QZDASOINIT after forced disconnect

I've not experienced the QZDASOINIT job keeping any setting from a previous connection.

Every time I disconnect and reconnect, it "starts fresh" and reapplies my JDBC settings.
Even when it reuses the same QZDASOINIT job it had before.

Using Version: 1.1.8.8

One test I've done is to create a table in QTEMP.
Then you disconnect and reconnect. The QTEMP table will be gone.

Chris Hiebert
Senior Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.

From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Niels Liisberg
Sent: Wednesday, October 27, 2021 2:41 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: ACS -> Run SQL Script reconnects to same QZDASOINIT after forced disconnect


Gents - Ladies ;



Suddenly my ACS "Run SQL Script " is behaving strange: Earlier when I

press the "reconnect" button it would spinn up a new QZDASOINIT process

where my initial librarylist, commit settings etc are set accordingly to

the JDBC connect string. Everything worked as expected....



But now it seems to reconnect to the previous QZDASOINIT job - whatever

state it was in.



Look at the job number !!



*[ 10/27/2021, 10:26:12 AM ] Reconnect...*

Connected to relational database Dksrv134 on dksrv134 as NLI -

359475/QUSER/QZDASOINIT using JDBC configuration 'sandbox.icebreak'.





*[ 10/27/2021, 10:31:43 AM ] Reconnect...*

Connected to relational database Dksrv134 on dksrv134 as NLI -

359475/QUSER/QZDASOINIT using JDBC configuration 'sandbox.icebreak'.



My ugly work around is actively killing the job with

cl: sbmjob cmd(endjob 662600/QUSER/QZDASOINIT option(*IMMED))

jobq(qsysnomax);



.. and then click "reconnect";



What am I doing wrong !!



Thank you in advance for your input