[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

336.0. "PAMS_GET_MSGA in un*x" by TAV02::WINDER (Aharon Winder) Mon Jan 20 1992 07:31

T.RTitleUserPersonal
Name
DateLines
336.1See note 280.* for a detailed discussion of GET_MSGA on UnixIGNATZ::JUDDEvery platform in the Known UniverseMon Jan 20 1992 08:250
336.2Any workaround for Digital UNIX v4GUIDUK::WU_CHFri Mar 28 1997 17:0220
    Hello,
    
    After reading 280.* which does not apply to my case at all... Thus I
    post this message.
    
    Is there any workaround for asyn. call in Digital UNIX...
    PAMS_GET_MSGA <--- only reside on VMS
    
    according 280.*, GET_MSGA was supposed to be implemented by DMQ v2.
    Yet, as of today DMQ v4.0 field test is already out... and I still see
    no sign of PAMS_GET_MSGA...
    
    Any help will be appreciated...
    
    
    Alex Wu
    [email protected]
    Digital NSIS
    (206) 8416046
    
336.3XHOST::SJZKick Butt In Your Face Messaging !Fri Mar 28 1997 18:5813
    
    there is not get_msga under UNIX.   it is still on the table for
    a future release.  i personally am dead set against  ever  imple-
    menting it.   users, imo,  are better served by our  making  the
    code thread safe which allows them to make blocking  calls  with-
    out the need for polls or asynchronous triggers.  but the  issue
    is still under debate.
    
    also,  despite what  is  in  note  280,  any  implementation  of
    pams_get_msga on the non-VMS platforms will semantically be very
    different from the exiting VMS behavior.
    
    _sjz.