GeoCOM Reference Manual 3. Fundamentals of Programming GeoCOM 3.6 COMMON COMMUNICATION ERRORS GeoCOM is based on calling functions remotely. Because of the additional communication layer the set of return codes increases with return codes based on communication errors. Since all of these codes may be returned by any RPC we will explain them here and omit them in the descriptions of the RPC's Return Code 0 Successful termination, implies also no RC_COM_CANT_ENCODE 3073 Can't encode arguments in client Returned by the client to the calling application directly, i.e. without anything being sent to RC_COM_CANT_DECODE 3074 Can,'t decode results in client. Once an RPC has been sent to the server and a reply has been sent back this return code states that the encoded reply could not be decoded in the client. This is usually the result of using different versions of geoCoM on client and server RC COM CANT SEND 3075 Failure in sending calls. If the resources at the ansmitting port have been all previously, i.e. GeoCOM does not have exclusive rights to the port, or if the failure. this error code is returned RC_COM_CANT_RECV 3076 Failure in receiving result. A failure has occurred during reception of a packet at the data link layer. This could be due to incorrect on the line TPS1100-Version l01 3-15
GeoCOM Reference Manual 3 . Fundamentals of Programming GeoCOM TPS1100-Version 1.01 3-15 3.6 COMMON COMMUNICATION ERRORS GeoCOM is based on calling functions remotely. Because of the additional communication layer the set of return codes increases with return codes based on communication errors. Since all of these codes may be returned by any RPC we will explain them here and omit them in the descriptions of the RPC’s. Return Code Val Description RC_OK 0 Successful termination, implies also no communication error. RC_COM_CANT_ENCODE 3073 Can't encode arguments in client. Returned by the client to the calling application directly, i.e. without anything being sent to the transport layer and beyond. RC_COM_CANT_DECODE 3074 Can't decode results in client. Once an RPC has been sent to the server and a reply has been sent back, this return code states that the encoded reply could not be decoded in the client. This is usually the result of using different versions of GeoCOM on client and server. RC_COM_CANT_SEND 3075 Failure in sending calls. If the resources at the transmitting port have been allocated previously, i.e. GeoCOM does not have exclusive rights to the port, or if the exception or similar routine has experienced a failure, this error code is returned. RC_COM_CANT_RECV 3076 Failure in receiving result. A failure has occurred during reception of a packet at the data link layer. This could be due to incorrect parameter settings or noise on the line, etc
GeoCOM Reference Manual 3. Fundamentals of Programming geoCOM Return Code Val Description RC COM TIMEDOUT 3077 Call timed out. The client has sent an RPC to the server but it has not replied within the current time-out period as set for the current transaction. This could be because the server has not received the request; the server has taken too long to client has not received the reply; the communication line(physical layer is longer there or the time-out is too short (especially true when communicating over noisy or radio links at low baud rates) RC_COM- WRONG- FORMAT 3078 The request and receive formats are different mixed up along or the application tried to send using a format which has not been implemented on both client and RC_COM_VER_MISMATCH 3079 RPC protocol mismatch error. An RPC protocol has been requested which does not exist. This error will indicate incompatible client and server protocols C_COM_CANTDECODE_3080 Can't decode request in server. If the client REQ sends the RPC but one which be decoded in replies with this error. It could be that the GeoCOM versions running on the client and server are different or the packet was not correctly sent over a noisy or unreliable line RC_COM_PROC_UNAVAIL 3081 The requested procedure is unavailable in the server. An attempt has been made to call an RPC which does not nis is usually between the differing versions of GeoCOM on client and server. To be on the safe side al ways use the same GeoCOM version whenever possible on both sides TPS1100-Version l01 3-16
GeoCOM Reference Manual 3 . Fundamentals of Programming GeoCOM TPS1100-Version 1.01 3-16 Return Code Val Description RC_COM_TIMEDOUT 3077 Call timed out. The client has sent an RPC to the server but it has not replied within the current time-out period as set for the current transaction. This could be because: the server has not received the request; the server has taken too long to execute the request; the client has not received the reply; the communication line (physical layer is no longer there; or, the time-out is too short (especially true when communicating over noisy or radio links at low baud rates). RC_COM_WRONG_FORMAT 3078 The request and receive formats are different. Something got mixed up along the way or the application tried to send using a format which has not been implemented on both client and server. RC_COM_VER_MISMATCH 3079 RPC protocol mismatch error. An RPC protocol has been requested which does not exist. This error will indicate incompatible client and server protocols. RC_COM_CANT_DECODE_ REQ 3080 Can't decode request in server. If the client sends the server an RPC but one which cannot be decoded in the server, the server replies with this error. It could be that the GeoCOM versions running on the client and server are different or the packet was not correctly sent over a noisy or unreliable line. RC_COM_PROC_UNAVAIL 3081 The requested procedure is unavailable in the server. An attempt has been made to call an RPC, which does not exist. This is usually caused when calling RPC’s which have been inserted, appended, deleted, or altered between the differing versions of GeoCOM on client and server. To be on the safe side, always use the same GeoCOM version whenever possible on both sides
GeoCOM Reference Manual 3. Fundamentals of Programming geoCOM Return Code Val Description RC_COM_CANT_ENCODE_ 3082 Can,t encode reply in server. The server has REP attempted to encode the reply but has failed This can be caused by the calling procedure trying to pass too much data back to the client and in so doing has exceeded the maximum RC COM SYSTEM ERR 3083 Communication hardware error RC COM FAILED 3085 Mess into communication itself Should be OK once the node has been recycled, i.e powered-down and -up again RC COM NO BINARY 3086 Unknown protocol. An unknown(or not yet upported) Transport or Network protocol has been used. Could appear when using differing GeoCOM versions on client and server RC COM INTR 3087 Call interrupted. Something has happened outside of the scope of GeoCOM, which has forced the current RPC to abort itself RC COM REQUIRE 8DBITS s_3090 This error indicates desired protocol requires 8 data bits C COM TR ID 3093 Request and reply transaction ids do not MISMATCH match. Somewhere along the line a packet (usually a reply) has been lost or delayed GeoCOM tries to bring everything back to order but if this error continues during the ession it b to inspect the line and at least, to restart the session. The immediately following RPC may be lost. RC_COM_NOT_GEOCOM 3094 Parse failed; data package not recognised as GeoCOM communication package RC_COM_UNKNOWN_PORT 3095 Tried to access an unknown hardware port. The application has not taken the physical resources of the machine on which it is running into account TPS1100-Version l01 3-17
GeoCOM Reference Manual 3 . Fundamentals of Programming GeoCOM TPS1100-Version 1.01 3-17 Return Code Val Description RC_COM_CANT_ENCODE_ REP 3082 Can't encode reply in server. The server has attempted to encode the reply but has failed. This can be caused by the calling procedure trying to pass too much data back to the client and in so doing has exceeded the maximum packet length. RC_COM_SYSTEM_ERR 3083 Communication hardware error RC_COM_FAILED 3085 Mess into communication itself. Should be OK once the node has been recycled, i.e. powered-down and -up again. RC_COM_NO_BINARY 3086 Unknown protocol. An unknown (or not yet supported) Transport or Network protocol has been used. Could appear when using differing GeoCOM versions on client and server. RC_COM_INTR 3087 Call interrupted. Something has happened outside of the scope of GeoCOM, which has forced the current RPC to abort itself. RC_COM_REQUIRES_ 8DBITS 3090 This error indicates desired protocol requires 8 data bits RC_COM_TR_ID_ MISMATCH 3093 Request and reply transaction ids do not match. Somewhere along the line a packet (usually a reply) has been lost or delayed. GeoCOM tries to bring everything back to order but if this error continues during the session it may be wise to inspect the line and, at least, to restart the session. The immediately following RPC may be lost. RC_COM_NOT_GEOCOM 3094 Parse failed; data package not recognised as GeoCOM communication package RC_COM_UNKNOWN_PORT 3095 Tried to access an unknown hardware port. The application has not taken the physical resources of the machine on which it is running into account
GeoCOM Reference Manual 3. Fundamentals of Programming GeoCOM Return Code Val Description RC COM OVERRUN 3100 Overruns during receive A packet has been received which has exceeded the maxim acket length. It will be discarded! This can be caused by a noisy line during GeoCOM Binary format transmissions IC COM SRVR RX 3101 Checksum received at server is wrong.The CHECKSUM ERROR checksum belonging to the current packet is wrong-no attempt is made at decoding the LC COM CLNT RX 3102 Checksum received at client is wrong. The CHECKSUM ERROR checksum belonging to the current packet is wrong-no attempt is made at decoding the 3103 COM port not available. This can be caused VAILABLE by attempting to open a port for unique use by GeoCoM, which has already been allocated to another application. RC COM PORT NO 3104 COM port not opened /initialised. The application has attempted COM port to which it has no unique rights RC_COMNO_PARTNER 3105 No communications partner on other end The connection to the partner could not be made or has been lost. Check that the line is there and try RC COM ERO NOT STARTED 3106The client, after calling an ERO has decided not to confirm the start of the ero and has instead called another RPC RC COM CONS REQ 3107 Attention to send consecutive requests.The application has attempted to send another request before it has received a reply to its original request. Although GeoCOM does not return control to the app until a reply is received, this error is still possible with event-driven applications, i.e., the user pushing a button yields control back to the application code which can then call GeoCOM agai TPS1100-Version l01 3-18
GeoCOM Reference Manual 3 . Fundamentals of Programming GeoCOM TPS1100-Version 1.01 3-18 Return Code Val Description RC_COM_OVERRUN 3100 Overruns during receive. A packet has been received which has exceeded the maximum packet length. It will be discarded! This can be caused by a noisy line during GeoCOM Binary format transmissions. RC_COM_SRVR_RX_ CHECKSUM_ERROR 3101 Checksum received at server is wrong. The checksum belonging to the current packet is wrong - no attempt is made at decoding the packet. RC_COM_CLNT_RX_ CHECKSUM_ERROR 3102 Checksum received at client is wrong. The checksum belonging to the current packet is wrong - no attempt is made at decoding the packet. RC_COM_PORT_NOT_ AVAILABLE 3103 COM port not available. This can be caused by attempting to open a port for unique use by GeoCOM, which has already been allocated to another application. RC_COM_PORT_NOT_ OPEN 3104 COM port not opened / initialised. The application has attempted to use a COM port to which it has no unique rights. RC_COM_NO_PARTNER 3105 No communications partner on other end. The connection to the partner could not be made or has been lost. Check that the line is there and try again. RC_COM_ERO_NOT_ STARTED 3106 The client, after calling an ERO has decided not to confirm the start of the ERO and has instead called another RPC. RC_COM_CONS_REQ 3107 Attention to send consecutive requests. The application has attempted to send another request before it has received a reply to its original request. Although GeoCOM does not return control to the app until a reply is received, this error is still possible with event-driven applications, i.e., the user pushing a button yields control back to the application code which can then call GeoCOM again
GeoCOM Reference Manual 3. Fundamentals of Programming GeoCOM Return Code Val Description RC COM SRVR IS 3108 TPS has gone to sleep. Wait and try again SLEEPING RC-COM-SRVR IS_-OFF3109TPS has shut down. Wait and try again TPS1100-Version 1.01 3-19
GeoCOM Reference Manual 3 . Fundamentals of Programming GeoCOM TPS1100-Version 1.01 3-19 Return Code Val Description RC_COM_SRVR_IS_ SLEEPING 3108 TPS has gone to sleep. Wait and try again. RC_COM_SRVR_IS_OFF 3109 TPS has shut down. Wait and try again