| 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 |
Dave -
Can you give us some tips on troubleshooting the C3? I have a customer
with multiple problems, but I'm stumped when trying to troubleshoot the
issues when I can't reproduce them. The file CONSOLE$C3_C_user_MSG.LOG;1
hasn't given any clues, and I don't know if CONSOLE$DEBUG is the ultimate
answer. Any suggestions would be welcomed.
Appreciatively,
Connie
P.S. If you are interested in the problems ...
1. When editing the C3 to modify the Break key, the customer gets
mixed results - sometimes the setting works and sometimes it
doesn't. He has been up and down the alphabet, and back.
The C3 is generated from the SYSTEM account with CONSOLE C3.
Saving the settings and reconfiguring is a given.
2. Two users with two C3 displays attempt to CONNECT to the same
system at the same time... PCM crashes requiring a restart.
I don't know at this time which images expire, but could find
out if you are interested.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 534.1 | Some suggestions | ZENDIA::DBIGELOW | Innovate, Integrate, Evaporate | Thu Dec 22 1994 21:30 | 23 |
Connie,
1. The problem with the key definitions is fixed in the MUP kit.
2. This isn't a problem with the C3. There were a lot of bugs fixed in
MUP kit, so have the customer install it and we'll take it from
there.
As for general debugging of the C3, you can define the logical as
follows:
For Unix: setenv CONSOLE_DEBUG C3
For VMS define CONSOLE$DEBUG C3
and then restart the C3. You should see a flurry of information. The
C3 will also run at a slower pace, because X windows synchronization
is turned off. There is also the local C3 resource database which you
can modify. It has the control keys defined. They could modify this
file manually until they get the MUP. Tell the customer to make
a copy before modifying. The name of the file is called console$c3.dat
or .consolec3rc, depending on platform
Dave
| |||||
| 534.2 | Thanks again ... | CSC32::C_TOWNSEND | Thu Dec 22 1994 23:09 | 7 | |
Dave, Sounds like the MUP is the ticket for now. We'll console$debug if problems persist. Happy holidays, Connie | |||||