Use the High Performance Storage Protect option (HPSPO) in production CA IDMS systems.
Business Value:
HPSPO protects the integrity of your systems by preventing user programs from overwriting CA IDMS and operating system storage, from overwriting CA IDMS and operating system code, and from executing privileged instructions.
With HPSPO you do not have to make the difficult choice between system integrity and CPU. You can implement storage protection with minimal CPU cost. The use of full storage protection incurs significant CPU time.
Additional Considerations:
While protecting the integrity of CA IDMS and the operating system, HPSPO will not protect non-reentrant user programs and user storage. Use full storage protection in test systems to identify and correct any renegade program before moving it into production.
The High Performance Storage Protect option was introduced with CA IDMS r16 SP2. HPSPO allows you to protect the IDMS system and control blocks from being overlaid by a user mode programs written in CA ADS, COBOL, Assembler, or PL/I.
To use HPSPO, you must specify the following system generation parameters:
HPSPO also requires special setup for your storage pools. You must segregate all user-oriented storage from CA IDMS system storage. Storage types, user, user-kept, shared, and shared-kept, can be together, but they must be defined to secondary storage pools and must be isolated from any secondary pools that contain database or terminal type storage.
Any user programs that attempt to perform I/O directly through operating system facilities may need to be modified because they must run with storage protection enabled. This ensures that the storage key and the execution key match, which is an operating system requirement for I/O.
To use full storage protection, set the STORAGE KEY IS parameter on the SYSTEM statement to a value between 10 and 15; also specify PROTECT on the SYSTEM statement and at the program definition level.
Use full storage protection for all development, test, non-performance related QA, and pre-production systems. This should help to identify any application errors before the application is moved to production. When full storage protect is enabled, any program attempting to overlay storage that it does not own will abend with a D003 abend code.
For production you should use the High Performance Storage Protect option. This provides for system integrity with negligible CPU overhead in the event that a change is made to an application that has not been tested on a non-production system.
More Information:
For more information about storage protection and the use of HPSPO, see Storage Protection in the CA IDMS System Generation Guide.
|
Copyright © 2013 CA.
All rights reserved.
|
|