[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

3861.0. "Notification Services fail to start automatically...." by KERNEL::DAVIES () Mon Oct 05 1992 16:51


	Hi all,

	I have a customer who is using MCC V1.2 and VMS V5.5.

	The DECmcc Notification services windows fail to appear automatically 
	when MCC is fired up.  He is starting it up from the SYSTEM account.
	
	Notification is working fine but the problem starts when he tries
	to customise it to start up automatically.

	He has saved the notify request to a file using the "Save as..." 
	option and this created the file in his default directory.  He then
	uses the "Customise" and "General Notification..." options from the 
	DECmcc Notification window and selects "Open Notification Window on
	Startup" and enters the "Notify Requests Startup File" (Same file as 
	above).  This is saved using the "Customise" "Save Current Settings" 
	option which creates the MCC_NOTIFICATION_RESOURCE.DAT file in his 
	default directory.
	
	I am unable to reproduce the problem myself.

	Has anyone any ideas/pointers as to where the problem might be...??

	
	Thanks in advance.....

	Phil Davies.  UK Comms TSC.
T.RTitleUserPersonal
Name
DateLines
3861.1similar problemBEANO::MISTRYWed Oct 07 1992 04:1320
Hi,


I've been having a similar problem with automatically enabling notification
services.
Having saved the customized settings into a file called 
MCC_NOTIFICATION_RESOURCE.DAT which it saves into my default area. If I then 
shut down MCC and fire it up again it should bring up the notification window
but it doesn't. If you type out the file you can see that the variable

mcc_ns.Wopen:   1

is set to 1. Having looked around various directories I found that the default
settings are kept in the directory DECW$SYSTEM_DEFAULTS:MCC_NOTIFICATION_RESOURCE.DAT
Unfortunately renaming this file and copying my saved file into this area still
had the same effect. So, it is picking up the default settings from another
area. However, I cannot find the file that MCC is reading. Can someone please
give a pointer to which file it is reading or what I'm doing wrong.

Bipin.
3861.2a work-around, please provide more informationMCC1::DITMARSPeteWed Oct 07 1992 11:3012
Hi,

What versions of VMS and DECwindows are you running?

The following work-around (from note 3607.3) helps
in some cases.

$ define DECW$SYSTEM_DEFAULTS -
		SYS$LOGIN:, -
		SYS$SYSROOT:[DECW$DEFAULTS.USER], -
		SYS$SYSROOT:[DECW$DEFAULTS.SYSTEM], -
		SYS$LIBRARY:
3861.3thanksBEANO::MISTRYWed Oct 07 1992 12:303
Thanks very much, it seemed to have solved the problem

Bipin.
3861.4more informationBEANO::MISTRYThu Oct 08 1992 11:3413
Hi,

More information about this. Even with the new logicals defined it only seems
to work if the MCC_NOTIFICATION_RESOURCE.DAT is in the directory 

SYS$COMMON:[DECW$DEFAULTS.USER] area. If not then the notification window 
doesn't fire up.

Does anyone have any ideas.

Bipin.

ps version of vms 5.4-2 and same version of decwindows.
3861.5Motif 1.0 --> Motif 1.1 gotchaCSOADM::ROTHYou like it, it likes you!Tue Dec 29 1992 16:243
Bit by upgrade of Motif... see note 3607.5.

Lee
3861.6Sorry, It doesn't workZUR01::SCHNEIDERRThu Feb 25 1993 10:1316
Hello,

I read the notes 3861.* and 3607.* but in our case it doesn't work.
We defined the DECW$SYSTEM_DEFAULTS as it is recomended and we copied the 
MCC_NOTIFICATION_RECSOURCE.DAT to the SYS$COMMON:[DECW4DEFAULTS.USR] as it is
written in 3861.4 but it doesn't work.

I had a look to the file acceses with "set watch/class=major file" and I saw on
the failing system more or less the same as in my system, where the window starts.

Is this Problem QARed or is there a real solution arround. I thing it depends the
inviroment how the failure is seen. My customer told me, that he had no problems
with the window one week ago. and now he sees the failure and all looks well
on the system.

Roland
3861.7See note 7 for QAR infoTOOK::MINTZErik MintzThu Feb 25 1993 12:215
I don't know the status of this question, but you can check for
QARs using the direcitons in note 7.

-- Erik