Re: Prestart Jobs for speeding up TCP/IP servers

Hello Jon,

Am 25.10.2021 um 23:44 schrieb Jon Paris <jon.paris@xxxxxxxxxxxxxx>:

I may be missing your point Patrick - but your comment re persistence of CGI jobs is not correct.

Thanks for pointing out the details.

What you _can't_ control without going the persistence route is whether you get connected to the _same_ instance of a program because your request may be allocated to a different thread.

That wouldn't matter in my case. Transactions running over the TCP connection are "complete", that means within one TCP connection all read/writes are done at once.

you can also have a pre-start job that just runs its own sockets interface - for example. Any non-interactive job can be restarted and will persist as will the state of the programs running within them unless you take actions to have them terminate.

Hmm! Big picture mode: Do you imply I can define prestart jobs to an SBS, start them once via strpj and then let them handle the incoming socket connections? There's no "trigger" needed from APPC to actually change the prestarted job state to "run"?

How is this related to named activation groups? PJs seem to be a nice way to have everything set up for running at IPL time with ease. strsbs, done. :-) Correct?

As you may see from my questions, I still struggle to grasp the concept of programs being activated but not running (or waiting for some event): AFAIK this is some novelty only OS/400 brought up. :-)

I'll re-read the ILE Concepts manual in the next days. :-)

:wq! PoC