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

Conference pamsrc::decmessageq

Title:	NAS Message Queuing Bus
Notice:	KITS/DOC, see 4.*; Entering QARs, see 9.1; Register in 10
Moderator:	PAMSRC::MARCUSEN

Created:	Wed Feb 27 1991
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2898
Total number of notes:	12363

2886.0. "ENABLE_MRS = No and ENABLE_SBS = No is not working ?" by BACHUS::SABLON (Mich�le Sablon, TP/IM Support Belgium 856-7238) Thu May 22 1997 10:39

DMQ 3.2B
VMS 6.2

A customer just upgraded to 3.2b, including the DMQ-V32B-AXP-3250 eco kit but
now complains that the SBS and MRS processes are started, what he doesn't want
as it is just overhead to him.

He says that the startup procedure has changed, comparing to his old version
(2.0). Previously He found these parameters in DMQ$INIT.TXT and set them to No
but the related processes are started. As he has several groups, that makes some
2 times the amount of group of unnecessary processes.

The question is about disabling them ? Any ideas ?

Mich�le.

T.R	Title	User	Personal Name	Date	Lines
2886.1		PAMSIC::STEPHENS		`Thu May 22 1997 11:59`	19
	Hi Mich�le. The overhead for DmQ V3, as compared with V2 and on back to PAMS V2.x, is just greater. The customer can configure the product down to a minimum of two process (COM and EVL) per group by setting all the "ENABLE_xxx" to "NO" in the profile section of the DMQ$INIT.TXT file. >He says that the startup procedure has changed, comparing to his old version Yes, it has changed. We do have a convert utility which will aid the transition between V2->V3. Did the customer use this conversion? >but the related processes are started. As he has several groups, that The customer may be having some problem sorting out the logical name tables and directory trees between V2 and V3, if the processes are still being started, and they have set the ENABLE_xxx NO. Bruce
2886.2		BACHUS::SABLON	Mich�le Sablon, TP/IM Support Belgium 856-7238	`Thu May 22 1997 13:35`	10
	Everything seems ok but we're already one step further. Per group, customer has a DMQ_C_xxxxxx process (COM server), a DMQ_L_xxxxxx (EVL server) and a DMQ_D_xxxxxx process (Decnet Link driver). From .1, (thanks Bruce !), it appears that the two first are mandatory. What about the third one ? Does it make sense not to remove it ? And if so how ? Best, Mich�le.
2886.3		PAMSIC::STEPHENS		`Thu May 22 1997 19:16`	11
	Hi Mich�le. The DECnet link driver can be eliminated if the customer is not communicating with UNIX/NT. To force connectivity via the COM server alone, in the transport field of the XGROUP section of the DMQ$INIT.TXT file, change DECNET to DECNETV2 for all of the group entries. Hope this helps, Bruce