Re: Ops Console problems -- MIDRANGE-L

We had the same problem some months ago on a new 170 at v4r3.  IBM support 
talked me
thru the setup and were able to get it corrected.  I don't remember all the 
steps,
but we did have to download a newer version of MSDUN from MS, and the steps to
install it on the PC were somewhat complex (as I remember it).   The other 
thing I
remember was that I had to "swap" the ops console cable and the ecs modem cable
connections on the back of the /400.  As I recall, if you use what they call "EZ
Setup" the cables attach one way, and if you use the "not ez setup" they are
reversed.  Once I got it setup, I promised myself I would never again use any 
method
which they named as "EZ"!

Our v4r3 configuration looks like this:

LIN01         2745  Operational           Comm Adapter
     CMN01       2745  Operational           V.24 Port
     CMN02       2745  Operational           Comm Port

and we donot have the 2721's that you have.  I bet either the 2745's or the 
2721's
go away when you get it fixed.  I think the 9745 is just a 2745 which is part 
of the
base system that you get at no additional charge.

We still get asked for the DST UserID and PW sometimes, and I don't understand 
why
that should be needed to start the console!  But we haven't ipl'd enough to 
figure
it out.

hth

Ray

Jon.Paris@halinfo.it wrote:

> After 3 weeks of trying we still cannot get the "new style" console on our new
> V4R4 Mod 170 to work.  We've got the CA PTFs loaded and with those we get
> further but ......
>
> When we try to connect we get asked for the DST User Id and PW and then it 
>just
> sits "validating" for a while before issuing a message (no ref # of course!)
> that indicates a communications failure while trying to validate the signon.  
>We
> have enabled all logging options in CA but nothing is logged.  A look at the 
>log
> from the "Modem" that was generated by the install indicates that the 400 was
> contacted and responded (with a <CR>) nothing else significant appears until 
>we
> disconnect.
>
> We have worked with IBM on this, and they have a problem log identical to ours
> which was closed because the customer got fed up with wasting so much time on 
>it
> and (as we have had to do to use the machine at all) went back to the old 
>style
> console.
>
> Anyone got any ideas?  Or if you have a new 170 at V4R4 perhaps you could tell
> me what your line descriptions etc. look like. Our hardware cfg looks a little
> odd but I have no idea what "normal" looks like.  Our console IOP is a 9745 
>but
> this doesn't show up - what we see is below - a 2745 which is operational and 
>a
> 2721 marked as "not detected".
>
>  Resource        Type  Status                Text
>  CMB01           6757  Operational           Combined function IOP
>    LIN03         2721  Not detected          Comm Adapter
>      CMN04       2721  Not detected          Comm Port
>      CMN05       2721  Not detected          Comm Port
>    LIN01         2745  Operational           Comm Adapter
>      CMN01       2745  Operational           V.24 Port
>      CMN02       2745  Operational           Comm Port
>
> This is all taking up way too much time and I'm wondering just what I'll lose 
>if
>  we just give up and save ourselves the frustration!
>
> +---
> | 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
> +---

--
Ray Peterson
WITC - Shell Lake
505 Pine Ridge Drive
Shell Lake  WI  54871
www.witc.tec.wi.us
715 468-2815


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