🚀 go-pugleaf

So far I have tried:
     "logon xxx here" with the response 'logoff/force pending'
    "msg xxx junk" with the response 'xxx not logged on'
    I have waited now for about 18 hours (since yesterday afternoon when
the controller crashed)
    "force xxx disc" with the response 'xxx already disconnected'

I am open to any other suggestions.

BTW: UNHANG is the exec I was looking for. Does anybody have a copy
available?





GEORGEH@msu.edu on 08-07-97 01:56:00 PM

To:   George Shedlock/Corp/Chep USA
cc:
Subject:  Re: Logoff/Force pending




I don't know of an ESA version of that old EXEC (UNHANG?). At our site, we
haven't had a hung ID since ESA 1.1.1. When they *do* get hung,
we've freed them by either using LOGON userid HERE or
FORCE userid DISC to get them unstuck. Sounds like you're past that
point, though. The 1 or 2 times I've seen a LOGOFF PENDING for an
ESA id, CP has mangaed to untangle itself withing about 10 mins.
Of course your mileage may vary.

> A long, long time ago, there once was an exec that would twiddle some
bits > in the appropriate control blocks to allow a userid in this state to
then
> be forced off. This problem occurred when the local non-sna controller
> (3174) it was attached to died (microcode 381 failure). Does this exec
> still exist in a form that can be used in a VM 1.2.2 environment? Do I
have > to IPL to get this userid back?
>
> Note: this is a critical userid (what else?) that I need to get back
> on-line soon.