hit counter script
IBM eServer iSeries Manual
  1. Manuals
  2. Brands
  3. IBM Manuals
  4. Server
  5. eServer iSeries
  6. Manual
IBM eServer iSeries Manual

IBM eServer iSeries Manual

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

Advertisement

Quick Links

Download this manual
ERserver
iSeries
iSeries Access for Windows
Operations Console
Version 5 Release 3

Advertisement

Table of Contents
loading

Related Manuals for IBM eServer iSeries

Summary of Contents for IBM eServer iSeries

  • Page 1 ERserver iSeries iSeries Access for Windows Operations Console Version 5 Release 3...
  • Page 3 ERserver iSeries iSeries Access for Windows Operations Console Version 5 Release 3...
  • Page 4 “Notices,” on page 111. Fifth Edition (May 2004) This edition applies to version 5, release 3, modification 0 of eServer iSeries Access for Windows (product number 5722-XE1) and to all subsequent releases and modifications until otherwise indicated in new editions. This version does not run on all reduced instruction set computer (RISC) models nor does it run on CISC models.

  • Page 5: Table Of Contents

    . 65 Terms and conditions for downloading and Manage your local console on a network . 77 printing information . . 112 Common tasks . . 86 Troubleshoot Operations Console connections . . 92 © Copyright IBM Corp. 2000, 2005...
  • Page 6 iSeries: iSeries Access for Windows Operations Console...

  • Page 7: Operations Console

    Operations Console support is available on V5R1 and later releases of the OS/400 operating system. The only type of PC console that IBM iSeries Models 270, and 8xx support is Operations Console. Enhanced authentication and data encryption provide network security for console procedures.

  • Page 8: What's New For V5R3

    What’s new for V5R3 New functions for Operations Console include: New functions added to the Operations Console user interface window The user interface has added functions to make it easier to manage your connections. v Expanded Properties dialog for making configuration changes and displaying extensive server information.
  • Page 9 USB support is now available for Operations Console Enhancements for Operations Console include: Improved Configuration Wizard The Installation Wizard has been simplified. v An assumption is made in the wizard to select both the console and remote control panel for LAN configurations.

  • Page 10: Print This Topic

    Print this topic To view or download the PDF version of this document, select Operations Console (1,105 KB). Saving PDF files To save a PDF on your workstation for viewing or printing: 1. Right-click the PDF in your browser (right-click the link above). 2.
  • Page 11 Prepare for your network environment Plan for your minimum network configurations. Secure your Operations Console configuration Plan for your Operations Console network security. Prepare for your Operations Console and iSeries Navigator configuration Plan for how Operations Console works with iSeries Navigator. Verify Operations Console requirements Verify you have met the Operations Console hardware, software and cabling requirements.
  • Page 12 PC. v There is a maximum of 26 emulator sessions available per PC. v IBM recommends that you not put your console on the same IOP as storage devices. – There may be configurations when this cannot be avoided.
  • Page 13 IOP can sometimes make it difficult to determine, in advance, which network adapter will be used for the console. IBM recommends only one network adapter for the IOP tagged as the primary console to support Operations Console local console on a network. The lowest addressed network adapter on the bus will be chosen for the console.
  • Page 14 – If the load source storage device fails and the system recovery will include the use of the IBM distribution Licensed Internal Code media instead of a customer backup, and the system is using Operations Console (LAN), you may have to use another console type for the initial portion of the system recovery.
  • Page 15 Scenarios: Select your configuration The following scenarios assists you in choosing your Operations Console configuration. Scenario: A single console directly attached to the server without remote support A scenario that discusses a situation in which you may want a single console attached to the server. Scenario: A single console directly attached to the server with remote support A scenario that discusses the ability to dial-in to the console from a remote location.
  • Page 16 For this scenario, configure a local console directly attached to the server with remote access allowed on the PC attached to the server. Then configure a remote console through dial-up on the remote PC. See Set up Operations Console to complete an interview that will produce a checklist specific to your configuration.
  • Page 17 For this scenario, configure a local console on a network. See Set up Operations Console to complete an interview that will produce a checklist specific to your configuration. Advantages: v You can configure a single PC to be the console for several different servers or partitions as long as they are connected to the service connection network.
  • Page 18 Network security IBM recommends treating the console over a LAN connection with the same physical security considerations and controls as a local console directly attached to the server or a twinaxial console. For instance, consider configuring a local console on a network in a network separate from the main network (or the company intranet) and strictly control access to the machine acting as the console.
  • Page 19 The iSeries console security consists of service device authentication, user authentication, data privacy, data integrity, and data encryption: Service device authentication This security assures one physical device is the console. Operations Console local console directly attached to the server is a physical connection similar to a twinaxial console. The serial cable you use for Operations Console using a direct connection may be physically secured similar to a twinaxial connection to control access to the physical console device.
  • Page 20 local console on a network encrypts and changes the password during each successful connection. You must use the default password to initially set up your server if using a local console on a network (LAN). Note: The device authentication requires a unique service tools device ID for each PC that will be configured with a local console on a network (LAN) connection.
  • Page 21 IPL to recover. These ports should be excluded from intrusion protection tests. Protection tips When using Operations Console local console on a network, IBM recommends the following items: 1. Create an additional service tools device ID for each PC that will be used as a console with console and control panel attributes.
  • Page 22 each partition is considered a separate iSeries server, you need a separate connection to the partition for which you want to use the console. Operations Console allows multiple connections to a single iSeries server, but only one PC can have control of an iSeries server at a time. Based on the Operation Console connectivity, you could have one of two methods of configuration.
  • Page 23 Figure 2. iSeries Navigator and Operations Console configuration on the same network However, if the network adapter and configured OS/400 LIND and the service network adapter as defined by the service host name (interface name) are on separate networks, then an additional PC LAN adapter is required.
  • Page 24 If you want to use an Operations Console local console on a network (LAN), you need to install the LAN adapter for Operations Console according to your iSeries model. IBM supports a local console on a network (LAN) only on Models 270 and 8xx. Table 2 shows the supported cards for LAN connectivity.
  • Page 25 The iSeries Access for Windows versions, for both the local console and the remote console, must be at the same level for proper operation of Operations Console. PC5250 or IBM Personal Communications (V5.7 CSD 1 minimum) needs to be installed for the console only. It is not required for remote control panel only configurations.
  • Page 26 Table 3. Card location | | | Model Operations Console async card LAN console card location location for the cable | | | 170, 250 Not supported | | | C06, second C05 | | | Not supported | | | 730, 740 See the Cabling information.

  • Page 27: Plan For Your Operations Console Install Or

    Note: Ports 5 thru 9 will only be available when the client service pack SI10817 (V5R3) or later is installed. Any adapter should work but IBM can not guarantee every adapter to work correctly in every PC environment. Should a failure occur, you can contact the manufacturer of the adapter, the manufacturer of the PC, your hardware service provider, or try another adapter.

  • Page 28: Plan For Your Control Panel

    It is recommended that you update iSeries Access for Windows to V5R3 before you upgrade the OS/400 operating system. For more information, see Install iSeries Access for Windows. Note: Failure to comply with the above actions may prevent the console from working correctly during the upgrade or install.
  • Page 29 RCP-only configuration. The VCP will require an additional configuration. Note: There are no requirements for PTFs on the server at this time. It is recommended that you install the latest service pack for the V5R3 client. The latest service pack can be found at: http://www-1.ibm.com/servers/eserver/iseries/clientaccess/casp.htm Operations Console...
  • Page 30 For additional information about the virtual control panel see the following: v Limitations of the virtual control panel for additional items to consider about the virtual control panel. v Installing the virtual control panel for instructions to install the virtual control panel. v Troubleshoot remote control panel and virtual control panel problems to solve problems with the virtual control panel.
  • Page 31 mode function available until the keystick is present. For systems without the keystick, the user ID being used would only require the remote panel key privilege. Installing the virtual control panel: Use the procedures below to install the virtual control panel. Create a service tools device ID using an existing console The virtual control panel (VCP) requires an available, unused service tools device ID.
  • Page 32 8. Use PF3 to go back to the DST main menu. Check user ID for permissions If you are using a service tools user ID other than QSECOFR, QSRV, 22222222, or 11111111 for use with the VCP, you have to set the service tools user privileges for Partition remote panel key to allow access to the mode function.
  • Page 33 Operations Console such as 192.168.1.n. If so, use the base address currently assigned to Operations Console, but make the last value a 2. For example, use 192.168.1.2. To check the current base address, use regedit (or other registry editing program) and navigate to: HKEY_LOCAL_MACHINE/Software/IBM/Client Access/CurrentVersion/AS400 Operations Console/LCS/HKEY_LOCAL_MACHINE/Software/IBM/Client Access/CurrentVersion/AS400 Operations Console/LCS/ Expand LCS and select the appropriate configuration.

  • Page 34: Prepare The Pc For Operations Console

    Prepare the PC for Operations Console Before beginning your Operations Console setup tasks, complete the planning requirements in Plan for Operations Console. After you complete the planning requirements you will know which configuration you will be creating. You can create a setup checklist if you know which configuration you will be doing and which PC operating system you will be using.
  • Page 35 __ 1. Meet Operations Console hardware requirements. __ 2. Meet Operations Console software requirements. __ 3. Meet Operations Console cable requirements. __ 4. Verify available communications port. __ 5. Run prerequisite checking program on the PC. __ 6. Install iSeries Access for Windows. __ 7.
  • Page 36 Complete prerequisite checklist for Windows 2000 Complete the prerequisite checklist for a local console directly attached to the server with remote access allowed running Windows 2000. Complete prerequisite checklist for Windows XP Complete the prerequisite checklist for a local console directly attached to the server with remote access allowed running Windows XP.
  • Page 37 __ 1. Meet Operations Console hardware requirements. __ 2. Meet Operations Console software requirements. __ 3. Meet Operations Console cable requirements. __ 4. Verify available communications port. __ 5. Run prerequisite checking program on the PC. __ 6. Install iSeries Access for Windows. __ 7.
  • Page 38 Complete prerequisite checklist for Windows XP: Local console on a network: Complete the following checklist to set up a local console on a network on Windows XP: __ 1. Meet Operations Console hardware requirements. __ 2. Meet Operations Console software requirements. __ 3.

  • Page 39: Complete Required Prerequisite Tasks

    Complete prerequisite checklist for Windows XP: Remote console through dial-up support: Complete the following checklist to set up a remote console through dial-up on Windows XP: __ 1. Meet Operations Console hardware requirements. __ 2. Meet Operations Console software requirements. __ 3.
  • Page 40 Access for Windows, you are going to install a 5250 emulator (if you do not already have PC5250 or IBM Personal Communications V5.7 CSD 1 minimum) and Operations Console support. See the iSeries Access web site for updated PC requirements.
  • Page 41 Note: The Operations Console component is not available using the Typical or PC5250 User options. a. Required Programs b. 5250 Display and Printer Emulator (if IBM Personal Communications (V5.7 CSD 1 minimum) is not installed) You do not need a license to use 5250 Display Emulation just for Operations Console, even though the window says that you do.
  • Page 42 6. Navigate to drive:\path\Client Access\Aoc\Inf\ cwbopaoc.inf where drive: is the drive where iSeries Access for Windows is installed. Note: The default installation path C:\Program Files\Ibm\Client Access\Aoc\Inf\cwbopaoc.inf. 7. Click Open, then click OK. 8. Select the communications port where you are going to install the Operations Console cable (for example, COM1).
  • Page 43 6. Click Browse... Navigate to drive:\path\Client Access\Aoc\Inf\ cwbopaoc.inf where drive: is the drive where iSeries Access for Windows is installed. Note: The default install path is: C:\Program Files\Ibm\Client Access\Aoc\Inf\cwbopaoc.inf 7. Click Open, then click OK. 8. Click Next. 9. Select the communications port where the Operations Console cable is attached, and click Next.
  • Page 44 2. If you are currently in the Modems tab of the Phone and Modem Options folder, click Add and then click Next. Otherwise, if you are at the Install New Modem window, click Next. The PC should find the new modem and report its location. 3.
  • Page 45 v You must have your Windows NT Setup CD-ROM available. v You will need to install Remote Access Service before installing Windows NT service pack. To install or configure Remote Access Service: 1. Open the Network folder by doing the following: __ a.
  • Page 46 a. Click Add. b. In the Add RAS Device window, select the modem. c. Click OK. You should be at the Remote Access Setup window. 7. If the Remote Access Setup window has an AS400 Operations Console Connection entry present, a.
  • Page 47 __ j. Click OK. __ k. Click OK again. 11. To complete the setup: a. Click Continue. b. If you get a message that says that the PC does not have a network adapter installed, click c. If you get a message that says that Remote Access Service has been successfully installed, click OK.
  • Page 48 Note: If Incoming Connections does not exist, you have to install it. For more information, see Create and configure incoming connections. 5. Click Incoming Connections. 6. Click the Users tab 7. In the Users allowed to connect field, select the check box next to the user ID for which you want to grant remote access.
  • Page 49 a. In the From field, type the address 192.168.0.5 b. In the To field, type the address 192.168.0.24 c. The Total field shows 20 12. Select the Allow calling computer to specify its own IP address check box. Then, click OK. 13.
  • Page 50 Important: It is assumed the server is powered down. Do not power on the iSeries server until you are instructed to do so. Note: You can also use the following instructions if you are removing one or more cables from your PC, server, or both.
  • Page 51 4. Select Operations Console. Note: If Operations Console did not appear, you need to complete an iSeries Access for Windows selective setup. Click Start —> Programs —> IBM iSeries Access for Windows —> Selective Setup. The configuration wizard and Operations Console window starts. Step through the wizard and enter any required data.

  • Page 52: Manage Operations Console

    Manage Operations Console After you have completed your Operations Console Planning and Set up your connection, you have options available to help you manage your local and remote console connections. These topics help you to successfully complete the tasks that you need to perform when managing your configurations: Manage your console configuration Manage your local and remote console through maintenance tasks.
  • Page 53 1. If your local console is connected to a server, disconnect as follows; otherwise, go to step 2: a. If the local console does not have control, do the following to request control; otherwise, go to step 1) Select the configuration name from the Operations Console window. 2) From the Connection menu, click Request Control.
  • Page 54 Perform the following steps to connect a local console on a network to an iSeries server: 1. Open Operations Console to start the connection: a. Click Start and select Programs. b. Select IBM iSeries Access for Windows. iSeries: iSeries Access for Windows Operations Console...
  • Page 55 c. Click Operations Console. By default, Operations Console does not automatically try to connect a local console on a network to an iSeries server. If you selected Start connection when Operations Console starts in Properties, the local console connects to the iSeries server automatically. The connection status shows Connecting before changing to Connecting Console.
  • Page 56 1. Open Operations Console to start the connection: a. Click Start and select Programs. b. Select IBM iSeries Access for Windows. c. Click Operations Console. By default, Operations Console does not automatically try to connect a local console directly attached to an iSeries server.
  • Page 57 3. If the User Logon window appears, sign on so the operating system at the local console checks whether you are a user with dial-in authority. After you sign on successfully, the connection status shows Connected. Note: If you do not sign on to the remote console connection in approximately a minute, Dial-up Networking ends the connection.
  • Page 58 allowing all Operations Console connections to see where the console is. This is associated with the new console option Allow console to be taken over by another console but the option does not have to be enabled for this behavior to occur. For more information regarding this new function see Take over or recover an Operations Console connection.
  • Page 59 If your local console starts in unattended mode, SERVER appears in the Current User field after you Connect a local console directly attached to the server. Operations Console automatically grants control to the first requester (local console or remote console). Default user (server): SERVER is an identification name that Operations Console assigns when there is no user in control of a server.
  • Page 60 3. If a remote console user has control and you do not want to force control back from the remote console, Send a message to the remote console asking the user to release control. To request control at the local console, after the remote console releases control and control did not return to the local console, do steps 2a on page 53 through 2e on page 53.
  • Page 61 3. If the local user has control, do the following: a. (Optional) Send a message to the local console explaining why you need to have control. Important: It is not necessary to send a message before requesting control. b. From the Connection menu, click Request Control. If the local user grants control to the remote console, the remote control panel becomes functional (if installed and configured at the local console) and the console appears.
  • Page 62 that has iSeries control and a remote console. It illustrates how control is transferred between the local console and the remote console when the remote console requests control. These interactions show the expected behavior from the local console and remote console users: 1.

  • Page 63: Manage Your Multiple Consoles

    On the initial startup of Operations Console you may notice some small changes. The first change is that there is a new drop-down menu item available, Options. v Show Warnings This option can be used to prevent many of the common dialog windows from showing.
  • Page 64 Note: The following topics are valid when the Allow console to be taken over by another console is not enabled. For information relating to console take over and recovery see Take over or recover an Operations Console connection. The following links will explain the more common procedures. Select the link that best describes your scenario.
  • Page 65 disconnect. The next remote would then connect at its assigned time and request control. This assumes that the local console did not have control when the first remote got control. Switching from one console type to another when a console is currently available If you know in advance that you will need a different console type you can use the current console to make the changes for use with a different console on the next IPL or in some cases, the next connection.
  • Page 66 the target console type, and the current state of the system. See Using the 65 + 21 functions for more details. If you are unsure of any function or recovery action contact your service provider for assistance. Take over or recover an Operations Console connection New for V5R3 is a special set of actions that allow an Operations Console to take control from another console device.
  • Page 67 v Since there can be only one Operations Console directly attached device, the takeover function cannot be used. However, any 5250 emulation-based device can be used to recover a loss of the console by changing the console mode. This may require a reallocation of hardware to support the new console mode.
  • Page 68 In order to accomplish a recovery using a different console mode you must set the new console mode before attempting the take over. This means that either the supporting hardware must already be available, including any logical partition tagging, or you have to move supporting hardware, physically or logically, before attempting the recovery.
  • Page 69 Scenarios: The following scenarios will help you understand the take over and recovery options. Scenario: LAN connected devices only with take over enabled Scenario: A normal IPL and dual-connectivity configurations with take over enabled Scenario: Recovery of a console requiring a new console mode setting Scenario: How to recover the console during a D-mode IPL Scenario: LAN connected devices only with take over enabled: This is a description of what happens during an IPL when console take over is enabled and more than one LAN-connected device is available.
  • Page 70 At the point in an IPL when the console device is being determined, it is more or less a race condition if more than one device is connecting at a time. The first device to connect, of the type specified by the console mode setting (LAN in our example), becomes the console and will be presented with the usual console screens.

  • Page 71: Change From One Console Type To Another

    the only valid console after the console mode change. When the network problem is fixed, the LAN connected devices would go directly to the Console Information Status screen and would not be able to take control as the console without changing the console mode back to LAN. Take over is not available when a device is directly connected as the console since only one connection of this type is allowed by the server.
  • Page 72 Change from a local console directly attached to a local console on a network (LAN) Before you begin, ensure that you have satisfied all the Operations Console hardware requirements for the PC and server. To change from an Operations Console with a local console directly attached to a local console on a network (LAN), you must perform steps on the PC and the server: 1.
  • Page 73 Note: If you need to add or move adapters to satisfy the hardware requirements for Operations Console, do this work prior to starting these steps. Do not move or remove the twinaxial adapter, if installed, from its current input and output processor (IOP) at this time. 1.
  • Page 74 e. Press F14 to activate the adapter for use by Operations Console. 14. Press F3 until you return to the DST main menu. The server is now configured for use by Operations Console. If you do not plan to use the local console directly attached configuration as a backup console, do not remove or move its adapter at this time.
  • Page 75 v Change the console from local console on a network (LAN) to a local console directly attached for a logical partition Use this procedure to change the console in a logical partition v Configure the PC to use the new console type when changing the console from a local console on a network (LAN) to a local console directly attached.
  • Page 76 Change the console from local console on a network (LAN) to a local console directly attached for a logical partition: To migrate Operations Console with a local console on a network (LAN) to a local console directly attached, follow these steps on the server using the existing console: Note: If you need to add or move adapters to satisfy the hardware requirements for Operations Console, do this work prior to starting these migration steps.
  • Page 77 Note: If this resource will be used for the service tools server (iSeries Navigator connections) or you plan to use the local console on a network (LAN) as a backup console then you won’t need to do the clear. If either of these choices is true, continue with step 17. 14.
  • Page 78 Once you are satisfied that the new console is working correctly you can proceed with any plans to move or remove any adapter or configurations. To delete the current configuration if you will not be using the cabled connection as a backup console do the following: 1.
  • Page 79 The iSeries system value QAUTOCFG must be set to ON. Use one of the following to verify or set this system value on the iSeries server: v Use the WRKSYSVAL QAUTOCFG OS/400 command. v During a manual IPL, in the IPL Options window, select Y for Set major system options. Then, for Enable automatic configuration, select Y.
  • Page 80 10. Select Work with DST environment. 11. Select System Devices (skip this step if using SST). 12. Select Console. 13. Use one of the following console choices to select the new console type. v If you select Operations Console (direct), option 2, continue with step 14. v If you select Operations Console (LAN), option 3, do the following: a.
  • Page 81 2. Change the console from an Operations Console to a twinaxial console in a logical partition Use these instructions to change the console from an Operations Console to a twinaxial console in a logical partition. 3. Perform optional steps on the PC when changing from an Operations Console to a twinaxial console Use these instructions to configure the PC to use the new console type when changing from Operations Console to a twinaxial console.
  • Page 82 2. Select Work with System Partitions. 3. Select Work with partition configuration. 4. Choose Select Console Resource on the logical partition. 5. Press F9 to Change capability filter. 6. Select Any Console. 7. To select the IOP that will support your intended console, do one of the following: v If the adapter to be used for the intended console is under the same IOP as the previous console’s adapter, the console IOP is already correctly tagged.

  • Page 83: Manage Your Local Console On A Network

    Continue with Perform optional steps on the PC when changing from an Operations console to a twinaxial console. Perform optional steps on the PC when changing from an Operations Console to a twinaxial console: Important: Perform these steps only after you are sure there are no problems with the twinaxial console. If the PC will not be used for Operations Console, follow these steps: 1.
  • Page 84 Deactivate the LAN card from use by Operations Console Use these instructions to deactivate the LAN card from use by Operations Console. Changing network values for Operations Console (LAN) Use these instructions to change the network values for Operations Console (LAN). Considerations for changing the service tools device ID passwords Review these considerations before you change the service tools device ID password: Note: You must unlock the SST option before the option is usable.
  • Page 85 Resynchronize the PC and service tools device ID password When a mismatch occurs in the service tools device ID password between the server and the Operations Console PC, you need to resynchronize the password by performing recovery steps on both the PC and the server.
  • Page 86 4. Press Enter again to confirm the deletion. 5. Using option 1 create a new service tools device ID and assign the password of your choice. If you delete and create a device ID, you will also have to delete and create the connection on the v If you do not have another device to sign on to the system, but do have an unused service tools device ID, do the following on the PC: 1.
  • Page 87 – Word 17 of the SRC D1008065 will contain the the number of function 65s you have done. When it reaches a count of 7 the reset of the service tools device ID password will take place. Word 18 will then be set to 00000000. –...
  • Page 88 c. Wait for the status to show Disconnected. 2. Delete the configuration: a. Select the configuration name (under iSeries Connection) that you want to delete. b. From the Connection menu, click Delete. c. Click Yes to confirm the deletion if prompted. 3.
  • Page 89 Configure a service host name (interface name) iSeries service host name (interface name) is the name that identifies the iSeries service connection on your network that is used for service tools, which includes an Operations Console local console on a network (LAN) configuration.
  • Page 90 a network configuration. Once the LAN card is deactivated you can move it or use it for another purpose. You must also be using a console type other than an Operations Console local console on a network (LAN) or the steps below will cause the console to disconnect. Follow these steps to deactivate the LAN adapter currently associated with an Operations Console local console on a network (LAN): Note: To perform the following procedure using SST, select the option Work with service tools user IDs and Devices everywhere it says select Work with DST environment.
  • Page 91 If you made a change that caused the network IP address or service host name (interface name) to be different for the currently configured connections, this change must be reflected on all PCs that connect to this service host name (interface name). Since you cannot modify the network IP address or service host name (interface name) of an existing connection’s configuration on the client you will have to delete the current connection and recreate a new connection using the new network IP address.

  • Page 92: Common Tasks

    e. Press F11. f. Press F17 to deactivate and reactivate the LAN adapter card. Note: This will cause all LAN connected console PCs to go to Connecting console as a status. Also, if more than one LAN connected console PC is connected, the selection of the next console device is unpredictable.
  • Page 93 Using the OPSCONSOLE native macro Use these instructions only under the direction of support personnel. The native macro is an advanced debug and analysis tool. Using Service Tools Device IDs in System Service Tools (SST) System Service Tools (SST) now provides the ability to make changes to Operations Console related configuration data.
  • Page 94 9. Reference code x6004031 or x6004501 (where x can be any letter) will appear in the Function/Data display for several minutes. Note: For console related work you can begin any tasks at this time. 10. When the system has completed the initial phase of the manual IPL it should show01 B and you have a console.
  • Page 95 If the deactivation is successful, the Function/Data window displays D1008065. See Failure to display D1008065 and D1008066 automatically after calling the function, if the expected reference code did not appear in a few minutes. Using the console service functions (65 + 21) When an unexpected console failure is encountered there may be no other workstations available for recovery or debug.
  • Page 96 Note: When possible, perform an IPL on the system to guarantee all vlogs get created even if the IPL will fail. The intent is that LIC has started the vlog tasks prior to performing the dump of flight recorders. The following is an overview of how this function works: Note: If your system is not in manual mode, and the extended functions are not activated, or both, follow these steps: 1.
  • Page 97 A6nn 500C You executed a second 21 to cause an action, such as setting the console to another value. A6nn 500D You waited too long after entering edit mode to cause an action so you will have to enter edit mode again if you intended to make a change.

  • Page 98: Troubleshoot Operations Console Connections

    7. Page down until you find the OPSCONSOLE option. Then, place a 1 next to the option and press Enter. You should be on the Specify Advanced Analysis Options window. The command should show as OPSCONSOLE. 8. Enter the appropriate option and any required parameters in the Options field. Use the following options based on the function you are running: v Deactivate communications adapter for direct attach console = deactdirect v Activate communications adapter for direct attach console = actdirect...

  • Page 99: Troubleshoot Status Messages

    Troubleshoot authentication problems This topic includes solutions to authentication problems encountered during your Operations Console connection. Troubleshoot emulator problems This topic includes solutions to emulator problems you may encounter during your Operations Console connection. Troubleshoot system reference code (SRC) data This topic includes solutions to SRC data received on your server.
  • Page 100 Status messages when configuration is running normally Status messages that indicate you do not have connection problems. Status messages when you have connection problems Status messages that indicate you have connections problems. Status messages when configuration is running normally The following status messages assist you in identifying whether or not you have connection problems. These status messages indicate that you do not have connection problems: Connecting This appears at the remote console during an initial connection to the local console.

  • Page 101: Troubleshoot Connection Problems

    Connecting remote control panel This appears when the connection fails during the initial connection or stops working after the initial connection. Possibly, the remote control panel cable is disconnected. To find a possible solution, see Troubleshoot connection problems. This status disappears when you solve the problem. Connecting console This is the normal status while the console is making the initial connection to an iSeries server.
  • Page 102 Local console connection problems When setting up your local console you may encounter problems connecting. Failure to connect is defined as problems resulting in the status not going to Connected and the emulator did not start. It is possible that the status will go to Connected and the emulator starts but no console data is present. If this is the case, see Troubleshoot emulator problems.
  • Page 103 e. Use the Up button to select function 26. f. Press the Enter button. 2. Use the Down button to select function 65. 3. Press the Enter button. If the deactivation is successful, the Function/Data window displays D1008065. To activate the communications line on the server, do the following: 1.
  • Page 104 If that does not help and you suspect that there is a possibility that the PC may truly not have the buffered UART, IBM recommends that you slow the connection down between the PC and server. Depending on the operating system, you may have to change the registry, the DUN object, or the phone book entry, or all three.
  • Page 105 Install HyperTerminal Instructions available to install HyperTerminal on your PC. Use HyperTerminal Instructions available for using HyperTerminal. Install HyperTerminal: To install HyperTerminal: 1. Click your path. v Start –> Programs –> Accessories –> HyperTerminal v Start –> Programs –> Accessories –> Communications –>HyperTerminal Note: You want the executable and not one of the predefined connections or the folder.
  • Page 106 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...

  • Page 107: Troubleshoot Authentication Problems

    v If your PC modem is listed as a Standard Modem option in the Modems folder, configure it with a different manufacturer and model. v If you have an original equipment manufacturer (OEM) modem, your OEM modem may not be configured correctly.

  • Page 108: Troubleshoot System Reference Code (Src) Data

    Local console emulator goes to Disconnected state This problem mostly affects a local console on a network. A possible cause is that another user has control of the server. To verify whether your local console has control of the server, do the following in the emulator window: 1.
  • Page 109 A6005001 and B6005001 A console resource (controller) was not found during a manual IPL. A6005004 and B6005004 A console device was not found during a manual IPL. A twinaxial controller was found but may not be used. This is only indicating the presence of a controller. It is not indicating the controller may be defective.
  • Page 110 | | | Hardware error Common error codes: Card position or serial 53001A80,53002AC0 number of adapter Network, cable or the LAN adapter may not be operational. Error code: 00000000 . This error code indicates the adapter reported but has not been initialized yet.

  • Page 111: Troubleshoot Remote Control Panel And Virtual

    Note: You may be able to use the console service functions (65+21) to assist in a recovery or to gather debug data. System reference code A6005082 Possible reasons you received system reference code A6005082: v If the system displays this SRC code, it usually means that a console was found, and then the server lost the console connection.

  • Page 112: Troubleshoot Configuration Wizard Problems

    Unable to use the mode function If you are unable to use the mode function on a remote control panel or virtual control panel, check that the user that authenticated the connection (Service Device Sign-on) has the Partition remote panel key privilege for the partition connected to.
  • Page 113 Local console does not detect console cable These are solutions to problems that occur when the local console does not detect the presence of the Operations Console cable. A status message of Connecting or Unavailable is usually present: v Verify that the cable is properly connected. For more information, see Install Operations Console cables. v For the console, verify that the communications adapter card on the server is properly located.

  • Page 114: Troubleshoot Other Operations Console Problems

    5250, in order to change it. Related information ™ Listed below are the iSeries manuals and IBM Redbooks (in PDF format), Web sites, and Information Center topics that relate to the Operations Console topic. You can view or print any of the PDFs.
  • Page 115 v iSeries Access for Windows Use this information to install and configure iSeries Access for Windows on both the iSeries server and the PC. Installation and configuration is necessary on both the server and the PC. v Control panel Operate the system by directly manipulating the control panel or using APIs in your programs. You can use the control panel to power on or off the system, perform an initial program load (IPL), or determine processor activity.
  • Page 116 iSeries: iSeries Access for Windows Operations Console...

  • Page 117: Appendix. Notices

    Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead.

  • Page 118: Trademarks

    The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us.
  • Page 119 IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the information is detrimental to its interest or, as determined by IBM, the above instructions are not being properly followed.
  • Page 120 iSeries: iSeries Access for Windows Operations Console...
  • Page 122 Printed in USA...

Table of Contents