Re: Twinax

I'm thinking it MUST have been after V3R1 because we had Hawkeye and used that
for remote control units for that very reason. Hmmm, must have been added 
latter.
Oh. well, good to know.  I had already written something to do this a while back
that presents in in what I consider to be a better format, but the hoops I 
jumped
through to get that info, would be MUCH easier swiped from the IBM generated
report :-)

Chuck

barsa@barsaconsulting.com wrote:

> Chuck,
>
> I don't know.
>
> I had a note from someone privately that said that it did not handle
> remote, but the help text clearly seems to differ.
>
> In general, remote work station controllers got most of the improvements in
> V3R1.  That was when the System Value (my favorite topic) QAUTORMT was
> added.
>
> Al
>
> Al Barsa, Jr.
> Barsa Consulting Group, LLC
>
> 400>390
>
> 914-251-1234
> 914-251-9406 fax
>
> http://www.barsaconsulting.com
> http://www.taatool.com
>
>                     Chuck Lewis
>                     <clewis@iquest.net>       To:     midrange-l@midrange.com
>                     Sent by:                  cc:
>                     midrange-l-admin@mi       Subject:     Re: Twinax
>                     drange.com
>
>                     09/18/01 01:20 PM
>                     Please respond to
>                     midrange-l
>
> Well I'll be danged Al - when did that change (to include remotes) ?
>
> Chuck
>
> barsa@barsaconsulting.com wrote:
>
> > PRTDEVADR works for both local and remote controllers.
> >
> > Al
> >
> > Al Barsa, Jr.
> > Barsa Consulting Group, LLC
> >
> > 400>390
> >
> > 914-251-1234
> > 914-251-9406 fax
> >
> > http://www.barsaconsulting.com
> > http://www.taatool.com
> >
> >                     "Dan Neal"
> >                     <dneal@btcgrp.com>        To:
> <midrange-l@midrange.com>
> >                     Sent by:                  cc:
> >                     midrange-l-admin@mi       Subject:     RE: Twinax
> >                     drange.com
> >
> >                     09/18/01 12:21 PM
> >                     Please respond to
> >                     midrange-l
> >
> > I should have said this is a remote workstation controller not local.
> Any
> > way to print that list.
> >
> > Thanks
> >
> > -----Original Message-----
> > From: midrange-l-admin@midrange.com
> > [mailto:midrange-l-admin@midrange.com]On Behalf Of
> > steven.donnellan@simonjersey.com
> > Sent: Tuesday, September 18, 2001 12:15 PM
> > To: midrange-l@midrange.com
> > Subject: Re: Twinax
> >
> > This is a multipart message in MIME format.
> > --
> > [ Picked text/plain from multipart/alternative ]
> > PRTDEVADR
> >
> > Steven Donnellan
> > AS/400 Systems Manager
> > IBM Certified Specialist - AS/400 Professional Operator
> > Simon Jersey Ltd
> >
> > http://www.simonjersey.com
> >
> > "Dan Neal" <dneal@btcgrp.com>
> > Sent by: midrange-l-admin@MIDRANGE.COM
> > 18/09/01 17:12
> > Please respond to midrange-l
> >
> >         To:     <midrange-l@midrange.com>
> >         cc:
> >         Subject:        Twinax
> >
> > We use primarily IP addressing but also has some twinax.  I recall from
> > years back that you can print a listing of twinax devices and their
> > addresses.
> >
> > Can someone assist with the command to print the list.
> >
> > Thanks
> >
> > Dan Neal
> >
> > _______________________________________________
> > 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.
> >
> > --
> >
> > _______________________________________________
> > 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.
> >
> > _______________________________________________
> > 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.
> >
> > _______________________________________________
> > 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.
>
> _______________________________________________
> 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.
>
> _______________________________________________
> 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.