Re: PJ Type Jobs

Chamara

ODBC (QZDASOINIT) jobs won't usually end - you don't have to worry about them. They stay around in order to allow other clients to connect, and not to take long to get a connection. They don't take any resources while waiting for a client to connect.

They are supposed to stay around - they are not supposed to go away.

Here is an excerpt from a forum about this -

DSPSBSD SBSD(QUSRWRK)

- Option 10 - Display Prestart Job Entries
- Option 5 - Display details on QZDASOINIT

These entries will let you know how many jobs will be started and how many times a particular job will be used before it ends.

These jobs are supposed to be re-used - so don't worry. Don't set the re-use value to 1, please. Do NOT!! :-)

Vern

On 10/14/2010 6:57 AM, Chamara Withanachchi wrote:

Dennis,

you expect the prestarted jobs to end - is that right? - Yes Once we close
the connection I expect the job also will get ended (But it is not)

Chamara



On Thu, Oct 14, 2010 at 4:46 PM, Dennis Lovelady<iseries@xxxxxxxxxxxx>wrote:

I am not sure I understand your question.

So you are connecting to some system using Java, and when you end your
connection you expect the prestarted jobs to end - is that right? So that
you know, PJ are prestart jobs, and those are automatically restarted by
the
system if they end. You can DSPSBSD for the subsystem in which those jobs
are running, and use option 10 to see the PJ entries. Does that help?

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"A problem well stated is a problem half solved."
-- Charles F. Kettering

We are connecting to our IBM i from Java an reading/writing to SB2
files,
even the Java job ends (Closed the connection) we can see some PJ type
jobs
in the system remains. How to overcome this?

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.