Reflective Memory Allocation Description

Data stored in reflective memory are identified by a set of names, which are listed in the file $COMMON/reflmem/rm_allocation. Entries in this file follow a naming convention which includes several ``fields'':

   name1_name2_..._type   or   name1_name2_..._Vm_..._type

   name1, name2, etc. form a descriptive name
   type is a code describing the data type:
      B  = integer, 8 bit                (1 byte)
      S  = integer, 16 bit               (2 bytes)
      L  = integer, 32 bit               (4 bytes)
      F  = IEEE floating point, 32 bit   (4 bytes)
      D  = IEEE floating point, 64 bit   (8 bytes)
      Cn = character array (string) of length n

   The code may be preceded by one or more sequences of type "Vm" to
   specify a vector.

   Examples:
     RM_THIS_VAL_F        : a 4-byte float
     RM_FILE_NAME_C50     : a 50 character string
     RM_DATA_V10_S        : an array of 10 16-bit integers
     RM_FDATA_V128_V128_D : a 128x128 array of 64-bit floating point values

Names may not be longer than characters, where RM_NAME_LENGTH is defined in the C header file rm.h (the is necessary to leave space for a terminating zero byte). Names are case-sensitive.

To add, change, or delete a data storage location, rm_allocation must be edited, after which the changes must be registered by typing make allocation. Also, the new version should be registered to CVS by typing cvs commit rm_allocation.

If there is difficulty in running make allocation or cvs commit rm_allocation, check the permissions of the directories $COMMON/reflmem, $COMMON/reflmem/CVS, and $COMMON/reflmem/api. See §.

NOTE: After the new allocation table has been registered, all programs using reflective memory must be stopped and the drivers on all computers must be reloaded. This may be done manually (see §), or the computers which use reflective memory may all be rebooted.