RE: v5r2

[rob@xxxxxxxxx]

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
If that is the case, then convert your PC's from twinax to LAN.  It's a
rare business that is thriving that is not running a lan, so you probably
have one anyway.

Back when the AS/400 first came out and we were planning the move, a boss
thought we should evaluate other platforms, like Wang.  At that time we
had over $250,000 in twinax perephials alone.  For that reason, and
numerous others, I thought we should ditch the move and just go to the
400.  Anyone aware of Wang's history knows that I am glad we did.  But
now, our usage of twinax terminals is extremely limited.  With the low
cost of netstations or PC's I can't see a reason to put in twinax
anywhere.  Including dirty shop floor.  Oh, there will be people who
disagree, and they will continue to cite reasons of durability, ease of
use, security, ease of setup, etc even past the day the last one rolls out
the door at their company.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




"DeLong, Eric" <EDeLong@Sallybeauty.com>
Sent by: midrange-l-admin@midrange.com
11/04/2002 12:13 PM
Please respond to midrange-l

        To:     "'midrange-l@midrange.com'" <midrange-l@midrange.com>
        cc:
        Fax to:
        Subject:        RE: v5r2


Troy,

A clarification.... Possibly your source was referring to twinax connected
PCs, which would require a non-express version of Client Access.  Twinax
PCs
will NOT fully connect (I think; this may apply only to services like file
transfer, remote command, etc.). This began as V5R1 issue.

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



> -----Original Message-----
> From: Troy Dills [mailto:troypmc@charter.net]
> Sent: Monday, November 04, 2002 10:28 AM
> To: midrange-l@midrange.com
> Subject: Re: v5r2
>
>
> Thank you for this info. We were informed that twinax would
> not be supported
> by V5R2 and most of the business uses twinax.   We also have
> a model 620
> AS/400, What kind of downfall will I have as far as resources
> go. We have
> approx. 130 users sign on now, and the CPU shows ++++ alot
> when doing a
> wrkactjob command. Does anyone have any advice concerning
> these issues? All
> inquiries will be greatly appreciated.
> Best Regards
> Troy
> ----- Original Message -----
> From: <rob@dekko.com>
> To: <midrange-l@midrange.com>
> Sent: Monday, November 04, 2002 11:13 AM
> Subject: Re: v5r2
>
>
> > This is a multipart message in MIME format.
> > --
> > [ Picked text/plain from multipart/alternative ]
> > Yes I can verify that.  It's false.  We have 5 iSeries.
> All running V5R2
> > with twinax consoles.  We have a very few 5494 controllers
> supporting a
> > very limited number of twinax devices.  The rest of our
> hundreds of users
> > are attached via PC's with LAN cards, netstations or the like.
> >
> > Was that your question?
> >
> > Rob Berendt
> > --
> > "They that can give up essential liberty to obtain a little
> temporary
> > safety deserve neither liberty nor safety."
> > Benjamin Franklin
> >
> >
> >
> >
> > "Troy Dills" <troypmc@charter.net>
> > Sent by: midrange-l-admin@midrange.com
> > 11/04/2002 11:00 AM
> > Please respond to midrange-l
> >
> >         To:     <MIDRANGE-L@midrange.com>
> >         cc:
> >         Fax to:
> >         Subject:        v5r2
> >
> >
> > Can anyone verify that on V5R2 that twinax will not be supported?
> >
> > Thank You
> > Troy Dills
> > The Parnell Martin Companies LLC
> > 1315 Graham Street
> > Charlotte, NC 28206
> > Phone 704-375-8651
> > Fax      704-375-5250
> >
> > _______________________________________________
> > 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.