| C'mon Dave.
This isn't what we're asking. Re-read .0.
What good is this feature if no one's sure it even gets out on the wire?
<<< NOTED::DISK$NOTES1:[NOTES$LIBRARY_1OF4]COMMON-AGENT.NOTE;2 >>>
-< Common Agent Project Conference. >-
================================================================================
Note 202.3 setting default arg/attr 3 of 3
RACER::dave "Ahh, but fortunately, I have the key t" 12 lines 9-MAR-1993 11:35
--------------------------------------------------------------------------------
The 1.3 interface, and the 1.2 interface support setting defaults just fine.
Select the object (e.g. click on it once), select the operations menu,
the set function, the characteristics sub function,
Get a list ot attributes, an select one that has a default value.
Use MB3 to get the selection menu, and select the "use default" option.
If the AM deals with this correctly is another matter, but in any case, it
can be entered from the user interface.
|
| .0 is a bug in the node AM. The PM is passing down a "use default"
to the AM. The AM mustn't be correctly translating it, or the node
itself is having a problem with it.
Each AM handles the "use default" (defined in the SRM as IMPLEMENTATION
SPECIFIC DEFAULT) according to what their device can handle. Some
AMs try to pass the command to set the default directly to the device
while others translate it into a real value before sending the set
to the device. I am uncertain what NODE is doing, but it isn't
working and this needs to be qared.
|