MSIR.0916 Could not connect to (ipaddr) port (portnum): Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (1 revision)
(Automatically generated page update)
 
(7 intermediate revisions by 3 users not shown)
Line 1: Line 1:
This message indicates that a SIRIUS DEBUG or SIRIUSDEBUG command failed because it was unable to connect to the indicated debugging client. <li>th The most common causes for this problem are:
This message indicates that a [[SIRIUS DEBUG, SIRDEBUG, or SIRIUSDEBUG command]] failed because it was unable to connect to the indicated debugging client. The most common causes for this problem are:


<ul> <li>The target client's IP address or host name was incorrect. Correct the address of host name. <li>The target client's port number was incorrect. Correct the port number. <li>The debugging client was not started on the target workstation. Start the debugger client on the workstation and reissue the command. Note that the client must be installed on the target workstation. For more information about the Sirius Debugger client see the ''"Janus/Sirius Debugger User's Guide"''.</ul> This message should be preceded by other messages giving more details about the nature of the communications error. If the problem is still not obvious, contact Sirius Software technical support for assistance.
<ul>  
<li>The target client's IP address or host name was incorrect. Correct the address of host name.  


[[Category:Sirius Mods Messages]]
<li>The target client's port number was incorrect. Correct the port number.
 
<li>The debugging client was not started on the target workstation. Start the Debugger Client on the workstation, and reissue the command. Note that the client must be installed on the target workstation. For more information about the Debugger client, see the <var class="book">[http://sirius-software.com/maint/download/jdebugr.pdf Janus/Sirius Debugger User's Guide]</var>.
</ul>
 
This message should be preceded by other messages giving more details about the nature of the communications error. If the problem is still not obvious, contact [[Contacting Rocket Software Technical Support|Technical Support]] for assistance.
 
{{Template:MSIR.0916 footer}}
[[Category:MSIR.0800 - MSIR.0999]]

Latest revision as of 23:36, 3 March 2017

This message indicates that a SIRIUS DEBUG, SIRDEBUG, or SIRIUSDEBUG command failed because it was unable to connect to the indicated debugging client. The most common causes for this problem are:

  • The target client's IP address or host name was incorrect. Correct the address of host name.
  • The target client's port number was incorrect. Correct the port number.
  • The debugging client was not started on the target workstation. Start the Debugger Client on the workstation, and reissue the command. Note that the client must be installed on the target workstation. For more information about the Debugger client, see the Janus/Sirius Debugger User's Guide.

This message should be preceded by other messages giving more details about the nature of the communications error. If the problem is still not obvious, contact Technical Support for assistance.


Message attributes:

RETCODEO=0Sets online return code
RETCODEB=4Sets batch (single user) return code
CLASS=EError class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter
AUDITERWrites the message with line type ER to the audit trail
COUNTIncrements the error count (ERCNT) parameter

Back to list of messages