|
Jeff,
I imagine you have already considered this, but from prior comments,
please make sure that you understand what the client means by Keepalive.
In a prior job, we had an RPG program that sent socket messages to a PC.
One PC program was receiving and staging the sockets messages which were
processed by another PC program that was driving a conveyor system. The PC
program that was driving the conveyors would send regular "KeepAlive"
messages to the RPG program, to be sure that this PC program had not
crashed. If the RPG program determined that that last "KeepAlive" was over
x minutes ago, the RPG alerted the operations staff. In theory, the socket
connection, run by a separate PC program could still be up, but the PC
conveyor program that was driving the conveyors might have crashed, and the
warehouse was idle.
In your case, I'm wondering if they are sending you a specific message
that you are expected to respond to, so they know you are still there. I
kind of expect this is not the case, but I thought I would mention it.
Sam
On 9/2/2015 1:19 PM, Jeff Young wrote:
In a previous post, it was recommended that I use the SO_KEEPALIVE in the--
setsockopt to enable my program to use this.
I have not been able to find any good example on how to set this and how
to
configure the keepalive interval.
Does anyone have an example of this that I can refer to?
Jeff Young
Sr. Programmer Analyst
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.