Conference pamsrc::decmessageq

2752.0. "Assistance with configuring SBS on v4 ft2" by OZROCK::PERKINS (Some contractors, their sex-life destroyed and overwhelmed by project pressures, turn to snorting quack.) Fri Jan 31 1997 03:10

Thanks in advance for any assistance/examples you can give me

Cheers Kevin


The installation and configuration guide (from ft1 i can't find
an updated version) provides little assistance (i.e example) for
setting up SBS other than ENABLE_SBS = YES.

I therefore have used the VMS as a model when trying to 
define a MOT.

e.g.

MOT_UNIV1       5101     0   0 . . .  . .  .      L     N

in the QCT section with nothing in the SBS section but get

************ dmqloader (4527) 31-JAN-1997 10:58:38 
************
ldr, DECmessageQ System Loader starting

ldr, Parsing PROFILE Section
ldr, Parsing GROUP Section
ldr, Parsing ROUTE Section
ldr, Parsing QCT Section
ldr, Invalid queue number 5101 on line 123 - ignored
ldr, Parsing GNT Section
ldr, Parsing SBS Section
ldr, Parsing NAM Section
ldr, Parsing MRS Section
ldr, Loader exiting normally
************ dmqld (4529.0) 31-JAN-1997 10:58:39 
************

out of curiousity when running a program that tries to
register the sbs log seems to imply i am sending a bad formatted
message (or this may just a consequence of the above with
poor status reporting????)

program trace with a dump of the registration request
immediately prior to sending...

REGISTRATION_EZ REQUEST
Enter Mot_Q (4800->5200)[4800] 5101
Enter group # of distribution_q: [2808]
Enter Q number of distribution_q (PAMS Process Q) [My 
PAMS id '219']
Mot_Q -> 5101
         28
         0
         13ed
         af800db
         1
         0
         0
         0
SBS_EXAMPLE STATUS -- PAMS__SUCCESS, Successful 
completion, SEVERITY -- 0
Wait for an ACK
SBS_EXAMPLE STATUS -- PAMS__SUCCESS, Successful 
completion, SEVERITY -- 0
Registration_EZ failed '20'

causes the following message to appear in the log file

************ dmqsbs (4528) 31-JAN-1997 17:42:01 
************
sbs, Invalid MOT Address = '1' from '2808.219'

Hi Kevin,

On UNIX/NT DmQ SBS, the only configuration issue is the 
ENABLE_SBS = YES/NO, except when using the GNT section and
you wish to name a MOT.   Remember that MOT is for multiple
*outbound* targets, and does not require an entry in the QCT.
The same on VMS, placing the MOT in the QCT is a naming issue,
not that a queue is created.   This inconsistency between DmQ 
loader implementations should be QARed.

Concerning your registration request, it is not easy to see from
your trace in .0 what's going on.   First, the recommended way 
to register for a broadcast MOT is to use the SBS_REGISTER_REQ 
message.    If you are using an older, obsolete SBS_REG_EZ message
it will work, but the message format must be 20 not 40.

Look at the structure in the programmer's guide and the typedef 
in p_msg.h which is included with the kit.

Hope this helps,
Bruce.

re: .1


>The same on VMS, placing the MOT in the QCT is a naming issue,
>not that a queue is created.   This inconsistency between DmQ 
>loader implementations should be QARed.

	  DmQ V4.0 will use the same loader on all server platforms.  As a
	result some consistency items are being cleaned up.  For V4.0, 
	only real queues, not MOTs or aliases, will be allowed in the QCT.
	The MOTs, aliases and the bindable queue names need to be in the
	GNT section.  On VMS, that will be taken care of by the init file
	conversion utility.


	Marty

    re.0 I've moved some SBS example programs to pamsic::dmq$public:[sbs]

Hi Bruce & Marty,

Thanks guys that helped alot.  the examples work (of course :-)
now i just have to workout why my poor program doesn't.

cheers Kevin