1 – circuit
set [node node-id] mop circuit circuit-name ...
Modifies the attributes for a mop circuit entity, which is
a data link circuit on which MOP services are available. The
modifiable attributes and their data types [in brackets] are:
known clients only [boolean]
link name [data-link-entity-name]
retransmit timer [seconds]
Refer to attributes for specific command examples.
1.1 – known_clients_only
Default: False Value: True or false
Specifies whether MOP attempts to service load requests from
remote systems which do not have a corresponding client entity.
Some network servers are designed to request specific software
by name, and in such a case there is no need for a client entity
to exist. By default, MOP tries to process requests for named
software from unknown clients. Set this attribute to true if you
wish MOP to ignore such requests.
set [node node-id] mop circuit circuit-name -
known clients only boolean
Example:
set mop circuit fddi-1 known clients only true
1.2 – link_name
Default: No name Value: Data link entity name
Name of a station entity in the Data Link layer module indicated
by the type characteristic. This name is passed to the Data Link
layer module when MOP opens a portal for the circuit.
set [node node-id] mop circuit circuit-name -
link name data-link-entity-name
1.3 – retransmit_timer
Default: 4 Value: 1-30
Time, in seconds, to wait for a response before retransmitting a
MOP protocol message.
set [node node-id] mop circuit circuit-name -
retransmit timer integer
Example:
set mop circuit fddi-1 retransmit timer 4
2 – client
set [node node-id] mop client client-name ...
Modifies the attributes for a mop circuit entity, which is
used to store default characteristics used by several MOP
functions. The modifiable attributes and their data types
[in brackets] are:
addresses [set of lan-addresses]
circuit [circuit-name]
device types [set of device-types] (OpenVMS)
diagnostic image [filespec]
dump address [integer]
dump file [filespec]
management image [filespec]
phase iv client address [phase4-address]
phase iv client name [phase4-name]
phase iv host address [phase4-address]
phase iv host name [phase4-name]
script file [filespec]
secondary loader [filespec]
system image [filespec]
tertiary loader [filespec]
verification [hex-string]
Refer to attribute descriptions for specific command examples.
2.1 – addresses
Default: Empty set Value: Set of LAN addresses
Set of LAN addresses for this client on the circuit specified
by the circuit characteristic.
For OpenVMS, 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
set [node node-id] mop client client-name -
addresses {lan-address[,lan-address..]}
Examples:
set mop client imply -
addresses {08-00-2b-13-d6-e0, aa-00-04-00-8a-13}
set mop client mynode addresses {08-00-2b-13-d6-e0}
2.2 – 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.
set [node node-id] mop client client-name circuit circuit-id
Examples:
set mop client imply circuit csmacd-1
2.3 – device types (OpenVMS)
Default: No device types 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.
set [node node-id] mop client client-name -
device types {device[,device...]}
Examples:
set mop client csma_clients device types {una,sva}
2.4 – diagnostic_image
Default: No file Value: Sequence of file specifications
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.
set [node node-id] mop client client-name -
diagnostic image {file-spec[,file-spec]}
2.5 – dump_address
Default: 1 Value: 0-4294967295
Memory address at which to begin an upline dump.
set [node node-id] mop client client-name dump address integer
Examples:
set mop client imply dump address 1
2.6 – dump_file
Default: No file Value: Sequence of file specifications
Files to write to when the client is upline dumped. File
identifications are interpreted according to the file system
of the local system.
set [node node-id] mop client client-name -
dump file {filespec[,filespec...]}
2.7 – management_image
Default: No file Value: Sequence of file specifications
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.
set [node node-id] mop client client-name -
management image {filespec[,filespec...]}
2.8 – 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.
set [node node-id] mop client client-name -
phase iv client address phaseiv-address
Example:
set mop client imply phase iv client name imply, -
phase iv client address 4.906
2.9 – 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.
set [node node-id] mop client client-name -
phase iv client name phaseiv-name
Example:
set mop client imply phase iv client name imply, -
phase iv client address 4.906
2.10 – phase_iv_host_address
Default: 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.
set [node node-id] mop client client-name -
phase iv host address phasiv-address
Example:
set mop client imply phase iv host name imply, -
phase iv host address 4.906
2.11 – 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.
set [node node-id] mop client client-name -
phase iv host name phasiv-name
Example:
set mop client imply phase iv host name imply, -
phase iv host address 4.906
2.12 – script_file
Default: No file Value: Sequence of file specifications
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.
set [node node-id] mop client client-name -
script file {filespec[,filespec...]}
2.13 – secondary_loader
Default: No file Value: Sequence of file specifications
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.
set [node node-id] mop client client-name -
secondary loader {filespec[,filespec...]}
Example:
set mop client lamchp -
secondary loader {sys$system:secondary_vmb.exe}
2.14 – system_image
Default: No file Value: Sequence of file specifications
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.
set [node node-id] mop client client-name -
system image {filespec[,filespec...]}
Example:
set mop client lamchp -
system image {"@net$niscs_laa($1$dua0:<sys16.>)"}
2.15 – tertiary_loader
Default: No file Value: Sequence of file specifications
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.
set [node node-id] mop client client-name -
tertiary loader {filespec[,filespec...]}
Example:
set mop client lamchp -
tertiary loader {sys$system:tertiary_vmb.exe}
2.16 – verification
Default: %x00-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.
set [node node-id] mop client client-name -
verification hex-string
Example:
set mop client lamchp -
verification %x0000000000000000