Implementing the Memory Update Security Exit

Code Debug CICS also offers a Memory Update Security Exit facility that complements the File Update Security Exit discussed in Implementing-the-File-Utility-Security-Exit. Update security is implemented at the transaction level. You can set this form of security for a single transaction, for multiple transactions, or not at all (the default) by creating a Memory Update Security Exit and setting the ENABLE_UPDATE_PASSWORD_FIELD global parameter for the desired transaction levels.

Once Memory Update Security is set for a screen, you must enter a password before changes on the screen can be executed. If the password is invalid or not entered, all changes to the data areas of the screen are ignored, and a message is displayed indicating why the update was bypassed.

CICS calls or external security manager calls cannot be made with this exit.

This section discusses the following topics:

• Implementing Memory Update Security Exits
• Debugging the Memory Update Security Exit
• Changing data on password-protected screens.

This section is important for system programmers who want to secure access to memory areas of their applications.

The task involves the following people:

• Code Debug CICS Installer
• z/OS Security Administrator.
  

This section provides more information on the following topics: