Macros

Contents
vmx32besp
Contents
VM:Secure
implements many commands and functions with REXX routines named
macros
. These macros call primitive functions written in Assembler to manipulate a directory and a user’s virtual machine by issuing commands to the command environment that
VM:Secure
creates.
Tracing Macros
When a
VM:Secure
command does not complete execution normally, you can find out where the associated macro failed by using the TRACE command. The TRACE command lets you trace the execution of a macro. This debugging information is valuable if you need to call Technical Support to report macro errors.
To use the TRACE command, you must have the appropriate authorization in the AUTHORIZ CONFIG file.
To enter the following command, you must have at least TRACE MACRO ULIST authorization:
vmsecure
trace macro ulist
Any of the following records in the AUTHORIZ CONFIG file can give you the required authorization. Replace
userid
with the userid who will issue the TRACE command:
GRANT TRACE MACRO ULIST TO 
userid
GRANT TRACE MACRO TO 
userid
GRANT TRACE TO 
userid
To trace a macro
  1. Spool your console to yourself:
    cp spool console start to *
    This step saves the trace so you can analyze it later.
  2. Enter the TRACE command with the optimized macro name that you want traced. For example, to trace the ULIST command when issued by user ID TESTUSR and send the trace information to user ID MONUSR, enter the following command:
    vmsecure
    trace macro ulist user testusr to monusr
  3. Note the trace number that is provided in the command response.
  4. Enter the command to trace. For example, to list all the information about user ID OPERATOR, enter the following:
    vmsecure
    ulist operator
  5. When the command fails, stop the trace by entering TRACE STOP followed by the trace number from step 3. For example, to stop trace 3, enter the following command:
    vmsecure
    trace stop
     
    3
  6. Close your console and send the output to your reader by entering:
    cp spool console close