ca.portal.admin

Factors to take into account when deciding whether to create a

Discussion created by ca.portal.admin on Mar 6, 2009
new production Retrieval CV

There are plans to significantly increase the number of users, possibly
thousands, defined to our IDMS application. Many of the existing users
and a high proportion of the new users will be retrieval only. Currently
we have approximately 3500 users, where the most we see signed on
concurrently is 580 or so. We kick them off after 20 minutes inactivity.

The users we currently have defined are the ""core"" stakeholders, and I
expect the new users will not be signed on as long or do as much
activity with the application.

I am aware of some of the issues when having a retrieval CV. What may
appear to be broken chains to the retrieval CV unless the buffers are
shared with the update system, the application would have to be adjusted
slightly to eliminate any updates during signon etc.

From the performance point of view, we don't have max tasks exceeded, no
SOS type issues and excellent response time overall. My expectation is
that we could add these new users into the existing update CV, scale the
maximum number of concurrent users appropriately, and there would be no
negative impact, except possibly for an increase in the size of pool 128
which contains SH,SK,US,UK types. However I would like to know what the
major benefits are in having a retrieval CV and what I should monitoring
in the update CV that will indicate a retrieval CV would be worth
considering.

Thank you all for the information.=20

Tim Williams
Alberta Department of Justice
JOIN Technical support
(780) 415 6160
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Factors to take into account when deciding whether to create a new production Retrieval CV
"Many years ago we started with 250 users being a ""big day"" - we now
regularly hit 750 users and put through a million tasks a day (between
3:00am and 6:00pm). We have 7,000+ registered users - so clearly the old
10% rule works pretty well, more likely because in our case our user
community is spread across 3 shifts. We do not think that we are
anywhere near capacity of a single region to support our requirements.

We use a single DB/DC architecture (no CICS). In addition to 700-750
VTAM users we have up to 100 mid-range (Java) users on at the same time.
IDMS has scaled very well for us. Only thing to remember is to keep
resources increasing with increasing numbers of users: storage pools,
Scratch, RCE's and RLE's. We have broken up our storage pools so that we
get High Performance Storage Protect Option to kick in, and to minimise
SOS's - see following display - HTH - cheers - Gary

************************************************************************
*******
Tape CV Num Julian Date+Time
*
G0GJ7M 20 2009065 09:41
*
************************************************************************
*******
Pool Pages In Use HWM Times SOS Cushion SSUUTDS
*
HKSKRBY
*
0 1000 88 92 0 250 X
*
8% 9% 25%
*
1 250 10 30 0 25 XX
*
4% 12% 10%
*
2 250 5 5 0 25 XX
*
2% 2% 10%
*
3 250 0 2 0 25 XX
*
0% 0% 10%
*
128 10000 5078 5416 0 0 XX
*
50% 54% 0%
*
129 1000 146 147 0 0 XX
*
14% 14% 0%
*
130 3750 1596 1770 0 0 XX
*
42% 47% 0%
*
255 10000 5518 5569 0 0 X
*
55% 55% 0%
*
************************************************************************
*******
Scratch-> Lo Page HI Page Alloc HWM
*
50001 68000 10786 11152
*
Percentages ------------> 59% 61%
*
************************************************************************
*******
Users-> Max Current HWM
*
760 583 588
*
************************************************************************
*******
V20 Release 16.0 SP7 >>> JIS Production CV <<< Enter next task:



Gary Cherlet
Justice Technology Services
Department of Justice, SA Government
Telephone +61 (0)8 8226 5199
Facsimile +61 (0)8 8226 5311
Mobile +61 (0)41 333 1613
MailTo:cherlet.gary@saugov.sa.gov.au

This e-mail message and any attachments are qualified as follows:
Addressing: If you have received this e-mail in error, please advise by
reply e-mail to the sender. Please also destroy the original
transmission and its contents. Confidentiality: This e-mail may contain
confidential information which also may be legally privileged. Only the
intended recipient(s) may access, use, distribute or copy this e-mail.
Individual Views: Unless otherwise indicated, the views expressed are
those of the sender, not Justice Technology Services. Computer Viruses:
It is the recipient's responsibility to check the e-mail and any
attached files for viruses.

Outcomes