Reference and How-To

Reference and How-To
Operations Console and Other i5/OS (OS/400)

Consoles
Reference and How-To - Operations Console and Other i5/OS (OS/400) Consoles
Reference and How-To

Operations Console and Other i5/OS (OS/400)
Consoles
This document has been formatted to be viewed. Internal links will be in light blue and
external links are dark blue.
You can obtain a free reader for this document at http://www.adobe.com.
Send comments or suggestions to:
egerwill@us.ibm.com
or
gerentz@us.ibm.com
First Edition (July 2008)

This edition contains information pertaining to V5R3M0 and later of OS/400, i5/OS, and IBM I OS.
Copyright International Business Machines Corporation 2007, 2008. All rights reserved.
US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Safety and environmental notices

Safety notices may be printed throughout this guide: DANGER notices call attention to a
situation that is potentially lethal or extremely hazardous to people.
CAUTION notices call attention to a situation that is potentially hazardous to people

because of some existing condition.
Attention notices call attention to the possibility of damage to a program, device,
system, or data.
World Trade safety information

Several countries require the safety information contained in product publications to be
presented in their national languages. If this requirement applies to your country, a safety
information booklet is included in the publications package shipped with the product. The
booklet contains the safety information in your national language with references to the U.S.
English source. Before using a U.S. English publication to install, operate, or service this
product, you must first become familiar with the related safety information in the booklet. You
should also refer to the booklet any time you do not clearly understand any safety information in
the U.S. English publications. German safety information Das Produkt ist nicht fr den Einsatz
an Bildschirmarbeitspltzen im Sinne 2 der Bildschirmarbeitsverordnung geeignet.
Laser safety information
IBM servers can use I/O cards or features that are fiber-optic based and that utilize lasers or
LEDs.
Laser compliance
All lasers are certified in the U.S. To conform to the requirements of DHHS 21 CFR Subchapter
J for class 1 laser products. Outside the U.S., they are certified to be in compliance with IEC
60825 as a class 1 laser product. Consult the label on each part for laser certification numbers
and approval information.
CAUTION:
This product might contain one or more of the following devices: CD-ROM drive, DVD-ROM
drive, DVD-RAM drive, or laser module, which are Class 1 laser products. Note the following
information:
Do not remove the covers. Removing the covers of the laser product could result in
exposure to hazardous laser radiation. There are no serviceable parts inside the
device.
Use of the controls or adjustments or performance of procedures other than those

specified herein might result in hazardous radiation exposure. (C026)
CAUTION:
Data processing environments can contain equipment transmitting on system links with laser
modules that operate at greater than Class 1 power levels. For this reason, never look into the
end of an optical fiber cable or open receptacle. (C027)
CAUTION: This product contains a Class 1M laser. Do not view directly with optical
instruments. (C028)
CAUTION:
Some laser products contain an embedded Class 3A or Class 3B laser diode. Note the following
information: laser radiation when open. Do not stare into the beam, do not view directly with
optical instruments, and avoid direct exposure to the beam. (C030)
Power and cabling information for NEBS (Network Equipment-Building System) GR-1089CORE
The following comments apply to the IBM servers that have been designated as conforming to
NEBS (Network Equipment-Building System) GR-1089-CORE:
The equipment is suitable for installation in the following: Network telecommunications
facilities
Locations where the NEC (National Electrical Code) applies
The intrabuilding ports of this equipment are suitable for connection to intrabuilding or
unexposed wiring or cabling only. The intrabuilding ports of this equipment must not be
metallically connected to the interfaces that connect to the OSP (outside plant) or its wiring.
These interfaces are designed for use as intrabuilding interfaces only (Type 2 or Type 4 ports as
described in GR-1089-CORE) and require isolation from the exposed OSP cabling. The addition
of primary protectors is not sufficient protection to connect these interfaces metallically to OSP
wiring.
Note: All Ethernet cables must be shielded and grounded at both ends.
The ac-powered system does not require the use of an external surge protection device (SPD).
The dc-powered system employs an isolated DC return (DC-I) design. The DC battery return
terminal shall not be connected to the chassis or frame ground.
Product recycling and disposal
This unit must be recycled or discarded according to applicable local and national regulations.
IBM encourages owners of information technology (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 IBMs Internet site at
http://www.ibm.com/ibm/environment/products/prp.shtml.
Esta unidad debe reciclarse o desecharse de acuerdo con lo establecido en la normativa nacional
o local aplicable. IBM recomienda a los propietarios de equipos de tecnologa de la informacin
(TI) que reciclen responsablemente sus equipos cuando stos ya no les sean tiles. IBM dispone
de una serie de programas y servicios de devolucin de productos en varios pases, a fin de
ayudar a los propietarios de equipos a reciclar sus productos de TI. Se puede encontrar
informacin sobre las ofertas de reciclado de productos de IBM en el sitio web de IBM
http://www.ibm.com/ibm/environment/products/prp.shtml.
Note: This mark applies only to countries within the European Union (EU) and Norway.
Appliances are labeled in accordance with European Directive 2002/96/EC concerning waste
electrical and electronic equipment (WEEE). The Directive determines the framework for the
return and recycling
of used appliances as applicable throughout the European Union. This label is applied to various
products to indicate that the product is not to be thrown away, but rather reclaimed upon end of
life per this Directive.
In accordance with the European WEEE Directive, electrical and electronic equipment (EEE) is
to be collected separately and to be reused, recycled, or recovered at end of life. Users of EEE
with the WEEE marking per Annex IV of the WEEE Directive, as shown above, must not
dispose of end of life EEE as unsorted municipal waste, but use the collection framework
available to customers for the return, recycling, and recovery of WEEE. Customer participation
is important to minimize any potential effects of EEE on the environment and human health due
to the potential presence of hazardous substances in EEE. For proper collection and treatment,
contact your local IBM representative.
Battery return program
This product may contain sealed lead acid, nickel cadmium, nickel metal hydride, lithium, or
lithium ion battery. Consult your user manual or service manual for specific battery information.
The battery must be recycled or disposed of properly. Recycling facilities may not be available
in your area. For information on disposal of batteries outside the United States, go to
http://www.ibm.com/ibm/environment/products/batteryrecycle.shtml or contact your local waste
disposal facility.
IBM sealed lead acid, nickel cadmium, nickel metal hydride, and other battery packs from IBM
Equipment. For information on proper disposal of these batteries, contact IBM at
1-800-426-4333. Please have the IBM part number listed on the battery available prior to your
call.
For Taiwan: Please recycle batteries.
For the European Union:
Note: This mark applies only to countries within the European Union (EU).
Batteries or packaging for batteries are labeled in accordance with European Directive 2006/66/
EC concerning batteries and accumulators and waste batteries and accumulators. The Directive
determines the framework for the return and recycling of used batteries and accumulators as
applicable throughout the European Union. This label is applied to various batteries to indicate
that the battery is not to be thrown away, but rather reclaimed upon end of life per this Directive.
In accordance with the European Directive 2006/66/EC, batteries and accumulators are labeled
to indicate that they are to be collected separately and recycled at end of life. The label on the
battery may also include a chemical symbol for the metal concerned in the battery (Pb for lead,
Hg for mercury and Cd for cadmium). Users of batteries and accumulators must not dispose of
batteries and accumulators as unsorted municipal waste, but use the collection framework
available to customers for the return, recycling, and treatment of batteries and accumulators.
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.
For California: Perchlorate Material special handling may apply. See
www.dtsc.ca.gov/hazardouswaste/perchlorate.
The foregoing notice is provided in accordance with California Code of Regulations Title 22,
Division 4.5 Chapter 33. Best Management Practices for Perchlorate Materials. This
product/part may include a lithium manganese dioxide battery which contains a perchlorate
substance.
Table of Contents
Safety and environmental notices....................................................................................................5
Start here - Welcome to Operations Console and other i5/OS consoles.......................................15
Chapter 1: Reference.....................................................................................................................19
Common Terminology............................................................................................................19
Console types covered in this document.................................................................................19
Platform and environment information...................................................................................20
Operating system console designations...................................................................................20
Operations Console connectivities..........................................................................................22
Supported Adapters.................................................................................................................23
Supported adapter locations....................................................................................................26
Supported models by release...................................................................................................29
Default addresses for the HMC1 and HMC2 ports.................................................................30
Power6 processor-based Blade and Power6 processor-based System running VIOS/IVM. . .31
PC requirements for Operations Console................................................................................32
What Functions, When?..........................................................................................................32
Local console on a network (LAN) specific information........................................................44
Local console directly attached...............................................................................................49
Other references......................................................................................................................54
Operations Console simplification (V6R1).............................................................................56
Chapter 2: Considerations for planning.........................................................................................59
All systems - General Operations Console considerations.....................................................59
Pre-Power5 processor-based systems......................................................................................69
Pre-Power5 processor-based - All systems..........................................................................69
Pre-Power5 processor-based systems using a local console directly attached....................71
Pre-Power5 processor-based - Non-partitioned systems.....................................................71
Pre-Power5 processor-based - Partitioned systems.............................................................72
Power-processor-based Systems - Common information.......................................................73
Power-processor-based Systems - All systems....................................................................73
Power Systems - Not HMC managed..................................................................................74
Power5 processor-based Systems Specific..............................................................................81
Power5 processor-based - Non-partitioned systems - Not managed by a Hardware
Management Console (HMC)..............................................................................................81
Power6 processor-based Systems Specific..............................................................................82
Power6 processor-based - All systems................................................................................82
Power6 processor-based - Non-partitioned systems............................................................83
Power6 processor-based - Partitioned systems....................................................................84
Power6 processor-based Blade and Power6 processor-based systems running VIOS/IVM
..............................................................................................................................................85
RCP & VCP.............................................................................................................................87
9
Chapter 3: First Time System Setup..............................................................................................91

Select your environment..........................................................................................................92
Verify the console tagging on a Power-processor-based system............................................92
Tagging the console for a logical partition on a pre-Power5 processor-based system...........94
Verify console resource setup for VIOS/IVM........................................................................96
Select your console - New.....................................................................................................101
Chapter 4: Changing consoles - Pre-Power5 processor-based....................................................103
Choosing the procedure to change a console - Pre-Power5 processor-based.......................103
Changing hardware on a pre-Power5 processor-based logical partition with the power off
...............................................................................................................................................105
Tagging a pre-Power5 processor-based logical partition for console................................105
Changing hardware on a pre-Power5 processor-based primary partition or standalone
system with the power off..................................................................................................107
Select your console - Pre-Power5 processor-based...............................................................107
Chapter 5: Changing consoles - Power-processor-based............................................................109
Verify proper environment for changing consoles................................................................109
Choosing the procedure to change a console - Power-processor-based................................111
Changing the console without an HMC................................................................................112
Changing the console without an HMC and when the correct hardware is installed........112
Changing the console without an HMC and when hardware changes are needed............113
Changing the console with an HMC.....................................................................................116
Changing the console using the partition profile with an activation.................................117
Completing a console change with the logical partition and managed system powered on
(HMC)................................................................................................................................119
Select your console - Power-processor-based.......................................................................124
Chapter 6: Setting up Operations Console..................................................................................125
Determining where to start installing Operations Console...................................................125
Cabling the Operations Console to your server.....................................................................126
Prepare your connection........................................................................................................127
Verify or Install Client Access..............................................................................................129
Applying Client Access service packs..................................................................................130
V6R1 - Completing your configuration setup tasks..............................................................131
Option A. Local console on a network (LAN)..................................................................131
Option B. Local console directly attached.........................................................................135
V5R3/V5R4 - Completing your configuration setup tasks...................................................138
Option A. Local console on a network (LAN) V5R3/V5R4.............................................139
Option B. Local console directly attached V5R3/V5R4....................................................144
Windows XP.................................................................................................................144
Windows 2000...............................................................................................................146
Windows NT.................................................................................................................149
Option C. Local console directly attached with remote support - V5R3 & V5R4 Only...156
Windows XP.................................................................................................................156
10
Windows 2000...............................................................................................................161
Windows NT.................................................................................................................165
Remote console through dial-up support (V5R3 & V5R4 only).......................................173
Windows XP.................................................................................................................173
Windows 2000...............................................................................................................175
Windows NT.................................................................................................................177
Configuring a remote control panel or virtual control panel.............................................183
Configuring a remote control panel (RCP)...................................................................183
Configuring a virtual control panel (VCP)....................................................................185
Configuring a virtual control panel (VCP) - V6R1..................................................185
Configuring a virtual control panel (VCP) - V5R3 & V5R4...................................191
Chapter 7: Twinaxial console......................................................................................................197
Supported twinaxial adapters................................................................................................197
Twinaxial console hardware environment............................................................................197
Setting up a twinaxial console...............................................................................................197
Chapter 8: Thin console..............................................................................................................201
Cabling and connecting the Thin Console............................................................................201
Start the console and power on the system............................................................................202
Troubleshooting problems when using the Thin Console.....................................................204
Chapter 9: HMC 5250 console....................................................................................................207
Start a 5250 console locally...................................................................................................207
Connecting to a 5250 console remotely................................................................................208
Chapter 10: How do I .................................................................................................................211
determine what model or serial number a system is?............................................................211
display the system reference code (SRC) detail?..................................................................211
change keyboard definitions?................................................................................................213
change the mode of the emulator for a 3179 or 3477?..........................................................214
use the OPSCONSOLE macro?............................................................................................215
use the Operations Console properties window?..................................................................217
use the Operations Console user interface?...........................................................................220
switch from one console type to another when a console is currently available?.................223
switch the console type to recover access to the system?.....................................................224
work with console takeover and recovery?...........................................................................226
use the Console Service Functions (65+21)?........................................................................232
Local console on a network (LAN)-specific topics...............................................................239
change the access password?.............................................................................................239
work with the service tools device ID?..............................................................................239
create service tools device IDs on the system?.............................................................239
consider changing the service tools device ID passwords?...........................................241
change the service tools device ID password on the PC and system?..........................241
resynchronize the PC and service tools device ID password?......................................242
change the value of autocreate service tools device IDs? (V6R1 only)?.........................247
11
unlock service tools device IDs in SST?............................................................................248

deallocate or move the Operations Console LAN adapter?...............................................249
create or verify a service host name (interface name)?......................................................250
change network values?.....................................................................................................252
disable support for the default embedded Ethernet port, 5706/5707, or 5767/5768
adapters?............................................................................................................................255
Local console directly attached with or without remote access allowed topics....................257
activate the asynchronous communications adapter on the server?...................................257
deactivate the asynchronous communications adapter on the server?...............................258
Local console directly attached with remote access allowed and remote console through dialup support topics...................................................................................................................260
Appendix A. Shutting down systems or logical partitions..........................................................271
Appendix B. Troubleshooting.....................................................................................................281
Troubleshooting connection problems..................................................................................281
Local console.....................................................................................................................281
Directly attached................................................................................................................281
On a network (LAN)..........................................................................................................283
Remote console..................................................................................................................284
Troubleshooting authentication problems.............................................................................285
Troubleshooting system reference code (SRC) data.............................................................288
SRCs A6nn500x.................................................................................................................288
SRCs A6005001, A6005004, and A6005007....................................................................289
SRC A6005008..................................................................................................................290
Step-by-step analysis.....................................................................................................298
D1008065 after attempting to activate the asynchronous communications adapter..........301
SRC A9002000..................................................................................................................307
SRC A6005082..................................................................................................................307
Failure to display D1008065 and D1008066 automatically after calling the function......308
Startup step C6004508 takes longer than expected in D-mode IPL..................................308
Troubleshooting configuration wizard problems..................................................................309
Troubleshooting remote and virtual control panel problems................................................310
Troubleshooting other Operations Console problems...........................................................311
Changing console tags without an IPL..............................................................................311
Operations Console remains in QCTL...............................................................................312
Error message: The user can not perform the option selected...........................................312
Unable to sign on because of a lost or expired password or disabled user ID...................312
Troubleshooting console changes.........................................................................................313
Troubleshooting the new console when the system is managed by an HMC....................313
Troubleshooting the new console when the system is not managed by an HMC..............314
Appendix C. Operations Console Networking............................................................................317
Bootstrap Protocol.................................................................................................................318
Additional considerations for a system connected to an HMC.............................................319
12
Appendix D. System Locations for Cards & Cables...................................................................321

Appendix E. Backup Consoles....................................................................................................341
Appendix F. Private Network Setup............................................................................................347
Appendix G. Advanced Systems Management Interface (ASMI)..............................................351
ASMI requirements...............................................................................................................351
ASMI authority levels...........................................................................................................352
Changing ASMI passwords...................................................................................................352
ASMI login restrictions.........................................................................................................353
Accessing the ASMI..............................................................................................................354
Appendix H. Danger Notice........................................................................................................359
Appendix I. Notices.....................................................................................................................361
13
Filler page
14
Start here - Welcome to Operations Console

and other i5/OS consoles
Operations Console is an installable component of iSeries Access for Windows, System i
Access for Windows, or other formal names depending on release, which will be referred to as
Client Access for the rest of this document. It allows you to use one or more PCs to access and
control, either remotely or locally, console and control panel functions.
You can use Operations Console to manage IBM i (formerly i5/OS), i5/OS, or OS/400
operating system in a partitioned or non-partitioned environment. In a partitioned environment,
you might want to use the Hardware Management Console (HMC) or the Advanced System
Management Interface (ASMI) to access your hardware.
Operations Console uses 5250 emulation provided by either Client Access or IBM Personal
Communications to emulate a console. To emulate a server control panel, Operations Console
provides a graphical remote control panel or virtual control panel. Operations Console can use a
local area network (LAN) or direct cable attachment to enable communications between a server
and a PC. It supports dial-in connections from remote PCs to PCs that are directly attached to
servers. These remote PCs can then function as a console. This remote capability is only
available in i5/OS or OS/400 prior to V6R1.
This document should answer nearly all questions in the planning, implementation and
management of Operations Console.
The first two chapters contain information that might be used to plan or implement an
i5/OS system or partition's console solution.
Use Chapter 1 Reference, page 19 for quickly looking up information pertaining to consoles.
Use Chapter 2 Considerations for planning, page 59 for details in using a console on your
system. Be sure you know all the considerations for a particular console and the hosting system
before you start any work.
The following chapters will guide you through preparing an i5/OS system or partition for a
console:
Use Chapter 3 First Time System Setup, page 91 for a new system, partition or Power6
processor-based blade to begin your console work.
Important: You must know what hardware will be used to support a console and any hardware
work to add, remove, or replace to accomplish the console goal.
15
Use Chapter 4 Changing consoles - Pre-Power5, page 103 to migrate from one console type to
another on older hardware.
Use Chapter 5 Changing consoles - Power-based, page 109 to migrate from one console type to
another on Power-processor-based systems. However, you cannot change the console on a
Power6 processor-based blade or any system using both Virtual I/O Server (VIOS) and Integrated
Virtualization Manager (IVM).
The following chapters contain information to set up the console and make a connection:
Chapter 6 Setting up Operations Console, on page 125.
Chapter 7 Twinaxial console, on page 197.
Chapter 8 Thin console, on page 201.
Chapter 9 HMC 5250 console, on page 207.
The following links will give you access to additional information when you need to make
changes, troubleshoot or repair a console connection.
Chapter 10 How do I, on page 211.
Appendix A Shutting down systems or logical partitions, on page 271.
Appendix B Troubleshooting, on page 281.
Appendix C Operations Console Networking, on page 317.
Appendix D System Locations for Cards & Cables, on page 321.
Appendix E Backup Consoles, on page 341.
Appendix F Private Network Setup, on page 347.
Appendix G Advanced Systems Management Interface (ASMI), on page 351.
Information Center Web sites at:
Note:
The following links are subject to change without notice as the Information Center evolves and
changes.
For pre-Power5 processor-based-processor-based hardware use:
http://publib.boulder.ibm.com/iseries/
Select your release >> Connecting to System i >> Operations Console
For Power5 processor-based systems use:
http://publib.boulder.ibm.com/infocenter/systems/topic/iphbx/opsconsole.htm
For Power6 processor-based systems use:
http://publib.boulder.ibm.com/infocenter/systems/topic/front/hwparent.htm
Select Power Systems information >> Select your model >> Working with consoles,
terminals, and interfaces for Power6 processor-based processor-based systems
16
For Power6 processor-based Blade use:

Select BladeCenter information >> Blade Servers >> Select your model
Note: If you need information specific to Operations Console itself you should use the
Power5 processor-based or Power6 processor-based link.
For the latest information regarding Client Access use:
http://www-03.ibm.com/systems/i/software/access/
The console white paper can be found at:
http://www-03.ibm.com/systems/i/resources/
From Literature >> Select Solution Briefs >> Select the Papers tab >> Scroll down for i5
Console Choices
17
Filler page
18
Chapter 1: Reference
This chapter provides you with quick lookup data. It assumes you already know what console
you will be working with and factors that might influence it.
Common Terminology
The use of the term embedded Ethernet port throughout this document is meant to mean the
Ethernet port available where an adapter slot is not used. For pre-Power5 processor-based
systems, the only system with an embedded Ethernet port is the 9406-825. On Power5
processor-based systems there are two ports designated as the embedded Ethernet ports. For
Power6 processor-based systems this refers to the Integrated Virtual Ethernet (IVE), or Host
Ethernet Adapter (HEA) in some documents, which comes as a 2-port or 4-port adapter.
IBM AS/400, AS/400e, iSeries, eServer, System i, Systemi5, eServer i5,
Power processor-based, Power5 processor-based, Power6 processor-based are all
designations for systems supported from before V5R3 to the present. You will see a mix of
these terms in this document and unless specified, the data can be applied to any supported
system for the release or releases. Operations Console relies on the level of Licensed Internal
Code (LIC) and not necessarily the level of i5/OS,Operating System/400, OS/400 or IBM i.
The client code does not use mid-release designations, only service packs. The use of the term
system and server are interchangeable in this document. Also, when referring to a system, in
most cases, you can also apply the data to a partition.
modem was renamed as the Operations Console Connection
modem in V5R4. All references to this modem driver will use the newer name.
AS/400 Operations Console Connection
iSeries Navigator, System i Navigator, and other names may pertain to the Navigator product of
Client Access and will be referred to Navigator in this document.
Console types covered in this document

The following console types are represented in this document. Although the main objective of
this document is to provide information for Operations Console, you will find that you can use
this document to install or change from and to other console types. These include twinaxial,
Thin Console, and the Hardware Management Console (HMC), plus the Advanced System
Management Interface. These other consoles and interfaces are not covered in detail but there
should be enough information available here or from the provided links for you to install a
system with your desired console or change from one console type to another.
19
Platform and environment information

The term platform refers to the type of hardware you will be using. Use the following table to
help determine your platform:
Platform
System types and models as an
example
Pre-Power Processor-based
9406 - 8xx series
Power5 Processor-based
9406 - 515, 520, 525
Power6 Processor-based
9407-M15 520, 9408-M25 520,

9409-M50 550
Power6 Processor-based using

VIOS/IVM
JS22 and JS12 Type 7998 blade

servers
The term environment is used to further define the platform:

- A standalone system has a single partition running a single copy of i5/OS, and no Hardware
Management Console (HMC). You can have a standalone environment with any platform except
the blade server.
- An HMC-managed system is a Power5 or Power6 processor-based system managed by an
HMC.
- A partitioned Pre-Power Processor-based system has a primary partition plus one or more
secondary partitions, and no HMC.
- The Power6 Processor-based blade is a IBM BladeCenter JS22 and JS12 Type 7998 blade
server based on IBM Performance Optimization with Enhanced RISC (POWER) Architecture
technologies. The BladeCenter JS22 Type 7998 blade server runs in BladeCenter units to
provide a high-density, high-performance blade server environment using advanced processing
technology.
All Power6 processor-based blades are restricted to use a local console on a network (LAN) only.
Operating system console designations

Note: The following terminology will help you communicate with service providers and
follow procedures for changing consoles.
DST console
The console in control of the system when the system is IPLed to Dedicated Service Tools
(DST) or, function 21 has been performed.
20
alternate console
The term alternate console is referring to a twinaxial console that has control of the
system in the following environments:
A twinaxial workstation on the primary twinaxial workstation controller with port

0 (address 1) or port 1 (address 0 or 1) can become an alternate console device if
twinaxial console is selected.
Only the use of port 0, address 0 will allow for a system console. Port 0, address
1 or port 1, address 0 or 1 work at DST to allow debugging issues of the system
console. If you attempt to install using one of the alternate consoles the system
will warn you that you are not on the system console.
A twinaxial workstation on the controller where the alternate console tag is

referencing. The use of Port 0, address 0 or 1 or port 1, address 0 or 1 work as an
alternate console.
The alternate console can only become a DST console so you can not install the system's
operating system from this console. If you attempt to IPL the system into i5/OS (OS/400
or IBM i) the system will post SRC A9002000 and you will not have a system console.
This terminal then becomes just another workstation. However, you can do a function
21 to access DST.
Operations Console and HMC type consoles do not use resources tagged as the alternate
console.
Note: Tagging the same IOP as both the primary console and the alternate console may
result in the inability to select a console.
system console
The console that is in control of the operating system when the ENDSYS command has
completed and the system is in a restricted state. Only one device can be the system
console.
backup console
A backup console is what you would use in the event that your current console becomes
inoperable for any reason. Having another set of resources that can be implemented
quickly is the goal. All the same considerations apply to the backup console. See
Appendix E Backup Consoles on page 341 for more information regarding backup
consoles.
21
Operations Console connectivities
Local console directly attached to the server

If your needs are to use a console type similar to the requirements of twinaxial console then
this is the connectivity for you. It uses a special serial cable between the PC and the system
so the requirement of locating the console close to the system is met. You rely on physical
security if you need to restrict access to the console.
Local console directly attached to the server with remote access allowed (V5R3/V5R4
only)
In addition to the properties of the directly attached console, this configuration choice also
allows a remote console to dial into the local console and become the console. Currently,
there are other third-party solutions that may be more flexible.
Local console on a network (LAN)

Use this configuration when you need more than one PC to become the console, one at a
time of course. This connectivity requires a network resource on the system and PCs. This
network, however, may only consist of the system and those PCs that might connect, or
could include a large network infrastructure allowing access from off-site locations. See
What are the network requirements for a local console on a network (LAN)? on page 48 or
Appendix C. Operations Console Networking on page 317 for specific information.
Remote console through dial-up support (V5R3/V5R4 only)

This is the configuration that would be paired with a Local console directly attached with remote
access allowed to provide console capability at a remote site in environments where there
may not be any network capability.
22
Supported Adapters
Supported adapter locations on page 26.
Supported models by release on page 29.
If you don't know what model system you are working with see determine what model or serial
number a system is on page 211.
Supported resources for a local console on a network (LAN)

2744
2838
Adapter type
PCI 100Mbps Tokenring Adapter
PCI 100/10 Mbps Ethernet IOA
2849 PCI 100/10 Mbps Ethernet IOA

5706/5707 PCI 1000/100/10 Mbps
Ethernet IOA
or embedded port
5767/5768 PCIe 1000/100/10 Mbps
Ethernet IOA
IVE (HEA) embedded port
The IVE (HEA) is the default resource.
Use the top, or right-most port.
Restrictions
Requires IOP
V5R3 - V5R4 Power5 processor-based
and earlier systems
Requires IOP
V5R3M5 IOP-less Power5 processorbased
V5R4M5 (or later) Power6 processorbased
V5R4M5 (or later) Power6 processorbased only
23
Supported asynchronous communication adapters for a local console directly

attached configuration
Supported asynchronous adapters, depending on platform:
Adapter type
2699/9699 Two-Line WAN IOA
2721/9721 PCI Two-Line WAN IOA
w/Modem
w/Modem (See table below)
576C/2893/2894 PCIe Two-Line WAN
IOA w/Modem (See table below)
Restrictions
V5R3 & V5R3M5 SPD hardware only
V5R3 & V5R3M5 SPD to PCI migration
tower hardware only
V5R3 thru V5R4M5 Pre-Power and
Power5 processor-based - Requires IOP
V5R3 and later Pre-Power5 processorbased
V5R4M5 IOP-less Power-processor-based
V5R3 and later Pre-Power5 processorbased
V5R4M5 IOP-less Power-processor-based
24
Supported asynchronous adapters, Power6 processor-based and later

Sales Feature (Order #)
2793/2794
6803/6804
6833
9474
9493/9494
9793/9794
9933/9934
2742/6805
2893/2894
Feature Code
(WRKHDWRSC *CMN)
2793 (0614/2793/9793)
2742
576C
Power6 processor-based console card slot types and supported adapters for each slot type
The IVE (HEA) is the default resource. Use the top, or right-most port.
Slots
C1, C2,
C3
Type
PCIe
C4, C5
PCI-X
Adapters
5767/5768 - Ethernet
2893/2894 (576C) Asynchronous
5706/5707 - Ethernet
2793/2794 - Asynchronous
2742 - Asynchronous
25
Supported adapter locations

number a system is on page 211.
Supported adapter locations in a non-HMC managed system
Note: Systems managed by a Hardware Management Console (HMC) or pre-Power5 processorbased systems that have logical partitions use tagging to designate the console resource.
Appendix D. System Locations for Cards & Cables on page 321.
Pre-Power5 processor-based primary partitions and non-partitioned systems
Type
Model ECS/Async
9406
9406
9406
9406
9406
170
250
270
720
730
9406
740
9406
9406
9406
9406
800
810
820
825
C07
C07
C06
C06
9406
9406
9406
830
840
870
C02
C02
C02
9406
890
C02
9406
9406
SB2
SB3
C02
C02
C08
C08
C07
C09
Graphic
page 324
Graphic
page 325
Local console on a
network (LAN) &
Twinaxial
Twinaxial only
Twinaxial only
C06, C05
Twinaxial only
Twinaxial only
Twinaxial only
C06, C05
C06, C05
C04, C03, C11
Embedded port
C03, C02, C01
C04, C06, C10
C04, C06, C10
C04, C06, C07, C08,
C09
C04, C06, C07, C08,
C09
C04, C06, C10
C04, C06, C10
26
Power5 processor-based (not HMC managed)

The embedded support was not supported for Operations Console at V5R3M0. Support started
with V5R3M5 along with the new plus models. This allowed the use of a local console on a
network (LAN) on systems with an IXS adapter. Full IOP-less function for add-in adapters was
supported starting in V5R4M5.
Type
Model ECS/Async
9407
515
C3 C4 C2 (2, 3)
9405
520
C3 C4 C2 (2, 3)
9406
520+
C3 C4 C2 (2, 3)
9406
525
C3 C4 C2 (2, 3)
9406
550
C2 (1, 3)
9406
570
C2 (3)
9406
595
C2 (3)
Local console on a
network (LAN) &
Twinaxial
Embedded port (5, 6)
C5, C2
C5, C2
C5, C2
C5, C2
C4 (4)
C4, C6
C4 (5, 6)
27

Type
9406
Model ECS/Async
Local console on a
network (LAN) &
twinaxial
HEA, C4, C2 (5, 6, 7)
MMA C1, C4 (3)

570
9117 MMA C1, C4 (3)
HEA, C4, C2 (5, 6, 7)
570
9407 M15 C1, C2, C5 (3)
HEA, C4, C2 (5, 6, 7)
520
9408 M25 C1, C2, C5 (3)
HEA, C4, C2 (5, 6, 7)
520
9409 M50 C1, C2, C3, C5, C4
C1, C2, C3, C5, C4
550
(3)
(5, 6, 7)
(1) If an IXS is installed then use C5 (V5R3M0 only)
(2) OPSCONSOLE macro or console service function (65+21) +Fn for card selection
(V5R3M5 with PTF MF39303)
(3) OPSCONSOLE macro or console service function (65+21) +Fn for card selection
(V5R4M5 or later)
(4) If an IXS is installed then no LAN card or WS card (V5R3M0 only)
(5) The embedded Ethernet port is the default location. You must disable this support in order to
use an external 1 Gbps Adapter such as a 5706/57075767/5768 (Power5 processor-based/6
only & V5R3M5 or later)
(6) OPSCONSOLE macro or console service function (65+21) +Bn for card selection
(V5R4M5 or later)
(7)The IVE (HEA) is the default resource. Use the top, or right-most port.
28
Supported models by release

number a system is on page 211
This group of models will be referred to as pre-Power5 processor-based.
When referring to logical partitions that belong to this group start counting from zero (o) as the
first partition.
This table indicates which releases of i5/OS or OS/400 are supported by each of the System
RISC models.
System Model to OS Level Mapping
Type Model V5R3 V5R4 V6R1
9406 170
X
9406 250
X
9406 270
X
X
9406 720
X
9406 730
X
9406 740
X
9406 800
X
X
X
9406 810
X
X
X
9406 820
X
X
9406 825
X
X
X
9406 830
X
X
9406 840
X
X
9406 870
X
X
X
9406 890
X
X
X
9406 SB2
X
X
9406 SB3
X
X
29
When referring to logical partitions that belong to this group start counting from one (1).
This table indicates which releases of Licensed Internal Code (LIC) are supported by each of the
Power5 processor-based models
System Model to LIC Level Mapping
Type Model V5R3 V5R3M5 V5R4
9407
515
X
9405
520
X
X
X
9406
520+
X
X
9406
525
X
9406
550
X
X
X
9406
570
X
X
X
9406
595
X
X
X
V6R1
X
X
X
X
X
X
X
When referring to logical partitions that belong to this group start counting from one (1).
This table indicates which releases of LIC are supported by each of the Power6 processor-based
models
System Model to LIC Level Mapping
Type Model
V5R4M5 V6R1
9406
MMA 570
X
X
9117
MMA 570
X
X
9119
FHA 595
X
X
9407
M15 520
X
X
9408
M25 520
X
X
9409
M50 550
X
X
Default addresses for the HMC1 and HMC2 ports

The following table lists the manufacturing default Ethernet port addresses for connecting an
HMC, Thin Console, or Advanced System Management Interface (ASMI).
Platform
FSP A
HMC1
Power5
192.168.2.147
processorbased
Power6
169.254.2.147
processorbased
Subnet Mask
HMC2
192.168.3.147
255.255.255.0
169.254.3.147
255.255.255.0
30
Platform
FSP B (if installed)

HMC1
HMC2
192.168.2.146 192.168.3.146
Subnet Mask
169.254.3.146
255.255.255.0
Power5
processorbased
Power6
169.254.2.146
processorbased
255.255.255.0
Power6 processor-based Blade and Power6 processorbased System running VIOS/IVM

The IBM BladeCenter JS22 and JS12 Type 7998 blade server is based on IBM Performance
Optimization with Enhanced RISC (POWER) Architecture technologies. The BladeCenter
JS22 Type 7998 blade server runs in BladeCenter units to provide a high-density, highperformance blade server environment using advanced processing technology.
All Power6 processor-based blades are restricted to use a local console on a network (LAN) only.
The physical/logical route to the network determined when configuring the Blade Center and
partition. The port assigned to the partition must be bridged in order to access the network.
Also, since VIOS/IVM are required, the VIOS will always be partition 1 so the first user
partition for a console will always be 2. You would configure a local console on a network (LAN)
to use partition 2 if you have to manually configure it.
The first usable partition for data would be partition 2. Partition 1 is where VIOS is installed.
31
PC requirements for Operations Console

Note: Operations Console does NOT support the use of more than one network adapter in the
PC.
Operating System (1,2)
PC requirements - processor and
memory
Windows NT 4.0 (V5R3 only)
Operations Console PC
Windows 2000
Windows XP Professional
Pentium 300 MHz recommended

64 MB memory minimum (128 MB recommended)
Pentium 500 MHz recommended
128 MB memory minimum (256 MB recommended)
Pentium 500 MHz (P6 or equivalent compatible
microprocessor)
256 MB memory minimum
Pentium 800 MHz
512 MB memory minimum
Windows Vista
(Use Windows XP instructions)
Notes:
1. See the Client Access Web site for any updated PC requirements.
2. Windows Vista only supports a local console on a network.
What Functions, When?

Supported Windows Operating Systems
Operating System Began
Thru
Win 9x
V4R3
V5R2
Win NT
V4R4 V5R3M5
Win 2000
V4R4
Current
Win XP
V5R2
Current
Win Vista (1)
V5R4
Current
Originally, Windows Vista was supported at SI25949 (SP4)
A problem in PC5250 requires SI27741 (SP6) for any function

requiring PC5250, including Operations Console.
32
Configurations
Function
Direct cable
Direct cable
w/remotes
Remote console
Dial-up Local
console
LAN console
Began
V4R3
V4R3
Thru
Current
V5R4
V4R3
V4R4
V5R4
V5R2
V5R1
Current
System side function

Function
CSFs / macros
All 5250 consoles
provide green-onblack
QCONSOLE device
ID grants RCP
access
Partition remote
panel granted by
default
Allow system value
security changes by
default
Allow new digital
certificates by
default
default and expired
password to change
its own password off
by default
Manual kick at
C6004508
Autocreate DevIDs
VSDISCOVER
Device ID option in
SST locked by
default
Unlock service tool
device IDs option in
DST security data
V5R3
X
X
V5R3
Update
X
X
V5R3M5
V5R4M0
V5R4M5
V6R1
X
X
X
X
X
X
X
X
X
X
X
33
Takeover / Recover
Function
Takeover/recover
Need to force option
to use it
Takeover/recover
Takes effect
immediately now
Behavior changed
with new macros:
SHOWSTATUS
SKIPSTATUS
TAKEON
TAKEOFF
V5R3
X
V5R3
Update
X
V5R3M5
V5R4M0
V5R4M5
V6R1
X
X
X
X
RCP/VCP (Power5 processor-based/6 hardware does not support ANY directly-cabled

RCP)
Function
RCP - cabled ser.
RCP - cabled par.
Begin
Thru
Notes
V4R3
V5R3
1
V4R5
V5R3
2
NT only
V5R1
Current
RCP (LAN)
Logical partitions
VCP
V5R2
Current
Note 1: No serial-based RCP models are supported
Note 2: Parallel-based RCP exist and may work but
not supported
Info Center changes

Function
Separate InfoCntrs
for iSeries/Power5
processor-based
Add Power6
processor-based doc
Separate Changing
console doc
V5R3
X
V5R3
Update
X
V5R3M5
X
34
V5R4M0
X
V5R4M5
V6R1
Client - Wizard
Function
V4R3
Client rewritten
Client rewrite w/new
panels w/graphics
All panels have the
X
same graphics
All panels have
context graphics
DevID/Access PW
Same panel
DevID/Access PW
Separate panels
Conditional DevID
panel / No access
PW
DevID no longer
requires a userentered PW
PC or system
Simplified some
wizard work
USB/PCMCIA
support for serial
COM1-9
AS/400 Operations
X
Console Connection
modem
Rebrand Operations
Console Connection
modem
V4R4
V4R5
V5R1
X
X
V5R2
X
X
V5R3
V5R4
V6R1
X
X
X
X
X
X
35
Client - GUI
Function
V4R3 V4R4 V4R5 V5R1 V5R2 V5R3 V5R4
Properties page
X
X
Device ID tab
gone
Display device
ID on general
tab
Answer BOOTP
has subnet mask
and gateway
address fields
for edit
Access PW tab
pre-filled with
old PW
Use console on
configuration tab
has field for IP
address
Hot keys (Settings)
X
X
Alt+w or
Alt+shift+w
Turn off Autodiscover
Answer BOOTP
X
to config tab
Expand connection
X
X
to display functions
Ability to change
X
X
X
X
X
config by using the
wizard
A more WindowsX
X
like interface
Single sign-on
X
X
Suppress msgs
Drag-n-drop
Sngl/dbl clicks
36
V6R1
X
X
X
X
X
X
X
X
X
X
X
X
X
Client - Function
Function
V5R4
Auto reset of device
X
ID for PC
Access PW managed
by client, not user,
by default
V6R1
X
X
Client - Misc
Function
PC-prerequisite
program
EZ-Setup
Navigator support
Navigator localhost
Crypto support
V4R3 V4R4 V4R5 V5R1 V5R2 V5R3

X
X
X
X
X
?
X
X
X
X
X
X
X
X
X
X
X
V5R4
X
V6R1
X
Implied
X
Implied
Implied
In Base
In Base
Pre-Power5 processor-based - Serial - Direct cable

Models &
Adapters
150/170
170 = 250
600/S10
620/720/S20
640/730/S30
650/740/S40
4xx/5xx
V4R3 V4R4 V4R5 V5R1 V5R2 V5R3 V5R3 V5R3M5

Update
2721 2721 2721 2721
2745 2745 2745 2745
2721 2721 2721 2721
2721
2745 2745 2745 2745
2745
2721 2721 2721 2721
2745 2745 2745 2745
2721 2721 2721 2721
720
720
720
720
2745 2745 2745 2745 2721 2721 2721
2721
2745 2745 2745
2745
2699 2699 2699 2699
730
730
730
730
2699 2699 2699
2699
2699 2699 2699 2699
740
740
740
740
2699 2699 2699
2699
2609 2609 2609 2609
2612 2612 2612 2612
37
Pre-Power5 processor-based (iSeries) - Serial - Direct cable

Models &
Adapters
270
V4R5 V5R1 V5R2

2721
2745
2745 2745
2771( 2771
1)
(2)
820/830/840
2721
2745
2745 2745
2771( 2771
1)
(2)
800/810
2745
2771
(2)
825/870/890
2745
2771
(2)
V5R3
2742
2745
2771 (2)
(3)
2742
2745
2771 (2)
(3)
2742
2745
2771 (2)
(3)
2742
2745
2771 (2)
(3)
V5R3 V5R3M5 V5R4M0 V5R4M5 V6R1

Update
2742
2742
2742
2742
2745
2745
2745
2745
2771 (2) 2771 (2) 2771 (5) 2771 (5)
(3)
(3)
2742
2742
2742
2742
2745
2745
2745
2745
2771 (2) 2771 (2) 2771 (5) 2771 (5)
(3)
(3)
2742
2742
2742
2742
2742
2745
2745
2745
2745
2745
2771 (2) 2771 (2) 2771 (5) 2771 (5) 2771
(3)
(3)
(5)
2742
2742
2742
2742
2742
2745
2745
2745
2745
2745
2771 (2) 2771 (2) 2771 (5) 2771 (5) 2771
(3)
(3)
(5)
(1) - 2771 will be searched for and takes over for the 2745 if both installed
(2) - New parallel RCP cable
(3) - Another new parallel RCP cable
(4) - IOPless for RSSF only
(5) - Parallel RCP - Not supported
Power5 processor-based - Asynchronous - Direct cable

Models
V5R3
Power5 processorbased
520/550/570
2742
2745
2771
2793
550/595
515-520+-525
(1) - IOPless for RSSF only
(2) - IOPless supported
V5R3
Update
2742
2745
2771
2793
V5R3M5
V5R4M0
V5R4M5
V6R1
2742
2745
2771
2793 (1)
2742
2745
2771
2793 (1)
2742
2745
2771
2793 (1)
2742
2745
2771
2793 (1)
2742 (2)
2745
2771
2793 (2)
2742 (2)
2745
2771
2793 (2)
2742 (2)
2745
2771
2793 (2)
2742 (2)
2745
2771
2793 (2)
38
Power6 processor-based - Asynchronous - Direct cable (all HW runs IOP-less)

Models
9117-MMA 570
9119-FHA 595
9406-MMA 570
9407-M15 520
9408-M25 520
9409-M50 550
New PCI-E slots
V5R4M5
2742
2793
276C
V6R1
2742
2793
276C
Pre-Power5 processor-based - Network (LAN)

Models
V5R1
V5R2
V5R3
V5R3
V5R3M5 V5R4M0
Update
150/170 - 600/S10 - 620/720/S20 - 640/730/S30 - 650/740/S40 - 4xx/5xx
Not supported
270
2724
2744
2744
2744
2744
2744
2744
2838
2838
2838
2838
2838
2838
2849
2849
2849
2849
2849
6149
820/830/840
2724
2744
2744
2744
2744
2744
2744
2838
2838
2838
2838
2838
2838
2849
2849
2849
2849
2849
6149
800/810
2744
2744
2744
2744
2744
2838
2838
2838
2838
2838
2849
2849
2849
2849
2849
825
Embed. Embed. Embed.
Embed.
Embed.
870/890
2744
2744
2744
2744
2744
2838
2838
2838
2838
2838
2849
2849
2849
2849
2849
39
V5R4M5
V6R1
2744
2838
2849
2744
2838
2849
2744
2838
2849
Embed.
2744
2838
2849
2744
2838
2849
Embed.
2744
2838
2849
Power5 processor-based - Network (LAN)

Models
V5R3
520/570
2744
2838
2849
V5R3
Update
2744
2838
2849
550/595
2744
2838
2849
Any model that
supports IOP-less
HW
V5R3M5 V5R4M0 V5R4M5 V6R1

Embed.
5706/7
2744
2838
2849
Embed.
5706/7
2744
2838
2849
Embed.
5706/7
2744
2838
2849
Power6 processor-based - LAN

Models
9117-MMA 570
9119-FHA 595
9406-MMA 570
9407-M15 520
9408-M25 520
9409-M50 550
New PCI-E slots
V5R4M5 V6R1
IVE(HEA) IVE(HEA)
5706/7
5706/7
2744
2744
2849
2849
Power6 processorbased Blade

LAN console only
IVE(HEA)
Only
VIOS/IVM managed
LAN console only
IVE(HEA)
Only
5767/8
5767/8
40
Embed.
5706/7
2744
2838
2849
Embed.
5706/7
2744
2838
2849
Embed.
5706/7
2744
2838
2849
Embed.
5706/7
2744
2838
2849
Embed.
5706/7
2744
2838
2849
Embed.
5706/7
2744
2838
2849
Embed.
5706/7
2744
2838
2849
Embed.
5706/7
2744
2838
2849
Embed.
5706/7
2744
2838
2849
Console Service Functions (65+21) - Equivalent macros

Functions
01 - 04
C3 / A3 / DD
E1 / E2 / D1 / D2
Fn
Bn
V5R3
X
X
X
V5R3M5
X
X
X
X (1)
V5R4M0
X
X
X
X (1)
V5R4M5
X
X
X
X
X
Timeout 45 - 60 secs
V6R1
X
X
X
X
X
X
(1) PTF MF39303 (V5R3M5) or PTF MF39304 (V5R4M0)

SRC data in SRC A6005008, D1008065, AND D1008066
Word / Data
Basic word 13 - 19
Expanded word 13
w/EnCn
Expanded word 13
w/LAN flag/card
Expanded word 16
V5R2
X
V5R3
X
V5R3M5
X
V5R4M0
V6R1
41
V5R4M5
System models by supported release (no longer supported)

Type Model
V3R6 V3R7 V4R1 V4R2 V4R3 V4R4 V4R5 V5R1 V5R2 V5R3 V5R4 V6R1
9401 150
X
X
X
X
X
X
X
X
9402 400
X
X
X
X
X
X
X
X
9402 436
X
X
X
X
X
X
X
9402 40S
X
X
X
X
X
X
X
X
9406 50S
X
X
X
X
X
X
X
X
9406 500
X
X
X
X
X
X
X
X
9406 505
X
X
X
X
X
X
X
X
9406 510
X
X
X
X
X
X
X
X
9406 530
X
X
X
X
X
X
X
X
9406 53S
X
X
X
X
X
X
X
X
9406 600
X
X
X
X
X
X
X
9406 620
X
X
X
X
X
X
X
9406 640
X
X
X
X
X
X
X
9406 650
X
X
X
X
X
X
X
9406 S10
X
X
X
X
X
X
X
9406 S20
X
X
X
X
X
X
X
9406 S30
X
X
X
X
X
X
X
9406 S40
X
X
X
X
X
X
X
9406 SB1
X
X
X
X
X
X
X
42
System models by supported release (currently supported)

Type Model
V3R6 V3R7 V4R1 V4R2 V4R3 V4R4 V4R5 V5R1 V5R2 V5R3 V5R4 V6R1
7998 60X JS12
X
Blade
7998
61X JS22
Blade
9117 MMA 570
9119 FHA 595
9405 520
9406 170
X
9406 250
9406 270
9406 520
9406 525
9406 550
9406 570
9406 MMA 570
9406 595
9406 720
9406 730
9406 740
9406 800
9406 810
9406 820
9406 825
9406 830
9406 840
9406 870
9406 890
9406 SB2
9406 SB3
9407 515
9407 M15 520
9408 M25 520
9409 M50 550
1 - Requires V5R4M5 of Licensed Internal Code
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
http://www-304.ibm.com/jct01004c/systems/support/i/planning/upgrade/osmapping.html
43
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X1
X1
X
X
X
X
X
X
X
X
X
X1
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X1
X1
X1
X
X
X
X
X
X
X
X
X
Local console on a network (LAN) specific

information
Supported resources for a local console on a network (LAN)
Adapter type
Restrictions
PCI 100Mbps Tokenring Adapter Requires IOP
PCI 100/10 Mbps Ethernet IOA V5R3 - V5R4 Power5 processor-based
and earlier systems
2849 PCI 100/10 Mbps Ethernet IOA Requires IOP
5706/5707 PCI 1000/100/10 Mbps
V5R3M5 IOP-less Power5 processorEthernet IOA or embedded port
based
V5R4M5 (or later) Power6 processorbased
5767/5768 PCI-E 1000/100/10 Mbps
V5R4M5 (or later) Power6 processorEthernet IOA
based only
IVE (HEA) embedded port
V5R4M5 (or later) Power6 processorThe IVE (HEA) is the default resource.
based only
Use the top, or right-most port.
2744
2838
44
Supported adapter locations in a non-HMC managed system

Note: Systems managed by a Hardware Management Console (HMC) or pre-Power5 processorbased systems that have logical partitions use tagging to designate the console resource.
Graphics of system locations for Operations Console on page 321.
Type
9406
9406
9406
9406
9406
9406
9406
9406
9406
9406
9406
9406
9406
Model Local console on a

network (LAN) &
twinaxial
170
Twinaxial only
250
Twinaxial only
270
C06, C05
800
C06, C05
810
C06, C05
820
C04, C03, C11
825
Embedded port
C03, C02, C01
830
C04, C06, C10
840
C04, C06, C10
870
C04, C06, C07, C08,
C09
890
C04, C06, C07, C08,
C09
SB2 C04, C06, C10
SB3 C04, C06, C10
45

The embedded support was not supported for Operations Console at V5R3M0. Support started
with V5R3M5 along with the new plus models. This allowed the use of a local console on a
network (LAN) on systems with an IXS adapter. Full IOP-less function for add-in adapters was
supported starting in V5R4M5.
Type
9407
9405
9406
9406
9406
9406
9406

network (LAN) &
twinaxial
515
C5, C2
520
C5, C2
520+ Embedded port (2, 3)
C5, C2
525
C5, C2
550
C4 (1)
570
C4, C6
595
C4 (2, 3)
46

Type

network (LAN) &
twinaxial
9406 MMA HEA, C4, C2 (2, 3, 4)
570
9407 M15 HEA, C4, C2 (2, 3, 4)
520
9408 M25 HEA, C4, C2 (2, 3, 4)
520
9409 M50 C1, C2, C3, C5, C4
550
(2, 3)
(1) If an IXS is installed then no LAN card or WS card (V5R3M0 only)
(2) The embedded Ethernet port is the default location. You must disable this support in order to
use an external 1 Gbps Adapter such as a 5706/57075767/5768 (Power5 processor-based/6
only & V5R3M5 or later)
(3) OPSCONSOLE macro or console service function (65+21) +Bn for card selection
(V5R4M5 or later)
(4) The IVE (HEA) is the default resource. Use the top, or right-most port.
What if my non-HMC managed system has an embedded Ethernet port?

The following information only pertains to systems that are not partitioned and therefore
aren't Hardware Management Console (HMC) managed. If your system is HMC managed
then you should tag the specific adapter resource you wish to use for the partition.
Pre-Power5 processor-based
The only model with a supported embedded Ethernet port is the 9406-825. By default, this
is the only supported resource when using a local console on a network (LAN). However, if this
port reports as failed the system will look at the following locations for an acceptable adapter
resource in the order given: C03, C02, C01
Power5 processor-based
The first embedded Ethernet port is now the default for a local console on a network (LAN)
starting with V5R3M5 of Licensed Internal Code. Prior to this code level the embedded
Ethernet port could not be used for Operations Console (LAN). If you want to use a different
adapter for console you have to disable support for the embedded port. See disable support
for the default embedded Ethernet port, 5706/5707, or 5767/5768 adapters on page 255 for
details.
47
By default, a non-HMC managed system will use the first embedded Ethernet port, top or
right-most. The system automatically reserves a logical port for each physical port available
on the IVE. If you want to use a different adapter for console you have to disable support
for the embedded port. See disable support for the default embedded Ethernet port,
5706/5707, or 5767/5768 adapters on page 255 for details.
What are the network requirements for a local console on a network (LAN)?
Basically, the network requirements are pretty simple. The PC client needs to be able to
connect to the target system or partition using whatever means is best in your working
environment. However, in order to set up a new system and perform some changes to the
console there may additional requirements. To set up a new system, for example, the system
relies on the BOOTP process in which the system sends out broadcast information which is
answered by the PC client. The network infrastructure needs to be capable of passing this
broadcast data through the network to the PC client.
With the increasing sensitivity to security on networks, some users have elected to isolate the
console from their normal network. You can connect a Ethernet cross-over cable directly
between the PC and the pre-Power5 processor-based system. On Power-processor-based
models, if you use a 1 Gbps adapter, such as a 5706/5707 or 5767/5768 you don't even have
to use a cross-over cable. A standard Ethernet cable would work just fine since all adapters
built after the 2849 have sensing hardware function that automatically uses either cable type.
A crossover cable is a standard network cable that has the transmit and receive signal wires
reversed. This virtually allows each end to act as if a hub, switch, or router were between
them. The use of a crossover cable might also require a nonstandard network configuration at
the system and PC.
V6R1 introduces the ability of the PC client to detect new V6R1 systems using a proprietary
method called VSDISCOVER. It uses the same requirements as BOOTP except the
broadcast packets are initiated at the PC client instead of the system. See Operations Console
networking on page 317 for more details regarding the network information and BOOTP
process.
48
Local console directly attached

Supported asynchronous communication adapters for a local console directly
attached configuration
Supported asynchronous adapters, depending on platform:
Adapter type
2699/9699 Two-Line WAN IOA
Restrictions
V5R3 & V5R3M5 SPD hardware only
V5R3 & V5R3M5 SPD to PCI
migration tower hardware only
2745/9745 PCI Two-Line WAN IOA V5R3 thru V5R4M5 Pre-Power5
2771/9771 PCI Two-Line WAN IOA processor-based and Power5 processorw/Modem
based - Requires IOP
2742/6805 PCI Two-Line WAN IOA V5R3 and later Pre-Power5 processorbased
V5R4M5 IOP-less Power-processorbased
2793/2794 PCI Two-Line WAN IOA V5R3 and later Pre-Power5 processorw/Modem (See table below)
based
V5R4M5 IOP-less Power-processorbased
V5R4M5 (or later) Power6 processor576C/2893/2894 PCIe Two-Line
WAN IOA w/Modem (See table below) based only
49
Power6 processor-based and later

Sales Feature
(Order #)
2793/2794
6803/6804
6833
9474
9493/9494
9793/9794
9933/9934
2742/6805
2893/2894
Feature Code
(WRKHDWRSC *CMN)
2793 (0614/2793/9793)
2742
576C
Supported adapter locations in primary partitions or non-partitioned systems
Systems managed by a Hardware Management Console (HMC) or pre-Power5 processorbased systems that have logical partitions use tagging to designate the console resource.
Operations Console does not use any embedded serial ports located on the system.
Graphics of system locations for Operations Console on page 321.

Type
9406
9406
9406
9406
9406
9406
9406
9406
9406
9406
9406
9406
9406
9406
9406
9406
Model
170
250
270
720
730
740
800
810
820
825
830
840
870
890
SB2
SB3
ECS/Async
C08
C08
C07
C09
Graphics page 324
Graphics page 325
C07
C07
C06
C06
C02
C02
C02
C02
C02
C02
50

The 9406-520 series typically had a 2793/2794 adapter in C03 for systems ordered with
Operations Console (Direct) driven by an IOP at V5R3M0. In V5R3M5 the 2793/2794 was
supported as IOP-less in C04 but only for remote service or other point-to-point
communications, not for Operations Console. Operations Console didn't fully support IOP-less
function until V5R4M5.
Type
9407
9405
9406
9406
9406
9406
9406
Model
515
520
520+
525
550
570
595
ECS/Async
C3 C4 C2 (2, 3)
C3 C4 C2 (2, 3)
C3 C4 C2 (2, 3)
C3 C4 C2 (2, 3)
C2 (1, 3)
C2 (3)
C2 (3)

Type
9406
Model ECS/Async
MMA C1, C4 (3)
570
9407 M15 C1, C2, C5 (3)
520
9408 M25 C1, C2, C5 (3)
520
9409 M50 C1, C2, C3, C5, C4
550
(3)
(1) If an IXS is installed then use C5 (V5R3M0 only)
(2) OPSCONSOLE macro or console service function (65+21) + Fn for card selection
(3) OPSCONSOLE macro or console service function (65+21) + Fn for card selection
(V5R4M5 or later)
51
Supported cables
Console cable
Model
9406 730/740
9401 150/170
Feature Code (card)

2699
2721, 2742, 2745,
2771, 2793
2742, 2745, 2771, 2793
9406
270/810/820/825/830/840/890
9407 M15 520
576C, 2742, 2793
9408 M25 520
576C, 2742, 2793
9409 M50 550
576C, 2742, 2793
9406-MMA 570
576C, 2742, 2793
Part Number (cable)

97H7556 (0328)
97H7557 (0367),
39J5835
97H7557 (0367),
39J5835
97H7557 (0367),
39J5835
97H7557 (0367),
39J5835
97H7557 (0367),
39J5835
97H7557 (0367),
39J5835
RCP cable - Support dropped for parallel in V5R4M0 / Serial RCP went away with no
supported HW in V5R4M0
Server
Part Number (cable)
9406 270/820/830/840 (1) 04N5592 (2) 53P5704
All other systems
97H7591 (0381)
Note 1. Currently, these servers support the remote
control panel only under Windows NT Workstations 4.0,
Windows 2000, and Windows XP.
Note 2. There is a missing pin in the connector at one end
of this cable. This end connects to the system. The new
cable is labeled dont trust missing pin
Parallel cabled RCP not supported in V5R4 and later
52
What communications port(s) are required for Operations Console?

For the configuration wizard to configure Operations Console successfully, you need to
verify that you have an available communications port. If you have a pre-Power5
processor-based system with V5R3 or V5R3M5 and it uses a serial remote control panel
cable the PC requires a serial port, also. If your system supports a serial remote control
panel and you plan to use it along with the console, the PC must have two serial ports.
You need a connector for a communications interface such as a serial port. Operations
Console supports serial COM ports 1 - 9. One COM port is required for system console
support.
Note: Operations Console does not use any embedded serial ports located on the system.
To check that you have an available communication port, check the documentation for your
PC or with the PC manufacturer to verify you have the necessary communications port or
ports. When you configure Operations Console, the wizard will search for a port for the
console.
The use of a Universal Serial Bus (USB) to serial port adapter support has been added to
Operations Console. The adapter will be placed at the PC end of the console serial cable and
connect to the PC's USB port. When installing the USB adapter, follow the manufacturer's
instructions, the operating system will assign a serial port to that adapter, COM 4, for
example. This adapter will be used exclusively for the console. 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.
Also, the use of a serial PCMCIA adapter on a notebook is also supported as long as the
communications port provided is within the range supported by Operations Console.
However, IBM does not guarantee that all adapters will work in all situations.
Restrictions on use
The adapter must plug directly into a USB connector on the PC. Neither the use of a
USB hub to share connections nor the use of USB extension cables is supported,
however these devices may function correctly in some situations.
Parallel directly attached remote control panel (V5R3 only)
Operations console uses LPT port 1. A directly attached remote control panel is not
supported on any system starting with V5R4.
53
Other references
What are the software requirements for Operations Console?
Operations Console is supported on Windows NT workstation (V5R3 only), Windows
2000 Professional, Windows XP Professional, and Windows Vista.
Note: Windows Vista can only be used for a local console on a network configuration. You
cannot use Windows Vista for a local console directly attached. Use the instructions for
Windows XP for any instructions.
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.
Note: If you run any software that enables SOCKS on your PC (the PC accesses the Internet
through a firewall, such as Microsoft Proxy Client, Hummingbird SOCKS Client, NEC
SOCKS 5, or others), you cannot route the subnet for 192.168.0.0 to the firewall. Operations
Console uses addresses in 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
54
What is the meaning of the field Current state of console tag on the Select
Console window?
For a partitioned system or partition the state supplies debug data for console failures by
showing the data. This data is available to any device capable of accessing SST. In addition to
this data, there is expanded data available in SRC A6005008 in word 16.
Select Console
System:
Allow console recovery and console can be taken
over by another console . . . . . . . . . 1
Select one of the following:
Console type . . . . . . . . . . . . . . . .
1. Twinaxial
2. Operations console(Direct)
3. Operations console(LAN)
4. Hardware management console(HMC)
Current state of console tag
. . . . . . . .
IOCSX0
1=Yes, 2=No
Taken from the help text:

This field indicates the current state of the console
tag if this is a logical system partition. The device
(IOA) or resource (IOP) tag value can be
0 = No device or IOP found or tagged
1 = Twinaxial device tagged
2 = Async direct attached device tagged
3 = LAN attached device tagged
4 = HMC device tagged.
5 = IOP resource tagged, device could be async or
LAN or twinaxial device.
6 = Invalid IOA device tagged.
It is normal for a value of 0 (zero) when the system is not partitioned.
55
Operations Console simplification (V6R1)

Operations Console can automatically create service tools device IDs, manage access passwords,
and discover systems.
Operations Console automates working with service tools device IDs. The system, by default, is
set to maintain up to ten service tools device IDs of a maximum value of 49 in addition to
QCONSOLE. You no longer have to manually create a new device ID when adding a PC to
connect into a system or partition. See Autocreate service tools device IDs below for more
details.
Also, Operations Console takes control of the access password activity for you. The
authentication process remains the same, but when this function is active, you are not asked to
enter the access password during a connection. However, you must provide a DST user ID and
password to successfully connect. This function does not affect a local console that is directly
attached or any other console type. See Automatic management of the access password below
for more details.
Auto-discovery of systems running V6R1 of Licensed Internal Code takes place each time
Operations Console is started or on-demand by pressing Alt+w (or Alt+W). See Automatic
discovery of systems below for more details.
Autocreate service tools device IDs

By default, the operating system sets the value of the Autocreate service tools device IDs option to
10. This default value gives you 11 connections to be automatically managed. You have
QCONSOLE as a default ID and then 10 additional service tools device IDs. These display as
QCONSOLE00, QCONSOLE 01, through whatever value is set. It is recommended that you
have at least one spare so 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.
You can change the default value of the Autocreate service tools device IDs option by performing
the instructions in change the value of autocreate service tools device IDs option topic on page
247.
This function is used for any new configured connections you create. This means that if you
upgraded from a prior release of Operations Console on the PC, your current configurations are
retained and continue to work just as they did before. However, if the PC and system do get out
of synchronization, instead of issuing an error message to resynchronize them, this function
automatically recovers the issue.
56
When you create a local console on a network configured connection, you need to enter the
name of the service interface (service host name.) The name you use depends on the
circumstances for the connection. For example, if this is a new system and this is the first
console to connect, then the name might be whatever you want to call it or it might be what a
DHCP server gave it.
There may be times in which you configure a connection with an auto-created service tools
device ID, grant access to the remote control panel, then at a later time you connect and find that
you no longer have a remote control panel. This is the result of a change in the assigned service
tools device ID. Something occurred, possibly not connecting this device in a few days for
instance, so the service tools device ID got reset. A reset of the device ID includes revoking
permission to the RCP, so you, again, have to manually grant permission to the RCP. Currently,
the only way to prevent this would be for you to create a specific service tools device ID for this
configured connection and delete the previous one. See create a service tools device ID on page
239 for instructions on how to do this.
Automatic management of the access password

By default, you cannot set an access password when you create an Operations Console
configuration. An access password is automatically generated and supplied to the connection
process at the appropriate time. You do not need to know this password as it is automatically
managed by the system.
However, if you do want to change the access password, you can do this on the Properties page.
Changing this password causes the automatic process of supplying the password to be disabled.
You need to enter your access password for any connection that requires an access password.
The sign-on process requires a valid DST user ID and password to be entered to authenticate the
user.
Automatic discovery of systems

When Operations Console starts, a search for qualified systems begins. A "qualified system" is
any system running V6R1 with an active service host name (service interface). It does not need
to have Operations Console as the console type. If the PC gets a response from the network for
any qualified systems, Operations Console creates a configuration for that system. It also
preserves any pre-existing configured connections. A qualified system must have a value set for
the Autocreate service tools device IDs option, which has a default value of 10. If this value is zero,
the system might not report correctly and therefore might not show up in this auto-generated list
of systems. This auto-discovery function occurs any time Operations Console begins or when
performed on-demand by holding down the alt key, the shift key, and then pressing w, or
alternately, by holding down the Alt key and pressing the w key. This causes Operations
Console to begin a new search for eligible systems.
57
Important: If a system shows up in the list of configured connections, it does not guarantee that
the system can be connected to. In rare cases, there are conditions in which the system is able to
satisfy the requirements to report but not meet all requirements for a connection.
This function can be turned off by entering the Settings window by holding the Alt key and
pressing the shift key and then the s key (Alt+S). You can then turn off the Auto-discover
function. To learn more about the other options, see use the Operations Console user interface
on page 220 for details.
58
Chapter 2: Considerations for planning

Use this chapter to determine what might influence your intended console or backup console.
All systems - General Operations Console

considerations
What if I need more than one adapter of the type currently used as the console?
If you need additional network or asynchronous communications adapters in your system
special consideration should be given to where you place or designate for console and
backup console. Consider the following:
Pre-Power5 processor-based systems
Non-partitioned
Since the adapter used for console is selected by location try to locate the additional
adapter(s) in locations not eligible for console use.
Partitioned
Since you tag at an IOP level for console you can place additional cards so they are
associated with a different IOP. If you cannot do this you run the risk that the system
will be unable, in all cases, to determine which adapter to use when activation occurs.
This is even true if the second adapter is intended to be used in an emergency as the
backup console. Using a backup console of a different connectivity, a Local console
directly attached as a backup to a local console on a network (LAN) instead of a second
network adapter is recommended.
Power5 processor-based and Power6 processor-based systems

Non-partitioned
The system still determines the console resource by location but some models and
releases allow an individual adapter to be designated for the console.
V5R3M5 uses PTF MF39303 to add this capability for a model 9406-520.
V5R4M0 uses PTF MF39304 to add this capability for a model 9406-520
Starting with V5R4M5 support for additional models to be able to designate a
particular location was implemented.
See Chapter 1: Reference on page 19 to find out if your model has this capability.
Partitioned
Power5 processor-based and Power6 processor-based systems typically tag the
console at an IOA level so you can specify the individual adapter to be used. The
Console tag determines the console for all consoles and the Operations Console tag is
also set if you plan to use a Local console directly attached.
59
What is Allow console recovery and console can be taken over by another
console?
There is also a special set of console options called Allow console recovery and console can be
taken over by another console. This set of functions allows Operations Console to take control
from another console device. The default value of this console option is disabled. Twinaxial
devices use a special 5250 emulation and do not qualify for this takeover and recovery
function.
When the option is enabled:

The first Operations Console device connected becomes the console. Additional LANconnected Operations Console devices will have a special DST signon.
All other 5250-based connections will display the new Console Information Status window.
Console recovery without the loss of the job is available.
When the option is disabled:

The first Operations Console device connected becomes the console.
All other 5250-based connections will be presented the new Console Information Status
window.
Console recovery without the loss of the job is not available.
For more information regarding takeover and recovery, see work with console takeover and
recovery on page 226.
Can more than one console be made available for use as necessary?
Operations Console, both local console directly attached to the server and a local console on a
network (LAN), HMC, and twinaxial workstations, can coexist as console-capable devices if
you remember the following rules:
Only the configured console type is supported.

If no console type is specified, such as when a new partition is being created, the
supporting hardware tagged by the HMC is used.
If there is no HMC, then the console is determined by any eligible adapters by location.
If more than one eligible adapter is found, then the first connected device determines the
console.
60
In the case of a server without an HMC, for example, if you use Operations Console
(Direct) as the console type and you have a LAN adapter that is available to support a
console, and has a valid configuration, then the console is the directly attached PC.
However, the LAN adapter is started at IPL time and the connecting PC, one or
multiple, displays the Console Information Status window. The field Take over the
console displays NO and the message at the bottom of the window indicates that this
device is not the supported console type.
Back in V5R1 and V5R2 if you had adapters present where they could be used to
support a console you could actually switch from one console to another very simply.
For example, if the console type was set to Operations console(LAN) you could
disconnect your console and start a twinaxial workstation or even Operations Console
(Direct). However, it was also found that the system didn't always select the correct
console during an IPL.
Starting with V5R3, the code was changed to only allow a console using the
configured console type. Other connectivities might be able to connect but not
become the console.
However, there are temporary solutions for the use of a different console. See Forced
takeover on page 227 for more information.
Only one device can be active at a time.

A twinaxial workstation on port 0 address 0 can become a console device if twinaxial
console is selected.
If twinaxial console is selected as the console type, then Operations Console devices
might not be started.
If there is a configured service host name, for example, to support iSeries Navigator, then
the system activates the supporting adapter in addition to the twinaxial adapter.
If you use Operations Console (LAN) for the console, but you have an eligible
asynchronous communications adapter available as a backup, then the LAN adapter is
activated to support the console. The asynchronous communications adapter does not
automatically get started since the console type value is not set for its use at this time.
However, because it is eligible to support the console, assuming the Operations Console
tag is set, then the operating system cannot use this resource.
Depending on your hardware environment you may have to change just the console type
or the console tag. This assumes that the hardware is already installed.
61
Can I have more than one connection active at a time?

Operations Console allows multiple LAN connections to a single system or logical partition,
but only one 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 window but only one is actually active.
The client PC also allows multiple local console connections but allows only one Local
console directly attached to the system configuration for a single PC.
How many 5250 sessions can I have active at a time?

There is a maximum of 26 active emulator sessions available per PC. Active emulator
sessions are identified by a single letter of the English alphabet (A through Z). You can have
more than 26 configured connections, but only 26 of those sessions can be active.
If you use 5250 emulation provided by IBM Personal Communications or the PC5250
emulation provided by Client Access for other than Operations Console then those sessions,
telnet for example, count as one each of the maximum 26 sessions.
If you had 20 active consoles and 6 active telnet sessions you have used the maximum
number of emulator sessions. During the course of using these connections, you can close
the emulator for a connected configuration to free up an emulator identifier. The next
emulation session started can then use that identifier.
Another limitation for having multiple connected emulators on the same PC is the amount of
available PC resources, memory and video capability, to support a large number of
connections. Since each connection and associated functions (console, control panel, or both)
will use PC resources, you might need to add more memory to support more connected
sessions. Each PCs hardware, operating system, and active programs vary so that there is no
clear way to identify in advance how many sessions your particular usage supports.
Do I have to be concerned about encryption?

Operations Console network connections use a version of Secure Sockets Layer (SSL),
which supports device and user authentication without using certificates. By default,
Operations Console uses the strongest encryption possible for authentication and data.
62
What do I need to be aware of when planning to install a new release of OS/400 or

i5/OS?
Pre-Power5 processor-based systems using a local console directly attached
Pre-Power5 processor-based systems have a small risk that a release upgrade may fail
when upgrading to V5R3 or later from an earlier release. See Pre-Power5 processorbased systems using a local console directly attached on page 71 for details.
All systems:
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 and Operations
Console using the service tools user ID of 11111111. This prevents any failed reauthentication of the client connection to the system caused by expired user IDs. This
is especially important for automated installations and upgrades.
It is recommended that you update Client Access to V6R1 before you upgrade the
i5/OS operating system.
Note: Failure to comply with the above actions may prevent the console from working
correctly during the upgrade or installation.
Important: During a manual IPL of the system and if no console has been specified
before, you receive two additional displays to confirm the setting of the console type.
The first requires that you accept your current console type, and the second shows that a
value did not previously exist (a zero is present for the old value) and the new value is
shown. Press Enter to exit and set the console type automatically. The IPL then continues
to the IPL or Install the System display. This condition is most likely to occur during the
installation of a new partition, but it can happen on your first manual IPL, for example,
during the A-mode IPL following the restore of Licensed Internal Code, or during the
upgrade or installation when a console value of zero is found.
What do I need to be aware of when planning to upgrade my system to another

model?
If you are migrating from a different console type to Operations Console on your new
system, it is important that you configure your new Operations Console PC before beginning
the upgrade. The Operations Console features that match the connectivity you plan to use
should be specified as part of the order for your new system. In this way, at the point in the
upgrade instructions where console functions are required on the new system, you can
perform them on your new Operations Console device.
63
Also, when migrating a former load source device that was used with Operations Console
local console on a network (LAN) configuration, and this load source device is to become a load
source device in a new partition, the LAN adapter must be deallocated before removing the
device from the old partition and installing it in the new partition.
When you upgrade your system, a change in system serial numbers could prevent the client
from answering the BOOTP request if you are relying on this method to configure the
service host name on the new system.
If the result of your system upgrade includes a Hardware Management Console (HMC),
make sure to use this as the system console until your upgrade is complete. Because some
upgrades are staged, your intended console might lack the necessary resources for a period of
time. Because the HMC uses virtual resources, you will not have problems with a lack of
resources for another console type.
How does the system determine what the console or console's resource should be?
Only the configured console type is supported.
If no console type is specified, such as when a new partition is being created, the supporting
hardware tagged by the HMC is used.
If there is no HMC, then the console is determined by any eligible adapters by location.
If more than one eligible adapter is found, then the first connected device determines the
console. In the case of a server without an HMC, for example, if you use Operations Console
(Direct) and you have a LAN adapter that is available to support a console, and has a valid
configuration, then the console is the directly attached PC. However, the LAN adapter is
started at IPL time and the connecting PC, one or multiple, displays the Console Information
Status window. The field Take over the console displays NO and the message at the bottom of
the window indicates that this device is not the supported console type.
Every time the system has to determine what to activate for a console, either during an IPL
or on demand using the console service functions (65+21) or OPSCONSOLE macro, the
system checks for a tag.
If the system is partitioned there has to be a tag. The tag would point to a console resource
and is converted to a console type value. This value is then saved for use later, if needed.
If there is no tag involved, when the system is not partitioned, a check is made to determine
if the system has a console type defined. If so, a check is made to determine if the user has
designated a particular slot location for the supporting resource.
If there is one then it is activated. If not, then a search is performed to determine the
resource and activate it.
64
If there isn't a console type defined, such as a D-mode to install a new partition, then the
system will activate all eligible console resources and use the first connected device for the
console. An attempt to save this data is made but in the case where a recovery is in progress
and the load source wasn't able to be copied, a new load source doesn't yet have structure
(provided by the initialize function) so the save will be aborted. Then, after the Licensed
Internal Code has been restored and the system IPLs again you will receive windows in
which you will be forced to accept the current console type and the data is saved.
Do I have to dedicate a resource to the console?

The service interface is typically a single adapter used for service tools. For a local console
that is directly attached, if there is no network adapter selected, either by location or partition
tagging, then this is the service interface. More commonly it is a network adapter to support
either a local console on a network or the service tools server. In the case where there is a
valid network adapter available, even if another console is selected and there is a valid
service host name associated with the adapter, then this is the service interface. It can support
a console, the service tools server, or both.
Occasionally the console is not connected using this network adapter, but the service tools
server is configured to support the Navigator interface for hard disk drive configuration or
similar functions.
With Version 6 Release 1, the service interface can be shared with a line description, thus
sharing the same interface. This works only when the Host Ethernet Adapter, 5706/5707, or
5767/5768 is supporting the service interface. It is possible to have a local console that is
directly attached using a 2793 adapter, for example, and a 2849 network adapter configured
for the service tools server. Each adapter is dedicated to support its respective function and is
not available in the operating system.
If you were to use the Host Ethernet Adapter in the previous example, the 2793 is dedicated
but the service tools server running on the Host Ethernet Adapter can be shared with the
operating system.
65
If I use a local console on a network (LAN) what should I take into consideration
if I have to recover my system?
New servers and partitions are most likely using distribution media from IBM and therefore,
the only service tools device ID available is QCONSOLE.
If you need to perform a recovery installation of a server or partition with the initialize
option (scratch installation) and are using IBM distribution media, you only have
QCONSOLE available.
If you elect not to use QCONSOLE, or the configured connection (at the PC) is using a
different service tools device ID, then you might need to delete and re-create the
configuration so that QCONSOLE can be used.
If the system and PC client both run V6R1 then, by default, the autocreate service tools device
ID function is enabled and the connection will automatically negotiate a usable service tools
device ID if the configured connection is already configured to use QCONSOLE.
Consider the following based on your server's configuration:
Servers without an HMC or pre-Power5 processor-based primary partitions
The only scenario where the value is not set is after a load-source hard-disk-drive
replacement without a good copy from old to new.
If this is the case, then all eligible adapters, by location, can support a console, except
LAN.
If LAN is the only available connectivity and the restoration media is not a SAVSYS,
then you might need to use the control panel to perform the console service functions
(65+21) to change the console type value. For more information, see use the console
service functions (65+21) on page 232 for details.
Logical partitions
When a logical partition is initially set up, you have to specify the Console tag, an IOA or
IOP (IOP in the case of pre-Power5 processor-based systems) for console and, in the case
of local consoles that are directly attached, the Operations Console tag. The system uses
this information to search for a console. Only this resource is activated and the system
uses the first connected device as the console to restore the Licensed Internal Code
(LIC). The data used to restore the LIC determines if you need to set the console type
value following the restoration of the code. You can also get a display asking for
confirmation for selecting the console type value.
If needed, you can use this console to change to another console.
If the console fails to connect, you can use the HMC command window, if an HMC is
present, to tag another resource and then use the console service functions (65+21) to
specify a different console type value, if needed. For more information, see use the
console service functions (65+21) on page 232 for details.
66
What is the service tools server and what should I know about it?
If you use Operations Console (LAN), you must create a service host name (interface). After
this is created, the server is also ready to use the service tools server to support, for example,
iSeries Navigator functions. However, you can have a network adapter for the service tools
server when the console is something other than Operations Console (LAN). To do this, you
need to configure the service host name (interface) so that the service tools server uses that
connection. With a configured network adapter available at IPL, the system activates the
adapter that supports the console, but also activates the adapter used for the service host
name, if different. In this scenario, you now have two resources in your system that might
not be used by the operating system, depending on your hardware. Conversely, if you
previously had a service host name for iSeries Navigator and are now using Operations
Console (LAN), you do not have to make any IP configuration changes because the same
resource is used. In other words if you use a local console on a network (LAN) you
automatically have access to the service tools server.
Note: If you do not use Operations Console (LAN) as your console, you might have to
temporarily change the console type value and Console tag to configure a LAN adapter for
use as the service tools server. After the configuration is complete, you are able to revert the
console type value and any tagging back to the original values.
What if I use a local console on a network (LAN) and have more than one device
connecting at the same time?
If you use Operations Console (LAN) with multiple PCs configured to become the console, all
of these PCs are actively connected at IPL time. There is no way to know which PC will
become the console because the first one connected will be the active console.
If you enabled the console option, Allow console recovery and console can be taken over by
another console, then you are able to take over the console at the PC you want to use.
What do I consider if I have multiple console devices with multiple systems?

Consider the following when considering multiple consoles and multiple servers:
Local console on a network (LAN)
Operations Console allows multiple LAN connections to a single server, but only one
5250 session can have control of the server at a time. An active console is a
command interface to a server (5250 emulation) that is currently interacting with the
server. More than one Operations Console device can have data on the window, but
only one is truly active.
A single PC can have multiple active connections to one or more servers or
partitions.
67
or local console directly attached with remote access allowed

The client (PC) only supports one local console that is directly attached or one local
console that is directly attached with remote access allowed for a single PC. Also, if the
PC being used as a local console that is directly attached with remote access allowed is
also a remote console to another server, only one outgoing asynchronous connection
is allowed at a time. You have to disconnect the local console that is directly attached to
connect as a remote console.
The server only supports a single incoming directly attached connection.
Local console directly attached
You can mix both connectivities, directly attached and LAN, at the same time on the same
PC if you follow the preceding guidelines.
Operations Console, twinaxial console and even an HMC can coexist. It might be best if you
use the HMC as the emergency console since switching to an HMC is a very simple process
and can even be performed without an IPL in nearly all cases.
Do I have to be aware of IOA/IOP placement?

Do not place your console adapter on the same IOP as storage devices. Having a dedicated
IOP for the console adapter and one for the storage devices reduces possible connectivity
problems. For example, during very heavy usage of storage devices, the console might
appear to stop working temporarily. If this happens, it should resume operation shortly.
If you must place the console adapter on shared resources, keep the other usages to a
minimum for better console reliability. Also, enable the console option Allow console recovery
and console can be taken over by another console.
How does the system handle adapter activation when multiple console types are
available?
When a server is not managed by an HMC, it is possible to have more than one console
adapter available for activation. For example, the console type is set to Operations
console(LAN) and has a device connected that is the system console.
If an Operations Console (Direct) adapter is also activated, the corresponding device can also
connect at the same time. However, this device cannot become the console and only displays
the Console Information Status window. Each of the adapters are dedicated to their designated
function and are not available for use in the operating system.
The console service functions (65+21) and the OPSCONSOLE macro have support to
designate a particular adapter which solves these issues.
68
Pre-Power5 processor-based systems

Pre-Power5 processor-based - All systems
What considerations do I take into account for IOPs?
Try to avoid putting your Operations Console on the same IOP as storage devices.
There might be configurations when this cannot be avoided.

During very heavy usage of storage devices, the console might appear to stop
working temporarily, but it should resume operation shortly.
If the console is placed on the same IOP as the storage devices, enable the console option
Allow console recovery and console can be taken over by another console.
Multiple IOPs capable of supporting a console workstation can interfere with the
selection of the desired LAN adapter. Consider the following:
Having a second IOP on the bus before your intended console adapter card, when the
first IOP contains a twinaxial adapter card, may fail to provide a LAN-connected
console. For example, a model 890 uses eligible card locations C04, and C06 through
C10 and if an IOP were placed in C08 and a twinaxial adapter preceded this IOP on
the bus then the LAN adapter card located at C09 or C10 will fail to provide a LANconnected console. The LAN adapter card must be in a location preceding the second
IOP, such as C06 or C07.
Typically, the card location used for Operations Console directly attached
configurations, commonly referred to as the Electronic Customer Support (ECS) slot, is
located close to the beginning of the bus. When the card location is a low number, for
example C02, then C03 is further from the beginning of the bus than C02. When the
card location is a high number, for example C07, then C06 is further from the
beginning of the bus than C07. There may be exceptions to this numbering scheme
based on specific models and expansion units. Contact your service representative if
you have questions about the placement of the ECS.
69
What considerations do I need to know about a backup console in a recovery

action?
When planning the configuration of the backup console or consoles remember that
recovering from the loss of the console depends on many factors. Some of these factors
include, the model and series, the hardware resources available, the previous console type,
and the intended console type. Recovery might consist of repairing the currently failed
console or temporarily replacing it with another console type. Most changes of a console
type can be performed without the need for an IPL but there may be circumstances in which
an IPL will still be necessary. When using the console service functions (65+21), consolesupporting hardware must be installed and available prior to performing the function. Any
partition tagging of resources must also have been done already.
Important: If you plan to use Operations Console local console on a network (LAN) as a
backup to another console type, the network adapter must be located in a console designated
slot or in a properly tagged IOP. If not previously configured, the BOOTP process is used to
configure the system.
What should I consider for a backup console?
If you access your system remotely, consider off-site console capability or another type
of connectivity for the console. A local console on a network can be backed up with an
additional local console on a network PC. If the network adapter were to fail, consider a
Local console directly attached to the system as a backup.
In a logical partition or multiple-system environment, you will most likely be using

multiple local consoles on a network (LAN) configuration on a single PC as your
primary consoles. Consider additional PCs using this same type configuration. Avoid
supporting too many consoles on the same PC if possible. The PC resources can be easily
overwhelmed when supporting multiple consoles and remote control panels.
Consider multiple local console on a network configurations in large environments so

that each PC has a core set of console responsibilities and the overlap coverage of backup
configurations with each other. For example, if you have a PC that supports 10 local
consoles on a network configuration and another PC with the same number of primary
consoles for another 10 partitions, instead of backing up each PC with the other's
configuration, you add a third PC and spread the 20 consoles out so that two PCs back up
a portion of each PC's primary console configurations. Another consideration is a
dedicated PC to be the backup of a certain number of consoles, but not connected until
necessary.
70
When you mostly use consoles on a network, consider setting up a Local console directly
attached to the system on a PC and place it on a rollaway cart with a console cable.
If you have supporting adapters, you can quickly roll the cart with the PC near the
system or partition in need of the console. After connecting the cable and changing the
console type value, you have a console to replace the currently failed console. This same
concept also applies to twinaxial workstations.
If more than one local console on a network is planned, be certain to create additional
service tools device IDs on the system before you start configuring the Operations
Console PC. Each PC connecting to the same target system or logical partition must have
a unique service tools device ID.
In summary, consider incorporating as much redundancy as possible into your console

configuration. You can reduce your exposure to a catastrophic console failure by using
another method to provide a console in place, or by making compromises and adjustments
for the various hardware requirements necessary to overcome the various levels of failures.
Pre-Power5 processor-based systems using a local console

directly attached
If your system has a 2771 adapter card in the processing unit and you plan to use
Operations Console as either your primary console or as a backup console, it must be
installed in the location designated by model for cable connections based on the
following table, prior to the upgrade or installation. Each model has a different preferred
location:
Pre-Power5 processor-based - Non-partitioned systems

Can I place a console resource anywhere in my system?
Console supporting hardware may be required to be located in specific slot locations,
based on model. Refer to Chapter 1: Reference on page 19 for locations based on your
system's model.
71
What do I need to know regarding any recovery actions?

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.
Pre-Power5 processor-based - Partitioned systems

What tags do I have to use for console?
Models 8xx are tagged for a console type only at the IOP level. Tagging an IOP that has
two similar console adapters reporting to it (for example, two 2849s or two 2771s) for
the same IOP can sometimes make it difficult to determine, in advance, which adapter
will be used for the console. When tagging the IOP, make sure that it only has one
console-capable adapter per connectivity (for example, only one 2849 and one 2771).
Each adapter can support a different console type but only one adapter type should be
present. The lowest addressed adapter on the bus is attempted first. But if that adapter is
slow in reporting to the system, another adapter might get selected instead, when two
adapters of the same connectivity are present. 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.
If you plan to use Operations Console as your primary console or as a backup console,
you must tag the IOP to support the primary console and Electronic Customer Support
(slot), even if you do not plan to use Electronic Customer Support. For example, if you
are planning to use Operations Console on a direct connection, you must tag an IOP with
the Console tag and the ECS tag. These steps are also necessary if you are planning to use
Operations Console with a LAN connection.
What do I need to know about multiple adapters for consoles?

When more than one console adapter is available for a single IOP, the adapter with the
lowest bus address will be chosen for use by Operations Console. For example, you tag
an IOP that has two LAN adapters installed. The system will use the first adapter found
on the bus. However, during an IPL the first adapter may not be ready in time and the
system could select the second adapter. This could prevent the console from starting
immediately or you might not be able to use that resource for your 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.
72
Power processor-based Systems - Common information

Power-processor-based Systems - All systems
5767/5768 and 5706/5707 adapters
The 2-Port 10/100/1000 Base-TX Ethernet PCI Express Adapter (5767), 2-Port Gigabit
Ethernet-SX PCI Express Adapter (5768), PCI 1 Gbps Ethernet TX IOA (5706), and PCI 1
Gbps Ethernet SX IOA (5707) do not require an IOP and are available for use with the
Operations Console. When using these adapters, you can locate the LAN adapters in any of
the remaining slots, specific to the adapter, on your server if your server supports this type of
operation and is managed by an HMC.
If the system is not managed by an HMC, the LAN adapter must be located in one of the
designated card locations that supports a local console on a network (LAN). Only the first port
of this adapter can be used for the console. The first port is the top port or the right-most
port.
If you elect to use this adapter instead of the default embedded Ethernet port, you must
disable the embedded port before the system can use the adapter. To disable support for the
default embedded Ethernet port, see disable support for the default embedded Ethernet port,
5706/5707, or 5767/5768 adapters on page 255.
2793 and 2742 asynchronous communications adapters

The 2793 and 2742 asynchronous communications adapters no longer require an IOP when
the system is running V5R4M5 or later of Licensed Internal Code.
73
Power Systems - Not HMC managed

What considerations do I take into account if I want to use a 5706/5707 or
5767/5768 (Power6 processor-based only) adapter instead of the embedded port?
When a server is not managed by an HMC, by default, the embedded port and external
adapter support are both enabled. In order to use the external adapter you first have to
disable support for the embedded port. When the embedded Ethernet port is disabled, the
console-supporting hardware is required to be located in specific slot locations based on the
server model. For Operations Console (LAN), there might be more than one location that can
support a console. When more than one location is available for a server model, the locations
are listed from highest priority to lowest priority when the console searches for consolecapable hardware resources. The console service functions (65+21) on page 232 and the
OPSCONSOLE macro on page 215 have support to designate a particular adapter. You can
also use the OPSCONSOLE macro or the console service functions (65+21) to disable this
support.
Also, the 5706/5707, 5767/5768, 2793, or 2742 adapters are able to run without an IOP. If
you do not want to use the embedded Ethernet port, a 5706/5707, or a 5767/5768 adapter for
the console, you can disable this option by following the steps in disable support for the
default embedded Ethernet port, 5706/5707, or 5767/5768 adapters on page 255. For more
information on either of these options, see use the OPSCONSOLE macro or use the console
service functions (65+21) for details.
How does the system know which resource to use for the console when there isn't
an HMC?
When a server is not managed by an HMC the system relies on a specific set of "rules" to
determine what resource will be used. By default, the embedded Ethernet port would be
used. However, you can disable this port so you can use a different adapter. Just disabling
the embedded Ethernet port forces the system to look at one or more specific locations for a
console-supporting resource. In the tables above, based on platform and model, the locations
are listed in the order the system searches for an appropriate resource. The first supporting
resource is then selected.
74
Depending on your model and level of Licensed Internal Code you may be able to designate
a specific resource which allows a little more flexibility in case you need a second or third
adapter of the same connectivity for non-console use. The embedded Ethernet port support
is one flag and the use of a 1 Gbps adapter (5706/5707, 5767/5768) is another. For example,
if you disabled both flags and still wanted to use a local console on a network (LAN) you would
need to supply an adapter like the 2849 driven by an IOP. You could then use an external
5706/5707, which is a higher speed adapter, for another purpose and the slower 2849 would
be dedicated to the console. The console service functions (65+21) and the OPSCONSOLE
macro have support to also designate a particular adapter and enable or disable the flags.
By following the steps in disable support for the default embedded Ethernet port, 5706/5707,
or 5767/5768 adapters on page 255, you can enable or disable one or both flags. For more
information on either of these options, see use the OPSCONSOLE macro on page 215 or use
the console service functions (65+21) on page 232 for details.
If you use V5R4M5 (or later) of Licensed Internal Code you can access this support using
the Select Console window, as shown here:
Select Console
System:
Console type . . . . . . . . . . . . . . . .
1. Twinaxial
. . . . . . . .
Allow
be
Allow
be
75
1=Yes, 2=No
supported internal LAN adapter to

the console . . . . . . . . . . . . . . . 1
supported Gigabit LAN adapter to
the console . . . . . . . . . . . . . . . 1
Press enter to continue.

F3=Exit
F12=Cancel
S10BACFC
1=Yes, 2=No
1=Yes, 2=No
What if the system has two or more adapters of the same connectivity?
Multiple console-supporting adapters on servers without an HMC, and without an enabled
embedded Ethernet port if a local console on a network (LAN) is to be used, might interfere with
console selection. Consider the following:
The server attempts to use the first, or only, console IOA based on the current console
type value.
If your server model supports a second adapter location for LAN and has a LAN adapter
installed, a problem with the first adapter might cause the server to use the second LAN
adapter for the console, making it unavailable for use by the operating system.
Selection of a specific adapter location is possible on select models prior to V5R4M5.

These PTFs allows you to specify the asynchronous communications adapter used for a
local console directly attached.
Starting in V5R4M5 most models have the ability to designate the adapter associated
with a local console directly attached and local console on a network (LAN).
If designating a network adapter, selecting a card slot, then support for the embedded
Ethernet port has to be disabled before the external adapter can be used. See disable
support for the default embedded Ethernet port, 5706/5707, or 5767/5768 adapters on
page 255 for details.
76
How do I specify which adapter to use for console when more than one is
available?
If you have an IBM System i5 or eServer i5 520, 525, or 515 model, your system (running
V5R3M5 or V5R4M0 of Licensed Internal Code) can have asynchronous adapters located in
multiple slots simultaneously, including locating the 2793 asynchronous adapter in slot C4.
Slot C4 allows an IOA that does not require an IOP. This is possible only for systems that
are not managed by an HMC and have an input/output adapter (IOA) that does not require an
input/output processor (IOP). To allow for this greater flexibility on the 520, you must install
PTF MF39303 (V5R3M5) or PTF MF39304 (V5R4M0). These PTFs should already be
installed on the 525 and 515.
With these PTFs, you are able to select an individual asynchronous adapter for use with the
console and remote service by using either the OPSCONSOLE macro or the console service
functions (65+21). The console and remote service functions must all remain on a single
asynchronous adapter.
If you have a system that was shipped with Licensed Internal Code (LIC) prior to V5R4M5,
you cannot select slot C4 for use with the console when using the 2793, but you can select
slot C4 for use with remote service.
Example: If you have an asynchronous adapter located in both C2 and C3 for use by
Operations Console (Direct), you can choose to use either slot for console and remote service,
without having to remove the asynchronous adapter from the other slot.
Starting in V5R4M5 all models have the ability to designate the adapter associated with a
local console directly attached and local console on a network (LAN).
For a local console directly attached you can use the macro:
OPSCONSOLE ENBSLOT <1 - 5> depending on model
Also available using the console service function 65+21+Fn
For a local console on a network (LAN) you can use the macro:
OPSCONSOLE ENBLSLOT <1 - 5> depending on model
Also available using the console service function 65+21+Bn
If designating a network adapter, selecting a card slot, then support for the
embedded Ethernet port has to be disabled before the external adapter can be
used. See disable support for the default embedded Ethernet port, 5706/5707, or
5767/5768 adapters on page 255 for details.
77
To disable either the embedded Ethernet port or add-on 5706/5707 adapters using
V5R4M5 (or later) of Licensed Internal Code, complete the following steps:
1. Access service tools using DST or SST.
1. If you are using DST, select Work with DST environment, and then
System devices.
2. If you are using SST, select Work with service tools user IDs and
devices.
2. Select Select Console.
3. Type a 2 in either the Allow supported internal LAN adapter to be the console
or Allow supported Gigabit LAN adapter to be the console field, depending on
what you want to disable.
4. Press Enter.
The example below shows how to set up a Power5 processor-based or Power6
processor-based system to use an external adapter instead of the embedded or
HEA/IVE port.
Select Console
System:
Console type . . . . . . . . . . . . . . . .
1. Twinaxial
. . . . . . . .
Allow
be
Allow
be
78
1=Yes, 2=No

the console . . . . . . . . . . . . . . . 2
the console . . . . . . . . . . . . . . . 1

F3=Exit
F12=Cancel
S10BACFC
1=Yes, 2=No
1=Yes, 2=No
If you do not have a working console device, but you have another workstation that can
access System Service Tools (SST), then you can use the preceding DST/SST procedure or use
the OPSCONSOLE macro on page 215, to disable your intended resource.
If you do not have any working devices, then you must use the console service functions
(65+21), on page 232. You can also use either of these methods to re-activate support for
these resources.
Can more than one console supporting resource be activated at the same time?
Power-processor-based Systems - HMC managed

What do I tag for console using the HMC?
IBM System i5 and eServer i5 models with an HMC support tagging at an IOP or IOA level.
There are advantages and disadvantages to tagging either the IOP or the IOA.
First, some background on how the system determines what console to use when the system
is HMC managed. The system starts this process by first looking at the tag and blindly
setting the console type to match the supported adapter.
If you try to change the console type and have an IOA tagged you get back an error that
there isn't any supporting hardware. The system only knows to use the resource tagged.
Determining the console happens during an IPL, obviously, but this process also takes place
when other console-related activity is performed such as a 65+21+21.
If the tag is to an IOA this is a predictable function.
If you tagged an IOP and had both a console-supporting network adapter, in addition to an
asynchronous communication adapter, the system selects the first detected and eligible
adapter to determine the console.
If for some reason the adapter reporting first were to be delayed the system would select the
other adapter and would set the console type to the wrong value. The result is no console
and a very puzzled user.
79
Another fact you should know is that tagging at an IOP level may reserve one or more
console-supporting adapters. For example, you use a network resource for the console but
have an asynchronous communication adapter associated with that same IOP. As part of the
console detection function the system may reserve the asynchronous adapter for use by a
console in case you want to make a quick change in the console device. When the operating
system tries to use this resource you might find that it won't vary on because it's in-use.
But tagging at the IOP level is still desirable if you only associate one network adapter and
one asynchronous communication adapter to it. To fall back from one console type to
another only requires a change of the console type. This works fine except that you may end
up dedicating the other adapter to possible console functions.
If you need to change the console type, you can make the change without an IPL in most
cases. You can use the HMC command window to specify the tag. This allows the change to
be used immediately, although you might have to force the system to determine the new
console in some instances. This can be performed using the same command window, using
the OPSCONSOLE macro, page 215, or use the console service functions (65+21) page
232. For more information on how to change the console, see Changing consoles - Powerprocessor-based on page 109 for details.
For more information about making console type changes without an IPL, see Completing a
console change with the logical partition and managed system powered on on page 119 for
details.
Which tags do I have to be aware of with Operations Console?

Consider the following when determining what to tag for Operations Console:
Operations Console (LAN)
If you use a LAN-based PC for your console, the only tag you need to set is for console.
Operations Console (Direct)
If you use a direct cable attached PC for your console, you need to specify the tag for
Console and Operations Console. The Operations Console tag is the equivalent of the former
Electronic Customer Support (ECS) tag.
The Operations Console tag is required if you are using a directly connected console, if you
are configuring for a directly connected backup console, or if you are using an asynchronous
communications adapter for remote service. Tagging the IOA allows you to select the
specific adapter used for the Operations Console. Therefore, if multiple console-capable
adapters exist in the IOP, only the selected console-capable adapter is used for the console.
The tag automatically sets the console type during the next activation following the partition
profile update. An IPL will not read the changed partition profile.
80
You can use the HMC command window to specify the tag. This allows the change to be
used immediately, although you might have to force the system to determine the new console
in some instances. This can be performed using the same command window, with the
OPSCONSOLE macro, page 215, or using the console service functions (65+21), on page
232. For more information on how to change the console, see Changing consoles - Powerprocessor-based on page 109 for details.
console change with the logical partition and managed system powered on on page 119 for
details.
Power5 processor-based Systems Specific

Power5 processor-based - Non-partitioned systems - Not
managed by a Hardware Management Console (HMC)
What is the default local console on a network (LAN) resource?
Operations Console now defaults the first embedded Ethernet port as the default console port
in systems not using an HMC. This includes the 5706/5707 adapters. However, the server
will not check for the 5706/5707 adapter unless support for the default embedded Ethernet
port has been disabled. Support for the default embedded Ethernet port is disabled in
manufacturing for systems where the embedded ports do not exist, for example, the
9406-595. To disable support for the default embedded Ethernet port or 5706/5707 adapters,
see disable support for the default embedded Ethernet port, 5706/5707, or 5767/5768
adapters on page 255 for details.
81
Power6 processor-based Systems Specific

Power6 processor-based - All systems
What is the default local console on a network (LAN) resource?
What is the Virtual Ethernet (IVE) - Host Ethernet Adapter (HEA)?
Operations Console now defaults the first Integrated Virtual Ethernet (IVE) port as the
default console port in systems not using an HMC. The IVE can also be referred to as the
Host Ethernet Adapter (HEA) in some documentation and these terms can be used
interchangeably. This document may just use the term embedded Ethernet port. In this
context it means the first port on the first physical port or the logical port reserved for the
console when the IVE was configured for the partition.
When working with IVE (HEA) on a system without an HMC, the top, or right-most, port is
the default port for console.
Consider the following regarding the IVE:
The IVE is available in two versions: 2-port and 4-port
Each Host Ethernet Adapter physical port supports a maximum of 16 logical ports.
A 2-port Host Ethernet Adapter supports a maximum of 16 logical ports, because
both ports share a single cable group.
If there are four ports, then two ports share the 16 logical ports for each port
group for a total of 32 logical ports. Each logical partition can have one logical
port for each physical port, and you cannot assign a logical port number to a
physical port or logical partition. You can assign the logical port ID to the
physical port, but the system assigns the actual port number.
Some systems can have up to four Host Ethernet Adapter ports, one for each drawer.
Partitions using Host Ethernet Adapter resources cannot be migrated.
See What is the default for a local console on a network (LAN) resource below for using the IVE in
a non-partitioned environment.
82
Power6 processor-based - Non-partitioned systems

What is the default for a local console on a network (LAN) resource?
Operations Console now defaults the first Integrated Virtual Ethernet (IVE) port, also known
as the Host Ethernet Adapter (HEA), as the default console port in systems not using an
HMC. The IVE can also be referred to as the Host Ethernet Adapter (HEA) in some
documentation and can be used interchangeably. In this document it may be referred to as
the embedded Ethernet port.
When working with IVE (HEA) on a system without an HMC, the top, or right-most, port is
the default port for console.
Consider the following regarding the IVE:
1. The IVE is available in two versions: 2-port and 4-port
2. Each Host Ethernet Adapter physical port supports a maximum of 16 logical ports.
3. A 2-port Host Ethernet Adapter supports a maximum of 16 logical ports, because
both ports share a single cable group.
4. If there are four ports, then two ports share the 16 logical ports for each port group
for a total of 32 logical ports. Each logical partition can have one logical port for
each physical port, and you cannot assign a logical port number to a physical port
or logical partition. You can assign the logical port ID to the physical port, but the
system assigns the actual port number.
5. Some systems can have up to four Host Ethernet Adapter ports, one for each drawer.
Partitions using Host Ethernet Adapter resources cannot be migrated.
If you do not want to use this resource for your console and would rather use an adapter
located in a card slot you must disable the embedded support. To disable support for the
default IVE port, see disable support for the default embedded Ethernet port, 5706/5707, or
5767/5768 adapters on page 255 for details.
83
Power6 processor-based - Partitioned systems

What do I have to know about servers with an HMC?
A Host Ethernet Adapter logical port or an input/output adapter (IOA) must be tagged for
console with a Hardware Management Console (HMC) if you will be using a console other
than the HMC. For more information, see What do I have to know about tagging a Host Ethernet
Adapter logical port or IOA for the console below.
What do I have to know about tagging a Host Ethernet Adapter logical port or IOA
for the console?
Consider the following when determining what to tag for Operations Console:
Operations console(LAN)
If you use a local console on a network (LAN), the only tag you need to set is for console.
Operations console(Direct)
If you use a direct cable attached PC for your console, you need to specify the tag for
Console and the Operations Console tag.
The Console tag requires that you specify a Host Ethernet Adapter logical port or an IOA.
The Operations Console tag is required if you are using a local console directly attached for your
console, if you are configuring for a directly connected backup console, or if you are using
an asynchronous communications adapter for remote service.
You can tag a Host Ethernet Adapter logical port for the console in the partition profile.
When doing this, you are actually tagging a physical port of the Host Ethernet Adapter and
using the assigned logical port.
Tagging the IOA allows you to select the specific adapter used for the Operations Console.
Therefore, if multiple console-capable adapters exist in the IOP, only the selected consolecapable adapter is used for the console. Tagging the IOA in the partition profile
automatically sets the console type during the next activation following the partition profile
update. An IPL will not read the changed partition profile.
You can also use the HMC command window to specify the tag. This allows the change to
be used without the need to power off the server or perform an IPL, in most cases. For more
information about how to change the console, see Changing consoles - Power-processorbased on page 109.
console change with the logical partition and managed system powered on on page 119.
84
Power6 processor-based Blade and Power6 processor-based

systems running VIOS/IVM
What do I have to know about Power6 processor-based blades and systems
running VIOS/IVM?
Power6 processor-based blade servers that have partitions only support a local console on a
network (LAN). Depending on how the IBM BladeCenter is configured, when you create the
partition, you may not have as many choices regarding the logical network ports. It is critical
that the Host Ethernet Adapter has been set to be bridged, as shown here:
>> Select the resource

(usually the resource showing zero in Available Connections) >> Properties
View/Modify Host Ethernet
Failure to have this bridged will prevent the client PC to configure the partition during the Dmode IPL to restore Licensed Internal Code.
85
View/Modify Virtual Ethernet
>> Click the Virtual Ethernet Bridge tab
A resource must be defined here, as well, or the system will be unable to connect to the network.
Operations Console is configured and managed the same as any other system with a local console
on a network (LAN). for information regarding the installation and setup of the blade server see
the on-line Information Center under Systems hardware >> BladeCenter information >> Blade servers
>> select your blade server. For information regarding Operations Console information not
covered in this document should be in the on-line Information Center under Systems hardware >>
System i information >> Managing consoles, interfaces, and terminals >> Managing i5/OS consoles >>
Managing Operations Console.
http://publib.boulder.ibm.com/infocenter/systems/index.jsp?topic=/front/hwparent.htm
86
RCP & VCP

What is a RCP or VCP?
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 console when directly attached or by way of a network connection. The virtual
control panel allows you to perform most of the control panel functions from a local location
but connects using the console's serial cable to remove the need for a network adapter.
If you are using a pre-Power5 processor-based system and the remote control panel
connection is with a separate serial or parallel cable (V5R3 only on pre-Power5 processorbased systems) then you have access to the system to include powering it on from the client.
A network connected RCP or VCP cannot power on a system or partition.
Use the configured connection's Properties > Configuration to add, remove, or validate the
RCP.
What type of restrictions am I likely to encounter?

The user must be granted access to a partition's remote control panel and functions to use the
remote control panel or virtual control panel.
If a local console on a network is being used, then the service tools device ID must also be
granted access to that partition's remote control panel to use this feature. By default, usercreated user IDs will have these permissions.
By default, service tools device IDs may not be automatically granted access to the remote
control panel for the partition. But access can be granted by an administrator for the user ID,
device ID, or both. The user that authenticates a connection must also have authority to the
respective partition's keylock to change the mode. This varies by release so check the
service tools device ID that will be used to verify it has access to this function.
Note: Starting with V6R1, the system is set to automatically create service tools device
IDs by default. However, these auto-created service tools device IDs do not
automatically have access to the remote control panel functions so you may be required
to manually grant this access. Also, if the service tools device ID gets reset, either
manually or automatically by the system access to the remote control panel functions will
be reset back to revoked.
87
Any configured connection that includes the remote control panel option and the device ID is
not authorized is temporarily disabled (grayed out) or missing.
1. The remote control panel option is disabled (grayed out) after the first connection if it
was selected but not authorized.
2. The remote control panel option is missing after the first connection if it was not
selected and was not authorized.
After the device ID is authorized, it becomes active or reappears in Properties, on the next
connection.
If you have a server model that uses the keystick, the mode button will work with the same
functions as the physical control panel when the keystick is inserted.
Note: Systems with a keystick require the keystick to be inserted before the user is
eligible to use the mode button. For example, the user has the remote panel key privilege
but will not have the 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.
The service tools user ID used to authenticate the connection must have the partition remote
panel key privilege to use the mode function provided by the RCP or VCP. Service tools user
IDs QSECOFR, QSRV, 22222222, or 11111111 already have this permission by default.
As always, check the online Information Center for more details.
Why did I lose the RCP when I previously had it working?

device ID, grant access to the remote control panel, then at a later time you connect and find
that you no longer have a remote control panel. This is the result of a change in the assigned
service tools device ID. Something occurred, possibly not connecting this device in a few
days for instance, so the service tools device ID got reset. A reset of the device ID includes
revoking permission to the RCP, so you, again, have to manually grant permission to the
RCP. Currently, the only way to prevent this would be for you to create a specific service
tools device ID for this configured connection and delete the previous one. See create a
service tools device IDs on the system, page 239, for instructions on how to do this.
88
What considerations are specific to the virtual control panel?
There is no requirement for a network adapter even though the configuration process
uses the local console on a network (LAN) option.
The VCP requires a unique service tools device ID. You may be required to manually
create the service tools device ID depending on your version of the operating system.
For example, if the system and PC client are both using V6R1 then auto-created service
tools device IDs should automatically create the necessary ID but it won't automatically
grant access to the system or partition. Earlier releases granted this function by default
when you manually created the ID.
The VCP is only available while the console is connected.
You must remove the parallel remote control panel cable, if installed, before configuring
the VCP connection.
You cannot use or reuse an existing network name when you create the additional VCP
configuration. For example, if you have a configuration named SERVER1, you cannot
name the VCP SERVER1. Also, if the intended VCP-capable PC is on a network, you
cannot use any name that already exists on that network.
All VCP and remote control panels are active at the same time.
If you have multiple PCs (LAN connected) that can become the console, one at a time,
and those configurations also use the remote control panel functions, all active RCPs can
control the system. Use care when working with control panel functions when multiple
PCs have access to the functions.
89
Filler page
90
Chapter 3: First Time System Setup

This chapter will set up a system, partition, or Power6 processor-based blade for the first time.
If you have an older system but it's not been in use for you, this is considered new.
If you are changing from your current console to another console type on a PrePower5 processor-based system, go to Chapter 4: Changing consoles - Pre-Power5
processor-based on page 103.
If you are changing from your current console to another console type on a Powerprocessor-based system, go to Chapter 5: Changing consoles - Power-processor-based on
page 109.
If this is a new system, partition, or Power6 processor-based blade it is expected to be powered
off at this point.
If this is not the case use Appendix A. Shutting down systems or logical partitions on page 271
and return here.
If you already have an HMC installed and it is ready for use, continue with Select your
environment on page 92.
Otherwise,
If you will be using a HMC with version 6 code, go to Installing the HMC and create your
partition.
http://publib.boulder.ibm.com/infocenter/systems/topic/iphai/installhmc.htm
Return here when the HMC is installed.
If you will be using a HMC with version 7 code, go to Installation and Configuration Guide
for the Hardware Management Console and create your partition.
http://publib.boulder.ibm.com/infocenter/systems/topic/iphdx/abstract_install_config_hmc_g
uide.htm
Return here when the HMC is installed.
If you are installing a Power6 processor-based blade or system with Virtual I/O Server (VIOS) is not
installed, use the Advanced POWER Virtualization Operations Guide for assistance in installing and
setting up VIOS/IVM. Then, return here.
http://publib.boulder.ibm.com/infocenter/systems/topic/iphdx/sa76-0100.pdf
91
Note: If your system is a Power6 processor-based Blade or is running VIOS/IVM the first partition is
VIOS. Partition 2 is the first user-created partition to support an IBM i operating system.
If you are working with a logical partition, the new partition should be created and powered off,
at this time.
If you are working with a primary partition or standalone system (without an HMC for Powerprocessor-based systems), the system is expected to be powered off, at this time.
Select your environment

Answer questions to help you choose the correct procedure to follow for setting up a new
system, partition or Power6 processor-based blade.
1. Are you installing a logical partition?
Note: If you have a Power-processor-based system without an HMC or without
VIOS/IVM answer No.
1. Yes. Continue to question 2.
2. No. Continue with Select your console - New on page 101.
2. Is the server managed by a Hardware Management Console (HMC)?
1. Yes. Continue with Verify the console tagging on a Power-processor-based system on
page 92.
2. No. Continue with question 3.
3. Are you working with a new logical partition on a pre-Power5 processor-based system?
1. Yes. Continue with Tagging the console for a logical partition on a pre-Power5
processor-based system on page 94.
2. No. Go to Verify console resource setup for VIOS/IVM on page 96.
Verify the console tagging on a Power-processor-based

system
To change or verify the console tag using an HMC, do one of the following based on the HMC type:
HMC using version 6 code
1.
Using the HMC, verify the console device setting for the partition profile.
a. In the navigation area, open Server and Partition.
b. Select Server Management.
c. In the contents area, open the server on which the partition profile is located.
d. Open Partitions.
e. Open the logical partition for the partition profile
f. Right-click the partition profile and select Properties.
92
g.
Click Tagged I/O, verify the Console resource to be used.

If the resource is other than what you will be using, do the following steps to
change the console resource:
i. Clear the current console setting, and click Select or click the check box for
Use HMC console.
If you selected to use the HMC as your console, go to step h.

Expand the list in the I/O devices in the profile area so that the console device
that you want to use is displayed.
iii. Select the console device that you want to use, and then click Select.
ii.
Note: If you selected an asynchronous communications adapter for Operations

Console (Direct), you must also select the same asynchronous communications
adapter in the Operations Console field.
Click OK, and then click OK again.
2. Continue with Select your console - New on page 101.
h.
Using HMC using version 7 code

1. Using the HMC, verify the console device setting for the partition profile.
a. In the Navigation area, expand Systems Management.
b. Expand Servers.
c. Select the managed system.
d. In the Contents area, select the partition you will be defining.
e. From the Tasks area, expand Configuration.
f. Click Manage Profiles. This should open the Manage Profiles window.
g. Select the profile you will be working with.
h. Click Actions, and select Edit.
i. Click Tagged I/O
j. Verify the correct console resource shows.
If the resource you would like to use for the console isn't selected, do one the
following:
If you will be using the HMC then click the check box for Use HMC
console, then go to step k.
If you won't be using the HMC then uncheck Use HMC console if it's
checked, then follow these steps:
1. Click Select.
2. If you will be using an adapter card be sure I/O device shows in the
upper left corner of the window. Then, select you resource from the
list. Go to step k.
If you will be using a logical port, such as provided by the IVE
(HEA), then select Logical Port in the upper left corner. Select the
logical port you want to use, then, click OK.
93
k. Click OK.
l. Click Close.
Tagging the console for a logical partition on a prePower5 processor-based system

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.
This work must be performed from the primary partition.

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 place a 1 in front of the IOP to
select it as the console IOP.
8. If you selected a resource to be used with twinaxial console you can use an optional
alternate console (twinaxial console only).
Note: The selection of an alternate console only pertains when twinaxial workstations
are to be the alternate console and the console type is also twinaxial console. The
alternate console must be under a different IOP than the IOP tagged for use by the
primary twinaxial console. Operations Console cannot be used as an alternate console.
Do not tag the same IOP for the console and the alternate console.
If you selected a resource to be used with Operations Console, you must also tag the
same IOP used for the console as the IOP for Electronic Customer Support (ECS).
94
To verify the console IOP for ECS, perform the following steps:
a. Press F12 until you arrive at the Work with partition configuration window.
b. Enter a 9 in front of the partition to be tagged for ECS.
c. Look at the symbols on the same line as the tagged console IOP (the Console tag
is the < symbol) for the ECS symbol, which is the + (the plus sign). If the +
symbol is shown, the IOP is correctly tagged for ECS. Go to step 9.
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.
Press F3 to exit to the DST main menu or SST.
9.
95
Verify console resource setup for VIOS/IVM

Power6 processor-based blade servers that have partitions only support a local console on a
network (LAN). Depending on how the IBM BladeCenter is configured, when you create the
partition, you may not have as many choices regarding the logical network ports. It is critical
that the Host Ethernet Adapter has been set to be bridged, as shown here:Follow these steps to
verify that IVM has a resource capable of communicating on a network:
1. Access IVM to your system or blade.
96
2. Click on the partition name you want to work with
3. Take note of the resource in Console adapter: In this case Virtual Ethernet 1, then close the
window.
4. Click View/Modify Virtual Ethernet.
97
5. Select the Virtual Ethernet Bridge tab.
6. Note the name ent0 (U78A5.001.WIH0036-P1-T6) is what Virtual Ethernet ID 1 shows.

7. Click View/Modify Host Ethernet Adapters.
98
8. Select the resource you just noted, ent0 (U78A5.001.WIH0036-P1-T6).
99
9. Click Properties.
10. Validate Allow virtual Ethernet bridging: is selected. Then close the window.
If this procedure shows all the associations properly, you have a usable resource for your
console.
Operations Console is configured and managed the same as any other system with a local console
on a network (LAN). for information regarding the installation and setup of the blade server see
the on-line Information Center under Systems hardware >> BladeCenter information >> Blade servers
>> select your blade server. For information regarding Operations Console information not
covered in this document should be in the on-line Information Center under Systems hardware >>
System i information >> Managing consoles, interfaces, and terminals >> Managing i5/OS consoles >>
Managing Operations Console.
http://publib.boulder.ibm.com/infocenter/systems/index.jsp?topic=/front/hwparent.htm
Continue with Select your console - New on page 101 and select Operations Console.
100
Select your console - New

If your Pre-Power5 processor-based system is already installed and you are just changing the
console, go to Chapter 4: Changing Consoles - Pre-Power5 processor-based on page 103.
If your Power-processor-based system is already installed and you are just changing the
console, go to Chapter 5: Changing Consoles - Power-processor-based on page 109.
If you will be using Operations Console as your console, go to Chapter 6: Setting up Operations
Console on page 125.
If you will be using twinaxial console as your console, go to Chapter 7: Twinaxial Console on
page 197.
If you will be using a Thin Console as your console, go to Chapter 8: Thin Console on page 201.
If you will be using an HMC for the console, either locally or remotely, go to Chapter 9: HMC
5250 Console on page 207.
If you need to set up ASMI, go to Appendix G. Advanced Systems Management Interface
(ASMI) on page 351.
101
Filler page
102
Chapter 4: Changing consoles - Pre-Power5

processor-based
If you will be changing consoles, it is suggested that you have a current backup of your system
or logical partition (including operating systems, licensed programs, and data). For information
about backing up your system or logical partition, see Backing up and recovering data.
http://publib.boulder.ibm.com/infocenter/systems/topic/iphbl/iphblos400backupandrecovery.htm
Referencing Chapter 1: Reference, on page 19 and Chapter 2: Considerations for planning on
page 59, as needed; verify any required hardware and cabling to satisfy your new console type.
You can also use Appendix D. System Locations for Cards and Cables on page 321 for help in
identifying where the cards or cables will be placed.
The server value QAUTOCFG must be set to ON. Use one of the following to verify or set this
system value on the server:
1. Use the WRKSYSVAL QAUTOCFG command.
2. During a manual IPL, in the IPL Options window, for Set major system options, select Y.
Then for Enable automatic configuration, select Y.
You must unlock the SST option before you can use it. For additional information on SST, see
unlock service tools device IDs in SST on page 248.
If your plan to change the console involves using another workstation to complete some
configurations then be sure to unlock the SST option before starting the change instructions.
Choosing the procedure to change a console - PrePower5 processor-based

Answer questions to help you choose the correct procedure to follow for changing the current
console.
1. Is the system powered off?
Yes. Go to question 8.
No. Continue with question 2.
2. Are you currently using a Local console on a network (LAN) as your console or you use the
service tools server for connecting iNavigator?
Yes. Continue with question 3.
103
3. Do you plan to continue using this resource as a backup console or to facilitate a

connection to the service tools server for iNavigator?
No. Perform the following task to deallocate the resource:
a. Access service tools using DST or SST.
If you are using DST, select Work with DST environment, and then System
devices.
If you are using SST, select Work with service tools user IDs and devices.
b. Press F6 to clear the old values, and then F7 to store the new values.
c. Press F3 or F12 to exit.
d. Continue with question 4.
4. Are you performing this work on a Power-processor-based system?
Yes. Go to Chapter 5 - Changing consoles - Power-processor-based on page 109.
5. Did you just make hardware changes to a pre-Power5 processor-based logical partition
with power on?
Yes. Go to Tagging a pre-Power5 processor-based logical partition for console on
page 105.
6. Is the target console resource managed by the same IOP as the current console in a
logical partition,
or
the resource is correctly located in a card slot on a primary partition or standalone
system?
Yes. Go to Select your console - Pre-Power5 processor-based on page 107.
7. Do you plan to make your changes with the power off?
Yes. Go to question 8.
No. Go to Remove and replace procedures in the on-line Information Center. Return
to Choosing the procedure to change a console - Pre-Power5 processor-based
question 1, above, when the hardware changes are complete.
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/topic/rzar5/rzar5rip.htm
8. Are you working with a logical partition?
Yes. Go to Changing hardware on a pre-Power5 processor-based logical partition
with the power off directly below.
No. Go to Changing hardware on a pre-Power5 processor-based primary partition or
standalone system with the power off on page 107.
104
Changing hardware on a pre-Power5 processor-based

logical partition with the power off
1. Referencing Appendix A. Shutting down systems or logical partitions on page 271, as
needed, power off the system.
2. Referencing Chapter 1: Reference, on page 19 and Chapter 2: Considerations for planning
on page 59, as needed; add, remove, or replace any required hardware and cabling to satisfy
your new console type. You can also use Appendix D. System Locations for Cards and
Cables on page 321 for help in identifying where the cards or cables will be placed.
3. Continue with Tagging a pre-Power5 processor-based logical partition for console directly
below.
Tagging a pre-Power5 processor-based logical partition for

console
On the pre-Power5 processor-based primary partition, do these steps using the physical control
panel:
1. If the primary partition is already powered on, continue with step 3.
If the primary partition is powered off, do the following steps:
The control panel should be lit and display 01 B N V=F.
If 01 B N V=F is not displayed, you might need to change the mode. To use the control
panel to change the mode, perform the following steps:
Note: If you have to install Licensed Internal Code (LIC) substitute D for B and M for N
a. Select function 02 by pressing the Increment () or Decrement () button on
the control panel.
Tip: The Increment () or Decrement () buttons change the field values, and
the Enter button advances you from field to field.
b. Press Enter to start function 02. The current IPL type is displayed with a pointer.
The current logical key mode and IPL speed are also displayed.
c. Using the Increment (), Decrement (), and Enter buttons, scroll through the
IPL types, logical key modes, and IPL speeds until 02 B N V is displayed.
d. Press Enter to exit function 02.
e. Using the Increment (), or Decrement () button, select function 01, and then
press Enter.
105
Note: Expect a delay between the time when power is applied to the system and when an
initial program load (IPL) can be performed. When power is initially applied to the
system, the service processor performs a self-check and the control panel remains blank
for up to 2 minutes. Wait until the C1xxxxxx progress codes are completed and 01 is
displayed on the control panel before you perform an IPL or change any control panel
functions.
2. Press the white Power On button. There is a short delay before the system powers on,
approximately 5 to 20 minutes.
If the control panel displays A9002000, the console might not be connected yet.
4. Select Work with System Partitions.
5. Select Work with partition configuration.
6. Choose Select Console Resource on the logical partition.
7. Press F9 to Change capability filter.
8. Select Any Console.
9. To select the IOP that will support your intended console place a 1 in front of the IOP to
select it as the console IOP.
Note: There may be cases in which an attempt to change a tag will require removing
resources and adding them back in before the system will allow the tag changes.
10. If you selected a resource to be used with twinaxial console you can use an optional alternate
console (twinaxial console only).
Note: The selection of an alternate console only pertains when twinaxial workstations
are to be the alternate console and the console type is also twinaxial console. The
alternate console must be under a different IOP than the IOP tagged for use by the
primary twinaxial console. Operations Console cannot be used as an alternate console.
Do not tag the same IOP for the console and the alternate console.
If you selected a resource to be used with Operations Console, you must also tag the same
IOP used for the console as the IOP for Electronic Customer Support (ECS).
To verify the console IOP for ECS, perform the following steps:
a. Press F12 until you arrive at the Work with partition configuration window.
b. Enter a 9 in front of the partition to be tagged for ECS.
c. Look at the symbols on the same line as the tagged console IOP (the Console tag is
the < symbol) for the ECS symbol, which is the + (the plus sign).
If the + symbol is shown, the IOP is correctly tagged for ECS. Go to step 9.
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.
11. Press F3 to exit to the DST main menu or SST main menu.
12. Continue with Select your console - Pre-Power5 processor-based, on page 107.
106
Changing hardware on a pre-Power5 processor-based

primary partition or standalone system with the power off
1. Referencing Appendix A. Shutting down systems or logical partitions on page 271, as
needed, power off the system.
2. Referencing Chapter 1: Reference, on page 19 and Chapter 2: Considerations for planning
on page 59, as needed; add, remove, or replace any required hardware and cabling to
satisfy your new console type. You can also use Appendix D. System Locations for
Cards and Cables on page 321 for help in identifying where the cards or cables will be
placed.
3. Continue with Select your console - Pre-Power5 processor-based, below.
Select your console - Pre-Power5 processor-based

Do one of the following:
If you will be using Operations Console as your console, go to Chapter 6: Setting up

Operations Console on page 125.
If you will be using twinaxial console as your console, go to Chapter 7: Twinaxial

107
Filler page
108
Chapter 5: Changing consoles - Powerprocessor-based

If you will be changing consoles, it is suggested that you have a current backup of your system
or logical partition (including operating systems, licensed programs, and data). For information
about backing up your system or logical partition, see Backing up and recovering data.
Referencing Chapter 1: Reference, on page 19 and Chapter 2: Considerations for planning on
page 59, as needed; verify any required hardware and cabling to satisfy your new console type.
You can also use Appendix D. System Locations for Cards and Cables on page 321 for help in
identifying where the cards or cables will be placed.
The server value QAUTOCFG must be set to ON. Use one of the following to verify or set this
system value on the server:
Use the WRKSYSVAL QAUTOCFG command.
During a manual IPL, in the IPL Options window, for Set major system options, select Y.
Then for Enable automatic configuration, select Y.
You must unlock the SST option before you can use it. For additional information on SST, see
If your plan to change the console involves using another workstation to complete some
configurations then be sure to unlock the SST option before starting the change instructions.
Verify proper environment for changing consoles

Answer the questions to determine if you have the right environment to perform a change of
your console:
1. Is the system powered on?
No. Go to Choosing the procedure to change a console - Power-processor-based directly
below.
2. Do you have access to DST or SST?
Yes. go to Choosing the procedure to change a console - Power-processor-based directly
below.
109
3. Has the system or partition posted a system reference code (SRC) with the attention light?
4. Refer to Troubleshooting system reference code (SRC) data on page 288. Is the SRC one of
the listed SRCs?
Yes. Go to Troubleshooting system reference code (SRC) data on page 288 and attempt
recovery.
If the information presented does not help correct your problem you need to call your
service provider.
If the information fixes your problem go to Choosing the procedure to change a console Power-processor-based directly below.
5. Refer to one of the following links to attempt a recovery of the console or workstation or call
your service provider.
Pre-Power5 processor-based
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/rzahb/rzahbrtrbshoo1.htm
http://publib.boulder.ibm.com/infocenter/systems/topic/iphau/kickoff.htm
http://publib.boulder.ibm.com/infocenter/systems/topic/iphdx/p6_troubleshootingsystem.htm
If the information fixes your problem go to Choosing the procedure to change a console Power-processor-based directly below.
110
Choosing the procedure to change a console - Powerprocessor-based

Answer questions to help you choose the correct procedure to follow for changing the current
console, interface, or terminal.
1. Are you currently using a Local console on a network (LAN) as your console or you use the
service tools server for connecting iNavigator?
2. Do you plan to continue using this resource as a backup console or to facilitate a
connection to the service tools server for iNavigator?
No. Perform the following task to deallocate the resource:
devices.
b. Press F6 to clear the old values, and then F7 to store the new values.
c. Press F3 or F12 to exit.
d. Continue with question 3.
3. Is the server managed by a Hardware Management Console (HMC), at this time?
Note: If your current console is the Thin Console, select No.
Yes. Continue to question 4.
No. Continue with Changing the console without an HMC on page 112.
4. Are you adding an HMC to the system, at this time?
Yes. Continue with one of the following:
If you will be using a HMC with version 6 code, go to Installing the HMC and
create your partition.
http://publib.boulder.ibm.com/infocenter/systems/topic/iphai/installhmc.htm
Return to Choosing the procedure to change a console - Power-processor-based
question 1, above, when the HMC is installed.
If you will be using a HMC with version 7 code, go to Installation and
Configuration Guide for the Hardware Management Console and create your
partition.
http://publib.boulder.ibm.com/infocenter/systems/topic/iphdx/abstract_install_co
nfig_hmc_guide.htm
Return to Choosing the procedure to change a console - Power-processor-based
question 1 when the HMC is installed.
No. Continue with Changing the console with an HMC on page 116.
111
Changing the console without an HMC

To change a console when no HMC is present, select one of the following tasks:
Changing the console without an HMC and hardware changes are needed on
page 113.
OR
Changing the console without an HMC and when the correct

hardware is installed
Before you perform this procedure, ensure that the target console resource has been installed.
To change the console, complete the following steps:
1. Change the console type.
devices.
If you are using SST, select Work with service tools user IDs and devices
b. Select Select console. The value of the current console is displayed. A value of 0
means that the console value is not set. The console value must be one of the
following values:
Console
Console
value
1
Twinaxial console
2
3
4
HMC or Thin Console
The HMC and Thin Console cannot be connected to
the server at the same time.
If you are unable to select a new console value, see IBM i5/OS problem analysis to
begin troubleshooting the problem.
http://publib.boulder.ibm.com/infocenter/systems/topic/ipha5/os400_problem_an
alysis.htm
2. Continue with Select your console - Power-processor-based on page 124.
112
Changing the console without an HMC and when hardware

changes are needed
Important: If you do not have another device other than the console to work in SST you will
have to make your changes with power off.
Select the procedure that best fits your situation:
Changing the console hardware with the power on - No HMC directly
below
Changing the console hardware with the power off - No HMC on page 115
Changing the console hardware with the power on - No HMC

This procedure requires that you have another workstation available that can use SST.
When changing consoles, you might have to either replace the current adapter or make another
hardware change to support a different console. This change might not require you to perform an
IPL if you follow the procedures to install, remove, or replace a PCI adapter (concurrent
maintenance) with the system power on. For more information regarding Power6 processorbased systems, see PCI adapters.
http://publib.boulder.ibm.com/infocenter/systems/topic/iphdx/abstract_pci_adapters_guide.htm
For Power5 processor-based PCI adapters, see Removing and replacing parts:
http://publib.boulder.ibm.com/infocenter/systems/topic/iphau/removereplace.htm
or
PCI adapters.
http://publib.boulder.ibm.com/infocenter/systems/topic/iphak/iphakprintthis.htm
To change your console, complete the following steps:
1. Using another workstation, vary off or deactivate the resource associated with the current
console.
If the current console is Operations Console, disconnect the connection:
a. Select the configuration name. This is the name that Operations Console uses to
refer to a specific server.
b. From the Connections menu, click Disconnect. The connection status displays
Disconnecting.
c. Wait for the status to display Disconnected.
d. Access service tools using DST or SST.
If you are using DST, select Work with DST environment.
e. Select Start a service tool.
f. Select Display/Alter/Dump.
g. Select Display/Alter storage.
113
h.
i.
j.
k.
Select Licensed Internal Code (LIC) data.

Select Advanced analysis. (Page down to display this option.)
Page down until you find the OPSCONSOLE option.
Type a 1 next to the option and press Enter. The Specify Advanced Analysis Options
window is displayed and the command displays as OPSCONSOLE.
l. Enter one of the following options:
If you are using a local console directly attached, enter DEACTDIRECT
If you are using a local console on a network (LAN), enter DEACTLAN
m. Press Enter. You should get a confirmation window.
n. Press F3 until you back to the DST or SST main menu.
If the current console is the twinaxial console, use the Vary Configuration
(VRYCFG) command to vary off all devices and the controller. You can power off
the device.
Important: This procedure must be performed using a PC or terminal not associated
with the current console. If the adapter is active at the time you attempt to exchange
it, the procedure to physically exchange the adapter will fail and you might have to
power off the partition to make the changes for the console.
If the current console is a Thin Console, you can power off and disconnect the
device.
2. After you verify that the adapter is not active, use a combination of powering off a slot,
replacing or moving adapters, and powering on the slot again as necessary, using
concurrent maintenance, until you have the correct location for the hardware of the new
console.
3. Change the console type.
a. Use one of the following options:
b. Select Select console. The value of the current console is present in the input field. A
value of 0 means that the console value is not set. The console value must be one of
the following values:
Console
Console
value
1
Twinaxial console
2
3
4
HMC or Thin Console
The HMC and Thin Console cannot be connected to
the server at the same time.
114
If you are unable to select a new console value, see IBM i5/OS problem analysis to
begin troubleshooting the problem.
http://publib.boulder.ibm.com/infocenter/systems/topic/ipha5/os400_problem_analys
is.htm
Changing the console hardware with the power off - No HMC

This procedure requires that you to have another workstation available that can use SST.
1. Using the current console or another workstation, power off the system. See Appendix A.
Shutting down systems or logical partitions on page 271.
2. Depending on the current console, do one of the following tasks:
Disconnecting.
If the current console is a twinaxial console or Thin Console, you can power off the
device now.
3. If you will not be using the current console as a backup remove any hardware or cables
associated with the previous console, and add or move any hardware or cables needed for
the new console.
4. Select the option that best fits your situation. More than one option might apply.
If the new console is not Operations Console, power on the console device and start a
connection at this time.
If you currently have a configured connection for Operations Console that you will
not be using as a backup console, delete the configured connection:
a. Select the configuration name.
b. Click Delete on the Connection menu.
c. Click Yes to confirm the deletion.
115
Changing the console with an HMC

1. Are you removing the HMC from the system?
Note: If you are changing from using the HMC 5250 console to another console type,
answer No.
Yes. Important: Removing the HMC from a currently managed system will require
the system to be reset.
To reset the system follow the steps using one of the links below:
Using a version 6 HMC
http://publib.boulder.ibm.com/infocenter/systems/topic/iphbl/iphblresetserver.ht
m
Using a version 7 HMC
http://publib.boulder.ibm.com/infocenter/systems/topic/iphat/iphblresetserverp6.htm
Return to Choosing the procedure to change a console - Power-processor-based when

the HMC has been removed.
2. Will you power off the logical partition or the managed system to make the hardware
changes?
Note: If either of the following statements are true, select Yes.
You already have the correct hardware installed in the system and need to change
only the console or Operations Console tag. You also plan to activate the logical
partition at a later time.
You are changing to or from a twinaxial console. This type of console change
requires an initial program load (IPL) to use a different console.
Yes. Complete Changing the console using the partition profile with an activation on
page 117.
No. Complete Completing a console change with the logical partition and managed
system powered on (HMC) on page 119.
116
Changing the console using the partition profile with an

activation
This procedure requires you to power off your system or partition..
1. Using the current console or another workstation, shut down the logical partition or
managed system. For instructions, see Appendix A. Shutting down systems or logical
partitions on page 271.
2. Depending on the current console, do one of the following:
Disconnecting.
If the current console is a twinaxial console or Thin Console, you can power off the
device now.
3. If you will not be using the current console as a backup remove any hardware or cables
associated with the previous console, and add or move any hardware or cables needed for
the new console.
4. To change the console tag using an HMC, do one of the following based on the HMC
type:
HMC using version 6 code
a. Using the HMC, verify the console device setting for the partition profile.
i. In the navigation area, open Server and Partition.
ii. Select Server Management.
iii. In the contents area, open the server on which the partition profile is located.
iv. Open Partitions.
v. Open the logical partition for the partition profile
vi. Right-click the partition profile and select Properties.
vii. Click Tagged I/O, verify the Console resource to be used.
If the resource is other than what you will be using, do the following steps to
A. Clear the current console setting, and click Select or click the check
box for Use HMC console. If you selected to use the HMC as your
console, go to step j.
B. Expand the list in the I/O devices in the profile area so that the console
device that you want to use is displayed.
C. Select the console device that you want to use, and then click Select.
117
Note: If you selected an asynchronous communications adapter for

Operations Console (Direct), you must also select the same asynchronous
communications adapter in the Operations Console field.
viii. Click OK, and then click OK again.
b. Continue with step 5.
Using HMC using version 7 code

a. Using the HMC, verify the console device setting for the partition profile.
i. In the Navigation area, expand Systems Management.
ii. Expand Servers.
iii. Select the managed system.
iv. In the Contents area, select the partition you will be defining.
v. From the Tasks area, expand Configuration.
vi. Click Manage Profiles. This should open the Manage Profiles window.
vii. Select the profile you will be working with.
viii. Click Actions, and select Edit.
ixi. Click Tagged I/O
x. Verify the correct console resource shows.
If the resource you would like to use for the console isn't selected, do one the
following:
If you will be using the HMC then click the check box for Use HMC
console, then go to step k.
If you won't be using the HMC then uncheck Use HMC console if it's
checked, then follow these steps:
A. Click Select.
B. If you will be using an adapter card be sure I/O device shows in the
upper left corner of the window. Then, select you resource from
the list. Go to step k.
If you will be using a logical port, such as provided by the IVE
(HEA), then select Logical Port in the upper left corner. Select the
logical port you want to use, then, click OK.
xi. Click OK.
xii. Click Close.
5. Select the option that best fits your situation. More than one option might apply.
If the new console is not Operations Console, power on the console device and start a
connection at this time. Continue with Select your console - Power-processor-based
on page 124.
If you currently have a configured connection for Operations Console that you will
not be using as a backup console, delete the configured connection:
b. Click Delete on the Connection menu.
118
c. Click Yes to confirm the deletion.

d. Continue with Select your console - Power-processor-based on page 124.
Completing a console change with the logical partition and

managed system powered on (HMC)
After making all of the necessary hardware changes, complete the console change with the
logical partition and managed system powered on. You will be required to start an HMC
command line session in this procedure. This procedure does not require an IPL.
Before you begin, it is recommended that you have a current backup of the system or logical
partition (including operating systems, licensed programs, and data). For information about
backing up the system or logical partition, see Backing up and recovering data.
Do one of the following to start an HMC command line:
If you want to access the HMC command line using a local terminal connection, start an
xterm shell on the HMC. To do this, open a terminal by right-clicking the background
and selecting Terminals > rshterm.
If you want to access the HMC command line using a remote terminal connection such
as PuTTy, first set up secure script execution between SSH clients and the HMC. For
instructions, see Setting up secure script execution between SSH clients and HMC.
http://publib.boulder.ibm.com/infocenter/systems/topic/iphai/settingupsecurescriptexecut
ionsbetweensshclientsandthehmc.htm
You must then start your remote terminal by specifying the name of the HMC that is
managing the partition you will be working with.
The following procedure contains examples within the steps to help you complete a console
change. In these examples, the system named sysname with partition identification number 1 is
changing from the HMC to Operations Console (LAN) using an embedded Ethernet port. These
variables are placeholders for your actual system name and partition ID number. In the following
instructions, replace sysname with your system name and replace 1 with your partition
identification number.
To make a console change without powering off the partition, complete the following steps:
1. List the current I/O configuration for the logical partition and locate the device that you
want to make the system console device.
If you already know which resource is being used for the console, continue with step 1.b.
119
Otherwise, complete step 1.a to list the currently tagged resource for the console.
a. Type the following command on the HMC command line:
lshwres -m sysname -r io --rsubtype taggedio --filter
lpar_ids=1 -F console_slot
This command returns none, hmc, or an eight-character hexadecimal string
representing the dynamic reconfiguration connector (DRC) index of the current
console adapter.
If you currently use Operations Console (Direct) as the console or backup console, or
previously specified an asynchronous communications adapter for remote service,
you can use the following command to display the current configured resource
associated with the Operations Console tag:
lshwres -m sysname -r io --rsubtype taggedio --filter
lpar_ids=1 -F op_console_slot
b.
Do one of the following to select the resource to be used for the console:
If you have a Power5 processor-based system, or you plan to use a resource other
than an IVE port do this:
To list the I/O owned by the logical partition, type the following command on the
HMC command line:
lshwres -m sysname -r io --rsubtype slot --filter
lpar_ids=1-F drc_index,drc_name,description
The system returns data in the following format:
21030001,U1234.001.123456A-P1-T6,PCI 10/100/1000Mbps
Ethernet UTP 2-port
21010003,U1234.001.123456A-P1-T12,PCI RAID
Controller ...
21010004,U1234.001.123456A-P1-C2,PCI 10/100/1000Mbps
Ethernet UTP 2-port
21010005,U1234.001.123456A-P1-C3,PCI 2-Line WAN
w/Modem
The location of the resource DRC 21030001 is listed as P1-T6 and not P1-Cn
(where n is a slot number). The Tn designation represents embedded resources.
If you designate an actual adapter, the location is a value similar to P1-C2. This
enables you to get the DRC index of the input/output adapter (IOA), which
becomes the new console device.
120
If you have a Power6 processor-based system and intend to use the Integrated
Virtual Ethernet (IVE) you need to list the logical ports owned by the logical
partition.
To list the logical ports owned by the logical partition, type the following
command on the HMC command line:
lshwres -m sysname -r hea --rsubtype logical --level
port --filter lpar_ids=1 -F drc_index,drc_name
The system returns data in the following format:
23e01000,Port 17
23e01100,Port 18
23e00000,Port 1
23e00100,Port 2
c. Identify the DRC index of the console IOA that you want. In the previous output
example, the first entry is an Ethernet IOA with a DRC index of 21030001. The
Ethernet port for this device is labeled T6 in unit 1234.001.123456A.
2. Change the Console tag of the partition to the device that you want to become the next
console device.
a. Complete one of the following tasks to change the console type:
Change your console to the HMC
To set the new Console tag to the HMC 5250 console, type the following
command:
chhwres -m sysname -r io --rsubtype taggedio --id 1 -o
s -a console_slot=hmc
Change your console to Operations console(LAN)

To set the new Console tag to an IOA with a DRC index of 21030001 (the DRC
index can be found in step 1), type the following command:
s -a console_slot=21030001
121
Change your console to Operations console(Direct)

To set the new Console tag to an IOA with a DRC index of 21010005 (the DRC
index can be found in step 1), type the following commands:
s -a console_slot=21010005
s -a op_console_slot=21010005
b. To verify your changes, repeat step 1. (You must also update your partition profile
settings later in step 5.)
Notes:
To clear the Console tag, type the following command:

chhwres -m sysname -r io --rsubtype taggedio --id 1
-o s -a console_slot=none
To clear the Operations Console tag, type the following command:

chhwres -m sysname -r io --rsubtype taggedio --id 1
-o s -a op_console_slot=none
If entering none in the previous commands results in an error message, try

entering eight zeros (00000000) instead.
3. Start a search for the console device by doing the following sequence of console service
functions against the partition: 65, 21, and 21. This sequence of three console service
functions within 45 seconds (60 seconds in V6R1 and later) for each function initiates a
new search for the console device. For more information, see use the console service
functions (65+21) on page 232.
a. To perform function 65 (remote DST off), type the following command:
chsysstate -m sysname -r lpar --id 1 -o remotedstoff
b. To perform function 21 (force DST), type the following command:
chsysstate -m sysname -r lpar --id 1 -o dston
c. Perform step 3.b again.
4. Try to connect with the newly selected console device and monitor the partition's system
reference codes (SRCs). It can take up to three minutes for the console adapter change to
be completed.
122
Note: To monitor the SRCs for the logical partition, type the following command to list
the last 10 SRCs:
lsrefcode -m sysname -r lpar -n 10 --filter "lpar_ids=1"
SRCs are listed in order from newest to oldest. To list a different number, replace 10 in
the command with the number of SRCs that you want returned. For more information
about SRC data, see Troubleshooting system reference code data.
http://publib.boulder.ibm.com/infocenter/systems/topic/ipha8/rzajr/rzajrtroublesrc.htm
5. If the previous steps were successful, the current console type for the logical partition no
longer matches the console type in the partition profiles.
If you want the new console type to be preserved across partition activations, go to the
partition profiles and change the Console tag to match the selection in the chhwres
command in step 2.
Use one of the following procedures depending on which version of HMC you use:
For HMC V6, use these instructions:
c. In the contents area, open the server on which the partition profile is located.
d. Open Partitions.
e. Open the logical partition for the partition profile.
f. Right-click the partition profile and select Properties.
g. Click Tagged I/O.
h. If the resource is other than what you will be using, do the following steps to
i. Clear the current console setting, and click Select or click the check box for
Use HMC console.
If you selected to use the HMC as your console, go to step i.

ii. Expand the list in the I/O devices in the profile area so that the console
device that you want to use is displayed.
iii. Select the console device that you want to use, and then click Select.
Note: If you selected an asynchronous communications adapter for Operations
Console (Direct), you must also select the same asynchronous communications
adapter in the Operations Console field.
i. Click OK, and then click OK again.
j. Continue with step 6.
123
For HMC V7, use these instructions:

a. In the navigation area, expand Systems Management.
b. Expand Servers
c. Select the managed system from the list.
d. In the Contents area, select the partition you want to work with.
e. In the Tasks area, expand Configuration.
f. Click Manage Profiles to open it.
g. A list of partition profiles will be presented. Select the partition profile you
will be working with.
h. Click the Actions drop-down menu and select Edit.
i. Click Tagged I/O.
j. Clear the current console setting.
k. Do one of the following to select your new console:
Click the check box for Use HMC console.
If you selected to use the HMC as your console, go to step l.
If you will be selecting a logical device, do the following:
i. In the upper-left corner of the window, select Logical Port.
ii. Select the logical port, then click OK.
iii. Continue with step l.
Expand the list in the I/O devices in the profile area so that the console
device that you want to use is displayed. Select the console device that
you want to use, and then click Select. Continue with step l.
Note: If you selected an asynchronous communications adapter for
Operations Console (Direct), you must also select the same asynchronous
communications adapter in the Operations Console field.
l.
Click OK, then, click Close.
Select your console - Power-processor-based
If you will be using Operations Console as your console, go to Chapter 6: Setting up

Operations Console on page 125.
If you will be using twinaxial console as your console, go to Chapter 7: Twinaxial
If you will be using the Thin Console as your console, go to Chapter 8: Thin console on
page 201.
If you will be using the HMC as your console, go to Chapter 9: HMC 5250 console on
page 207.
124
Chapter 6: Setting up Operations Console

Consider the following if you are installing a new system or changing consoles:
The server value QAUTOCFG must be set to ON. Use one of the following to verify or set
this system value on the server:
During a manual IPL, in the IPL Options window, for Set major system options, select
Y. Then for Enable automatic configuration, select Y.
If you are changing the console and did not power down you may have to complete one of the
following tasks to have the new console type recognized:
Perform an initial program load (IPL) of the system. See below for assistance.
OR
Use the OPSCONSOLE RESTART macro. For more information about the macro, see
use the OPSCONSOLE macro on page 215.
Attention: Changing to or from a twinaxial console requires you to perform an IPL on the
system.
The references to release is specific to the client PC and not the operating system unless
otherwise stated. For V6R1 with the simplified client functions it is assumed that the system is
also using V6R1 of the operating system to take advantage of this new function. However, it
does not mean the system has to be at that level of code. The V6R1 client code will work with
any supported level of Licensed Internal Code, but the detection function and automatic sensing
will not work. The V6R1 client will automatically manage the access password regardless of the
system's code level.
Determining where to start installing Operations

Console
Answer the questions to determine where to start these instructions:
1. Do you have to add or remove any cables for your old or new console?
Yes. Go to Cabling the Operations Console to your server on page 126.
2. Is your system already powered on and IPLed?
Yes. Go to Verify or Install Client Access on page 129.
No. Go to Prepare your connection on page 127.
125
Cabling the Operations Console to your server

Before you cable your server with Operations Console, determine the type of connection you
will be making. You can attach directly to the server using the Operations Console cable or
connect on a network (LAN) using an Ethernet cable
Before making changes to the system, be sure to read the information in the Danger Notice.
Important: It is assumed the server is powered down. Do not power on the server until you
are instructed to do so.
The following steps assume you have already set up the PCs that are connecting to the system.
You can also use these steps if you are removing one or more cables from your PC, server, or
both.
If you are installing a local console directly attached you need to install the Operations Console
cable if you want to use the console function. Cabling information is available with instructions
and graphics to install your cables for most server models in the Information Center specific to
your model. See Appendix D. System Locations for Cards & Cables on page 321 for graphics of
most supported systems.
Connect any required cables to support the console.
To connect the Operations Console cable (directly attached):
1. Shut down and unplug the PC that will serve as the system console.
2. Locate the Operations Console cable (97H7557 or 39J5835), and connect the
Operations Console cable to the corresponding connector on the adapter to be used.
Note: If you are using the 2742 or 2745 adapter, the Operations Console cable must
be attached to the lower (or left-most) connector. See the graphics, page 321, for
assistance in determining the location of the Operations Console supporting adapter.
3. Install the cable.
4. Connect the other end of the Operations Console cable to the first or only serial port
on the PC.
To connect the Ethernet cable on a network (LAN):
1. Shut down and unplug the PC that will serve as the system console.
2. Connect the network cable from the PC to your local network.
3. Connect another network cable from the same local network to the adapter to be used
for the console.
If you would like to use a private network, only a few devices or just the console and
system, see Appendix F. Private Network Setup on page 347.
126
Notes:
The 2849 adapter requires an input/output processor (IOP).
If your system is a Power6 processor-based model the adapter is required to be
located in an expansion unit.
Note: To use an adapter in an expansion unit you may be required to use an
HMC to tag the resource.
If you are using an external 5706/5707 or 5767/5768 adapter, you must connect the
network cable to port 1 (top or right-most connector).
You also need to disable support for the embedded Ethernet port.
If you are using the IVE (HEA), you must connect the network cable to port 1 (top or
right-most connector).
Support for the embedded port is enabled by default.
After your cabling has been completed, continue with Prepare your connection below.
Prepare your connection

To power on the system, if needed, use one of the following methods:
1. On a pre-Power5 processor-based primary partition, standalone system, or a Powerprocessor-based system without an HMC, do these steps:
Using the physical control panel

a. Plug in your system or uninterruptible power supply and attached expansion
units.
b. Open the control panel door on the front of the system. The control panel should
be lit and display 01 B N V=F. The system is not yet powered on.
If 01 B N V=F is not displayed, you might need to change the mode. To use the
control panel to change the mode, perform the following steps:
Note: If you have to install Licensed Internal Code (LIC) substitute D for B and
M for N
i. Select function 02 by pressing the Increment () or Decrement () button on
the control panel.
Tip: The Increment () and Decrement () buttons change the field values,
and the Enter button advances you from field to field.
ii. Press Enter to start function 02. The current IPL type is displayed with a
pointer. The current logical key mode and IPL speed are also displayed.
127
iii. Using the Increment (), Decrement (), and Enter buttons, scroll through
the IPL types, logical key modes, and IPL speeds until 02 B N V is displayed.
iv. Press Enter to exit function 02.
v. Using the Increment () or Decrement () button, select function 01, and
then press Enter.
Note: Expect a delay between the time when power is applied to the system and
when an initial program load (IPL) can be performed. When power is initially
applied to the system, the service processor performs a self-check and the control
panel remains blank for up to 2 minutes. Wait until the C1xxxxxx progress codes
are completed and 01 is displayed on the control panel before you perform an IPL
or change any control panel functions.
c. Press the white Power On button. There is a short delay before the system powers
on, approximately 5 to 20 minutes.
d. Continue with step 3.
Use the primary partition on a pre-Power5 processor-based system to power on a

logical partition
b. Select Work with System Partitions.
c. Select Work with partition status.
d. Place a 1 on the line for the partition you will be powering on, then press Enter.
e. Answer any prompts presented.
f. Continue with step 3.
2. Using an HMC, complete the following task using one of the following methods to
activate a system profile:
Using version 6 or earlier of the HMC, follow these steps:
c. In the contents area, open the server on which the system profile is located.
d. Open System Profiles.
e. Right-click the system profile and select Activate.
f. Click Continue.
g. Continue with step 3.
128
Using version 7 or later of the HMC, follow these steps:

Do the following:
a. In the Navigation pane, expand Systems Management > Servers, and click on the
target server.
b. In the Work area, select the box in the Select column next to the target
partition.
c. Click the Tasks button, select Operations then Activate.
If you experience problems, refer to Appendix B. Troubleshooting on page 281.

3. Continue with Verify or Install Client Access below.
Note: An SRC A9002000 may be displayed during the IPL.
Verify or Install Client Access

Attention: Plug in and turn on your console at this time if you have not already done so.
During the installation of Client Access, you are going to install a 5250 emulator, unless you
already have PC5250 or IBM Personal Communications V5.9 (V5.7 CSD 1 minimum), and
Operations Console support. For updated PC requirements, see the Client Access Web site.
To check whether you have Client Access already installed, complete the following steps:
1. Click Start and select Settings.
2. Click Control Panel.
3. Double-click Add/Remove Programs.
If you are using Microsoft Windows Vista, double-click Programs and Features.
4. Locate IBM Client Access.
5. To close Add/Remove Programs, click Cancel.
6. Close the control panel.
7. If you have Client Access already installed go to Applying Client Access service packs
on page 130.
If you do not have Client Access installed, use the media Client Access install code is located on
to install it:
1. Insert the Client Access media in the optical drive.
2. Select the Client Access option to start the installation.
3. Wait until the IBM Client Access window is displayed.
4. Click Next and follow the prompts. For further installation assistance with Client Access,
see the Client Access Web site.
129
5. If you are installing Client Access for the first time, you must verify that you have at least
a minimum configuration for running Operations Console.
If you are only adding the Operations Console component, add only the components
necessary to meet this minimum configuration.
6. To ensure the minimum configuration, select Custom or Full installation and select at least
the following components:
Note: The Operations Console component is not available using the Typical or PC5250
User options.
Required Programs
5250 Display and Printer Emulator (if
IBM Personal Communications V5.9 (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 indicates that one is required.
Important:
If your Operations Console configuration is going to support only the remote control
panel, you do not need to install an emulator.
Operations Console
Click Next and follow the prompts. You will be asked to restart your PC at this time.
Before applying the latest service pack, you must restart the system.
8. Apply the latest service pack for Client Access using the instructions below.
Applying Client Access service packs

It is recommended that you use the latest service pack for Client Access.
Service packs are available for your PC at the following Web sites:
1. The Client Access Service Packs page:
2. http://www.ibm.com/eserver/iseries/access/casp.htm
3. The IBM FTP site:
4. ftp://ftp.software.ibm.com
5. Navigate down to the directory path:
as400/products/clientaccess/win32/v6r1m0/servicepack.
130
To set up a client PC using V5R3 or V5R4 go to V5R3 or V5R4 - Completing your

configuration setup tasks on page 138.
V6R1 - Completing your configuration setup tasks

You can configure your Operations Console to be a local console directly attached or a local console
on a network (LAN).
To complete the setup tasks specifically for your configuration, choose one of the following
options:
Option A. Local console on a network (LAN) below.

Option B. Local console directly attached on page 135
Option A. Local console on a network (LAN)

If you are setting up a new system using Operations Console (LAN), the LAN adapter is installed
and the correct console type is specified during the manufacturing process. When working
through the Operations Console configuration wizard, you must supply the connection name, as
well as the network parameters. During the initial connection, this data finishes the server
configuration for the network. This method uses BOOTP to configure the server. For more
information about BOOTP, see Bootstrap Protocol on page 318.
To continue to setup for a new system continue with Configuring a local console on a network
(LAN) directly below.
Configuring a local console on a network (LAN) - V6R1

Complete the configuration of your Operations Console (LAN) on the PC by using the Operations
Console configuration wizard.
The system is expected to have been powered on and is IPLing or already IPLed.
Important: You must be using a profile that has administrator rights to create or alter a
configuration.
131
To configure a new local console on a network (LAN), follow these steps:

1. Click Start Programs Client Access Operations Console.
If Operations Console is not displayed, complete a Client Access selective setup.
Click Start Programs IBM Client Access Selective Setup.
Notes:
When Operations Console starts it will check your network for any systems not
already configured and display them.
If you had one or more previously configured connections they will also appear.
2. Select from the following options:
If the system you want to connect to is in the list of configured connections, go to
Start your connection - V6R1 LAN on page 134.
If the system you want to connect to is not in the list of configured connections,
manually create one starting with step 3.
If there were no configured connections prior to starting and no systems were

detected, the configuration wizard automatically starts. Continue with step 4.
Select Connection New Connection.
Click Next on the Welcome window.
If the Configure Operations Console Connection window is displayed, click Next.
On the Select Configuration window, ensure Local console on a network (LAN) is selected and
click Next. Consider how the service host name is being created. During the next step,
you need to know if you already created a service host name (service interface), or if you
will be creating one during the step. For more information about the service host name
(interface name), see create or verify a service host name (interface name) on page 139.
In the Specify Service Host Name window, specify the service host name and click Next to
allow Operations Console to search for the system on the network. Operations Console
attempts to contact the system using the service host name you just entered.
One of the following will occur:
If an address is returned, Operations Console will display the network address of
the system and the IP address is disabled. Click Next.
3.
4.
5.
6.
7.
If an address is returned and the PC previously resolved the name and address,
Operations Console will display the network address of the system and
automatically goes to the next window.
If an address was not returned, enter the IP address that you want to assign to the
service host name you entered. Click Next.
The data shown in the Specify Interface Information window depends on several factors as
explained above.
132
8. Ensure that you verify all returned data before proceeding.

Consider the following:
All fields might not appear at this time and some fields might be disabled. This is
the result of the previous step in which you attempted to contact the system.
If the PC does not receive information from the network, you must enter any
required data manually. This might happen if the system has never been
configured or if the system is not connected to the network yet.
Power-processor-based models start counting logical partitions with number 1

(even if it is the only partition) instead of a 0. For the console to connect
correctly, your logical partitions must also begin numbering at 1 instead of 0.
This is especially true if you rely on the BOOTP process to configure the server
with its network data.
9. If all the data is correct, click Next.
10. Select from the following options:
Note: The next window displayed depends on whether Operations Console was able to
connect to the system and what information was provided.
If the Specify Service Tools Device ID window is displayed, the target system was either
not able to be contacted, or the system is not running Version 6 Release 1. Perform
the following steps:
a. Enter a device ID. You can either use the default QCONSOLE service tools
device ID that is provided or enter a service tools device ID that you created
specifically for this configured connection.
b. Click Next.
c. Click Finish in the Complete window to save the configuration and to exit the
setup wizard.
If the Complete window is displayed, click Finish to save the configuration and to exit
the setup wizard. You are now ready to start your connection.
11. Continue with Start your connection.
133
Start your connection - V6R1 LAN

Complete the final step of setting up your Operations Console by starting your connection.
1. Highlight the connection name.
2. Start your connection by selecting one of the following tasks:
1. Right-click the connection name and select Connect.
2. Click the Connection icon in the toolbar.
3. Click the Connection menu and select Connect
Note: The server needs to be powered on for the console to connect.
View the online help associated with using Operations Console by selecting Help from the
Operations Console window Help menu.
134
Option B. Local console directly attached

Note: Windows Vista does not support a directly attached console.
Installing Operations Console Connection Modem

If you are configuring a local console that is directly attached, you must install the Operations
Console connection modem.
Note: The Operations Console connection modem is not a physical modem. It is a logical device
driver that is included with Operations Console and allows a local console to connect to the
server. When it is present, it displays as Operations Console Connection in the Remote Access
Setup window.
Answer the following questions to determine where to begin your setup:
1. Do you need to install the Operations Console Connection modem?
No. Go to Configuring a local console directly attached to the system - V6R1 on
page 137.
2. Are you using Windows 2000?
Yes. Go to Installing Operations Console Connection Modem for Windows 2000 V6R1 on page 136.
No. Continue with Installing Operations Console Connection Modem for Windows XP V6R1 directly below.
Installing Operations Console Connection Modem for Windows XP - V6R1

You must install the Operations Console connection modem that is supplied with Operations
Console for a local console to communicate with the server. Use these instructions only if you
are configuring a local console that is directly attached.
To install the connection modem, complete the following steps:
1.
2.
3.
4.
5.
Click Start Control Panel.

Double-click Phone and Modem Options.
Click the Modems tab.
Click Add to display the Install New Modem panel.
Select Dont detect my modem; I will select it from a list, and then click Next.
135
6. Click Have Disk.

If you know the full path to the Operations Console Connection driver (cwbopaoc.inf),
enter it here. Then, go to step 8. If you do not know the path, continue with step 7.
Note: The default installation path is:
C:\Program Files\Ibm\Client Access\Aoc\Inf\cwbopaoc.inf
7. Click Browse. Navigate to drive:\path\Client Access\Aoc\Inf\ cwbopaoc.inf
where drive: is the drive where Client Access is installed.
8. Click Open, and then click OK.
9. Click Next.
10. Select the communications port where the Operations Console cable is attached, and then
click Next.
11. If prompted, select Continue Anyway to continue the installation.
12. Click Finish, and then click OK.
Continue with Configuring a local console directly attached to the system - V6R1 on page 137.
Installing Operations Console Connection Modem for Windows 2000 - V6R1

Console for a local console to communicate with the server. Only use these instructions if you
1. Click Start Settings Control Panel.
2. Double-click Phone and Modem Options.
3. Click the Modems tab.
4. Click Add to display the Install New Modem panel.
5. Select Dont detect my modem; I will select it from a list, and then click Next.
6. Click Have Disk.
enter it here. Then, go to step 8. If you do not know the path, continue with step 7.
C:\Program Files\Ibm\Client Access\Aoc\Inf\cwbopaoc.inf.f)
where drive: is the drive where Client Access is installed. Click Open.
8. Click OK. Operations Console Connection should be listed.
9. Click Next.
136
10. Select the communications port where you are going to install the Operations Console
cable (for example, COM1).
11. Click Next.
12. If the Digital Signature Not Found window is displayed, click Yes.
13. Click Finish to return to the Modems tab of the Phone and Modem Options folder.
14. Click OK.
Continue with Configuring a local console directly attached to the system - V6R1 directly
below.
Configuring a local console directly attached to the system - V6R1

Complete the configuration of your Operations Console (Direct) on the PC by stepping through the
Operations Console configuration wizard.
configuration.
To configure a new local console that is directly attached to the system, follow these steps:
Notes:
The configuration wizard starts automatically.
If it does not start automatically, click Connection New Connection.
If Operations Console had a previous configuration, that configuration will open
now.
2. Click Next on the Welcome window.
3. If the Configure Operations Console Connection window is displayed, click Next.
4. On the Select Configuration window, select Local console directly attached to the system and
click Next.
5. On the Specify Connection Name window, enter a name that you want to use to refer to this
configured connection. Click Next.
6. On the Detect Console Port window, ensure the Detect console communication port option is
selected. Click Next.
7. If the Port Not Found window is displayed, the communications port could not be
determined and some possible reasons are listed in the window. Click Back to try again or
click Next to manually assign the port.
137
8. On the Select Console Port window, the next available communications port is displayed.
You can either use the port provided or select another port where you have the console
cable attached. Operations Console uses COM ports 1 thru 9.
9. Click Next after you select a port.
10. If you selected Local console directly attached to the system for your console type, click
Finish on the Complete window.
You are now ready to start your connection.
Right-click the connection name and select Connect.
Click the Connection icon in the toolbar.
Click the Connection menu and select Connect
V5R3/V5R4 - Completing your configuration setup tasks

To complete the setup tasks specifically for your configuration, choose one of the following
options:
Option A. Local console on a network (LAN) V5R3/V5R4 continue below.

Option B. Local console directly attached V5R3/V5R4 on page 144.
Option C Local console directly attached with remote support - V5R3 & V5R4 Only on
page 156.
Use this link if you are setting up a Remote console through dial-up support (V5R3 &
V5R4 only) on page 173.
138
Option A. Local console on a network (LAN) V5R3/V5R4

Answer the following questions to determine where to start setting up a local console on a network
(LAN).
1. Are you setting up a system for the first time or you don't have any other workstations
available?
No. Go to Create or verify a service host name (interface name) directly below.
2. Will you be using Windows NT (V5R3 only)?
Yes. Go to Confirm installation of TCP/IP on the PC for Windows NT (V5R3
only) on page 141.
No. Go to Configuring a local console on a network (LAN) - V5R3 & V5R4 on page
141.
Create or verify a service host name (interface name)

You should only be here if you changing a system's console to a local console on a network (LAN)
and you have a workstation capable of using SST. For more information regarding a service
host name (interface name) refer to create or verify a service host name (interface name) on page
250.
Note: You might have to temporarily change the console to complete this task. You can also use
any option pertaining to the service tools LAN adapter to verify the service host name or data.
To create or verify the service host name, complete the following steps:
If you are using DST, select Work with DST environment, and then System devices.
3. Select Operations console(LAN) and press Enter. This displays Verify Operations Console
Adapters.
4. Press F11 to configure.
5. The service host name (interface name) field contains the name.
If you are creating a new service tools connection, follow these steps:
a. Enter the network data in the appropriate fields.
b. Store your configuration by pressing F7.
c. Activate the LAN adapter by pressing F14.
d. Press F3 to exit.
e. If you changed the console to a local console on a network (LAN) in step 2, re-select
the original console.
6. Continue with Create service tools device IDs on the server directly below.
139
Create service tools device IDs on the server

You need to set up service tools device IDs on the server for a local console on a network
configuration:
2. Select Service tools device Ids.
3. 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.
4. Enter the service tools device ID password. Enter it again for verification. You may enter
a description.
Note: The service tools device ID password is case-sensitive.
Press Enter. You have finished creating a service tools device ID.
Note: The device ID and the service tools user ID must have the proper authorities
granted before the remote control panel and all it's functions are available for the
associated partition.
5. To create additional service tools device IDs, repeat the steps starting at step 4.
6. Press F3 when you finish creating your service tools device IDs.
7. Use one of the following to continue setting up the console.
If you are not using Windows NT go to Configuring a local console on a network
(LAN) - V5R3 & V5R4 on page 141.
If you will be using Windows NT go to Confirm installation of TCP/IP on the PC for
Windows NT (V5R3 only) directly below.
Notes:
1. If you have to reset a service tools device ID, the password becomes the name of your
service tools device ID in uppercase.
2. If you have more than one PC connected to your console, you should create several service
tools device IDs.
3. Sometimes the service tools device ID password has to be changed, such as when the
password has to be resynchronized between the PC and the server. 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. For more information, see resynchronize the PC and service tools device ID
password on page 242.
4. QCONSOLE should not be left in a reset state on the server.
140
Confirm installation of TCP/IP on the PC for Windows NT (V5R3

only)
Use this section to satisfy the network requirements for Windows NT. Be sure you fully install
and configure any network adapter cards (such as LAN or Ethernet adapters) before starting the
Operations Console installation.
Confirm the existence of TCP/IP as follows:
3. Double-click Network.
If you get a message indicating that Networking is not installed, click Yes to install it.
4. Click the Protocols tab.
If TCP/IP is not installed on your PC, access your Windows Help by clicking Start > Help for
instructions on installing TCP/IP.
Note: Windows 2000 Professional and Windows XP Professional automatically installs with
TCP/IP.
Configuring a local console on a network (LAN) - V5R3 & V5R4

Complete the configuration of your Operations Console (LAN) on the PC by using the Operations
Console configuration wizard.
configuration.
To configure a new local console on a network (LAN), follow these steps:
Note: If you had one or more previously configured connections they will also appear.
2. If there were no configured connections prior to starting the configuration wizard
automatically starts. Continue with step 4.
3. Select Connection New Connection.
141
6. On the Select Configuration window, ensure Local console on a network (LAN) is selected and
click Next.
7. On the Specify Service Host Name window, specify the partition number and enter the
service host name (service interface name) for that partition.
Use either of the following ways to create the service host name (service interface):
Manually assign it, along with the network configuration, using another workstation.
If you did this previously, you will enter that name here.
If the system is attached to a network with a DHCP server, the system might already
be configured and you will enter the name assigned by that server here. For more
information about the service host name (interface name), see create or verify a
service host name (interface name) on page 250.
Let the PC assign the name and IP information by using the BOOTP process. This
assumes that the target interface on the system has not been configured and this is the
first connection to that interface. In this case, you can use any name that has not
previously been used on the network or with this PC. For more information about the
BOOTP process, see Bootstrap Protocol on page 318.
For more information about the service host name (interface name), see create or verify a
Important: Power-processor-based models start counting logical partitions with the
number 1 (even if it is the only partition) instead of a 0. For the console to connect
correctly, your logical partitions must also begin numbering at 1 instead of 0. This is
especially true if you rely on the BOOTP process to configure the server with its network
data.
6. Click Next to allow the system to search for the system on the network.
7. If the PC receives information back from the network or the target service interface, the
Service TCP/IP Address field displays the returned IP address.
Note: If the PC does not receive information back from the network, you must enter the
network address manually. This might happen if the system has never been configured
before or the system might not be connected to the network yet. In this case, the Service
TCP/IP Address field becomes editable and you can enter the IP address you want to
assign to the service interface.
If the address is correct, click Next.
8. On the Specify Interface Information window, verify or enter data for all of the required
fields. Click Next.
Note: Operations Console provides as much information as it can based on the response
received in this step. Some of the data might be based on standard network
configurations, which might be incorrect for your network infrastructure.
142
9. On the Specify Service Tools Device ID window, you can either use the default
QCONSOLE service tools device ID that is provided or enter a service tools device ID
that you created specifically for this configured connection.
Click Next.
10. On the Specify Access Password window, create and enter a password to start Operations
Console. This password is required each time you access Operations Console.
11. Click Finish on the Complete window to save the configuration and exit the setup wizard.
143
Option B. Local console directly attached V5R3/V5R4

Select your PC's operating system:
Windows XP continue directly below.
Windows 2000 on page 147.
Windows NT on page 149.
Windows XP
Local console directly attached for V5R3 & V5R4
Setup window.
Installing Operations Console Connection Modem for Windows XP - V5R3 &

V5R4
1. Click Start Control Panel.
6. Click Have Disk.
enter it here. Then, go to step 8.
If you do not know the path, continue with step 7.
144

9. Click Next.
click Next.
13. Continue with Configuring a local console directly attached to the system - V5R3 & V5R4
directly below.
Windows XP
Configuring a local console directly attached to the system - V5R3 & V5R4
configuration.
Note: The configuration wizard starts automatically. If it does not start automatically, do
the following:
Click Connection New Connection.
click Next.
145
10. Click Finish on the Complete window.
Windows 2000
Local console directly attached for V5R3/V5R4
Setup window.
Installing Operations Console Connection Modem for Windows 2000 - V5R3 &
V5R4
146
3.
4.
5.
6.
Click the Modems tab.

Click Add to display the Install New Modem panel.
Select Dont detect my modem; I will select it from a list, and then click Next.
Click Have Disk.

9. Click Next.
11. Click Next.
14. Click OK.
15. Continue with Configuring a local console directly attached to the system directly below.
Windows 2000
configuration.
the following:
147
click Next.
148
Windows NT
Local console directly attached for V5R3/V5R4
Confirm installation of TCP/IP on the PC

Setup window.
Install Operations Console Connection Modem for Windows NT - V5R3 & V5R4
You must install the Operations Console connection modem that is shipped with Operations
Console in order for a local console to communicate with the server using the Operations
Console cable. Only use these instructions if you are configuring a local console directly attached
to the server or a local console directly attached to the server with remote access allowed.
To install:
1. Click Start > Settings > Control Panel, and then click Modems.
2. If the Install New Modem window appears, go to the next step.
If you are currently in the Modem Properties window, click Add.
3. Select Dont detect my modem; I will select it from a list, then click Next.
4. Click Have Disk...
5. Click Browse...
149
6. Navigate to drive:\path\Client Access\Aoc\Inf\ cwbopaoc.inf where drive: is the drive

where Client Access is installed.
Note: The default installation path
C:\Program Files\Ibm\Client Access\Aoc\Inf\cwbopaoc.inf.
7. Click Open, then click OK.
9. Click Next.
10. Click Finish.
11. Click OK.
Install or configure Remote Access Service (NT only)

Make sure that you install and set up Remote Access Service according to your intended
configuration. You only need to install Remote Access Service if you are using Windows NT.
You are going to add and configure the modems needed for your configuration even if you are
not installing Remote Access Service.
Important:
You may need your Windows NT Setup CD-ROM.
You may need to install Remote Access Service before installing the Windows NT
service pack.
To install or configure Remote Access Service:
1. Open the Network folder by doing the following:
a. Click Start and select Settings.
b. Click Control Panel.
c. Double-click Network.
2. Click the Services tab.
3. Do one of the following:
If Remote Access Service is listed, do the following:
a. Select Remote Access Service; then, click Properties.
If Remote Access Service is not listed, follow these instructions to install:
a. Put the Windows NT CD into the optical device drive (for example, a CD-ROM
drive), unless installing from a network drive.
b. Click Add.
150
c. Select Remote Access Service and click OK.

d. Set the path the Windows NT files will be read from, then click Continue. When
the necessary files have been copied, the Add RAS Device window should appear.
Read step 4, then, continue with step 5b.
4. Using Table 1, identify the correct modems that you need to add in Remote Access
Service for your Operations Console configuration.
Important: You may have to add more than one modem in Remote Access Service to
satisfy your intended configuration.
Under certain circumstances, such as when installing Windows NT and Remote Access
Service, you may have had to install a nonexistent modem. If so, any modem you intend
to use with Operations Console may not show up in the Add RAS Device window even
though it was previously installed. In these cases, you will need to Remove the previously
installed modem from Remote Access Service, and later from the Modems folder, since it
may be on the same COM port. In this way, the intended modem is made available to be
selected. Remote Access Service does not allow more than one modem for the same
COM port.
Table 1. Modems for Operations Console configurations for Windows NT
Desired configuration
Necessary modems
Local console directly attached to the
Operations Console connection
server
Operations Console connection and a PC
server with remote access allowed
modem
Remote console through dial-up support
A PC modem
Note:
1. The 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 an iSeries server. When it is present, it shows as AS400 Operations
Console Connection in the Remote Access Setup window.
5. To add the first or the only modem, do the following:
a. If you are in the Remote Access Setup window, click Add.
b. In the Add RAS Device window, select the modem.
c. Click OK. You should be at the Remote Access Setup window.
d. If you have satisfied the modems for your intended configuration, go to step 7.
6. If Table 1 indicates that you need to add another modem, add the modem as follows:
a. Click Add.
151
7. If the Remote Access Setup window has an AS400 Operations Console Connection entry
present,
a. Select AS400 Operations Console Connection, then click Configure.
b. Click Dial out only. Click OK.
c. Click Network.
d. Select TCP/IP. Click OK.
8. If the Remote Access Setup window does not have a PC modem present, go to step 11.
If the Remote Access Setup window does have a PC modem present, continue with step 9.
9. Select the PC modem. Then, click Configure. Do one of the following:
To configure only a remote console, select Dial out only.
To configure a local console to receive calls from a remote console through dial-up
support, select Receive calls only.
To configure as both, select Dial out and Receive calls.
Click OK.
10. Click Network on the right side of the window. Do one of the following:
To configure only a remote console through dial-up support, follow these steps:
a. For Dial out Protocols, select the TCP/IP check box.
b. Click OK.
c. Go to step 11.
To configure a local console to receive calls from a remote console, select the
following values:
a. For Allow remote clients running, select the TCP/IP check box and clear any others
(unless your own operation requires them).
b. For Encryption settings, click Allow any authentication including clear text.
c. Click Configure (located to the right of TCP/IP).
d. For Allow remote TCP/IP clients to access, click This computer only.
e. Click Use Static address pool.
f. In the Begin field, type the address 192.168.0.5
g. In the End field, type the address 192.168.0.24
h. Select the Allow remote clients to request a predetermined IP address check box.
i. Click OK.
j. Click OK again. Go to step 11.
To configure as both a local console that receives calls and a remote console, select
a. For Dial out Protocols, select the TCP/IP check box and clear any others (unless
your own operation requires them).
b. For Allow remote clients running, select the TCP/IP check box and clear any others
c. For Encryption settings, click Allow any authentication including clear text.
d. Click Configure (located to the right of TCP/IP).
152
e. For Allow Remote TCP/IP client to access, click This computer only.
f. Click Use Static address pool.
g. In the Begin field, type the address 192.168.0.5
h. In the End field, type the address 192.168.0.24
i. Select the Allow remote clients to request a predetermined IP address check box.
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 OK.
c. If you get a message that says that Remote Access Service has been successfully
installed, click OK.
This message does not appear for all installations.
d. Click Close.
e. Click Yes to restart.
12. Continue with Install Microsoft service pack directly below.
Install Microsoft service pack

Anytime Remote Access Service is either installed or reinstalled, you need to install Windows
NT Service Pack 6 (minimum level) before attempting to use Operations Console.
If you need a service pack and have Internet capabilities, download the latest Service Pack from
http://www.microsoft.com. Otherwise, contact Microsoft for the latest update.
153
Windows NT
configuration.
the following:
click Next.
154
155
Option C. Local console directly attached with remote

support - V5R3 & V5R4 Only
This section is structured for a top to bottom flow. If you do NOT need to perform the
function skip to the next topic until you have your connection created and the instructions
indicate it is the end of instructions for your PC's operating system.
Select your PC's operating system

Windows XP Continue directly below.
Windows XP
Local console directly attached with remote access allowed V5R3 &
V5R4
Installing Operations Console Connection Modem for Windows XP V5R3 &
V5R4
Setup window.
Installing Operations Console Connection Modem for Windows XP

156
6. Click Have Disk.
9. Click Next.
click Next.
Install PC modem for Windows XP V5R3 & V5R4

If you are installing a PC modem that requires specific drivers, use the instructions that the
modem manufacturer provides. Otherwise, follow these steps to install the PC modem:
1. Click Start > Settings > Control Panel > Phone and Modem Options.
2. If you are currently in the Modems tab of the Phone and Modem Options folder, click Add
and then click Next.
If you are at the Install New Modem window, click Next. The PC should find the new
modem and report its location.
3. When the window shows the modem it found, click Next to accept it. The PC will now
load the driver code to support it.
4. Click Finish to return you to the Phone and Modem Options folder.
5. Close the Phone and Modem Options folder.
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.
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.
157
Create and configure incoming connections for Windows XP

Complete the following steps to create and configure incoming connections for Windows
2000.
1. Click Start >Settings > Network Connections.
2. Click New Connection. The Welcome window appears.
3. Click Next.
4. Click Set up an advanced connection. Then, click Next.
5. Click Accept incoming connections. Then, click Next.
6. Select the check box for the PC modem that is going to receive the calls from the remote
console.
Make sure that the AS400 Operations Console Connection check box is not selected. If
other check boxes are selected, do not change them.
Then, click Next.
7. Click Do not allow virtual private connections.
Note: If you have a virtual private network (VPN), leave this check box unchecked.
Then, click Next.
8. Select or add any users who are going to dial into the local console. Then, click Next.
9. Select the Internet Protocol (TCP/IP) check box (if needed). Then, click Properties.
10. Make sure that the Allow callers to access my local area network check box is selected.
11. If your network uses Dynamic Host Configuration Protocol (DHCP), click Assign TCP/IP
addresses automatically using DHCP. Then, go to the next step.
If your network does not use DHCP, click Specify TCP/IP addresses. Then, do the
following to specify the addresses:
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. Click Next.
14. Click Finish to save Incoming Connections.
158
Grant remote access for Windows XP

To grant remote access using Windows XP Incoming Connections Properties:
1. Click Start.
2. Select Settings.
3. Select Control Panel.
4. Select Network and Dial-up Connections.
5. Click Incoming Connection Properties.
6. In the Users allowed to connect field, select the check box next to the user ID for which
you want to grant remote access.
Configuring a local console directly attached with remote access allowed for
Windows XP
configuration.
the following:
click Next.
159
10. Select attended or unattended mode.
Attended mode will present the sign-on window when a configured connection is
attempting a connection.
Unattended mode does not automatically display the connection's sign-on window.
To sign on you need to perform a request control.
Click Next.
11. The Set up User Access is a reminder that this setup must be performed prior to making a
connection. Click Next.
Note: If you want to make changes, go to Properties Configuration tab to select or deselect the
function you do not want started for that connection.
160
Windows 2000
Local console directly attached with remote access allowed V5R3 &
V5R4
Installing Operations Console Connection Modem for Windows 2000 V5R3 &
V5R4
Setup window.
Installing Operations Console Connection Modem for Windows 2000

6. Click Have Disk.
9. Click Next.
11. Click Next.
14. Click OK.
161
Install PC modem for Windows 2000 - V5R3 & V5R4

1. Click Start > Settings > Control Panel > Phone and Modem Options.
2. If you are currently in the Modems tab of the Phone and Modem Options folder, click Add
and then click Next.
4. Click Finish to return you to the Phone and Modem Options folder.
6. If you get a message that indicates that you need to restart the PC before you can use the
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.
Create and configure incoming connections for Windows 2000

Complete the following steps to create and configure incoming connections for Windows
2000.
1. Click Start >Settings > Control Panel.
3. Click New Connection. The Welcome window appears.
4. Click Next.
5. Click Accept incoming connections. Then, click Next.
6. Select the check box for the PC modem that is going to receive the calls from the remote
console.
Make sure that the Operations Console Connection check box is not selected. If other check
boxes are selected, do not change them.
Then, click Next.
7. Click Do not allow virtual private connections.
Note: If you have a virtual private network (VPN), leave this check box unchecked.
Then, click Next.
8. Select or add any users to dial into the local console. Then, click Next.
9. Select the Internet Protocol (TCP/IP) check box (if needed). Then, click Properties.
162
10. Make sure that the Allow callers to access my local area network check box is selected.
11. If your network uses Dynamic Host Configuration Protocol (DHCP), click Specify TCP/IP
addresses automatically using DHCP. Then, go to the next step.
If your network does not use DHCP, click Specify TCP/IP addresses. Then, do the
following to specify the addresses:
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. Click Next.
14. Click Finish to save Incoming Connections.
Grant remote access for Windows 2000

To grant remote access using the Windows 2000 Incoming Connections:
1. Click Start.
2. Select Settings.
3. Select Control Panel.
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.
Configuring a local console directly attached with remote access allowed for
Windows 2000
configuration.
the following:
163

click Next.
Click Next.
164
Windows NT
Local console directly attached to the server with remote access allowed
V5R3 & V5R4
Confirm installation of TCP/IP on the PC for Windows NT
Installing Operations Console Connection Modem for Windows NT

Setup window.
165
Install Operations Console Connection Modem for Windows NT

You must install the Operations Console connection modem that is shipped with Operations
Console in order for a local console to communicate with the server using the Operations
Console cable. Only use these instructions if you are configuring a local console directly attached
to the server or a local console directly attached to the server with remote access allowed.
To install:
1. Click Start > Settings > Control Panel, and then click Modems.
2. If the Install New Modem window appears, go to the next step.
If you are currently in the Modem Properties window, click Add.
3. Select Dont detect my modem; I will select it from a list, then click Next.
4. Click Have Disk...
5. Click Browse...
6. Navigate to drive:\path\Client Access\Aoc\Inf\ cwbopaoc.inf
C:\Program Files\Ibm\Client Access\Aoc\Inf\cwbopaoc.inf.
7. Click Open, then click OK.
9. Click Next.
10. Click Finish.
11. Click OK.
Install PC modem for Windows NT

1. Click Start > Settings > Control Panel > Modems.
2. If you are currently in the Modems Properties window click Add, and then Next.
4. Click Finish to return you to the Modems Properties window.
5. Close the Modems Properties window.
Note: You must add and configure this modem in Remote Access Service before the
modem can be used by Operations Console.
166

Important:
You may need to install Remote Access Service before installing the Windows NT service
pack.
b. Click Add.
167
COM port.
Necessary modems
server
modem
A PC modem
Note:
a. Click Add.
present,
c. Click Network.
168

To configure a local console to receaive calls from a remote console through dial-up
Click OK.
b. Click OK.
c. Go to step 11.
following values:
i. Click OK.
j. Click OK.
k. Click OK again.
169

a. Click Continue.
click OK.
d. Click Close.
12. Continue with Install Microsoft service pack.

Grant remote access for Windows NT

To grant remote access using the Windows NT User Manager:
1. Click Start.
2. Select Programs.
3. Select Administration Tools.
4. Select User Manager.
5. In User Manager, select New User from the User menu and enter the user name and
password information, or double-click the desired user if it is already defined.
6. On the User Properties dialog, click Dial-In.
7. Select Grant dial-in permission to user.
8. Click OK twice.
170
Configuring a local console directly attached to the server with remote access
allowed for Windows NT
configuration.
the following:
click Next.
Click Next.
171
Note: If you want to make changes, go to Properties Configuration tab to select or deselect the
function you do not want started for that connection.
172
Remote console through dial-up support (V5R3 & V5R4

only)
Important: These instruction assume got here from earlier in this chapter and not from the table
of contents.
If you did not start at the beginning of this chapter return to Chapter 6: Setting up Operations
Console on page 125 and perform any necessary work before it returns you here.
Complete the following sections in order to set up a remote console through dial-up support.
Select your PC's operating system

Windows XP continue directly below.
Windows XP
Installing the PC modem for Windows XP
You must install the PC modem if you are configuring a local console that is directly attached with
remote access allowed or a remote console through dial-up support.
4. Click Add... to display the Install New Modem panel, and then click Next.
5. When the window displays the modem it finds, click Next to accept it. The PC now loads
the driver code to support it.
6. Click Finish to return to the Phone and Modem Options folder.
8. If you receive a message indicating you need to restart the PC before you can use the
You might be prompted to restart the PC. If this is the case, click Yes or OK to perform
the shutdown.
Note: If you are not prompted to restart the PC, restart the PC to force a rewrite of
changed data.
173
Configuring a remote console through dial-up support on the PC

Complete the configuration of your remote console through dial-up support on the PC by stepping
through the Operations Console configuration wizard.
configuration.
To configure a new remote console through dial-up support, follow these steps:
the following:
4. On the Select Configuration window, select Remote console through dial-up support and click
Next.
5. On the iSeries and Local Console Name window, enter the name of configured connection
as it appears at the local console directly attached with remote support. Then enter the name
of the PC that this PC will be connecting to in the Computer name field. Click Next.
6. Click the Dial-up Networking button.
7. Be sure the correct PC modem is selected and then enter the phone number of the remote
PC. Click OK.
8. Click Next.
9. Click Finish to save the configuration.
174
Windows 2000
Installing the PC modem for Windows 2000
You must install the PC modem if you are configuring a local console that is directly attached with
remote access allowed or a remote console through dial-up support.
4. Click Add... to display the Install New Modem panel, and then click Next.
5. When the window displays the modem it finds, click Next to accept it. The PC now loads
the driver code to support it.
6. Click Finish to return to the Phone and Modem Options folder.
8. If you receive a message indicating you need to restart the PC before you can use the
You might be prompted to restart the PC. If this is the case, click Yes or OK to perform
the shutdown.
Note: If you are not prompted to restart the PC, restart the PC to force a rewrite of
changed data.
175

configuration.
the following:
Next.
PC. Click OK.
8. Click Next.
176
Windows NT
Installing the PC modem for Windows NT
1. Click Start > Settings > Control Panel > Modems.
2. If you are currently in the Modems Properties window click Add, and then Next.
4. Click Finish to return you to the Modems Properties window.
5. Close the Modems Properties window.
Note: You must add and configure this modem in Remote Access Service before the
modem can be used by Operations Console.

Important:
You may need to install Remote Access Service before installing the Windows NT service
pack.
177

b. Click Add.
COM port.
Necessary modems
server
modem
A PC modem
Note:
178

a. Click Add.
present,
c. Click Network.
To configure a local console to receive calls from a remote console through dial-up
Click OK.
b. Click OK.
c. Go to step 11.
179
following values:
i. Click OK.
j. Click OK.
k. Click OK again.
a. Click Continue.
click OK.

d. Click Close.
12. Continue with Install Microsoft service pack directly below.
180


configuration.
the following:
Next.
PC. Click OK.
8. Click Next.
181
182
Configuring a remote control panel or virtual control panel

To set up a virtual control panel, see Configuring a virtual control panel (VCP) on page 185.
Configuring a remote control panel (RCP)

To configure a remote control panel directly attached or with a local console on a network (LAN)
you configure a connection using the instructions above, if one doesn't already exist. To add this
function, follow these steps:
1. Select the configured connection you want to work with.
Note: The connection needs to show a status of Disconnected or Connected to access the
properties. If you receive a message that some changes will take affect at the next
connection, click OK.
2. Click Connections then select Properties.
3. Select the Configuration tab.
4. Use one of the following according to your configuration:
For a Local console directly attached with or without remote support
Select Serial or Parallel and the port it is connected to
For a Local console on a network (LAN)
Under Use remote control panel select or deselect the check box.
Note: If the check box is already checked but is greyed out it is indicating that the
configured connection's service tools device ID isn't currently authorized to support the
RCP. This is normal before the first connection attempt.
If the local console on a network (LAN) connection status shows Connected and you did not get the
RCP graphical interface, do one the following to authorize the service tools device ID to use the
RCP functions:
For a V6R1 client and V6R1 Licensed Internal Code, do the following:
1. Look in the Operations Console user interface for the VCP connection. In the
Configuration field, the first item of information is the currently used service tools
device ID. Take note of this name.
2. To authorize the service tools device ID, do the following:
1. If you are using DST, select Work with DST environment.
2. If you are using SST, select Work with service tools user IDs and devices.
b. Select Service tools device IDs.
c. Check the attributes for the device ID by selecting option 7 (Change attributes)
next to the associated ID and then press Enter.
d. Grant authority to the service tools device ID by entering a 2 for the entry Partition
remote panel entry for the system or partition, then press Enter.
e. Exit SST or return to the DST main menu.
183
3. To disconnect the configuration, follow these steps:

a. Under Connection, select the configuration name. This is the name that Operations
Console uses to refer to a specific system.
b. From the Connection menu, select Disconnect. The connection status shows
Disconnecting until it completes with a status of Disconnected.
4. Reconnect the connection. You should get the graphical RCP interface.
For all other levels of code, do the following:

1. Select the VCP configuration and go into Properties. On the General tab you will see
the currently used service tools device ID. Take note of this name then exit
Properties.

4. Reconnect the connection. You should get the graphical RCP interface.
184
Configuring a virtual control panel (VCP)

To set up a VCP using V5R3 or V5R4 see Configuring a virtual control panel (VCP) - V5R3 &
V5R4 on page 191.
Configuring a virtual control panel (VCP) - V6R1

The VCP connects using the console's serial cable and a separate configured connection which
uses the wizard path for a local console on a network (LAN).
Prepare for the VCP configuration

To prepare an install of the VCP, do the following:
1. If the console is currently the only function being provided, go to Create the VCP
configuration - V6R1 on page 187.
If your current Operations Console configured connection includes the remote control
panel, use the following steps to configure the connection for just the console.
Note: Unpredictable results may occur if both a directly connected remote control panel
and a virtual control panel exit to the same system.
a. To remove the remote control panel from the configuration, the connection status
must be Disconnected.
To disconnect the configuration, follow these steps:
i. Under Connection, select the configuration name. This is the name that
Operations Console uses to refer to a specific system.
ii. From the Connection menu, select Disconnect. The connection status shows
b. Select the configuration name that you want to change.
c. From the Connection menu, select Properties.
d. Select the Configuration tab.
e. Remove the check from the Remote Control Panel option.
f. Select OK.
g. Reconnect the console.
2. Determine the value of the option Autocreate service tools device IDs, if needed. By
default, a V6R1 system is automatically configured to automatically create any needed
service tools device IDs.
Note: You can only access the option using Dedicated Service Tools (DST).
185
To verify the autocreate service tools device ID value, follow these steps:
a. Access Dedicated Service Tools (DST).
b. Select Work with DST environment.
c. Select Service tools security data.
d. Verify the value of the option Autocreate service tools device IDs is not zero.
e. Press F3 until you are back to the DST main menu.
3. Complete the following step only if the option Autocreate service tools device ID has a
value of 0 and you want to leave this function turned off:
a. Select Work with DST environment > Service tools device IDs.
b. Enter a 1 next to the Device ID field. Then enter a name to call the VCP's device ID
and press Enter.
c. Optionally, enter a description. Then press Enter.
d. You have now created a device ID for the VCP connection from one PC.
e. Check the attributes for the device ID by selecting option 7 (Change attributes).
Grant authority to the service tools device ID, if needed.
f. Press F3 until you are back to the DST main menu.
4. If you will be 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. To verify or set this
service tools user privilege, do the following:
a. Select Work with DST environment > Service tools user IDs.
b. Move the cursor to the user you want to verify or set the privileges for and place a 7
on the same line and press Enter.
c. 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.
eligible to use the mode button. For example, the user has the remote panel key
privilege but will not have the mode function available until the keystick is present.
For systems without the keystick, only the user ID remote panel key privilege is
necessary.
d. You can now exit back to the DST main menu. It is recommended that you leave the
console here until you have completed a successful VCP connection.
186
Create the VCP configuration - V6R1

You are now ready to create a new configuration for the VCP on the client PC.
1. From the Connection menu, select New Connection.
2. Select Next.
If the window asking about prerequisites appears, select Yes.
3. Leave the option Local Area Network (LAN) selected and click Next.
4. Enter a name to refer to your VCP connection and the partition ID, then click Next..
Notes: If the PC you are working with is connected to a network, do not use a name that
can be found on that network.
5. If the Service TCP/IP Address field contains a value, you will have to enter another name.
The name you used was found on your network or in the hosts file.
To check the hosts file, do one the following:
Search for the file
a. Start > Search > For files or folders.
b. Enter hosts as the file name to search for and press Search.
Manually find the file
a. Start Explorer or similar file manager program.
b. Expand drive C (or whatever drive letter is used for the operating system.
c. Expand the following path:
d.
e.
f.
Windows (or whatever name is used for your PC's operating system) > System 32 >
drivers
Select etc.
Double-click the file name hosts and if prompted, select a file editor like
Notepad.
If you find the name you want to use in the list and it won't be used any more
then you can delete the entry and save the file.
If the entry needs to remain active then you need to select a different name for
the VCP configuration.
If no TCP/IP address is listed, enter 192.168.0.2, then click Next.
187
Note: In some cases, the address 192.168.0.n may have been previously used for
something other than Operations Console. In those cases the user may have had to use a
different base address for 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. Check the registry 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. .
7. Enter a serial number in the System serial number field. This does not have to be the real
system serial number. Then, select the partition the VCP will control and click Next.
Note: When setting up VCP for a Power-processor-based system, there is no partition 0.
8. Enter the name of the device ID you will be using for the VCP connection authentication.
By default, you can use QCONSOLE if it hasn't been used.
If you created a specific device ID, enter the name you assigned it during the creation
process. Then click Next.
9. Click Finish.
10. Select the VCP configuration and go into Properties. Select the Configuration tab and
deselect the console option. Select the remote control panel option, if needed. Then,
click OK to exit Properties.
You have completed the configuration for the VCP connection.
Start a connection for the console (your original connection), if needed. Sign on normally, if
necessary, and wait for the console window to appear.
Now you can connect the VCP connection.
188

The LAN Service Tools Sign-on window opens.
Enter any service tools user ID and password, commonly referred to as the DST user ID and
password. Since this is authenticating the connection and not setting up any authorities to the
work, there is no difference between using 11111111 and 11111111 or QSECOFR and
<password>.
If you have previously created additional service tools user IDs, you could use any of those as
well.
If the connection status shows Connected and you did not get the RCP graphical interface, do the
following to authorize the service tools device ID to use the RCP functions:
For a V6R1 client and V6R1 Licensed Internal Code, do the following:
1. Look in the Operations Console user interface for the VCP connection. In the
Configuration field, the first item of information is the currently used service tools
device ID. Take note of this name then exit Properties.
4. Reconnect the VCP connection. You should get the graphical RCP interface.
Note: If this device connects at a later time and gets assigned a different service tools
device ID by the system the new ID probably have been reset and therefore it loses the
authority you just granted. This would require you to re-authorize this service tools
device ID for this device or any other device that this ID is assigned to. To prevent this
from happening you can create a service tools device ID specifically for this
configuration, authorize it, and it will not get reset.
189
For all other levels of code, do the following:

1. Select the configuration name that you want to change.
2. From the Connection menu, select Properties. On the General tab is the name of the
currently used service tools device ID. Take note of this name then exit Properties.
Note: The connection needs to show a status of Disconnected or Connected to access
the properties. If you receive a message that some changes will take affect at the next
You can now exit DST or SST, if necessary.

190
Configuring a virtual control panel (VCP) - V5R3 & V5R4

Prepare for the VCP configuration - V5R3/V5R4
To install the VCP using V5R3 or V5R4, do the following:
Change the current configuration to console only
If your current Operations Console configured connection includes the remote control panel, use
the following steps to configure the connection for just the console.
1. To remove the remote control panel from the configuration the connection status must be
Disconnected. To disconnect the configuration, follow these steps:
a. If your local console is running in unattended mode and you have not requested
control, do the following to get control:
i. Select the configuration name. This is the name that Operations Console uses to
refer to a specific iSeries server.
ii. From the Connection menu, select Request Control.
b. If the Service Device Sign-on window appears, select Cancel.
c. Select the configuration name. This is the name that Operations Console uses to refer
to a specific iSeries server.
d. From the Connection menu, select Disconnect. The connection status shows
3. From the Connection menu, select Properties.
4. Select the Configuration tab.
5. Remove the check from the Remote Control Panel option.
6. Select OK.
7. Reconnect the console, if needed.
Create a service tools device ID using an existing console
The virtual control panel (VCP) requires an available, unused service tools device ID.
If the server does not use, or never did use, Operations console(LAN) for the console type, you can
use the existing service tools device ID of QCONSOLE. Continue with Check user ID for
permissions on page 193.
If you aren't certain about the status of an available service tools device ID it would be best if
you created one specific for the VCP.
To create a service tools device ID follow these steps:
191
2. Select Service tools device IDs.

Note: By default, the Service tools device IDs option is not available from SST. If you
receive the message The user can not perform the option selected it indicates that the option
has not been made available. The unlock method can only be performed in DST.
To unlock this option for use in SST, do the following:
a. This function requires PTF MF32320 if you use V5R3, ensure you have this PTF
installed.
b. Access Dedicated Service Tools (DST).
c. Select Start a service tool.
d. Select Display/Alter/Dump.
e. Select Display/Alter storage.
f. Select Licensed Internal Code (LIC) data.
g. Select Advanced analysis. (You will have to page down to display this option.)
h. Page down until you find the FLIGHTLOG 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 FLIGHTLOG.
i. Enter the option SEC UNLOCKDEVID.
Note: If you want to secure this option later use the option SEC LOCKDEVID.
Alternatively, if the system uses V5R4, or later, you can unlock the service tools
device IDs by performing the following steps in DST:
1. Access service tools using DST.
2. Select Work with DST environment > Service tools security data.
3. Type a 7 next to the Work with lock for device IDs from SST option and press
Enter.
The status displays as Enabled, indicating that the service tools device ID has been
unlocked.
3. Enter a 1 next to the Device ID field. Then enter a name to call the VCP's device ID and
press Enter.
4. If prompted, enter a password into both password fields. Optionally, enter a description.
Then press Enter.
Note: It is recommended that you assign the password as the name of the service tools
device ID in upper case.
5. You have now created a device ID for the VCP connection from one PC.
6. Optionally, you can check the attributes for the device ID by selecting option 7 (Change
attributes). By default, the console and partition remote panel for partition 0 (current
partition) will be granted. Grant this attribute, if necessary.
7. Use F3 to go back to the DST or SST main menu.
192
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. To verify or set this service tools user privilege, do the
following:
2. Select Service tools user IDs.
3. Move the cursor to the user you want to verify or set the privileges for and place a 7 on
the same line and press Enter.
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.
eligible to use the mode button. For example, the user has the remote panel key privilege
but will not have the mode function available until the keystick is present. For systems
without the keystick, only the user ID remote panel key privilege is necessary.
5. You can now exit back to the DST or SST main menu. It is recommended that you leave
the console here until you have completed a successful VCP connection.
Create the VCP configuration - V5R3 & V5R4

Use the following instructions to create a new connection configuration specifically for the
virtual control panel.
1. From the Connection menu, select New Connection.
2. Select Next. If the window asking about prerequisites appears, select Yes.
3. Leave the option Local Area Network (LAN) selected and click Next.
4. Enter a name to refer to your VCP connection and make the partition selected 0, then
click Next.
Note: If the PC you are working with is connected to a network, do not use a name that
can be found on that network.
5. If the Service TCP/IP Address field contains a value, you will have to enter another name.
The name you used was found on your network or in the hosts file.
To check the hosts file, do one the following:
Search for the file
a. Start > Search > For files or folders.
b. Enter hosts as the file name to search for and press Search.
193
Manually find the file

a. Start Explorer or similar file manager program.
b. Expand drive C (or whatever drive letter is used for the operating system.
c. Expand the following path:
d.
e.
f.
Windows (or whatever name is used for your PC's operating system) > System 32 >
drivers
Select etc.
Double-click the file name hosts and if prompted, select a file editor like
Notepad.
If you find the name you want to use in the list and it won't be used any more
then you can delete the entry and save the file.
If the entry needs to remain active then you need to select a different name for
the VCP configuration.
If no TCP/IP address is listed, enter 192.168.0.2.

Note: In some cases, the address 192.168.0.n may have been previously used for
something other than Operations Console. In those cases the user may have had to use a
different base address for 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. Check the registry key IP Address.
Use the IP address reported on your PC to validate the VCP address.
You may also have to check the entries in the hosts file on your PC for a matching name
or 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.
7. Enter a serial number in the System serial number field. This does not have to be the real
system serial number. Click Next.
8. Enter the name of the device ID you will be using for the VCP connection authentication.
By default, you can use QCONSOLE if it hasn't been used.
If you created a specific device ID, enter the name and password you assigned it during
the creation process. Then click Next.
194
9. If prompted, enter a password and enter it a second time to confirm it.

This password is only used by the PC for the VCP connection and is not known at the
server. For example, if you entered access as the password you will use access later to
sign on. Click Next.
10. Click Finish.
You have completed the configuration for the VCP connection.
Start a connection for the console (your original connection), if needed. Sign on normally, if
necessary, and wait for the console window to appear.
Now you can connect the VCP connection.
You will get the Service Device Sign-on window with an extra field. The Access password field is
where you enter the password you chose during the setup wizard. Enter the password you used
in the Specify Access Password window.
Enter any service tools user ID and password, commonly referred to as the DST user ID and
password. Since this is authenticating the connection and not setting up any authorities to the
work, there is no difference between using 11111111 and 11111111 or QSECOFR and
<password>.
If you have previously created additional service tools user IDs you could use any of those as
well.
195
If the connection status shows Connected and you did not get the RCP graphical interface, do the
following to authorize the service tools device ID to use the RCP functions:
2.
From the Connection menu, select Properties.
Note: The connection needs to show a status of Disconnected or Connected to access the
properties. If you receive a message that some changes will take affect at the next
On the General tab is the name of the currently used service tools device ID. Take note of
this name then exit Properties.
c. Check the attributes for the device ID by selecting option 7 (Change attributes) next
to the associated ID and then press Enter.
You can now exit DST or SST, if necessary.
196
Chapter 7: Twinaxial console

Supported twinaxial adapters
2720
PCI twinaxial Adapter (Pre-Power5 processor-based only)
2722
PCI twinaxial Adapter (Pre-Power5 processor-based only)
2746
PCI twinaxial Adapter (Requires IOP)
twinaxial can go into any Operations Console supported slot for console. This is usually the
LAN adapter slot since the asynchronous adapter is assumed to always be present.
Twinaxial console hardware environment

The twinaxial console is used to manage only the operating system and its resources. The HMC
or the ASMI is used to configure, manage, and repair Power-processor-based system hardware.
Note: If you plan to connect a twinaxial console to a Power6 processor-based server, you must
have an HMC.
If you are setting up a new twinaxial console or changing to this console type, consider the
following:
Setting up a twinaxial console

Before you set up a twinaxial console, ensure that you have completed the following tasks:
If you plan to use an HMC to manage your hardware, ensure that the HMC is set up and
configured. For HMC setup instructions, see Managing the Hardware Management
Console (HMC).
http://publib.boulder.ibm.com/infocenter/systems/topic/iphai/hmc.htm
If you plan to connect a twinaxial console to a Power6 processor-based server, you must
have an expansion unit and an HMC.
197
To set up a twinaxial console on a pre-Power5 processor-based system, or a Power-processorbased system not managed by an HMC, complete the following tasks:
1. Connect the twinaxial cable, if the cable is not already installed.
a. Locate the position the supported twinaxial adapter card.
If more than one position contains a console supporting adapter, select the card position
listed first. See Chapter 1: Reference on page 19 to determine, by model, which locations
support a twinaxial console.
Note:
The 2746 adapter requires an IOP which may restrict where it can be placed in the
system.
For Power6 processor-based systems the adapter must be placed in an expansion unit
which might require an HMC.
If your system is managed by an HMC then you will select the intended adapter in
the Console tag using the HMC.
b. Locate the 8-port (or 4-port) twinaxial attachment cable. Attach the cable to the
connector on the twinaxial adapter card.
c. Connect a twinaxial cable from the workstation that you will be using as the system
console to port 0 on the 8-port (or 4-port) twinaxial attachment cable.
Note: The workstation address of your console must be set to 0. To set the address, refer
to the reference material that was supplied with your workstation.
2. To power on the system, if needed, use one of the following methods:
On a pre-Power5 processor-based primary partition, standalone system, or a Powerprocessor-based system without an HMC, do these steps:

Complete the steps to prepare the system for a connection.
a. Plug in your system or uninterruptible power supply and attached expansion
units.
b. Open the control panel door on the front of the system. The control panel should
be lit and display 01 B N V=F. The system is not yet powered on.
Note: If you have to install Licensed Internal Code (LIC) substitute D for B and
M for N
i. Select function 02 by pressing the Increment () or Decrement ()
button on the control panel.
Tip: The Increment () and Decrement () buttons change the field
values, and the Enter button advances you from field to field.
198
iii. Using the Increment (), Decrement (), and Enter buttons, scroll
through the IPL types, logical key modes, and IPL speeds until 02 B N V
is displayed.
v. Using the Increment () or Decrement () button, select function 01,
and then press Enter.
Note: Expect a delay between the time when power is applied to the system
and when an initial program load (IPL) can be performed. When power is
initially applied to the system, the service processor performs a self-check and
the control panel remains blank for up to 2 minutes. Wait until the C1xxxxxx
progress codes are completed and 01 is displayed on the control panel before
you perform an IPL or change any control panel functions.
Use the primary partition on a pre-Power5 processor-based system to power on

a logical partition
b. Select Work with System Partitions.
d. Place a 1 on the line for the partition you will be powering on, then press Enter.
e. Answer any prompts presented.
f. Continue with step 3.
Using an HMC on a Power-processor-based system or partition, complete the following

task using one of the following methods to activate a system profile:
Using version 6 or earlier of the HMC, follow these steps:
c. In the contents area, open the server on which the system profile is located.
d. Open System Profiles.
e. Right-click the system profile and select Activate.
f. Click Continue.
g. Continue with step 3.
199
Using version 7 or later of the HMC, follow these steps:

a. In the Navigation pane, expand Systems Management > Servers, and click on the
target server.
b. In the Work area, select the box in the Select column next to the target partition.
c. Click the Tasks button, select Operations then Activate.
3. To have the new console type recognized, complete one of the following tasks, if needed:
Perform an initial program load (IPL) of the system, if needed.
OR
Use the OPSCONSOLE RESTART macro. For more information about the macro,
see use the OPSCONSOLE macro on page 215.
system.
4. For problems with the twinaxial console, such as a failed connection, see Beginning problem
analysis.
http://publib.boulder.ibm.com/infocenter/systems/topic/ipha5/begin_pa.htm
For problems IPLing the system that displays an SRC code, see Troubleshooting system
reference code (SRC) data on page 288.
200
Chapter 8: Thin console

IBM withdrew the 9944-100 Thin Console in April 2008 and last availability
was June 2008. Neoware will provide warranty service only. They are not
accepting orders for the C50 with the IBM flash code.
The thin console, IBM model 9944, is a Neoware C50 terminal tailored to support the operating
system as the console. This console solution will be available for Power5 processor-based
systems only. This console device provides a 5250 emulation session as a console only for
servers not managed by a Hardware Maintenance Console (HMC). This console device is not
supported on an ethernet network even if the server is already connected. A cable must connect
this device directly to the HMC access port on the server, and uses all virtual resources. A
device can be attached to the remaining HMC access port for an ASMI connection.
This device is only available in the U.S., Canada, and Western Europe. Neoware has all
responsibility for servicing the device itself. Contact Neoware for more information regarding
the device.
http://www.neoware.com/
http://www.neoware.com/support/support_request.html
Cabling and connecting the Thin Console

If you need to cable the Thin Console to the system, use this topic to do so.
Before making changes to the product, be sure to read the information in the Danger Notice.
Use an Ethernet cable to connect this console device directly to an HMC access port (either
HMC 1 or HMC 2) on the back of the server.
Restrictions:
Do not attach another Thin Console or an HMC to the remaining HMC port.
This console device is not available on an Ethernet network, even if the server is already
connected.
201
OR
Use the OPSCONSOLE RESTART macro. For more information about the macro, see
use the OPSCONSOLE macro on page 215.
system.
Start the console and power on the system

1. Power on the Thin Console, if needed.
2. To power on the system, if not already powered on.
Complete the steps to prepare the system for a connection.
a. Plug in your system or uninterruptible power supply and attached expansion units.
b. Open the control panel door on the front of the system. The control panel should be
lit and display 01 B N V=F. The system is not yet powered on.
Note: If you have to install Licensed Internal Code (LIC) substitute D for B and M
for N
i. Select function 02 by pressing the Increment () or Decrement () button on
the control panel.
Tip: The Increment () and Decrement () buttons change the field values,
and the Enter button advances you from field to field.
202
iii. Using the Increment (), Decrement (), and Enter buttons, scroll through
the IPL types, logical key modes, and IPL speeds until 02 B N V is displayed.
v. Using the Increment () or Decrement () button, select function 01, and
then press Enter.
Note: Expect a delay between the time when power is applied to the system and
when an initial program load (IPL) can be performed. When power is initially applied
to the system, the service processor performs a self-check and the control panel
remains blank for up to 2 minutes. Wait until the C1xxxxxx progress codes are
completed and 01 is displayed on the control panel before you perform an IPL or
change any control panel functions.
3. For problems with the Thin Console or it failed to make its initial connection, see
Troubleshooting problems when using the Thin Console. For problems IPLing the system
that displays an SRC code, see Troubleshooting system reference code (SRC) data on
page 288.
203
Troubleshooting problems when using the Thin

Console
For problems concerning the Thin Console, your server, and the connection between the two,
choose from the following options:
Troubleshooting hardware problems directly below.

Troubleshooting, using the status codes on page 205.
Troubleshooting hardware problems

Review the following table for hints and tips on how to resolve common problems that might
occur when using the Thin Console. You can also refer to the documentation that came with
your console device or see http://www.neoware.com/
Troubleshooting hardware problems
Symptom
Problem and recovery tasks
The display of the Thin
There might be a hardware problem with the Thin
Console is completely
Console or monitor, or there might be a setup problem.
blank.
Follow these steps to resolve the problem:
1. Verify that the cabling is secure and accurate.
2. Verify that the Thin Console and monitor are powered
on.
3. Reset the default monitor resolution setting. Refer to
the documentation that came with the console device or
see http://www.neoware.com/.
The keyboard is not
This might be a hardware problem or it might be that the
working correctly.
keyboard is set to a location that does not match the
current keyboard setting. Refer to the documentation that
came with your console device or see
http://www.neoware.com/.
You cannot view wide
Set the resolution of the Thin Console to 1024 x 768.
displays (such as spool
files) using the 5250
console.
204
Troubleshooting, using the status codes

Review the following table for hints and tips on how to resolve common problems that might
occur while the Thin Console is becoming active.
Thin Console status codes
Symptom
The status field does not
continue to display system
status after displaying 00.xx.
The status field displays

status code 10.xx, and then
prompts you for the HMC
access password. After
entering the password, the
user ID and password cannot
be authenticated.

status after displaying 10.xx
or 20.xx.
Recovery tasks
The Thin Console is not able to find an active service processor. Complete
these steps to resolve the problem:
1. Verify that the Ethernet cable is plugged into either the HMC 1 or HMC 2
port on the back of the server.
2. Verify that the Ethernet ports on both the server and the Thin Console are
showing link-active and activity lights.
3. Verify that the HMC port on the server is configured with either the
192.168.3.147 or the 192.168.2.147 IP address (manufacturing defaults). If
the port is not configured using one of these IP addresses, see Restoring
your server to factory settings.
http://publib.boulder.ibm.com/infocenter/systems/topic/iphbp/factorysettings.ht
m
4. Verify that the service processor is powered on by noting whether the
control panel display is active.
5. Restart the Thin Console to find out if the problem is reproducible.
6. Isolate faulty hardware problems by using the other HMC port at the back
of the server, using another Ethernet cable, or by using another Thin
Console.
Complete these steps to resolve the problem:
1. Verify that the keyboard is set to a location that matches the current
keyboard setting.
2. Verify that the Caps Lock, Num Lock, Scroll Lock keys are off.
3. Change the HMC access password to a new value by logging into ASMI as
the administrator. See Changing ASMI passwords page 352.
http://publib.boulder.ibm.com/infocenter/systems/topic/iphby/chgpwd.htm
4. Use a password with only uppercase English alphabetic characters. If this
resolves the problem, contact Neoware customer support at
http://www.neoware.com/support/support_request.html
Complete these steps to resolve the problem:
1. Verify that another Thin Console or an HMC is not connected alongside this
Thin Console.
2. Restart the Thin Console to determine if the problem is reproducible.
The Thin Console displays status code 30.xx until the console device is
powered on and PHYP standby is reached. If the Thin Console remains in state
30.xx, then try restarting the console device. If the state is 0x0F and the status
does not display system status after you see 30.xx, see Contacting IBM service
and support.
http://publib.boulder.ibm.com/infocenter/systems/topic/ipha5/contacting_suppo
rt.htm
205
Symptom
Recovery tasks
Verify that another Thin Console or an HMC is not connected alongside this
Thin Console. If so, disconnect the other console device or use it as the system
console.
Remaining in this state means that the Thin Console has completed
initialization of the firmware communication and has not successfully started
communication with the Licensed Internal Code in the operating system.
Connection progress stops at

60.00 (of 100) .
The connection progress stops because console access is denied. This is normal
when the console type value is not set to a 4. For instructions about how to
change the console type value, see Changing Consoles - Power-processor-based on page
109.
206
Chapter 9: HMC 5250 console

OR
Use the OPSCONSOLE RESTART macro. For more information about the macro,
see use the OPSCONSOLE macro on page 215.
system.
Note: The remote HMC client is not able to start a 5250 emulator.
Start a 5250 console locally

To activate a system profile using version 6 or earlier of the HMC, follow these steps:
1. In the navigation area, open Server and Partition.
2. Select Server Management.
3. In the contents area, open the server on which the system profile is located.
4. Open System Profiles.
5. Right-click the system profile and select Activate.
6. Click Continue.
7. In the contents area, right-click on the partition and select Open dedicated 5250 console or
Open shared 5250 console.
If you select Shared, you must enter a session key that can be used by another user with
another 5250 emulator.
If you are the first user, the session key is entered twice to verify accuracy and it is not
echoed to the window as you type. Selecting this option allows you to:
Share a console session
Display the same logical partition console windows
Navigate each of the logical partition console windows
207
If you select Open dedicated 5250 console, other users are not able to share the session
with you.
To activate a system profile using version 7 or later of the HMC, follow these steps:
Note: You cannot perform this task remotely.
Do the following:
1. In the Navigation pane, expand Systems Management > Servers, and click on the target
server.
2. In the Work area, select the box in the Select column next to the target partition.
3. Click the Tasks button, select Operations then Activate.
4. Click the Tasks button, then Console Window, and then click Open Shared/Dedicated 5250
Console. The same function can also be accessed by using the partition pop-up menu
button or by using the Task pane (if enabled).
If you need a remote 5250 console, follow the instructions below.
Connecting to a 5250 console remotely

The remote support for HMC 5250 can use the same SSL configuration as System Manager
Security on the HMC. For more information, see System Manager Security.
http://publib.boulder.ibm.com/infocenter/systems/topic/iphai/clientserver.htm
To connect to a 5250 console remotely, you must use one of the following emulators:
IBM Client Access PC5250 emulator, Version 5, Release 3 with PTF SI13587 or later
Note: To view your service pack level, select Start --> Programs --> IBM Client Access -->
Service --> Check Service Level.
IBM Personal Communications 5250 emulator, Version 5.7 or later for V5R3 clients and
Version 5.8 or later for V5R4 and later clients.
To connect remotely, complete the following steps:

1. To configure your PC that is running Windows, do the following:
a. Open the 5250 emulator application on your PC.
b. Create a new session.
c. In the Configure PC5250 window, type the HMC host name or IP address in the
System Name field and indicate the port number. Type 2300 into the port number field
if you are not using SSL, or 2301 if you are using SSL.
d. Select Properties.
e. If you are using the IBM Client Access PC5250 emulator, do the following:
i. Select Use default User ID, prompt as needed from the menu.
ii. Type Q#HMC into the User ID field.
Note: The user ID, Q#HMC, is not used for security authentication. You will be
prompted for additional security values by the HMC Telnet Proxy.
208
2.
3.
4.
5.
iii. Select Not secured as the security setting since this would be the default.
If you use SSL on the HMC then you would select that and the level of SSL.
Certificates would have to have been set up before this method will work.
Open the 5250 emulator and select the language you want to use for the interface.
Log in using your HMC user ID and password.
Select the managed system that contains the logical partition to which you want to
connect.
Select the logical partition to which you want to connect.
If you select Shared, you must enter a session key that can be used by another user
with another 5250 emulator.
If you are the first user, the session key is entered twice to verify accuracy.
If you select Dedicated, other users are not able to share the session with you.
If you select Details, you can view which users are connected to this partition.
If you want to configure the HMC firewall, see Changing HMC firewall settings.
http://publib.boulder.ibm.com/infocenter/systems/topic/iphai/lanfirewall.htm
209
Filler page
210
Chapter 10: How do I ...

This chapter answers your questions regarding how to perform functions, learn about Operations
console, make changes, or service the console. Topic titles show without the "How do I" words.
determine what model or serial number a system is?

If your system uses a Hardware Management Console (HMC) you can display the properties
of the managed system to determine the model and serial number.
If your system is not managed by an HMC then you can perform a function 20 at the
physical control panel to find out the model. For example, if you receive 6520nnnn it would
mean:
6 = 9406
520 = model of the system
nnnn = Processor group ID
If you have a Power5 processor-based or Power6 processor-based system you can also get
the model and serial number from Advanced System Management.
The serial number of most systems is usually located on a label attached to the physical
control panel or somewhere on the front of the system in the first frame. The 9407-M15 520
and 9408-M25 520 serial number is no longer on the front cover. It is now on a sticker near
the HMC1 and HMC2 ports.
display the system reference code (SRC) detail?

Displaying SRC detail data depends on the system, availability to the physical control panel,
whether the system has multiple partitions, and other factors. You are probably familiar with
the codes displayed as the system IPLs which is really word 11 of nine words reserved to
display information associated with the status of the system. This data consists of 4-byte (8
characters) per word to be displayed using the physical control panel. This data contains
words 11 through 19. Depending on how you access this data you might see that this data is
referred to as word 1 through 9. When displaying the data using the physical control panel
you perform a function, for example, using the up or down button to select a 12 and then
pressing the Enter button. Don't confuse these functions with the words of data that get
displayed.
211
Old control panels only had a 8-digit display so function 13, for example, only gave you
word 13. Newer control panels display four words at a time. That's two rows of 16
characters. These would be represented by:
Function
11
12
13
Word data
Word 11
Word 12 Word 13
Word 14 Word 15
Word 16 Word 17
Word 18 Word 19
In addition to the physical control panel you can also obtain this data using the following
methods:
The LPAR virtual control panel

If you have a Pre-Power-processor-based system with logical partitions and have a
workstation on the primary partition capable of using System Service Tools (SST) or
Dedicated Service Tools (DST) you can display the SRC data by following these steps:
1. Enter SST/DST
2. Work with logical partitions
3. Work with partition status
4. Press F10. This will display the current word 11 data.
5. Press F9 to expand this out to the details.
Operations console remote control panel or virtual control panel

Using the graphical user interface (GUI) of the remote control panel you would select the
function/word to display then click Enter. This is a single word display so performing a
function 14, for example, would only display word 14.
The Hardware Management Console (HMC)

HMC V6
Perform these steps to collect reference codes (functions 11-19).
1. In the navigation area, expand Server and partition > Server Management.
2. To view the reference code that corresponds to function 11 on the control
panel: In the contents area, select the system or logical partition and view the
associated value in the Operator panel value column.
3. To view reference codes that correspond to function 12-19 on the control
panel: In the contents area, expand the system.
4. Select the system or logical partition.
5. Right-click the system or logical partition and select Properties.
6. Select the Reference Code tab.
7. Select the entry that corresponds to the time stamp you want to view.
8. Click the Details button.
9. Record the values that correspond to functions 12 through 19 on the control
panel.
10. When finished, click OK twice.
212
HMC V7
Selecting a server: To work with a server, you can perform one of the following
actions:
Select a server under the Servers node from the navigation pane.
Click on a server name from the work pane table.
Click in the Select column next to the server name in the work pane table.
displays the system reference codes for the server. Click the
reference code in the table for a detailed description.
Reference Code
Integrated virtualization manager (IVM) interface

To display the reference code details of the current SRC code just click on the reference
code.
Advanced system management (ASM) interface

Once signed in to ASM, do the following:
1. Expand System Information.
2. Click Progress Indicator History.
3. Select the progress indicator (SRC) you want details of.
4. Scroll to the bottom of the page.
5. Click the Show details button.
change keyboard definitions?

Complete the following steps to change your keyboard definitions:
1. In the emulator window, use the drop-down menu to do the following steps:
a. Click Edit.
b. Click preferences.
c. Click keyboard.
2. Click User-Defined.
3. Click Browse... and then navigate to where Client Access is installed. Under the Client
Access folder, navigate to the Emulator folder, followed by the Private folder.
4. Select your choice.
5. Click OK, and then click OK again.
Note: If you are using IBM Personal Communications, the default path is: Documents and
Settings > User Name > Application Data > IBM > Personal Communications.
213
change the mode of the emulator for a 3179 or 3477?

You might need to change the mode of the emulator from its current setting to something wider
or narrower depending on what you are viewing.
By default, the emulator is set to 24 X 80 (3179), so viewing a spool file or vlog requires you to
use the keyboard to shift right and left in the window. In this case, it might be more convenient
to use the 27 X 132 (3477) mode.
Important: During the transition from one mode to the other, the console is disconnected and
reconnected.
To change the mode of the emulator, complete the following steps:
1. In the emulator window, click Communications.
2. Select Configure, and then click Session Parameters.
3. Select the desired emulator size and click OK.
4. Click OK.
If you are not using IBM Personal Communications, you receive a message indicating
the connection is terminated.
5. Click OK. The emulator session closes.
If the option Allow console recovery and console can be taken over by another console is not enabled,
the console returns to the signon window and is in the correct mode. You can exit these
instructions.
If the option Allow console recovery and console can be taken over by another console is enabled, the
console returns to the signon window, but the Console Information Status window and the option
to perform a takeover are most likely set to NO. This is due to a change in the emulator's
attributes and the new console type does not match that of the current console when it connected.
At this point, you must do one of the following:
Use SST from another workstation to perform the macro OPSCONSOLE RESTART.
For more information, see use the OPSCONSOLE macro on page 215 for more
information.
Use the console service functions (65+21) to do a 65, 21, 21, which performs the restart. For
more information, see use the console service functions (65+21) on page 232 for more
information.
Note: The console closes again, but should reconnect in two or three minutes.
214
use the OPSCONSOLE macro?

Native macros are advanced debug and analysis tools resident on the server. These tools are
intended to be used only with the direction of support personnel because inappropriate use of
these tools can cause unpredictable problems with your system.
If you are not comfortable in the service tools area, call your service provider for assistance
before using these tools.
Important: Incorrect use of macros can result in a change requiring a complete system reload.
Use macros only at the request of a support representative.
To use the OPSCONSOLE macro support, follow these steps:
2. Select Start a service tool.
3. Select Display/Alter/Dump.
4. Select Display/Alter storage.
5. Select Licensed Internal Code (LIC) data.
6. Select Advanced analysis. (Page down to display this option.)
7. Page down until you find the OPSCONSOLE option.
8. Type a 1 next to the option and press Enter. The Specify Advanced Analysis Options
window is displayed and the command displays as OPSCONSOLE.
9. Enter the appropriate option and any required parameters in the Options field. Use the
following options based on the function you are running:
Change the console type = cnsltype x (where x is 1, 2, 3, or 4)
Clear the resource and configuration for the Operations Console LAN adapter =
cnfglan -clear
Dump Operations Console-related flight recorders to vlogs = dump -vlog

Deactivate the communications adapter for a local console that is directly attached =
deactdirect
Activate the communications adapter for a local console that is directly attached=
actdirect
Deactivate the LAN adapter for a local console on a network (LAN) = deactlan
Activate the LAN adapter for a local console on a network (LAN) = actlan
Restart the console device (any console) = restart
Note: Use the restart option when you need to deactivate the current console and
allow the server to determine and start or restart a console. You can use the restart
option to correct a problem with the original console or when switching from one
console type to another.
215
The following options are new in Licensed Internal Code V5R4M5 and later. These
functions can be added by installing:
V5R4M5
MF44882
MF44894
V6R1
MF44647
MF44644
Show takeover
Console Information Status window = showstatus

Do not show the takeover Console Information Status window = skipstatus
F18 console take over is set to not allowed = takeoff
F18 console take over is set to allowed = takeon
See work with console takeover and recovery? on page 226 for information regarding
takeover and recovery options.
The following options are only used when a Power-processor-based system is not managed
by an HMC:
Enable the embedded Ethernet port = enbintlan
You might want to run this command if you have a system model manufactured
before V5R4 and you want to use the embedded port for the console.
Disable the embedded Ethernet port = disintlan
You might want to run this command if you have a system model manufactured at
V5R4 as the default LAN console resource and you want to use the resource for
another purpose.
Enable a 5706/5707 adapter = enbextlan
You might want to run this command if you have an IBM System i5 and eServer i5
model manufactured prior to V5R4 to take advantage of the faster network capability
from one of these adapters instead of your current network adapter.
Disable a 5706/5707 adapter = disextlan
model and want to prevent the use of this LAN adapter for use as a console.
Enable both the embedded port and the 5706/5707 adapter = enbboth
model manufactured prior to V5R4 to make your current server use these resources
as the default settings for new models being built.
Disable both the embedded port and the 5706/5707 adapter = disboth
model and do not want the adapters used for the console.
Display both the embedded port and the 5706/5707 adapter configuration flags =
dspcfg
model and a service and support representative asked you for this information. This
macro returns the state of the embedded port and Gigabit LAN adapter support.
216
PTF MF39303 (V5R3M5) and PTF MF39304 (V5R4M0) allow you to select an
individual asynchronous adapter for console and remote service = enbslot x (x is 2, 3,
or 4)
Notes:
1. This option applies to the IBM System i5 520, 525, and 515 models that are not
managed by an HMC and have an IOA that does not require an IOP. For the 520,
you can install PTF MF39303 (V5R3M5) or PTF MF39304 (V5R4M0). For the
525 and 515, these PTFs should already be installed.
2. If you are running LIC prior to V5R4M5 and you have moved the 2793/2794
asynchronous adapter from its manufacturing default location to use Operations
console (Direct), you must first activate the communications adapter for a local
console that is directly attached (actdirect).
3. If you no longer want to select an individual asynchronous adapter, you can clear
your current selection by using clrslot.
The following options are available with V5R4M5, or later, for Power-processorbased models:
Select a specific LAN adapter location = enblslot x (x is 2 or 5)
Clear the LAN adapter location = clrlslot
use the Operations Console properties window?

Verify and change information about the server and connection configurations using the
Properties window.
The Properties window contains information about the server associated with the connected
configuration. This is where you make changes to an existing configuration.
The General tab contains information about the server your selected connection represents. The
Log Directory field displays the path to the Operations Console data logs and is the only field you
are allowed to edit.
If the selected connection is not connected, the data provided originates from the last successful
connection.
If you select Properties for a connected configuration, you are presented with a dialog window
that indicates some changes might not take effect until the next time you reconnect the
configured connection. In V6R1 the service tools device ID name used for the connection is
shown and the Device ID tab is not shown.
If the partition number is displaying ****, then there is a configuration error associated with the
configured connection. The error might be a wrong partition ID or possibly a wrong service host
name IP address.
217
The Configuration tab contains options that change what functions are used and how the
configuration connects. Options not available for the associated configuration are disabled. The
remote console (V5R3 & V5R4) does not have a Configuration tab. To make changes to the
remote console, you must first delete and then re-create the remote console connection.
device ID, grant access to the remote control panel, then at a later time you connect and find that
you no longer have a remote control panel. This is the result of a change in the assigned service
tools device ID. Something occurred, possibly not connecting this device in a few days for
instance, so the service tools device ID got reset. A reset of the device ID includes revoking
permission to the RCP, so you, again, have to manually grant permission to the RCP. Currently,
the only way to prevent this would be for you to create a specific service tools device ID for this
configured connection and delete the previous one. See create service tools device IDs on the
system on page 239 for instructions on how to do this.
Also, it's the Configuration tab that has seen the most change over the releases. Here are the
options available by release:
Option
Start connection when Operations
Console starts
Allow remote access
Run unattended
Use console with this connection
TCP/IP address
Use remote control panel with this
connection
Answer bootp
Mask / Gateway
V5R3
yes
V5R4
yes
V6R1
yes
yes
yes
yes
no
yes
yes
yes
yes
no
yes
yes
yes
yes
yes
yes
no
no
yes
no
yes
yes
On the Configuration window, the system administrator can use the Answer bootp option to
determine which PC's configuration will supply the IP data to the server. New servers or logical
partitions attempting to connect to a local console on a network (LAN) might be using BOOTP.
If more than one PC or configuration is allowed to supply the data, the first PC to respond to the
broadcast packet supplies this data. Controlling which PC supplies this data might allow the
administrator additional flexibility.
218
An example is when it is desirable to refer to a system within Operations Console with a name
other than the name already assigned to the service tools host name (service interface). You have
a PC in the computer room that was used to initially set up your server or partition so it uses the
real service interface name. You want all the other PCs to display the name as something else.
You can create the configured connection on the other PCs to use a fictitious serial number for
the server so that BOOTP is always ignored from these PC's configurations. However, if you
clear this option, you prevent this PC from configuring the server with the wrong name and still
use the real server's serial number. For more information regarding BOOTP, see Bootstrap
Protocol on page 318.
For both local console directly attached configurations, the default IP used for the console is
192.168.0.2. If the PC uses the address range for another purpose, this field provides the user
with a convenient method to change the address used by Operations Console. For example, you
can use 192.168.1.2.
Note: An initial local console on a network (LAN) configuration configures both the console and
remote control panel. This is where you turn on or off any of the functions as needed. Also, the
remote control panel function is not available until the configured connection is successfully
connected for the first time and permissions have been verified. An initial local console that is
directly attached configuration does not configure the remote control panel. This is where you can
turn on or off one of the functions if you do not want to use it.
The Device ID tab allows a single button to reset the service tools device ID password on the PC.
The server's service tools device ID password must also be reset separately. The service tools
device ID's name for the configuration cannot be changed. To use a different service tools device
ID, you must delete this configuration and create a new configuration using a new device ID of a
different name.
Note: The Device ID tab is no longer available. This is part of the V6R1 Operations Console
simplification enhancement. The PC automatically handles any resets necessary. The systems
service tools device ID must be reset separately only if the option Autocreate service tools device
IDs has been set to zero. See Operations Console simplification on page 56 for more
information.
If you receive an error message that indicates you need to resynchronize the device ID
passwords, you have to only reset the server's device ID password. The client automatically
resets itself during the next connection attempt.
The Access Password tab allows you to change the access password. The access password is
used, in part, to authenticate the device making the connection.
219
Note: Starting with V6R1, the Access Password tab is not used, by default. If you manually
change this password, the system will no longer manage the access password and you might be
required to enter it each time you make a connection. This is part of the V6R1 client
simplification enhancement. See Operations Console simplification on page 56 for more
information.
While on the Properties window, you can use the ? help for more information. You can move
the ? to the field you want more information on, and then click again. A context sensitive help
dialog window is displayed containing information regarding that field.
use the Operations Console user interface?

Operations Console allows the user more flexibility when interacting with Operations Console
and the graphical user interface it provides. By using these features, you can customize the
Operations Console window so that you can view and interact with the information most
important to you.
The Options menu option provides the ability to modify the following functions:
Show Warnings
This option can be used to prevent many of the common dialog windows from
displaying. For example, the confirming a delete function dialog window is not displayed
if this is not selected.
Prerequisite Warning
The dialog that is presented during the configuration wizard concerning the requirements
can be turned off using this option.
Use Single Sign-on
This option provides the ability to share common signon data when connecting multiple
configurations at the same time. This allows the use of a single signon dialog window
instead of one for each connection.
Double-Click
This option has two items associated with it. The first is for expanding or collapsing the
tree structure, the + (plus sign) control. Instead of a single click to expand or collapse,
you can change the function to use a double-click. The second item requires the user to
use another method for starting a connection instead of double-clicking on the
configuration name.
220
Each configured connection has a + (plus sign) to the left of the icon. The + (plus sign) is a
standard Windows expand and collapse function. Each configured connection expands out into
separate functions associated with that particular connection. If you right-click on a remote
control panel while the configured connection is in expanded mode, a system reference code
SRC history option becomes available. The SRC history option allows you to retrieve all or part of
the recorded SRCs issued by the server. This function can be very useful when you are resolving
problems in a variety of situations.
You can drag and drop your configured connections to display them the way you want. This
allows you to group configurations together so a common function can be performed on multiple
connections at the same time. The standard Windows tagging methods for selecting more than
one connection applies. Connections most likely to share functions can be grouped at the top of
the list, for example.
Selected data columns can be placed in the order you want them. Using the drag and drop
method, you can arrange any column, except Connection, in the position most useful to you. You
can also select which columns to display. From the View menu, select the Choose Columns
menu. Then, select the columns you want to display and click on the column title to include it or
not include it.
Starting with V6R1, the user interface was enhanced. You will notice that much of the data
found in Properties is now available in the user interface. In the Configuration field you can easily
find the service tools device ID name, release of the connected system, the type and model,
whether the system is IPLed in A, B, or D mode, and the console type value. The Partition field
shows you the serial number of the connected system and the partition number. Of course, this
data can only be provided after an initial successful connection has been made.
221
The captures above are from a V6R1 client. The Settings and user interface for previous releases
will differ from these.
A little-used part of the user interface is the Settings window. It has been around since V5R3 and
it allows more control of some aspects of Operations Console. The options Keep Alive Interval and
Virtual Control Panel Interval should not be changed unless instructed to do so by your service
provider. Changes to these controls can adversely affect how Operations Console works and can
make it difficult to control the Operations Console connections. These changes are not directly
tied to a specific configuration and are global to Operations Console.
The two options to split the log files can be altered without fear of causing a problem. However,
should a problem arise and both options are unchecked may cause a delay in analyzing your
problem should the service logs for Operations Console be required by development. This is
especially true if you have a lot of active connections. The split logs option causes each
configured connection to create a separate log for the type of information associated with the log
file. The CON logs are connection specific and the AOC log is activity associated with the
graphical aspects of the connection like window control and the remote control panel, if
configured. By default, the CON logs are split and the AOC logs are not.
222
The option Auto-discover was discussed above in the simplified client section. This controls
whether or not Operations Console on this PC will attempt to discover new connections.
The button Re-authenticate RCPs has no function associated with it, at this time. It may be
utilized at a later time, re-utilized as another option, or removed at a later date.
switch 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 necessary for use with a different console.
Note: The following information assumes that hardware to support a new console type is
available in the correct location or can be tagged without the need to add or move hardware.
Systems with an HMC require at least one tag change prior to using a new console type. The tag
change, unless performed using a method that does not require an initial program load (IPL),
requires a shutdown and activation to reflect a change in the partition profile. This same
restriction also applies when you are ready to return to the original console type.
If the hardware resources for the targeted console type have already been specified and
configured for use as a console, making the change might be as simple as specifying the new
console type value and activating the associated hardware resource. However, if hardware used
for the targeted console type requires allocation or configuration, you need to use the appropriate
information in Changing Consoles - Pre-Power5 processor-based on page 103 or Changing
consoles - Power-processor-based on page 109.
An example is the planned loss of the network used by your LAN-connected console. You are
doing some infrastructure changes requiring more than a day and you also have the console
cable already installed between the server's asynchronous communications adapter and the PC.
The server is not managed by an HMC. Using the LAN-connected console you can change the
console type to Operations Console(Direct). You can then use the OPSCONSOLE RESTART
macro to force the system to the other configuration. After the asynchronous communications
adapter is active, you can disconnect the LAN-connected console and create a configuration for
the local console that is directly attached, if a configuration does not already exist, and start a
connection.
For systems managed by an HMC, you can dynamically tag a different resource and then force
the system to start using the new console. For more information about changing from one
console type to another, see Changing Consoles - Power-processor-based on page 109.
To return to the previous console type, you need to use the current console and the same basic
method as previously described to make your change.
223
Note: To force the system to use the new console type, you can choose to have the change take
effect immediately or wait until the next time you IPL the server. For an immediate change, you
can use the console service functions of 65+21+21 or the macro OPSCONSOLE RESTART.
For more information on the console service functions (65+21), see use the console service
functions (65+21) on page 232. For more information on the OPSCONSOLE macro, see use the
OPSCONSOLE macro on page 215.
switch the console type to recover access to the

system?
If you develop a problem with the current console, depending on the type of problem, you might
be able to recover access to the system by changing the console type.
Note: The following information assumes that hardware to support a new console type is
available in the correct location or can be tagged without the need to add or move hardware.
Systems with an HMC require at least one tag change prior to using a new console type. The tag
change, unless performed using a method that does not require an initial program load (IPL),
requires a shutdown and activation to reflect a change in the partition profile. This same
restriction also applies when you are ready to return to the original console type.
The following recovering option is new in Licensed Internal Code V5R4M5 and later. This
function can be added by installing:
V5R4M5
MF44882
MF44894
V6R1
MF44647
MF44644
Use the OPSCONSOLE macro to enable a special recovery option. By performing a

OPSCONSOLE TAKEON macro you can enable the ability to allow another console type, as
long as it's a 5250-based connection, thus leaving out twinaxial console, to become the console
on a temporary basis.
An example would be when you use Operations Console (LAN) as the console type and you
have encountered a problem with the network adapter or the network. You planned ahead and
have an Operations Console directly-attached PC available. If you connect this device you will
be taken to the Console Information Status window. When this function is enabled you could
perform a F18 and this device will instantly become the console and take you to the i5/OS
signon screen. You can now perform and debug or gather data to work with the original data.
224
The following information applies to this recovery function:
This recovery action from any 5250-based connection other than twinaxial
The current console type and connectivity is ignored. As long as they have the takeover
signon screen they can perform the F18. The console type does NOT get set to a new
value.
The system has to have supporting hardware to allow another device to get the signon
screen, of course. The currently set tagged resource(s) for console is/are NOT changed.
This device session is temporary. If the user IPLs or performs a console service function
to reset or make console type changes the system will use whatever values are in effect at
that time. For example, if the user had a problem with their LAN console and connected
a directly-attached device and used F18, the current console tag is set to the resource for
LAN but manually activating the supporting resource for the directly-attached device
would allow that device to be taken directly to the Console Information Status screen wrong console type error message - and the F18 would take them to the i5/OS signon. No
changes to those tags (Console and Operations Console) take place. If they did a restart
while in i5/OS the system will again try to bring up LAN console, not the directlyattached device.
This function allows the user the capability to debug a failing console or overcome a
disabled user ID.
V5R4 & V6R1 will not show this function is available at either screen due to MRI. This
will be added in V6R1M1.
See work with console takeover and recovery, on page 226, for more information on these new
take over functions.
Before you start, observe the following:
Several console service functions (65+21) might be needed to recover or resolve an
Operations Console problem. These functions might work depending on the problem,
connectivity used for the current console, the target console type, and the current state of
the system.
If you are unsure of any function or recovery action, contact your authorized service
provider for assistance.
225
Use one of the following methods to change the console type:

If you are using a PC connected to a LAN for the console and have another PC set up to
be the console, you might be able to use the other PC for the console until the problem
with the first console is fixed.
Use SST from another workstation.
Use the console service functions (65+21) on page 232 to change or reset the console.
Use the appropriate macro from another workstation. Any hardware allocations or
configurations must be accomplished before connecting with another connectivity. For
example, you can use the alternative method for tagging a different console to save an
IPL instead of deactivating and activating the partition to enable the change with just the
partition profile. Some tasks might require one or more IPLs to get the system into a state
where you can use the new console.
For more information about changing to a different console type, see Changing Consoles - PrePower5 processor-based on page 309, or Changing Consoles - Power-processor-based on page
109.
work with console takeover and recovery?

A special set of functions included in allow an Operations Console to take control from another
console device. The two main actions that you can do are:
Takeover is the process used for a LAN-connected console-capable device to take control
from the current LAN-connected console device. This take over action can not be used
with directly attached consoles.
Recovery is the process of regaining control of the job running on the console after a
problem with the console was encountered. The recovery process may be to the same
console device or a different console device and may be facilitated by additional work to
enable a device using a different connectivity. The exception is twinaxial console which
does not use the same type of 5250 emulation and thus cannot recover the console.
Every console-capable device running 5250 emulation, regardless of connectivity, will be
presented a window of data regardless of whether it is the console when it successfully connects.
This means that more than one device will have data on the window after the console has been
established. A console device will not have a blank window showing 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.
226
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.
The default setting for the console take over and recovery function is disabled. If this function is
disabled, all console-capable devices will open the Console Information Status window whenever
they are not the active console.
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
operating system. When the console option for takeover is enabled, the system also has enhanced
recoverability from the loss of the console.
A new function has been added that allows the user the ability to choose whether or not to force
a user to perform all the steps for a takeover. This new function will allow the user to bypass the
Console Information Status window, doing the F10 and confirm with the Enter key. When the
bypass function has been enabled using a macro, the user signs on normally and if the user has
takeover authority and the device meets all takeover requirements the window will return to the
current console's window without any further interaction. This function will be included with
MF44882 & MF44894 (V5R4M5) and MF44644 & MF44647 (V6R1) and later versions of
Licensed Internal Code. Use the following macro to select how you want the takeover to be
performed:
SECAUDITLOG SKIPSTATUS
SECAUDITLOG SHOWSTATUS
(default is showstatus)
Forced takeover
This function will be included with MF44882 & MF44894 (V5R4M5) and MF44644 &
MF44647 (V6R1) and later versions of Licensed Internal Code. Use the following macro to
select whether you want this function on (default) or off:
SECAUDITLOG TAKEOFF
SECAUDITLOG TAKEON
F18 Console take over is set to not allowed.

F18 Console take over is set to allowed (default)
This new function is a recovery method in which the user is unable to perform a normal
takeover. For example, a user has forgotten the DST user ID's password assigned to them and
they need to perform a takeover to recover from a previous problem. They can start using the
system since they know the password for their i5/OS user ID but can't get to it without the
takeover.
227
On the special DST sign-on window or the Console Information Status window, a user can press
F18 and they will be taken directly to the i5/OS sign-on screen. However, they may lose data in
the process. Since this method bypasses the normal takeover process any saved data intended
for the console is lost and the user may get a new job after signing on to i5/OS. It is up to i5/OS
to determine if the user can restore the previous session.
To expand on this new function, let's say that the current console, Operations Console local
console on a network (LAN) crashed with a hardware failure. You have a backup Operations
Console directly attached available so you activate the line on the asynchronous communications
adapter and connect. Unfortunately, this device came up with the Console Information Status
window and it says you can't perform a takeover (actually a recovery) because this device
doesn't meet the current console's requirements. You could perform the console service
functions (65+21) procedure to change the console type but you have no way to invoke the
function since the system is behind a locked door and there are no other workstations available.
Now what? Well, actually, you can perform a F18 and this device will become the console with
nothing more to do. Of course, the same restriction applies about about the possible lose of data
exists.
This forced takeover is only temporary. If you IPL, do a console service functions (65+21) that
sets up a different console or resets the console, the system will return to the originally set
console type. This function is available anytime you have a device with an active connection,
data on the screen even though it isn't capable of becoming a console without additional work.
Since twinaxial consoles use a different type of 5250 emulation this function won't work when
you would like to go to twinaxial console. You could, however, go from twinaxial console to
another console. This function now becomes the exception to the rule of honoring the console
type. Keep in mind, however, that this is temporary and the console will return to the console
defined unless you make a change. This function does not rely on the Allow console recovery and
console can be taken over by another console option.
Takeover details
Here is the additional information about the console takeover function.
Recovery details on page 230.
Here is the additional information about the console recovery function.
Enabling console takeover on page 231.
Before you can enable console takeover, you must have the Take over console privilege.
228
Takeover details
Here is the additional information about the console takeover function.
This function must be enabled if you want to take over the console or be protected from
the loss of the console using the recovery function.
The option Allow console recovery and console can be taken over by another console is
enabled on the Select Console window in DST or SST.
This function does not include support for twinaxial consoles. Only Operations Console
workstations and the HMC, which use 5250 emulation, can use this function.
Since there can be only one Operations Console directly attached device, the takeover
function cannot be used. However, any 5250 emulation-based console device can be used
to recover a loss of the console by changing the console type. This may require a
reallocation of hardware to support the new console type.
The DST user ID used to sign on at an eligible device must also have the user privilege
of take over console, a new feature for V5R4.
Only devices with the same attributes (for example: 24x80 or 27x132) can perform a take
over. For example, if device LAN1 is running in 24x80 mode and LAN2 is running in
27x132 mode, and LAN1 is the console, LAN2 will display NO in the Take over the
console field.
Data on the Console Information Status window does not change. Currently, there is no
method to automatically refresh the data. You can manually cause a refresh of all fields
except the Take over the console field by pressing Enter. The user would have to exit this
window and sign on again to display a change to that field.
Beginning in V5R4, takeover is supported in a D-mode IPL. Two devices can be
connected, with data, at the same time during a D-mode IPL.
Console type respectability is still honored when take over is enabled. However, each
console-capable workstation will present either a DST signon or the Console Information
Status window. If the console type is set to LAN, for example, a local console directly
attached, if connected, will present the Console Information Status window without
displaying the DST signon window but the Take over the console field will show NO to
indicate it cannot take over the existing console. However, it could be used for a recovery
action.
229
Recovery details
Here is the additional information about the console recovery function.
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.
Console recovery utilizes the take over function. Recovery can be from the same device
or another device of the same connectivity. For example, if you are using Operations
Console (LAN) and have multiple PCs set up to be the console and the existing console
fails you can use the take over function from the same PC, after correcting the reason for
the failure, or from another PC. Regardless of what the former console was doing, the
new console will be in the same job, at the same step, as the original console would have
been. The job continues even though the console was not operational. Using a directly
attached console to recover a loss of a LAN-connected console doesn't fit this scenario
The recoverability of the console using a different console connectivity provides
additional options for the user.
If you have a backup console plan that involves the need for a change in the console
type, consider the following:
For ease of adapting recovery, you can place all console supporting adapters for
use by the same IOP. This reduces the number of steps necessary to accomplish a
recovery.
The console type change can be immediate depending on the method used to
make the change. Examples would be:
Using DST or SST to change the console type would allow the console to
change only at the next IPL. Following this action with a force DST
(function 21) using the control panel or LPAR menu may not always work
either.
Changing tags in the LPAR environment will also require an IPL to cause
a change of the console.
However, using the console service functions (65+21), forces the system
to do this search and activates the appropriate hardware and tasks
immediately.
Supporting hardware for each console type you want to use for recovery must be
available at the time of recovery. For example, if you want a local console directly
attached to be able to recover a local console on a network, both adapter cards
must be located in their respective locations or be properly tagged for logical
partitions. For this to be completed, you also need to change the console type,
either using an available menu or using the console service functions (65+21).
230
In order to accomplish a recovery using a different console type, you must set the
new console type before attempting the takeover. 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. Then, you will have to use one of the methods to change
the console type to the desired setting. You can use an existing workstation and
SST, if available, the OPSCONSOLE macro, or the console service functions
(65+21).
In V5R4, a D-mode IPL with the take over function, one console device taking
over for another, is supported.
If you change the console type value during a D-mode IPL, for example using
65+21, you should be able to connect another device as long as the new console
type has supporting hardware and a device.
Enable console takeover

Before you can enable console takeover, you must have the Take over console privilege.
Use the following procedure to grant the 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:
2. Select Service tools user IDs.
3. Type a 7 on the line in front of the desired user ID and press Enter.
4. Scroll down until you find the option Take over console and place a 2 on that line to grant
the user this privilege and press the Enter key.
To repeat this procedure for additional user IDs, repeat steps 4 and 5.
This privilege will be used the next time the user ID signs on.
Note: When a user signs on at a device capable of taking over the console the status of
the Take over the console field is updated. In order to reflect a change, such as a user
being granted the Take over console privilege, the user would have to exit the Console
Information Status window, using F3 or F12 and sign on again.
231
To enable the console takeover and recovery, perform the following:

devices.
b. Select System devices (skip this step if using SST).
c. Select Select Console.
d. Type a 1 in the option column for Allow console recovery and console can be taken
over by another console and press the Enter key.
The console takeover option will take effect immediately (except for pre-V5R4M0).
Scenarios: Takeover and recovery

These scenarios can help you understand the takeover and recovery options. See the on-line
Information Center for more details.
use the Console Service Functions (65+21)?

Use the console service functions (65+21) only when you encounter an unexpected console failure
and there are no other workstations available for recovery or resolution. Inappropriate use can
result in the inability to use the intended console.
Note: The use of the console service functions (65+21) will require you to use the physical control
panel, the remote control panel, the HMC, or the LPAR virtual control panel menu in Work with
system partitions.
If you are uncomfortable using these functions it is highly recommended that you contact your
next level of support.
Any hardware allocations or configurations must be accomplished before using the console
service functions (65+21). For example, if you installed an input/output adapter (IOA) for use with
the console device, you must tag this IOA to change the type of console or connectivity.
Important: To use the console service functions (65+21), the server must be far enough through
the initial program load (IPL) for the code to run correctly.
If a console device is available, you can use that device for changes or recovery.
If a console device is not available, you can perform the console service functions (65+21) only
after a failing system reference code (SRC) is displayed. The code is typically A6005008 for a
manual IPL.
232
The console service functions (65+21) apply to systems with or without a Hardware Management
Console (HMC), as well as a control panel.
If your system is managed by an HMC, you can enter these functions using the HMC,
Operations Console remote control panel, or the virtual control panel.
If your system is not managed by an HMC, you can enter these functions at the physical control
panel, Operations Console remote control panel, or the virtual control panel.
The following functions are available using the console service functions (65+21):
Changing the console value in (01 - 04)
You can use the console service functions (65+21) to change the console value 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.
If you have received the console cable for a directly attached console, you might want to
change the value from a 03 (LAN) to a 02 (Direct).
Clearing the resource and configuration for the Operations Console (LAN) adapter (C3)
With this option, you can disassociate the current LAN adapter used for Operations
Console. You might use this option to overcome a mistake in the configuration. For
example, assume that you made a typing error and entered another device's IP address.
At connection time, the client configured the system's LAN adapter for use by the
console, but the console fails to connect because the other device is active. This option
clears the system's network data for the console and allows you to delete the client's
configuration so that you can start over and make the BOOTP work again.
Depending on your intent to clear the LAN adapter configuration, you might also want to
stop and restart the LAN adapter. The example here benefits from following the clear
function with a deactivate and activate (A3) function to save time from having to do an
IPL.
Deactivating and activating the Operations Console LAN adapter (A3)

With this option, you can reset the LAN adapter used by Operations Console when some
network problem causes the system to get into a bad state and the console cannot become
active. This forces the LAN adapter to deactivate, and then start back up again. This
might clear up the problem, providing the original problem that caused the connection
failure has been solved.
This option might be used in place of an IPL for some circumstances, such as after the
LAN adapter configuration has been cleared.
233
Dumping Operations Console-related flight recorders to vlogs (DD)

Note: This option will not work during an IPL in D-mode.
You can capture valuable resolution information regarding an Operations Console
connection failure for support personnel. This option is less invasive than performing a
main storage dump, which forces the server to restart. The console service functions
(65+21) gather the flight recorder logs for Operations Console and then the server creates
a set of vlogs for major code 4A00 and minor code 0500. You can send these vlogs to
your authorized service provider for analysis. When possible, continue the IPL of the
server to the operating system to guarantee that all vlogs are created even if the IPL fails.
The intent is that the Licensed Internal Code (LIC) function has started the vlog tasks
before performing the dump of flight recorders.
The following functions are only available on Power-processor-based systems
Enabling or disabling the embedded Ethernet port and 5706/5707 or 5767/5768 adapters
(E1, E2, D1, D2)
Note: These options are only used when the system is not managed by an HMC.
You can enable or disable support for the embedded Ethernet port and for the 5706/5707
or 5767/5768 adapters. Systems shipped with LIC V5R3M5 or later have both options
enabled by default. Systems upgraded to LIC V5R3M5 or later might need to manually
enable or disable the appropriate functions. The current option is displayed in word 13 of
SRC A6nn5008, D100 8065, and D100 8066. The values displayed depends on the
model and code level, for example, 06C30005, E6C30005 or E1E20005. All three
examples carry the same meaning but from different releases from V6R1, V5R4, and
V5R3 respectably.
If you want to use an adapter installed in a specific slot location, as long as it's a
supported slot for use by the console of course, you must first disable the embedded port
support using D1. By default, there is support for both the embedded port and external
adapters so you shouldn't need to use E2. However, there might be circumstances,
especially in a system recovery scenario, in which you might have to turn on E1 or E2
depending on which port type you plan to use. See disable support for the default
embedded Ethernet port, 5706/5707, or 5767/5768 adapters on page 255 for details.
Note: The Dn function has no bearing on non-1 Ghz adapters such as the 2849. Even if
you turn off both the embedded port support and support for external adapters the system
may still be able to use the older adapter if it is placed in a console supporting location.
234
Selecting an individual LAN adapter location (Bn)

If you have an IBM Power5 processor-based or Power6 processor-based model, your
system can have LAN adapters for use with a console located in multiple slots
simultaneously. A 5706/5707 or 5767/5768 adapter can be used without an IOP if your
hardware supports this function.
If you use another network adapter, such as the 2849, then you must install an IOP.
Note: This option will only appear if support for the embedded port has been disabled
and support for the external adapter is enabled and the system is not HMC-managed.
The search order for console supporting slot locations also determine the order of the Fn
function being displayed. See Chapter 1: Reference on page 19 for the search order of
your particular model.
Selecting an individual asynchronous adapter location (Fn)

If you have an IBM Power5 processor-based or Power6 processor-based model, your
system can have asynchronous adapters located in multiple slots simultaneously,
including locating the 2793 asynchronous adapter in slot C4. Slot C4 allows an IOA that
does not require an IOP. This is possible only for systems that are not managed by an
HMC and have an input/output adapter (IOA) that does not require an input/output
processor (IOP). To allow for this greater flexibility on the 520, you must install PTF
MF39303 (V5R3M5) or PTF MF39304 (V5R4M0). These PTFs should already be
installed on the 525 and 515 for later releases and other Power-processor-based models..
With this new function, you will be able to select an individual asynchronous adapter for
use with the console and remote service by using either the OPSCONSOLE macro or the
console service functions (65+21). The console and remote service functions must all
remain on a single asynchronous adapter.
If you have a system that was shipped with Licensed Internal Code (LIC) prior to
V5R4M5, you cannot select slot C4 for use with the console when using the 2793, but
you can select slot C4 for use with remote service.
Also, if you are running LIC prior to V5R4M5 and you have moved the 2793/2794
asynchronous adapter from its manufacturing default location to use Operations Console
(Direct), you must use the 65+21 functions to increment nn of SRC A6nn 500x until the
nn value is appropriate for the location in your model.
Note: This option will only appear if the system is not HMC-managed. The search order
for console supporting slot locations also determine the order of the Fn function being
displayed. See Chapter 1: Reference on page 19 for the search order of your particular
model.
235
How console service functions work

Note: If your system is not in manual mode, and the extended functions are not activated, or
both, follow these steps:
1. If your system uses a keystick, insert it in the key slot.
2. Place the system into manual mode by using the system's control panel.
3. Using Up and Down, select function 25. Press Enter.
4. Use Up to select function 26. Press Enter.
A function 65 is performed from one of the input methods. You have approximately 60 seconds
to enter a function 21 for the system to pair the two functions together.
If not, the function 21 is a force of DST to the console. Depending on the state of the current
IPL, you might not see a change at the console, assuming the console is still present after the 65.
If the 65 and 21 are entered in less than 60 seconds, a system reference code (SRC) of
A6nn500A is displayed on the control panel. The value of nn depends on the console value
currently being used, 01 thru 04. Repeating the 65 and 21 puts the system into an edit mode
where you can make a change or cause an action to be performed.
After the second 65+21 pair is entered, the control panel responds with an SRC of A6nn500B to
indicate you are in edit mode. Each repeated 65+21 within edit mode increments nn of the SRC
until you reach the value representing the action you intend to perform. At this time, you enter a
single 21, which causes the selected function to be performed. The SRC then becomes
A6nn500C to indicate the function was successfully submitted.
If at any time you exceed 60 seconds (45 seconds for code levels prior to V6R1) between the 65
and 21 or between succeeding 21s, SRC A6nn500D might be displayed, indicating a time-out
condition and the system is no longer in edit mode.
If you planned to make a change, you must restart the operations. This SRC will reset in
approximately three minutes. You can quit the edit mode by using function 66. The function 66
does not have to complete successfully.
Use the following codes to track your progress:
A6nn 500x
Where nn means: (Presented in the order they would appear)
00 = No console defined
01 = Twinaxial console
02 = Operations console(Direct)
03 = Operations console(LAN)
04 = Hardware Management Console (HMC) or Thin Console
C3 = Clear LAN configuration
A3 = Deactivate followed by an activate of the LAN Operations Console adapter
DD = Dump all console related flight recorder into a set of vlogs
236
The following functions are only available on Power-processor-based models

E1 = Enable Ethernet embedded port or IVE
E2 = Enable add-on 5706/5707 or 5767/5768 LAN adapter
D1 = Disable Ethernet embedded port or IVE
D2 = Disable add-on 5706/5707 or 5767/5768 LAN adapter
Bn = Enable LAN adapter in slot Cn (V5R4M5 and later) based on model
Fn = Enable asynchronous adapter in slot Cn based on model
Notes:
Selecting 02 will automatically activate the asynchronous communications adapter used

for Operations console(Direct).
Selecting 03 might also require a function A3 to activate the LAN adapter in rare cases.
Also, if a local console on a network (LAN) is connected, the emulator might go to a
Disconnected state. If so, you can start it again by clicking Communication and selecting
Connect. You may also have to change the state of either the embedded or external addon adapter support, or both in order to use a local console on a network (LAN).
The Bn and Fn functions display only numbers specific to the model you are working
with. Also, the functions display in the order the system would search for a supporting
adapter.
Console Service Functions (65+21) - Equivalent macros

Functions OPSCONSOLE
V5R3
V5R3M5 V5R4M0 V5R4M5 V6R1
macro
01 - 04
CNSLTYPE n
X
X
X
X
X
C3
CNFGLAN
X
X
X
X
X
-CLEAR
A3
RESTART
X
X
X
X
X
DD
DUMP
X
X
X
X
X
E1
ENBINTLAN
X
X
X
X
X
E2
ENBEXTLAN
X
X
X
X
X
D1
DISINTLAN
X
X
X
X
X
D2
DISEXTLAN
X
X
X
X
X
Bn
ENBLSLOT n
X
X
Fn
ENBSLOT n
X (1)
X (1)
X
X
Time-out
45 to 60
secs
(1) PTF MF39303 (V5R3M5) or PTF MF39304 (V5R4M0)
237
Where x means:
A6nn 500A = Your current console value is displayed.
A6nn 500B = You did a second 65+21 pair so you are in edit mode.
A6nn 500C = You executed a second 21 to cause an action, such as setting the console to
another value.
A6nn 500D = Too much time has passed after entering edit mode to cause an action. You
must enter edit mode again if you intend to make a change. A 21 at this time will force
the console to DST, not cause an action.
If you do not want to make a change after entering edit mode, you can wait 3 minutes and the
completion code indicates a change is no longer pending. You can also enter a function 66 to
cancel any pending changes and exit.
An example of a console change is when you have a twinaxial console (01) and you want to use
LAN (03).
65 - 21 = A601 500A You are in display mode and the console value is 01.
65 - 21 = A602 500B You entered edit mode and incremented the counter.
65 - 21 = A603 500B You incremented the counter again.
21 = A603 500C You invoked the action (set the console value to 03).
If the LAN adapter already had a valid configuration, for example, you previously configured
the LAN adapter for use with the service tools server, then you are ready to create a local console
on a network (LAN) configuration on the client, if one does not already exist. You can then turn off
the twinaxial device and connect the Operations Console (LAN) configuration.
Note: To reset the console without changing the console value, you can enter a 65 - 21 - 21. The
system will respond with A6nn500A after the first 21 and A6nn500C after the second 21. This
causes the connection to the console to be dropped during the reset process. Do not use this
function when you already have a working console. This function does not correct all errors
associated with a console failure, but rather resets the hardware associated with the configured
console connection.
238
Local console on a network (LAN)-specific topics

change the access password?
When using V6R1, the system automatically creates and maintains an access password.
If you manually change the access password in Properties, you take control of this password and
might have to provide it each time you make a connection.You can change the password used to
access the service tools device ID information at any time after the creation of a new local
console on a network (LAN) configuration. If you are working with partitions, you can change this
password for the corresponding partition.
Important: The password is case sensitive and can be a maximum of 128 characters of mixed
case. You use this password during the connection process to sign on through the LAN Service
Device Sign-on window. This password is only used at the PC and is unknown to the server.
To use the connection properties to change the access password, follow these steps:
1. Select the connection name that you will be changing the access password for.
2. Click Connection > Properties.
If the configured connection is not in a disconnected state, you receive a message
explaining that changes might not be reflected until the next connection. Click OK to
continue.
3. Select the Access Password tab.
4. For Current Password field, 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.
work with the service tools device ID?

create service tools device IDs on the system?
By default in V6R1, the system maintains service tools device IDs automatically. You
only need to do this procedure if the system option Autocreate service tools device IDs is set
to 0 or the system is using Licensed Internal Code earlier than V6R1. See change the
value of autocreate service tools device IDs (V6R1 only) to verify the value or make a
change.
You will need to set up service tools device IDs on the system for a local console on a
network configuration.
239
Note: To perform the following procedure using System Service Tools (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 Service tools device IDs. You must unlock the SST
option before the menu option is usable. For additional information on SST, see unlock
service tools device IDs in SST on page 248.
1.
2.
3.
4.
Access Dedicated Service Tools (DST) or System Service Tools (SST).

Select Work with DST environment.
Select Service tools device IDs.
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. You can enter a description. Press Enter. You have finished creating a service
tools device ID.
Note: The device ID and the service tools user ID must have the proper
authorities granted before the remote control panel and all it's functions are
available for the associated partition. To verify or change the service tools device
ID attributes you can press F5 (change attributes on the Create Service Tools Device
ID window or enter a 7 in front of the device ID on the Work with Service Tools
Device IDs window.
6. To create additional service tools device IDs, repeat the steps starting at step 4.
7. Press F3 when you finish creating your service tools device IDs.
Notes:
1. If you reset a service tools device ID, the password becomes the name of your
service tools device ID in uppercase.
2. If you have more than one PC connected to your console, you need to create
several service tools device IDs.
3. Sometimes the service tools device ID password must be changed, such as when
the password has to be resynchronized between the PC and the system. 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 doing
recovery steps on both the system and possibly the PC.
4. QCONSOLE cannot be left in a reset state on the system. This is considered a
security exposure.
240
consider changing the service tools device ID passwords?

You need to review these considerations before you reset the service tools device ID
password.
When using V6R1 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. Consider the following information if you elect to
manually manage the device IDs.
Note: You must unlock the SST option before the option is usable. For additional
information on SST, see unlock service tools device IDs in SST on page 248.
The service tools device ID password on the PC must be the same as the service
tools device ID password on the system.
If you change one, you have to change the other.
By default, the PC automatically creates and manages the access password and
you cannot set this password during the creation of a configuration. However, if
you need to manually manage the access password, you can change the password
on the Properties page and you might have to supply this password when making a
connection.
Operations Console changes and re-encrypts the service tools device ID password
during each successful connection.
If you delete the local console on a network configuration after making at least
one successful connection, you need to reset the service tools device ID password
on the system before you reuse the profile for a new local console on a network
configuration.
If the configuration uses QCONSOLE as the device ID, do not reset the device
ID until you are again ready to use it. By default you do not need to manage this
unless you elected to set the system option Autocreate service tools device IDs to 0.
change the service tools device ID password on the PC and

system?
When using V6R1 the system manages the service tools device IDs and its password. As
a result, you do not need to resynchronize the device ID passwords manually.
When using code prior to V6R1, there is no advantage of changing the service tools
device ID password unless the passwords on the PC and system are out of
synchronization.
You can resynchronize the PC and service tools device ID password to make them both
the same again. Since this password is actually changed at each successful connection,
manually changing the password, except for synchronization, is not recommended.
241
resynchronize the PC and service tools device ID password?

When using V6R1 the system creates and maintains the service tools device ID and its
password. You should not have to manually resynchronize the password. However, if the
system option Autocreate service tools device IDs is set to 0, then you must manually
manage the IDs and their passwords.
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.
Note: You need to access Dedicated Service Tools (DST) or System Service Tools (SST) to
reset using the service tool device. If there is already a console device present, you can
use that device. Otherwise, you might need to:
Use a different local console on a network (LAN), if available.
Reconfigure the same local console on a network (LAN) using an unused emergency
service tools device ID.
Use an Operations Console local console that is directly attached to the system (if an
Operations Console cable is available).
Use a twinaxial-attached console.
Use the control panel or remote control panel to reset QCONSOLE.
Reset the service tools device ID password on the system below.
Notes:
This procedure is only necessary if the system option Autocreate service tools
device IDs is set to 0 and the system is no longer maintaining service tools
device IDs.
You no longer need to manually reset a connection's service tools device ID
password on the client PC.
reset the service tools device ID password on the system?

This procedure is only necessary if the system option Autocreate service tools device
IDs is set to 0 and the system is no longer maintaining service tools device IDs.
To reset the service tools device ID password on the system, you need to perform
these steps.
Note: You must unlock the SST option before the menu option is usable. For
additional information on SST, see unlock service tools device IDs in SST on
page 248.
242
reset using a console session with another device?

If you can obtain a console session or access SST using another device, reset the
service tools device ID password.
By doing this, the service tools device ID password becomes the service tools
device ID name, in uppercase. To reset the service tools device ID, follow these
steps:
2. Select Service tools device IDs.
3. Type 2 in front of the service tools device ID to be reset, and then press
Enter.
4. Press Enter again to confirm the reset.
Note: When you reset the password in DST, the service tools device ID
password becomes the service tools device ID name in uppercase. If you
delete and create a device ID, you also need to delete and create the
connection on the PC.
reset using unused service tools device ID?

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. Delete the current configuration as follows:
b. From the Connection menu, click Delete.
c. Click Yes to confirm the deletion if prompted.
2. Use the unused service tool device ID to create a new configuration.
3. Use one of the previous methods to reset the failing service tools device
ID after connecting.
reset using the control panel or the remote control panel specifically
for the QCONSOLE service tools device ID password?
If you cannot use another service tools device (PC or other terminal) or service
tools device ID to sign on and you are using the QCONSOLE service tools device
ID, you need to use the control panel or the remote control panel to reset the
service tools device ID password by following these steps.
243
If you need to reset the DST user ID 11111111 you can use these instructions but
continue to nine (9) function 65s. The service tools device ID QCONSOLE still
gets reset at seven (7) function 65s but the PC and system/partition will
automatically handle the reset.
Note: To increase the success rate of resetting with the control panel, it is
recommended that you disconnect the configured connection before you begin
the reset procedure.
1. Place the system in Manual mode. Systems without a keystick shows 01 B
in the Function/Data display.
Note: Systems with a keystick should show the mode as Manual and 01 B
in the Function/Data display.
2. Use the following information to help determine your progress and
success of the reset:
Note: If your system uses the new double-row Function/Data display
control panel, you might need to perform a function 11 to display the
results (D1008065). Allow at least 15 seconds for the initial function 65 to
complete before doing a function 11 if the display does not respond with
the D1008065.
The double-row display control panel presents data like this (models 8xx):
xxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxx
Each word is 8 characters but 4 words are displayed at a time for
functions 12 through 19. For example, requesting function 12 will provide
you:
word__12word__13
word__14word__15
Requesting function 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:
xxxxxxxx
Each word is 8 characters only and displayed individually. If you want
word 17, you have to request function 17.
244
The data provided in the words can be accessed using many different
methods, depending on the model.
Important: In order to know where you are in the process the following
information is provided:
Word 17 of the SRC D1008065 will contain 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.
Word 18 will show 00000001 until you have entered the seventh
function 65. When the reset has completed, this word will be set to
00000000 unless more than five minutes have elapsed.
Note: If you enter function 65 more than seven times, the count
will start over except when the following PTFs are installed:
V5R4M5
V6R1
MF45244 MF45247
MF45246 MF45248
When these PTFs are installed
the function 65 count will start over
at the count of 9.
3. Use one of the following methods to reset the QCONSOLE service tools
device ID depending on the partition type:
For independent systems or primary partitions, follow these steps:
a. From the control panel, use the Up or Down buttons so that
Function/Data display shows 25. Then press the Enter button. The
Function/Data display should show 25 00.
b. Use the Up button once to increment the data to 26. Then, press
the Enter button. The system will most likely respond with 01 B in
the Function/Data display.
Note: If the system responds with 65 FF repeat steps a and b
again.
c. Using the Down button, decrement the data to 65, and then press
the Enter button. The system will respond with 65 00. After
processing the function the system will respond with a D1008065.
Repeat this step so that you have entered 7 function 65s. You will
have five minutes to complete this task. When the seventh 65 is
entered and if it is found that greater than five minutes have
elapsed, the reset will not be processed and the count will return to
zero. Check WORD 17 to verify that the system handled each
request. Entering the 65s quickly may cause the system to miss the
entries.
245
For secondary partitions on pre-Power5 processor-based systems,

follow these steps using the console on the primary partition:
a. Access Dedicated Service Tools (DST) or System Service Tools (SST).
Note: You must unlock the SST option before the menu option is
usable. For additional information on SST, see unlock service
tools device IDs in SST on page 248.
b. Select Work with system partitions.
Note: If the partition on which the reset will be performed is not in
manual mode, you need to force the partition into manual mode by
placing a 10 on the line for the partition selection area before
continuing.
d. Enter a 65 on the line for the partition to be reset, then press Enter.
e. Repeat this step so that you have entered 7 function 65s. You will
have five minutes to complete this task. When the seventh 65 is
entered and more than five minutes have elapsed, the reset will not
be processed and the count will return to zero.
Proceed to reset the service tools device ID password on the PC.
reset the service tools device ID password on the PC?

beginning with V5R4, you no longer need to manually reset a connections service
tools device ID password on the client PC.
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.
Deleting the configuration and re-creating it

To delete the configuration and re-create it, follow these steps.
1. If the console is connected, disconnect it by following these steps:
a. Select the configuration name. This is the name that Operations
b. From the Connection menu, click Disconnect. The connection status
shows Disconnecting.
c. Wait for the status to show Disconnected.
246
2. Delete the configuration:

a. Select the configuration name that you want to delete.
b. From the Connection menu, click Delete.
c. Click Yes to confirm the deletion if prompted.
3. Re-create the configuration with the service tools device ID you
previously reset or with the new service tools device ID.
Resetting the password

To reset the password for the same service tools device ID, follow these steps.
1. Select the connection name that you will be making the change for, and
then select Connection > Properties.
2. Select the Device ID tab.
3. Click the Reset button, and then click OK.
4. The Access Password window opens. Enter the current access password,
and then click OK.
change the value of autocreate service tools device IDs?

(V6R1 only)?
This topic steps you through the process of changing the value used by local consoles on
a network to automatically manage service tools device IDs.
To change the value of the Autocreate service tools device IDs option, follow these steps:
1. Access Dedicated Service Tools (DST).
2. Select Work with DST environment.
3. Select Service tools security data.
4. Change the value for the option Autocreate service tools device IDs.
If you set the value to zero, you disable this function and you will have to
manually create and manage service tools device IDs. This includes
resynchronizing the PC and system if the associated password gets out of
synchronization. The maximum value allowed is 49.
5. Select option 11 in the Selection area. Then, press Enter to save the new value.
247
unlock service tools device IDs in SST?

With the Work with service tools user IDs and Devices option, you can change Operations
Console configuration data from System Service Tools (SST) .
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 macro in Dedicated Service Tools (DST) or use the
Service tools security data menu. To unlock the service tools device IDs menu option,
complete one the following tasks:
Note: By default, the Service tools device IDs option in SST is locked. If you receive the
message The user can not perform the option selected, it indicates that the option has not
been unlocked.
To unlock this option, do the following from DST:
1. Access Dedicated Service Tools (DST).
2. Select Start a service tool > Display/Alter/Dump > Display/Alter storage > Licensed
Internal Code (LIC) data > Advanced analysis.
3. Page down until you find the FLIGHTLOG macro. Place a 1 next to the option and
press Enter. You should be on the Specify Advanced Analysis Options display.
The command should show as FLIGHTLOG.
4. Enter SEC UNLOCKDEVID in the Options field.
Note: If you want to lock this option to prevent later use, enter the parameter SEC
LOCKDEVID.
Alternatively, you can unlock the service tools device IDs by performing the following
steps in DST (V5R4M5 or later):
1. Access service tools using DST.
2. Select Work with DST environment > Service tools security data.
3. Type a 7 next to the Work with lock for device IDs from SST option and press Enter.
The status displays as Enabled, indicating that the service tools device ID has been
unlocked.
248
deallocate or move the Operations Console LAN

adapter?
During a migration, you might need to deallocate the LAN card from use by Operations
Console. You 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.
After the LAN card is deallocated, 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 following steps will cause the console to disconnect.
Follow these steps to deallocate the LAN adapter currently associated with an Operations
Console local console on a network (LAN):
devices.
2. Select System devices (skip this step if using SST).
3. If you are not using this resource for the console and you are working from
another device; or the console type is not Operations console(LAN) and you need
to stop the adapter from communicating on the network, do the following:
a. Select Configure service tools LAN adapter. You should be on the Configure
Service Tools LAN Adapter window.
b. Press F13 to deallocate the adapter. You will be required to use another
console type or resource on the next IPL.
c. If you also need to clear the LAN adapter configuration data, continue with
step 4.
If you only needed to deallocate the LAN adapter temporarily, press F12 to
exit this window. You should have returned to the Work with System Devices
window. If you are using SST, this returns you to Work With Service Tools User
IDs and Devices.
Note: After you exit this window, do not enter the configuration again.
Entering the configuration again will reallocate the LAN adapter resource. If
the LAN adapter has a configuration, the adapter will be reallocated again the
next time the system needs to start the console if you don't clear the
configuration.
249
4. To clear the network data associated with the network adapter, do the following:
a. Press F6 to perform a clear.
b. Press Enter to confirm the clear.
5. If you had to change the console type be sure to change it back.
Important: You must change the console type to something other than Operations
console(LAN) or the adapter will get reallocated.
create or verify a service host name (interface name)?

The service host name (interface name) is the name that identifies the service connection
on your network that is used for service tools, which includes an Operations Console
local console on a network (LAN) configuration.
You need a service host name (interface name) any time a console or remote control
panel is being connected using a network connection. One reason to add this function is
when a system has been logically partitioned. Although the primary partition can have a
non-networked console, a remote control panel to a secondary partition might be
desirable.
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. Follow these
guidelines when entering the name for the service host:
For small network infrastructures in which only a few devices are connected, you can
typically specify anything you want for the name and associated address. When you
set up a small network, you can specify the name and an address range.
For large network infrastructures managed by IT personnel, a specific name might be
required. This avoids confusion with other devices on the same network, and might
be used to allow the network infrastructure's equipment to know in advance what the
connection name is and what address the connection will use to communicate on the
network. Alternatively, you might be able to specify an original name, but the
address might be given to you by the network administrator.
250
There are two methods to create a service host name (interface name).
If you are setting up a new system or partition using Operations Console (LAN), the
LAN adapter is installed and the correct console type is specified during the
manufacturing process. When working through the Operations Console configuration
wizard, you must supply the connection name, as well as the network parameters.
During the initial connection, this data finishes the server configuration for the
network. This method uses BOOTP to configure the server. For more information
about BOOTP, see Bootstrap Protocol on page 318.
If you already have a console or another workstation, use the following steps to
either verify or create the configuration for the service connection. You can do this
during a migration or an upgrade before disconnecting your old console.
You must unlock the SST option before you can use it. For additional information on
SST, see unlock service tools device IDs in SST on page 248.
Note: You might have to temporarily change the console to complete this task. You can
also use any option pertaining to the service tools LAN adapter to verify the service host
name or data.
devices.
3. Select Operations console(LAN) and press Enter. This displays Verify Operations
Console Adapters.
4. Press F11 to configure.
5. The service host name (interface name) field contains the name.
If you are creating a new service connection, follow these steps:
a. Enter the network data in the appropriate fields.
b. Store your configuration by pressing F7.
c. Activate the LAN adapter by pressing F14.
d. Press F3 to exit.
e. If you changed the console to a local console on a network (LAN) in step 2,
re-select the original console.
251
change network values?

If you need to make a change to the network adapter used for Operations Console (LAN),
such as a new IP address, use these instructions.
devices.
2. Select System devices (skip this step if using SST).
4. Select Operations console(LAN). The LAN adapter currently in use should be
shown.
5. Press F11.
6. Use one of the following methods to make your change:
If you are making a simple change, such as the IP address, enter in the new
values and continue with step 7.
If you will be changing the adapter card press F6 to perform a clear. Continue
with step 8.
7. Press F7 to store the new values.
8. Press F3 until the DST main menu appears.
Important: If the change did not affect the network IP address or the service host
name (interface name) you can exit these instructions now.
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 re-create a new connection using
the new network IP address. Continue with the next step.
9. If the system/partition and client PC are using V6R1 Licensed Internal Code
(LIC) then the system and PC will manage the service tools device ID
automatically unless you have disabled this support. See change the value of
autocreate service tools device IDs (V6R1 only) on page 247 for instructions on
how to verify this support.
If you are using an earlier release or support for autocreate service tools device
IDs is not enabled, you need to reset any service tools device IDs for all eligible
console devices that will use this service interface. To reset service tools device
IDs, follow these steps:
252
Note: You must unlock the SST option before the menu option is usable. For
additional information on SST, see unlock service tools device IDs in SST on
page 248.
a. Select Work with DST environment.
c. Type 2 in front of the service tools device ID to be reset, and press
Enter.
d. Press Enter again to confirm the reset.
Note: When you reset the password in DST, the device ID password
becomes the device ID name in uppercase.
Important: If more than one PC connects to this service host name
(interface name) using a network connection you will have to delete
the configurations and therefore reset the service tools device IDs of
those PCs as well. To reset another service tools device ID, repeat this
step.
e. Press F3 until the DST main menu appears.
10. 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. The system will continue to use the old values
until an IPL or manual intervention. The second method is to perform the manual
intervention, at this time. Perform one of the sets of steps below to complete the
network changes.
Using an IPL
This method requires that the client reconfiguration be complete prior to
establishing the next connection using Operations Console on a network.
If you are currently using the console connected via LAN you would
normally start an IPL, it is recommended that the IPL be an attended IPL, and
you can reconfigure the client during the initial stages of the IPL. You could,
for example, use a different PC as the console instead of the one you currently
have connected. You could do the configuration on that PC using the steps
here, then after the IPL has been started you could disconnect the current
console PC's connection and start a connection on the other PC with the
newly created configuration. In this manner you could reconfigure the
existing client at your leisure, before the next connection to the system.
a. Start an attended IPL on the system.
b. Continue with Completing the PC changes.
253
Perform the manual intervention

Perform these steps from the DST or SST main menu.
If you are using DST, select Work with DST environment, and then
System devices.
If you are using SST, select Work with service tools user IDs and
devices
b. Select System devices (skip this step if using SST).

c. Select Select Console.
d. Select Operations console(LAN). The LAN adapter currently in use
should be shown.
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.
g. Continue with Completing the PC changes
The PC is now ready to make a connection. If you have already performed an IPL on the
system, you are now ready to reconnect using the new network data.
Completing the PC changes

After making changes to the network values for Operations Console (LAN), you need to
complete the changes to the PC.
1. To delete the old configuration, perform these steps:
a. Select the configuration name. 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.
d. Select the configuration name.
e. From the Connection menu, click Delete.
f. Click Yes to confirm the deletion if prompted.
2. Close and reopen Operations Console in order to purge the PC of network data
associated with the configuration you are changing.
Note: It is also suggested that you remove or alter the old entry in the hosts file
on the PC. You can do a search or find for hosts then double-click the file when it
is found to start the default editor.
254
3. Create a new configuration using the following steps:

a. From the Connection menu, select New configuration.
b. Continue the configuration and enter the new IP data or service host name
at the appropriate time.
c. Complete the rest of the new configuration.
disable support for the default embedded Ethernet

port, 5706/5707, or 5767/5768 adapters?
These options do not disable the port or adapters, but makes them ineligible as consolesupporting resources. Also, this support is only available on servers that are not managed
by a Hardware Management Console (HMC).
Disabling console support for either the embedded Ethernet port, add-on 5706/5707 or
5767/5768 adapters, or both, allows you to use one or both of these resources for another
purpose other than Operations Console. By default, the embedded Ethernet port is the
default location for Operations Console (LAN) configurations and may be dedicated for that
purpose.
If a 5706/5707 or 5767/5768 adapter is also present in a location where the console can
use it, you can disable this support to prevent Operations Console from selecting the
adapter for console use. These instructions are used only when the system is not managed
by the HMC and the console resource is determined by location.
To disable either the embedded Ethernet port or add-on 5706/5707 adapters using
V5R4M5 (or later) of Licensed Internal Code, complete the following steps:
1. If you are using DST, select Work with DST environment, and then System
devices.
2. If you are using SST, select Work with service tools user IDs and devices.
3. Type a 2 in either the Allow supported internal LAN adapter to be the console or Allow
supported Gigabit LAN adapter to be the console field, depending on what you want
to disable.
255
4. Press Enter.
Select Console
System:
Console type . . . . . . . . . . . . . . . .
1. Twinaxial
. . . . . . . .
Allow
be
Allow
be
S10BACFC
1=Yes, 2=No

the console . . . . . . . . . . . . . . . 2
the console . . . . . . . . . . . . . . . 2
1=Yes, 2=No
1=Yes, 2=No

F3=Exit
F12=Cancel
If you do not have a working console device, but you have another workstation that can
access System Service Tools (SST), then you can use the preceding DST/SST procedure or
use the OPSCONSOLE macro on page 215 to disable your intended resource.
If you do not have any working devices, then you must use the console service functions
(65+21) on page 232. You can also use either of these methods to re-activate support for
these resources.
256
Local console directly attached with or without remote

access allowed topics
activate the asynchronous communications adapter on the
server?
The following procedures explain how to activate an asynchronous communications adapter
on the server manually. You can activate the asynchronous communications adapter
manually whether you have a local Hardware Management Console (HMC). (A local HMC
is one that is connected to the server directly through a private network.) Refer to the
appropriate procedure for your system.
Activate the asynchronous communications adapter on a server with an HMC
To activate an asynchronous communications adapter on a server with an HMC, follow these
steps:
1. In the navigation area, expand the managed server's entry with which you want to
work.
2. Expand Service Applications, then click on Service Focal Point.
3. In the contents area, click Service Utilities.
4. From the Service Utilities window, select the managed system with which you want to
work.
5. From the Selected menu on the Service Utilities window, select Operator Panel Service
Functions.
6. From the Operator Panel Service Functions window, select the logical partition with
which you want to work (it might be the only partition on your system).
7. From the Partition Functions menu on the Operator Panel Service Functions window,
select Enable Remote Service (66).
The system attempts to initialize the asynchronous communications adapter.
If it is successful, the Function/Data window displays the system reference code (SRC)
D1008066.
If the modem initialization is unsuccessful, the Function/Data window displays D1008065
after attempting to activate the asynchronous communications adapter.
257
Activate the asynchronous communications adapter on a server without an HMC

To activate an asynchronous communications adapter on a server without an HMC, follow
these steps:
1. Use the system's control panel to place the server into manual mode
2. Use the Up and Down buttons to select function 25, and then press Enter.
3. Use the Up button to select function 26, and then press Enter.
4. Use the Down button to select function 66, and then press Enter.
The system attempts to initialize the asynchronous communications adapter.
D1008066.
If the modem initialization is unsuccessful, the Function/Data window displays D1008065
after attempting to activate the asynchronous communications adapter.
If the system fails to produce an SRC automatically, you might need to manually attempt to
retrieve the results. For more information, see Failure to display D1008065 and D1008066
automatically after calling the function on page 308 for more information.
deactivate the asynchronous communications adapter on

the server?
The following procedures explain how to deactivate an asynchronous communications
adapter on the server manually. You can deactivate the asynchronous communications
adapter manually whether or not you have a local Hardware Management Console (HMC).
(A local HMC is one that is connected to the server directly through a private network.)
Refer to the appropriate procedure for your system.
Deactivate the asynchronous communications adapter on a server with an HMC
To deactivate an asynchronous communications adapter on a server with an HMC, follow
these steps:
1. In the navigation area, expand the managed server's entry with which you want to
work.
2. Expand Service Applications, then click on Service Focal Point.
3. In the contents area, click Service Utilities.
4. From the Service Utilities window, select the managed system with which you want to
work.
5. From the Selected menu on the Service Utilities window, select Operator Panel Service
Functions.
258
6. From the Operator Panel Service Functions window, select the logical partition with
which you want to work (it might be the only partition on your system).
7. From the Partition Functions menu on the Operator Panel Service Functions window,
select Disable Remote Service (65).
The system attempts to deactivate the asynchronous communications adapter.
D1008065.
Deactivate the asynchronous communications adapter on a server without an HMC
To deactivate a asynchronous communications adapter on a server without an HMC, follow
these steps:
1. Use the system's control panel to place the server into manual mode
2. Use the Up and Down buttons to select function 25, and then press Enter.
3. Use the Up button to select function 26, and then press Enter.
4. Use the Down button to select function 65, and then press Enter.
The system attempts to deactivate the asynchronous communications adapter.
D1008065.
If the modem initialization is unsuccessful and SRC D1008065 is not displayed, see Failure
to display D1008065 and D1008066 automatically after calling the function on page 308 for
more information.
259
Local console directly attached with remote access

allowed and remote console through dial-up support
topics
work with your local console directly attached with remote
access allowed or with a remote console through dial-up
support?
This topic applies to the following configurations only:
Local console directly attached with remote access allowed
The following information applies only to this specific environment:
connect a remote console to a local console by modem directly below

work with multiple remote consoles on page 262.
use server control on page 262.
understand default user (SERVER) on page 263.
control tasks between users on page 264.
activate the asynchronous communications adapter on the server on page 257.
deactivate the asynchronous communications adapter on the server on page 258.
260
connect a remote console to a local console by modem?

Local console directly attached with remote

access allowed
The remote console user must have dial-in authority at the local console. This authority is
needed so that the operating system at the local console allows the dial-in connection
between the PCs.
Perform the following steps to connect the remote console to the local console:
1. Open Operations Console to start the connection by clicking Start --> Programs -->
IBM Client Access --> Operations Console.
By default, Operations Console does not automatically try to connect a remote
console to the local console.
If you select Start connection when Operations Console starts in Properties, the local
console starts a connection to the server automatically. The connection status
displays Connecting before changing to Connecting Console.
If you select Start connection when Operations Console starts when you configured the
remote console, the remote console starts the connection to the local console
automatically.
If a remote console connects to a local console that is not already connected to a
server, upon completion of the remote console's connection, the local console
automatically starts a connection to the server.
2. If you did not select Start connection when Operations Console starts, you need to start
the connection to the local console as follows:
b. From the Connection menu, click Connect.
3. If the User Logon window is displayed, sign on so that the operating system at the
local console can check if you are a user with dial-in authority. After you sign on
successfully, the connection status displays Connected.
Note: If you do not sign on to the remote console through dial-up support connection in
approximately a minute, Dial-up Networking ends the connection.
4. If the Service Device Sign-on window is displayed, sign on using your service tools
user ID and password.
5. Request control of the local console that is directly attached with remote access allowed.
For instructions, see requesting control at the remote console on page 267 for more
information.
If you encounter other connection problems, see Troubleshooting connection problems
on page 281 to find a possible solution.
261
work with multiple remote consoles?


access allowed
This environment is not directly affected by the takeover and recovery function.
However, if the function is enabled and there is a loss of the console, either at the local
console or remote console, data loss does not occur
The environment consists of multiple remote consoles connecting to the same local
console that is directly attached with remote access allowed. In this environment only one
remote console is allowed to connect to the local console that is directly attached with remote
access allowed. The users must work out an arrangement in which another remote console
can access the local console. If this is needed on a regular basis, it might be as easy as
assigning a time period when each remote console can access the local console. When
the time has expired for the first remote console, it releases control and disconnects. The
next remote console then connects at its assigned time and requests control. This assumes
that the local console does not have control when the first remote console gets control.
This environment might also be a single PC that can, one at a time, connect to multiple
servers.
use server control?


access allowed
An active console is a command interface to a server (5250 emulation) that is currently

interacting with the server. Thus, the PC in control becomes the console and can perform
console functions. Only one PC can have control at a time.
If your local console starts in attended mode, you have control immediately after you
connect to a local console directly attached to the server.
When you have control at this local console, you must be present to grant or refuse
control to requesting remote consoles. To grant or refuse control, see grant or refuse
control to a remote console through dial-up support on page 265.
If your local console starts in unattended mode, SERVER is displayed in the Current User
field after you connect a local console that is directly attached to the server. Operations
Console automatically grants control to the first requester (local console or remote
console).
262
Important: It is possible to create a confusing environment regarding server control. For

example, if you have Operations console(LAN) selected as your console type and you
manually activate the asynchronous communications adapter, you can connect the local
console that is directly attached with remote access allowed. This situation presents you with
the Console Information Status window, which indicates that the local console on a network
(LAN) has control. If you then connect a remote console to the local console and request
control, and the local console grants control to the remote console, the Operations Console
window properly reflects that the remote console is in control. In this environment, a
local console and a remote console, the use of control is meant only to define where the
emulator is available, not necessarily the actual console in control of the server itself. The
assumption in this environment is that Operations Console (LAN) does not exist and the
console type is Operations console(Direct).
understand default user (SERVER)?


access allowed
SERVER is
an identification name that Operations Console assigns when there is no user

in control (either the local console or a remote console) of a server.
When no user has control, SERVER is displayed in the Current User field. In addition,
Operations Console automatically grants control to the first requester (local console or
remote console).
Operations Console automatically grants control to the first requester in the following
cases:
Immediately after you release control at a local console that is directly attached with
remote access allowed.
Immediately after connecting a local console that is directly attached with remote
access allowed, if it started in unattended mode. See use server control on page 262
for more information regarding control and the initial state of making a
connection..
When SERVER is displayed in the Current User field.
263
control tasks between users?

These control tasks apply to the following configurations only:
1. Local console directly attached with remote access allowed
2. Remote console through dial-up support
The following information covers the relationship between the local console that is directly
attached with remote access allowed and a remote console through dial-up support, and the
console type is set to Operations console(Direct).
1. identify a user in control of a server directly below
2. grant or refuse control to a remote console through dial-up support on page 265.
3. request and release control at the local console on page 265.
4. request control at the remote console on page 267.
5. release control at the remote console on page 268.
6. send a message to a controlling console on page 268.
7. transfer control between users on page 269.
identify a user in control of a server?

This task applies to the following configurations only:
To identify which user has control, perform the following steps:

1. In the Operations Console window, look for the row that displays the
connection details for the configuration in question.
2. Identify the Current User and System Name values. These values belong to the
user who has control. Current User displays the user ID with which the user in
control signed on to the operating system of the PC in control or completed
the connection. System Name displays the PC name where the user is in
control.
3. Identify the Local Console value. It is the name of the PC that is directly
attached to the server.
4. Compare the System Name and Local Console values as follows:
The local console has control if the System Name and Local Console values
are the same. This comparison is useful to the connected remote console
through dial-up support user.
A remote console through dial-up support has control if the System Name and
Local Console values are different. This comparison is useful to the local
console user.
No user has control if SERVER displays as the Current User and System
Name value. This is useful to either the local console or the remote console
through dial-up support user. A request for control is automatically granted.
264
grant or refuse control to a remote console through dial-up

support?
As an operator of a local console that is directly attached with remote access allowed, you
must handle incoming requests for when you have control. For additional
information on server control, see use server control on page 262 for more
information.
Granting control allows another user to work with the server. Refusing control denies
a requesting user access to the server and allows the current user to continue to have
control. When you grant control to another user, your console session closes.
When a remote console requests control, and the local console has control, the
Operations Console Request window is displayed at the local console. The window
displays the service tools user ID with which the requesting remote console user
signed on to the operating system of the remote console (PC). The default is set to
grant control.
Note: If the local console is not in control at the time the remote user requests
control, there is no dialog presented at the local console. The remote user is
automatically granted control.
Grant control
To grant control to a remote console through dial-up support, in the Operations Console
Request window, click OK.
Refuse control
To refuse control to a remote console through dial-up support, follow these steps:
1. In the Operations Console Request window, click Reject request.
2. (Optional) In the Message field, type an explanation for the refusal.
3. Click OK.
request and release control at the local console?

When your local console does not have control of the server, you must request
control at the local console to work with a server. Requesting control at the local
console forces control back from a remote console if the remote console has control.
265
After finishing your work, you must release control to allow Operations Console to
automatically grant control to a requester. For more information about server control,
see use server control on page 262 for more information.
Request control at the local console
To request control at the local console, perform the following steps:
1. Identify a user in control of a server.
2. If no user has control (SERVER is displayed in the Current User field), do the
following:
b. From the Connection menu, click Request Control.
c. If the Service Device Sign-on window is displayed, sign on using your service
tools user ID and password. Operations Console needs a valid service tools
user ID and password to authorize the connection between the server and the
PC.
If you have problems when signing on, see Troubleshooting authentication
problems on page 285.
d. Confirm that the console is displayed.
If it is not displayed, see Troubleshooting connection problems on page 281.
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 a controlling console asking the user
to release control. To request control at the local console, after the remote console
releases control and control does not return to the local console, complete steps
2.a through 2.d.
If a remote console user has control and you do want to force control back from
the remote console, complete steps 2.a through 2.d. At the remote console, the
console closes and a message is displayed indicating that the local console has
taken control.
Release control at the local console
To release control, do the following:
1. Select the configuration name.
2. From the Connection menu, click Release Control.
At this time, SERVER is displayed in the Current User field. The console disappears.
Then control is automatically granted to the first requester.
266
request control at the remote console?

Requesting control of the server at the remote console allows you to have an active
console at the remote console. An active console is a command interface to a server
(5250 emulation) that is currently interacting with the server. You must have a
remote console connected to a local console by a modem. For more information, see
connect a remote console to a local console by modem on page 261.
For more information about server control, see use server control on page 262.
To request control at the remote console, perform the following steps:
1. Identify the user who has control.
2. If SERVER is displayed in the Current User field, do the following:
a. Select the configuration name from the Operations Console window.
If no user has had an active console, the Service Device Sign-on window might
be displayed.
c. If the Service Device Sign-on window is displayed, sign on using your service
tools user ID and password. Operations Console needs a valid user ID and
password to authorize the connection between the server and the PC. For
problems when signing on, see Troubleshooting authentication problems on
page 285.
After you sign on successfully, the console is displayed.
3. If the local user has control, complete the following steps:
a. Optional: Send a message to the local console explaining why you need to
have control. For more information, see send a message to a controlling
console on page 268.
If the local user grants control to the remote console, the console is displayed.
If the local user refuses control to the remote console, a window displays
indicating the refusal.
267
release control at the remote console?


Releasing control of the server 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 grants control to the first requesting remote console,
releasing control at the remote console allows the local console to regain control.
However, if control is automatically granted to the first requesting remote console,
releasing control at the remote console allows the next requester to automatically be
granted control (local or remote). For more information about server control, see use
server control on page 262.
To release control at the remote console, perform the following steps:
1. Select the configuration name from the Operations Console window.
2. From the Connection menu, click Release Control. The console window closes.
After you release control at the remote console, you can end the remote console
connection to the local console:
1. Select the configuration name.
2. From the Connection menu, click Disconnect. The connection status displays
Disconnecting.
3. Wait until the status displays Not connected to local console.
send a message to a controlling console?


While using Operations Console, you might need to communicate with the user who
has control of the server. Operations Console allows a local console and a remote
console to exchange messages when connected. Only the user that does not have
control can initiate a message. For more information about server control, see use
server control on page 262.
To send a message to the user who has control, perform the following steps:
1. Select the configuration name from the Operations Console window.
2. From the Connection menu, click Send Message.
3. Type the message.
4. Click Send.
At this time, the receiver can reply by typing a response and clicking Reply.
268
transfer control between users?

The following examples show interactions between a local console and a remote
console. The examples illustrate how server control is transferred between PCs after
beginning an Operations Console configuration.
Example: Transfer control between a local console in control and a remote
console
This example describes interactions between a local console that is directly attached with
remote access allowed that has server control and a remote console through dial-up
support. It illustrates how control is transferred between the local console and the
remote console through dial-up support when the remote console requests control.
These interactions describe the expected behavior from the local console and remote
console through dial-up support users.
The local console user has control of a server. At this time, the local console
user must handle all incoming control requests.
When a remote console through dial-up support requests control, the local
console user decides whether to grant or refuse control to the requester.
If the local console user grants control, control is granted to the requester.
If the local console user refuses control to the requester, the local console user
continues to have control.
Example: Transfer control between a local console not in control and remote
consoles
This example describes interactions between a local console that is directly attached with
remote access allowed that does not have server control and remote consoles through
dial-up support requesting control. It illustrates how control transfer occurs when no
user has control and a remote console through dial-up support requests control.
These interactions describe the expected behavior from the local console and remote
console through dial-up support users:
No user has control of a server. Therefore, SERVER is displayed in the Current
User field and incoming control requests are automatically granted.
When a remote console through dial-up support requests control, control is
granted to the remote console through dial-up support.
269
Filler page
270
Appendix A. Shutting down systems or

logical partitions
Shutting down systems or logical partitions overview
The correct way to shut down a logical partition safely is from a command line.
If you cannot shut down the logical partition from a command line, you can shut down the
logical partition from the Shut Down Partition window on your HMC, from the remote control
panel on the Operations Console, or use the physical control panel. Using these methods can
cause an abnormal shutdown and can result in loss of data.
Before you shut down a logical partition, you must perform all of the basic shutdown tasks. For
example, all other users must be signed off of the logical partition before you can shut it down.
If you shut down the logical partition without completing all of the required tasks, you can cause
damage to data or cause the system to behave in unpredictable ways. For more information on
what you must do before shutting down the logical partition, see the Basic system operations
topic collection in the on-line Information Center.
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/rzal2/rzal2kickoff.htm
http://publib.boulder.ibm.com/infocenter/systems/topic/rzal2/rzal2kickoff.htm
Important: Use a delayed shutdown only if the PWRDWNSYS command fails to power down
the system or partition. Only use the immediate shutdown if the delayed shutdown isn't
successful.
Delayed shutdown
Use delayed shutdown only when you must shut down a logical partition, and the
PWRDWNSYS command does not work.
When you use the delayed shutdown option, the partition waits a predetermined amount of time
to shut down. This allows the partition time to end jobs and write data to disks.
If the partition is unable to shut down within the predetermined amount of time, it will end
abnormally and the next restart might take a long time.
271
Immediate shutdown
Use immediate shutdown only when a logical partition cannot shut down using PWRDWNSYS
or delayed shutdown.
When you use the immediate shutdown option, the system powers down without any preset
delay.
Attention: This will cause an abnormal IPL of the logical partition to be performed and possibly
cause loss of data.
Use the remote control panel, physical control panel, or HMC, if available, to perform a delayed
shutdown or an immediate shutdown. The power button will start a delayed shutdown and
function 8 will start an immediate shutdown of a system.
Shutting down systems or partitions using the current console or

other workstation
The correct way to shut down a logical partition or system safely is from a command line and
run the Power Down System (PWRDWNSYS) command.
Before you shut down a system or logical partition, complete the following:
1. If an Integrated xSeries Adapter (IXA) is present on the system, shut down the IXA.
2. Ensure that all jobs are completed and all applications are ended.
3. Ensure that your partition profiles, if a HMC or IVM is being used, are updated with any
dynamic logical partitioning resource changes that you want to keep when you restart the
logical partition.
From the command line in the emulator session, type PWRDWNSYS OPTION (*CNTRLD)
DELAY (600) and press Enter. The system will only shut down the logical partition you
selected. The PWRDWNSYS command does not affect other logical partitions on your system.
If you enter the PWRDWNSYS command with the RESTART(*YES) option, the operating
system restarts, and the resource specifications of the logical partition remain the same.
If you do not use the RESTART(*YES) option, then the logical partition shuts down
completely, and other logical partitions will be able to take and use the resources that were used
by the logical partition. Also, when you reactivate the logical partition using a partition profile,
the partition profile overlays the resource specifications of the logical partition with the resource
specifications in the partition profile. Any resource changes that you made to the logical
partition using dynamic logical partitioning are lost when you reactivate the logical partition
using a partition profile.
272
If the logical partition is set to start automatically when the managed system starts, you can
preserve the resource specifications on that logical partition by restarting the entire managed
system using the Partition autostart power-on mode. When the logical partitions start
automatically, the logical partitions have the resource specifications that the logical partitions
had when you shut down the managed system.
If the PWRDWNSYS command does not work, use one of the following methods to shut down
the system or logical partition:
Attempt to power down using the immediate option.
A delayed power down using the physical control panel
Delayed - Pre-Power5 processor-based

http://publib.boulder.ibm.com/infocenter/iseries/v5r3/topic/rzal2/rzal2usepower.htm
Use the power push button
If you cannot use option 3 (Power off the system immediately) or option 4 (Power off the
system immediately and then power on) on the Power On and Off Tasks (POWER) menu to
stop the system, you can turn the power off using the Power push button to turn off the
system when the mode is set to Manual.
Note: Using the power push button to turn off the system may cause results that cannot
be predicted in your data files, and the next IPL (initial program load) will take longer to
complete. Using the Power push button to turn off the system will power down all
partitions.
Make sure that there are no tapes in the tape units or diskettes in the diskette units, and
that the mode is set to Manual.
Do not turn the modem on or off when the system is turned off and is made ready for
remote IPL. Otherwise, the system may start unexpectedly, although it turns itself off in a
few minutes.
To turn the power off using the Power Push button, do the following:
1. On the control panel, press the Power push button. The Function/Data display
blinks with 0 (the international power off symbol).
2. Press the Power push button again. The Power On light blinks as the system is
being powered off. When power off is complete, the light goes off.
273
If the system does not turn the power off within 30 minutes, wait for the System
Attention light to come on. When the System Attention light comes on, go to
Service and support and Troubleshooting and follow the steps necessary to solve the
problem.
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/topic/rzahg/rzahgictroub2.htm
Delayed - Power-processor-based systems

http://publib.boulder.ibm.com/infocenter/systems/topic/iphb5/cpfoffpanelbutton.htm
Using the control panel power button to power off
By using the control panel power button to power off the server, you can initiate a
delayed power off (DPO) or a fast power off (FPO).
Attention: Using the control panel power button to power off the system might cause
unpredictable results in the data files, and the next IPL will take longer to complete.
Note: Some servers do not respond to the power-off sequence unless the system is in
manual operating mode. If necessary, set the system operating mode to manual mode.
See Putting the physical control panel in manual operating mode.
http://publib.boulder.ibm.com/infocenter/systems/topic/iphb5/cpfmanualmode.htm
To use the control panel power button to power off the system, see the following topics
Initiating a delayed power off (DPO)

You can use the power button on the control panel to initiate the delayed power
off (DPO) feature.
To initiate a delayed power off (DPO), do the following:
1. Press and hold the power button on the control panel for four seconds.
After one second, a countdown time is displayed. The default countdown
time is four seconds.
2. Continue to press and hold the power button until the countdown time
reaches zero, and then release the power button. The DPO is initiated.
To cancel the DPO before it starts, release the power button before the
countdown reaches zero.
If the power button is depressed for less than one second, no countdown time is
displayed, and the power-off function is not initiated.
Initiating a fast power off (FPO)

You can use the power button on the control panel to initiate the fast power off
(FPO) feature.
To initiate a fast power off (FPO), do the following:
1. Press and hold the power button on the control panel for four seconds.
After one second a countdown time is displayed. The default countdown
time is four seconds.
274
2. Continue to press and hold the power button until the countdown time
reaches zero and until after the delayed power off (DPO) is initiated. A
new DPO-FPO separation count of 10 seconds is started. The separation
count is used to distinguish a DPO from an FPO. During this interval,
SRC D10E0FF0 is displayed, followed by the countdown time.
3. Continue to press and hold the power button for 10 seconds until the
DPO-FPO separation count reaches zero, and then release the power
button. When the FPO count expires, SRC D10E0FF1 is displayed, and the
FPO is initiated.
If you release the power button during the DPO-FPO separation count, the FPO is
canceled, and the DPO continues.
If you continue to press the power button after the DPO-FPO separation interval
has expired, or if you press and hold the power button while a DPO is in progress,
the FPO countdown begins again with a SRC D10E0FF0 displayed.
Delayed power down using the remote control panel from

Operations Console
To perform a delayed power off or an immediate power off, you should be working with the
remote control panel. The power button will start a delayed power off and function 8 will
start an immediate power off of a system. You need a Service Tools user ID with operations
or administration authority to the System Partitions function in Dedicated Service Tools (DST) to
display the remote control panel.
Delayed power down using version 6 or earlier of the HMC

You can shut down a logical partitions using the Hardware Management Console (HMC).
Before you shut down the logical partition, complete the following:
1. If an Integrated xSeries Adapter (IXA) is present on the system, shut down the IXA.
2. Ensure that all jobs are completed and all applications are ended.
3. Ensure that your partition profiles are updated with any dynamic logical partitioning
resource changes that you want to keep when you restart the logical partition.
The correct way to shut down an logical partition from the HMC is to open an HMC 5250
emulator session and run the Power Down System (PWRDWNSYS) command.
275
To shut down an logical partition version 6 or earlier of the HMC, follow these steps:
1. Open an HMC 5250 emulator session for a logical partition. See Start a 5250 console
locally on page 207 or Connecting to a 5250 console remotely on page 208 for
instructions.
2. From the command line in the emulator session, type PWRDWNSYS OPTION
(*CNTRLD) DELAY (600) and press Enter. The system will only shut down the
logical partition you selected. The PWRDWNSYS command does not affect other
logical partitions on your system.
If you enter the PWRDWNSYS command with the RESTART(*YES) option, the
operating system restarts, and the resource specifications of the logical partition
remain the same.
If you do not use the RESTART(*YES) option, then the logical partition shuts down
completely, and other logical partitions will be able to take and use the resources that
were used by the logical partition. Also, when you reactivate the logical partition
using a partition profile, the partition profile overlays the resource specifications of
the logical partition with the resource specifications in the partition profile. Any
resource changes that you made to the logical partition using dynamic logical
partitioning are lost when you reactivate the logical partition using a partition profile.
If the logical partition is set to start automatically when the managed system starts,
you can preserve the resource specifications on that logical partition by restarting the
entire managed system using the Partition auto-start power-on mode. When the
logical partitions start automatically, the logical partitions have the resource
specifications that the logical partitions had when you shut down the managed
system.
3. If the PWRDWNSYS command does not work, you can use either of the following
methods to shut down the logical partition.
Attention: Using these methods can cause an abnormal shutdown and can result in loss
of data.
Performing a delayed shutdown of an logical partition using version 6 or earlier

of the HMC
You can perform a delayed shutdown of a logical partition using the Hardware
Management Console (HMC). Using delayed shutdown is equivalent to using the
power button on the remote control panel. Use delayed shutdown only when you
must shut down a logical partition, and the PWRDWNSYS command does not work.
When you use the delayed shutdown option, the logical partition waits a
predetermined amount of time to shut down. This allows the logical partition time to
end jobs and write data to disks.
276
If the logical partition is unable to shut down within the predetermined amount of
time, it will end abnormally and the next restart might take a long time.
To perform a delayed shutdown of a logical partition using version 6 or earlier of the
HMC, complete the following:
3. In the contents area, open the managed system on which the logical partition
resides.
4. Open Partitions.
5. Right-click the logical partition that you want to shut down and select Shut
Down Partition.
6. Select Delayed and click OK.
Performing an immediate shutdown of an logical partition using version 6 or earlier of
the HMC
Use this procedure to perform an immediate shutdown of a logical partition using the
Hardware Management Console (HMC).
Attention: Using immediate shutdown can cause an abnormal IPL of the logical
partition and possibly cause loss of data. Use immediate shutdown only when a
logical partition cannot shut down using PWRDWNSYS or delayed shutdown.
When you use the immediate shutdown option, the system shuts down without any
preset delay. Using immediate shutdown is equivalent to using function 8 on the
remote control panel.
To perform an immediate shutdown of a logical partition using version 6 or earlier of
the HMC, complete the following:
3. In the contents area, open the server on which the logical partition resides.
4. Open Partitions.
5. Right-click the logical partition that you want to shut down and select Shut
Down Partition.
6. Select Immediate and click OK.
277
A delayed power down using version 7 or later of the HMC

You can perform a delayed shutdown of a logical partition using the Hardware Management
Console (HMC). Using delayed shutdown is equivalent to using the power button on the
remote control panel. Use delayed shutdown only when you must shut down a logical
partition, and the PWRDWNSYS command does not work.
When you use the delayed shutdown option, the logical partition waits a predetermined
amount of time to shut down. This allows the logical partition time to end jobs and write data
to disks.
If the logical partition is unable to shut down within the predetermined amount of time, it
will end abnormally and the next restart might take a long time.
To perform a delayed shutdown of a logical partition using version 7 or later of the HMC,
complete the following:
1. In the navigation pane of your HMC, open Systems Management, open Servers, and
click the managed system on which the logical partition is located.
2. In the contents pane, select the logical partition, click the Tasks button, and choose
Operations > Shut Down.
3. Select Delayed and click OK.
Performing a shutdown using IVM

Use any role other than View Only to perform this task.
The Integrated Virtualization Manager provides the following types of shutdown options for
logical partitions:
Operating System (recommended)
Delayed
Immediate
The recommended shutdown method is to use the client operating systems shutdown command.
Using the immediate shutdown method should be used as a last resort as this causes an abnormal
shutdown which might result in data loss.
278
If you choose the Delayed shutdown method, then be aware of the following considerations:
Shutting down the logical partitions is equivalent to pressing and holding the white
control-panel power button on a server that is not partitioned.
Use this procedure only if you cannot successfully shut down the logical partitions
through operating system commands. When you use this procedure to shut down the
selected logical partitions, the logical partitions wait a predetermined amount of time to
shut down. This allows the logical partitions time to end jobs and write data to disks.
If the logical partition is unable to shut down within the predetermined amount of time, it
ends abnormally, and the next restart might take a long time.
If you plan to shut down the entire managed system, shut down each client logical partition an
then shut down the Virtual I/O Server management partition.
To shut down a logical partition, do the following:
1. From the Partition Management menu, click View/Modify Partitions. The View/Modify
Partitions panel is displayed.
2. Select the logical partition that you want to shut down.
3. Click Shutdown. The Shutdown Partitions panel is displayed.
4. Select the shutdown type.
5. Optional: Select Restart after shutdown completes if you want the logical partition to start
immediately after it shuts down.
6. Click OK to shut down the partition. The View/Modify Partitions panel is displayed, and the
partition is shut down.
Return to the procedure you were working with.
279
Filler page
280
Appendix B. Troubleshooting
Some common troubleshooting topics are included here. For additional topics see the on-line
Information Center appropriate for your model system.
Troubleshooting connection problems

Local console
All connectivities
Message: The connection to the system is not a secure connection
You may receive this error message: The connection to the system
is not a secure connection.
These messages appropriately appear during a D-mode (installation) IPL.
Authentication is not performed and the remote control panel (LAN) is not
supported for this IPL type.
Directly attached
Status remains Connecting
Here are some possible solutions to try if you are experiencing problems that
prevent the local console from connecting to the server or prevent the remote
console from connecting to a local console due to incorrect hardware or software
configurations.
Try these possible solutions:
Verify that the PC resources 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
Note: Use the Operations Console Properties window to change the IP

base address from 192.168.0.2. For example, you can use 192.168.1.2.
A SOCKS-enabled PC accesses the Internet through a firewall, such as
Microsoft Proxy Client, Hummingbird SOCKS Client, or others.
281
Console fails to start

Under certain circumstances, a local console that is directly attached fails to connect.
This might be the result of the server's asynchronous communications adapter
being deactivated for some reason, such as an exception that takes place.
This deactivation most likely results when you start your server and have an
associated system reference code (SRC) on the control panel or Hardware
Management Console )HMC), if installed, along with the attention light.
To reset the asynchronous communications adapter with or without an HMC, see
deactivate the asynchronous communications adapter on the server on page 258.
If the deactivation is successful, the Function/Data window (or the HMC)
displays D1008065.
To activate the asynchronous communications adapter on the server with or
without an HMC, see activate the asynchronous communications adapter on the
server on page 257.
The system attempts to initialize the adapter.
If it is successful, the Function/Data window (or the HMC) displays D1008066.
If it cannot initialize the asynchronous communication adapter, it displays
D1008065 after attempting to activate the asynchronous communications adapter.
If the expected SRC is not displayed after several minutes on servers without an
HMC, see Failure to display D1008065 and D1008066 automatically after calling
the function on page 308.
Session unexpectedly disconnects

Here is a possible solution to try if you have a console session that unexpectedly
disconnects while working with a local console that is directly attached.
If the console session closes unexpectedly and the status is Connecting console, the
input/output processor (IOP) that controls the console might experience a
reset/reload. When the IOP, particularly the MFIOP, goes into a reset or reload,
the connection to the local console that is directly attached does not automatically
reconnect. You must perform a control panel function 65, and then a function 66
to manually reactivate the connection. For more information on deactivating and
activating the asynchronous communications adapter, see deactivate the
asynchronous communications adapter on the server on page 258 and activate the
asynchronous communications adapter on the server on page 257.
282
On a network (LAN)
configurations.
For a local console on a network (LAN) configuration and you are using Ethernet for
your network, you can use a crossover cable. This isolates the PC and server from
any potential problems on your network that might interfere with correct
operations.
Note: A crossover cable is a standard network cable that has the transmit and
receive signal wires reversed. This essentially allows each end to act as if a hub,
switch, or router is between them.
Network connection errors

occur when a local console on a network (LAN) fails to connect to a server.
Try these possible solutions:
Verify the network is working.
Verify that you provide the correct password to allow the server to access
your service device information during the configuration wizard. Also,
verify that you are providing the correct service tools user ID and
password.
If you are using Ethernet for your network, you can use a crossover cable
to directly connect the PC to the adapter temporarily. This isolates the PC
and server from any potential problems on your network that might
interfere with correct operations.
Note: A crossover cable is a standard network cable that has the transmit
and receive signal wires reversed. This essentially allows each end to act
as if a hub, switch, or router is between them.
283
Session unexpectedly disconnects

Here is a possible solution to try if you have a console session that unexpectedly
disconnects while working with a local console that is directly attached.
If the console session closes unexpectedly and the status is Connecting console, the
input/output processor (IOP) that controls the console might experience a
reset/reload. When the IOP, particularly the MFIOP, goes into a reset or reload,
the connection to the local console that is directly attached does not automatically
reconnect. You must perform a control panel function 65, and then a function 66
to manually reactivate the connection. For more information on deactivating and
activating the asynchronous communications adapter, see deactivate the
asynchronous communications adapter on the server on page 258 and activate the
asynchronous communications adapter on the server on page 257.
Remote console
configurations.
For a remote console connecting to the local console, verify that the server
name and the local console name are correct.
Remote console fails to connect to local console

Here are some possible solutions to try if a problem occurs when a remote
console modem fails to establish a connection with a local console.
Verify that the server name and the local console name are correct.
If your PC modem is listed as Standard Modem in the Modems folder,
configure it with a different manufacturer and model.
If you have an original equipment manufacturer (OEM) modem, your
OEM modem might not be configured correctly. If that is the case, try to
configure it using some similar modem setups.
284
Local console name mismatch when remote console connects to

the local console
Here is a possible solution to try if there is a console name mismatch when the
remote console connects to the local console.
It is important that the users at both ends check the Local Console column in the
Operations Console window. The name TCP/IP uses is retrieved and placed there.
When the remote console through dial-up support is then configured, you need to
verify the name of the local console is the same. It is possible to have two
different system names on the same PC. The name used for Operations Console is
taken from the DNS entry in the TCP/IP service.
Troubleshooting authentication problems

Authentication errors
Here are some possible solutions to try if your PC cannot complete a connection between
the local console and the server.
While you are connecting a local console to a server, you might encounter local console
connection problems. The errors consist of software configuration problems or
unrecognizable service tool user Ids.
Verify that you are entering a valid service tools user ID and password during the
configuration wizard. For example, you just performed a scratch installation and
the console is not coming up after the code was restored. The PC being used has a
user-created service tools device ID. In this case, the only valid service tools
device ID is QCONSOLE since all of the user-created service tools device IDs
were removed or reset as part of the initialization of the load source hard disk
drive. You must delete and then recreate a connection using QCONSOLE as the
service tools device ID.
285
Verify that your server and Operations Console are installed with the same
version of i5/OS and Client Access, respectively. If you are running different
versions and are creating a new service tools device ID, the password becomes
the name of the service tools device ID in uppercase, just as if the device ID were
to be reset. For example, if the client is running V5R4 code and the server is
running V5R3 code and you are creating a new service tools device ID for a new
PC to connect, the PC asks for a password for the device ID. You might name the
device "system1", for example. When you create this on the PC, you are
prompted for a password. You must use "SYSTEM1" because the system cannot
assign a different password for this name. The same is true if the client is running
V5R3 and the server is running V5R4. The V5R4 code, at either end, cannot
assign a password since the password is automatically made the same as the name
in uppercase.
You might also receive an error message regarding a secure connection. For information
about this error, see Error message: Connection to system is not secure.
Local console on a network (LAN) receives device ID password error

message
Here is a possible solution to try if a local console on a network (LAN) receives a device ID
password error message.
Due to a synchronization problem involving the service tools device ID's password
between the client (PC) and server, you might receive the following error message while
having a local console on a network (LAN) connection:
The PC service tools device password and the iSeries service tools device password do not
match. Either the service tools device ID is already in use or the passwords must be RESET on
this PC and the system.
To resynchronize these passwords, see resynchronize the PC and service tools device ID
password on page 242.
286
Unable to authenticate a connection due to all DST user IDs being

disabled
The following PTFs add function that allows you to reset the DST user ID 11111111:
V5R4M5
MF45244
MF45246
V6R1
MF45247
MF45248
With this PTF installed, the user would be able to perform 9 control panel function 65s to
reset the user 11111111 to its default state and password allowing the user to sign on and
proceed with recovery. To allow the user to keep track of their progress create a link to
take them to the reset service tools device ID QCONSOLE using the control panel. This
function also resets this device ID in the process of resetting the user ID. For assistance in
performing this function see see resynchronize the PC and service tools device ID
password on page 242. The resynchronize has you perform 7 control panel function 65s
so you just need to perform two additional 65s
Once this procedure has been successfully been performed you will be able to
authenticate using this user ID and continue recovering the console or other DST users
from i5/OS using the F18 recovery mechanism, if enabled. See Forced takeover on page
227 for information regarding the F18 function.
287
Troubleshooting system reference code (SRC) data

The following SRCs are available here for look-up and analysis:
A6nn500x, A6005001, A6005004, A6005007, A6005008, D1008065, A9002000, A6005082,
D1008066, C6004508
SRCs A6nn500x
These system reference codes (SRC) are used to access console types and console tasks
associated with the console service functions (65+21).
These SRCs are associated with the operation of the control panel method to change the
console type or accomplish a console task when the console or other workstation is not
available. For more information on how to use this function, see Using the console service
functions (65+21).
Note: nn can be any alphanumeric designation.
A6nn 500A - You are displaying the current console value setting.
A6nn 500B - You did a second 65+21 so you are in edit mode.
A6nn 500C - You executed a second 21 to cause an action, such as setting the
console to another value.
A6nn 500D - Too much time elapsed after entering edit mode to cause an action so
you must enter edit mode again if you intend to make a change. A function 21 at this
time forces the console to DST, not causing an action.
288
SRCs A6005001, A6005004, and A6005007

These system reference codes (SRCs) are used for a console that fails during initial program
load (IPL) (not Operations Console).
The following SRCs might be displayed for twinaxial consoles.
A6005001
A console resource (controller) was not found when the server was started.
A6005004
A console device was not found when the server was started. A twinaxial
controller was found but cannot be used. This indicates only the presence of a
controller. It does not indicate that the controller can be defective.
A6005007
A console device was not found when the server was started. The controller
(6A59) was found but the connection is starting. This can be a problem with the
device or emulator, or the data flow path is not being established or maintained.
These SRCs, as well as the attention light, are reset when a console is detected and
becomes active. It is possible that you might have to restart the server to find a console
device again if one of these SRCs exists for a long period of time, depending on many
factors, including model, hardware present, etc. You can force the server to try to find the
console again by doing a function 21 from the control panel, remote control panel, or
virtual control panel. You can also use the console service functions (65+21) to gather
data or attempt recovery.
289
SRC A6005008
This system reference code (SRC) is used for a console that fails during a manual IPL
(Operations Console or D-mode IPL). The data present in this SRC has evolved from V5R3 to
the latest code. Some of these changes were introduced using PTFs and later used in the next
release's base code. Not all words within the SRC are used for all problems.
Use the following tables if you received SRC A6005008. If restarting the server did not find a
console and if the console type is set to anything except a 1, the system displays code
A6005008.
If you are attempting to use a twinaxial console, the only data relevant in this SRC is
word 16. Use the following table to determine the twinaxial failure. The first four
characters of this word contains the last four characters of the original failure type. For
example, if word 16 contains 50010001, the twinaxial-related SRC is A6005001 and the
console type is set to use a twinaxial console.
If you are attempting to use Operations Console, select the appropriate section in the
table below as follows:
Local console on a network (LAN) uses words 13, 14, and 15.
Local console that is directly attached uses words 17, 18, and 19.
Note: If you just replaced the LAN adapter associated with a local console on a network (LAN),
you need to wait at least 35 minutes for the server to find and use the new LAN adapter. In this
case, after the server is satisfied, it starts using the new adapter, the console starts, and the SRC
disappears.
This topic will provide a step-by-step analysis, on page 298 of an example A6005008 SRC and
provide the meaning of the data along with applicable usage and reference what needs to be
performed in order to make a change. Keep in mind that you do not have to follow this step-bystep method to get to the meaning of the various parts of the data.
The words of data are represented differently depending on how you accessed the data. In our
example you see words 1 thru 9 which would correspond to functions 11 thru 19 on older
physical control panels or the RCP/VCP. For more help in determining this data see display the
system reference code (SRC) detail on page 211.
Here's a very common SRC we'll work with:
Word 1: A6005008
Word 2: 03D00061
Word 3: 06C00004
Word 4: 00000011
Word 5: C0000000
Word 6: 50070A03
Word 7: 000000FA
Word 8: 00000000
Word 9: 00000000
290
Here the data is broken down into the significant pieces:

Click the link in the data areas to go to the appropriate table of details.
Word
Data
Significant
Data
A6005008
Base SRC
Not used
Significant
Data
Significant
Data
11
A6005008
12
03D00061
13
06C00004
06
AA
LAN flag
C0
BB
Assigned
direct connect
location
0004
CCCC
LAN console reason
code for the failure
14
00000011
15
C0000000
16
50070A03
0A
GG
Tag information
03
HH
Console type
17
000000FA
18
00000000
19
00000000
00000011
DDDDDDDD
Depends on reason
code in word 13
C0000000
EEEEEEEE
Depends on reason
code in word 13
5007
FFFF
If the console is
twinaxial this is the
SRC that would have
been displayed
000000FA
JJJJJJJJ
Direct cable reason
code
00000000
KKKKKKKK
Depends on reason
code in word 17
00000000
LLLLLLLL
Depends on reason
code in word 17
291
Word 13 (AA BB) of AA BB CCCC

The following table contains the Word 13 values for the AABB status indicators, which display
differently depending on the system's code level and whether or not you have installed PTF
MF39303 (V5R3M5) or PTF MF39304 (V5R4M0). The AABB values only display on systems
that are not managed by a Hardware Management Console (HMC).
V5R3/V5R4 Without PTF MF39303 (V5R3M5) or PTF MF39304 (V5R4M0)
AA means:
E1 - Allows the internal embedded adapter.
00 - No support for the internal embedded
adapter.
Example
BB means:
E2 - Allows the external adapter.
00 - No support for the external
adapter.
E1E20005 (AA BB CCCC) = Allows both the internal embedded adapter and external adapter (typical values for
new systems). The system is on the network, but is not communicating with the PC.
V5R3/V5R4 With PTF MF39303 (V5R3M5) or PTF MF39304 (V5R4M0)

AA means:
E0 - System is upgraded from V5R3 and support
for the 1 GB Ethernet adapter is not set.
E1 - Disabled. Both the internal embedded
adapter and external adapters are not being
searched for.
E2 - Allows the internal embedded adapter.
E4 - Allows the external adapter.
E6 - Allows both internal embedded adapter and
external adapter.
BB means:
C2, C3, or C4 - Location of selected
asynchronous adapter used for console,
ECS, and remote service.
Note: C4 cannot be selected for use
with the console when using the 2793
asynchronous adapter, but it can be
selected for use with ECS and remote
service.
Example
E6C30005 (AA BB CCCC) = Allows both the internal embedded adapter and external adapter
(typical values for new systems), and the asynchronous adapter can be used for console, ECS,
and remote service. The system is on the network, but it is not communicating with the PC.
292
V5R4M5 and later

Word 13 reason codes as AA BB in the 5008 SRC code AABBCCCC:
A
0
0
0
0
0
0
E
E
F
A Embedded or External flag state (0 or E)

Embedded flag is on
0 D-mode with no flags
1 no LAN flags are on - This is the disable
flag.
2 Embedded is enabled
4 External is enabled
6 Both internal and external enabled
Only the external flag is on
0-5 Selected LAN card location
BB Selected Async card location C1 - C5
F FF HMC managed, Thin Console or
Primary / standalone on Pre-Power5
processor-based
Examples for AABB

06C0 Both internal and external enabled and no async card has been selected.
E1C2 Only the external flag is on and the LAN adapter in C1 has been selected. The async
adapter in C2 has been selected.
293
Word 13 (CCCC) of AA BB CCCC

Word 14 (DDDDDDDD) Word 15 (EEEEEEEE)
The following table defines the Words 13, 14, and 15 values.
Word 13 (AA BB CCCC) for a local console on a network (LAN).
(AA BB
CCCC)
If Word 13
value
(CCCC) is:
0000
0001
Failure
Unexpected condition
LAN
Word 14
DDDDDDDD
means:
Could report any word 14 data
for any of the other reason
codes (cccc)
No supported hardware
detected or hardware
detected is not expected.
For example, you replaced
the LAN IOA so the serial
number is different.
Word 15
EEEEEEEE
means:
Could report any data for any
word 15 of the other reason
codes (cccc)
In some cases the serial number
of the expected adapter might
be displayed. If a serial number
is displayed, an adapter was
previously configured. If you
are installing a new server or
partition that you will rely on
BOOTP to complete the
configuration, you might have
to clear this data use the
console service functions

(65+21) on page 232.
0002
0003
LAN IOA failed to report

Hardware error
Common error codes:

53001A80, 53002AC0 Network, cable or the LAN
adapter might not be
operational.
Adapter position or serial

number of adapter
00000000: This error code

indicates the adapter reported,
but is not initialized yet. This is
not considered an error at this
time. The adapter should be
activated shortly.
0004
BOOTP status:
If attempts are zero, then
BOOTP is ready when
called.
If attempts have a value,
then the PC did not
respond.
For other error codes, contact

your service provider.
Attempts
294

number of adapter
(AA BB
CCCC)
If Word 13
value
(CCCC) is:
0005
FFFF
Failure
Word 14
DDDDDDDD
means:
Server's LAN connection IP address

is active, but the PC failed
to connect. Are the PC and
server on the same
network? Are they using
the same protocol? Can
the PC ping the server?
(ping serverhostname)
The system has a problem
with the alternate stack.
Word 15
EEEEEEEE
means:
number of adapter
Word 16 (FFFF) of FFFF GG HH

The following SRCs might be displayed for twinaxial consoles.
twinaxial equivalent SRC Description
code
A6005001
A console resource (controller) was not found when the
server was started.
A6005004
A console device was not found when the server was
started. A twinaxial controller was found but cannot be
used. This indicates only the presence of a controller. It
does not indicate that the controller can be defective.
A6005007
A console device was not found when the server was
started. The controller (6A59) was found but the
connection is starting. This can be a problem with the
device or emulator, or the data flow path is not being
established or maintained.
295
Word 16 (GG) of FFFF GG HH

Value
Description
(HEX)
1
Supported, reporting workstation IOA in the tagged IOA location.
2
Reporting communications IOA in the tagged IOA location with at least one
reporting port that supports the async protocol and needed physical interface
3
Supported, reporting LAN IOA in the tagged IOA location, or a LAN port with
the tagged port DRC (used for HEA).
4
HMC console has been configured.
0A
No console IOA tag, no console IOP tag, and no console port DRC tag found,
and HMC console has not been configured.
Note: This is normal for standalone systems since they don't involve tagging.
0B
A physical slot number cannot be determined from the IOA tag.
0C
No reporting IOA in the tagged IOA location.
0D
More than one valid, reporting console IOA in the tagged IOA location. This is
an unexpected error.
0E
A reporting IOA was found at the location specified by the console IOA tag, but
it was NOT a communications IOA, and was not valid for any other kind of
console (i.e. not twinaxial).
The following codes are new at V6R1
0F
An IOP has been tagged for the console, and not an IOA nor an HEA port.
10
Reporting LAN ports were found at the location specified by the console IOA
tag, but the specific LAN port type (CCIN) is not supported for LAN console.
11
A reporting communications IOA is in the tagged IOA location, but it has no
reporting ports.
12
A reporting communications IOA is in the tagged IOA location, but it has no
reporting LAN ports, and no reporting ports that support direct connect
Operations Console (support the async protocol and have the correct physical
interface).
13
No reporting port resource was found with the DRC tag for the console port
resource.
14
A reporting port was found with the DRC tag for the console, but it did not
qualify for use with operations console.
296
Word 16 (HH) of FFFF GG HH

HH = Console type
The console type value is represented by
the last two characters in the form xxxx
yy zz.
00 = Not defined by user (old default
value)
01 = Twinaxial
02 = Operations console(Direct)
03 = Operations Console (LAN )
04 = Hardware Management Console
(HMC) or Thin Console
Note: It is expected that a D-mode IPL with a new load source hard disk drive displays the
console type value of 00. An example of when this can occur is if the copy of data from a failing
hard disk drive does not copy all data or you are installing a new logical partition. Also, there are
times when the hard disk drive is late reporting and the console type value is not retrieved in
time. In these cases, you can use the console service functions (65+21) to set a console type
value or attempt to contact the console again.
Words 17, 18, and 19

The following table defines the Words 17, 18 and 19 values for a local console that is directly
attached.
(JJJJJJJJ)
If Word 17 value is:
00000001
00000002
00000003
00000004
000000FA
Direct cable
Failure
(KKKKKKKK) (LLLLLLLL)
Word 18 means: Word 19 means:
Asynchronous adapter
not detected
No cables detected
Adapter position Adapter type
Wrong cable detected Adapter position
Cable ID
Port in use
Adapter position Adapter type
Not configured for
direct cable
297
Step-by-step analysis
We'll start with the same example data from the beginning of this topic.
Here's a very common SRC we'll work with:
Word 1: A6005008
Word 2: 03D00061
Word 3: 06C00004
Word 4: 00000011
Word 5: C0000000
Word 6: 50070A03
Word 7: 000000FA
Word 8: 00000000
Word 9: 00000000
You normally know the console type you are trying to connect. Let's start with that. The
console type is located in word 16 (FFFF GG HH) so the data Word 6: 50070A03 means that
our example system's problem is with LAN console. Of course if you got this value and you
were trying to use another console type you know this is the problem. If that's true, assuming
you don't have another device to use, you would use the console service functions (65+21) to set
the correct console type. For this example a value of 03 (Operations Console (LAN)) is correct.
The next piece of data of concern is the tag information, also in word 16 (FFFF GG HH), shows
a value of Word 6: 50070A03. From the appropriate table you can see that it means:
0A
No console IOA tag, no console IOP tag, and no console port DRC tag found,
and HMC console has not been configured.
Note: This is normal for standalone systems since they don't involve tagging.
So if this was representing a single partitioned 9406-520 then this isn't the problem. However, if
this represented a different value, such as 0A you see the console is incorrectly tagged.
0C
No reporting IOA in the tagged IOA location.
For this example, the data is correct so we'll move on.

Note:
We already know that this is a local console on a network (LAN) so the only data left that is
relevant is in words 13, 14 and 15. Words 17, 18 and 19 have no bearing, which is further
represented with:
Word 7: 000000FA
000000FA
Not configured for

direct cable
298
Another possible problem affecting a Power-processor-based system not managed by an HMC

is, as in our example system, whether the LAN flags are correct. If we are trying to use the
embedded port for the console the embedded port flag must be turned on. The data:
Word 3: 06C00004
V5R4M5 and later (our example system)
Reason codes as AA BB in the 5008 SRC code AABBCCCC:
A
0
0
0
0
0
0
E
E
F

Embedded flag is on
flag.
processor-based
The only part of the table we're concerned with is AA. The value in BB isn't used for a network
attached console. If you look under AA you see that both the embedded port and the external
port flags are on. This is the default value from manufacturing. Since the embedded port is on,
the external flag isn't considered. So this is good also.
If the data had indicated a 00 or 01 then the system wouldn't be able to use the embedded port.
In this case you'd have to use the console service functions (65+21) to set the correct flags.
Another scenario might be that AA had a value of E0 which would indicate an intent to use an
external 1 GB Ethernet adapter such as the 5706 but the adapter location has not been selected
yet.
299
That only leaves the reason code in word 13.

Word 3: 06C00004
Word 4: 00000011
Word 5: C0000000
(AA BB CCCC)
If Word 13
value (n) is:
0004
Failure
BOOTP status:
If attempts are zero,
then BOOTP is ready
when called.
If attempts have a
value, then the PC did
not respond.
Word 14
DDDDDDDD
means:
Attempts
Word 15
EEEEEEEE
means:
Adapter position or
serial number of adapter
Word 14 has a value so the data is indicating BOOTP was taking place at the time the SRC was
issued. There are numerous reasons for this condition:

The system serial number might be in error when you created the configured connection.
Delete and recreate the configured connection.
The partition number might be in error when you created the configured connection.
Delete and recreate the configured connection.
The system and PC aren't connected to the system in a way that broadcast packets sent by
the system can be detected by the PC.
Either connect the PC or system to the same hub, router or switch, or configure the
network device to pass broadcast packets.
If you are setting up a Power6 processor-based blade check that you have bridging
properly enabled in VIOS/IVM on page 96.
Word 15 is rarely used when the system is using V5R4M5 or later of Licensed Internal Code
since the system uses the UID (Universal Identifier) of the adapter to find the resource and for
the embedded there is no card slot so this data often contains just the C0000000 to indicate no
slot number. Also, there are conditions in which a location or adapter serial (or UID) cannot be
determined so you may see just 00000000.
300
D1008065 after attempting to activate the asynchronous

communications adapter
This system reference code is used primarily to debug a failure to activate the asynchronous
adapter for a console directly attached or remote service. However, it can be useful in getting
information, such as the LAN flags/adapter without the need to see a SRC of A6005008.
Note: The same data is also represented when the system posts an SRC D1008066.
The words of data are represented differently depending on how you accessed the data. In our
example you see words 1 thru 9 which would correspond to functions 11 thru 19 on older
physical control panels or the RCP/VCP. For more help in determining this data see display the
system reference code (SRC) detail on page 211.
Here is an example:
Word 1: D1008065
Word 2: 0D200060
Word 3: 06C41015
Word 4: 00000006
Word 5: 00000001
Word 6: 0000000F
Word 7: 00000001
Word 8: 00000001
Word 9: Not returned or used for this function
301
Data broken out into significant pieces:

Click the link in the data areas to go to the appropriate table of details.
Word
Data
Significant
Data
D1008065
Base SRC
Not used
Significant
Data
Significant
Data
11
D1008065
12
0D200060
13
06C41015
06
AA
LAN flag
C4
BB
Assigned
direct connect
location
10 15
CC DD
CC = IOP state
DD=Reason code for
failure on activation
14
00000006
15
00000001
16
0000000F
17
18
19
00000001
00000001
00000006
EEEEEEEE
initialization return
code
00000001
FFFFFFFF
activation return code
0000000F
GGGGGGGG
cable ID
Not used
Not used
Not returned or used
302
Word 13
Word 13 values for the AABBCCDD status indicators display differently depending on the
system's code level and whether or not you have installed PTF MF39303 (V5R3M5) or PTF
MF39304 (V5R4M0). Values AABB only display on systems that are not managed by a
Hardware Management Console (HMC) so the expected values are 0000 or FFFF.
Note: References to the RVX port means the port in which you would attach the console cable
or an external modem.
V5R3/V5R4 Without PTF MF39303 (V5R3M5) or PTF MF39304 (V5R4M0)
If Word 13
value is:
Without PTF
MF39303
(V5R3M5) or
PTF MF39304
(V5R4M0)
AA means:
E1 - Allows the
internal
embedded
adapter.
00 - No support
for the internal
embedded
adapter.
BB means:
CC means:
DD means:
E2 - Allows the
external adapter.
00 - No support
for the external
adapter.
10 - IOP RVX
port
20 - IOP internal
modem
30 - IOPless
RVX port
40 - IOPless
internal modem
FF - No
supported
resource or port
was found
00 - Received OK
status from
modem
01 - CTS time
out
02 - Received
Connect status
from PC client
03 - Stop request
07 - Received
function 66 while
active
08 - Failed to
find port
16 - Port not
found
303
V5R3/V5R4 With PTF MF39303 (V5R3M5) or PTF MF39304 (V5R4M0)

If Word 13
value is:
With PTF
MF39303
(V5R3M5) or
PTF MF39304
(V5R4M0)
AA means:
BB means:
CC means:
DD means:
E0 - System is
upgraded from
V5R3 and
support for the 1
GB Ethernet
adapter is not set.
E1 - Disabled.
Both the internal
embedded
adapter and
external adapters
are not being
searched for.
E2 - Allows the
internal
embedded
adapter.
E4 - Allows the
external adapter.
E6 - Allows both
internal
embedded
adapter and
external adapter.
C2, C3, or C4 Location of

selected
asynchronous
adapter used for
console, ECS,
and remote
service.
Important: If
you have a
system that was
shipped with
Licensed Internal
Code (LIC) prior
to V5R4M5, you
cannot select slot
C4 for use with
the console when
using the 2793,
but you can select
slot C4 for use
with ECS and
remote service.
10 - IOP RVX
port
20 - IOP internal
modem
30 - IOPless
RVX port
40 - IOPless
internal modem
FF - No
supported
resource was
found
00 - Received OK
status from
modem
01 - CTS time
out
02 - Received
Connect status
from PC client
03 - Stop request
07 - Received
function 66 while
active
08 - Failed to
find port
16 - Port not
found
Example: With PTF

MF39303 (V5R3M5)
or PTF MF39304
(V5R4M0)
E6C210002 (AABBCCDD) = Allows for the internal

embedded adapter and the asynchronous adapter. The
asynchronous adapter is located in slot C2, which is running
with IOP support, can be used for console, ECS, and remote
service. The system is directly connected and is communicating with
the PC.
304
V5R4M5 and later

Reason codes as AA BB in the D1008065 SRC code AABBCCDD:
A
0
0
0
0
0
0
E
E
F

Embedded flag is on
flag.
processor-based

CC means:
Word 13 values for
the AABBCCDD
status indicators
With PTF MF39303 10 - IOP RVX port
(V5R3M5) or PTF
20 - IOP internal modem
MF39304 (V5R4M0) 30 - IOPless RVX port
40 - IOPless internal
modem
FF - No supported resource
was found
DD means:
00 - Received OK status from modem

01 - CTS time out
02 - Received Connect status from
PC client
03 - Stop request
07 - Received function 66 while active
08 - Failed to find port
16 - Port not found
Note: Only the most common values for DD are documented here. If you have a value other
than what is provided, contact your service provider.
305
Words 14 (EEEEEEEE) and 15 (FFFFFFFF)

Word 14 contains the reason an SRC of D1008065 is returned. A successful activation usually
occurs when the console type value is set to Operations console(Direct), value of 02. All zeros for
word 14 indicate the server was able to activate the asynchronous communications adapter but
the resulting failure SRC was issued because the system was unable to detect the correct
condition on the cable. The most common reason for this is that the serial port on the PC is in an
unexpected state. Powering off the PC and then powering it back on might clear this condition.
An unstable Client Access installation might also cause this condition. Try uninstalling and then
reinstalling Client Access, and removing the Operations Console connection modem, and
reinstalling it might correct this condition.
(EEEEEEEE)
00000000
00000001
00000002
00000004
(FFFFFFFF)
CC100301
CC10031A
Word 14 means:
Successful activation
Port not found
No cable attached
Activation failed (see word 15)
Word 15 means:
Resource might be in use
Cable mismatch or country code not set (Use CHGNETA to set
country code, if needed.)
Note: Only the most common values are documented here. If you have a value other than what
is provided, contact your service provider.
Word 16
Word 16 contains the cable ID which is expected to be 00000006. Another value or 00000000
might indicate a wrong cable or no cable at all. Don't assume that a value of 00000000 is no
cable since some asynchronous communications adapters can provide a value here even when no
cable is attached.
306
SRC A9002000
The console creation fails in i5/OS.
These are some possible reasons you might receive system reference code (SRC) A9002000:
The console was not found by i5/OS.
The server value QAUTOCFG must be set to ON. Use one of the following to verify or
set this system value on the server:
During a manual IPL, in the IPL Options window, for Set major system options,
select Y. Then for Enable automatic configuration, select Y.
If you just migrated the console from one type to another and the new console fails to
work in i5/OS, you might need to use another workstation to manually delete the
controller and device description associated with the old console device.
Note: You might be able to use the console service functions (65+21), on page 232 to assist
in a recovery or gathering resolution data.
SRC A6005082
This system reference code (SRC) occurs during a manual initial program load (IPL) when
the system obtains a console, but the console closes.
Note: The console type does not affect this SRC.
These are some possible reasons why you might receive SRC A6005082:
1. If you IPL the server to DST and then close the emulator, disconnect the console, or
close Operations Console after the console is found.
2. If a console is found, but then the server loses the console connection.
This SRC disappears if the console is reassigned and the server can locate a console.
307
Failure to display D1008065 and D1008066 automatically

after calling the function
When working with servers that have a double row for the Function/Data window, after
calling the function 65 or 66, the control panel might not automatically display the resulting
system reference code.
In these cases, you must do a function 11 to determine whether the function 65 or 66
completed successfully. If you were doing an activation (66) and the function did not
complete successfully, see D1008065.
Note: This pertains only to those servers without a Hardware Management Console.
1. Using the control panel or the remote control panel, press the Up or Down buttons
until 11 is displayed.
2. Press Enter.
For more information, see Reference codes list for customers.
http://publib.boulder.ibm.com/infocenter/systems/topic/ipha5/referencecodes.htm
Startup step C6004508 takes longer than expected in Dmode IPL

This can be the result of a problem or configuration change. If you are troubleshooting a
connection issue, you can force the system to end the search for the console by performing a
function 21 (enable DST) from the control panel, remote control panel, or Hardware
Management Console. This speeds the process of posting a failing system reference code
(SRC) without waiting the entire search time, which can be 45 minutes or longer. Allow the
system to attempt to find the console for five or 10 minutes before circumventing the step
unless you expect a failure to occur and only need to retrieve the SRC data.
Important: Use care when considering this bypass function. Bypassing the remaining time
in the process of the search might prevent a correctly working console from being activated
in some cases.
308
Troubleshooting configuration wizard problems

Local console does not detect console cable
Here are some solutions to problems that occur when the local console does not detect
the presence of the Operations Console cable.
If this problem exists, a status message of Connecting or Unavailable is usually present or
the port detection in the setup wizard fails.
Verify that the cable is connected correctly. For more information on cable
installation, see Installing an Operations Console cable.
For the console, verify that the asynchronous communications adapter on the
server is located correctly.
Verify that the part number for the Operations Console cable is correct.
Verify that the server is in a state such that the console is active. For example, the
console is active after the server is started. After you start the server, the system
reference codes (SRCs) C6004031, C6004508, or A600500x (where is a number)
indicate that the server is in the correct state.
Verify that the PC resources 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:
Direct 192.168.0.0 255.255.255.0

Note: Use the Operations Console Properties window to change the IP base
address from 192.168.0.2. For example, you can use 192.168.1.2.
Old network data interferes with reconfiguration of network

connectivity
Here are some possible solutions to try if your local console on a network (LAN)
configuration continues to get an old IP address.
If you are configuring a local console on a network (LAN) and you continue to get an old IP
address, which might be wrong but you cannot get to it without changing the name, you
might need to edit the hosts file on the PC to remove the entry in question.
1. Remove or alter the old entry in the hosts file on the PC. You can do a search for
hosts and then use a text editor to edit the file.
2. Close and restart Operations Console before attempting to connect a new
configuration. This action removes all cached values associated with any old
configurations.
309
Troubleshooting remote and virtual control panel

problems
Remote control panel fails to start
If you are connecting over a network, the RCP might fail to start when either the user ID
or service tools device ID being used does not have permission to use the RCP.
Virtual control panel fails to start

If the VCP fails to start, do the following:
1. Verify that the cables are correctly connected. For more information, see
Installing a console cable.
2. Verify that the resources of the PC are free of address or interrupt request (IRQ)
conflicts. The 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 as follows:
Direct 192.168.0.0 255.255.255.0

Unable to use the mode function

If you are unable to use the mode function on a RCP or VCP, check that the user that
authenticated the connection (Service Device Sign-on) has the Partition remote panel key
privilege for the logical partition to which they are connected. To verify the privilege
setting, do the following:
devices.
Remember: You must unlock the SST option before you can use it. For
instructions, see unlock service tools device IDs in SST on page 248.
2. Select Change privileges.
That user must be granted this privilege, by logical partition, to use the mode function.
Also, if the system supports the keystick, the keystick must be inserted before the mode
function is active.
310
Virtual control panel authentication errors

Problem: The current access password entered is not valid. Please enter the valid access
password.
Solution: This message typically means that the access password that you entered in
the Service Device Sign-on window is not the same as the password that you entered
in the Specify Access Password window during the configuration wizard. Ensure that
the Caps Lock key is not active, and then re-enter the access password using the
password that you assigned. Passwords are case sensitive.
Problem: The PC service tools device password and the service tools device password
do not match. Either the service tools device ID <name> is already in use or the
passwords must be RESET on this PC and the server.
Solution: This indicates that the Service Tools Device ID password might be
incorrect. If this is the case, then the Service Device ID password stored on the PC no
longer matches the value stored on the server. The password assigned to the Service
Device ID during the configuration wizard on the PC must match the password
assigned to the service device ID on server. If you used the QCONSOLE device ID,
then both the PC and server must have the password set to QCONSOLE. Each time
that you authenticate successfully, this password is re-encrypted to a new value and
stored on both sides of the connection. In rare situations, this password does not
synchronize, so you need to reset the value back to the original default values on both
the PC and the server. For instructions, see resynchronize the PC and service tools
device ID password on page 242.
Troubleshooting other Operations Console problems

Changing console tags without an IPL
If you have a problem with Operations Console on a server or partition that is managed
by a Hardware Management Console (HMC), you can change the tags without requiring
an IPL. This procedure might be needed to change console types to work around a
problem or to just change which resource to use for the console if the console type is not
changing, such as when an adapter fails and it cannot be replaced immediately. You must
use the HMC command interface.
To change Operations Console tags without performing an IPL, see Completing a
console change with the logical partition and managed system powered on on page 119.
311
Operations Console remains in QCTL

This situation is usually present after a migration, but can be found any time you are
working with system resources. QCONSOLE still remains in QCTL when you might
expect it to be reassigned as another workstation.
Verify that the system is not starting with DEBUG turned on. A good indication is that
no other interactive subsystem is starting, if present, and others might also be absent.
Check to see that SYSVAL QIPLTYPE is set to 0.
Note: If the new console fails to work in i5/OS, you might need to use another
workstation to manually delete the controller and device description associated with the
old console device.
Error message: The user can not perform the option

selected
If you are working with a local console on a network (LAN) configuration and attempted to
access the Service tools device IDs option on the Work With Service Tools User IDs and
Devices window within SST, it posts the message, The user can not perform the option
selected. This error indicates that the option is not unlocked yet. To unlock the option, see
Unable to sign on because of a lost or expired password or

disabled user ID
If you have the special DST Sign-on window but are unable to sign on because of either
a disabled user ID or expired password, you can attempt recovery by doing the
following:
Verify that no other devices (PCs) that typically are eligible to become the
console are connected.
Perform the console service functions (65+21) using 65, 21, 21.
This action causes the console to be lost temporarily. The device then becomes the
console with a sign-on window appropriate to the system state, assuming that it matches
the current console type setting. For example, if you IPL the system to the command line,
then you see the i5/OS Sign-on window. You can then sign on using any user ID with
the authority to continue the recovery of the DST user ID that has the problem.
312
Troubleshooting console changes

Here are some possible solutions to problems that you might experience with your new console.
Troubleshooting the new console when the system is managed by an HMC directly
below
Read about some possible solutions to problems that you might experience when you
change consoles and the system is managed by a Hardware Management Console
(HMC).
Troubleshooting the new console when the system is not managed by an HMC on page
314.
Read about some possible solutions to problems that you might experience when you
change consoles and the system is not managed by a Hardware Management Console
(HMC).
Troubleshooting the new console when the system is

managed by an HMC
When your system is managed by an HMC, you can attempt to resolve the connection
problem.
Verify that the console adapter is correctly tagged in the partition profile, or
specified if you used the HMC command prompt, to dynamically change the tag.
For Operations Console (Direct), the Operations Console tag must also be set to the
same resource as the Console tag.
Verify that the console device is powered on and connected correctly.
For Operations Console (LAN), verify that the PC is active on the network.
If you did not configure the service host name using your previous console,
BOOTP is used to configure the system. For more information, see Bootstrap
Protocol on page 318.
Verify that you entered the system serial number correctly.
Verify that you specified the correct partition ID.
Important: Power-processor-based models start counting logical
partitions with the number 1 (even if it is the only partition) instead of a 0.
For the console to connect correctly, your logical partitions must also
begin numbering at 1 instead of 0. This is especially true if you rely on the
BOOTP process to configure the server with its network data.
Ensure that your network passes BOOTP requests.
For Operations Console (Direct), verify that the cable is plugged into the correct
serial port on the PC and server.
For a configured twinaxial console, the device must be on port 0 with an address
of 0.
313
For a configured twinaxial console, verify that the cursor is in the upper-left
corner of the display. This indicates that the device is communicating with the
controller correctly.
If the cursor is in the upper-right corner, the device and controller are not
communicating. You might have a defective adapter, the adapter might have to be
reseated in the slot, or the controller is not varied on.
When changing from or to a twinaxial console and the partition has completed an
IPL, an additional IPL is required to complete the console change.
Troubleshooting the new console when the system is not

managed by an HMC
If your system is not managed by an HMC, you can attempt to resolve the connection
problem.
Verify that the adapter used by the console is located correctly. The adapter that
is used for the console must be located in a particular location based on the
model. For more information, see Chapter 1 Reference on page 19.
Verify that the console device is powered on and connected correctly.
For Operations Console (LAN), verify that the PC is active on the network.
If you did not configure the service host name using your previous console,
BOOTP is used to configure the system. For more information regarding
BOOTP, see Bootstrap Protocol on page 318.
Verify that you entered the system serial number correctly.
Verify that you specified the correct partition ID.
Important: Power-processor-based models start counting logical
partitions with the number 1 (even if it is the only partition) instead of a 0.
For the console to connect properly, your logical partitions must also
begin numbering at 1 instead of 0. This is especially true if you rely on the
Ensure that your network infrastructure passes BOOTP requests.
For Operations Console (Direct), verify that the cable is plugged into the correct
serial port on the PC and server.
For a configured twinaxial console, the device must be on port 0 with an address
of 0.
314
For a configured twinaxial console, verify that the cursor is in the upper-left
corner of the display. This indicates the device is communicating with the
controller correctly.
If the cursor is in the upper-right corner, the device and controller are not
communicating. You might have a defective adapter, the adapter might have to be
reseated in the slot, or the controller is not varied on.
When changing from or to a twinaxial console and the partition has completed an
IPL, an additional IPL is required to complete the console change.
315
Filler page
316
Appendix C. Operations Console Networking

If you are not using the default embedded Ethernet port as the default console port, you need to
install the LAN adapter for Operations Console according to your server model. To do this, see
Chapter 1 Reference on page 19.
If your server is new and you ordered a local console on a network (LAN), the adapter should
already be configured with the server. The LAN adapter may need to be dedicated for service
tools.
You might want to treat the console over a LAN connection with the same physical security
considerations and controls as a local console that is directly attached or a twinaxial console. For
example, consider configuring a local console on a network (LAN) in a network that is separate
from the main network (or the company intranet) and strictly control access to the machine
acting as the console.
It is suggested that you restrict LAN topologies for LAN-attached local consoles to a single,
physical ring, hub, switch, or router environment. In the event that the local console on a
network is used in a larger network topology, it is suggested that you use broadcast (DHCP)
packet filtering. This might be as simple as connecting the PC and system using an inexpensive
hub or router. Temporarily, you could also use an Ethernet crossover cable (when using a 2849
adapter). When you have only a single PC or a small number of devices connected to the system
using a hub, and these devices do not connect to another network or the Internet, you can then
use any numeric numbers for addresses, for example, 1.1.1.x or 10.220.215.x (where x can be 2
through 255, but avoid x.x.x.1, which might cause problems in some hubs). However, if you
have a network that many users share, or in which the devices are connected to the Internet, then
you should consult a network administrator for addresses.
Temporarily, you could also use an Ethernet crossover cable (when using a 2849) or any
Ethernet cable if you are using a 1 GHz network adapter such as the Host Ethernet Adapter,
5767/5768, or 5706/5707. When you have only a single PC or small number of devices
connected to the server using a router, switch, or hub, and these devices do not connect to
another network or the Internet, you can then use any numeric numbers for addresses. For
example, use 1.1.1.x or 10.220.215.x (where x can be 2 through 255, but avoid x.x.x.1, which
might cause problems in some networks).
A crossover cable is a standard network cable that has the transmit and receive signal wires
reversed. This virtually allows each end to act as if a hub, switch, or router were between them.
The use of a crossover cable might also require a nonstandard network configuration at the
system and PC.
317
Bootstrap Protocol
Although the system and PC can still perform a standard BOOTP operation as described here,
i5/OS Version 6 Release 1 enables the automatic discovery of a connection between the system
and a PC. This function, called VSDISCOVER, is a mechanism used solely for Operations
Console. Both the system and PC listen for a special broadcast frame from the network and
when received, there is a negotiation using ports 67 and 68, and the system and PC can use the
data exchanged to configure itself, if needed. In addition, the PC creates a configured connection
that you can use to start a console session. This VSDISCOVER function is the default
mechanism for configuring a connection. The BOOTP process is still used when VSDISCOVER
is not necessary, such as when you already have a configured connection and the network data
needs to be reset.
A local Operations Console on a network uses the Bootstrap Protocol (BOOTP) to configure the
server service IP communications stack. The IP stack configuration, plus server serial number
and partition ID, is requested in the Operations Console configuration wizard. The server
broadcasts a BOOTP request. The Operations Console PC replies with the information submitted
during the configuration wizard. The server then stores and uses the configuration information
for the service IP communications stack.
The system will perform a BOOTP when the console type is set to Operations console(LAN) and
the system does not contain a valid IP address for the service host name (service interface).
The Operations Console PC must be placed on a network that is accessible by the server. This
can be the same physical network or a network that permits broadcast packets to flow. This is an
initial setup requirement; typical Operations Console operation does not require this. This setup
should occur on the same physical network.
The BOOTP request carries the server serial number and partition ID. The server serial number
and partition ID are used to assign the IP configuration information.
If you are having problems configuring the service IP communications stack, check that the
Operations Console PC is on the same physical network and the server serial number and
partition ID are correct in the configuration.
Important: Power-processor-based models start counting logical partitions with the number 1
(even if it is the only partition) instead of a 0. For the console to connect correctly, your logical
partitions must also begin numbering at 1 instead of 0. This is especially true if you rely on the
A local console on a network (LAN) uses ports 2323, 3001, and 3002. To use Operations Console in
a different physical network, the router and firewall must allow IP traffic on these ports. BOOTP
uses UDP ports 67 and 68 per RFC 951. For more information, see
http://www.faqs.org/rfcs/rfc951.html.
318
The success of BOOTP is dependent on the network hardware used to connect the server and the
PC. In some cases, you might need a different console device to configure the connection in
DST. To use BOOTP, the network hardware used must be capable of auto-negotiation of speed
and duplex if using the 2838 Ethernet adapter for the Operations Console connection.
Additional considerations for a system connected to an

HMC
Networking security considerations are different when your system is managed by a Hardware
Management Console (HMC) because your network and network security are configured
differently. When you set up your HMC, determine whether you want to configure a private or
open network.
If it is the first HMC in your network, configure that HMC as a DHCP server. For more
information, see Types of HMC network connections.
http://publib.boulder.ibm.com/infocenter/systems/topic/iphai/connectingthehmctoanetwork.htm
and
Preparing for HMC configuration.
http://publib.boulder.ibm.com/infocenter/systems/topic/iphai/prep.htm
319
Filler page
320
Appendix D. System Locations for Cards &

Cables
See the figure that applies to your server.
Model 170(250) Operations Console ports - A=C08 port
321
Server 270 Operations Console ports.
322
Model 720 Operations Console ports
323
324
325
Model 800/810
326
Model 820
327
Model 825
328
Model 830/SB2
329
Model 840/SB3
330
Model 870/890
331
Models 9405-520, 9406-520, 9406-525, or 9407-515 with the integrated HSL/RIO ports (T3/T4)
332
333
Back views of a model 9405-520, 9406-520, 9406-525, or 9407-515 without the integrated HSL
ports (T3/T4)
334
335
9406-550
9406-570
336
9407-M15-520 and 9408-M25-520
337
9409-M50-550
338
9406-MMA-570
339
Filler page
340
Appendix E. Backup Consoles

To quickly recover from the unexpected loss of the console, you might want to consider a
backup console. Many system plans include a level of redundancy to allow for hardware failures,
but some do not consider the console in those plans.
Here are some suggestions for planning for a backup console to manage i5/OS:
Considerations for a backup console

General considerations
If you access your system remotely, consider off-site console capability or another
type of connectivity for the console. A local console on a network can be backed up
with an additional local console on a network PC. If the network adapter were to fail,
consider a Local console directly attached to the system as a backup.
In a logical partition or multiple-system environment, you will most likely be using
multiple local consoles on a network (LAN) configuration on a single PC as your
primary consoles. Consider additional PCs using this same type configuration. Avoid
supporting too many consoles on the same PC if possible. The PC resources can be
easily overwhelmed when supporting multiple consoles and remote control panels.
Consider multiple local console on a network configurations in large environments so
that each PC has a core set of console responsibilities and the overlap coverage of
backup configurations with each other. For example, if you have a PC that supports
10 local consoles on a network configuration and another PC with the same number
of primary consoles for another 10 partitions, instead of backing up each PC with the
other's configuration, you add a third PC and spread the 20 consoles out so that two
PCs back up a portion of each PC's primary console configurations. Another
consideration is a dedicated PC to be the backup of a certain number of consoles, but
not connected until necessary.
When you mostly use consoles on a network, consider setting up a Local console
directly attached to the system on a PC and place it on a rollaway cart with a console
cable. If you have supporting adapters, you can quickly roll the cart with the PC near
the system or partition in need of the console. After connecting the cable and
changing the console type value, you have a console to replace the currently failed
console. This same concept also applies to twinaxial workstations.
341
Note: If more than one local console on a network is planned, be certain to create
additional service tools device IDs on the system before you start configuring the
Operations Console PC unless both the system and the PC client are using V6R1.
Each PC connecting to the same target system or logical partition must have a unique
service tools device ID. With V6R1, new function will autocreate service tools
device IDs by default.
Non-partitioned considerations
The adapter location for Operations Console or a twinaxial console is fixed, or at

least limited for some non-partitioned systems. Based on your system's hardware
requirements you might have limited console choices for i5/OS. Try to accommodate
at least one additional console type, if possible.
Consider using the takeover and recovery function as part of your i5/OS backup
console strategy. However, the hardware used for the Operations Console or
twinaxial console must be installed prior to the recovery. For more information on
the general Operations Console consideration, see Chapter 2: Considerations for
planning on page 59.
Partitioned considerations
Alternate console refers to a twinaxial console resource tagged as the alternate

console when the console is also a twinaxial console. An alternate console gives you
an added layer of protection because if the system detects a failure of the primary
console during an attended mode initial program load (IPL), it automatically tries the
alternate console. Tagging the same resource as both the console and the alternate
console can result in an inability to select a console at all. Consider specifying the
alternate console by tagging an input/output adapter (IOA) on a different bus in case
you develop a bus-related problem. The alternate console cannot become the system
console.
Models 8xx are tagged for a console type only at the IOP level. Tagging an IOP that
has two similar console adapters reporting to it (for example, two 2849s or two
2771s) for the same IOP can sometimes make it difficult to determine, in advance,
which adapter will be used for the console. When tagging the IOP, make sure that it
only has one console-capable adapter per connectivity (for example, only one 2849
and one 2771). Each adapter can support a different console type but only one
adapter type should be present. The lowest addressed adapter on the bus is attempted
first. But if that adapter is slow in reporting to the system, another adapter might get
selected instead, when two adapters of the same connectivity are present. 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.
342
Systems using a Hardware Management Console (HMC), Power-processor-based

systems only, enable you to tag a specific IOA as the console device. For more
information, see Chapter 2: Considerations for planning on page 59.
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.
On large multi-partitioned systems or high-availability systems, use Operations Console (LAN)

as the system console for each system or partition. In the event of a console failure, you can
switch to the HMC 5250 console without having to verify you have additional hardware in
place. Most changes of a console to HMC are performed without the need for an IPL.
Verify your system is ready for a backup console

Recovering from the loss of a console depends on many factors, some of which include the
model, the hardware resources available, the previous console type, and the intended console
type. Recovery might consist of repairing the currently failed console or temporarily replacing it
with another console type. Most changes of a console type can be performed without the need
for an IPL, but there might be circumstances in which an IPL is necessary. Before you use the
console service functions (65+21), verify the following:
For systems without an HMC, verify that the console hardware is installed and available.
For systems with an HMC, verify that the appropriate console resources are tagged in the
partition profile.
Important: If you plan to use a local console on a network (LAN) as a backup for another console
type, the network adapter must be located in a slot designated for a console or the IOA is tagged
correctly. If not previously configured, you can use BOOTP to configure the server. For more
information on BOOTP, see Operations Console networking on page 317 and create or verify a
Redundancy in backup console configurations

It is important to consider as much redundancy as possible for your console needs. If you
consider "what if this fails?" and you have another method to provide a console, and also make
compromises for the hardware requirements necessary to overcome the various levels where a
failure might occur, you are reducing your exposure to an unrecoverable console failure
condition.
343
Several backup console configurations can fit your environment. The following table lists
possible solutions.
If...
Possible backup
console
configurations
If your server is
accessed remotely...
If your system is
configured with an
HMC, but you are
running Operations
Console...
If you are using
multiple local
consoles on a
network (LAN) on a
single PC...
If you are using

multiple local
consoles on a
network (LAN) on
multiple PCs...
Then...
consider an off-site console capability or another connectivity for the

console. A local console on a network (LAN) can be backed up with
additional local console on a network (LAN) PCs. If the network
adapter were to fail, consider a local console that is directly
attached as a backup console.
you can quickly switch to the HMC 5250 console if Operations
Console fails, without having to change hardware.
Remember: You must configure each console separately.
consider additional PCs using this same type of configuration.

Important: The PC resources can become overwhelmed when
supporting multiple consoles and remote control panels.
consider setting up a local console that is directly attached on a
PC and place it on a roll-away cart with a console cable. If you
have supporting adapters, you can quickly roll the cart with the
PC near the server or logical partition in need of the console.
After connecting the cable and changing the console type
value, you have a console to replace the currently failed
console. This same concept can be implemented for twinaxial
workstations.
consider assigning each PC a core set of console
responsibilities and then overlap coverage of backup
configurations with each other. For example, if you have a PC
that supports 10 local consoles on a network (LAN) and
another PC with the same number of primary consoles for
another 10 logical partitions, instead of backing up each PC
with the other's configuration, you add a third PC and
distribute the 20 consoles so that two PCs back up a portion of
each PC's primary console configurations.
consider having a dedicated PC to be the backup of a certain
number of consoles, but not connect it until necessary.
344
Note: If more than one local console on a network (LAN) is planned, you no longer need to create
additional service tools device IDs on the server before you start configuring the Operations
Console PC if both the client PC and system are using V6R1. Each PC connecting to the same
target server or logical partition must have a unique service tools device ID and will be given an
autocreated service tools device ID upon connecting.
For more information about the ability to switch between console devices, see Switching from
one console type to another when a console is currently available on page 223.
In summary, consider incorporating as much redundancy as possible into your console
configuration. You can reduce your exposure to a catastrophic console failure by using another
method to provide a console in place, or by making compromises and adjustments for the
various hardware requirements necessary to overcome the various levels of failures.
345
Filler page
346
Appendix F. Private Network Setup

You don't need a lot of expensive equipment to take advantage of Operations Console (LAN). It
can be as simple as a single Ethernet cable connected between the PC and the system. You can
make it more flexible by adding an inexpensive hub.
First, a word about the cable if you only connect the system and PC. A crossover cable is a
standard network cable that has the transmit and receive signal wires reversed.
If you have non-1Ghz adapters, you may have to use a crossover cable. However, if you use an
adapter or network resource such as 5706/5707, 5767/5768, or the IVE (HEA), then the adapter
itself will detect if you use a standard Ethernet cable or an Ethernet crossover cable.
Using this method to create a private network will require some non-standard configurations.
There are examples on the internet but these steps will also accomplish the task. The use of a
non-routable address, such as 192.168.n.n or 10.n.n.n (where n is any number from 1 to 255) is
recommended, but you could use addresses comparable to your business network to temporarily
set up the connection and then later you can migrate from a single cable to your network. If you
make the PC your network gateway you minimize the amount of work should you use real
network addresses and migrate later.
Note: Microsoft defaults an Ethernet adapter to obtain the IP address automatically, implying
that there will be a DHCP server on the network. If the PC is placed on a network that does not
have a DHCP server the default address will in the range of 169.254.?.?. If you connect the
Ethernet cable directly from the PC to the system you'll need to know what the PC address is
before you create the configuration in Operations Console so that you specify an address for the
system to use that can actually connect to the PC.
Let's get some formalities out of the way. These instructions assume your system already has
supporting hardware, either in it's proper location for primary partitions or non-partitioned
systems.
If the intended system or partition is a logical partition, or is HMC managed, then the supporting
resource has to have been tagged correctly. Also, the connection between the system and the PC
must already exist, even if there is a hub or other network device used to satisfy your Ethernet
network.
347
These instructions represent Windows XP and are intended to be a guideline for any other
supported Windows operating system.
Follow these steps to set up a direct connection between the system and PC:
1. If you already have a console or another workstation, use the following steps to either verify
or create the configuration for the service connection. You can do this during a migration or
an upgrade before disconnecting your old console.
Note: You might have to temporarily change the console type to complete this task. You can
also use any option pertaining to the service tools LAN adapter to verify the service host
name or data.
If you are using DST, select Work with DST environment, and then System devices.
b. Select Select Console.
c. Select Operations console(LAN) and press Enter. This displays Verify Operations Console
Adapters.
d. Press F11 to configure.
e. The service host name (interface name) field contains the name.
If you are creating a new service connection, follow these steps:
i. Enter the network data in the appropriate fields.
Use the following example data to complete the system configuration:
Internet address:
10.10.10.10
Primary router address:
Subnet mask:
Host name for service tools:
10.10.10.1
255.255.255.0
<See note>
Note: This name can be anything you want to refer to the system on the
network or a name you plan to use after later migrating to your business
network, if you plan to do this.
ii. Store your configuration by pressing F7.
iii. Activate the LAN adapter by pressing F14.
iv. Press F3 to exit.
v. If you changed the console to a local console on a network (LAN) in step 2, reselect the original console.
Your system is now configured and ready for a connection.
vi. Continue with step 3.
348
2. If you are setting up a new system using Operations Console (LAN), the LAN adapter has to be
installed and the correct console type specified. When working through the Operations
Console configuration wizard, you must supply the connection name, as well as the network
parameters. During the initial connection, this data finishes the server configuration for the
network.
If the system and client PC are both using V6R1 code then Operations Console will first
attempt to detect the system using VSDISCOVER. If that fails to detect the system then the
connection will attempt to use BOOTP to configure the server. For more information see
Bootstrap Protocol on page 318.
3. To configure the PC, do one of the following set of steps:
Configure the PC to use a static address, do the following:
a. Click Start > Settings > Control Panel > Network Connections.
Note: You should have a network connection available for the Ethernet adapter
installed in your PC. If you do not find one you need to install or repair a network
adapter.
b. Right-click on the Local Area Network object and select Properties. This should open
the Local Area Connection Properties window.
c. Select Internet Protocol (TCP/IP), then select Properties. This should open the Internet
Protocol (TCP/IP) Properties window.
The following example data should correspond to the data you used for the system.
d. Select Use the following IP address.
e. Enter 10.10.10.1 for the IP address field.
f. Enter 255.255.255.0 for the Subnet mask field.
g. Enter 10.10.10.1 for the Default gateway field.
h. Click OK twice and close any other windows you opened to perform this
configuration.
If you want to let Windows assign an address for the PC, do the following:
a. Click Start > Settings > Control Panel > Network Connections.
Note: You should have a network connection available for the Ethernet adapter
installed in your PC. If you do not find one you need to install or repair a network
adapter.
b. Right-click on the Local Area Network object and select Properties. This should open
the Local Area Connection Properties window.
c. Select Internet Protocol (TCP/IP), then select Properties. This should open the Internet
Protocol (TCP/IP) Properties window.
d. Verify the option Obtain an IP address automatically is selected.
e. Exit Properties and close any window you don't need.
349
f. Open a command prompt. Start > Run > type "cmd" (without the quotes).
g. In the command window, type ipconfig -all then press Enter.
h. Find your Ethernet adapter and then find IP Address. This is the address that the PC
will be using. This is also the address that you will specify for the gateway address
when you create the Operations Console configuration.
For example if it shows 169.254.1.1 then you would use an address of 169.254.1.2 to
assign to the system during the configuration process. You want to match the first 3
sets of numbers, 169.254.1 in our case but select a number other than what the PC
will use for the system.
i. You can close the command window, if you desire.
The PC is now ready to be configured for Operations Console. Continue with Chapter 6: Setting
up Operations Console on page 125.
350
Appendix G. Advanced Systems Management

Interface (ASMI)
The Advanced System Management Interface (ASMI) is the interface to the service processor
that is required to perform general and administrator-level service tasks, such as reading service
processor error logs, reading vital product data, setting up the service processor, and controlling
the system power. The ASMI might also be referred to as the service processor menus.
The ASMI allows you to perform a variety of tasks associated with managing your server. The
purpose of this information is to familiarize you with some ASMI concepts:
ASMI requirements
To successfully access and use the ASMI, note the following requirements:
The ASMI requires password authentication.
The ASMI provides a Secure Sockets Layer (SSL) Web connection to the service
processor. To establish an SSL connection, open your browser using https://.
Supported browsers are Netscape (version 7.1), Microsoft Internet Explorer (version
6.0), and Opera (version 7.23). Later versions of these browsers cannot be used to access
ASMI. JavaScript and cookies must be enabled.
Clicking Back in the browser might display outdated data. To display the most up-to-date
data, select the desired item from the navigation pane.
The browser-based ASMI is available during all phases of the system operation,
including initial program load (IPL) and run time. Some menu options are not available
during the system IPL or run time to prevent usage or ownership conflicts if
corresponding resources are in use during that phase.
The ASMI that is accessed on a terminal is available only if the system is at platform
standby.
All requested input must be provided in English-language characters regardless of the
language selected to view the interface.
351
ASMI authority levels

There are several authority levels for accessing the service processor menus using the ASMI.
The following levels of access are supported:
General user
The menu options presented to the general user are a subset of the options available to
the administrator and authorized service provider. Users with general authority can view
settings in the ASMI menus. The login ID is general and the default password is general.
Administrator
The menu options presented to the administrator are a subset of the options available to
the authorized service provider. Users with administrator authority can write to persistent
storage, and view and change settings that affect the server's behavior. The first time a
user logs into the ASMI after the server is installed, a new password must be selected.
The login ID is admin and the default password is admin.
Authorized service provider
This login gives the authorized service provider access to all functions that could be used
to gather additional debug information from a failing system, such as viewing persistent
storage, and clearing all deconfiguration errors. The login ID is celogin. The password is
dynamically generated and must be obtained by calling IBM technical support.
During the initial administrator and general user logins, the only menu option available is
Change Password. In order to gain access to additional ASMI menus, you must change the
administrator and general user default passwords. If you are an authorized service provider, you
cannot change your password.
Changing ASMI passwords

You can change the general user, administrator, and HMC access passwords.
If you are a general user, you can change only your own password.
If you are an administrator, you can change your password and the passwords for general user
accounts and the HMC access password.
If you are an authorized service provider, you can change your password, the passwords for
general and administrator user accounts, and the HMC access password.
Passwords can be any combination of up to 64 alphanumeric characters. The default password
for the general user ID is general, and the default password for the administrator ID is admin.
After your initial login to the ASMI and after the reset toggle jumpers are moved, the general
user and administrator passwords must be changed. For information about how to reset the
administrator password, see Resetting the ASMI administrator password below.
352
The HMC access password is usually set from the HMC during initial login. If you change this
password using the ASMI, the change takes effect immediately.
To change a password, follow these steps:
Note: As a security measure, you are required to enter the current user's password into the
Current password for user ID field. This password is not the password for the user ID you want to
change.
1. On the ASMI Welcome pane, specify your user ID and password, and click Log In.
2. In the navigation area, expand Login Profile.
3. Select Change Password.
4. Specify the required information, and click Continue.
Resetting the ASMI administrator password

You can reset the administrator password by either of the following methods:
Contact an authorized service provider

Use the reset toggle jumpers on the service processor
To reset the toggle jumper on the service processor, move both service processor reset toggle
switches from their current position to the opposite position. For information about how to use
the reset toggle jumpers, refer to the remove and replace procedure for your system model in the
Service processor assembly, service processor cable, and time-of-day-battery topic.
http://publib.boulder.ibm.com/infocenter/systems/topic/iphbs/iphbs_serviceprocessor.htm
ASMI login restrictions

Only three users can log in at the same time. For example, if three people are logged in to the
ASMI and a person with a higher authority level than one of the current logged in users attempts
to log in, the ASMI forces one of the lowest privileged users to log out. In addition, if you are
logged in and not active for 15 minutes, your session expires. You receive no immediate
notification when your session expires. However, when you select anything on the current page,
you are returned to the ASMI Welcome pane.
To see who is logged in to the ASMI, view Current users on the ASMI Welcome pane after you
log in.
If you make five login attempts that are not valid, your user account is locked out for five
minutes and none of the other accounts are affected. For example, if the administrator account is
locked, the general user can still log in using the correct password. This login restriction applies
to the general user, administrator, and authorized service provider IDs. This login restriction also
applies to the managed system HMC access ID, which is set using the HMC.
For information about HMC-access passwords for a managed system, see Overview of
passwords.
http://publib.boulder.ibm.com/infocenter/systems/topic/ipha1/overviewofthepasswords.htm
353
Accessing the ASMI

Use the following information to help you set up access to the ASMI:
Accessing the ASMI using a Web browser

Connect a PC or mobile computer to the server to access the ASMI. The Web interface to the
ASMI is available during all phases of system operation including the initial program load
(IPL) and run time.
The Web interface to the Advanced System Management Interface (ASMI) is accessible
through Microsoft Internet Explorer 6.0, Netscape 7.1, or Opera 7.23 running on a PC or
mobile computer connected to the service processor. The Web interface is available during
all phases of system operation including the initial program load (IPL) and run time.
However, some of the menu options in the Web interface are unavailable during IPL or run
time to prevent usage or ownership conflicts if the system resources are in use during that
phase.
Note: If your system is not managed by an HMC, you must set up ASMI to perform general
and administrator-level service tasks, such as reading service processor error logs, reading
vital product data, setting up the service processor, and controlling the system power.
The following instructions apply to systems that are not connected to an HMC. If you are
managing the server using an HMC, use the appropriate link below to Access the ASMI
using the HMC.
Power5 processor-based:
http://publib.boulder.ibm.com/infocenter/systems/topic/iphby/asmihmc.htm
http://www.ibm.com/servers/resourcelink/lib03030.nsf/pages/OperationsGuidefortheHardwa
reManagementConsoleandManagedSystems?OpenDocument&pathID=sa76-0085.pdf
To set up the Web browser for direct or remote access to the ASMI, complete the following
tasks:
1. Connect the power cord from the server to a power source, and wait for the control
panel to display 01.
2. Select a PC or mobile computer that has Microsoft Internet Explorer 6.0, Netscape
7.1, or Opera 7.23 to connect to your server.
If you do not plan to connect your server to your network, this PC or mobile
computer will be your ASMI console.
If you plan to connect your server to your network, this PC or mobile computer will
be temporarily connected directly to the server for setup purposes only. After setup,
you can use any PC or mobile computer on your network that is running Microsoft
Internet Explorer 6.0, Netscape 7.1, or Opera 7.23 as your ASMI console.
354
3. Connect an Ethernet cable from the PC or mobile computer to the Ethernet port
labeled HMC1 on the back of the managed system.
If HMC1 is occupied, connect an Ethernet cable from the PC or mobile computer to
the Ethernet port labeled HMC2 on the back of the managed system.
4. Configure the Ethernet interface on the PC or mobile computer to an IP address and
subnet mask within the same subnet as the server so that your PC or mobile computer
can communicate with the server. For instructions, see Setting the IP address on your
PC or mobile computer.
http://publib.boulder.ibm.com/infoceoanter/systems/topic/iphby/asmiipaddress.htm#a
smiipaddress
Use the following table to help you determine these values:
Platform
FSP-A
HMC1
Power5
192.168.2.147
processorbased
Power6
169.254.2.147
processorbased
Platform
HMC2
192.168.3.147
255.255.255.0
169.254.3.147
255.255.255.0
FSP-B (if installed)

HMC1
HMC2
192.168.2.146 192.168.3.146
255.255.255.0
169.254.3.146
255.255.255.0
Power5
processorbased
Power6
169.254.2.146
processorbased
For example, if you connected your PC or mobile computer to service processor A,

HMC1, the IP address for your PC or mobile computer could be 192.168.2.147 and
the subnet mask would be 255.255.255.0. Set the gateway IP address to the same IP
address as the PC or mobile computer.
355
5. Use the table above to determine the IP address of the Ethernet port that your PC or
mobile computer is connected to, and type the IP address in the Address field of your
PC's or mobile computer's Web browser. For example, if you connected your PC or
mobile computer to HMC1, type https://169.254.2.147 in your PC's or
mobile computer's Web browser.
6. When the login display appears, enter one of the following default user IDs and
passwords:
User ID
Password
Table 2. Default user IDs and

passwords for the Web interface
general
general
admin
admin
7. Change the default password when prompted. For information, see ASMI authority
levels on page 352.
8. If you plan to connect your PC or mobile computer to your network, complete the
following steps:
a. From the navigation area, expand Network Services.
b. Click Network Configuration.
c. If your PC or mobile computer is connected to HMC1, fill in the section labeled
Network interface eth0.
If your PC or mobile computer is connected to HMC2, fill in the section labeled
Network interface eth1.
Ensure that the following fields are filled in correctly.
Field
Value
Table 3. Fields and values for

network configuration
Configure this interface?
Selected
Type of IP address
Static
Host name
Enter a new value.
Domain name
Enter a new value.
IP address
This is a set IP address obtained from

the network administrator.
Subnet mask
This is a set subnet mask obtained from

the network administrator.
356
Note: For information about the other fields and values, refer to Configuring
network interfaces.
http://publib.boulder.ibm.com/infocenter/systems/topic/iphbp/networkconfig.htm
d.
e.
f.
g.
h.
Click Continue.
Click Save Settings.
Disconnect your PC or mobile computer from the server.
Connect the server to your company network.
Go to any PC or mobile computer on your company network that is running
Microsoft Internet Explorer 6.0, Netscape 7.1, or Opera 7.23, and type the
following in the Address field of your browser:
https://host name.domain name
where host name and domain name are the host name and domain name you
entered when completing step 8.c above.
i. Log in to the ASMI.
Accessing the ASMI using an ASCII terminal for Power5 processor-based

http://publib.boulder.ibm.com/infocenter/systems/topic/iphby/ascii.htm
Connect the ASCII terminal to the server to access the ASMI.
Accessing the ASMI using the HMC for Power5 processor-based

http://publib.boulder.ibm.com/infocenter/systems/topic/iphby/asmihmc.htm
Access the ASMI through the HMC interface.
Power6 processor-based information is located in:

357
Filler page
358
Appendix H. Danger Notice

DANGER
When working on or around the system, observe the following precautions:
Electrical voltage and current from power, telephone, and communication
cables are hazardous. To avoid a shock hazard:
Connect power to this unit only with the IBM provided power cord. Do
not use the IBM provided power cord for any other product.
Do not open or service any power supply assembly.
Do not connect or disconnect any cables or perform installation,
maintenance, or reconfiguration of this product during an electrical
storm.
The product might be equipped with multiple power cords. To remove all
hazardous voltages, disconnect all power cords.
Connect all power cords to a properly wired and grounded electrical
outlet. Ensure that the outlet supplies proper voltage and phase
rotation according to the system rating plate.
Connect any equipment that will be attached to this product to properly
wired outlets.
When possible, use one hand only to connect or disconnect signal
cables.
Never turn on any equipment when there is evidence of fire, water, or
structural damage.
Disconnect the attached power cords, telecommunications systems,
networks, and modems before you open the device covers, unless
instructed otherwise in the installation and configuration procedures.
Connect and disconnect cables as described in the following procedures
when installing, moving, or opening covers on this product or attached
devices.
To Disconnect:
1. Turn off everything (unless instructed otherwise).
2. Remove the power cords from the outlets.
3. Remove the signal cables from the connectors.
4. Remove all cables from the devices
To Connect:
1. Turn off everything (unless instructed otherwise).
2. Attach all cables to the devices.
3. Attach the signal cables to the connectors.
4. Attach the power cords to the outlets.
5. Turn on the devices. (D005)
359
Filler page
360
Appendix I. Notices
This information was developed for products and services offered in the U.S.A.
The manufacturer may not offer the products, services, or features discussed in this document in
other countries. Consult the manufacturers representative for information on the products and
services currently available in your area. Any reference to the manufacturers product, program,
or service is not intended to state or imply that only that product, program, or service may be
used. Any functionally equivalent product, program, or service that does not infringe any
intellectual property right of the manufacturer may be used instead. However, it is the users
responsibility to evaluate and verify the operation of any product, program, or service.
The manufacturer may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you any license to
these patents. You can send license inquiries, in writing, to the manufacturer.
The following paragraph does not apply to the United Kingdom or any other country
where such provisions are inconsistent with local law: THIS INFORMATION IS
PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in certain transactions,
therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are
periodically made to the information herein; these changes will be incorporated in new editions
of the publication. The manufacturer may make improvements and/or changes in the product(s)
and/or the program(s) described in this publication at any time without notice.
Any references in this information to Web sites not owned by the manufacturer are provided for
convenience only and do not in any manner serve as an endorsement of those Web sites. The
materials at those Web sites are not part of the materials for this product and use of those Web
sites is at your own risk.
The manufacturer may use or distribute any of the information you supply in any way it believes
appropriate without incurring any obligation to you.
Any performance data contained herein was determined in a controlled environment. Therefore,
the results obtained in other operating environments may vary significantly. Some measurements
may have been made on development-level systems and there is no guarantee that these
measurements will be the same on generally available systems. Furthermore, some
measurements may have been estimated through extrapolation. Actual results may vary. Users of
this document should verify the applicable data for their specific environment.
361
Information concerning products not produced by this manufacturer was obtained from the
suppliers of those products, their published announcements or other publicly available sources.
This manufacturer has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to products not produced by this
manufacturer. Questions on the capabilities of products not produced by this manufacturer
should be addressed to the suppliers of those products.
All statements regarding the manufacturers future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
The manufacturers prices shown are the manufacturers suggested retail prices, are current and
are subject to change without notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to change
before the products described become available.
This information contains examples of data and reports used in daily business operations. To
illustrate them as completely as possible, the examples include the names of individuals,
companies, brands, and products. All of these names are fictitious and any similarity to the
names and addresses used by an actual business enterprise is entirely coincidental.
If you are viewing this information in softcopy, the photographs and color illustrations may not
appear.
The drawings and specifications contained herein shall not be reproduced in whole or in part
without the written permission of the manufacturer.
The manufacturer has prepared this information for use with the specific machines indicated.
The manufacturer makes no representations that it is suitable for any other purpose.
The manufacturers computer systems contain mechanisms designed to reduce the possibility of
undetected data corruption or loss. This risk, however, cannot be eliminated. Users who
experience unplanned outages, system failures, power fluctuations or outages, or component
failures must verify the accuracy of operations performed and data saved or transmitted by the
system at or near the time of the outage or failure. In addition, users must establish procedures to
ensure that there is independent data verification before relying on such data in sensitive or
critical operations. Users should periodically check the manufacturers support websites for
updated information and fixes applicable to the system and related software.
362
Trademarks
The following terms are trademarks of International Business Machines Corporation in the
United States, other countries, or both:
IBM AS/400, AS/400e, iSeries, eServer, System i, Systemi5, eServer i5,

Power, Power5, Power6
AS/400
AS/400e
BladeCenter
e(logo)server
eServer
eServer i5
Hummingbird
i5/OS
i5/OS(logo)
IBM
IBM (logo)
Operating System/400
iSeries
OS/400
Power
Power5
Power6
System i5
System i
xSeries
MMX, Pentium, and are trademarks or registered trademarks of Intel Corporation in the
United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft
Corporation in the United States, other countries, or both. Other company, product or
service names may be trademarks or service marks of others.
363
Electronic emission notices

Class A Notices
The following Class A statements apply to the IBM System i models that contain the POWER6
processor.
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. These limits are designed to provide reasonable protection
against harmful interference when the equipment is operated in a commercial environment. This
equipment generates, uses, and can radiate radio frequency energy and, if not installed and used
in accordance with the instruction manual, may cause harmful interference to radio
communications. Operation of this equipment in a residential area is likely to cause harmful
interference, in which case the user will be required to correct the interference at his own
expense.
Properly shielded and grounded cables and connectors must be used in order to meet FCC
emission limits. IBM is not responsible for any radio or television interference caused by using
other than recommended cables and connectors or by unauthorized changes or modifications to
this equipment. Unauthorized changes or modifications could void the users authority to operate
the equipment.
This device complies with Part 15 of the FCC rules. Operation is subject to the following two
conditions: (1) this device may not cause harmful interference, and (2) this device must accept
any interference received, including interference that may cause undesired operation.
Industry Canada Compliance Statement
This Class A digital apparatus complies with Canadian ICES-003.
Avis de conformit la rglementation dIndustrie Canada Cet appareil numrique de la
classe A respecte est conforme la norme NMB-003 du Canada.
European Community Compliance Statement
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.
This product has been tested and found to comply with the limits for Class A Information
Technology Equipment according to European Standard EN 55022. The limits for Class A
equipment were derived for commercial and industrial environments to provide reasonable
protection against interference with licensed communication equipment.
364
European Community contact: IBM Technical Regulations Pascalstr. 100, Stuttgart, Germany
70569 Tele: 0049 (0)711 785 1176 Fax: 0049 (0)711 785 1283 E-mail: tjahn@de.ibm.com
Warning: This is a Class A product. In a domestic environment, this product may cause radio
interference, in which case the user may be required to take adequate measures.
VCCI Statement - Japan
The following is a summary of the VCCI Japanese statement in the box above.
This product is a Class A Information Technology Equipment and conforms to the standards set
by the Voluntary Control Council for Interference by Information Technology Equipment
(VCCI). In a domestic environment, this product may cause radio interference, in which case the
user may be required to take adequate measures.
Electromagnetic Interference (EMI) Statement - Peoples Republic of China
Declaration: This is a Class A product. In a domestic environment this product may cause radio
interference in which case the user may need to perform practical action.
Electromagnetic Interference (EMI) Statement - Taiwan
The following is a summary of the EMI Taiwan statement above.
Warning: This is a Class A product. In a domestic environment this product may cause radio
interference in which case the user will be required to take adequate measures.
IBM Taiwan Contact Information:
365
Electromagnetic Interference (EMI) Statement - Korea
Please note that this equipment has obtained EMC registration for commercial use. In the event
that it has been mistakenly sold or purchased, please exchange it for equipment certified for
home use.
Germany Compliance Statement
Deutschsprachiger EU Hinweis: Hinweis fr Gerte der Klasse A EU-Richtlinie zur
Elektromagnetischen Vertrglichkeit
Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie 2004/108/EG zur
Angleichung der Rechtsvorschriften ber die elektromagnetische Vertrglichkeit in den EUMitgliedsstaaten und hlt die Grenzwerte der EN 55022 Klasse A ein.
Um dieses sicherzustellen, sind die Gerte wie in den Handbchern beschrieben zu installieren
und zu betreiben. Des Weiteren drfen auch nur von der IBM empfohlene Kabel angeschlossen
werden. IBM bernimmt keine Verantwortung fr die Einhaltung der Schutzanforderungen,
wenn das Produkt ohne Zustimmung der IBM verndert bzw. wenn Erweiterungskomponenten
von Fremdherstellern ohne Empfehlung der IBM gesteckt/eingebaut werden.
EN 55022 Klasse A Gerte mssen mit folgendem Warnhinweis versehen werden: Warnung:
Dieses ist eine Einrichtung der Klasse A. Diese Einrichtung kann im Wohnbereich FunkStrungen verursachen; in diesem Fall kann vom Betreiber verlangt werden, angemessene
Manahmen zu ergreifen und dafr aufzukommen.
Deutschland: Einhaltung des Gesetzes ber die elektromagnetische Vertrglichkeit von
Gerten
Dieses Produkt entspricht dem Gesetz ber die elektromagnetische Vertrglichkeit von Gerten
(EMVG). Dies ist die Umsetzung der EU-Richtlinie 2004/108/EG in der Bundesrepublik
Deutschland.
Zulassungsbescheinigung laut dem Deutschen Gesetz ber die elektromagnetische
Vertrglichkeit von Gerten (EMVG) (bzw. der EMC EG Richtlinie 2004/108/EG) fr
Gerte der Klasse A.
Dieses Gert ist berechtigt, in bereinstimmung mit dem Deutschen EMVG das EGKonformittszeichen - CE - zu fhren.
Verantwortlich fr die Konformittserklrung nach des EMVG ist die IBM Deutschland GmbH,
70548 Stuttgart.
366
Generelle Informationen:
Das Gert erfllt die Schutzanforderungen nach EN 55024 und EN 55022 Klasse A.
Electromagnetic Interference (EMI) Statement - Russia
Terms and conditions

Permissions for the use of these publications is granted subject to the following terms and
conditions.
Personal Use: You may reproduce these publications for your personal, noncommercial use
provided that all proprietary notices are preserved. You may not distribute, display or make
derivative works of these publications, or any portion thereof, without the express consent of the
manufacturer.
Commercial Use: You may reproduce, distribute and display these publications solely within
your enterprise provided that all proprietary notices are preserved. You may not make derivative
works of these publications, or reproduce, distribute or display these publications or any portion
thereof outside your enterprise, without the express consent of the manufacturer.
Except as expressly granted in this permission, no other permissions, licenses or rights are
granted, either express or implied, to the publications or any data, software or other intellectual
property contained therein.
The manufacturer 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 the
manufacturer, the above instructions are not being properly followed.
You may not download, export or re-export this information except in full compliance with all
applicable laws and regulations, including all United States export laws and regulations.
THE MANUFACTURER MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE
PUBLICATIONS. THESE PUBLICATIONS ARE PROVIDED AS-IS AND WITHOUT
WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT
NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.
367
368

Reference and How-To - Operations Console and Other i5-OS Consoles

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Reference and How-To - Operations Console and Other i5-OS Consoles

Transféré par

Droits d'auteur :

Formats disponibles

Operations Console and Other i5/OS (OS/400)

Reference and How-To

First Edition (July 2008)

Safety and environmental notices

CAUTION notices call attention to a situation that is potentially hazardous to people

World Trade safety information

Use of the controls or adjustments or performance of procedures other than those

Locations where the NEC (National Electrical Code) applies

For Taiwan: Please recycle batteries.

For the European Union:

Chapter 3: First Time System Setup..............................................................................................91

unlock service tools device IDs in SST?............................................................................248

Appendix D. System Locations for Cards & Cables...................................................................321

Start here - Welcome to Operations Console

For Power6 processor-based Blade use:

Console types covered in this document

Platform and environment information

9406 - 8xx series

9406 - 515, 520, 525

9407-M15 520, 9408-M25 520,

Power6 Processor-based using

JS22 and JS12 Type 7998 blade

The term environment is used to further define the platform:

Operating system console designations

A twinaxial workstation on the primary twinaxial workstation controller with port

A twinaxial workstation on the controller where the alternate console tag is

Operations Console connectivities

Local console directly attached to the server

Local console on a network (LAN)

Remote console through dial-up support (V5R3/V5R4 only)

Supported resources for a local console on a network (LAN)

2849 PCI 100/10 Mbps Ethernet IOA

Supported asynchronous communication adapters for a local console directly

Supported asynchronous adapters, Power6 processor-based and later

Supported adapter locations

Power5 processor-based (not HMC managed)

Power6 processor-based (not HMC managed)

MMA C1, C4 (3)

Supported models by release

Default addresses for the HMC1 and HMC2 ports

FSP B (if installed)

Power6 processor-based Blade and Power6 processorbased System running VIOS/IVM

PC requirements for Operations Console

Pentium 300 MHz recommended

(Use Windows XP instructions)

What Functions, When?

A problem in PC5250 requires SI27741 (SP6) for any function

System side function

RCP/VCP (Power5 processor-based/6 hardware does not support ANY directly-cabled

Info Center changes

V4R3 V4R4 V4R5 V5R1 V5R2 V5R3

Pre-Power5 processor-based - Serial - Direct cable

V4R3 V4R4 V4R5 V5R1 V5R2 V5R3 V5R3 V5R3M5

Pre-Power5 processor-based (iSeries) - Serial - Direct cable

V4R5 V5R1 V5R2

V5R3 V5R3M5 V5R4M0 V5R4M5 V6R1

Power5 processor-based - Asynchronous - Direct cable

Power6 processor-based - Asynchronous - Direct cable (all HW runs IOP-less)

Pre-Power5 processor-based - Network (LAN)

Power5 processor-based - Network (LAN)

V5R3M5 V5R4M0 V5R4M5 V6R1

Power6 processor-based - LAN

Power6 processorbased Blade