Re: Operations Console problem -- MIDRANGE-L

Some thoughts

Evan mentioned not using the console for other stuff and Iwholeheartedly support that. It makes for simply too many things to gowrong. I DO however use W2K Server as the console quite often because Ilove the ability to use terminal services to access the consoleremotely. While unsupported, I've found it to be rock solid repeatedlyboth for LAN console and Direct Attach.

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

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

If you meant LAN console then you will need to reset the passwords onthe console PC and on the Server .The password gets encrypted and sharedbetween the PC and the system. When you changed PCs the new one doesn'thave the encrypted password and the system no longer has an unencryptedone. Since you have changed the console to 5250 for now, you can simplyboot to DST, then change the password for the QCONSOLE console deviceback 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 SQLserver on which we loaded Client Access but we can not attach as an opsconsole, it just sits at "connection pending". The odd thing is we can useOps Nav and see the file structure and directory listing of objects, so yesthe wire is connected. We've IPL'd the 800 with a 5250 as the console so wecan 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 itwon't accept PC C as the console. I know we can't try anything until were-IPL to remove the 5250 console.