In the XYZ3 profile we have MACH XA 3 defined and we override the user ABCDEF15 directory with MACH XA 2.
We are receiving message VMXDXS0835E CPU limit from MACHINE statement has been exceeded.
This seems to be a problem for us with VM:Secure r2.8 G0808 SP01 but works in VM:Secure r2.8 G0706 SP00.
VMXDXS0835E CPU limit from MACHINE statement has been exceeded.
VMXDXS0056I On record 11 in file 'ABCDEF15 VMXMAINT U '.
VMXEDI0459I Update of user 'ABCDEF15' failed.
VMXEDI0469I Do you wish to correct the problem?
VMXEDI0404R Enter 'YES' or 'NO':
VMSECURE 0006 VMXDXI0738I A Source Start will be performed due to use of a startup option.
VMSECURE 0006 VMXDXS0835E CPU limit from MACHINE statement has been exceeded.
VMSECURE 0006 VMXDXS0056I On record 21 in file 'ABCDEF15 VMXMAINT U '.
VMSECURE 0006 VMXCFG0115I Processing file 'AUTHORIZ CONFIG A1'.
VMSECURE 0006 VMXINI0022T VM:Secure initialization failed.
Corrections were made in CPU record processing logic for the VM:Secure G0808 release. The corrections expose directory entry errors in this area that were accepted erroneously in the previous release.
As documented in the IBM CP Planning and Administration guide, user directory entry records override that in an included profile. This is the case for the MACHINE record that contains the CPU record limit for the user definition. However, CPU records are additive between the profile and the user entry so you must consider the CPU records in both of them, decide what the CPU record limit should be set at, or, rework your profile or user CPU record definitions so the appropriate limit is met.
In the example given here, the directory profile XYZ3 contains a maximum CPU limit definition on the MACHINE record of 3. However, the user record contains a CPU limit of 2 from its MACHINE record. Since the MACHINE record in the user entry will override that of the profile, the user will end up with a CPU limit of 2. The profile contains 3 CPU records. The user entry didn't contain any. However, since the user definition would include in the CPU records from the profile, it would end up with 3, which exceeds its limit of 2.
Use the VM:Secure EDX command to see user entries expanded with their included directory profile for a clear view of the user definition. This can help you avoid errors such as this during directory maintenance. Always refer to the IBM documentation for record processing policies. Contact CA Technical Support if it appears the product is not processing directory records as documented in the IBM CP Planning and Administration guide.