Re: WDSCI-L Digest, Vol 2, Issue 34

Don,

I took your advise and extended my wait time in the timeout value of the
pref_store.ini from 60 to 180. It was line 4 for me though.

One note though. Before I could change the value, low and behold, the
message popped up saying it was timing out.  Wow, is that coincidental or
what.  Guess what, I now had 2 QZRCSVRS jobs running.  The first one when
starting WDSC when it connected (with the correct connection library list),
and the second one(With the wrong library list) was now the active
connection.  So I manually killed the old one.  Disconnected all, and
reconnected and I have not had that message pop up all day since I changed
it.

I have done other work and now have multiples running again though.  I will
email you what I have.  A snap shot of the service jobs and a .log file.
Embedded in the .log file are my comments as to what I was running when the
log was populated.  At this point, I stayed away from the Implementer
plugin functions, since I can replicate the multiple connections without
trying to use them. Debuging seems to be a big culprit with opening new
connections and stranding them.

David,
I will cc you on the log and snap shot of active service jobs as well.

Thanks all for getting me 1 step closer to resolving this thing.

Regards,

Duie





date: Thu, 15 Jan 2004 22:20:39 -0500
from: Don Yantzi <yantzi@xxxxxxxxxx>
subject: Re: [WDSCI-L] Re: RSE Connections Continue To Get Lost or
             Confused?





David,

Which API are you using to get the AS400 object?  The ISeriesConnection
class defines the following 2 APIs for this:

public AS400 getAS400ToolboxObject(Shell shell)

public AS400 getAS400ToolboxObject(Shell shell, boolean createNew)

The first one returns the AS400 object we use for communications, so
anything you run using this API will run in the RSE comm server job with
it's library list, CURLIB, etc...  The second one uses the createNew option
to determine whether you want the same one we use or a new one based on the
one we use.  Passing true will create a new one with the same user ID and
password and will also set any library list or curlib changes the user
specified in the Initial library list properties for the RSE connection but
won't have any changes made to the library list by the user on the fly.  If
you ask for the RSE's AS400 object and then clone it or create a new one
based on it then you will not get the library list and current library
settings, just the user ID and password.

Sounds like you want to just use the first API, or the 2nd one but passing
false for createNew.

We can take this off-line if you think this is not appropriate for the
mailing list.

Don Yantzi
WebSphere Development Studio Client for iSeries
IBM Toronto Lab
Phone: (905) 413-4476
IBM internal:  IBMCA(yantzi)  -  Internet: yantzi@xxxxxxxxxx

















________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service.