[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

336.0. "Node Icons Missing from C3 Display" by CSC32::C_TOWNSEND () Sat Aug 06 1994 00:32

Hello -

My customer could generate a C3 display, but all the node icons were
missing.  The peripherals were there, but many C3 command functions were
stippled out.  After checking the Editor for the User access and privileges
which were all turned on, I finally found the problem.  

The User name in the Editor had somehow retained some trailing blank or
control character. My customer was an invalid user, so the C3 was displayed
without service node icons.  Regardless of the cause of the invalid
username, my tests confirmed the missing icon behavior.  

I have two requests.

	1.  Strip trailing blanks or non-printable characters
            from fields such as Username
	2.  Display text in that C3 message box like 
            "Invalid User - Access Denied".  

Respectfully submitted,
Connie
T.RTitleUserPersonal
Name		DateLines
336.1OPG::PHILIPAnd through the square window...Sat Aug 06 1994 13:4313
Connie,

  The Username is supposed to have leading and trailing
  spaces trimmed, I will put this on our bug board to
  check out and fix.

  As for the second request, I dont think so, as external
  events sent to ENS via the API may need to be displayed
  but these events may relate to a peripheral which is
  outside the scope of the PCM database.

Cheers,
Phil
336.2Perhaps you could consider this29067::C_TOWNSENDMon Aug 08 1994 22:0122
Hey Phil -

>  As for the second request, I dont think so, as external
>  events sent to ENS via the API may need to be displayed
>  but these events may relate to a peripheral which is
>  outside the scope of the PCM database.

In the case where there are no nodes in the C3 view, what difference 
does it make if there are ENS events to display ... the customer can't 
do anything about them anyway.  How about if we compromise?  

We need some troubleshooting logfiles that are generated on startup.  
Right now customers and CSC support specialists are having to guess what 
might be going on.  Turning on CONSOLE$DEBUG doesn't give the type of 
error messages that are meaningful in managing PCM in a production 
environment.  If we have separate logfiles for the C3, ENS, the 
controllers, network activity etc., then we can reduce troubleshooting 
time and give customers a chance to resolve their own problems as an 
added bonus.  

Respectfully submitted,
Connie
336.3Wouldn't hurt56649::DBIGELOWInnovate, Integrate, EvaporateMon Aug 08 1994 22:254
    Giving the "user xxxx not found in PCM database" certainly would not hurt.
    It could be tucked away in the C3 log file. 
    
Dave
336.429067::BUTTERWORTHGun Control is a steady hand.Mon Aug 08 1994 23:295
    >could be tucked into the C3 logfile
    
    or at least sent to SYS$OUTPUT
    
    Dan
336.5OPG::PHILIPAnd through the square window...Tue Aug 09 1994 10:1423
Connie,

  For the next major version, I am working on separate log
  files for each of the "detached" components, this includes
  each child controller daemon, the messages in these log
  files should be a little more meaningful than those we
  put out today.

  What types of messages would you like to see in these log
  files? as, what is useful to me may not be very useful to
  the average customer.

  As for the C3, thats up to Dave, whatever he decides is
  best, but, yes you can have a C3 without "Nodes" which
  is useful, as when you add "Peripherals" which have the
  same name as the system field in an event record, their
  icons will change colour. Although, in V1.5 you will not
  be able to get the context for these external
  "CMUserSendEvent()" generated events, this is also fixed
  in the next major release..

Cheers,
Phil
336.6Great news!29067::C_TOWNSENDTue Aug 09 1994 19:5122
Phil -

Providing logfiles each time PCM is started would be great ... with a
message timestamp perhaps and in a central location for easy retrieval! 
I'll start compiling some ideas on the type of information or messages that
would be useful, and hope that others in the notesfile will contribute as
well.  What timeframe do we have for getting these ideas to you? 

Another feature of VCS that is appreciated are the on-line 'Message and
Error Recovery Procedures'.  I can issue HELP VCS MESSAGE BADRANGE and get
a brief explanation and 'user action' text.  I haven't located any
information on PCM messages either online or in the documentation.  There
are probably several ways to deliver that kind of information including a
STARS article (to make it real simple for you).  Let me know if I can help.

Thanks for all the hard work.  I realize my requests are far from trivial.

Regards,
Connie
336.7OPG::PHILIPAnd through the square window...Wed Aug 10 1994 10:1713
Connie,

  Give me the ideas anytime, I will slot as many as I
  can in as I go along, add them as replies to this
  note.

  We havnt documented any of the messages up until now
  because of lack of time and resources, I dont see
  this situation changing in the near future.

Cheers,
Phil