| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 495.1 | When is a CTRL/P not a CTRL/P ?! | SUPER7::HUGHESA | Swimming against the tide @#%* | Wed Nov 30 1994 15:02 | 60 |
| Max,
If you re-read your own base note carefully you have answered
your own question.
In Console Manager you have the CTRL/P key sequence defined as
Break. Thus when you enter CTRL/P you are infact transmitting the
ASCII code for break and not CTRL/P. Thus unless you have changed
your console setup on the 6610 to halt upon break then this
means nothing.
This is further detailed below....
PCM - How to HALT systems and differences with VCS
There are two separate methods of halting VAX systems which differ
based upon there type. The larger systems (namely the 6000, 7000
and 8000 series) expect the CTRL/P key sequence to halt the system.
The smaller VAX systems (namely the 3000 and 4000 series) expect
the BREAK key as the halt sequence.
The way Polycenter Console Manager and VCS handle the break key
is different. The table below details the correct method for
halting systems using the two tools;
1/ VAX 6000, 7000 and 8000 series systems
Polycenter Console Manager VaxCluster Console System
-----------------------------------------------------------------
CONSOLE CONNECT/BREAK=CTRL_K {system} VCS CONNECT {system}
CTRL/P CTRL/P
or
CONSOLE CONNECT {system}
CTRL/G
SET BREAK_KEY CTRL_K
CONNECT {system}
2/ VAX 3000 and 4000 series systems
Polycenter Console Manager VaxCluster Console System
-----------------------------------------------------------------
CONSOLE CONNECT {system} VCS CONNE/BREAK=CTRL_K {system}
CTRL/P CTRL/P
It should be remembered that if you set the BREAK key (from CTRL/P)
that you will have to enter the new BREAK sequence to halt the
small VAX systems.
I have also added this information to IS_SUPPORT database in STARS for
future reference.
If anybody has any queries please come back to me.
Andy.
|
| 495.2 | Put it another way... | ELGIN::RASOOLM | The computer in front is an ALPHA | Thu Dec 01 1994 11:07 | 19 |
|
Andy,
So if I read that right, I can achieve what I want by;
Defining a break key in sys$login:console$monitor_init.dat to, say
CTRL/K (I always go in via monitor).
Merrily CTRL/P to halt my 6610's and CTRL/K to halt my 3000 and 4000's.
Regards,
Max.
|
| 495.3 | You got it. | SUPER7::HUGHESA | Swimming against the tide @#%* | Thu Dec 01 1994 16:48 | 18 |
|
Max,
You have got it.
This area has caused alot of confusion and will be changed in
the next release to a halt key sequence.
Except .....
Redefining the keys via the initialisation file did not
work in PCM v1.5 or ECO1 as there is a bug. This is fixed
in the latest CONSOLE$CONMOM image in OPG::CM$KITS.
Also the initialisation file is called when you enter
EITHER the monitor or connect interface.
Andy.
|
| 495.4 | Get this man on the team!! | OPG::SIMON | | Thu Dec 01 1994 17:24 | 7 |
| Andy,
you keep answering questions like this and we will get you
writing the code for the next version :-))
Thanks for helping out.
Cheers Simon...
|
| 495.5 | !! | SUPER7::HUGHESA | Swimming against the tide @#%* | Thu Dec 01 1994 22:29 | 6 |
|
Simon,
Only if you pay me more money and sack the project leader !!
Andy.
|
| 495.6 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Thu Dec 01 1994 23:15 | 5 |
| Andy,
Get in line..... ;-}
Dan
|
| 495.7 | | OPG::PHILIP | And through the square window... | Fri Dec 02 1994 10:02 | 8 |
|
Ahhhhh dissent within the ranks!! Is this Mutinee?
I dont think that you would want my job, or the pittance I get paid,
trust me ;-)
Cheers,
Phil
|