 |
» |
|
|
|
|  | |
(Subsystem 231 NMDF WARN, NMDF
ERR) | |
- -1
- MESSAGE
An invalid call to either Get or Set_device_information has
occurred. No return parameter was provided for a requested return
item.
- -2
- MESSAGE
An invalid call to either Get or Set_device_information has occurred.
An item number was specified that is not a valid item for Get or
Set_device_information.
- -3
- MESSAGE
A return parameter to NMDF specifies an address out of the user data
area.
- -4
- MESSAGE
Information was requested on a native mode device file that does not
exist.
- -5
- MESSAGE
Get or Set_device_information could not sm_open a device file.
- -6
- MESSAGE
Get or Set_device_information was passed an invalid device file
name.
- -7
- MESSAGE
Get/set_device_information could not open a device file.
- -8
- MESSAGE
Get/set_device_information was asked for a next device or class and no next device or class exists.
- -9
- MESSAGE
A reference parameter to get or set_device_information specifies an address out of the user data area.
- -10
- MESSAGE
A non-existent device file name was passed to get or set_device_information.
- -11
- MESSAGE
Both device and class were specified to get/set_device_information.
- -12
- MESSAGE
No device or class was passsed to get/set_device_information.
- -13
- MESSAGE
A parameter to Get/set_device_information was out of its valid range.
- -14
- MESSAGE
Get or set_device_information was passed an invalid device file name.
- -15
- MESSAGE
Device specifier not passed to get/set_device_information.
- -16
- MESSAGE
No device or class was passsed to get/set_device_information.
- -17
- MESSAGE
An invalid kind of device specifier was passed to get/set_device_information.
- -18
- MESSAGE
In a call to Get/set_device_information, caller requested to set an item that cannot be set.
- -19
- MESSAGE
A parameter to Get/set_device_information asks for information that is incompatible with the type of device/class specified.
- -20
- MESSAGE
Get_device_information was asked for a next device or class and no next device or class exists.
- -20
- MESSAGE
Get_device_information was asked for a next device or class and no next device or class exists.
- -21
- MESSAGE
Get_device_information was asked for an nth device and no nth device exists.
- -22
- MESSAGE
Get_device_information was asked for the nth device/class but "n" was not first specified.
- -23
- MESSAGE
Information was requested on the nth device or class and it is larger than the number of devices or classes for the device file specified.
- -24
- MESSAGE
A device specifier that was not properly delimited was passed to Get/Set_device_information.
- -25
- MESSAGE
A request was made to NMDF_reserve_device for a device that was already reserved.
- -26
- MESSAGE
A request was made to NMDF_exercise_device_reservation for a device that was not reserved.
- -27
- MESSAGE
A request was made to NMDF_exercise_device_reservation with a ticket that was not valid.
- -28
- MESSAGE
A bad file name address was passed to NMDF_convert_name_to_qualiafied_name.
- -29
- MESSAGE
Get or set_device_information was unabale to access the file label extension for a device file.
- -30
- MESSAGE
Nmdf_create_device_or_class could not HPFOPEN a new device file.
- -31
- MESSAGE
NMDF_create_device_or_class could not create the file label extensionfor the device file.
- -32
- MESSAGE
Add_device was called to add a locally connected terminal to Network Server processor.
- 1
- MESSAGE
Nmdf_create_device_or_class was called to create a device class that already exists.
- 2
- MESSAGE
Nmdf_create_class was called to create a class that already exists.
- 3
- MESSAGE
Nmdf_create_device was called to create a device that already exists.
|
Printable version
