Page 1 System i Connecting to System i Operations Console Version 5 Release 4...
Page 3 System i Connecting to System i Operations Console Version 5 Release 4...
Page 4 Seventh Edition (February 2006) This edition applies to version 5, release 4, modification 0 of IBM i5/OS (product number 5722–SS1) 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 6 . . 71 Troubleshooting status message . . 97 Configuring the PC to use the new console Status messages when configuration is type . . 73 running normally . . 97 System i: Connecting to System i Operations Console...
Page 7 Status messages when you have connection System reference code A6nn500x . . 105 problems . . 98 System reference code A6005001, A6005004, Troubleshooting connection problems . . 99 and A6005007 . . 105 Local console connection problems . 99 System reference code A6005008 . .
Page 8 System i: Connecting to System i Operations Console...
Page 9: Operations Console
PCs, which facilitates many administrative functions. Operations Console uses 5250 emulation provided by either iSeries Access for Windows or IBM Personal Communications to emulate a console. To emulate a system control panel, Operations Console provides a graphical remote control panel or virtual control panel.
Page 10: Printable Pdfs
The twinaxial console uses a command line interface to access and manage your System i environment, and it does not require the use of a personal computer to act as a console. You access the System i platform through a console screen, a keyboard, and twinaxial cables.
Page 11: Planning Considerations For Operations Console
This topic describes how to migrate data from one system or partition to another system or partition. When performing a data migration, the source system and the target system must have different serial numbers. v Planning for your physical environment Good planning is essential for the successful setup and use of your system.
Page 12: Console Planning Considerations
5250 session can have control of a system at a time. An active console is the command interface to a system through 5250 emulation or IBM Personal Communications that is currently interacting with the system. More than one Operations Console device might have data on the screen but only one is truly active.
Page 13 The following information pertains to console takeover and recovery: In V5R4 and later releases, there is a special set of functions known as console take over and recovery, that allows a LAN-connected Operations Console to take control from another console device. Use the following information to help determine what console devices are best for your work environment and how to deploy these devices to take advantage of the new functions.
Page 14: Planning Considerations For Your Backup Console
Another example of this might be that the IOP has both a 2838 and a 2849 Ethernet adapter reporting to it. They are different adapters but have the same connectivity for the console. System i: Connecting to System i Operations Console...
Page 15 – If the load source storage device fails and the system recovery includes the use of the IBM distribution Licensed Internal Code media instead of a customer backup, and the system is using Operations Console (LAN), you might have to use another console type for the initial portion of the system recovery.
Page 16: Scenarios: Selecting Your Configuration
This scenario discusses a situation in which you might want a single console attached to the system. Your company owns a System i product, and you want to use a PC to manage your system. You need one console directly connected to the system to physically access the console to manage your system.
Page 17: Scenario: A Single Console Directly Attached To The System With Remote Support
This scenario discusses the ability to dial-in to the console from a remote location. Your company owns a System i product, and you want to use a PC to manage your system. You need a console connected to this system, which allows you to manage the console from a remote location. Then you can perform an IPL from home over the weekend or check to see if the job you started has completed.
Page 18: Scenario: Consoles For Multiple Systems Or Partitions
This scenario discusses a situation in which you want to manage multiple systems or partitions. Your company owns a System i product, and you want to use the PC to manage your system. You need to manage multiple systems or partitions from one console. You have a secured network that you can configure your console on.
Page 19: Preparation For Your Network Environment
Console. Related reference “Operations Console hardware requirements” on page 18 You need to meet the PC and System i hardware requirements for an Operations Console configuration. “Planning considerations for your backup console” on page 6 Most system plans include a level of redundancy to allow for the event of hardware failures; however, many people do not consider the console in their plans.
Page 20 “Operations Console hardware requirements” on page 18 You need to meet the PC and System i hardware requirements for an Operations Console configuration. System i: Connecting to System i Operations Console...
Page 21: Security Of Your Operations Console Configuration
Security of your Operations Console configuration Operations Console security consists of service device authentication, user authentication, data privacy, and data integrity. An Operations Console local console directly attached to the server has implicit device authentication, data privacy, and data integrity because of its point-to-point connection. User authentication security is required to sign on to the console display.
Page 22 (DST) and system service tools (SST). They consist of a service tools device ID and a service tools device ID password. The default service tools device ID is QCONSOLE and the default password is QCONSOLE. An Operations Console local console System i: Connecting to System i Operations Console...
Page 23 on a network encrypts and changes the password during each successful connection. You must use the default password to initially set up your system if you use a local console on a network (LAN). Important: The device authentication requires a unique service tools device ID for each PC that is configured with a local console on a network (LAN) connection.
Page 24: Preparation For Your Operations Console And Iseries Navigator Configuration
Preparation for your Operations Console and iSeries Navigator configuration Both iSeries Navigator and Operations Console can be run on a single PC. Depending on how you have Operations Console connected to your system, these network configuration options are available. System i: Connecting to System i Operations Console...
Page 25 Windows desktop. iSeries Navigator makes operation and administration of systems easier and more productive. Operations Console lets you use a local or remote PC to access and control a System i console, a control panel, or both. Operations Console enables connections or console activities across a local area network (LAN), along with enabling directly cabled connections.
Page 26: Verification Of Operations Console Requirements
Before using Operations Console, ensure that you have met all the hardware, software, and cabling requirements for Operations Console. Operations Console hardware requirements: You need to meet the PC and System i hardware requirements for an Operations Console configuration. System i: Connecting to System i Operations Console...
Page 27 Certain types of power management on the PC and in the operating system might cause system reference code (SRC) 0000DDDD to appear in the System i control panel or remote control panel. This SRC data should be cleared when PC activity resumes.
Page 28 Table 3. System i requirements - LAN card location (continued) Model Operations Console (LAN) console Operations Console direct card location connection (asynchronous) location for the cable | | | 800, 810 C06, second C05 | | | C04, second C03, third C11...
Page 29: Operations Console Software Requirements
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.8 (or V5.7 with CSD 1) needs to be installed for the console only. It is not required for remote control panel only configurations.
Page 30: Verification Of Available Communications Port
This scenario discusses the ability to dial-in to the console from a remote location. “Operations Console hardware requirements” on page 18 You need to meet the PC and System i hardware requirements for an Operations Console configuration. “Installing an Operations Console cable” on page 39 You need to install an Operations Console cable when your configurations have a local console that is directly attached to the system or a local console that is directly attached with remote access allowed.
Page 31: Planning Considerations For Your Operations Console Installation Or Upgrade
As above, Operations Console supports serial COM ports 1-9. 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 you can try another adapter.
Page 32: Planning Considerations For Your Control Panel
Planning considerations for your control panel To make a connection to the control panel, you need to configure a remote control panel (RCP) or a virtual control panel (VCP). All IDs that want access need proper authority. System i: Connecting to System i Operations Console...
Page 33: Remote Control Panel
Both RCP and VCP are graphical interfaces to the control panel. The remote control panel allows you to perform most of the control panel functions from a local or a remote location. The virtual control panel allows you to perform most of the control panel functions from a local location only. By default, user-created user IDs will have these permissions.
Page 34: Virtual Control Panel
VCP cannot, for example, be used to turn on a system or a partition. The VCP function can work with the V5R2, or later, version of iSeries Access that communicates to a V5R2, or later, release of the System i product.
Page 35: Installing The Virtual Control Panel
v The use of a virtual control panel at a remote console is not supported. v An alternative for powering on the system at a later time, instead of using a cabled remote control panel, can be provided using the IPL scheduling function in Operational Assistant, available in i5/OS, by pressing the Attention key.
Page 36 1. To remove the remote control panel from the configuration, the connection status must be Disconnected. To disconnect the configuration, follow these steps: System i: Connecting to System i Operations Console...
Page 37 If the PC you are working with is connected to a network, do not use a name that can be found on that network. v When setting up VCP in System i environment, there is no partition 0. 5. If the Service TCP/IP Address field contains a value, you will have to use Back and enter another name.
Page 38: Pc Preparations For Operations Console
You need to complete the Operations Console prerequisite checklist for the configuration that you will be installing on your PC. If you are not sure which configuration you need, see the Planning considerations for Operations Console topic. System i: Connecting to System i Operations Console...
Page 39: Setting Up A Local Console Directly Attached To The Server
Note: If you are working with a printed PDF rather than using the interactive interview, the PDF includes the entire checklist and all of the setup tasks. Select the configuration you will be installing on your PC: Related concepts “Planning considerations for Operations Console” on page 3 Before you begin setting up your Operations Console, determine how to best configure it.
Page 40: Completing Prerequisite Checklist For Windows Xp: Local Console Directly Attached To The Server With Remote Access Allowed
5. Configure a service host name (interface name) on the server. 6. Create service tools device IDs on the server. 7. Configure Operations Console on the PC. Completing prerequisite checklist for Windows XP: Local console on a network: System i: Connecting to System i Operations Console...
Page 41: Setting Up A Remote Console Through Dial-Up Support
Before you use Operations Console, you must install iSeries Access for Windows. During the installation of iSeries Access for Windows, you are going to install a 5250 emulator or IBM Personal Communications V5.8 (V5.7 CSD 1 minimum) and Operations Console support. See the iSeries Access Web site for updated PC requirements.
Page 42: Applying Iseries Access For Windows Service Packs
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.8 or 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 43: Installing Operations Console Connection Modem
7. 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 installation path C:\Program Files\Ibm\Client Access\Aoc\Inf\cwbopaoc.inf). Click Open. 8. Click OK. Operations Console Connection should be listed. 9. Click Next.
Page 44: Installing Operations Console Connection Modem For Windows Xp
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 45: Installing Pc Modem For Windows Xp
6. If you get a message that indicates that you need to restart the PC before you can use the modem, click OK. Then, perform a shutdown and restart your PC. Otherwise, you may be prompted to restart the PC. If that is the case, click Yes or OK to perform the shutdown. Note: If you were not prompted to restart the PC, restart the PC to force a rewrite of changed data.
Page 46: Granting Remote Access For Windows Xp
13. Click Next. 14. Click Finish to save Incoming Connections. Related tasks “Granting remote access for Windows 2000” on page 37 To grant remote access using the Windows 2000 Incoming Connections, follow these steps. System i: Connecting to System i Operations Console...
Page 47: Creating And Configuring Incoming Connections For Windows Xp
Related reference “Granting remote access” on page 37 You need to grant remote access in order for a remote console to have access to the local console. Creating and configuring incoming connections for Windows XP: You need to complete these steps to create and configure incoming connections for Windows 2000. 1.
Page 48 Cabling information is available with instructions and graphics to install your cables for each model. Follow the instructions appropriate to your model. Related reference “Operations Console cable requirements” on page 21 You need to meet these cable requirements for supported models, cables and card locations. System i: Connecting to System i Operations Console...
Page 49: Cabling A Model 830 Or A Model 840 Operations Console
“Planning considerations for your Operations Console installation or upgrade” on page 23 To plan for your Operations Console installation or upgrade, you need to know this information. Cabling a model 830 or a model 840 Operations Console: These diagrams illustrate how to cable a model 830 or model 840 Operations Console. Figure 5.
Page 50: Configuring Operations Console On The Pc
Important: IBM System i and eServer i5 models start counting logical partitions with the number 1 (even if it is the only partition) instead of a 0. iSeries 270 and 8xx models start counting logical partitions with the number 0.
Page 51: Managing Operations Console
Note: The configuration wizard automatically configures the connection to use the console and remote control panel for some configurations. If you do not want to use one of these functions, use the connection’s Properties → Configuration tab to deselect the function you do not want started for this connection.
Page 52: Changing A Local Console
Operations Console. “Releasing control at the remote console” on page 54 Releasing System i control at the remote console allows control to go back to the state that the local console was in when the first remote console requested control.
Page 53: Deleting A Local Console
“System i control” on page 50 Control of your system means having an active console at a PC. Deleting a local console: To delete an existing local console, follow these steps: 1. If your local console is connected to a system, disconnect it as follows; otherwise, go to step 2: a.
Page 54: Connecting To Another System
(if configured). An active console is a command interface to a System i platform (5250 emulation) that is currently interacting with the system. You can use a functional remote control panel to perform most control panel functions (depending on the partition to which you are connected) as if you were at the system.
Page 55: Connecting A Local Console Directly Attached To The System
Connecting a local console directly attached with remote access allowed enables remote consoles to connect to the system. It also allows System i control to be automatically granted to the first requester, or allows you to have control at the local console to handle incoming control requests.
Page 56: Connecting A Remote Console To A Local Console By Modem
2. If you did not select Start connection when Operations Console starts, you need to start the connection to the local console as follows: a. Select the configuration name. b. From the Connection menu, click Connect. System i: Connecting to System i Operations Console...
Page 57: Control Tasks Between Users
5250 emulation. Related reference “System i control” on page 50 Control of your system means having an active console at a PC. “Remote console through dial-up fails to connect to local console” on page 104 Here are the solutions to a problem that occurs when a remote console modem fails to establish a connection with a local console.
Page 58 Connecting a local console directly attached with remote access allowed enables remote consoles to connect to the system. It also allows System i control to be automatically granted to the first requester, or allows you to have control at the local console to handle incoming control requests.
Page 59: Identifying User In Control Of A System
“Releasing control at the remote console” on page 54 Releasing System i control at the remote console allows control to go back to the state that the local console was in when the first remote console requested control. “Sending a message to a controlling local console or remote console” on page 55 While using Operations Console, you might need to communicate with the user who has control.
Page 60: Displaying The Remote Control Panel In Read-Only Mode
“Identifying user in control of a system” on page 51 Identifying the user who has System i control at a given time can help you determine how to proceed when you want to obtain control. This information applies to a local console directly attached with remote support and a remote console.
Page 61: Sending A Message To A Controlling Remote Console
Sending a message to a controlling remote console: When using Operations Console, you might need to communicate with the user who has System i control. Operations Console allows a local console and a remote console to exchange messages when connected.
Page 62: Requesting Control At The Remote Console
“Identifying user in control of a system” on page 51 Identifying the user who has System i control at a given time can help you determine how to proceed when you want to obtain control. This information applies to a local console directly attached with remote support and a remote console.
Page 63: Sending A Message To A Controlling Local Console Or Remote Console
Releasing System i control at the remote console allows control to go back to the state that the local console was in when the first remote console requested control. For example, if the local console granted control to the first requesting remote console, releasing control at the remote console allows the local console to regain control.
Page 64: Using The Properties Page
This example shows interactions between a local console directly attached with remote access allowed that has System i 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.
Page 65: Customizing The Operations Console Window
Note: An initial local console on a network configuration will configure both the console and remote control panel. This is where you would turn off one of the functions if you did not want to use it. The Device ID tab has been changed to allow a single button to reset the service tools device ID password on the PC.
Page 66: Management Of Multiple Consoles
1. Select the connection name you want to disconnect. 2. Click Connection → Disconnect. v Disconnect the emulator session. To disconnect the emulator, follow these steps: 1. In the emulator window, click Communication. 2. Select Disconnect. System i: Connecting to System i Operations Console...
Page 67: Multiple Remote Consoles Through Dial-Up Support Connecting To The Same Local Console Directly Attached To The System
If no device is acting as the console the next time a connection is made, either through Operations Console or the emulator, this PC will become the console. It is up to the users to determine whether or not this method is the correct way to manage console activities. Multiple remote consoles through dial-up support connecting to the same local console directly attached to the system In this environment, only one remote console is allowed to connect to the local console at a time.
Page 68: Switching From One Console Type To Another When The Current Console Is Not Operational
Disconnected. This action allows the job at the console to be ″transferred″ to another device without causing loss of data. When the console option for takeover is enabled, the system also has enhanced recoverability from loss of the console. System i: Connecting to System i Operations Console...
Page 69: Takeover Details
The recovery action is accomplished by suspending the data stream to a console that loses a connection, or is being taken over, saving further data and then sending that data to the next device to become the console, even if the device is the same former console. Recoverability is essentially just taking over the console from the same or different qualified device regardless of what the former console was doing.
Page 70: Recovery Details
Related reference “Takeover details” on page 61 Here is the additional information about the console takeover function. System i: Connecting to System i Operations Console...
Page 71: Enabling Console Takeover
“Using the console service functions (65+21)” on page 92 Console service functions (65+21) are the emergency console recovery functions. Enabling console takeover: Before you can enable console takeover, you must have the Take over console privilege. Use the procedure following to grant Take over console privilege and then continue with the next procedure to enable console takeover.
Page 72 66 however, it would be taken directly to the new Console Information Status screen where the user can see data related to the System i: Connecting to System i Operations Console...
Page 73 current console. The field Take over the console will show NO since it is not of the correct type (the console type is set to LAN). At LAN2, a user with the user privilege of take over console signs on. This user will now be presented the same Console Information Status screen but the Take over the console field will show a YES indicating that take over is possible.
Page 74: Changing From One Console Type To Another
(LAN), you must change settings on both the PC and the system. Before you begin, ensure that you have satisfied all the Operations Console hardware requirements for the PC and system. Related reference System i: Connecting to System i Operations Console...
Page 75: Changing The Console From A Local Console Directly Attached To A Local Console On A Network (Lan) In A Non-Partitioned Or Primary Partitioned System
“Operations Console hardware requirements” on page 18 You need to meet the PC and System i hardware requirements for an Operations Console configuration. Changing the console from a local console directly attached to a local console on a network (LAN) in a...
Page 76 Press F11 to configure the adapter. c. Enter the appropriate network data. d. Press F7 to store the data. e. Press F14 to activate the adapter for use by Operations Console. System i: Connecting to System i Operations Console...
Page 77: Configuring The Pc To Use The New Console Type When Changing From A Local Console Directly Attached To A Local Console On A Network
(LAN), you must configure the PC to use the new console type. Related reference “Operations Console hardware requirements” on page 18 You need to meet the PC and System i hardware requirements for an Operations Console configuration. Related information...
Page 78: Changing From A Local Console On A Network (Lan) To A Local Console Directly Attached
When you get your new console choice working, you can remove the LAN adapter from the system or move it to another location. System i: Connecting to System i Operations Console...
Page 79: Changing The Console From Local Console On A Network (Lan) To A Local Console Directly Attached For A Logical Partition
The system value QAUTOCFG must be set to on. Use one of the following methods to verify or set this system value: v Use the WRKSYSVAL QAUTOCFG 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 “Configuring the PC to use the new console type” on page 73 After changing from a local console on a network to a local console directly attached, you must configure the PC to use the new console type. Related information Access service tools System i: Connecting to System i Operations Console...
Page 81: Configuring The Pc To Use The New Console Type
Related reference “Operations Console hardware requirements” on page 18 You need to meet the PC and System i hardware requirements for an Operations Console configuration. Changing the console from a twinaxial console to an Operations Console in a non-partitioned or...
Page 82: Changing The Console From A Twinaxial Console To An Operations Console In A Logical Partition
Related reference “Operations Console hardware requirements” on page 18 You need to meet the PC and System i hardware requirements for an Operations Console configuration. “Configuring the PC to use the new console type after changing from a twinaxial console to an Operations Console”...
Page 83 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. Go to step 8. v If the adapter to be used for intended console is under a different IOP than the currently configured console, place a 1 in front of the IOP to select it as the console IOP.
Page 84: Configuring The Pc To Use The New Console Type After Changing From A Twinaxial Console To An Operations Console
Related reference “Operations Console hardware requirements” on page 18 You need to meet the PC and System i hardware requirements for an Operations Console configuration. “Configuring the PC to use the new console type after changing from a twinaxial console to an Operations Console”...
Page 85: Changing The Console From An Operations Console To A Twinaxial Console In A Logical Partition
5. If you are currently using Operations Console local console on a network (LAN), select Operations Console (LAN) and follow these steps to deallocate the network adapter: 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.
Page 86 During a manual IPL, in the IPL Options window, select Y for Set major system options. Then, for Enable automatic configuration, select Y. Continue with Performing optional steps on the PC when changing from an Operations console to a twinaxial console. Related tasks System i: Connecting to System i Operations Console...
Page 87: Performing Optional Steps On The Pc When Changing From An Operations Console To A Twinaxial Console
“Performing optional steps on the PC when changing from an Operations Console to a twinaxial console” If the PC will not be used for Operations Console, follow these steps: Related information Access service tools Performing optional steps on the PC when changing from an Operations Console to a twinaxial console: If the PC will not be used for Operations Console, follow these steps: Important: Perform these steps only after you are sure there are no problems with the twinaxial console.
Page 88: Changing The Service Tools Device Id Password On The Pc And System
To use the connection properties to change the access password, follow these steps: 1. Select the connection name for which you will be changing the access password. 2. Click Connection → Properties. System i: Connecting to System i Operations Console...
Page 89: Resynchronizing The Pc And Service Tools Device Id Password
3. Select the Access Password tab. 4. For Current Password enter what you currently use for the access password. 5. Enter the new password into the New Password and Confirm password fields, and then click OK. Resynchronizing the PC and service tools device ID password When a mismatch occurs in the service tools device ID password between the system and the Operations Console PC, you need to resynchronize the password by performing recovery steps on both the PC and the system.
Page 90 Each word is 8 characters but 4 words are displayed at a time for words 12 through 19. For example, requesting word 12 will provide you: word__12word__13 word__14word__15 Requesting word 13 will provide you: word__16word__17 word__18word__19 The single-row display control panel and the remote control panel presents data like this: System i: Connecting to System i Operations Console...
Page 91: Resetting The Service Tools Device Id Password On The Pc
xxxxxxxx Each word is 8 characters only and displayed individually. If you want word 17, you have to request function 17. The data provided in the words can be accessed using many different methods. Important: In order to know where you are in the process the following information is provided: v Word 17 of the SRC D1008065 will contain the the number of function 65s you have done.
Page 92: Creating Service Tools Device Ids On The System
ID attributes you can press F5 (change attributes on the ″Create Service Tools Device ID″ screen or enter a 7 in front of the device ID on the ″Work with Service Tools Device IDs″ screen. System i: Connecting to System i Operations Console...
Page 93: Configuring A Service Host Name (Interface Name)
Configuring a service host name (interface name) The service host name (interface name) is the name that identifies the System i service connection on your network that is used for service tools, which includes an Operations Console local console on a network (LAN) configuration.
Page 94: Deallocating Or Moving The Lan Adapter Card From Use By Operations Console
When using the following procedure, you can either verify or create the configuration for the System i service connection. You can find the service host name (interface name) by going into Dedicated Service Tools (DST), or System Service Tools (SST) on the partition that you are configuring and use the Configure Service Tools Adapter display.
Page 95: Changing Network Values For Operations Console (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. 1. Access Dedicated Service Tools (DST) or System Service Tools (SST). 2. Select Work with DST environment. 3.
Page 96 Start an attended IPL on the system. b. Continue with completing the PC changes. v Perform the manual intervention Perform these steps from the DST or SST main menu. System i: Connecting to System i Operations Console...
Page 97: Completing The Pc Changes
Note: a. 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 and skip the step Select System Devices. a. Select Work with DST environment. b.
Page 98: Common Tasks
Client Access folder, navigate to the Emulator folder, followed by the Private folder. Note: If you are using IBM Personal Communications the default path would be: Documents and Settings → User Name → Application Data → IBM → Personal Communications 4.
Page 99: Activating The Asynchronous Communications Line On The System
8. Press Power on the control panel. The system takes approximately 10 to 45 minutes to power on and progress through an IPL far enough to continue with these instructions. You should see that the data changes in the Function/Data display. The last step of the IPL may take up to 30 minutes to complete or the Attention light may turn on.
Page 100: Deactivating The Asynchronous Communications Line On The System
If a console device is available, you should use that console to perform any console service functions, if possible. If a console device is not available, then perform these functions only after a failing system reference code (SRC) has been displayed. This SRC typically is A6005008. System i: Connecting to System i Operations Console...
Page 101 The following functions are available using the console service functions (65+21): v Change the console type value (01-03) You can use the console service functions (65+21) to change the console type from its current value to another. For example, assume that you ordered your system with Operations Console LAN, but you are having trouble getting it to work.
Page 102 Note: You have 45 seconds between a 65 and the 21 to start display mode or edit mode changes. If the time between these codes exceeds this limit the 21 will become a force DST console request. An example of a console change would be: System i: Connecting to System i Operations Console...
Page 103: Using The Opsconsole Macro
(SST). Note: Improper use of IBM-supplied macros could result in a change requiring a complete system reload. It is strongly suggested that you use these IBM-supplied macros only at the request of a support representative. To use the Operations Console IBM-supplied macro support, follow these steps: 1.
Page 104: Using Service Tools Device Ids In System Service Tools
Troubleshooting Operations Console connection Problems can occur during an Operations Console session. The following topics are some solutions to common problems that are encountered during your initial setup and management of your configurations. System i: Connecting to System i Operations Console...
Page 105: Troubleshooting Status Message
Settings dialog window Operations Console has a built-in, hot-key-activated, settings dialog window that has special options used to help troubleshoot problems. The Settings window is activated by pressing and holding the Alt and shift keys then, press the s key before releasing all three keys (ALT+Shift+s). The options to split the log files can be very helpful to your service provider, especially if you have many connection configurations.
Page 106: Status Messages When You Have Connection Problems
Console unavailable or Remote control panel unavailable This appears when there is a problem during an initial connection to a system, and you choose System i: Connecting to System i Operations Console...
Page 107: Troubleshooting Connection Problems
not to retry the connection for the console and remote control panel. It indicates that there is a problem with the console connection, possibly because the Operations Console connection modem is not available or the console cable is disconnected. Operations Console connection modem is not a physical modem but a logical device driver that comes with Operations Console and allows a local console to connect to a system.
Page 108: Network Connection Errors
These are solutions to problems that prevent the local console from connecting to the system or prevent the remote console from connecting to a local console due to improper hardware or software configurations. System i: Connecting to System i Operations Console...
Page 109: Console Fails To Connect And Port Detection Fails
v Verify that the resources of the PC are free of address or interrupt request (IRQ) conflicts. Operations Console uses addresses in the range of 192.168.0.0 to 192.168.0.255. If you run any software that makes your PC SOCKS-enabled, check your SOCKS configuration and make sure that the entry is: Direct 192.168.0.0 255.255.255.0...
Page 110: Using Hyperterminal To Validate Connectivity Between Client And The System
Start → Programs → Accessories → HypertTerminal v Start → Programs → Accessories → Communications → HypertTerminal 2. In the Connect To window, enter a name, select an icon, and then click OK. System i: Connecting to System i Operations Console...
Page 111 3. A new Connect To window will appear. Click the little arrow at the end of line for Connect using: Select the communications port being used for the console. It might also be listed as direct to COMn (where n is 1 to 4). Click OK. 5.
Page 112: Remote Console Connection Problems
When setting up your initial connection you may encounter emulator problems. If the emulator window did not start and the connection status is not Connected, refer to the Local console connection problems topic. System i: Connecting to System i Operations Console...
Page 113: Pc5250 Window Does Not Display User Data
Related reference “Local console connection problems” on page 99 When setting up your local console, you might encounter problems connecting. Failure to connect is defined as problems resulting in the status not going to Connected and the emulator did not start. PC5250 window does not display user data This can be caused by a non-buffered UART for the serial connection in the PC.
Page 114: System Reference Code A6005008
This is not considered an error, at this time. The adapter should be activated shortly. For other error codes contact your service provider. System i: Connecting to System i Operations Console...
Page 115: System Reference Code A9002000
If Word 13 value is: Failure Word 14 means: Word 15 means: BOOTP status: If attempts Attempts Card position or serial are zero, then BOOTP is number of adapter ready, when called. If attempts have a value, then the PC did not respond The system’s LAN IP address Card position or serial...
Page 116: System Reference Code A6005082
If you are connecting via a network, another reason the remote control panel fails to start may be that either the user ID or service tools device ID being used does not have permission to use the remote control panel. Related reference System i: Connecting to System i Operations Console...
Page 117: Unable To Use The Mode Function
“Installing an Operations Console cable” on page 39 You need to install an Operations Console cable when your configurations have a local console that is directly attached to the system or a local console that is directly attached with remote access allowed. Unable to use the mode function When you are unable to use the mode function, you should verify that the authenticated connection has the correct privileges to use the mode function on a remote control panel.
Page 118: Local Console Does Not Detect Console Cable
Note: If the new console fails to work in i5/OS you may need to use another workstation to manually delete the controller and device description associated with the old console device. System requests do not work Here are the solutions for when system requests do not work. System i: Connecting to System i Operations Console...
Page 119: Unable To Sign On Because Of A Lost Or Expired Password Or Disabled User Id
When using Operations Console, SYSREQ corresponds to Shift+ESC and is defined as the default for PC5250 emulation. Most keyboards have a Print Screen key, also labeled as SYSREQ and would be activated by using that key with the Ctrl key, however Windows reserves this key for the Print Screen function. You must remap the keyboard by using the operating system, not PC5250, in order to change it.
Page 120 System i: Connecting to System i Operations Console...
Page 121: 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 122: Trademarks
Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows: © (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rights reserved.
Page 123: Terms And Conditions
IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the publications is detrimental to its interest or, as determined by IBM, the above instructions are not being properly followed.
Page 124 System i: Connecting to System i Operations Console...
Page 126 Printed in USA...

IBM System i Manual

Operations Console

Appendix. Notices

Quick Links

Troubleshooting

Need help?

Questions and answers

Related Manuals for IBM System i

Summary of Contents for IBM System i

Table of Contents