Re: Operations Console problem

[Larry Bolhuis <lbolhuis@xxxxxxxxxx>]

Some thoughts

Evan mentioned not using the console for other stuff and I 
wholeheartedly support that. It makes for simply too many things to go 
wrong. I DO however use W2K Server as the console quite often because I 
love the ability to use terminal services to access the console 
remotely. While unsupported, I've found it to be rock solid repeatedly 
both for LAN console and Direct Attach.

Since you mention 'Local' I'm assuming you really meant using the 
Direct/Async cable. In that case did you install the modem driver for 
the serial port? Did you install to the correct COMx port if there are 
more than one? Did you have an available 9 pin port on the server or did 
you have to add one (perhaps via USB.) If you added a USB serial port 
you have about a 50/50 chance that the connection will work.   Did you 
try hyperterminal at 115200 and type NEGOTIATE? You should get a 
response of 115,200 which tells you the system and the PC are 
communicating.

There is no special password saved in this connection type. On V5R2 the 
system will find the first IOA that pops up and is console capable so 
you'll want to move the Twinax IOA to another IOP or you risk the system 
finding that first and quitting on the operations console connection.

If you meant LAN console then you will need to reset the passwords on 
the console PC and on the Server .The password gets encrypted and shared 
between the PC and the system. When you changed PCs the new one doesn't 
have the encrypted password and the system no longer has an unencrypted 
one. Since you have changed the console to 5250 for now, you can simply 
boot to DST, then change the password for the QCONSOLE console device 
back to QCONSOLE (Be SURE to use CAPS and it MUST be QCONSOLE).

- Larry

nntp://news.gmane.org/gmane.group.name: wrote:
> 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.
>