Conference pamsrc::decmessageq

2763.0. "does not detect UNAVAIL" by WING::ODAHARA (Takashi Odahara/EJ3 PSC/NSIS/DEC-Japan) Mon Feb 10 1997 10:43

  My customer has a follwing problem, bus we can not reproduce yet.
  Is it a bug, or a spec. ?

  DmQ version is V3.2 on Digital Unix V3.2D.

  (1) Process-A watches the process-B's attach/detach to DMQ using 
      AVAIL/UNAVAIL services.
  (2) Usually process-A receive UNAVAIL message for process-B when was killed 
      the process-B by shell command. ( % kill -9 process-B )
  (3) But last week(only one time), process-A cannot receive the process-B's 
      UNAVAIL message when was killed the process-B.
      Process-B does not exist on the system after killed, but written the 
      PID of process-B in queue information of dmqmonc,
      and we cannot attach the queue No. of process-B. (PAMS__DECLARED)

  Why cannot DMQ detect UNAVAIL of process-B ?

  Best regards,

Takashi Odahara/SI/NSIS/Japan

    
    don't rightly know,  but you should upgrade to V3.2A (it is a MUP
    as in MANDATORY upgrade).  all further questions regard V3.2 will
    be met with this same answer.
    
    _sjz.

  Thanks to your quick reply.

  But my customer strongly ask me the reason of topic .0.


  Detail situation of the topic .0 is as follows.

  (1) Process-A and B were running that attached to DMQ.
  (2) System manager made a wrong operation. (set forward system clock to 10 
      days future by 'date' shell command)
  (3) 3 hours later, System manager notice that his wrong operation.
  (4) return the system clock to current time by same command.
  (5) after that, kill to Process-B.

  Does DMQ cannot detect UNAVAIL when the above situation?

  Best regards,

Takashi Odahara/SI/NSIS/Japan 

    
    
    AVAIL/UNAVAIL has no notion of time.  It is event driven.
    _sjz.