[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

2745.0. "Problem with pams_put_msg" by NETRIX::"peterg@zuo.dec.com" (Peter Goedtler) Fri Jan 24 1997 08:09

Hello,
I'm using DMQ 3.2A on Unix 3.2g.
Somtimes the call of pams_put_msg with delivery-mode PDEL_MODE_WF_SAF and
uma PDEL_UMA_DISCL returns  pams_status: -230 (PAMS__NO_SAF?) 
delivery satus: -230 and uma status: 25. (I send always the same message)
I found nothing about PAMS__NO_SAF in the documentation. 
What can i do?

Thank you
Peter
[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name
DateLines
2745.1PAMS_NO_SAF undocumentedGVA05::GUYMon Feb 03 1997 11:4615
A customer has the following problem :

The program send messages with delivery mode PDEL_MODE_WF_SAF and PDEL_UMA_DISCL
They experience intermittently error PAMS_NO_SAF after the PAMS_PUT_MSG.

If they restart the program 2 or 3 times, sometime it works again.

It turns out that PAMS_NOSAF error doesn't seem to be documented, so could you
please tell us under which conditions this error can occur.


Thanks

Jean-Paul.

2745.2PAMSIC::POPPDeep in the Heart...Mon Feb 03 1997 14:539

   What version of DMQ are you running?

   In DMQ V3.2 for VMS, PAMS__NO_SAF is returned when journaling has
 been disabled.  The user controls the availablity of the SAF.  What
 exactly is the customers configuration?  What are they trying to do?

  -Lisa
2745.3XHOST::SJZRocking the Messaging Desktop !Mon Feb 03 1997 16:3211
    
    I moved the last two notes from 2756.*.   This is the same
    problem.   PAMS__NO_SAF is the correct error code for  the
    problem that these people are running into in that the SAF
    to which they are enqueuing is disabled because of  a  bug
    in the UNIX V3.2A release.
    
    We already have a fix for this which we hope to be  releas-
    ing later this week.
    
    _sjz.