|
-- [ Picked text/plain from multipart/alternative ] Hi Vern, Shame about the absent twinax adapter. One thing I haven't tried is the Lan Console. Probably not very practicle because it think it needs a dedicated Lan Card. I think the problem with Ops Console is Windows related and largely out of IBMs control. IBM have put OS/400 in Microsoft's 'capable' hands and it is up to MS to produce the reliablity!!! My own thoughts on this matter are - if a Windows system is working leave it alone, don't change it, don't install anything new, and it should continue working. If you have a working console I would be tempted to keep it and leave it dedicated to that job. Unfortunately, when Windows applications don't work it can be very difficult to find out why and correct the problem. The cost in time and effort to 'bring things up to date' is likely to be far greater than the value of the PC hardware. If the console ties up the laptop, it would probably be cheaper to buy a new laptop than to try and set up another console. Best of luck with this one Syd Nicholson vhamberg@attbi.com wrote: >Thanks, Syd > >I understand exactly what you say. But we don't have a >twinax card on the 400. We do have an ancient PC with a >twinax card, but I'd still need a port out of the 400, >right? > >Win98 has been fairly stable, on a laptop with powersave >turned off. Maybe I'll go to an older machine that's I'm >replacing with this Win2K box and install 98SE on it and >see. > >I'll check the archives, too. Why is this so hard? I >remember the earlier discussion. > >>Hi Vern, >> >>I had a similar problem which ended up being the subject of much >>discussion about the OS/400 console. >> >>I my case I was unable to resolve the problem in the time I was prepared >>to give it. I resorted to (and still use) a 'Dumb' twinax terminal for a >>console - vastly superior to anything else IBM has come up with. >> >>The messages I received were much the same as the ones you outline >>below, but in my case I could get a connection and I was able to use >>Ops Console. The problem I had was that it wasn't stable - It would >>crash in the middle of a SAVSYS, or a Cum PTF install, or some other >>important function. I would have considerable dificultly re-establishing >>the connection to the system, which is not a pleasant situation when the >>system is in restricted state. Sometimes it was necessary to force power >>off, do a normal IPL, then start the process all over again and hope it >>doesn't crash a second time. One can go round and round in circles here. >> >>The message I am trying to put over, though rather negative, is - even >>if you do get it working it might not be reliable. You might be better >>to consider alternatives. >> >>Syd Nicholson >> >>vhamberg@attbi.com wrote: >> >>>I'm having fits with Ops Console on a Win2K box. Same >>>one I'm having Domino plugin problems with. It has >>>worked fine consistently with a Win98 laptop. >>> >>>New Dell 500SC server, on which I put Win2K Pro instead >>>of Server. Ops Console setup manual only speaks of Pro. >>>Installed SP3 for Win2K. >>> >>>I'm setting up a direct cable LCS, no RCS's. I created >>>the "modem" according to the manual, then went carefully >>>through the steps for creating a new connection. Max >>>speed 115200, as specified. It's going to a new 270-2248 >>>(1517) 1gig 6x17.54 DASD. >>> >>>I get a 'Communication error validating... Error code >>>10060' when using 115200 speed. When I shut it down to >>>19200, as suggested for authentication errors, I get 2 >>>messages, 'RAS connection to FLASH failed. There was a >>>hardware failure in the modem', and 'Console connection >>>to FLASH failed. Do you want to try again?' >>> >_______________________________________________ >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.
midrange.com
