T.R | Title | User | Personal Name | Date | Lines |
---|
2813.1 | another bit of info and ... please reply ! | ROM01::OLD_BOCCANER | | Wed Mar 19 1997 04:17 | 33 |
| Another bit of information
We tested our interface using several combinations of
queues. Here is what observed :
OpenVms :
MRQ queue isn't never addressable with Class or Type compound selection
filter. We got always an unsupported features error message
(enabling PAMS_TRACE) so I suppose that MRQ compound filter is not
available at this time.
Unix :
After I read some notes, I thought MRQ compound selection was available
on Unix platform, but we have a funnny problem :
1) if I attach to MRQ queue as my primary queue, and then build the
compound select filter passing the address (group Number) into the
queue field of array_component I get this error :
PAMS - xxxxxx - queue provided isn't a valid queue (queue address)
2) if I attach MRQ queue as above, but passing 0 value into queue field
of array_component, pams_set_select works fine (no error)
3) If I attach another primary queue then MRQ is attached as MRQ type,
I get the same error as at point 1)
I'd like to know, in deepth, what's the problem about MRQ and
pams_set_select that i'm experiencing, if I made a mistake in group
init file ( all looks fine, but I have an OpenVms know-how ....)
Please help me on this problem ....
regards
stefano
|
2813.2 | | XHOST::SJZ | Kick Butt In Your Face Messaging ! | Sun Mar 23 1997 17:40 | 7 |
|
as far as unix is concerned, what you describe in .0 is a bug.
it has been in the product since its inception. specifically you
cannot select from an MRQ. this is fixed in DECmessageQ for UNIX
V4.0 (NT and OS/2). i cannot speak for vms.
_sjz.
|
2813.3 | Limited support on VMS... | KLOVIA::MICHELSEN | BEA/DEC MessageQ Engineering | Mon Mar 24 1997 07:41 | 7 |
| On VMS, pams_set_select limits selection on MRQs to FIFO on one or both
priorities. In other words, no style of selection is allowed that could result in
the reordering of messages within an internal queue (each priority is a separate
queue).
Marty
|
2813.4 | It was a mistake .... | ROM01::OLD_BOCCANER | | Tue Mar 25 1997 08:13 | 20 |
| sorry there is not a bug but it was an our mistake, we passed a
group+queue address when only a queue address was required.
On unix all works fine now.
On vms platform, I read several times notes and I think that is a
restriction on the platform, due to Operating System constraint.
Thank yoou for reply.
N.B.
Our customer has systems with Unix 4.0a what's the right DMQ version to
be used ?
There is some www pointer to conference or tech info ? (we have
internet access at customer site, but no digital net access from the
same site ...)
stefano
|
2813.5 | | PAMSRC::MILLER | | Tue Mar 25 1997 10:31 | 6 |
| The URL for the internal site is: http://www.dmq.rch.dec.com/dmqeng/home.html
we have V4.0 field test (soon to be released) documentation out there. From
there you can go to the external site (InfoCenter).
tm
|