|
Hi Leif, On my 150 there were two identical ports for the console cable, but of course only 1 was the correct port. Since I only used the console once a year or so, I was always confused as to which was which. So when I got the "connection broken" msg I switch to the other port. The other solution when I had console connection problems was to reboot the 400 and/or the pc. Also, I think the pc console software had to be active when the 400 booted up. Good luck, Steve Richter -----Original Message----- From: midrange-l-admin@midrange.com [mailto:midrange-l-admin@midrange.com]On Behalf Of Leif Svalgaard Sent: Wednesday, March 13, 2002 10:32 PM To: midrange-l@midrange.com Subject: Re: 504 From: <bdietz@3x.com> To: <midrange-l@midrange.com> Sent: Wednesday, March 13, 2002 9:15 PM Subject: Re: 504 > Are you sure you are using async console. What is the part number of the > comm cable? > What type of comm card are you plugging into? If i remember right you are > v5r1. > One box is V5R1, the other one is V4R5. The console has worked great (the PC with CA at my end of the cable) on both machines until I just moved the cable from one to the other one. Now none of them work. That is, moving it back to the one that worked (V5R1) it now longer works on it. I'm absolutely flabbergasted. If I go with CFGPCS on either box and select option 5 (ASYNC) it says "no hardware found on this system". If I go to WRKHDWRSC *CMN it says Comm Adapter (and port) "Not detected". If I try from CA's Connections display to verify the connection on either box it says "Connection verified" although only one of them even has a cable. If I go WRKDEVD *ALL, I see DSP02 (that's the one that used to work). Option 8 (Work with status) says DSP02 "powered off or not yet available". Option 1 to Make available results in: "DSP02 already available". As you can see, I'm totally mystified. No software or configuration has changed, all I did was to unplug the cable from one box and plug it into the other box (and eventually back again to the first box). _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.