MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » March 2007

Operations Console problem



fixed

We've got an as400 model 170 v4r5 and a model 800 v5r2 on the same network.

The 170 console is defined as local on PC A. That works OK
The 800 console was defined as local on PC B. That use to work fine.

PC A and B are used as servers for Exchange and SQL server

PC B is no longer around and was replaced by PC C which is now the SQL 
server on which we loaded Client Access but we can not attach as an ops 
console, it just sits at "connection pending". The odd thing is we can use 
Ops Nav and see the file structure and directory listing of objects, so yes 
the wire is connected. We've IPL'd the 800 with a 5250 as the console so we 
can do console things but we'd rather not live with that.

Any suggestions as what to look at.

Does the 800 have a setting somewhere that is set to the name of PC B so it 
won't accept PC C as the console. I know we can't try anything until we 
re-IPL to remove the 5250 console.





Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact