- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Vax Console Input not Enabled
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2010 11:24 AM
тАО05-11-2010 11:24 AM
Vax Console Input not Enabled
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2010 11:54 AM
тАО05-11-2010 11:54 AM
Re: Vax Console Input not Enabled
but I'd start with:
SHOW TERMINAL OPA0
Look for "[No] Type_ahead". If it's "No",
then that might explain everything.
> [...] sometime during the boot process, the
> console input is disabled. [...]
Well, I'd say that it's disabled at the
beginning, and gets (re-)enabled late in the
start-up sequence (if ever).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2010 01:12 PM
тАО05-11-2010 01:12 PM
Re: Vax Console Input not Enabled
To determine if this is the case and in addition to the SHOW TERMINAL, issue a SHOW DEVICE /FULL and see if there's an (non-zero) owning process PID listed for the console.
There were AFAIK patches, or (as most of us did) you simply disabled OPCOM output on the console.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2010 09:39 PM
тАО05-11-2010 09:39 PM
Re: Vax Console Input not Enabled
If you're able to login from another terminal or a remote system check the various suggestions that others have suggested. Also check OPA0 to see what it's terminal characteristics have become. Check for broadcast, broadcast mailbox, typeahead... I'm stretching my memory here and no longer have access to Notes that cover the issue with $ SET LOGIN, but I vaguely remember that in some circumstances you could still login from remotes or other terminals. All are worth a look to check. If you could post the output from $ SHOW TERM OPA0 as an attachment somehow that would help.
bob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2010 11:59 PM
тАО05-11-2010 11:59 PM
Re: Vax Console Input not Enabled
welcome to the OpenVMS ITRC forums.
When talking about 'input' on OPA0:, you are certainly expecting to get a Username: prompt, when typing
Some VAX 4000 systems have this 'annoying' feature, that you can't immediately login on the console terminal, once startup has finished. Sometimes you have to wait a little bit, maybe a couple of minutes. Did you try that ?
Please also check SHOW TERM OPA0: and SHOW DEV/FULL OPA0: - as requested.
Try to login from remote and issue a SET LOGIN/INTER=128, then try to login on the console again, if the previous checks did not show a problem.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-12-2010 03:36 PM
тАО05-12-2010 03:36 PM
Re: Vax Console Input not Enabled
To answer some questions:
Current login interactive login limit is 64. Setting it to 128 made no difference. Current interactive value = 1, does this mean that my remote is one and OPA0 is not interactive?
I find no place in startup files where it calls for $ SET LOGIN/INTERACTIVE, but that may only be due to not looking in the right place. The "show terminal OPA0" file shows the device as interactive.
I've attached a couple of Word files for reference if anyone cares to look further. This has been running a good while like this, but it would be nice to get my console back.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-12-2010 05:54 PM
тАО05-12-2010 05:54 PM
Re: Vax Console Input not Enabled
search sys$startup:*.com "/interactive"
> The "show terminal OPA0" file shows the
> device as interactive.
That's all it says? Really?
> Okay, let me try to make this clearer.
> [...]
> I've attached a couple of Word files [...]
And if I were sitting at a Windows system I
might care. (That's clearer?)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-12-2010 11:07 PM
тАО05-12-2010 11:07 PM
Re: Vax Console Input not Enabled
when posting session output from a terminal session in an OpenVMS related forum, it would be appreciated, if you include simple plain ASCII .TXT files. Use cut & paste or the session log file function of your terminal emulator and post a .TXT file as an attachment.
Your OPA0: terminal is set to /TYPE_AHEAD and /INTERACTIVE, so that would be fine. Unfortunately the SHOW DEV OPA0:/FULL output is missing.
The SET LOGIN/INTER=n command will be executed from VMS$LPBEGIN-050_STARTUP.COM with a value of n = startup$interactive_logins - this global symbol could be defined in your startup files.
Did you try logging in on OPA0: after waiting for a couple of minutes after the 'Job terminated' message ?
To show, that physical input still works on OPA0:, once the system has booted, try this:
In your remote TELNET session, issue the following commands:
$ OPEN/READ/WRITE x OPA0:
$ READ/PROMPT="Hallo: " x line
Then you should see the "Hallo: " prompt on your OPA0:, enter some text and press
Then return to your TELNET sessiom , which should be at the DCL prompt again. Enter $ SHOW SYMB line - you should see your response typed on the OPA0:
Then don't forget to enter $ CLOSE x on your TELNET session, otherwise you'll block your OPA0: terminal from logging in again, because you have still a channel assigned to OPA0:
If the OPEN/READ/WRITE x OPA0: command fails, you might have found the problem ! Some other process may have a channel assigned to OPA0:
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-13-2010 06:51 AM
тАО05-13-2010 06:51 AM
Re: Vax Console Input not Enabled
Could it be because the Device Type: is LA36 (which if I remember correctly is a Dot Matrix Printer.)??
Dave.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-13-2010 11:21 AM
тАО05-13-2010 11:21 AM
Re: Vax Console Input not Enabled
if so, then what has changed (VMS updates, wiring changes, etc) since then ?
WAG - VMS changes the baud rate or modem controls or something, resulting in the vt520 not being set properly ... I noticed AutoBaud is disabled ...
have you tried any other terminal (or terminal emulator) ... any other cables or adapters ... again just a wild guess.
Interesting problem :-)
Verne