Conference pamsrc::decmessageq

2762.0. "UNIX with DECnet/OSI and DMQ3.2A - dmqld loop !" by PRIVAT::ANCA () Fri Feb 07 1997 07:58

	Hi everybody,

        If somebody heard me ,please ,I really need an urgent
        help/idea before I open an IPMT.

        One of my customers has following production enviroment:

        DigitalUnix V3.2a and DECnet/OSI V3.2 (321).
        On this system he has had an DECmessageQueue V3.2
        and has had problems with "dmqld - loader - looping".

        He updated to DECmessageQueue V3.2A.
        He use an communication via DECnet to another VMS system.

        When they start DMQ all the proccess are started o.k.,
                        B U T
        if you take a look on the system the :

        1. topcpu indicate an usage from 65%,
	2. vmstat indicate 100% busy,
        3. ps -e -o pid,pcpu,ucomm
           indicate for dmqld 9% usage and for dnqnsd 55%
                        A N D
	none links can be created no connection established.

        The GroupInit file looks like :

%PROFILE

ACCEPT_KILL_COMMAND     YES     ! accept kill commands from DMQ Monitor
ENABLE_XGROUP           YES      ! allow cross-group communications
XGROUP_VERIFY           NO      ! do not verify cross group links
NAME_TABLE_SIZE         100     ! number of names
FIRST_TEMP_QUEUE        200     ! minimum is 101,  maximum is 850
!MAX_USER_QUEUE          150     ! ......neu....
GROUP_MAX_LINKS         20      ! size of the group link table
GROUP_MIN_GROUP_NUMBER  008     ! 1 is the minimum
GROUP_MAX_GROUP_NUMBER  017     ! 32000 is the maximum
GROUP_MAX_USER_QUEUE    300     ! 999 is the maximum
GROUP_MAX_MESSAGE_SIZE  8192    ! largest message size permitted in this group

ENABLE_MRS              YES       ! Start Recoverable Messaging Servers
  
 %MRS
MRS_JOURNAL_PATH           /witron/dmq/mrs/jou  ! recovery journal path
MRS_POST_CONFIRMATION_PATH /witron/dmq/mrs/pcj  ! post confirmation journal path
MRS_DEAD_LETTER_PATH       /witron/dmq/mrs/dlj  ! dead-letter journal path
%EOS


        Did we have an memory problem ?

        Has somebody an Idea what can be wrong here ?

        Why is DECMESSAGE QUEUE V3.2 put it on Eng. HOLD  ?


        Regards,
        Anca Radulescu
        (Netw. & IBM Comms. CsSC Munich)                                       

    
    V3.2A is on engineering hold pending some fixes to
    recently discovered problems.  It should be coming
    off any day now at which point a fix for the  prob-
    lem mentioned above will become available.
    
    _sjz.

Hi again,

thanks for the quickly answer.
I informed my customer BUT I have a problem with the production till 
the new patches are comming.
Aprox. on how many days do you think if you say the patches are comming 
"off any day now" ?	
 
I have time,to fix the problem till Feb.12-13  after this time DEC has to 
go back /to reinstall  DMQ 3.2.

Thanks and Regards,
 Anca .
  

    
    The kit has been ready since last Wednesday. We are curently
    waiting on documentation and a blessing from our  test  team.
    Once that is out of the way we should be all set.
    
    If you NEED (not want) a kit before then,  then  you  should
    contact Peter (PAMSRC::) Marcus with the understanding  that
    what you receive is not the final product.
    
    _sjz.

	aha,but I have to wait for the "final product" because is an 
	production env.
		
	I'll look every day on PAMSRC::dmq$kits:

	Thanks,
	 Anca.

re: .5

>	I'll look every day on PAMSRC::dmq$kits:

  ...to do that, the ECO kit will be announced in this notes file when it is
ready.


Marty

    
    and odds are it won't show up in dmq$kits,  we are moving to
    web oriented downloads and ftp.
    
    _sjz.