Code | Meaning | Action |
|
|
|
134 | No 802 path records. The | One or both of the following |
| request could not be satisfied | actions may be taken: (1) Retry |
| because IEEE 802.3 did not | the request later after some |
| have an available path record. | NetIPC connections have been |
| Such path records are used to | aborted and some IEEE 802.3 |
| hold protocol context and | path records have been |
| addressing information. | released; or (2) ask the System |
|
| Manager to configure more IEEE |
|
| 802.3 path records into the |
|
| system. |
|
|
|
135 | No TCP path records. The | One or both of the following |
| request could not be satisfied | actions may be taken: (1) Retry |
| because TCP did not have an | the request later after some |
| available path record. Such | NetIPC connections or call |
| path records are used to hold | sockets have been aborted; or |
| protocol addressing and context | (2) ask the System Manager to |
| information. | configure more TCP path |
|
| records into the system. |
|
|
|
136 | Bad upper bound. A bad upper | Check the value of the |
| descriptor bound was specified | descriptor bound parameter to |
| while invoking IPCSelect. | verify that its value was the |
|
| intended one. |
|
|
|
1001 | Cannot read select on the | The socket has been gracefully |
| socket now. | released by the remote and the |
|
| user has been informed about it. |
|
| Hence, there will be no more |
|
| data on that socket. |
|
|
|
Numeric Error Codes 221