MSIR.0169 SYBMSG(20169,15,1) Implicit conversion from datatype '(itype)' to '(otype)' is not allowed.: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Created page with "This message indicates that a request on an EXEC2RPC port had an implicit type conversion that is not supported by EXEC2RPC processing. This message can be caused by a client app...")
 
(Automatically generated page update)
 
(11 intermediate revisions by 4 users not shown)
Line 1: Line 1:
This message indicates that a request on an EXEC2RPC port had an implicit type conversion that is not supported by EXEC2RPC processing. This message can be caused by a client application error or a client application trying to use an implicit type conversion not supported by ''[[Janus Open Server]]'' EXEC2RPC processing. See the ''Janus Open Server Reference Manual'' for the type conversions supported by EXEC2RPC processing. This message can also be caused by an attempt to send generic SQL code to an EXEC2RPC port or perhaps by an ODBC driver sending unknown SQL code to the ''[[Janus Open Server]]'' port. In the latter case, contact Sirius Software technical support to determine if it is possible to make ''[[Janus Open Server]]'' support the ODBC driver or if it is necessary to switch to another ODBC driver or to access ''[[Janus Open Server]]'' through some middleware such as a Sybase Adaptive Server.
This message indicates that a request on an EXEC2RPC port had an implicit type conversion that is not supported by EXEC2RPC processing. This message can be caused by a client application error or by a client application trying to use an implicit type conversion not supported by <var class="product">Janus Open Server</var> EXEC2RPC processing. See the <var class="book">[[Media:JosrvrNew.pdf|Janus Open Server Reference Manual]]</var> for the type conversions supported by EXEC2RPC processing.  


[[Category:Sirius Mods Messages]]
This message can also be caused by an attempt to send generic SQL code to an EXEC2RPC port or perhaps by an ODBC driver sending unknown SQL code to the Janus Open Server port. In the latter case, contact [[Contacting Rocket Software Technical Support|Technical Support]] to determine if it is possible to make Janus Open Server support the ODBC driver or if it is necessary to switch to another ODBC driver or to access Janus Open Server through some middleware such as a Sybase Adaptive Server.
 
{{Template:MSIR.0169 footer}}
[[Category:MSIR.0001 - MSIR.0199]]

Latest revision as of 23:00, 3 March 2017

This message indicates that a request on an EXEC2RPC port had an implicit type conversion that is not supported by EXEC2RPC processing. This message can be caused by a client application error or by a client application trying to use an implicit type conversion not supported by Janus Open Server EXEC2RPC processing. See the Janus Open Server Reference Manual for the type conversions supported by EXEC2RPC processing.

This message can also be caused by an attempt to send generic SQL code to an EXEC2RPC port or perhaps by an ODBC driver sending unknown SQL code to the Janus Open Server port. In the latter case, contact Technical Support to determine if it is possible to make Janus Open Server support the ODBC driver or if it is necessary to switch to another ODBC driver or to access Janus Open Server through some middleware such as a Sybase Adaptive Server.


Message attributes:

RETCODEO=0Sets online return code
RETCODEB=0Sets batch (single user) return code
CLASS=IInformation class; the message can be suppressed with the X'02' bit setting of the MSGCTL parameter
AUDITMSWrites the message with line type MS to the audit trail
NOCOUNTDoes not increment the error count (ERCNT) parameter
NOTERMDoes not display the message on the user's terminal

Back to list of messages