Improving CA VM:Secure Performance › Service Virtual Machine Performance

Service Virtual Machine Performance

To improve performance on the CA VM:Secure service virtual machine

• Rewrite heavily used user exits in Assembler for faster execution.
• (CA VM:Secure only) Use the CPIGNORE record in the VMXRPI CONFIG file when you are generating the Rules Facility to ignore directory links and the SPOOL and TAG commands. CA VM:Secure will call the Rules Facility less often for rules evaluation. This also reduces the amount of auditing.
• Use the MACLOAD record in the PRODUCT CONFIG file for frequently used macros, or better yet, all macros.
• Do not create macros that issue long–running commands on the CA VM:Secure machine. Instead, run the commands on the issuing user ID’s machine. When a process starts on CA VM:Secure, it runs until the process is complete or until it prompts a user for information. At that point, the next process in the queue is started.
• Use the AUDIT user exit to decrease the number of audit records that CA VM:Secure creates.
• (CA VM:Secure only) Put links that are in PROFILE EXECs in directory entries. This reduces the number of links that must be validated by the Rules Facility (assuming that you have generated the Rules Facility with the CPIGNORE DIRLINK record in the VMXRPI CONFIG file).
• (CA VM:Secure only) Use *HS= special comments and rules with the HISTORY option with care, because they add overhead to the rules evaluation process. A larger blocksize for the DRCT minidisk may improve performance or reduce disk space if the addition of history special comments causes the majority of directory entries to use an additional data block at the current block size.