Configuration Files and Records › PRODUCT CONFIG File › CA VM:Secure PRODUCT CONFIG File

CA VM:Secure PRODUCT CONFIG File

For CA VM:Secure, the PRODUCT CONFIG file can contain the following records:

• ACCESS (cannot be changed while CA VM:Secure is running)
• ALTERNAT (cannot be changed while CA VM:Secure is running and SERVANTS are ON)
• AUTOUSER
• DELAYHIS
• DELAYLOG
• DIRECT (cannot be changed while CA VM:Secure is running)
• DUMP
• ENCRYPT (cannot be changed while CA VM:Secure is running)
• IPLDISK
• MACLOAD
• MAXOLDPW
• MESSAGE
• MSGCASE
• PRODUCT
• RESID (cannot be changed while CA VM:Secure is running)
• SERVANT
• SSINODE (cannot be changed while CA VM:Secure is running)
• SYSOPER
• USEREXIT

As part of installation, the PRODUCT CONFIG file is created for you and resides on the CA VM:Secure A–disk. You cannot use the records in this file in any other configuration file.

To make any changes to the ACCESS, DIRECT, ENCRYPT, RESID, or SSINODE records, or you are running with Servant Facility and want to add an ALTERNAT FORMAT record, you must take down CA VM:Secure and make the changes manually in the file. The changes will take effect when CA VM:Secure is brought back up. For the remaining records, you can change them dynamically, and the changes take effect immediately.

When you are operating in a Single System Image complex, you must bring down the CA VM:Secure server on every member node in order to make a manual change to the PRODUCT CONFIG file. After the change is made, restart each server by issuing an IPL CMS command so that the configuration files are re-accessed properly.