[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxaxp::vmsnotes

Title:VAX and Alpha VMS
Notice:This is a new VMSnotes, please read note 2.1
Moderator:VAXAXP::BERNARDO
Created:Wed Jan 22 1997
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:703
Total number of notes:3722

600.0. "Queue Mgr and Lat queues problem" by TAINO::RFONSECA () Thu May 15 1997 09:27

     Customer is running OpenVMS 5.5-2 (I know is old but they are working
     on the Alpha version in order to migrate) and lately the queue manager
     is behaving strangely.  Several of their Lat queues start aborting and
     them all of them start having problems.  Around 30 of these Lat queues
     are assigned to the 1st symbiont and the remaining to the 2nd.  All
     queues having problems are in the 1st symbiont.  Below are some of the
     error messages displayed at the console terminal.

     %%%%%%%%%%%  OPCOM   6-MAY-1997 09:16:30.48  %%%%%%%%%%%
     Message from user QUEUE_MANAGE on RRPAD
     %QMAN-E-SYMDEL, unexpected symbiont process termination

     %%%%%%%%%%%  OPCOM   6-MAY-1997 09:16:30.48  %%%%%%%%%%%
     Message from user QUEUE_MANAGE on RRPAD
     -SYSTEM-F-RADRMOD, reserved addressing fault at PC=00000000, PSL=00000000

     %%%%%%%%%%%  OPCOM   6-MAY-1997 16:05:49.35  %%%%%%%%%%%
     Message from user QUEUE_MANAGE on RRPAD
     %QMAN-E-SYMDEL, unexpected symbiont process termination

     %%%%%%%%%%%  OPCOM   6-MAY-1997 16:05:49.35  %%%%%%%%%%%
     Message from user QUEUE_MANAGE on RRPAD
     -SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual 
     	address=00000000, PC=0001A540, PSL=03C00000

     %%%%%%%%%%%  OPCOM   7-MAY-1997 14:09:45.06  %%%%%%%%%%%
     Message from user QUEUE_MANAGE on RRPAD
     %QMAN-E-SYMDEL, unexpected symbiont process termination

     %%%%%%%%%%%  OPCOM   7-MAY-1997 14:09:45.06  %%%%%%%%%%%
     Message from user QUEUE_MANAGE on RRPAD
     -PSM-F-BADLOGIC, internal logic error detected at PC 00000000

     I don't think that this might be the cause but this problem started
     soon after the installation of the VAXLIBR06_070 patch (Delta patch).
     Also, the follwing two patches were installed at their system:

     	o VAXLAT03_U2055

     	o VAXPRTS02_070

     Any assistance would be greatly appreciated.

% ====== Internet headers and postmarks ======
% Received: from mail13.digital.com by us7rmc.bb.dec.com (5.65/rmc-17Jan97) id AA22205; Wed, 14 May 97 15:16:00 -0400
% From: [email protected]
% Received: from UPR1.UPR.CLU.EDU by mail13.digital.com (8.7.5/UNX 1.5/1.0/WV) id PAA09553; Wed, 14 May 1997 15:03:42 -0400 (EDT)
% Received: from UPR1.UPR.CLU.EDU by UPR1.UPR.CLU.EDU (PMDF V5.0-6 #22317) id <[email protected]> for [email protected]; Wed, 14 May 1997 15:09:52 -0400 (AST)
% Date: Wed, 14 May 1997 15:09:52 -0400 (AST)
% Subject: LAT queue problem at RRPAD
% To: bohio::rfonseca
% Message-Id: <[email protected]>
% X-Vms-To: IN%"[email protected]"
% X-Vms-Cc: R_FONSECA
% Mime-Version: 1.0
% Content-Transfer-Encoding: 7BIT
T.RTitleUserPersonal
Name
DateLines
600.1Acquire Some Information, Then Start IPMT...XDELTA::HOFFMANSteve, OpenVMS EngineeringThu May 15 1997 10:3217
   See note 125.* in CSC32::BATCH_PRINT_SERVICES, as well as various
   other notes in that particular notes conference.

   Make sure you are running LATSYM on the LAT queues.

   Is the system running WordPerfect?  (If so, check the version of
   the software.  Also consider turning WordPerfect off and deleting
   the SMBSRVSHR logical name(s) WordPerfect creates, and see if the
   symbiont failure(s) stop.)

   Apply the VAXQMAN03_070 ECO -- the VAXLIBR06_070 ECO calls this out
   for early OpenVMS releases.

   Check for any recent dump files: DIRECTORY SYS$SYSTEM:*.DMP/DATE

   Start an IPMT.
600.2please use PDA tool ...HAN::HALLEVolker Halle MCS @HAO DTN 863-5216Fri May 16 1997 02:486
    
    Whenever you run into LATSYM or PRTSMB dumps, please use the PDA tool
    (Printsymbiont Dump Analysis, see note HAN::LOOPING_LATSYM 96) as a
    first step during troubleshooting.
    
    Volker.