ILE performance considerations

["Jon Paris" <Jon.Paris@xxxxxxxxxxxxxx>]

 >> When the client connects, one of the things that happens is the client
exchanges a kind of hash table with the server and vice versa. Now if I have
ten more clients connect, guess what, the data segment in each of the 11
instances of the *SRVPGM are practically identical.

That is what I suspected you were after.  This is a classic User Space case
I would say.  You don't need shared AGs to do this.  All you need to do is
have the RPG program define the structure as based and have your code
attempt to obtain a pointer to the space.  If it can't get the pointer it
creates the space, loads it and then gets the pointer and off it goes.  A
"Shared AG".

If this was in a shared AG - who, when would it get cleaned up?  What would
most likely happen is that you and OS/400 would disagree about when this
should happen (the cause of the debugger problems I think).  What if you had
_two_ items in the AG and only wanted one cleaned up but the OS thought it
was OK to clear both?  etc. etc.  As I said be careful what you ask for -
you might get it.  With the User Space solution you have full control and
can clean up whenever you want.  With RPG III User Spaces weren't that
practical because of having to use GET/PUT APIs - but now that you can use
based storage they are perfect for this kind of application.

Jon Paris
Partner400