RE: Word of advice: Dont' close a socket you didn't create.

Thanks. I was worried for a second there.

-Walden

------------
Walden H Leverich III
President
Tech Software
(516) 627-3800 x11
(208) 692-3308 eFax
WaldenL@TechSoftInc.com
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)



-----Original Message-----
From: David Gibbs [mailto:dgibbs@mks.com]
Sent: Monday, April 29, 2002 15:56
To: rpg400-l@midrange.com
Subject: Re: Word of advice: Dont' close a socket you didn't create.


"Walden H. Leverich" <WaldenL@TechSoftInc.com> wrote in message
FAD7A1A61D7EBF49B994F1A4BBDCD3044EEC6B@neptune.techsoftwareinc.com">news:FAD7A1A61D7EBF49B994F1A4BBDCD3044EEC6B@neptune.techsoftwareinc.com...
> So do I understand this correctly? Your job that had absolutely
> nothing to do with the remote command job caused the remote command
> job to fail by closing a socket number that belonged to the remote
> command job? Is that correct?

No ... my job was being RUN inside the remote command job, using the remote
command API (from a client side java program).

Socket zero belonged to the remote command job ... my program closed it.

My program ran to completion fine, but the remote command job couldn't send
the necessary status updates to the remote system because the socket was
closed.

david




_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.