× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: New Machine, QSECOFR not authorized
  • From: "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
  • Date: Sat, 24 Mar 2001 12:57:30 -0600
  • Importance: Normal

Regardless of the PORT/ADDRESS issue of the twinax brick, I think I'm
starting to understand.  The DB25 connector on the back of my machine is for
an eight-port twinax controller which is not on address 0.  One of the other
connectors is address 0.  Address 0 supports two devices, port 0 and port 1,
and is used for the system console.  Unfortunately, I need a specific cable
to connect a twinax device to the system console, and I have a sneaking
suspicion that I don't have that particular cable.  I believe they're part
numbers 4236482 (with vinyl covering) and 7362062 (with Teflon covering).

So it looks as though my only connection option is through OpsNav.  I do
have the 97H7557 cable required for this.  My concern here is the following:
can I connect both as an LCS (Local Controlling System) and as a regular
device from the same workstation?

Joe

+---
| 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 thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.