User Exit Reference › POSTMOVE User Exit › Description

Description

Because of the requirements of issuing macro primitives, the POSTMOVE user exit cannot be written in assembler. It must be coded in REXX or EXEC2.

The POSTMOVE user exit uses CA VM:Secure macro primitives, commands that are issued within the user exit, to communicate with the servant user ID; the servant user ID has ACCESSed both the minidisk and the SFS directory.

The CA VM:Secure macro primitives that are most likely to be used are:

• SERVANT EXECUTE—Issues a command on the servant user ID

  The command text arguments that follow will be issued on the servant machine through CMSCALL.

• SERVANT READ—Places the data that exists on the servant user program stack into the CA VM:Secure server machine program stack

  To manipulate the data in the servant user stack, which you may need to do as the result of a command, use the SERVANT READ * primitive. This places the contents of the servant user stack into the server program stack, in the same order in which it was stacked on the servant user stack.

• SERVANT STACK—Stacks a line of data on the servant user stack

  Place data that you will need later on, such as for a subsequent command, on the servant user program stack by using the SERVANT STACK primitive. The data will be stacked LIFO on the servant user stack.

To use any of these primitives, precede it with the token TEST. This allows a nonzero return code to be passed back to the exit.

Note: For more information about macro primitives and how they work, see the chapter "Macros" in the Administration Guide.

The prototype user exit contains examples of the use of these primitives.