System i Connecting to System i Operations Console Version 6 Release 1...
System i Connecting to System i Operations Console Version 6 Release 1...
“Notices for software topics,” on page 105 and the IBM Systems Safety Information manual, G229-9054. This edition applies to version 6, release 1, modification 0 of IBM i5/OS (product number 5761–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.
(IT) equipment to responsibly recycle their equipment when it is no longer needed. IBM offers a variety of product return programs and services in several countries to assist equipment owners in recycling their IT products. Information on IBM product recycling offerings can be found on IBM’s Internet site at http://www.ibm.com/ibm/environment/...
Customer participation is important to minimize any potential effects of batteries and accumulators on the environment and human health due to the potential presence of hazardous substances. For proper collection and treatment, contact your local IBM representative.
System i: Connecting to System i Operations Console...
Changing the console from a local console Configuring a service host name (interface directly attached to a local console on a name) . . 75 network (LAN) in a nonpartitioned or Deallocating or moving the LAN adapter card primary partitioned system . .
Old network data interfering with Programming interface information . . 106 reconfiguration of network connectivity . 101 Trademarks . . 107 Troubleshooting other Operations Console Terms and conditions. . 107 problems . . 101 Operations Console remains in QCTL . .
System i: Connecting to System i Operations Console...
PCs, which facilitates many administrative functions. Operations Console uses 5250 emulation provided by either System i 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.
In PDF files, you might see revision bars (|) in the left margin of new and changed information. To find other information about what’s new or changed this release, see the Memo to users. PDF file for Operations Console You can view and print a PDF file of this information. To view or download the PDF version of this document, select Operations Console (1,105 KB).
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 actually active.
following information to help determine what console devices are best for your work environment and how to deploy these devices to take advantage of these functions. v Takeover is the process used for a LAN-connected console device to take control from the current console device.
intended purposes. It is recommended that you install only one console-capable adapter that matches your configurations for a single IOP. This situation also will affect asynchronous adapters used by a local console directly attached to the system. v The term alternate console is referring to a twinaxial console type located in another IOP tagged as the alternate console.
– 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.
You need to meet the PC and System i hardware requirements for an Operations Console configuration. Note: This topic covers only models 8xx and earlier. For models 5xx, go to the Operations Console hardware requirements topic in the IBM Systems Hardware Information Center. Table 1. PC requirements - processor and memory...
Important: IBM System i5 and eServer i5 models start counting logical partitions from 1 (even if it is the only partition) instead of 0. iSeries 8xx models start counting logical partitions from 0. For the console to connect properly, your logical partitions must also begin numbering at 1 instead of 0.
Windows Vista for a local console directly attached. PC5250 or IBM Personal Communications V5.9 (V5.7 with CICS system definition data set (CSD) 1 minimum) needs to be installed for the console only. It is not required for configurations that are used only for remote control panel.
the range of 192.168.0.0 to 192.168.0.255. Incorrect routing causes Operations Console to fail. Check your SOCKS configuration and make sure that the entry is: Direct 192.168.0.0 255.255.255.0 Data encryption for a local console on a network To use a local console on a network, you are strongly encouraged to install cryptographic products. This support may be a separate product or it may be available from another source.
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.
| | | Model Operations Console - Asynchronous adapter locations 800, 810 870, 890 When you receive the i5/OS release upgrade, all of the user IDs included with the operating system are expired, except for 11111111 (eight 1’s). For all upgrades and installations, you need to establish a connection between the System i platform and Operations Console using the service tools user ID of 11111111.
need to deallocate the LAN card if you are not planning on using an Operations Console local console on a network configuration or the service tools server. Related reference “Installing an Operations Console cable” on page 32 You need to install an Operations Console cable when your configurations have a local console that is directly attached to the system.
Starting with i5/OS V6R1, Operations Console can detect systems that are capable of being configured with less user interaction. If this condition is detected, the PC and system attempt to exchange information for a new configuration. If the information exchange is successful, the system uses this information during the setup of the connection at the PC.
The following list gives you an overview of your Operations Console LAN security as shown in Figure 1. 1. A user enters the correct password. 2. Operations Console sends the service tools device ID (QCONSOLE) and its encrypted password to the system.
that is directly attached to the system is a physical connection similar to a twinaxial console. The serial cable you use for Operations Console using a direct connection can be physically secured similar to a twinaxial connection to control access to the physical console device. Operations Console local console on a network uses a version of Secure Sockets Layer (SSL) that supports device and user authentication, but without using certificates.
encryption possible, depending on the cryptographic products installed on the system and the PC running Operations Console. Data encryption can only occur if a cryptographic product is installed on the system. Data integrity This security provides confidence that the console data has not changed en route to the recipient. An Operations Console local console that is directly attached to the system has the same data integrity as a twinaxial connection.
Protection tips When using an Operations Console local console on a network, it is suggested that you complete the following tasks: 1. If you changed the value of Autocreate service tools device IDs on the system to 0, do the following: Create an additional service tools device ID for each PC that will be used as a console with console and control panel attributes.
v If the PC uses Operation Console as a local console directly attached to the system, a network connection for System i Navigator is required. To complete the System i connection, the system needs a network adapter and a configured i5/OS line description (LIND). Operations Console is connected over a serial cable attached to an asynchronous card on the System i platform.
Related information System i Navigator Scenarios: Selecting your configuration These scenarios help you decide which configuration works best in your environment. Use the following scenarios to help assist you in choosing your Operations Console configuration. Keep in mind that these scenarios apply only to nonpartitioned systems. Scenario: A single console directly attached to the system without remote support: This scenario discusses a situation in which you might want a single console attached to the system.
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.
Planning considerations for your control panel To make a connection to the control panel, you need to configure a remote control panel or a virtual control panel. All IDs that want access need proper authority. Both remote control panel and virtual control panel 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 function can work with the System i Access for Windows V6R1, or later, IBM eServer iSeries Access for Windows V5R4 or V5R3, or iSeries Access for Windows V5R2 that communicates with a System i product running i5/OS V5R3, or ®...
For example, you have connected a PC named DIRECT to SERVER1 using a direct cable and you want to configure a VCP. If no Operations Console (LAN) configuration exists to this system then the service tools device ID QCONSOLE has not been used. Therefore, you can specify QCONSOLE when you configure the VCP.
“Limitations of the virtual control panel” on page 23 Before you install and use a virtual control panel, consider these features and limitations. Creating a service tools device ID using an existing console: About this task The virtual control panel (VCP) requires an available, unused service tools device ID. By default, this should not require any intervention from the user and no longer has any bearing on the console type.
4. You only have to verify or set the privilege for the Partition remote panel key entry, which would be the partition currently being used. Place a 2 on the line for the partition, and press Enter to grant permission to the mode functions. Note: Systems with a keystick require the keystick to be inserted before the user is eligible to use the mode button.
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. Check the key IP Address. Use the IP address reported on your PC to validate the VCP address. 6. Enter the value of 0.0.0.0 in the Service gateway address 1 field. You are not required to enter anything in the Service gateway address 2 field.
Completing the setup prerequisite checklist 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.
Select the operating system on which you are installing Operations Console on: Completing prerequisite checklist for Windows 2000: Local console on a network: You need to complete this checklist to set up a local console on a network on Windows 2000. 1.
SK3T-4098 to install it: 1. Insert the System i Access for Windows DVD into the DVD drive. 2. Select the System i Access for Windows option to start the installation. Wait until the IBM System i Access for Windows window appears.
Then, go to step 8. If you do not know the path, continue with step 7. 7. Click Browse. Navigate to drive:\path\Client Access\Aoc\Inf\cwbopaoc.inf, where drive is the drive where System i Access for Windows is installed. Note: The default installation path is C:\Program Files\Ibm\Client Access\Aoc\Inf\cwbopaoc.inf). Operations Console...
6. Click Browse. Navigate to drive:\path\Client Access\Aoc\Inf\cwbopaoc.inf, where drive is the drive where System i 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.
v During a manual IPL, in the IPL Options window, for Set major system options, select Y. Then for Enable automatic configuration, select Y. DANGER Electrical voltage and current from power, telephone, and communication cables are hazardous. To avoid a shock hazard: v Do not connect or disconnect any cables or perform installation, maintenance, or reconfiguration of this product during an electrical storm.
2. If you are using Windows XP or an earlier Windows operation system, select Programs. If you are using Windows Vista, select All Programs. 3. Select IBM System i Access for Windows. It is assumed that the system is powered on and is in the process of or has completed an IPL.
4. Select Operations Console. If Operations Console does not appear, you need to complete an IBM System i Access for Windows selective setup. Click Start → Programs → IBM System i Access for Windows → Selective Setup.
v Manually assign the name along with the network configuration using the current console or another workstation. v Let the PC assign the name and IP information. Click Next to allow the system to search for the system on the network. If the PC receives information back from the network or the target service interface, the Service TCP/IP Address shows the IP address returned.
Configuring a local console directly attached to the system: To create a new local console that is directly attached to the system, follow these steps. 1. Click Start → Programs → IBM System i Access for Windows → Operations Console to start Operations Console.
1. Open Operations Console to start the connection. a. Click Start and select Programs. b. Select IBM System i Access for Windows. c. Click Operations Console. By default, Operations Console does not automatically try to connect a local console that is directly attached to a system.
“Troubleshooting authentication problems” on page 94 When setting up your initial connection, you might encounter authentication problems. “Troubleshooting emulator problems” on page 94 When setting up your initial connection you may encounter emulator problems. “Troubleshooting status message” on page 87 If you encounter connection problems when connecting a console, Operations Console provides status messages to assist you in troubleshooting the connections.
“Failure to display D1008065 and D1008066 automatically after calling the function” on page 98 When working with models that have a double row for the Function/Data display portion of the control panel, the control panel might not automatically display the resulting system reference code (SRC).
Benefits of these functions include convenience and redundancy. Console-capable devices can be placed around a site, or multiple sites, allowing users to move around and gain control of the system from any of these devices. Whatever the previous console’s activity was, the new console is at the exact same place, even during the process of restarting the system or installing the i5/OS operating system.
Recovery details Here is the additional information about the console recovery function. v The recovery of the console using a device with the same console connectivity is directly tied to the take over option. If you do not want take over capability but do want recovery from loss of the console, you must still enable the take over option.
About this task Use the procedure following to grant Take over console privilege and then continue with the next procedure to enable console takeover. To add the Take over console privilege to a user, perform the following steps: Note: To perform any of the following procedures 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.
LAN3 will show a special DST signon screen with a new line of data stating ATTENTION: This device can become the console. The rest of the window will be the same as any other DST signon window. 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 and the take over the console field will show a YES indicating that takeover is possible.
At this point only one device has met all the conditions for a console take over. At the bottom of the screen is F10 = Take over console connection. Pressing F10 will present the user with the Take over Console Connection From Another User screen. This is a confirmation screen that gives the user a last chance to cancel the take over.
The proper asynchronous communications adapter is available without further configuration changes, so you can use the console service functions (65+21) to change the console type. This automatically starts the communications adapter associated with the local console directly attached to the system. If you want to use the PC that you were using for the network-attached console, you simply disconnect the network configuration and create (or use a previously created configuration) a local console directly attached to the system configuration.
“Deleting a console configuration” You might need to delete an existing local console to meet your specific needs while using Operations Console. You must be a member of the Administrators group to delete a console. Changing a local console: About this task To change an existing local console, follow these steps: 1.
c. Wait until the connection status shows Disconnected at the local console. 2. Select the configuration name from the Operations Console window. 3. From the Connection menu, click Delete. 4. Click Yes to confirm the deletion. Windows 2000/XP users: About this task You may need to delete the network object each time you delete a configuration entry in Operations Console.
An IP address may be supplied for the console when using a directly attached local console with or without remote support. This is to provide the user with a convenient method when the default address is already in use on the PC. Note: An initial local console on a network configuration is configured for only the console.
If you are familiar with the older releases of Operations Console, you might have used the second button to change a configuration. The second button takes you to the Properties page of the selected configuration. All changes to the configuration of Operations Console are made through the Properties page.
1. In the emulator window, click Communication. 2. Select Disconnect. 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 you to determine whether or not this method is the correct way to manage console activities.
v Use the appropriate native macro from another workstation. Note: Any hardware allocations or configurations will have to be accomplished before connecting with another connectivity. For example, if you are using a shared IOP in an LPAR environment you can deallocate and allocate the resource from one partition to another, if your hardware supports this method.
“Operations Console hardware requirements” on page 7 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 nonpartitioned or primary partitioned system: To change from an Operations Console with local console directly attached to a local console on a network (LAN), follow these steps on the system, using the existing console.
To change from an Operations Console with a local console directly attached to a local console on a network (LAN), follow these steps on the system using the existing console. About this task 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.
d. Press F7 to store the data. e. Press F14 to activate the adapter for use by Operations Console. 14. Press F3 until you return to the DST main menu. Results The system is now configured for use by Operations Console local console on a network when an action is taken to search for a new console.
DANGER Electrical voltage and current from power, telephone, and communication cables are hazardous. To avoid a shock hazard: v Do not connect or disconnect any cables or perform installation, maintenance, or reconfiguration of this product during an electrical storm. v Connect all power cords to a properly wired and grounded electrical outlet. Ensure outlet supplies proper voltage and phase rotation according to the system rating plate.
To migrate an Operations Console local console on a network (LAN) to a local console that is directly attached, follow these steps on the system by using the existing console. 1. Access Dedicated Service Tools (DST) or System Service Tools (SST). You must unlock the SST option ″Service tools device IDs″...
Changing 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 that is directly attached, follow these steps on the system by using the existing console. About this task 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.
Note: If this resource will be used for the service tools server (System i Connections) or you plan to use the local console on a network (LAN) as a backup console, you do not need to do the clear operation. If either of these choices is true, continue with step 17. 14.
About this task DANGER Electrical voltage and current from power, telephone, and communication cables are hazardous. To avoid a shock hazard: v Do not connect or disconnect any cables or perform installation, maintenance, or reconfiguration of this product during an electrical storm. v Connect all power cords to a properly wired and grounded electrical outlet.
b. From the Connection menu, click Delete. c. Click Yes to confirm the deletion. Related reference “Setting up a local console directly attached to the system” on page 28 You need to complete the unique setup prerequisites checklist based on the configuration and the operating system you are using.
v During a manual IPL, in the IPL Options window, select Y for Set major system options. Then, for Enable automatic configuration, select Y. Related reference “Operations Console hardware requirements” on page 7 You need to meet the PC and System i hardware requirements for an Operations Console configuration.
d. To tag the console IOP for ECS, enter a 1 in front of the IOP to be tagged for ECS. Note: If you will be using Operation Console as the intended console you should now see both a < and a + associated with the console IOP.
It is preferred that you perform an initial program load (IPL) to ensure there are no errors. Then, at a later time, remove or move any hardware you planned for. It is preferred that you turn off the system when removing adapter cards or cables. 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.
If you do not plan to use the local console directly attached configuration as a backup console, do not remove or move it or its adapter at this time. You may need it to debug a problem. The system value QAUTOCFG must be set to on. Use one of the following to verify or set this system value on the system: v Use the WRKSYSVAL QAUTOCFG command.
10. Select Work with DST environment. 11. Select System Devices (skip this step if using SST). 12. Select Select Console. 13. If you are currently using Operations Console local console on a network (LAN), select Operations Console local console on a network (LAN) and follow these steps to deallocate the network adapter: Note: If this resource will be used for the service tools server (System i Connections) or you plan to use the local console on a network (LAN) as a backup console then you do not need to do the clear operation.
a. Select the configuration name (under System i Connection). This is the name that Operations Console uses to refer to a specific system. b. From the Connection menu, click Disconnect. The connection status shows Disconnecting. c. Wait for the status to show Disconnected. 2.
you need not remember to increase the value if you try to add an additional connection. These service tools device IDs are listed in the Work with Service Tools Device IDs window so you can keep track of how many are created. However, the device ID QCONSOLE is listed and can be used normally. For example, if you create a service tools device ID with a name of QCONSOLE02, when the third connection is established to use the autocreated device IDs, the ID is given out as if it were created automatically.
Considerations for changing the service tools device ID passwords You need to review these considerations before you reset the service tools device ID password. By default, the system and PC automatically maintain service tools device IDs. If you elect to set the option Autocreate service tools device IDs to 0, then you must manually manage these device IDs.
Related reference “Considerations for changing the service tools device ID passwords” on page 69 You need to review these considerations before you reset the service tools device ID password. “Resynchronizing the PC and service tools device ID password” By default, the system creates and maintains the service tools device ID and its password. You should not have to manually resynchronize the password.
v Using an Operations Console local console that is directly attached to the system (if an Operations Console cable is available). v Using a twinaxial-attached console. v Use the control panel or remote control panel to reset QCONSOLE. Related tasks “Creating service tools device IDs on the system”...
Using unused service tools device ID: About this task If you do not have another device (PC or other terminal) to sign on to the system, but do have an unused service tools device ID, do the following on the PC. 1.
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.
About this task If the password is reset on the system, the next connection made by the client automatically tries the reset password if using the current value fails. If successful, the newly generated password is saved for the next connection. If you suspect that the automatic process failed and you want to manually reset the password, complete one of the tasks described in the subtopics.
2. Select Work with DST environment. 3. Select Service tools device IDs. 4. Use option 1 to create a new service tools device ID and enter the new service tools device ID name in the first blank name field. Press Enter. 5.
Regardless of which method you use to implement the configuration data, the actual name and associated address used for the service host name depends on the network environment in which the system will be placed. The implementation method has no bearing on whether the configured connection is the first connection.
“Preparation for your network environment” on page 13 To prepare for your network environment, you need to identify and comply with the minimum network configuration required to set up an Operations Console local console on a network (LAN) configuration. Related information Service tools user IDs and passwords Access service tools Deallocating or moving the LAN adapter card from use by Operations Console...
“Planning considerations for your Operations Console installation or upgrade” on page 11 To plan for your Operations Console installation or upgrade, you need to know this information. “Changing from one console type to another” on page 52 Depending on how your console connection is set up, you can change to a different console type. Related information Access service tools Changing network values for Operations Console (LAN)
e. Press F3 until the DST main menu appears. 11. There are two methods for completing the necessary work in order to allow a new IP address or service host name (interface name). The first is using an IPL. This is the recommended method because you will have more control over when you do the remaining work on the PC.
3. Click Browse, and then navigate to where System i Access for Windows was installed. Then, expand Client Access → Emulator → Private. Note: If you are using IBM Personal Communications the default path would be Documents and Settings → User Name → Application Data → IBM → Personal Communications 4.
5. Click OK twice. Starting the system using a manual IPL You can start your system by performing a manual initial program load (IPL). About this task These instructions assume the system is powered off. If the system is powered on, use one of the various methods available to start the manual IPL.
details. If you do not see System Reference Code (SRC) x6xx500x (where the x can be any letter or number) in the Function/Data display, then, see the information about handling and reporting system problems in the Troubleshooting and service topic. Note: If you are working with a console related problem the most common SRC code reported would be A6005008.
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.
(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.
About this task From the Work with Service Tools User IDs And Devices display, select the Service tools device IDs option. By default, this option is locked to prevent unauthorized changes to existing service tools device IDs, the creation of new IDs, or the deletion of IDs. To unlock this SST option, you must use a native macro in dedicated service tools (DST).
There is also a hot-key-activated function to capture the screen data when the connection is not responding correctly. To capture the screen data, select the configuration and press Ctrl+C. This will dump the contents of the last ten screen buffers (three screens of data) and the timestamp they were received into the connection log.
If the status message you received is not listed, see the Status messages when you have connection problems topic. Related reference “Status messages when you have connection problems” These status messages help you identify whether you have connection problems. Status messages when you have connection problems These status messages help you identify whether you have connection problems.
“Troubleshooting connection problems” When setting up your initial connection, you might encounter problems connecting your Operations Console configuration. “Local console does not detect console cable” on page 101 These are solutions to problems that occur when the local console does not detect the presence of the Operations Console cable.
2. Press Enter. The system attempts to initialize the line. If it is successful, the Function/Data window displays D1008066. If it could not initialize the line, it displays D1008065. Related tasks “Failure to display D1008065 and D1008066 automatically after calling the function” on page 98 When working with models that have a double row for the Function/Data display portion of the control panel, the control panel might not automatically display the resulting system reference code (SRC).
v If you are using Ethernet for your network, you can use a crossover cable to directly connect the PC to the adapter temporarily. This cable isolates the PC and system from any potential problems on your network that might interfere with proper operations. A crossover cable is a standard network cable but has the transmit and receive signal wires reversed.
1. The data is slow to appear so be certain to allow a 15 - 20 seconds for an action to complete before moving to the next step. Also keep in mind that some steps may not provide data to the window.
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. Note: If you have a problem accessing the PC’s serial port, you might have to power off the PC and then restart it to reset the hardware port.
If the above process fails to solve your connection problem, you need to contact your service provider for further assistance. Related tasks “Installing HyperTerminal” on page 92 To install HyperTerminal, follow these steps. Troubleshooting authentication problems When setting up your initial connection, you might encounter authentication problems. Authentication errors While you are connecting a local console to a system, you may encounter local console connection problems.
Troubleshooting system reference code data If you receive any of these system reference codes (SRCs), you might have some problems in your Operations Console configuration. Refer to the sections below to find information about specific system reference codes and troubleshooting options.
System reference code A6005008 Use this table if you received system reference code (SRC) A6005008. If an IPL did not find a console and if the console type is set to anything except a 1, the system will display code A6005008. v If you are attempting to use a twinaxial console the only data relevant in this SRC is word 16.
If Word 13 value is: Failure Word 14 means: Word 15 means: Word 16 Word 16 in the form of xxxx yy zz means the following: v xxxx where: – The twinaxial-related SRC is represented by the first 4 characters. v yy where: –...
Note: You might be able to use the console service functions (65+21) to assist in a recovery or to gather debug data. System reference code D1008065 When an attempt to activate the asynchronous communications adapter fails, you might get these common return codes for system reference code (SRC) D1008065.
About this task In these cases, you have to do a function 11 in order to determine whether the function 65 or 66 completed successfully. If the function did not complete successfully, that is, if the SRC did not display automatically: 1.
About this task 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 Tools Sign-on) has the Partition remote panel key privilege for the partition that the user is connected to. To ensure you have the proper privileges for the connection to the partition, follow these steps: 1.
Troubleshooting configuration wizard problems Here are the solutions to problems encountered while you are completing the Operations Console configuration wizard. 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.
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. When using Operations Console, SYSREQ corresponds to Shift+ESC and is defined as the default for PC5250 emulation.
Web site v System i Access Web site (www.ibm.com/servers/eserver/iseries/access) This Web site includes online product information about System i Access and Operations Console. Other information v System i Access for Windows: Installation and setup This topic collection describes how to install and configure System i Access for Windows on both the system and the PC.
System i: Connecting to System i Operations Console...
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.
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.
System i: Connecting to System i Operations Console...
Electronic emission notices Class A Notices The following Class A statements apply to the IBM System i models with the exception of those that are specifically identified as Class B. Federal Communications Commission (FCC) statement Note: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules.
This product is in conformity with the protection requirements of EU Council Directive 2004/108/EC on the approximation of the laws of the Member States relating to electromagnetic compatibility. IBM cannot accept responsibility for any failure to satisfy the protection requirements resulting from a non-recommended modification of the product, including the fitting of non-IBM option cards.
Um dieses sicherzustellen, sind die Geräte wie in den Handbüchern beschrieben zu installieren und zu betreiben. Des Weiteren dürfen auch nur von der IBM empfohlene Kabel angeschlossen werden. IBM übernimmt keine Verantwortung für die Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung der IBM verändert bzw.
Geräten (EMVG) (bzw. der EMC EG Richtlinie 2004/108/EG) für Geräte der Klasse A. Dieses Gerät ist berechtigt, in Übereinstimmung mit dem Deutschen EMVG das EG-Konformitätszeichen - CE - zu führen. Verantwortlich für die Konformitätserklärung nach des EMVG ist die IBM Deutschland GmbH, 70548 Stuttgart. Generelle Informationen: Das Gerät erfüllt die Schutzanforderungen nach EN 55024 und EN 55022 Klasse A.
System i: Connecting to System i Operations Console...