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

Conference noted::pwv50ift

Title:Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server
Notice:Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server
Moderator:CPEEDY::KENNEDY
Created:Fri Dec 18 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4319
Total number of notes:18478

4131.0. "Thinks Queue Manager Not Running... Won't Start" by SLICER::ROD (Paradise Awaits!) Tue Jan 28 1997 19:04

I've just upgraded from OpenVMS V5.5-2 to V6.1.  Things seemed to be going
ok, except the Pathworks V5.0D server won't start.  I have reinstalled
V5.0D, made some suggested sysgen changes, and other things I picked up 
from this notesfile, except none have helped.  

I just discovered the Master Process doesn't think the Queue Manager is 
running.  However, it is!  I've looked in the notesfile, and no mention of
this problem.  I've included the last event from Pathworks, and
most of a SHOW SYS.

Any help would be much appreciated...

Rod Rehor 
Minneapolis Sales Support


   ================= EVENT #560 ==================

Event Time:   28-JAN-1997 17:53:09.35       Node:  SLICER
Process Id:   0000021C
Event:        LANman Controller process shutting down
Event Source: Master Process
Event Class:  Audit

      Process Id:   00000227(X)
      Status:       %JBC-E-JOBQUEDIS, system job queue manager is not running

Slicer> SHO SYS
VAX/VMS V6.1  on node SLICER  28-JAN-1997 17:55:22.44   Uptime  0 03:00:38
  Pid    Process Name    State  Pri      I/O       CPU       Page flts Ph.Mem
00000203 PWRK$KNBDAEMON  HIB     10       96   0 00:00:01.36       833   1869
00000085 IPCACP          HIB     10        7   0 00:00:00.10        99     87
00000086 ERRFMT          HIB      8      611   0 00:00:02.98       186    111
00000087 OPCOM           HIB      7       94   0 00:00:09.15       371    173
00000088 AUDIT_SERVER    HIB     10       60   0 00:00:00.77       535    655
00000089 JOB_CONTROL     HIB     10      457   0 00:00:01.42       575    257
0000008B SECURITY_SERVER HIB     10       23   0 00:00:00.94      1658    170
0000008C TP_SERVER       HIB     10      741   0 00:00:07.71       789    165
0000008D NETACP          HIB      8      227   0 00:02:03.62      7341   2163
0000008E EVL             HIB      6       95   0 00:00:00.88       464    233  N
0000008F REMACP          HIBO     8       --  swapped  out  --             56
00000210 PWRK$LICENSE_R  HIB      9       72   0 00:00:01.36       882    219
00000217 PWRK$LICENSE_S  HIB      4      100   0 00:00:01.85      1121    608
0000021C PWRK$MASTER     HIB      6      316   0 00:00:03.66      1201    775
000000A9 UCX$PWIP_ACP    HIB     10       48   0 00:00:00.44       294    272
000000AA UCX$INET_ACP    HIB     10       69   0 00:00:00.38       217    220
000000AB UCX$INET_ROUTED LEF      6     4012   0 00:00:16.98       604    183  S
0000022E PWRK$MONITOR    HIB      6       80   0 00:00:03.24      2814   1084
000000B2 LAD$KERNEL      HIBO     9       --  swapped  out  --            216
000001DE QUEUE_MANAGER   HIB      8       36   0 00:00:01.03       600    918
000001E1 NETBIOS         HIB      5       85   0 00:00:00.35       269    258
000001E4 PWRK$NBDAEMON   HIB     10       30   0 00:00:00.46       308    475
Slicer>
    
T.RTitleUserPersonal
Name
DateLines
4131.1Need VAXQMAN02_070VMSNET::P_NUNEZWed Jan 29 1997 10:0013
    
    You might try stopping and restarting the queue manager.  Also see if
    any opcom messages got logged to operator.log during startup.  
    
    But it looks like this is a VAX VMS 6.1 problem fixed by ECO
    VAXQMAN02_070 (which applies to VAX VMS 5.5-2 - 7.0)
    
      o  When $GETQUI with the DISPLAY_JOB function and the THIS_JOB
         flag  is called from a non-batch process, a JOBQUEDIS error is
         returned even when the queue manager is running.  This problem
         also occurs when a process is spawned from a batch process.
    
    Paul
4131.2VAXQMAN02_070 fixed itSLICER::RODParadise Awaits!Wed Jan 29 1997 13:5119
     	
    >>You might try stopping and restarting the queue manager.  Also see if
    >>any opcom messages got logged to operator.log during startup.
    
    Yes, I had tried that, and it didn't make a difference.  There were no
    opcom messages during startup.
    
    >>But it looks like this is a VAX VMS 6.1 problem fixed by ECO
    >>VAXQMAN02_070 (which applies to VAX VMS 5.5-2 - 7.0)
    
    I found and applied the patch.  It now works.  It also solved my
    Purveyor startup problem.  Apparently (and I'm sure we can debate on
    why) both of them check queues to see if they exist/started.
    
    Thanks for your help
    
    rod