|
Dave, I would respectfully disagree. The console should show up in the controlling subsystem. IBM ships two controlling subsystems, QBASE and QCTL, however you can change this to any subsystem you want. This is determined by the system value QCTLSBSD. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 "i" comes before "p", "x" and "z" e gads Our system's had more names than Elizabeth Taylor! 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com http://www.as400connection.com daparnin@cooperst andard.com Sent by: To midrange-l-bounce midrange-l@xxxxxxxxxxxx s@xxxxxxxxxxxx cc Subject 04/01/2005 09:24 Re: IPL Error AM Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> We found that we had a similar situation except that we found it on the first IPL of a V5R3 upgrade. Our original twinax console had died last year and was replaced with another twinax terminal but was never set to address 0. A normal IPL found it plugged into port 0 but this one did not. If you do a normal IPL does the console show up under QINTER or QCTL? If QINTER I would say that it's the address. Dave Parnin Nishikawa Standard Company Topeka, IN 46571 daparnin@xxxxxxxxxxxxxxxxxx Keith Carpenter <carpcon@xxxxxxx> To: Midrange Systems Technical Discussion Sent by: <midrange-l@xxxxxxxxxxxx>@SMTP@CTB midrange-l-bounces@m cc: (bcc: David A Parnin/Topeka/NISCO/SPCO) idrange.com Subject: Re: IPL Error 03/31/2005 11:03 PM Please respond to Midrange Systems Technical Discussion <midrange-l@midrange .com> For a twinax terminal to be a "console" it must be set to address 0 and be on port 0 of the first twinax controller. Anything else will *only* work when the OS is running (after IPL). dpalme@xxxxxxxxxxx wrote: > I was working from the console, our console is connected via twinax and with > a normal IPL it loads fine, and we can log in from the console with no > problem, perform normal everyday routines, it is only when attempting a BM > that it fails. > > The console is connected and powered on > > -- 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. -- 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.