Posts: 31 Location: Fort Worth, TX, USA Joined: 15.12.05
Posted on July 31 2014 00:01
On the back of my M95 the MMJ jacks are labeled from left to right, Port 0, 1, 3. The OPA0: port is the rightmost port, #3.
A M40 may be different though. If you're getting the init sequence when it's powered up, that should be the right port. It goes through the testing okay?
Something like this:
KA51-A V2.6, VMB 2.15
Performing normal system tests.
Then you get the "dead sergeants" prompt and it tries to boot from ESA0?
One possibility is that your console cable has the correct pinout for sending but the receive (from the terminal) is wrong or broken. Are you using a DEC cable or a home made one? Do you have anything else to test it with?
Check your wiring. Search http://labs.hoffmanlabs.com/ for the openvms faq and serial port information.
Most RJ-45 or home-made Modtap to 25 or 9 pin adapters are wired wrong and are missing a signal return. Usually this is not noticed because the signal returns are usually also connected to the chassis and will happily pass through the safety ground pin between the devices.
There are two signal returns in a mod-tap or RJ-45 and when you terminate them on an 9 or 25 pin connector, they both need to be connected together in the adapter.
Terminals, PCs, and VAXes, etc are DTE devices. When you use RJ-45 or Modtap cables that are commonly wired with only one signal return connected, because of the twist, it results a different wire connected to the signal common on each end.
Surprisingly, this usually mostly works, except when it does not. Then strange things happen. And then people who do not pay attention to how things should be wired spend a lot of time arguing that it works everywhere else, so the incorrect wiring could not be the problem.
If the VAX has 9 pin serial ports instead of 25 pin ones, be aware that the older DEC 9 pin serial ports are wired differently than on PCs.
While many devices, and I think that includes the MicroVAX ignore the special signals on the connector, some actually care about them. A PC may be one of those devices.
On your serial connector, if you are not passing the DSR/DTR and RTS/CTS signals through the cable, they need to be jumpered at the connector.
DTR is asserted by a device when it is able send/receive data. A serial port that does not have a program connected to it or is listening for login should not be asserting DTR. But who cares about standards?
A device should not pay attention to any serial input unless the DSR signal has been asserted from the remote device. So the DSR must be connected to the sending DTR or jumpered to the local DSR. On a properly configured system, dropping DSR on an interactive terminal session should cause the session to disconnect or logout.
CTS is asserted when the program connected a serial port is able to accept data.
A program should not send data out the serial port if RTS is not asserted.
Of course these behaviors are inconsistently implemented. I do recall some PC terminal emulation programs refusing to work properly if the RTS signal is missing.
So I always make sure either the signals are wired or jumpered.
malmberg September 05 2020 VSI community non-commercial licenses for AXP/IA64 are available now.
malmberg September 05 2020 See the forum about licensing. Don't know if HPE hobby licenses still being issued. Commercial licenses still being sold.
silfox70 September 01 2020 I need the license for OpenVMS7.3. Where can I find them?
malmberg August 29 2020 Eisner, which is currently being moved, got an SSH update and the keys were updated to more modern encryption standards.
jiml July 11 2020 ssh to eisner is now giving (on linux) "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!" , Has the server key in fact changed ? Of WHO can we ask that somewhere on the eisner webpage they
wyan May 06 2020 Turns out I had an account here, it still was set to my location a decade ago, so hey, I'm back after over a decade!
Hein April 21 2020 Hi all, haven't been here in years. Good to see it is all there still. I'm looking around at the forum to stop/start msipcap - 'could not be stopped' - for now. I'll shutdown FreeA
EstesDave January 09 2020 does anyone have or know of DRB32 manuals