|
You said you can telnet in. Can you take a look at your QINTERXXXXX subsystem descriptions and take a look at the workstation types and names to see why one of those subsystems isn't picking this device up. It sounds like it is on CTL02 like you said. Other than being locked out of an interactive subsystem by name, I can't imagine why it won't come up. Also, since you determined that the cable is ok, you may want to try another port on the brick. Maybe it's a bad brick or link cable. Autoconfig should just grab it and give it another device. Thanks, Mark Mark D. Walter Senior Programmer/Analyst CCX, Inc. mwalter@xxxxxxxxxx http://www.ccxinc.com Pete Helgren <Pete@xxxxxxxxxx> Sent by: To midrange-l-bounce Midrange Systems Technical s@xxxxxxxxxxxx Discussion <midrange-l@xxxxxxxxxxxx> cc 04/19/2005 02:38 PM Subject Re: No signon screen Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> No. No Ops Console. This system always had a Twinax console. But, I am beginning to think that there WAS another twinax controller at one time. Here is what I am seeing: CTL01 is a 266C device type (not sure what that is exactly) CTL02 is a 2722 device type. The QCTLSBSD is QCTL. QCTL is active. There is a QCTL controller defined as a 266C device although it is varied off. If you try to vary it on it tells you that the resource is already in use (presumably by CTL01 which uses the same resource). When I delete the terminal device description on CTL02 (the only device configured on it), it autoconfigs as DSP020000 which tells me that it is on CTL02 (true) and has address 0 (true) on port 0 (true). Even if I didn't want this as a console, shouldn't it still give me a signon screen? There is only one connector at the back of the 720 that will connect to the "brick". I just re-checked that the cable and terminal are OK by taking the terminal and cable off of our Model 800 and putting it on the 720. No luck. I suspect that it has something to do with the fact that the Twinax controller is CTL02 and probably something to do with the multiple QINTER subsystems but I can't quite pull it all together. Pete Ingvaldson, Scott wrote: >I wouldn't try the install until I knew I could get a console device, >you'll be in bad shape without it. Since you can't force the console >using DST that indicates to me that your device is not the console. Was >this system possibly originaly configured with an Ops Console? > >Regards, > >Scott Ingvaldson >iSeries System Administrator >GuideOne Insurance Group > >-----Original Message----- >date: Tue, 19 Apr 2005 10:21:33 -0600 >from: Pete Helgren <Pete@xxxxxxxxxx> >subject: Re: No signon screen > >OK, lots of suggestions. Let me see if I can sort through them all. > >Mark: I am not necessarily trying to get this guy to come up as a >console. I'd just like to make sure I get a signon screen so that I >know everything is working OK BEFORE I scratch this thing. I'd hate to >scratch install and not have a console at that point so what I am trying >to do is a reality check to make sure that when I really do need it, it >will come up. > >Phil: When I do a PRTDEVADR on CTL02 I have a single 3476 device called >DSP010000. > >Scott: No SRC codes. I tried changing the front panel to manual then set >the option to 21 and pressed enter (think that is what you meant by >forcing DST option 21). No change. > >Rob: > >- If QCTLSBSD is set to QCTL, make sure that QINTER is running. > >It is, and they have this thing configured with two interactive >subsystems: QINTER001 and QINTER002. AS I recall they did this because >they had, like, 1000 devices on QINTER and somehow it reached a maximum >so they split the subsystem in two. > >- Check the station address on the terminal Address is 0 >- Check the port number that you are plugged into Port is 0 > >- Check out that the workstation is varied on. > >DSP010000 shows varied on. > >QCONSOLE shows that DSP010000 is the console name. > > >More questions arise in my mind though. The DSP010000 value as console >tells me that it was originally created on CTL01, correct? CTL01 shows >a type of 266C. CTL02 shows a type of 2722 and that is what the twinax >"brick" cable is connected to. Perhaps they removed the original >hardware for CTL01? There is an empty slot in the back of this thing and >I don't see anything indicating a 266C on the back either. > >I hate to just "try" a scratch install and hope that I get a console. I >want to know all was well before I wipe it clean..... > >Thanks, > >Pete > > > -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx 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
