[Info-vax] TCPIP tying up system

[John Wallace]

On Nov 29, 7:54 pm, Ken Fairfield <ken.fairfi... at gmail.com> wrote:
> On Nov 28, 3:40 am, John Wallace <johnwalla... at yahoo.co.uk> wrote:
>
> > On Nov 28, 11:09 am, "R.A.Omond" <Roy.Om... at BlueBubble.UK.Com> wrote:
>
> > > On 28/11/2010 10:57, Phillip Helbig---undress to reply wrote:
>
> > > >[...snip...]
>
> > > Never mind all of that - did you get a crash dump ?
>
> > While we await the crash dump info, would it be appropriate, for the
> > benefit of other readers who may one day find themselves in a similar
> > situation where a crash dump provides answers rather than the present
> > guesswork and speculation, to briefly remind folk of how it's done
> > (and where to find the full details documented)?
>
> While I expect you know, to answer your question, the
> simple way to crash a system and get a dump is to:
>
>    $ run sys$system:opccrash
>
> from a suitably prvileged account.  And Philip would
> have wanted to have set his priority high before hand,
> or have been happy to wait a (little?) while.
>
> In fact, SHUTDOWN.COM runs OPCCRASH as the
> last thing it does on the way down.  My recollection
> is that SHUWDOWN.COM defines a logical name
> that causes OPCCRASH to skip the dump step.
>
> As to where this is documented, I'd expect it's in
> the System Manager's Manual (or Guide to System
> Management, whatever it's called these days),
> although I admit I haven't gone an checked.
> gone an checked
>
>     -Ken

Thank you for that, Ken.

And for those cases where terminals are unresponsive but console
access is available?

I can't remember if there's an official procedure, but getting to
console mode (>>> on Alpha) and depositing rubbish (eg a 1) in the PC
springs to mind. It worked on my PWS when I tried it not long ago, but
that's not a very extensive sample. Also, different consoles have
different syntax, iirc some have a "crash" command, etc.

To fail to plan is to plan to fail, etc.

regards
john