[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

1157.0. "How many CFS_125 patches have we ?" by 48243::MENICACCI () Fri Jan 19 1996 08:42

	Hi,

a customer is running PCM V1.6 + ECO 1, on OpenVMS V6.2 (both VAX and ALPHA).
He reported to me the problem already discussed here notes 932 and 1100, which
appeared with OpenVMS V6.2 (not seen on OpenVMS V6.1).

i.e console monitor is hung after a few seconds ...

As I read this conference very often, it sounded fixed to me and I gave the
patches located in : CSC32::dumps:[butterworth.pcm]. (csc_125_vax.bck and
csc_124_axp.bck).

Patches got installed and ... to my surprise the problem is still there.

The sub_process running console$conmon.exe became LEF after a few seconds
(waiting in SYS$QUIOW).

I read the IPMT CFS32266 which is closed : correction given by NSI_111_smg.bck
and NSI_111_V.bck.

I believed that CFS_125 was a patch replacing these old ones !!!

Then, I copied pcmsvr::pcmsvr$dkb500:[eco.cfs_125]vax62.bck, extracted 
console$conmon.exe and compared it to console$conmom.exe from csc_125_vax.bck
and it's not the same.

I supposed that this is because one got created on OpenVMS V6.1 and the other
one on OpenVMS V6.2, isn't it ?

I wanted to compare with the one extracted from VAX61.bck and to my (great)
surprise the pcmsvr::pcmsvr$dkb500:[eco.cfs_125] is now empty. It was not a few
hours ago.

So who can tell me what is the patch that DID correct the problem solved in IPMT
32266 ? Where is it on PCMSVR or CSC32 ?

And, finally, Dan could tell us if the patches (I think there is now CFS_126)
which are in [butterworth.pcm] are intended to be used on OpenVMS V6.1 or V6.2 ?

Maria.

T.R	Title	User	Personal Name	Date	Lines
1157.1		29067::BUTTERWORTH	Gun Control is a steady hand.	`Fri Jan 19 1996 17:36`	8
	Maria, Those are good for either 6.1 or 6.2 on both architectures. I know that NSI fixed the problme you described. I am running the VAX kit and I just double-checked to make sure and I cannot reproduce the Monitor hang. Regards, Dan
1157.2	I don't reproduce neither but the customer does ...	48243::MENICACCI		`Mon Jan 22 1996 03:59`	18
	Hi, I installed the csc_125_vax and I can't reproduce the problem ... but I'm unfortunately running V6.1 and not V6.2. This customer reproduces the hang AT WILL I will ask to have a connection the this site, I will verify that the eco is correctly and totally installed. Have you more informations to give just to verify that this is the same problem as the one corrected by the NSI patch ? Thanks, Maria.
1157.3	I reproduce the problem too at our internal site	48243::MENICACCI		`Mon Jan 22 1996 10:50`	52
	Hi, I installed PCM V1.6 on a system running OpenVMS ALPHA V6.2. I just added a system after installing the product. console monitor this_system, previous screen, next screen, sh system and then wait 10 seconds ... console monitor hang after a few seconds ! I then, installed CSC_124_AXP.bck : still hung I then, installed CSC_126_AXP.bck : still hung between each patch, I did : console shutdown and @sys$startup:console$startup. I did nothing particular and I very simply reproduced the problem (on AXP, I haven't an available system VAX for now). After installing, the "126" I got the following error message at startup : Defining Console Manager Logical names. De-Installing Console Manager Images. Installing Console Manager Images. %INSTALL-E-FAIL, failed to CREATE entry for DISK$CLUSKI_SYS:<CONSOLE.IMAGES>CONS OLE$ENS_DAEMON.EXE -INSTALL-E-IMGTRACED, /TRACEBACK image cannot be a privileged, execute_only, or resident image Starting Console Manager Processes. Clearing out Temporary Directory Starting Console Manager Processes. POLYCENTER Console Manager startup complete. Should I IPMT again ? Maria.
1157.4	more infos about console monitor hang	48243::MENICACCI		`Wed Jan 24 1996 09:13`	32
	Hi, I installed the "new" csc_126 it's ok now as for the /traceback. Concerning, the console monitor hang, I defined console$debug to "SHM,IPC,ALL" here is the output from the decterm that executed the monitor IPCMainLoop: All Queues Empty - Going to sleep for the winter period IPCAddWorkProc: Inserting TIMER Queue entry (2291344) IPCAddWorkProc: Wake Status:: status = 1 IPCMainLoop: Awake, processing queues IPCMainLoop: Processing Timer Queue : Executing Queue Entry (2291344) RestartTimer: bintim status:: status = 1 RestartTimer: bintim status:: status = 1 IPCMainLoop: All Queues Empty - Going to sleep for the winter period IPCAddWorkProc: Inserting TIMER Queue entry (2291344) IPCAddWorkProc: Wake Status:: status = 1 IPCMainLoop: Awake, processing queues IPCMainLoop: Processing Timer Queue : Executing Queue Entry (2291344) RestartTimer: bintim status:: status = 1 RestartTimer: bintim status:: status = 1 IPCMainLoop: All Queues Empty - Going to sleep for the winter period Looping there and I can't type anything. Is this a new problem ? Time to IPMT ? Maria.