 |
» |
|
|
|
- -11001
- MESSAGE
Invalid itemnum specified in itemnums array.
- CAUSE
Item number is not valid for this call.
- ACTION
Check the logic of your application.
- -11002
- MESSAGE
Invalid create option.
- CAUSE
The value given for the create option is not a valid value.
- ACTION
Check the logic of your application.
- -11003
- MESSAGE
The Max message size parm is more than
the maximum allowed, or less than 0.
- CAUSE
The value for max_msg_size is out of range.
- ACTION
Check the logic of your application.
- -11004
- MESSAGE
Normal message size is more than
the maximum allowed, or less then zero.
- CAUSE
The value for normal_msg_size is out of range.
- ACTION
Check the logic of your application.
- -11005
- MESSAGE
Max number of messages is less than 0 or more than
the maximum allowed.
- CAUSE
The max_norm_msgs value is out of range.
- ACTION
Check the logic of your application.
- -11006
- MESSAGE
Normal message size specified is more than the
maximum message size.
- CAUSE
Normal size cannot be larger than maximum size.
- ACTION
Check the logic of your application.
- -11007
- MESSAGE
Num normal msgs * norm_msg_size NOT >= max_msg_size.
- CAUSE
Must have room for at least one max sized message.
- ACTION
Check the logic of your application.
|
- -11008
- MESSAGE
Timeout value not >= -1.
- CAUSE
Timeout value is out of range.
- ACTION
Check the logic of your application.
- -11009
- MESSAGE
Priority value not between 0 and 31 for AIFPORTSEND.
- CAUSE
Priority is out of range.
- ACTION
Check the logic of your application.
- -11010
- MESSAGE
Open of existing port failed; port does not exist.
- CAUSE
Opened old port, but port does not exist.
- ACTION
Check the logic of your application.
- -11011
- MESSAGE
Open of new port failed; port already exists.
- CAUSE
Opened new port, but port already exists.
- ACTION
Check the logic of your application.
- -11012
- MESSAGE
Max msg size specified > max size when port was created.
- CAUSE
Port was created with a smaller max size than passed in this call.
- ACTION
Check the logic of your application.
- -11013
- MESSAGE
Num_norm_msgs specified is more than originally allowed.
- CAUSE
Num_norm_msgs is greater than number specified when port was
created.
- ACTION
Check the logic of your application.
- -11014
- MESSAGE
Invalid creation option for an asynchronous port.
- CAUSE
Item 11201 was not specified with a value of 2.
- ACTION
Check the logic of your application.
- -11015
- MESSAGE
Invalid option, asynchronous ports cannot be permanent.
- CAUSE
Item 11205 cannot be specified with an async port.
- ACTION
Check the logic of your application.
|
- -11016
- MESSAGE
Invalid option combination between connectionless/waited.
- CAUSE
Connectionless sends must specify item 11101 with a value of -1
nowait.
- ACTION
Check the logic of your application.
- -11017
- MESSAGE
Invalid port was specified to AIFPORTINT.
- CAUSE
An invalid asynchronous port id was specified.
- ACTION
Check the logic of your application.
- -11018
- MESSAGE
Invalid creation option for asynchronous port.
- CAUSE
Item 11207 interrupt state was specified without item 11206 handler
address.
- ACTION
Check the logic of your application.
- -11019
- MESSAGE
Invalid send to an asynchronous port, no receiver exists.
- CAUSE
The receiver has closed the asynchronous port before the sender, or
the receiver process has terminated.
- ACTION
Close the port and check the logic of your application.
- -11020
- MESSAGE
A send was issued against a port which no longer exists.
- CAUSE
A portid was specified for a port which is no longer open.
- ACTION
Check the logic of your application.
- -11023
- MESSAGE
Invalid option combination portid = 0 and item 11007 is true.
- CAUSE
A single asynchronous portid is required when item 11007 is used on
the AIFPORTRECEIVE call.
- ACTION
Check the logic of your application.
- -11024
- MESSAGE
An invalid receive option was used on a synchronous port.
- CAUSE
Item 11007 can only be used an asynchronous portid.
- ACTION
Check the logic of your application.
- -11025
- MESSAGE
There are no more messages with pending interrupts. No message
was received.
- CAUSE
There currrently are no messages with pending interrups on the
port.
- ACTION
Check the logic of your application.
|
|
