List of RSI Error Codes

Edit online

All RSI subroutines use constants to define error codes.

The RSI Error Code table lists the error descriptions.

Symbolic Name Number Description
RSiTimeout 280 A time-out occurred while waiting for a response to a request.
RSiBusy 281 An RSiOpenx subroutine was issued, but another is already active.
RSiSendErr 282 An error occurred when the library attempted to send a UDP packet with the sendto() system call.
RSiPollErr 283 A system error occurred while issuing or processing a poll() or select() system call.
RSiRecvErr 284 A system error occurred while attempting to read an incoming UDP packet with the recvfrom() system call.
RSiSizeErr 285 A recvfrom() system call returned a UDP packet with incorrect length or incorrect source address.
RSiResync 286 While waiting for a response to an outgoing request, one of the following occurred and cause an error return to the calling program:
  1. An error occurred while processing an exception packet.
  2. An error occurred while processing an i_am_back packet.
  3. An i_am_back packet was received in response to an output request other than are_you_there.
  4. While waiting for a response to an outgoing request, some asynchronous function closed the handle for the remote host.
The code may also be set when a success return code is returned to the caller, in which case it shows that either an exception packet or an i_am_back packet was processed successfully while waiting for a response.
RSiBadStat 287 A bad status code was received in the data packet received.
RSiBadArg 288 An argument that is not valid was passed to an RSi subroutine.
RSiBadHost 289 A valid host address cannot be constructed from an IP address or the nameservice doesn't know the hostname.
RSiDupHost 290 An RSiOpenx call was issued against a host but a connection is already open to a host with this IP address and a different hostname.
RSiSockErr 291 An error occurred while opening or communicating with a socket.
RSiNoPort 292 The RSi is unable to find the port number to use when inviting remote suppliers. The likely cause is that the xmquery entry is missing from the /etc/services file or the NIS (Yellow Pages) server.
RSiNoMatch 293 One of the following occurred:
  1. The SpmiStatVals argument on the RSiStatGetPathx call is not valid.
  2. On an RSiPathAddSetStatx call, the SpmiStatSet argument is not valid or the path name given in the last argument does not exist.
  3. On an RSiAddSetHotx call, the SpmiHotSet argument is not valid, the grand parent context doesn't exist or none of its subcontexts contain the specified statistic.
  4. On an RSiDelSetStatx call, the SpmiStatSet or the SpmiStatVals argument is not valid.
  5. On an RSiDelSetHotx call, the SpmiHotSet or the SpmiHotVals argument is not valid.
  6. On an RSiPathGetCxx call, the path name given does not exist. On an RSiGetValuex or RSiGetRawValuex call, the SpmiStatVals argument is not valid.
  7. On an RSiGetHotItemx call, the SpmiHotSet argument was not valid.
RSiInstErr 294 An error was returned when attempting to instantiate a remote context.
RSiNoFeed 295 When extracting a data value with the RSiGetValuex call, the data value was marked as not valid by the remote data supplier.
RSiTooMany 296 An attempt was made to add more values to a statset than the current buffer size permits.
RSiNoMem 297 Memory allocation error.
RSiNotInit 298 An RSi call was attempted before an RSiInitx call was issued.
RSiNoLicense 299 License expired or no license found.
RSiNotSupported 300 The subroutine call requires a later protocol version that is the one supported by the remote system's xmtopas daemon.