|
Jeff, Four posibilities, in the order of liklihood: 1. The new printer is terminating the cable causing the twinax to be doubly terminated. Look for a terminating switch or check the documentation regarding termination. 2. The cable you used to attach the new printer is defective. Check it out with a tester and carefully examine the pins for looseness. 3. The twinax controller in the AS/400 has a defective port. Hope this helps. Joe Frank Synapse Communications, Inc. Jeff Crosby wrote: > > I guess one has never seen it all because I saw a new one yesterday and > today. <g> > > I got a new IBM 6400 printer yesterday. My twinax port 0 cabling looks > like this: > > Console (3180 display) at address 0 > Printer (Anzac 5080) at address 1 > Printer (Anzac 3017) at address 2 > > The above is also the _physical_ cabling device order. I set this new > printer to address 3 and tried to physically cable it in between the 2 > existing printers on port 0. All 3 devices were powered off during > these attempts. > > It wouldn't work. When I would power the console back on, there was no > display. Doing a WRKCFGSTS at another display showed the console as > SIGNON DISPLAY, but the console screen was blank. I didn't even try the > 2 existing printers. No print device was autoconfigured for the new > printer. It was as if the twinax card in the new printer was DOA or > something. > > This morning I tried something different. I had an open port (port 7) > on the AS/400 with no devices on it. I ran a cable from this port on > the AS/400 to the new printer and powered it on. The AS/400 > autoconfigured it just as I expected, device type 4234 address 3. I > have not tried recabling it into the port 0 string where I really want > it. > > Has anyone seen this? Is there some restriction on port 0 (other than > address 0 for the console) that I evidently don't know about? Is this > new printer so new that it won't coexist on the same port with that > ancient 3180 and Anzac printers? <g> Will the AS/400 not autoconfigure > on port 0? > > Thanks for any help. > > -- > -Jeff > > jlcrosby@fwi.com > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.