Greg,
Here are some more situations which can reproduce the message.
I can generate this NetIPC message when I connect with a terminal emulator,
but before logging on, close the window. I also can open my terminal
emulator and click the "disconnect" button and I receive the same message on
the console. With the former method, the NetIPC message shows up instantly
on the console, but the latter takes a moment for the timers to kick and the
HP3000 to notice. At that point, there is no job number assigned to the
VTSERVER process, thus "Job: 0".

The NetIPC error 42 will occur when an "unexpected disconnect" happens. At
my previous MPE/iX shop, the HP3000 was on battery backup but none of the
PC's. The power would go out a few times in the summer and we would get
about 70-80 NetIPC 42's because the HP3000 never received a graceful :bye
from any of those sessions. Similar results can be seen from a network
interruption of sufficient time so the various 'retry' counters are
exceeded. Of course in these cases and the two that Mr. Hofmeister suggested
you will see the session number.

For Test Case number 3, I connected a terminal emulator and waited for the
logon prompt timeout. In this case, I don't see the console message which
adds weight to the fact that when the HP3000 knows what happened (it
generated the disconnect because it had been too long since attempting to
logon), it wasn't "unexpected".

Unless you receive many of these simultaneously, they can be ignored as
"informational" for the most part. Witnessing an unusual amount could mean
some sort of outage (power, LAN/WAN) often times accompanied by the phone
ringing or darkness. ;)

HTH

Greg Skvorak
Beechglen Development, Inc.
Cincinnati, Ohio
----- Original Message -----
From: "Greg Stigers" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Thursday, January 20, 2005 7:32 PM
Subject: Re: NS/3000 NetIPC ERROR IN VT; Job: 0; PIN: 437; Info: 1


> When user "x out", isn't the job normally the session number of the user?
> I'm used to seeing
> NS/3000 NetIPC ERROR IN VT; Job: #S4226; PIN: 710; Info: 1
> (although users insist that they are not xing out). It's the Job: 0 that
> has
> me a bit puzzled, and unsure how to chase down. If we have shared IP
> addresses, that's a bit scary. But I would expect resulting disconnects to
> also result in a call to our help desk.
>
> Greg Stigers
>
> James Hofmeister wrote:
>> Hello  Greg,
>>> ** NS/3000 NetIPC ERROR IN VT; Job: 0; PIN: 199; Info: 1
>>> - Error: 42;
>>> in all three cases that I see today.
>>
>> VTERROR 42 is REMOTE NOT RESPONDING, CONNECTION CLOSED.
>>
>> This is a common error message can be easily duplicated by selecting
>> [x] on your terminal emulator window rather than ":bye".  This error
>> message is also seen when 2 PC share an IP address (duplicate IP
>> address).. as one starts a network connection, the other will
>> generate a VTERR 42 to the console and disconnect.
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *