|
|
|
Traces remain active until stopped using the TRACE STOP command. If messages are going to a printer spool file, you can close the file and start a new spool file by using the TRACE CLOSE command. If these is more than one trace defined for a userid / macroname combination, CA VM:Secure uses only the first trace definition against the macro.
Each TRACE command that specifies the PRINT parameter uses a new virtual printer device on the service virtual machine. CA VM:Secure imposes a maximum of 240 virtual printers in the address range of 0010 ‑ 00FF for use with trace output going to spooled printer files. If this limit is reached and a virtual printer cannot be defined, the TRACE command waits until a virtual printer is made available.
If a macro to be traced is run from the CA VM:Secure service virtual machine, the TRACE command ignores the LINES, USER, and TO parameters, and types the trace messages to the service virtual machine console.
If a macro you are tracing calls a user exit written as an EXEC, the TRACE command will not trace the user exit. You can trace user exits only by inserting the appropriate trace function in the user exit itself. User exit trace output always goes to the service virtual machine console.
Note: Tracing a macro’s execution reveals passwords being checked or set. However, if the CA VM:Secure Password Encryption Facility is being used, only the encrypted passwords are revealed.
Example
User ID MAINT wants to trace the CHGMDISK command every time it is used by user ID MARY. Enter:
vmsecure trace macro chgmdisk user mary to maint print
Each time MARY issues the CHGMDISK command, CA VM:Secure sends the trace messages to a new spool file in MAINT’s reader queue.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |