Re: Lots of QZDASOINIT jobs

James,

1) one of our customers has more than 1000 QZDASOINIT active and they still can work fluently.

The thing is: What kind of applications are connecting? Client/Server? N-Tier applications? Web Applications?

When using Web Applications or N-Tier applications you can use connection pooling:  N connections from application/web server shared between users.

I've seen applications connecting and disconnecting on each command and I can confirm it's a really bad idea.

Memory is cheaper than CPU licenses and connection-disconnection can increase CPU usage. More persistent connections use more memory, but less CPU.

So... maybe having 315 active connections is a good thing.

Regards

Diego E. KESSELMAN


El 29/06/18 a las 12:25, James H. H. Lampert escribió:

I've got a situation where there are lots and lots of QZDASOINIT jobs (315 active, the last time I counted) running on a box. Along with hundreds more that show up in a WRKJOB QZDAZOINIT as "Joblog Pending."

Two questions:

1. 315 active QZDASOINIT jobs sounds to me like it would be a drain on system performance. Am I right?

2. I'm not entirely sure what "Joblog Pending" means (yes, even after looking at the helptext, which doesn't really tell me anything that isn't self-evident). They don't have spool files; what are they doing still in the system at all?

--
JHHL