| 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 |
Hi!
My customer is running PCM V1.5 + MUP on an ALPHASTATION 400.
Everything works fine except the access to a PSEUDO TERMINAL
standing for a X25 Router. The exact same thing works from another
station. The problems bellow occure after an unpredictable amount of
time. They can only be fixed by rebooting the PCM Station
PRoblem:
trieing to connect to the pseudo terminal results in:
10:52:05 No Privilege to access System, Ignoring (null)
10:52:05 No Privilege to access System, Ignoring fspec
10:52:05 No Systems for watch operation specified
10:52:06 POLYCENTER Console Manager
10:52:06 Watch facility Version V1.5-006
10:52:06 Copyright (c) 1994 Digital Equipment Corporation. All Rights
Reserved
10:52:06
10:52:06 No Privilege to access System, Ignoring (null)
10:52:06 No Privilege to access System, Ignoring fspec
10:52:06 No Systems for watch operation specified
10:52:07 POLYCENTER Console Manager
10:52:07 Watch facility Version V1.5-006
10:52:07 Copyright (c) 1994 Digital Equipment Corporation. All Rights
Reserved
10:52:07
.
.
.
Definition:
PCM Edit> sho system x25ca1
Full or Brief listing? [f=full, b=brief] (b): f
Output file (SYS$OUTPUT):
System Name = X25CA1
Information =
Connection = Pseudo-Terminal
Command = CONSOLE WATCH CAVI02 /OUT=TT
Scan Profile = SCAN_X25CA1 Scan Profile for X25-Router
Icon filename = LANBRIDGE.XBM
Console line = Enabled
Logging is enabled, directory = CONSOLE$LOGFILES
2.nd Station that has NO PROBLEMS:
PCM Edit> sho system cabvtx
Full or Brief listing? [f=full, b=brief] (b): f
Output file (SYS$OUTPUT):
System Name = CABVTx
Information = OETOB TRADER STATIONS
Connection = Pseudo-Terminal
Command = CONSOLE WATCH CAVI04 /OUT=TT
Scan Profile = SCAN_OETOB_LAVC Scan for OETOB Workstation
Icon filename = VAXSTATION_3100.XBM
Console line = Enabled
Logging is enabled, directory = CONSOLE$LOGFILES
Status of the PSEUDO TERMINAL when problem occures:
System ............: CABVTx
Enabled ...........: Yes
Line status .......: OK
In use by .........:
Parent pid ........: 0000011A
Connection type....: Pseudo-Terminal
Logging device ....: 16% Full
Last Archive ......: None Performed
Lines of data .....: 44.1K Bytes: 1.71M
Event total .......: 0
Crit: 0 Maj: 0 Min: 0 Warn: 0 Clr: 0 Ind: 0
IS this a known Problem (BUG,Parameter,...)
thanks
Michael
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1014.1 | ZENDIA::DBIGELOW | Innovate, Integrate, Evaporate | Mon Oct 02 1995 10:37 | 12 | |
Not sure exactly what you are trying to do here. Why do you do a
'console watch' within a pseudo-terminal? It seems to be a waste of a
license.
What does the definition for system CAVIO2 and CAVIO4 look like?
Can you enter the editor and do a 'sho system CAVIO2' and 'show system
CAVIO4' command?
Are you comfortable with the understaing of PCM and what a
pseudo-terminal is?
Dave
| |||||
| 1014.2 | more infos available | 49312::VNABRW::KARTNER_M | This is the road to hell | Mon Oct 02 1995 12:53 | 19 |
Hi!
Hera are some new infos
1) the problem occures on both systems (not only on one as mentioned)
after about a day of normal operation
2) the only workaround to the problem is a "shutdown"/"startup" from
the graphical interface. Restart or reconfig doesn't work.
3) the workaround for the daemon-problems (set hidden) is allready in
use.
thanks
Michael
PS.: If the customer gets a problem with the X25 gateway he doesn't
want that the colour of the VAX is switched to red, so he uses
a pseudo terminal
| |||||
| 1014.3 | more infos | 49312::VNABRW::KARTNER_M | This is the road to hell | Tue Oct 03 1995 11:16 | 54 |
Here are the definitions of the 2 nodes:
PCM Edit> sho system cavi02
Full or Brief listing? [f=full, b=brief] (b): f
Output file (SYS$OUTPUT):
System Name = CAVI02
Information = Wallstreet Backup
Connection = LAT (terminal server)
Terminal Server = SERVV2
Server Port = PORT_2
Scan Profile = SCAN_WALLSTREET Wallstreet System
Icon filename = VAX_7000.XBM
Console line = Enabled
Logging is enabled, directory = CONSOLE$LOGFILES
PCM Edit> sho system cavi04
Full or Brief listing? [f=full, b=brief] (b): f
Output file (SYS$OUTPUT):
System Name = CAVI04
Information = OETOB
Connection = LAT (terminal server)
Terminal Server = SERVV2
Server Port = PORT_4
Scan Profile = SCAN_OETOB OETOB System
Icon filename = VAX_6000.XBM
Console line = Enabled
Logging is enabled, directory = CONSOLE$LOGFILES
PCM Edit> sho system cabvtx
Full or Brief listing? [f=full, b=brief] (b): f
Output file (SYS$OUTPUT):
System Name = CABVTx
Information = OETOB TRADER STATIONS
Connection = Pseudo-Terminal
Command = CONSOLE WATCH CAVI04 /OUT=tt
Scan Profile = SCAN_OETOB_LAVC Scan for OETOB Workstation
Icon filename = VAXSTATION_3100.XBM
Console line = Enabled
Logging is enabled, directory = CONSOLE$LOGFILES
PCM Edit> sho system x25ca1
Full or Brief listing? [f=full, b=brief] (b): f
Output file (SYS$OUTPUT):
System Name = X25CA1
Information = X25 Router
Connection = Pseudo-Terminal
Command = CONSOLE WATCH CAVI02 /OUT=tt
Scan Profile = SCAN_X25CA1 Scan Profile for X25-Router
Icon filename = LANBRIDGE.XBM
Console line = Enabled
Logging is enabled, directory = CONSOLE$LOGFILES
thanks
Michael
| |||||
| 1014.4 | ZENDIA::DBIGELOW | Innovate, Integrate, Evaporate | Tue Oct 03 1995 11:44 | 8 | |
I can't see anything wrong with the setup. You could disable logging
for the pseudo-terminal to save some overhead and disk space.
I still can't really see why this is done this way. If they don't wnat
to see 'Red' they can lower the priority of the events that they are
trapping. Would Green be ok?
Dave
| |||||
| 1014.5 | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Mon Oct 09 1995 12:39 | 10 | |
I suspect that you have a symbol or logical of CAVIO2 and CAVI04. PCM
uses the C RTL getenv which translates symbols and logicals. The error
messages posted in .0 indicate that the user running the watch command
doesn't have a user record in the PCM database. If you started things
up under the SYSTEM account you'll always have access. If you didn't
then this could be part of the problem.
Regs,
Dan
| |||||