Re: Question for socket gurus

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

What do you mean by "forcibly cancel its server job"?   Do you mean 
actually END the server job?  That isn't (and shouldn't) be possible, 
unless code has been written on the server to provide that feature.

Do you mean end the connection to the server?  That should be easy, just 
call close().

Do you mean "interrupt" what the server is doing?  That requires 
changing the code in the server.  You can write the server so that it 
sends a POSIX signal when out-of-band data is received, then have the 
server abort it's processing when it receives the signal (for example, 
by sending an *ESCAPE message to the SQL engine).   Then you trigger 
this behavior by sending OOB data from the client to the server.


James Lampert wrote:
> Given a client job connected through a socket to a server job on an AS/400,
>
> Is there, by any chance, some way I'm unaware of for a client job to 
> forcibly cancel its server job through the socket connection, even if 
> the server job is busy with (for example) some horribly complex SQL 
> call, instead of listening for client requests?