Is the message coming from the submitted job or from the QZDASOINIT job where your DB2 connection is running?
Your connection job will not wait for the submitted job to run or complete unless you've done something explicitly to make it wait.
Memory allocation for the submitted job is controlled by the job description it picks up from the subsystem monitoring the job queue and the run type. You might want to look at that *JOBD.
QZDASOINIT jobs are autostart jobs and are meant to hang around waiting for a new connection request. The jdbc connection itself you should close in the same class you used to open it. If you are using a connection pool, the close method will return the connection to the pool and the QZDASOINIT will remain connected for quick reuse.
<div>-------- Original message --------</div><div>From: Praveen Enukonda <praveen.as400.java@xxxxxxxxx> </div><div>Date:09/30/2014 1:45 PM (GMT-06:00) </div><div>To: java400-l@xxxxxxxxxxxx </div><div>Subject: Additional 17 megabytes of storage allocated for this job </div><div>
We have web application that calls DB2 stored procedures for business
Db2 stored procedure inturn calls an external CL program that submits a job
I have a couple of questions on this and I would appreciate if anyone could
1) Whenever DB2 stored proc is invoked by web application, system allocates
16 to 17 MB additional storage space to the existing memory, Is it because
the stored proc submits a job in batch and is waiting for the job to be
job log message:-
Job 766200/LIBRARY/JOB submitted to job queue XXX in library
Additional 16 megabytes of storage allocated for this job.
Cause . . . . . : The data access server for this job has used 17
of storage and needs more storage to continue processing. Another 16
megabytes of storage has been requested.
Recovery . . . : If the data access server is using too much storage,
determine if there is some storage that can be freed or if there is a
different way to run the requested functions that will use less storage.
2) JDBC connection is held up even after of the job is completed and is
like a zombie connection. Is it because system wants to reuse this jdbc
connection upon another request?
Any inputs on this would be highly appreciated.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2021 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.