ca.portal.admin

Storage Protection

Discussion created by ca.portal.admin on Mar 17, 2009
Latest reply on Mar 17, 2009 by ca.portal.admin
Could someone please confirm the recommended storage protection
settings?
In Production we have PROTECT at system level and NOPROTECT at program
level which I thought was the right combination. I am currently
installing IDMS 17 and the Installation and Maintenance guide for Z/OS
(we are at Z/OS 1.9) recommends NOPROTECT at system level with PROTECT
at program level. Which way round should they be?
"
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: Storage Protection
"If you ever find yourself in a place where you have one problematic program you want to catch in the act, you would want PROTECT on at the system level, and every program except the culprit defined as NOPROTECT. The other way 'round you're stuck with having either modify gobs of programs to NOPROTECT, or living with all the overhead of having your entire production environment running in PROTECT mode, when all you want to do is investigate one program.

Don Casey
Run Right, LLC
(hiding out in the redwood country at the moment)

----- Original Message -----

From: Paul Clarke

To: IDMS-L@LISTSERV.IUASSN.COM

Sent: Tue, 17 Mar 2009 16:08:04 +0000 (UTC)

Subject: Storage Protection



Could someone please confirm the recommended storage protection settings?

In Production we have PROTECT at system level and NOPROTECT at program

level which I thought was the right combination. I am currently installing

IDMS 17 and the Installation and Maintenance guide for Z/OS (we are at

Z/OS 1.9) recommends NOPROTECT at system level with PROTECT at program

level. Which way round should they be?
"
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: Storage Protection
"In production we run with PROTECT ON at the system level, i.e. NOPROTECT
at the program level because storage handling is much move efficient. In
test and QA PROTECT it is on at both levels with the hope being that any
possible storage overlays are detected before they get into a production
environment. CA also has high speed storage protection now, I believe it
came out in 16.0, maybe 15.0. I have not done much with this yet so
maybe someone else can comment on that.

Steve Harmeson

Outcomes