A-25
A4
All configuration messages pertaining to actions shall respond with an RPC
reply and then (if the status is No Error) execute the action.
All Edevice configuration commands will reply with statuses corresponding
to Error Codes as defined by the VXI-11 (section B.5.2).
All Edevice configuration command data will use XDR encoding. Numeri-
cal values will be of 4-byte unsigned integer format. String and binary fields
will be of opaque array format. Variable length string values will be NULL
terminated and will contain a leading length numerical value defining the total
length (inclusive of the NULL).
All Edevice configuration commands and replies will result in RPC messages
which are multiples of 4-byte lengths. Padding will occur following the last
data field and may consist of any byte value.
When the Action boolean signals a read of a mode/value setting, the RPC com-
mand must contain a dummy mode/value. While the mode/value in the RPC
command is not used, it must exist. If the mode/value is not contained within
the RPC command, an error status will result.
The successful modification of a configuration setting will result in the change
taking effect immediately, except where noted. Thus, it is strongly advisable
to not make configuration changes if VXI-11 device links are currently active.
Doing so can cause unpredictable results and Edevice misbehavior. However,
such dynamic modifications may be desirable and are possible at the discre-
tion of the user. Messages that require rebooting will not take affect until the
Edevice is rebooted.
B.2
Edevice PROGRAM ID AND VERSION
The Edevice configuration procedures shall use an RPC program ID of
1515151515 and an RPC version number of 1.
