The online Module Overrides Management lets you manage modules in load libraries.
This facility has features that you may want to restrict access from especially in a production environment.
For example: Installing and modifying module overrides.
A module override instructs CICS to take a module from a specified library, even if that module is found in a library higher in the CICS library concatenation.
Renaming a module within a load library or deleting a module from a load library.
CA DADS Plus for CICS currently has no way to restrict any of its online feature including the Module Overrides Management.
But as a work around you could try to limit access by user ID to certain CA DADS transactions.
You can access the DADS MODULE OVERRIDES MANAGEMENT features using the CA DADS primary option panel or by entering transaction identifiers which bypass the primary option panel and go directly to the sub panels.
Selecting Option 3 MODULE OVERRIDES MANAGEMENT or option 6 STARTUP MANAGEMENT above is the most common way of accessing these overrides
But if a user enters the DAM0 transaction from a clear screen they go directly to the option 3 MODULE OVERRIDES MANAGEMENT panel.
The same is true if the user enters the DAS0 transaction from a clear screen they go directly to 6 STARTUP MANAGEMENT.
From the option 6 STARTUP MANAGEMENT panel the user has three options.
These options can also be accessed directly by entering DAS1, DAS2 and DAS3.
6 STARTUP MANAGEMENT
STARTUP MANAGEMENT 1 - DFHRPL MODIFICATION STARTUP DAS1 2 - MODULE OVERRIDES STARTUP DAS2 3 - DCT STARTUP DAS3
Option 6 startup management can also be accessed by entering DAS0 from a clear screen.
The three options from the startup management menu are DAS1, DAS2 and DAS3.
You could try setting up transaction level security to limit access to these panels by limiting access to transactions DAM0, DAS0, DAS1, DAS2 and DAS3 as
needed at your site.
No quality assurance has been performed using this method so you will have to test if you choose to use this method.