MSIR.0152 SYBMSG(20152,14,1) Language request invalid on RPCONLY port.: Difference between revisions

From m204wiki
Jump to navigation Jump to search
mNo edit summary
(Automatically generated page update)
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
This message indicates that a client to a [http://m204wiki.rocketsoftware.com/images/1/17/JosrvrNew.pdf Janus Open Server] port attempted to issue a language request (probably a SQL statement) but the port was defined as RPCONLY. This could simply indicate a error in the client code or it could indicate a need to support language requests in the port's <var class="product">Janus Open Server</var> application code. It is also possible that some intermediate code on the client machine (such as an ODBC driver) is actually generating the language request. Turning on RPC/language tracing on the port via a "JANUS TRACE 3" command and re-running the request will cause the offending language request (along with any valid RPC's) to be sent to the <var class="product">Model 204</var> audit trail as RK lines.
This message indicates that a client to a [http://m204wiki.rocketsoftware.com/images/1/17/JosrvrNew.pdf Janus Open Server] port attempted to issue a language request (probably a SQL statement) but the port was defined as RPCONLY. This could simply indicate a error in the client code or it could indicate a need to support language requests in the port's <var class="product">Janus Open Server</var> application code. It is also possible that some intermediate code on the client machine (such as an ODBC driver) is actually generating the language request. Turning on RPC/language tracing on the port via a "JANUS TRACE 3" command and re-running the request will cause the offending language request (along with any valid RPC's) to be sent to the <var class="product">Model 204</var> audit trail as RK lines.


[[Category:Sirius Mods messages]]
{{Template:MSIR.0152 footer}}
[[Category:MSIR.0001 - MSIR.0199]]

Latest revision as of 23:00, 3 March 2017

This message indicates that a client to a Janus Open Server port attempted to issue a language request (probably a SQL statement) but the port was defined as RPCONLY. This could simply indicate a error in the client code or it could indicate a need to support language requests in the port's Janus Open Server application code. It is also possible that some intermediate code on the client machine (such as an ODBC driver) is actually generating the language request. Turning on RPC/language tracing on the port via a "JANUS TRACE 3" command and re-running the request will cause the offending language request (along with any valid RPC's) to be sent to the Model 204 audit trail as RK lines.


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