IBM eServer iSeries Manual page 106

Access for windows operations console
Hide thumbs Also See for eServer iSeries:
Table of Contents

Advertisement

8. Do a Disconnect.
9. Select File –> Properties.
10. You should be in the Properties for the connection you just created. Select the Settings tab.
11. Click the ASCII Setup button.
12. Change the following settings so there is a check mark in the check box:
v Send line ends with line feeds
v Echo typed characters locally
v Append line feeds to incoming line ends
v Wrap lines that exceed terminal width
13. Click OK. Click OK.
14. Do a Connect.
15. At the server's control panel enter a function 65 (you need to take the server to a known state).
Note: You may need to enter a function 25 and 26 in order to have access to the upper functions.
16. The server's control panel may display D1008065 after a little while. Also, in the HyperTerminal
window, you may get some data.
17. At the server's control panel enter a function 66. You may get D1008066. This reference code may not
appear in all cases. Also, in the HyperTerminal window, you may get some data.
18. Using uppercase, type NEGOTIATE 1 in the HyperTerminal window. Press Enter. The
HyperTerminal data window displays 115200.
Note: If nothing is returned, repeat NEGOTIATE 1.
If a speed value is returned, you had data exchanged in both directions and have full connectivity. If
Operations Console will not connect, more than likely you have a setup problem on the client side.
If a speed value was not returned, you might try powering off the PC, power it back on, and repeat
the test. Or attempt to connect the console again. In rare cases the server may need to be IPLed. For
the best results it is recommended you do the following, in sequence:
a. Power off the server.
b. Power off the PC.
c. Power on the PC.
d. Start a connection for the console.
e. Power on the server.
If the above process fails to solve your connection problem, you need to contact your service
provider for further assistance.
Remote console connection problems
When setting up your remote console you may encounter problems connecting. Possible troubleshooting
solutions include:
Remote console through dial-up fails to connect to local console
Solutions to a problem that occurs when a remote console modem fails to establish a connection
with a local console.
Local console name mismatch when remote console connects to the local console
Reasons for a possible console name mismatch when the remote console connects to the local
console.
Remote console through dial-up fails to connect to local console: While you are connecting a remote
console to a local console, you may encounter remote console connection problems. These are solutions to
a problem that occurs when a remote console modem fails to establish a connection with a local console:
100
iSeries: iSeries Access for Windows Operations Console

Advertisement

Table of Contents
loading

Table of Contents