| Hi,
I don't know if this will help or not, but a customer I worked with had
a similar situation with everyone trying to log back in simultaneously
after a region crash, sometimes taking up to an hour to recover.
In our case, the delay in the region starting was related to recovering
all the aborted terminal sessions. If you are doing a warm re-start
(and I presume you are...), you should see all the recovery procedures
run for the database, the region and all previously logged in users, before
the region is available for users to log in (all these events show up in
the console.msg file...)
We never did find a way to throttle the number of users logging in. We
had ~150 users, and 20-30 cicsas servers running. Hint - if you haven't
done this already, make sure you are starting all cicsas server processes
up front when the region starts - don't allow it to happen dynamically,
or you will likely see worse performance due to server startup overhead.
I have not seen the problem you aluded to regarding the number of
pending login requests queued .vs. cicsas servers running.
rgds,
Duane
|
| Hi,
I am in USA now and we , CICS instructor and me , discussed with
your problem and he said to check RegionPool Size ,that is , default is
1k. As you know, we can check that by CSTD on cicsterm.
I hope this help you.
Regards,
Jun-Mok Song
|