10-02-2012 11:49 AM
I have a VAX 4000 machine that does not accept user input on the local system console. I've restarted the terminal (power off/on) and it shows the VT420 screen, and when I hit the return key it shows a blinking cursor only. If I hit the CAPS lock key, the 'lock' indicator shows on the screen so it is accepting some input.
I'm able to log in to the system from a remote terminal, so I can issue commands. The obvious answer might be to restart the system, but it is not that simple. I can't do that without significant compensatory measures in place. So, is there a simple way to reset the local console device? Maybe disable it and then enable it again? I'm fairly new to VAX systems, so I appologize for the newbie question.
Thanks in advance,
10-02-2012 12:31 PM
If you can log in to a remote terminal, look at OPA0 for its status. If it is allocated, check who has it and what they are doing. This can get involved a bit, so if you are not familiar with OpenVMS, this will take a while.
Can you shoot me contact info via Email so we can talk directly or Email directly. There may be things you don't want posted on a public forum.
10-02-2012 02:43 PM
Simple things first, try a control-q at the console.
It's been a very long time, but some VAX models would crash if the console was disconnected. I don't recall if the 4000 had this feature.
Confirm that the port is correct terminal port. Terminals can have multiple serial ports, if the terminal was switched from comm 2 to comm 1, this would be expected behavior. Confirm the VAX cable is going into the comm port configured in setup.
Check the port speed against the terminal speed. I'd expect garble on screen if this was the case, but it's worth checking.
10-03-2012 03:22 AM
Output from 'SHOW DEV' has the status of OPA0 as 'online' with 0 errors. I'm thinking that maybe the terminal was left logged in accidentally and now the session is hung up.
10-03-2012 03:25 AM
I know about the terminal reset problem and our system has the 'halt on break' turned off. I've tried CTRL-Q as well with no luck. I'll check the serial port settings but am very confident that they are OK. The console was working fine previous and it is difficult for people to make changes to the cabling without someone knowing they were in the cabinet.
10-03-2012 10:56 AM
Have you verified the VT terminal is working correctly? Can you bring up the set menus (F5 key I think)?
Do a SHOW TERMINAL OPA0 from another session and post the results.
10-04-2012 06:55 AM
Note that the F5 key is normally the equivalent of a Ctrl-P on the console.
The F3-key is the "setup" key.
Kris (aka Qkcl)
10-04-2012 08:45 AM
I have found that terminal lines can get into an "unknown" state that is not apparent. I have successfully use the following sequence of commands to "clear" them. Give this a try.
Seems simple enough, but this seems to clear out any remaining buffers that are hanging around and attached to the terminal. I'm not sure of why or what is "hanging" around, just that this has cleared up terminal lines with similar symptoms for me.