Re: forcing session from limbo to disconnected
From: Larry Kilgallen (Kilgallen_at_SpamCop.net)
Date: 10/29/04
- Next message: Ken Randell: "Undocumented (?) PCSI error messages"
- Previous message: Sue Skonetski: "HEADS UP Date Change for the OpenVMS Advanced Technical Boot Camp 2005"
- In reply to: Bob Kaplow: "forcing session from limbo to disconnected"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 29 Oct 2004 14:41:44 -0500
In article <EDvctgPEEwT8@eisner.encompasserve.org>, kaplow_r@encompasserve.org.TRABoD (Bob Kaplow) writes:
> 2) Is there some way to force the process into a DISCONNECTED state
> immediately so the user can reconnect to it?
>
> What I would like to see eventually is something like
>
> $ DISCONNECT /TERM=VTA73
>
> or perhaps
>
> $ DISCONNECT /ID=000015B1
>From within a process, DCL handles the DISCONNECT command by
1. Checking to ensure TT2$V_DISCONNECT is set
2. Issuing an IO$_SETMODE $QIO with IO$M_TT_DISCON
Perhaps that would work on the terminal of some other process with
the SHARE privilege.
- Next message: Ken Randell: "Undocumented (?) PCSI error messages"
- Previous message: Sue Skonetski: "HEADS UP Date Change for the OpenVMS Advanced Technical Boot Camp 2005"
- In reply to: Bob Kaplow: "forcing session from limbo to disconnected"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]