Skip to main content

Assume I have two instances of the runcbl running. Each running an extend cobol application. Designate them A and B. Can A do something that would interrupt an accept statement that B was doing?  (And preferably in such a way that B knows A did the interrupt and can get some information. Just like the thread "SEND", but between two separate runtime instances.)

 

I've figured out one way to do it, but it requires creating a socket service program to route socket messages between the processes, and each runtime session would have to spawn a thread that connected to the service so messages could be received from the socket, then internally "sent" to the IO thread.  I don't need this feature badly enough to write the code to do all that,  so I'm hoping someone else has already solved this or has a better idea.

Assume I have two instances of the runcbl running. Each running an extend cobol application. Designate them A and B. Can A do something that would interrupt an accept statement that B was doing?  (And preferably in such a way that B knows A did the interrupt and can get some information. Just like the thread "SEND", but between two separate runtime instances.)

 

I've figured out one way to do it, but it requires creating a socket service program to route socket messages between the processes, and each runtime session would have to spawn a thread that connected to the service so messages could be received from the socket, then internally "sent" to the IO thread.  I don't need this feature badly enough to write the code to do all that,  so I'm hoping someone else has already solved this or has a better idea.

One option would be to consider using Websphere ... www.microfocus.com/.../BKITITMIDDS001.html

Assume I have two instances of the runcbl running. Each running an extend cobol application. Designate them A and B. Can A do something that would interrupt an accept statement that B was doing?  (And preferably in such a way that B knows A did the interrupt and can get some information. Just like the thread "SEND", but between two separate runtime instances.)

 

I've figured out one way to do it, but it requires creating a socket service program to route socket messages between the processes, and each runtime session would have to spawn a thread that connected to the service so messages could be received from the socket, then internally "sent" to the IO thread.  I don't need this feature badly enough to write the code to do all that,  so I'm hoping someone else has already solved this or has a better idea.

Interesting, very interesting, but I suspect those routines do not interrupt an accept statement. In which case I have to have a client thread to talk to websphere (using non-blocking reads) and send a thread message to the screen IO thread when a message is detected. Basically same as my idea but using websphere instead of a home-grown socket message server.