[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

459.0. "Error code 5816" by OPCO::TSG_SJM (Coming live to you from Rosebery) Mon Oct 31 1994 21:14

    PCM 1.5-002, VAX 7000-620 V6.1
    
    Over the past week or so, I've started getting the following message,
    from different systems.  Could you please advise what this is telling
    me.
    
    Console link for system <> lost - Unrecognised system error code: 5816
    
    Cheers
    Steve
T.RTitleUserPersonal
Name		DateLines
459.1OPG::PHILIPAnd through the square window...Mon Oct 31 1994 21:3811
Steve,

  Unfortunately the software is getting this code back from one of its system 
  calls during communication with a console. It is an unrecognised error code 
  because sys$getmsg cannot translate it.

  My guess would be that you are low on a quota or two, has anything at all 
  changed on your system as far as either the system configuration or PCM?

Cheers,
Phil
459.2WOTVAX::ELLISMAre you all sitting too comfybold square on your botty? - Then wMon Oct 31 1994 22:496
    Phil,
    
    I'm here with Steve. I presume you are refering to process quotas that
    affect memory usage?
    
    Martin
459.3OPG::PHILIPAnd through the square window...Tue Nov 01 1994 09:4714
Martin,

  Yup, the quotas associated with the daemon process. You
  may have to "tweek" the values in the startup file, if
  you do and get everything running, let me know what you
  changed.

  All this about quotas assumes of course that you have
  already checked out your DECserver connection.

Cheers,
Phil
459.4WOTVAX::ELLISMAre you all sitting too comfybold square on your botty? - Then wTue Nov 01 1994 22:4810
    Phil,
    
    we had checked out the DECserver connection, and it worked. However, we
    have since found out that the DECserver was running out of memory. We
    have done something to correct this, and are monitoring.
    
    Oneof those nasty little problems that is hard to disocover. We'll let
    you know if anything else is required to fix the problem.
    
    Martin