Reference Guide › User Exit Reference › POSTMOVE User Exit

POSTMOVE User Exit

Use the POSTMOVE user exit to manipulate data that has been moved from minidisks to SFS.

POSTMOVE entry filepool vaddr mmode dir dmode recomp

Definitions

entry

The directory entry that owns the data that has just been moved from a minidisk to SFS.

filepool

The name of the file pool to which the data was moved.

vaddr

The virtual address of the minidisk that was moved.

mmode

The CMS file mode at which the minidisk is currently accessed on the servant user ID.

dir

The fully qualified SFS directory name to which the data was moved.

dmode

The CMS file mode at which the SFS directory is currently accessed on the servant user ID.

recomp

Is RECOMP if the minidisk whose data was just moved has a recomputed area, or NORECOMP if the minidisk has no recomputed areas.

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.

Return Codes

The following table describes the return code:

Macros

The following macro calls the POSTMOVE user exit: