ca.portal.admin

R16 SP2 - HPSPO questions

Discussion created by ca.portal.admin on Jul 11, 2005
It appears that the new High Speed Storage Protection (HPSPO) will
automatically be turned on if your SYSGEN specifies ""STORAGE KEY = 9"",
which is the default. My questions are about what happens if you DON'T
want to turn it on:

1) If you change the storage key to something other than 9, will
storage protection continue to work as it does now? (Assuming you don't
change anything else related to storage protection.)

2) What should the storage key be changed to? Are any other numbers
dangerous for some reason?

3) Can the storage key be changed prior to upgrading to R16 SP2, with
no ill effects?

Kay Rozeboom
State of Iowa
Information Technology Enterprise
Department of Administrative Services
Telephone: 515.281.6139 Fax: 515.281.6137
Email: Kay.Rozeboom@Iowa.Gov

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: R16 SP2 - HPSPO questions
"Kay,
To use the new HPSPO option you need to do two things:

Specify ""STORAGE KEY IS 9"" in your SYSGEN
and
Separate all of your user orientated storage (USER, USER KEPT, SHARED,
SHARED KEPT) into secondary storage pools which do not contain any
database or terminal storage - both above and below the line. If you do
not do this you will get a message at startup saying that the HPSPO will
not be used.

Unless both of these things are in place storage protection continue to
work as it does prior to SP#2.

You must not set the storage key to the same value as your Primary
Storage Protect Key - shown on DCPROFIL first screen. I used a value of
10 and that worked fine.

I can see no reason why you cannot do these changes prior to upgrading
to R16 SP#2.


Steve Terry
BT
Tel: +44 (0)121 230 7728

British Telecommunications plc
Registered office: 81 Newgate Street London EC1A 7AJ
Registered in England no. 1800000

This electronic message contains information from British
Telecommunications plc which may be privileged and confidential. The
information is intended to be for the use of the individual(s) or entity
named above. If you are not the intended recipient, be aware that any
disclosure, copying, distribution or use of the contents of this
information is prohibited. If you have received this electronic message
in error, please notify us by telephone or e-mail (to the number or
address above) immediately.-----Original Message-----
From: IDMS Public Discussion Forum [mailTo:IDMS-L@LISTSERV.IUASSN.COM]
On Behalf Of Rozeboom, Kay [DAS]
Sent: 11 July 2005 20:57
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: R16 SP2 - HPSPO questions

It appears that the new High Speed Storage Protection (HPSPO) will
automatically be turned on if your SYSGEN specifies ""STORAGE KEY = 9"",
which is the default. My questions are about what happens if you DON'T
want to turn it on:

1) If you change the storage key to something other than 9, will
storage protection continue to work as it does now? (Assuming you don't
change anything else related to storage protection.)

2) What should the storage key be changed to? Are any other numbers
dangerous for some reason?

3) Can the storage key be changed prior to upgrading to R16 SP2, with
no ill effects?

Kay Rozeboom
State of Iowa
Information Technology Enterprise
Department of Administrative Services
Telephone: 515.281.6139 Fax: 515.281.6137
Email: Kay.Rozeboom@Iowa.Gov

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Working relational database with IDMS
"Hi Everyone:

We just start a project defining a new relational database using IDMS. We
are new with a project like this using IDMS. Does anybody want to share
experiencies, tips with us ??? Does anybody want to share a cobol program,
just to learn how to codify a typical cobol program using sql and IDMS ??
Any comments ???? Actually we are on 14.1 and we will move to 16.0 sp1 tis
weekend maybe.

Thanks.

Javier S.

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Working relational database with IDMS
"Javier,


Look at the following link





http://www.geocities.com/idmssql/index.html






Regards






Philippe Jacqmin
CCDBMS

IDMS (Data Base & Transaction Server)
WT 20/8 zone 1
+32 (0)2 222 93 52
<mailTo:Philippe.P.Jacqmin@dexia.be> Philippe.P.Jacqmin@dexia.be or philippe.jacqmin@formulaopensoft.com




-------------------------------------------------------------
Dexia Bank disclaimer :
http://www.dexia.be/maildisclaimer.htm
-------------------------------------------------------------




"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Working relational database with IDMS
"Javier, do you still need some sample COBOL code? Please let me know if
you do.

Here are the main things I can tell you about our experience with
IDMS/SQL:

1) If you and your developers have experience with other relational
databases, IDMS/SQL will be easy to learn. If you do not have prior
relational experience, you will have a steep learning curve. Be sure
that your management understands this, and that you will need time to
experiment.

2) With IDMS network databases, the developer has complete control over
the access path. With IDMS/SQL databases, the developer has NO control
over the access path. The optimizer chooses the access path for you.
In my experience, this is the hardest part for developers to get used
to, so you may as well warn them up front.

3) The optimizer may choose a different access path on production than
it did on test. Be sure to use the 'explain' function on both test and
production, so that you know what access path is being used. Also, be
sure to run 'update statistics' after loading data into your test and
production databases for the first time. If you don't do this, you are
likely to have performance problems.

Outcomes