PRODUCT CONFIG File (Rules Facility not installed)

Contents
vmx32besp
Contents
As part of installation, the PRODUCT CONFIG file is created for you and resides on the
VM:Director
A-disk. You cannot use the records in this file in any other configuration file.
To make any changes to the ACCESS, DIRECT, RESID, or SSINODE records, or if you are running with the Servant Facility and want to add an ALTERNAT FORMAT record, take down
VM:Director
and make the changes manually in the file. The changes take effect when
VM:Director
is brought back up. For the remaining records, you can change them dynamically, and the changes take effect immediately.
To make a manual change to the PRODUCT CONFIG file when you are operating in a Single System Image complex, bring down the
VM:Director
server on every member node in order. After the change is made, restart each server by issuing an IPL CMS command. Restarting the servers ensures that the configuration files are reaccessed properly.
PRODUCT CONFIG File Records
The following table contains the records that can appear in the PRODUCT CONFIG file and says whether they are required, recommended, or optional. A sample file follows.
Record
Use
Quantity Allowed
ACCESS
Required for DRCT, BKUP, LOG, and HOLD minidisks. Recommended for the AUDT minidisk. If you are using the Servant Facility, ACCESS COMMON is required. If you are running in a Single System Image complex, an ACCESS LOG record is required. ACCESS cannot be changed while
VM:Director
is running.
Multiple
ALTERNAT
Optional. ALTERNAT cannot be changed while
VM:Director
is running and SERVANTS are ON.
Multiple
AUDRECFM
Optional
1
DIRECT
Required. DIRECT cannot be changed while
VM:Director
is running.
1
DUMP
Recommended
1
ESM
Required if your site is enabling interfacing with an external security manager
1
IPLDISK
Recommended
1
MAXOLDPW
Optional
1
MESSAGE
Optional
Multiple
MSGCASE
Optional; recommend using the MESSAGE record instead
1
PRODUCT
Optional
Multiple
RESID
Required only if your site has implemented the IBM Systems Management API support or Single System Image support. RESID cannot be changed while
VM:Director
is running.
1
SERVANT
Required if using SFS administration; otherwise recommended; requires use of ACCESS COMMON record
1
SSINODE
Optional. SSINODE cannot be changed while
VM:Director
is running.
Multiple
SYSOPER
Optional
Multiple
USEREXIT
Optional
Multiple
Sample PRODUCT CONFIG File
* *SERVANT ON VMX$ 120 1 6 * DUMP 
VMSECURE
 NOCLEAR * SYSOPER OPER1 SYSOPER OPER2 RESID 
VMSECURE
* *** * ACCESS AUDT 1D0 Q ACCESS BKUP 1B1 P ACCESS HOLD 1B2 T ACCESS DRCT 1B0 U ACCESS RULE 1B4 V ACCESS COMMON 194 N * MESSAGE MSGNOH MIXED * DIRECT 1A0 VST023