[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

556.0. "Unrecognised system error code 5808" by COMICS::JUDD (Geoff Judd. UK TSC. Viables, Basingstoke) Fri Jan 13 1995 13:30

Hi,
  This note was originally posted as a reply to note 481 but did not get a 
response so I have created a new note in case it got missed.

Thanks,

Geoff Judd.

          <<< OPG::DISK$TOOLS:[NOTES$LIBRARY]CONSOLEMANAGER.NOTE;1 >>>
                        -< POLYCENTER Console Manager >-
================================================================================
Note 481.2                More unrecognised error codes                   2 of 2
COMICS::JUDD "Geoff Judd. UK TSC. Viables, Basingstoke"  20 lines   3-JAN-1995 15:24
                        -< Another occurrence of 5808 >-
--------------------------------------------------------------------------------
Hi,
  I have had a  customer report this problem on a PCM V1.5 system running on
OpenVMS VAX V6.1. The monitored system that caused the problem is a DEC 
4000-720 running OpenVMS AXP V6.1 connected via LAT. The console was connected to 
via PCM and was at the >>> prompt. the monitored system was then powered on and 
off. PCM then reported the event "Unrecognised system error code 5808" and 
communication was lost to the console. The customer tried reconfiguring PCM but
communication was not restored. The customer then shutdown PCM and was able to 
define a LAT port and connect to the system using SET HOST/DTE. PCM was then 
restarted and communication to the port was OK.

It is stated in the previous reply the error code means that it is not recognised 
by PCM. What system call(s) are returning these errors. Is possible that the 
error message isn't being passed so correctly ie. the error code reported isn't 
actual error code ? Would more information be found in CONTROLLER_nn.LOG if 
CONSOLE$DEBUG was set xx ? (If so what should xx be set to ?)

Thanks,

Geoff.
T.RTitleUserPersonal
Name
DateLines
556.1CSC32::BUTTERWORTHGun Control is a steady hand.Fri Jan 13 1995 22:5216
    Geoff,
      SOme more info would defintely help. I took a real quick cursory look
    a while back and it "appeared" to emanate from the LAT code via the
    IOSB in a QIO. If this really is the case what we should be putting out
    is the internal LAT code that is the high-order word of the 2nd
    longword of the IOSB. We can create a debugging image to do this if
    need be but first I think it might help if we had some more context for
    the message. If you define
    
    DEFINE/SYSTEM CONSOLE$DEBUG DAEMON
    
    you'll get *a lot* of information in the controller log in CONSOLE$TMP.
    
    
    Regards,
       Dan