[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

2813.0. "pams_set_select bad parameter with MRQ queue" by ROM01::OLD_BOCCANER () Tue Mar 18 1997 13:18

    Hi, 
    we are working on an integration project btw several software subsystem
    at TLC Italian customer.
    We have some problem with set_select function .
    
    Some customer applications  have to get message from two queue :
    . one primary MRQ queue (we are on Unix system)
    . one secondary temporary queue
    (the opposite it's true on OpenVms Platform, primary is temporary,
    secondary is MRQ queue)
    
    On each queue we have to get messages belong to a specific class of
    message, we developed a function to build a compound selection, but
    during test we observed that :
    
    . if we build a compound selection with a primary queue and secondary
    queue (both are not MRQ queue) all works fine, but if one of queue in
    selection array is of MRQ type, pams_set_select returns a bad parameter
    error code. That's true in on our OpenVms platform and Unix platform.
    Our Configuration is :
    OpenVms 6.2 DMQ 3.2
    Unix 3.2 DMQ 3.2
    
    I'm wondering if we make a mistake in configuration or it exists a
    limitation about MRQ management by pams_set_select.
    
    Any help will be very appreciated .....
    regards
    stefano
T.RTitleUserPersonal
Name
DateLines
2813.1another bit of info and ... please reply !ROM01::OLD_BOCCANERWed Mar 19 1997 07:1733
    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.2XHOST::SJZKick Butt In Your Face Messaging !Sun Mar 23 1997 20:407
    
    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.3Limited support on VMS...KLOVIA::MICHELSENBEA/DEC MessageQ EngineeringMon Mar 24 1997 10:417
  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.4It was a mistake ....ROM01::OLD_BOCCANERTue Mar 25 1997 11:1320
    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.5PAMSRC::MILLERTue Mar 25 1997 13:316
    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