Hello Bonnie, Friends @ 3000-l,

------------------------------------------------------------------Bonnie says--
My experience has been the opposite - I setup a job within JMS3000 to abort
sessions and stop the scheduler if sessions continue to be active. Well, every
time I get page because JMS3000 stops its a stuck nsvt session. I haven't had a
problem with TELNET. We're on MPE/iX 5.5 PP6...

my .02
Bonnie
------------------------------------------------------------------Bonnie says--

I have not seen many VTSERVER hangs since Power Patch (includes NSSFD16 patch).
Please do a ":nmmaint,6" to verify "Network Services overall subsystem version:  
B.02.06".

I might be able to get a little clue of your problem with a debug stack trace of
the HUNG VTSERVER...     

Example:

:showproc ;pin=1;system;tree
...
152  0:00.410  WAIT   S53         68   (JSMAIN.PUB.SYS)
C200  0:00.471  READY  S53           74   :SHOWPROC ;pin=1;system;tree
C152  0:00.232  WAIT   S53           51   (VTSERVER.NET.SYS)   Ÿ;
...

:debug
DEBUG/iX C.05.08  

HPDEBUG Intrinsic at: a.00a54698 hxdebug+$e4
$1 ($4a) nmdebug > pin #51
$2 ($33) nmdebug > tr,d,i  
       PC=a.0018370c enable_int+$2c
NM* 0) SP=41836f30 RP=a.0119b534 notify_dispatcher.block_current_process+$324
NM  1) SP=41836f30 RP=a.0119d9bc notify_dispatcher+$264
NM  2) SP=41836eb0 RP=a.001b3c20 wait_for_active_port+$ec
NM  3) SP=41836db0 RP=a.001b48a0 receive_from_port+$534
NM  4) SP=41836d30 RP=a.00357efc extend_receive+$494
NM  5) SP=41836b30 RP=a.01167720 nowait_io_comp.get_any_io+$84
NM  6) SP=418369b0 RP=a.011687d4 nowait_io_comp+$2dc
NM  7) SP=418367b0 RP=a.00208e80 ?nowait_io_comp+$8
         export stub: a.0026d29c IOWAIT+$bc
NM  8) SP=418363b0 RP=a.0026d1cc ?IOWAIT+$8
         export stub: 364.0002c364  
NM  9) SP=418362f0 RP=364.0002fb08  
NM  a) SP=41836230 RP=364.0002f9a4  
         export stub: 364.00014c80  
NM  b) SP=418361b0 RP=364.00000000  
     (end of NM stack)

$6 ($33) nmdebug >:copy vtserver.net.sys,x
Purge old "X.PUB.HOFMESTR"?y
$6 ($33) nmdebug > xl x 364
Preprocessing X.PUB.HOFMESTR, please wait ... #1411 symbols... Done
$7 ($33) nmdebug > tr,d, i
       PC=a.0018370c enable_int+$2c
NM* 0) SP=41836f30 RP=a.0119b534 notify_dispatcher.block_current_process+$324
NM  1) SP=41836f30 RP=a.0119d9bc notify_dispatcher+$264
NM  2) SP=41836eb0 RP=a.001b3c20 wait_for_active_port+$ec
NM  3) SP=41836db0 RP=a.001b48a0 receive_from_port+$534
NM  4) SP=41836d30 RP=a.00357efc extend_receive+$494
NM  5) SP=41836b30 RP=a.01167720 nowait_io_comp.get_any_io+$84
NM  6) SP=418369b0 RP=a.011687d4 nowait_io_comp+$2dc
NM  7) SP=418367b0 RP=a.00208e80 ?nowait_io_comp+$8
         export stub: a.0026d29c IOWAIT+$bc
NM  8) SP=418363b0 RP=a.0026d1cc ?IOWAIT+$8
         export stub: 364.0002c364 wait_for_completion+$98
NM  9) SP=418362f0 RP=364.0002fb08 main+$90
NM  a) SP=41836230 RP=364.0002f9a4 ?main+$8
         export stub: 364.00014c80 _start+$138
NM  b) SP=418361b0 RP=364.00000000  
     (end of NM stack)

$8 ($33) nmdebug > exit

In this case the VTSERVER is not hung, but I am sure yours will be a little
bit more interesting...  It may also be useful to get a stack trace of the
above CI pin #74 & JSMAIN pin #68.

In the end, if we have a new problem it typically requires a memory dump to
figure all the ins/outs of VTSERVER interaction with CI & JSMAIN and DSDAD.

I hope this helps.


Regards,

James Hofmeister
Hewlett Packard
Worldwide Technology Network Expert Center
P.S. My Ideals are my own, not necessarily my employers.