access:       modify
   mechanism:    by 32- or 64-bit reference
   Process identification (PID) of the process to be activated. The
   pidadr argument is the 32- or 64-bit address of a longword that
   contains the PID. The pidadr argument can refer to a process
   running on the local node or a process running on another node in
   the cluster.
 

prcnam

   OpenVMS usage:process_name
   type:         character-coded text string
   access:       read only
   mechanism:    by 32- or 64-bit descriptor-fixed-length string
                 descriptor
   Process name of the process to be activated. The prcnam argument
   is the 32- or 64-bit address of a 32- or 64-bit character string
   descriptor pointing to the process name. A process running on the
   local node can be identified with a 1 to 15 character string.

   To identify a process on a particular node in a cluster, specify
   the full process name, which includes the node name as well as
   the process name. The full process name can contain up to 23
   characters.

   The process name is implicitly qualified by the UIC group number
   of the calling process. For this reason, you can use the prcnam
   argument only if the process to be activated is in the same UIC
   group as the calling process. To activate a process in another
   UIC group, you must specify the pidadr argument.
 

2  $WFLAND
   Allows a process to specify a set of event flags for which it
   wants to wait.

   Format

     SYS$WFLAND  efn ,mask

   C Prototype

     int sys$wfland  (unsigned int efn, unsigned int mask);
 

3  Arguments
 

efn

   OpenVMS usage:ef_number
   type:         longword (unsigned)
   access:       read only
   mechanism:    by value
   Number of any event flag within the event flag cluster to be
   used. The efn argument is a longword containing this number;
   however, $WFLAND uses only the low-order byte. Specifying the
   number of an event flag within the cluster serves to identify the
   event flag cluster.

   There are two local event flag clusters: cluster 0 and cluster
   1. Cluster 0 contains event flag numbers 0 to 31, and cluster 1
   contains event flag numbers 32 to 63.

   There are two common event flag clusters: cluster 2 and cluster
   3. Cluster 2 contains event flag numbers 64 to 95, and cluster 3
   contains event flag numbers 96 to 127.
 

mask

   OpenVMS usage:mask_longword
   type:         longword (unsigned)
   access:       read only
   mechanism:    by value
   Event flags for which the process is to wait. The mask argument
   is a longword bit vector wherein a bit, when set, selects the
   corresponding event flag for which to wait.
 

2  $WFLOR
   Allows a process to specify a set of event flags for which it
   wants to wait.

   Format

     SYS$WFLOR  efn ,mask

   C Prototype

     int sys$wflor  (unsigned int efn, unsigned int mask);
 

3  Arguments
 

efn

   OpenVMS usage:ef_number
   type:         longword (unsigned)
   access:       read only
   mechanism:    by value
   Number of any event flag within the event flag cluster to be
   used. The efn argument is a longword containing this number;
   however, $WFLOR uses only the low-order byte. Specifying the
   number of an event flag within the cluster serves to identify the
   event flag cluster.

   There are two local event flag clusters: cluster 0 and cluster
   1. Cluster 0 contains event flag numbers 0 to 31, and cluster 1
   contains event flag numbers 32 to 63.

   There are two common event flag clusters: cluster 2 and cluster
   3. Cluster 2 contains event flag numbers 64 to 95, and cluster 3
   contains event flag numbers 96 to 127.
 

mask

   OpenVMS usage:mask_longword
   type:         longword (unsigned)
   access:       read only
   mechanism:    by value
   Event flags for which the process is to wait. The mask argument
   is a longword bit vector wherein a bit, when set, selects the
   corresponding event flag for which to wait.
 

2  $WRITE
   The Write service transfers a user-specified number of bytes
   (beginning on a block boundary) to an RMS file of any file
   organization.

   For additional information about this service, see the OpenVMS
   Record Management Services Reference Manual.