A MOP Client entity is a set of default characteristics used by these MOP
   functions: dump/load server, load requester,  loop requester, and console
   requester. When a command or a request for one of these services does not
   supply all of the required arguments, the values stored by the client are
   used to perform the operation.  The client-name refers to the client managed
   by this command.

1  –  character

     ADDRESSES
         Default: Empty Set                    Values: Set of LAN Address

         Set of LAN addresses for this client on the circuit specified by the
         circuit characteristic.  Phase IV nodes can use an extended DECnet
         LAN address in addition to their hardware address, so you must include
         both of these addresses in the addresses set. To calculate the
         extended DECnet address, express the Phase IV node address as a
         four-digit hex integer, then add the prefix AA-00-04-00.

         For example, if the Phase IV node address is 4.260:

                  4.260

     CIRCUIT
         Default: No circuit                  Value: Circuit-id

         Name of the MOP circuit that corresponds to the Data Link circuit that
         is to be used for communicating with this client.

     DEVICE TYPES
         Default: No device type              Value: Set of device types

         Specifies one or more device types associated with this client. Use
         device types and omit addresses if you want to set up a generic
         client entity; the entity will be used for any incoming load or dump
         requests that specify a matching communications device type.

         To determine the communications device type for a particular network
         server, consult the server documentation, or use the Configuration
         Monitor Function of MOP.

     DIAGNOSTIC IMAGE
         Default: No File                     Value: Sequence of file specs

         Files to be loaded when the client requests a diagnostic image during
         a downline load operation. File identifications are interpreted
         according to the file system of the local system.

     DUMP ADDRESS
         Default: 1                           Value: 0 - (2 to the 23rd -1)

         Memory address at which to begin an upline dump.

     DUMP FILE
         Default: No File                     Value: Sequence of file specs

         Files to write to when the client is upline dumped.  File
         identifications are interpreted according to the file system of the
         local system.

     MANAGEMENT IMAGE
         Default: No File                     Value: Sequence of file specs

         Files to be loaded when the client requests a management image during
         a downline load operation. File identifications are interpreted
         according to the file system of the local system.

     PHASE IV CLIENT ADDRESS
         Default: 0.0                          Value: Phase IV Address

         Phase IV node address given to the client system when it is downline
         loaded. This address is passed in a load parameters message; whether
         it is needed depends on the software being loaded.

     PHASE IV CLIENT NAME
         Default: No Name                      Value: Phase IV name

         Phase IV node name given to the client system when it is downline
         loaded.  This name is passed in a load parameters message; whether it
         is needed depends on the software being loaded.

     PHASE IV HOST ADDRESS
         Default: 0.0                          Value: Phase IV address

         Phase IV node address to be passed as the host node address when a
         client is downline loaded.  This address is passed in a load
         parameters message; whether it is needed depends on the software being
         loaded.

     PHASE IV HOST NAME
         Default: No name                      Value: Phase IV name

         Phase IV node name that is passed as the host name when the client is
         downline loaded. This name is passed in a load parameters message;
         whether it is needed depends on the software being loaded.

     SCRIPT FILE
         Default: No File                      Value: Sequence of file specs

         Files to be loaded when the client requests a CMIP initialization
         script during a downline load operation. File identifications are
         interpreted according to the file system of the local system.

     SECONDARY LOADER
         Default: No File                       Value: Sequence of file specs

         Files to be loaded when the client requests a secondary loader during
         a downline load operation.  File identifications are interpreted
         according to the file system of the local system.

     SYSTEM IMAGE
         Default: No File                       Value: Sequence of file specs

         Files to be loaded when the client requests an operating system image
         during a downline load operation.  File identifications are interpreted
         according to the file system of the local system.

     TERTIARY LOADER
         Default: No File                        Value: Sequence of file specs

         Files to be loaded when the client requests a tertiary loader during a
         downline load operation. File identifications are interpreted according
         to the file system of the local system.

     VERIFICATION
         Default: %X00-00-00-00-00-00-00-00      Value: Hex string

         Verification string to be sent in a boot message to this client. The
         value must have an even number of digits from 2 to 16.