System z10
Support Element Operations Guide
Version 2.10.1
SC28-6879-00



System z10
Support Element Operations Guide
Version 2.10.1
SC28-6879-00
 Note
Before using this information and the product it supports, be sure to read the information under
“Safety notices” on page ix and “Notices” on page 265.

First Edition (October 2008)

This edition, SC28-6879-00, applies to the IBM® Support Element Console Application, Version 2.10.1.
There may be a newer version of this document in PDF format available on Resource Link™. Go to
http://www.ibm.com/servers/resourcelink and click on Library on the navigation bar. A newer version is indicated by a
lower case alphabetic letter following the form number suffix. For example: 00a, 00b, 01a, 01b.
© Copyright International Business Machines Corporation 2008.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Safety and environmental notices . . . . . . . . . . . . . . . . . ix
Safety notices . . . . . . . . . . . . . . . . . . . . . . . . . ix
World trade safety information . . . . . . . . . . . . . . . . . . ix
Laser safety information . . . . . . . . . . . . . . . . . . . . . . ix
Laser compliance . . . . . . . . . . . . . . . . . . . . . . . ix
Environmental notices . . . . . . . . . . . . . . . . . . . . . . ix
Product recycling and disposal . . . . . . . . . . . . . . . . . . ix
Refrigeration . . . . . . . . . . . . . . . . . . . . . . . . . xi
Battery return program . . . . . . . . . . . . . . . . . . . . . xxi
Flat panel display . . . . . . . . . . . . . . . . . . . . . . xxiii
Monitors and workstations . . . . . . . . . . . . . . . . . . . xxiii

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
How to use this guide . . . . . . . . . . . . . . . . . . . . . . xxv
What’s new in version 2.10.1 . . . . . . . . . . . . . . . . . . xxvi
How to send your comments . . . . . . . . . . . . . . . . . . . xxvii

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . 1
The support element console application . . . . . . . . . . . . . . . . 1
Establishing a support element console session from a Hardware Management
Console . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Logging off the support element console . . . . . . . . . . . . . . . 3
User Interface (UI) styles for the support element console . . . . . . . . . 4
Tree style user interface . . . . . . . . . . . . . . . . . . . . . 4
Classic style user interface . . . . . . . . . . . . . . . . . . . . 4
Enabling users to change interface style . . . . . . . . . . . . . . . 5
Changing interface style . . . . . . . . . . . . . . . . . . . . . 5
Context sensitive help . . . . . . . . . . . . . . . . . . . . . . . 6
Disruptive tasks . . . . . . . . . . . . . . . . . . . . . . . . . 7
USB flash memory drive . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2. Using the tree style user interface . . . . . . . . . . . . . 9

Task bar . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Navigation pane . . . . . . . . . . . . . . . . . . . . . . . . 10
Navigation pane collapse/expand controls . . . . . . . . . . . . . . 10
Navigation toolbar . . . . . . . . . . . . . . . . . . . . . . . 11
Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Systems management . . . . . . . . . . . . . . . . . . . . . 12
SE management . . . . . . . . . . . . . . . . . . . . . . . 19
Service management . . . . . . . . . . . . . . . . . . . . . 20
Tasks index . . . . . . . . . . . . . . . . . . . . . . . . . 21
Work pane . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Work pane title and breadcrumb trail . . . . . . . . . . . . . . . . 23
Work pane table footer . . . . . . . . . . . . . . . . . . . . . 23
Work pane views . . . . . . . . . . . . . . . . . . . . . . . 23
Working with the work pane table toolbar . . . . . . . . . . . . . . 30
Tasks menu . . . . . . . . . . . . . . . . . . . . . . . . . 32
Views menu . . . . . . . . . . . . . . . . . . . . . . . . . 32
Status bar . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Status: exceptions . . . . . . . . . . . . . . . . . . . . . . . 32
Status: hardware messages . . . . . . . . . . . . . . . . . . . 32
Status: operating system messages . . . . . . . . . . . . . . . . 33
Status overview . . . . . . . . . . . . . . . . . . . . . . . 33

© Copyright IBM Corp. 2008 iii

 Object locking for disruptive tasks . . . . . . . . . . . . . . . . . . 34

Chapter 3. Using the classic style user interface . . . . . . . . . . . 35

Support element workplace . . . . . . . . . . . . . . . . . . . . 35
Monitoring and operating the system . . . . . . . . . . . . . . . . . 37
Monitoring summarized system status . . . . . . . . . . . . . . . 37
Getting detailed system status . . . . . . . . . . . . . . . . . . 39
Locating groups and objects . . . . . . . . . . . . . . . . . . . 40
Determining the exact status of an object . . . . . . . . . . . . . . 43
Locating objects with unacceptable status . . . . . . . . . . . . . . 48
Recognizing exceptions . . . . . . . . . . . . . . . . . . . . . 48
Returning an exception to an acceptable status . . . . . . . . . . . . 48
Starting tasks . . . . . . . . . . . . . . . . . . . . . . . . 49
Setting object locking for disruptive tasks on an object . . . . . . . . . . 54
Monitoring and operating the support element console: an overview . . . . . 55
Opening an online book . . . . . . . . . . . . . . . . . . . . . 56
Getting online help . . . . . . . . . . . . . . . . . . . . . . 56
Opening the workplace pop-up menu . . . . . . . . . . . . . . . . . 57

Chapter 4. Daily operation of the system . . . . . . . . . . . . . . 59

Starting the system . . . . . . . . . . . . . . . . . . . . . . . 59
Activation . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Getting ready for an activation . . . . . . . . . . . . . . . . . . 62
Activating the CPC . . . . . . . . . . . . . . . . . . . . . . 62
Checking hardware messages from the CPC . . . . . . . . . . . . . . 64
Recognizing when hardware messages were received . . . . . . . . . 64
Viewing hardware messages . . . . . . . . . . . . . . . . . . . 65
Using the support element console as an operating system console . . . . . 65
Checking operating system messages from images . . . . . . . . . . 66
Sending commands to operating systems . . . . . . . . . . . . . . 67
Monitoring system activity . . . . . . . . . . . . . . . . . . . . . 68
System activity analysis . . . . . . . . . . . . . . . . . . . . 69
System activity profiles . . . . . . . . . . . . . . . . . . . . . 69
Starting system activity analysis . . . . . . . . . . . . . . . . . 71
Resetting the system or logical partitions . . . . . . . . . . . . . . . 74
Shutting down and turning off the system . . . . . . . . . . . . . . . 75
Deactivating the CPC . . . . . . . . . . . . . . . . . . . . . 76
Logging off the support element console . . . . . . . . . . . . . . 77
Managing groups of objects . . . . . . . . . . . . . . . . . . . . 77

Chapter 5. Error recovery . . . . . . . . . . . . . . . . . . . . 81

Processor operations: start all and stop all . . . . . . . . . . . . . . . 81
Stopping all processors . . . . . . . . . . . . . . . . . . . . . 82
Starting all processors . . . . . . . . . . . . . . . . . . . . . 82
Resets: normal and clear . . . . . . . . . . . . . . . . . . . . . 83
Reset normal . . . . . . . . . . . . . . . . . . . . . . . . 83
Reset clear . . . . . . . . . . . . . . . . . . . . . . . . . 84
Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Power-on reset . . . . . . . . . . . . . . . . . . . . . . . . . 85
Installing software from a CD-ROM, DVD or FTP server . . . . . . . . . . 86

Chapter 6. Settings for system operations . . . . . . . . . . . . . . 89

Getting ready to operate the system: customizing activation profiles . . . . . 89
Default activation profiles . . . . . . . . . . . . . . . . . . . . 90
Using the right profiles . . . . . . . . . . . . . . . . . . . . . 90
Developing an activation strategy . . . . . . . . . . . . . . . . . 91

iv Support Element Operations Guide

 Profiles for complete activation . . . . . . . . . . . . . . . . . . 92
Profiles for staged activations . . . . . . . . . . . . . . . . . . 122
Viewing activation profiles . . . . . . . . . . . . . . . . . . . 132
Assigning activation profiles to objects . . . . . . . . . . . . . . . 132
Grouping objects for activation . . . . . . . . . . . . . . . . . . 133
Starting the system automatically after a power outage. . . . . . . . . . 135
Automating system operations . . . . . . . . . . . . . . . . . . . 136
Scheduling operations . . . . . . . . . . . . . . . . . . . . . 136
Setting the CPC time-of-day clock . . . . . . . . . . . . . . . . . 137
Synchronizing the CPC TOD clock to a time synchronization source . . . . 137
Synchronizing the CPC TOD clock and the support element TOD clock 138
Allocating storage . . . . . . . . . . . . . . . . . . . . . . . 138
Reviewing current storage allocations . . . . . . . . . . . . . . . 139
Degraded storage mode . . . . . . . . . . . . . . . . . . . . 139
Getting ready to monitor the system: customizing system activity profiles 142
Opening a list of system activity profiles . . . . . . . . . . . . . . 142
Viewing a system activity profile . . . . . . . . . . . . . . . . . 143
Customizing a system activity profile . . . . . . . . . . . . . . . 143
Creating a new system activity profile . . . . . . . . . . . . . . . 144
Preparing to monitor system activity . . . . . . . . . . . . . . . . 145

Chapter 7. Settings for remote connections and communications . . . . 147

Connecting and communicating with a remote service support system . . . . 147
Getting ready to report problems and get service . . . . . . . . . . . 147
Getting ready to retrieve internal code changes . . . . . . . . . . . 148
Getting ready to transmit service data . . . . . . . . . . . . . . . 149
Customizing remote service settings . . . . . . . . . . . . . . . 149
Assisting service providers with contacting your company . . . . . . . . . 150

Chapter 8. System testing, problem determination, and service . . . . . 153

Enabling service status . . . . . . . . . . . . . . . . . . . . . 153
Testing the CPC hardware . . . . . . . . . . . . . . . . . . . . 154
Reporting problems and getting service . . . . . . . . . . . . . . . 154
Settings for reporting problems and getting service automatically . . . . . 155
Using hardware messages to report problems and get service . . . . . . 155
Starting problem analysis manually for suspected problems . . . . . . . 156
Reporting and getting service manually for suspected problems . . . . . 157
Sending service data to IBM . . . . . . . . . . . . . . . . . . 157
Keeping records of problems and service . . . . . . . . . . . . . . 161
Offloading virtual RETAIN data to the HMC DVD . . . . . . . . . . . . 162
Checking InfiniBand multiport status . . . . . . . . . . . . . . . . 162
Setting OSA-Express network traffic analyzer (NTA) controls . . . . . . . 163
Displaying global OSA status . . . . . . . . . . . . . . . . . . . 164

Chapter 9. LPAR mode operations . . . . . . . . . . . . . . . . 165

Changing how logical partitions operate: alternatives to activation . . . . . . 165
Logical partition security . . . . . . . . . . . . . . . . . . . . 165
Logical partition controls . . . . . . . . . . . . . . . . . . . . 167
Logical partition group controls . . . . . . . . . . . . . . . . . 169
Logical partition cryptographic controls . . . . . . . . . . . . . . . 170
Adding logical processors . . . . . . . . . . . . . . . . . . . 171
Setting the system time offset . . . . . . . . . . . . . . . . . . . 172
Enabling I/O priority queuing . . . . . . . . . . . . . . . . . . . 173
Changing LPAR I/O priority queuing . . . . . . . . . . . . . . . . . 173
Exporting and importing profile data . . . . . . . . . . . . . . . . . 174

Contents v
 Chapter 10. CPC configuration management . . . . . . . . . . . . 175
Getting information about the hardware configuration . . . . . . . . . . 175
Displaying the InfiniBand adapter ID . . . . . . . . . . . . . . . . 176
The I/O configuration . . . . . . . . . . . . . . . . . . . . . . 176
Defining the I/O configuration using the stand-alone IOCP . . . . . . . 176
Determining PCHIDs assignments to channels . . . . . . . . . . . . 177
Viewing the input/output (I/O) configuration data . . . . . . . . . . . . 178
Hardware configuration upgrades and model conversions . . . . . . . . . 179
Hardware upgrades . . . . . . . . . . . . . . . . . . . . . . 179
Permanent upgrades . . . . . . . . . . . . . . . . . . . . . 180
Temporary upgrades . . . . . . . . . . . . . . . . . . . . . 181
Time Synchronization features . . . . . . . . . . . . . . . . . . . 182
Setting up time synchronization . . . . . . . . . . . . . . . . . 183
The Crypto Express2 feature . . . . . . . . . . . . . . . . . . . 189
Working with the Crypto Express2 feature . . . . . . . . . . . . . 189
Configuring and monitoring the Crypto Express2 feature . . . . . . . . 190
Changing permission for TKE commands . . . . . . . . . . . . . . 192
Selecting a crypto type configuration . . . . . . . . . . . . . . . 193
Configuring the User Defined Extensions (UDX) . . . . . . . . . . . 193
Releasing a X2 Coprocessor or X2 Accelerator . . . . . . . . . . . . 194
Releasing NPIV port names. . . . . . . . . . . . . . . . . . . . 195

Chapter 11. Internal code change management . . . . . . . . . . . 197

Licensed internal code . . . . . . . . . . . . . . . . . . . . . 197
Internal code changes . . . . . . . . . . . . . . . . . . . . . 197
Internal code change process . . . . . . . . . . . . . . . . . . 197
Changing internal code . . . . . . . . . . . . . . . . . . . . . 198
Automating the process . . . . . . . . . . . . . . . . . . . . 198
Making changes manually . . . . . . . . . . . . . . . . . . . 200
Checking dependencies . . . . . . . . . . . . . . . . . . . . 200
Considerations when activating internal code changes . . . . . . . . . 202
Keeping records of internal code changes . . . . . . . . . . . . . . 204
Viewing internal code change information. . . . . . . . . . . . . . 205
Settings for internal code change management . . . . . . . . . . . . 205
Settings for retrieving internal code changes from the IBM service support
system . . . . . . . . . . . . . . . . . . . . . . . . . 206
Settings for changing internal code . . . . . . . . . . . . . . . . 206
Defining clonable internal code levels . . . . . . . . . . . . . . . . 207
Forcing channel internal code change . . . . . . . . . . . . . . . . 208
Selective channel apply controls . . . . . . . . . . . . . . . . . . 209
Querying channel/crypto configure off/on pending . . . . . . . . . . . . 209
Querying internal code changes pending power-on reset . . . . . . . . . 210
Querying coupling facility reactivations . . . . . . . . . . . . . . . . 210
Specifying a concurrent upgrade sync point . . . . . . . . . . . . . . 211
Performing an alternate support element action . . . . . . . . . . . . 211
Forcing an immediate mirroring of the primary support element to the
alternate support element . . . . . . . . . . . . . . . . . . . 211
Querying switch capabilities between support elements . . . . . . . . 212
Switching to the alternate support element . . . . . . . . . . . . . 213

Chapter 12. Processor and storage operations . . . . . . . . . . . 215

Processor operations: start and stop . . . . . . . . . . . . . . . . 215
Displaying or altering data in processor storage . . . . . . . . . . . . 216
Restarting a processor . . . . . . . . . . . . . . . . . . . . . 217
Interrupting a processor . . . . . . . . . . . . . . . . . . . . . 217
Stopping CPs on address matches or events . . . . . . . . . . . . . 218

vi Support Element Operations Guide

Performing store status . . . . . . . . . . . . . . . . . . . . . 219

Chapter 13. Channel operations . . . . . . . . . . . . . . . . . 221

Configuring channel paths on or off . . . . . . . . . . . . . . . . . 221
Configuring reconfigurable channel paths in LPAR mode . . . . . . . . . 222
Releasing reconfigurable channel paths . . . . . . . . . . . . . . 222
Reassigning reconfigurable channel paths . . . . . . . . . . . . . 223
Setting service on or off for channels . . . . . . . . . . . . . . . . 224
Setting the channel LED on . . . . . . . . . . . . . . . . . . . . 225
Performing channel problem determination . . . . . . . . . . . . . . 226
Identifying channel definition errors . . . . . . . . . . . . . . . . 227
Working with the Open Systems Adapter (OSA)-Express . . . . . . . . . 227
Using advanced facilities for OSA-Express channels . . . . . . . . . 228

Chapter 14. CHPID operations . . . . . . . . . . . . . . . . . . 231

Configuring channel paths on or off . . . . . . . . . . . . . . . . . 231
Releasing reconfigurable channel paths . . . . . . . . . . . . . . . 232
Setting the channel LED on . . . . . . . . . . . . . . . . . . . . 233
Performing channel problem determination . . . . . . . . . . . . . . 233
Identifying channel definition errors . . . . . . . . . . . . . . . . 234
Enabling NPIV mode . . . . . . . . . . . . . . . . . . . . . . 235

Chapter 15. Crypto service operations . . . . . . . . . . . . . . . 237

Configuring crypto on or off . . . . . . . . . . . . . . . . . . . . 237
Setting service on or off for crypto . . . . . . . . . . . . . . . . . 238
Performing crypto problem determination . . . . . . . . . . . . . . . 239
Identifying crypto definition errors. . . . . . . . . . . . . . . . . 239
Using advanced facilities for crypto . . . . . . . . . . . . . . . . . 240

Chapter 16. Console actions . . . . . . . . . . . . . . . . . . . 241

Assigning domain security to your support element console . . . . . . . . 241
Blocking automatic licensed internal code change installation . . . . . . . 241
Changing your password . . . . . . . . . . . . . . . . . . . . . 242
Console messenger . . . . . . . . . . . . . . . . . . . . . . 242
Sending a broadcast message . . . . . . . . . . . . . . . . . . 243
Initiating a two-way chat . . . . . . . . . . . . . . . . . . . . 243
Controlling the system exclusively from the support element console . . . . 244
Customizing console default user settings . . . . . . . . . . . . . . 245
Customizing network settings . . . . . . . . . . . . . . . . . . . 246
Customizing password profiles . . . . . . . . . . . . . . . . . . . 247
Customizing product engineering access . . . . . . . . . . . . . . . 248
Customizing user profiles . . . . . . . . . . . . . . . . . . . . 248
Customizing user settings . . . . . . . . . . . . . . . . . . . . 250
Enabling automatic support element switchover . . . . . . . . . . . . 251
Enabling console messenger . . . . . . . . . . . . . . . . . . . 251
Enabling the network message forwarding . . . . . . . . . . . . . . 252
Enabling the application programming interface . . . . . . . . . . . . 252
Logging off the support element console . . . . . . . . . . . . . . . 253
Managing enterprise directory server definitions . . . . . . . . . . . . 254
Managing print screen files . . . . . . . . . . . . . . . . . . . . 254
Migrating channel configuration files . . . . . . . . . . . . . . . . 255
Performing problem analysis of optical errors . . . . . . . . . . . . . 255
Performing problem analysis on system I/O errors . . . . . . . . . . . 256
Providing modem services to the support element . . . . . . . . . . . 256
Setting object locking . . . . . . . . . . . . . . . . . . . . . . 257
Shutting down or restarting the system . . . . . . . . . . . . . . . 258

Contents vii
 Synchronizing the support element TOD clock and the CPC TOD clock . . . 258
Setting the support element time-of-day clock manually . . . . . . . . 259
Viewing console events . . . . . . . . . . . . . . . . . . . . . 259
Viewing licensed Internal code . . . . . . . . . . . . . . . . . . . 261
Viewing network diagnostic information . . . . . . . . . . . . . . . 261
Pinging the TCP/IP address . . . . . . . . . . . . . . . . . . . 262
Viewing security logs . . . . . . . . . . . . . . . . . . . . . . 262
Viewing users and tasks information . . . . . . . . . . . . . . . . 263

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . 266
Electronic emission notices . . . . . . . . . . . . . . . . . . . . 267

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

viii Support Element Operations Guide

Safety and environmental notices
Safety notices
Safety notices may be printed throughout this guide. DANGER notices warn you of
conditions or procedures that can result in death or severe personal injury.
CAUTION notices warn you of conditions or procedures that can cause personal
injury that is neither lethal nor extremely hazardous. Attention notices warn you of
conditions or procedures that can cause damage to machines, equipment, or
programs.

There are no DANGER notices in this document.

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 US English source. Before using a US English publication to
install, operate, or service this IBM 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 US English
publications.

Laser safety information

All System z models can use I/O cards such as PCI adapters, ESCON, FICON,
Open Systems Adapter (OSA), InterSystem Coupling-3 (ISC-3), or other I/O
features which are fiber optic based and 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:
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)

Environmental notices

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
© Copyright IBM Corp. 2008 ix
 equipment owners in recycling their IT products. Information on IBM product
recycling offerings can be found on IBM’s Internet sites at http://www.ibm.com/ibm/
recycle/us/index.shtml and http://www.ibm.com/ibm/environment/products/
index.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 tecnología de la información (TI) que reciclen responsablemente sus equipos
cuando éstos ya no les sean útiles. IBM dispone de una serie de programas y
servicios de devolución de productos en varios países, a fin de ayudar a los
propietarios de equipos a reciclar sus productos de TI. Se puede encontrar
información sobre las ofertas de reciclado de productos de IBM en el sitios web de
IBM http://www.ibm.com/ibm/recycle/us/index.shtml y http://www.ibm.com/ibm/
environment/products/index.shtml.

Notice: 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

x Support Element Operations Guide

 the potential presence of hazardous substances in EEE. For proper collection and
treatment, contact your local IBM representative.

Refrigeration
This system contains one or more modular refrigeration units with either R-134A or
R-507 refrigerant and a polyol ester oil. This refrigerant must not be released or
vented to the atmosphere. Skin contact with refrigerant may cause frostbite. Wear
appropriate eye and skin protection. Modular refrigeration units are hermetically
sealed and must not be opened or maintained.

This notice is provided in accordance with the European Union (EU) Regulation
842/2006 on fluorinated greenhouse gases. This product contains fluorinated
greenhouse gases covered by the Kyoto Protocol.

Per Annex I, Part 1, of EU Regulation 842/2006, the global warming potential of

R-134A is 1300. If the system is a z10 EC, each system contains 4.54 kg of
R-134A. If the system is a z9 EC or z990, each unit contains 1.22 kg of R-134A. If
the system is a Parallel Enterprise Server - Generation 4, 5, or 6, each unit
contains 0.76 kg of R-134A.

Per Annex I, Part 2, of the EU Regulation 842/2006, the global warming potential of
R-507 is calculated to be 3850. If the system is a z900, each unit contains 0.94 kg
of R-507.
Тази система съдържа един или повече модулни охладителни блока с R-
134A или R-507 охладител и полиолно естерно масло. Този охладител не
трябва да бъде освобождаван или изпускан в атмосферата. Контактът на
охладителя с кожата може да причини премръзвания. Носете подходяща
защита за кожата и очите. Модулните охладителни блокове са херметично
запечатани и не трябва да бъдат отваряни или ремонтирани.

Тази забележка се предоставя в съответствие с Наредба 842/2006 на

Европейския съюз (ЕС) за флуорирани парникови газове. Този продукт
съдържа флуорирани парникови газове, покривани от Протокола от Киото.

Според Анекс I, Част 1 на ЕС Наредба 842/2006, потенциалът за глобално

затопляне на R-134A е 1300. Ако системата е z10 EC, всяка система
съдържа 4.54 кг R-134A. Ако системата е z9 EC или z990, всеки блок
съдържа 1.22 кг R-134A. Ако системата е Parallel Enterprise Server -
Generation 4, 5 или 6, всеки блок съдържа 0.76 кг R-134A.

Според Анекс I, Част 2 на ЕС Наредба 842/2006, потенциалът за глобално

затопляне на R-507 е изчислен на 3850. Ако системата е z900, всеки блок
съдържа 0.94 кг R-507.

Safety and environmental notices xi

 Dette system indeholder en eller flere modulopbyggede køleenheder, der
indeholder kølemidlet R-134A eller R-507 og en polyolesterolie. Kølemidlet må
ikke frigives eller udledes til atmosfæren. Hvis kølemidlet kommer i kontakt med
huden, kan det give forfrysninger. Brug passende beskyttelsesbriller, og sørg for
at beskytte huden. Modulopbyggede køleenheder er hermetisk lukkede og må
hverken åbnes eller vedligeholdes.

Denne meddelelse opfylder betingelserne i EU-forordning 842/2006 om visse

flourholdige drivhusgasser. Dette produkt indeholder fluorholdige drivhusgasser,
som er omfattet af Kyoto-protokollen.

I henhold til bilag I, del 1 i EU-forordning 842/2006 er det globale opvarmnings-

potentiale for R-134A 1300. Hvis systemet er et z10 EC-system, indeholder hvert
system 4,54 kg R-134A. Hvis systemet er et z9 EC- eller et z990-system,
indeholder hver enhed 1,22 kg R-134A. Hvis systemet er en Parallel Enterprise
Server - generation 4, 5 eller 6, indeholder hver enhed 0,76 kg R-134A.

I henhold til bilag I, del 2 i EU-forordning 842/2006 er det globale opvarmnings-

potentiale for R-507 beregnet til 3850. Hvis systemet er et z900-system,
indeholder hver enhed 0,94 kg R-507.

xii Support Element Operations Guide

See server sisaldab ühte või mitut mooduljahutusseadet, mis sisaldavad
külmutusagensit R-134A või R-507 ja polüesterõli. Külmutusagens ei tohi sattuda
atmosfääri. Külmutusagensi kokkupuute korral nahaga võib tekkida
külmakahjustus. Kandke asjakohast silmi ja nahka kaitsvat riietust.
Mooduljahutusseadmed on hermeetiliselt suletud ja neid ei tohi avada ega
remontida.

Käesolev teave on esitatud vastavalt Euroopa Liidu (EL) määrusele 842/2006

fluoritud kasvuhoonegaaside kohta. See seade sisaldab Kyoto protokolliga
hõlmatud fluoritud kasvuhoonegaase.

Vastavalt EL-i määruse 842/2006 I lisa 1. osale on külmutusagensi R-134A

globaalse soojenemise potentsiaal 1300. Kui serveriks on z10 EC, sisaldab iga
server 4,54 kg külmutusagensit R-134A. Kui serveriks on z9 EC või z990,
sisaldab iga seade 1,22 kg külmutusagensit R-134A. Kui kasutatakse serveri
Parallel Enterprise Server versioone 4, 5 või 6, sisaldab iga seade 0,76 kg
külmutusagensit R-134A.

Vastavalt EL-i määruse 842/2006 I lisa 2. osale on külmutusagensi R-507

globaalse soojenemise potentsiaal 3850. Kui serveriks on z900, sisaldab iga
seade 0,94 kg külmutusagensit R-507.

Safety and environmental notices xiii

 Tämä järjestelmä sisältää yhden tai useita modulaarisia jäähdytysyksiköitä, joissa
käytetään joko R-134A- tai R-507-jäähdytysainetta ja polyoliesteriä (POE). Tätä
jäähdytysainetta ei saa päästää ilmakehään. Ihokosketus jäähdytysaineen
kanssa voi aiheuttaa paleltumia. Käytä asianmukaisia silmäsuojaimia ja
suojavaatetusta. Modulaariset jäähdytysyksiköt ovat ilmatiiviisti suljettuja eikä
niitä saa avata tai huoltaa.

Tämä ohje on fluorattuja kasvihuonekaasuja koskevan EU:n säädöksen 842/2006

edellyttämä ilmoitus. Tämä tuote sisältää Kioton sopimuksen piiriin kuuluvia
fluorattuja kasvihuonekaasuja.

EU:n säädöksen 842/2006 liitteen I osan 1 mukaan R-134A-jäähdytysaineen

lämmitysvaikutus (GWP) on 1300. Jos järjestelmä on z10 EC -järjestelmä, kukin
järjestelmä sisältää 4,54 kiloa
R-134A-jäähdytysainetta. Jos järjestelmä on z9 EC- tai z990-järjestelmä, kukin
yksikkö sisältää 1,22 kiloa R-134A-jäähdytysainetta. Jos järjestelmä on
sukupolven 4, 5 tai 6 Parallel Enterprise Server -palvelin, kukin yksikkö sisältää
0,76 kiloa R-134A-jäähdytysainetta.

EU:n säädöksen 842/2006 liitteen I osan 2 mukaisesti laskettu R-507-

jäähdytysaineen kokonaislämmitysvaikutus (GWP) on 3850. Jos järjestelmä on
z900-järjestelmä, kukin yksikkö sisältää 0,94 kiloa R-507-jäähdytysainetta.

Ce système comporte une ou plusieurs unités modulaires de réfrigération

utilisant le réfrigérant R-134A ou R-507 et une huile à base d'ester de polyol. Ce
réfrigérant ne doit pas être libéré ou ventilé dans l'atmosphère. Le réfrigérant est
très froid et peut causer des gelures. Portez une protection appropriée pour les
yeux et pour la peau. Les unités de réfrigération modulaires sont scellées
hermétiquement et ne doivent pas être ouvertes ou réparées.

La présente notice est fournie conformément au Règlement de l'Union

européenne (UE) n° 842/2006 sur les gaz à effet de serre fluorés. Ce produit
contient des gaz à effet de serre fluorés contrôlés en vertu du protocole de Kyoto.

D'après l'Annexe I, Partie 1 du Règlement de l'UE n° 842/2006, le potentiel de

réchauffement planétaire du R-134A est de 1300.Si le système est un z10 EC,
chaque système contient 4,54 kg de R-134A. Si le système est un z9 EC ou un
z990, chaque unité contient 1,22 kg de R-134A. Si le système est un Parallel
Enterprise Server de génération 4, 5 ou 6, chaque unité contient 0,76 kg de R-
134A.

D'après l'Annexe I, Partie 2 du Règlement de l'UE n° 842/2006, le potentiel de

réchauffement planétaire du R-507 est calculé à 3850. Si le système est un z900,
chaque système contient 0,94 kg de R-507.

xiv Support Element Operations Guide

Αυτό το σύστημα περιέχει μία ή περισσότερες αρθρωτές μονάδες ψύξης που
χρησιμοποιούν ψυκτικό R-134A ή R-507 και ένα έλαιο από εστέρες πολυόλης.
Αυτό το ψυκτικό δεν πρέπει να εκλυθεί στην ατμόσφαιρα. Η επαφή του ψυκτικού
με το δέρμα μπορεί να προκαλέσει κρυοπαγήματα. Πρέπει να φοράτε τα
κατάλληλα προστατευτικά ματιών και δέρματος. Οι αρθρωτές μονάδες ψύξης
είναι ερμητικά σφραγισμένες. Μην τις ανοίξετε και μην επιχειρήσετε να εκτελέσετε
εργασίες συντήρησης με τις μονάδες αυτές.

Αυτή η προειδοποίηση παρέχεται στα πλαίσια του Κανονισμού 842/2006 της

Ευρωπαϊκής Ένωσης που αφορά τα φθοριούχα αέρια που προκαλούν το
φαινόμενο του θερμοκηπίου. Το παρόν προϊόν περιέχει φθοριούχα αέρια που
συμβάλλουν στην ενίσχυση του φαινομένου του θερμοκηπίου και υπόκεινται στο
Πρωτόκολλο του Κυότο.

Σύμφωνα με το Παράρτημα I, Μέρος 1, του Κανονισμού 842/2006 της

Ευρωπαϊκής Ένωσης, η τιμή της δυνατότητας πλανητικής θέρμανσης για το
ψυκτικό R-134A είναι 1300. Στο σύστημα z10 EC, κάθε σύστημα περιέχει 4,54
κιλά ψυκτικού R-134A. Στο σύστημα z9 EC, κάθε μονάδα περιέχει 1,22 κιλά
ψυκτικού R-134A. Στο σύστημα Parallel Enterprise Server - Generation 4, 5 ή 6,
κάθε μονάδα περιέχει 0,76 κιλά ψυκτικού R-134A.

Σύμφωνα με το Παράρτημα I, Μέρος 2, του Κανονισμού 842/2006 της

Ευρωπαϊκής Ένωσης, η τιμή της δυνατότητας πλανητικής θέρμανσης για το
ψυκτικό R-507 έχει υπολογιστεί ότι είναι 3850. Στο σύστημα z900, κάθε μονάδα
περιέχει 0,94 κιλά ψυκτικού R-507.

Dieses System enthält mindestens eine modulare Kühleinheit (MRU) entweder

mit dem Kühlmittel R-134A oder R-507 sowie einem Polyolester-Öl. Dieses
Kühlmittel darf nicht in die Atmosphäre freigesetzt oder entlüftet werden. Der
Hautkontakt mit Kältemitteln kann Erfrierungen verursachen. Entsprechende
Schutzbekleidung und Schutzbrille sind zu tragen. Modulare Kühleinheiten sind
hermetisch verschlossen und dürfen nicht geöffnet oder gewartet werden.

Dieser Hinweis wird gemäß der Verordnung (EG) Nr. 842/2006 über bestimmte
fluorierte Treibhausgase angegeben. Dieses Produkt enthält fluorierte Treibhaus-
gase, die unter das Kyoto-Protokoll fallen.

Gemäß Anhang I, Teil 1 der Verordnung (EG) Nr. 842/2006 beträgt das Treib-
hauspotenzial von R-134A 1300. Wenn es sich um ein System vom Typ z10 EC
handelt, enthält jedes System 4,54 kg R-134A. Wenn es sich um ein System
vom Typ z9 EC oder z990 handelt, enthält jede Einheit 1,22 kg R-134A. Wenn
es sich um ein System vom Typ "Parallel Enterprise Server", Generation 4, 5
oder 6 handelt, enthält jede Einheit 0,76 kg R-134A.

Gemäß Anhang I, Teil 2 der Verordnung (EG) Nr. 842/2006 wurde das Treibhaus-
potenzial von R-507 mit 3850 berechnet. Wenn es sich um ein System vom
Typ z900 handelt, enthält jede Einheit 0,94 kg R-507.

Safety and environmental notices xv

 Questo sistema contiene uno o più Modular Refrigeration Unit (MRU) con
refrigerante R-134A o R-507 e un olio estere di poliolo. Questo refrigerante non
deve essere disperso nell’atmosfera. Il contatto della pelle con il refrigerante può
causare congelamento. Indossare una protezione adeguata per gli occhi e la
pelle. I Modular Refrigeration Unit sono sigillati ermeticamente e non devono
essere aperti o sottoposti ad interventi di manutenzione.

Questo avviso viene fornito in accordo con il Regolamento dell’Unione europea

(UE) 842/2006 sui gas fluorurati ad effetto serra. Questo prodotto contiene gas
fluorurati ad effetto serra contemplati nel Protocollo di Kyoto.

Per l’Allegato I, Parte 1, del Regolamento UE 842/2006, il potenziale di

riscaldamento globale di R-134A è 1300. Se il sistema è un z10 EC, ogni
sistema contiene 4,54 kg di R-134A. Se il sistema è un z9 EC o un z990, ogni
unità contiene 1,22 kg di R-134A. Se il sistema è un Parallel Enterprise Server -
Generation 4, 5 o 6, ogni unità contiene 0,76 kg di R-134A.

Per L’Allegato I, Parte 2, del Regolamento UE 842/2006, il potenziale di

riscaldamento globale di R-507 si ritiene sia 3850. Se il sistema è un z900, ogni
unità contiene 0,94 kg di R-507.

xvi Support Element Operations Guide

Šajā sistēmā ir viens vai vairāki modulāri dzesēšanas elementi ar aukstumnesēju
R-134A vai R-507 un poliolu estera eļļu. Šo aukstumnesēju nedrīkst izlaist vai
izvēdināt atmosfērā. Saskaroties ar ādu, aukstumnesējs var radīt apsaldējumu.
Lietojiet atbilstošus acu un ādas aizsarglīdzekļus. Modulārie dzesēšanas
elementi ir hermētiski noslēgti, un tos nedrīkst atvērt vai apkalpot.

Šis paziņojums sniegts saskaņā ar Eiropas Savienības (ES) Regulu 842/2006

par fluorētām siltumnīcefekta gāzēm. Šajā produktā ir fluorētas siltumnīcefekta
gāzes, kas minētas Kioto protokolā.

Saskaņā ar ES Regulas 842/2006 I pielikuma 1. daļu R-134A globālās sasilšanas

potenciāls ir 1300. Ja sistēma ir z10 EC, katrā sistēmā ir 4,54 kg R-134A. Ja
sistēma ir z9 EC vai z990, katrā elementā ir 1,22 kg R-134A. Ja sistēma ir 4., 5.
vai 6. paaudzes Parallel Enterprise Server, katrā elementā ir 0,76 kg R-134A.

Saskaņā ar ES Regulas 842/2006 I pielikuma 2. daļu R-507 globālās sasilšanas

potenciālam pēc aprēķina jābūt 3850. Ja sistēma ir z900, katrā elementā ir 0,94
kg R-507.

Šioje sistemoje yra vienas ar daugiau modulinių aušinimo įrenginių, naudojančių

aušinimo medžiagą R-134A arba R-507 ir poliesterio alyvą. Ši aušinimo
medžiaga neturi patekti arba būti išlieta į atmosferą. Aušinimo medžiaga gali
sukelti odos nušalimus. Užsidėkite tinkamus akinius ir dėvėkite apsauginius
drabužius. Moduliniai aušinimo įrenginiai yra hermetiškai uždaryti, jų negalima
atidaryti arba prižiūrėti.

Šis įspėjimas atitinka Europos Sąjungos (ES) reglamentą 842/2006 dėl fluorintų
šiltnamio efektą sukeliančių dujų. Šiame produkte yra fluorintų šiltnamio efektą
sukeliančių dujų, nurodytų Kyoto protokole.

Pagal ES reglamento 842/2006 I priedo 1 dalį medžiagos R-134A globalinio

atšilimo potencialas yra 1300. Jei sistema yra „z10 EC“, kiekvienoje sistemoje
yra 4,54 kg medžiagos R-134A. Jei sistema yra „z9 EC“ arba „z990“,
kiekviename įrenginyje yra 1,22 kg medžiagos R-134A. Jei sistema yra 4, 5 arba
6 kartos „Parallel Enterprise Server“, kiekviename įrenginyje yra 0,76 kg
medžiagos R-134A.

Pagal ES reglamento 842/2006 I priedo 2 dalį apskaičiuotas medžiagos R-507

globalinio atšilimo potencialas yra 3850. Jei sistema yra „z900“, kiekviename
įrenginyje yra 0,94 kg medžiagos R-507.

Safety and environmental notices xvii

 System zawiera co najmniej jeden moduł chłodzący z czynnikiem chłodzącym
R-134A lub R-507 oraz olejem poliestrowym. Nie można dopuścić do wydostania
się czynnika chłodzącego do atmosfery. W przypadku kontaktu ze skórą może
on spowodować odmrożenia. Należy odpowiednio chronić oczy i skórę przed
jego działaniem. Moduł chłodzący jest hermetycznie zamknięty; nie wolno go
otwierać ani naprawiać.

Informacja ta jest udostępniana zgodnie z Rozporządzeniem (WE) nr 842/2006

Parlamentu Europejskiego i Rady w sprawie niektórych fluorowanych gazów
cieplarnianych. Produkt ten zawiera fluorowane gazy cieplarniane, o których
mowa w Protokole z Kioto.

Zgodnie z Załącznikiem I, Część 1 Rozporządzenia (WE) nr 842/2006,

współczynnik ocieplenia globalnego R-134A wynosi 1300. Każdy egzemplarz
systemu z10 EC zawiera 4,54 kg czynnika R-134A. Każdy egzemplarz systemu
z9 EC lub z990 zawiera 1,22 kg R-134A. Każdy serwer Parallel Enterprise Server
- generacja 4, 5 lub 6 zawiera 0,76 kg R-134A.

Zgodnie z Załącznikiem I, Część 2 Rozporządzenia (WE) nr 842/2006,

współczynnik ocieplenia globalnego R-507 wynosi 3850. Każdy egzemplarz
systemu z900 zawiera 0,94 kg R-507.

Este sistema contém uma ou mais unidades de refrigeração modular com o

refrigerante R-134A ou R-507 e óleo poliolester. Este refrigerante não deve ser
libertado na atmosfera nem entrar em contacto com o ar. O contacto do
refrigerante com a pele pode causar queimaduras. Utilize vestuário e protecção
ocular adequados. As unidades de refrigeração modular são seladas
hermeticamente e não devem ser abertas nem deve ser efectuada qualquer
manutenção.

Este aviso é fornecido em conformidade com o regulamento 842/2006 da União

Europeia (UE) sobre gases de estufa fluorinados. Este produto contém gases de
estufa fluorinados abrangidos pelo Protocolo de Quioto.

De acordo com o Anexo I, Parte 1, do regulamento 842/2006 da UE, o potencial

de aquecimento global do R-134A é de 1300. Se o sistema for um z10 EC, cada
sistema contém 4,54 kg de R-134A. Se o sistema for um z9 EC ou z990, cada
unidade contém 1,22 kg de R-134A. Se o sistema for um Parallel Enterprise
Server - Generation 4, 5, ou 6, cada unidade contém 0,76 kg de R-134A.

De acordo com o Anexo I, Parte 2, do regulamento 842/2006 da UE, o potencial

de aquecimento global do R-507 estima-se nos 3850. Se o sistema for um z900,
cada unidade contém 0,94 kg de R-507.

xviii Support Element Operations Guide

Acest sistem conţine una sau mai multe unităţi de răcire cu refrigerent R-134A
sau R-507 şi ulei poliol-ester. Nu este permisă eliberarea acestui refrigerent în
atmosferă. Dacă se produce un contact între piele şi refrigerent, pot apărea
degerături. Purtaţi echipament de protecţie corespunzător pentru ochi şi piele.
Unităţile de răcire modulare sunt etanşe şi nu este permisă deschiderea sau
întreţinerea lor.

Acest anunţ este furnizat în conformitate cu Regulamentul UE 842/2006 privind

gazele fluorurate cu efect de seră. Acest produs conţine gaze fluorurate cu efect
de seră reglementate de Protocolul de la Kyoto.

În conformitate cu Anexa I, Partea 1 a Regulamentului 842/2006, potenţialul de

încălzire globală al refrigerentului R-134A este 1300. Dacă sistemul este un z10
EC, fiecare sistem conţine 4,54 kg de refrigerent R-134A. Dacă sistemul este un
z9 EC sau z990, fiecare unitate conţine 1,22 kg de refrigerent R-134A. Dacă
sistemul este un Parallel Enterprise Server - Generaţia 4, 5 sau 6, fiecare unitate
conţine 0,76 kg de refrigerent R-134A.

În conformitate cu Anexa I, Partea a 2-a a Regulamentului UE 842/2006,

potenţialul de încălzire globală al refrigerentului R-507 are valoarea calculată
3850. Dacă sistemul este un z900, fiecare unitate conţine 0,94 kg de refrigerent
R-507.

Tento systém obsahuje jednu alebo viac chladiacich jednotiek s chladiacou

náplňou R-134A alebo R-507 a polyol-esterovým olejom. Chladiaca náplň
nesmie byť uvoľnená do atmosféry. Kontakt s pokožkou môže spôsobiť omrzliny.
Kvôli ochrane používajte pri manipulácii okuliare a rukavice. Modulárne
chladiace jednotky sú hermeticky uzavreté a nesmú byť otvorené ani
opravované.

Toto vyhlásenie je v súlade s normou European Union (EU) Regulation 842/2006

o plynoch spôsobujúcich skleníkový efekt. Tento produkt obsahuje plyny
spôsobujúce skleníkový efekt, ktoré stanovuje Kjótsky protokol.

Podľa dodatku I, časť 1, normy EU Regulation 842/2006, potenciál globálneho

otepľovania pre chladiacu náplň R-134A je 1300. V systéme z10 EC obsahuje
každá jednotka 4,54 kg chladiacej náplne R-134A. V systéme z9 EC alebo z990
obsahuje každá jednotka 1,22 kg chladiacej náplne R-134A. V systéme Parallel
Enterprise Server - generácia 4, 5 alebo 6, obsahuje
každá jednotka 0,76 kg chladiacej náplne R-134A.

Podľa dodatku I, časť 2, normy EU Regulation 842/2006, potenciál globálneho

otepľovania pre chladiacu náplň R-507 je 3850. V systéme z900 obsahuje každá
jednotka 0,94 kg chladiacej náplne R-507.

Safety and environmental notices xix

 Ta sistem vsebuje eno ali več modularnih hladilnih enot s hladilnim sredstvom R-
134A ali R-507 in poliol estrovo olje. Tega hladilnega sredstva ni dovoljeno
izpuščati ali odvajati v ozračje. Stik kože s hladilnim sredstvom lahko povzroči
ozebline. Uporabite ustrezno zaščito za oči in kožo. Modularne hladilne enote so
hermetično zapečatene; njihovo odpiranje ali vzdrževanje ni dovoljeno.

Ta opomba je ponujena v skladu s predpisom 842/2006 Evropske unije (EU) v

zvezi s toplogrednimi plini z vsebnostjo fluora. Ta izdelek vsebuje toplogredne
pline z vsebnostjo fluora, ki so vključeni v Kyotski protokol.

Glede na 1. del dodatka I predpisa EU 842/2006 je potencial za globalno

segrevanje, povezan z R-134A, 1300. Če gre za sistem z10 EC, vsebuje vsak
sistem 4.54 kg R-134A. Če gre za sistem z9 EC ali z990, vsebuje vsaka enota
1.22 kg R-134A. Če gre za vzporedni strežnik Parallel Enterprise Server
generacije 4, 5 ali 6, vsebuje vsaka enota 0.76 kg R-134A.

Glede na 2. del dodatka I predpisa EU 842/2006 je izračun potenciala za

globalno segrevanje, povezan z R-507, 3850. Če gre za sistem z900, vsebuje
vsaka enota 0.94 kg R-507.

Este sistema contiene una o varias unidades de refrigeración modular con

refrigerante R-134A o R-507 y aceite poliol-éster. Este refrigerante no se debe
liberar en la atmósfera. El contacto de la piel con el refrigerante puede causar
congelación. Use una protección adecuada para ojos y piel. Las unidades de
refrigeración modular están cerradas herméticamente y no se deben abrir ni se
les debe realizar ningún mantenimiento.

Este aviso se proporciona conforme al Reglamento (CE) n.º 842/2006 del

Parlamento Europeo y del Consejo sobre la reducción de los gases fluorados de
efecto invernadero. Este producto contiene gases fluorados de efecto
invernadero que quedan cubiertos por el Protocolo de Kyoto.

De acuerdo con el Anexo I, Sección 1, de la Regulación europea 842/2006, el

potencial de calentamiento global del R-134A es 1300. Si el sistema es un z10
EC, cada sistema contiene 4,54 kg de R-134A. Si el sistema es un z9 EC o
z990, cada unidad contiene 1,22 kg de R-134A. Si el sistema es un Parallel
Enterprise Server - Generación 4, 5 o 6, cada unidad contiene 0,76 kg de R-
134A.

De acuerdo con el Anexo I, Sección 2, de la Regulación europea 842/2006, el

potencial de calentamiento global del R-507 se calcula en 3850. Si el sistema es
un z900, cada unidad contiene 0,94 kg de R-507.

xx Support Element Operations Guide

 Systemet innehåller minst en modulär kylningsenhet med kylmediet R-134A
eller R-507 och en polyolesterolja. Kylmediet får inte släppas eller ventileras ut
i atmosfären. Kylmediet kan orsaka köldskador vid hudkontakt. Använd lämplig
skyddsutrustning för ögon och hud. Modulära kylningsenheter är hermetiskt
tillslutna och får inte öppnas eller utföras underhåll på.

Detta meddelande tillhandahålls i enlighet med EU-direktiv 842/2006 avseende

fluorinerade växthusgaser. Utrustningen innehåller växthusgaser med fluor vilka
täcks av Kyoto-protokollet.
Enligt bilaga I, del 1 i EU-direktiv 842/2006 har R-134A en potential för global
uppvärmning på 1300. Om systemet är en z10 EC innehåller varje enhet 4,54 kg
R-134A. Om systemet är en z9 EC eller z990 innehåller varje enhet 1,22 kg
R-134A. Om systemet är en Parallel Enterprise Server - generation 4, 5 eller 6
innehåller varje enhet 0,76 kg R-134A.

Enligt bilaga I, del 2 i EU-direktiv 842/2006 beräknas R-507 ha en potential för

global uppvärmning på 3850. Om systemet är en z900 innehåller varje enhet
0,94 kg R-507.

Bu sistem, R-134A ya da R-507 soğutma gazı ve polyol ester yağı içeren modüler
bir ya da daha çok soğutma birimini içerir. Bu soğutma gazı atmosfere
yayılmamalıdır. Ayrıca, cildin gazla teması vücutta soğuk ısırmasına neden
olabilir. Gözünüzü ve cildinizi korumak için uygun koruma araçları kullanın.
Modüler soğutma birimleri hava geçirmez bir biçimde mühürlenmiştir ve
açılmamalıdır. Ayrıca, bu birimlere bakım yapılmamalıdır.

Bu özel bildirim, Avrupa Birliği'nin florlu sera gazına ilişkin 842/2006 numaralı
düzenlemesiyle uyumludur. Bu ürün, Kyoto Protokolü kapsamında bulunan florlu
sera gazlarını içerir.

842/2006 numaralı AB Düzenlemesi Ek 1, Bölüm 1 uyarınca, R-134A gazının

genel ısı potansiyeli 1300'dür. Sistem bir z10 EC ise, her sistem 4.54 kg R-134A
gazı içerir. Sistem bir z9 EC ya da z990 ise, her bir birim 1.22 kg R-134A gazı
içerir. Sistem bir Parallel Enterprise Server - Generation 4, 5 ya da 6 ise, her bir
birim 0.76 kg R-134A gazı içerir.

842/2006 numaralı AB Düzenlemesi Ek 1, Bölüm 2 uyarınca, R-507 gazının

genel ısı potansiyeli 3850 olarak hesaplanmıştır. Sistem bir z900 ise, her bir birim
0.94 kg R-507 gazı içerir.

Battery return program

This product may contain sealed lead acid, nickel cadmium, nickel metal hydride,
lithium, or lithium ion battery(s). 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/index.shtml or contact your local waste disposal facility.

In the United States, IBM has established a return process for reuse, recycling, or
proper disposal of used 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:

Safety and environmental notices xxi

 Please recycle batteries

For the European Union:

Notice: 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.

Les batteries ou emballages pour batteries sont étiquetés conformément aux

directives européennes 2006/66/EC, norme relative aux batteries et accumulateurs
en usage et aux batteries et accumulateurs usés. Les directives déterminent la
marche à suivre en vigueur dans l’Union Européenne pour le retour et le recyclage
des batteries et accumulateurs usés. Cette étiquette est appliquée sur diverses
batteries pour indiquer que la batterie ne doit pas être mise au rebut mais plutôt
récupérée en fin de cycle de vie selon cette norme.

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 Spain:

xxii Support Element Operations Guide

 This notice is provided in accordance with Royal Decree 106/2008. The retail price
of batteries, accumulators, and power cells includes the cost of the environmental
management of their waste.

Este aviso se proporciona de conformidad con, además de otros requisitos, el Real

Decreto español 106/2008: El precio de venta al público de las baterías, los
acumuladores y las celdas de potencia incluye el coste de la gestión de su
desecho.

For California:

Perchlorate Material - special handling may apply. See http://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, or both may include a lithium manganese dioxide
battery which contains a perchlorate substance.

Flat panel display

The fluorescent lamp or lamps in the liquid crystal display contain mercury. Dispose
of it as required by local ordinances and regulations.

Monitors and workstations

New Jersey – For information about recycling covered electronic devices in the
State of New Jersey, go to the New Jersey Department of Environmental Protection
Web site at http://www.state.nj.us/dep/dshw/recycle/Electronic_Waste/index.html.

Oregon – For information regarding recycling covered electronic devices in the

State of Oregon, go to the Oregon Department of Environmental Quality Web site at
http://www.deq.state.or.us/lq/electronics.htm.

Washington – For information about recycling covered electronic devices in the

State of Washington, go to the Department of Ecology Web site at
https://fortress.wa.gov/ecy/recycle, or telephone the Washington Department of
Ecology at 1-800-Recycle.

Safety and environmental notices xxiii

xxiv Support Element Operations Guide
Preface
This operations guide is for anyone who is responsible for monitoring and operating
the IBM System z10™ Enterprise Class (z10™ EC) and IBM System z10 Business
Class (z10 BC).

This operations guide provides information and instructions for users who use a
support element while logged on in the following default user IDs and roles:

Access Administrator ACSADMIN PASSWORD

Advanced Operator ADVANCED PASSWORD
Operator OPERATOR PASSWORD
Service Representative SERVICE SERVMODE
System Programmer SYSPROG PASSWORD

Notes:
1. There are representations of the Hardware Management Console and Support
Element windows displayed throughout this manual. They may or may not
represent the exact windows that are displayed for your user ID or version.
2. Many of the same tasks and controls that are available in the user modes listed
above are available also in the service representative user mode. This
operations guide does not provide information or instructions for using tasks and
controls available exclusively in the service representative user mode. Service
representatives should refer instead to the service documentation provided with
the system.

Support element users should be familiar with using:

v CD-ROM
v Communication devices
v Direct access storage devices (DASD)
v DVD-RAM
v Graphical user interfaces
v Printers
v USB flash memory drive (formerly referred to as the memory key)
v Workstations

Note: If you are using a USB flash memory drive, plug it into the console and then
wait for the console to beep three times. This indicates that the device is
ready and can be accessed. If it does not beep three times, unplug the
device and try again.

For information and instructions for operating devices other than the support
element, refer to the documentation provided with the devices.

How to use this guide

If you are accessing the support element console remotely through the hardware
management console using single object operations, this guide is available in
portable document format (PDF) to view or print as an online document or by
accessing Resource Link (http://www.ibm.com/servers/resourcelink).

When the PDF version of the guide opens, a list of bookmarks displays on the
left-hand side. These bookmarks display the highest level topics in the order that
they appear as chapters in the book. If any of these topics have lower level topics,

© Copyright IBM Corp. 2008 xxv

 a + is displayed to the left of the higher level topic. To expand the topic, click once
on the + and the next level will be displayed.

If you are accessing the support element console locally, this guide is available in
HTML format to view as an online document from the support element console.

To view this guide in its online form using the tree style user interface,
see“Welcome” on page 11. If you are using the classic style interface, see “Opening
an online book” on page 56.

What’s new in version 2.10.1

This guide reflects the licensed internal code for Support Element Console
Application, Version 2.10.1. You can tell if your support element console has this
version installed by looking at the title bar on the Support Element Console
Workplace window.
v Tree style user interface enhancements have been made to the tree style user
interface:
– Navigation pane tasks pad collapse and expand controls.
– Additional work pane table functions: data export, quick filter, and table
paging.
– Additional work pane table view: topology
See Chapter 2, “Using the tree style user interface,” on page 9.
v Context sensitive provides you the ability to view a brief description for each
input field or selectable field on a task window. See “Context sensitive help” on
page 6.
v Counter Facility Security Options and Sampling Facility Security Options to
Image profiles. See “Authorizing basic counter set control” on page 113.
v STP enhancements to allow the Current Time Server of an STP-only CTN to
configure the external time source to use Network Time Protocol (NTP) with a
pulse per second (PPS) signal for improved accuracy. See “Time Synchronization
features” on page 182.
v Change LPAR weights for scheduled operation allows you to change the weights
of LPARs on a scheduled basis instead of manually doing it through the Change
LPAR Controls tasks. See “Scheduled operations” on page 199.
v Change LPAR Security task counter measurement security controls. See
“Logical partition security” on page 165.
v System I/O Configuration Analyzer (SIOC) task to allow the system hardware
administrator access to the system’s I/O configuration (SIOC) information from
one place instead of obtaining it from many separate applications. The analyzer
makes it easier to manage I/O configurations. See “Viewing the input/output (I/O)
configuration data” on page 178.
v Specify Concurrent Upgrade Sync Point task to restrict specific internal code
changes from being installed and activated on the system. “Specifying a
concurrent upgrade sync point” on page 211.
v Manage Print Screen task to allow you to capture full screens or specific
windows of the support element console and save them as PNG, JPG, or GIF
files. These files can then be viewed, copied to removable media, or deleted.
See “Managing print screen files” on page 254.
v Console Messenger task to allow basic messaging capabilities between users of
the support element console and the Hardware Management Console. It also

xxvi Support Element Operations Guide

 allows messaging between local users and remote users using existing Hardware
Management Console and support element interconnection protocols. See
“Console messenger” on page 242.

There may be other changes to the system code that are not described in this
guide. Please refer to the other documents shipped with your processor for
additional information.

How to send your comments

Your feedback is important in helping to provide the most accurate and high-quality
information. Send your comments by using Resource Link at http://www.ibm.com/
servers/resourcelink. Select Feedback on the Navigation bar on the left. Be sure to
include the name of the book, the form number of the book, the version of the book,
if applicable, and the specific location of the text you are commenting on (for
example, a page number or table number).

Preface xxvii
xxviii Support Element Operations Guide
Chapter 1. Introduction
A support element is a dedicated workstation used for monitoring and operating a
system. It is attached to the central processor complex (CPC) of a system. If you
have experience using other systems, you may have used a processor console,
support processor, or a similarly named workstation to monitor and operate them.

The IBM System z10 EC and Z10 BC is an integrated support element, that is, the
support element is located inside the same frame that the central processor
complex (CPC) is located. An alternate support element is also provided to give you
the option to switch from your primary support element to your alternate support
element if hardware problems occur. For more information on the alternate support
element, see “Forcing an immediate mirroring of the primary support element to the
alternate support element” on page 211.

The z10 EC and z10 BC operates only in logically partitioned mode.

A Hardware Management Console is required for monitoring and operating systems

with integrated support elements.

The support element console application

The Support Element Console Application version 2.10.1 is a licensed application
that provides the tasks you will use to monitor and operate your system. The
application is shipped with each support element.

The version number of the Support Element Console Application is displayed in the
title bar of the Support Element Logon window and also the Support Element
Workplace window.

The Support Element Console Application starts automatically whenever the support
element is turned on or rebooted. Starting the application begins the process of
initializing it. A window displays the IBM Logo and copyright information. When the
process completes, the logon window is displayed.

The Welcome window includes links for logging on to the support element console
and to the online help. It also includes status indicators and message icons. The
status indicator reflects the current overall status of the CPC and images. The
message indicators alert you to any hardware or operating system messages. If any
of these icons do not display a green check mark, you are alerted that a message
was logged that may require your attention. See Figure 1 or an example of the
Welcome window.

© Copyright IBM Corp. 2008 1

Figure 1. support element console welcome window

To log on to the support element console, click Log on and launch the Support
Element web application from the Welcome window. The Logon window is
displayed

Figure 2. support element console logon window

Default user IDs and passwords are established as part of a base Support Element
Console. The Access Administrator should assign new user IDs and passwords for
each user and remove default user IDs as soon as the support element console is
installed by using the User Profiles task. The following default user roles, user IDs,
and passwords are:

2 Support Element Operations Guide

 Operator OPERATOR PASSWORD
Advanced Operator ADVANCED PASSWORD
System Programmer SYSPROG PASSWORD
Access Administrator ACSADMIN PASSWORD
Service Representative SERVICE SERVMODE

Note: The support element workplace is distinguished from the Hardware

Management Console workplace most notably by the title of its window and
the background pattern of the z10 EC and z10 BC.

The support element workplace is the window from where you start tasks for
monitoring and operating the CPC. Your user role determines which tasks and
controls you can use on the support element workplace. Not all tasks are available
for each user role. Refer to the description of the specific task you want to access
to see what user role(s) it is available in.

If at any time you do not know what user ID is currently logged on to the support
element console, click on the user ID located on the task bar in the tree style user
interface, or open the Users and Tasks task in the classic style user interface.

Establishing a support element console session from a Hardware

Management Console
A Hardware Management Console must be used for monitoring and operating
systems with integrated support elements.

Ordinarily, you should use the Hardware Management Console to monitor status
and perform tasks for the systems defined to it. Only the Hardware Management
Console can be used for monitoring and operating multiple systems; using it is
more efficient than using each system’s support element console individually.

Using a system’s support element console is necessary only for getting information
or using tasks that are not available from the Hardware Management Console. If
using a system’s support element console is necessary, use the Hardware
Management Console’s Single Object Operations task to establish a session with
the support element console. Upon establishing a support element session, you can
refer to this manual for information and instructions for using the support element to
monitor and operate the system it is attached to.

The Single Object Operations Task Confirmation window displays. Follow the
instructions on the Confirmation window to complete this task.

Logging off the support element console

Once you have completed your tasks on the support element, log off the console.
The Logoff or Disconnect task allows you to end the current user session and
logs off the support element console or to disconnect while your tasks continue
running. If you disconnect, you can reconnect at a later time to continue working.
However, a disconnect session is eventually ended (This is because disconnect
sessions exist only while the support element console application is running. If the
support element console is restarted or the console is shut down or rebooted, all
session information is lost).

Select the log off operation when you no longer need access to the support element
console. Logging off the console does not affect the status of the CPC or Images.
After you log off or disconnect, the Welcome to the Primary Support Element
Console window is displayed. If you chose to disconnect rather than logoff, when

Chapter 1. Introduction 3
 you logon again, the Choose a Disconnected Session window is displayed. You
can select the disconnected session to continue working or you can begin a new
session. (The number of windows displayed depends on the state of the session
when it was disconnected. One of the windows is the main user interface; additional
windows are for each task that was running when the session was disconnected.)

The support element workplace window closes and the Hardware Management
Console workplace window is displayed.

To log off the support element console:

1. Open the Logoff or Disconnect task. The Choose to Logoff or Disconnect

window is displayed.
2. Select Log off.
3. Click OK to end your session on the support element console.

To disconnect from the support element console:

1. Open the Logoff or Disconnect task. The Choose to Logoff or Disconnect
window is displayed.
2. Select Disconnect.
3. Click OK to disconnect from your session on the support element console with
the intent of returning at a later time.

User Interface (UI) styles for the support element console

The support element console allows you to choose the interface style in which you
prefer to work with:
v Tree style user interface (default)
v Classic stype user interface.(older interface with object-oriented design.

Tree style user interface

The support element concole tree style user interface is the default for Operator,
Advanced Operator, Access Administrator, and System Programmer user roles, but
not for the Service Representative user role. The tree style navigation provides
hierarchical views of system resources and tasks using drill-down and
launch-in-context techniques to enable direct access to hardware resources and
task management capabilities. It also utilizes common terminology where possible.
For example, instead of referring to CPC, a more general term of server is used for
this interface.

See Chapter 3, “Using the classic style user interface,” on page 35 if you want to
use the tree style user interface for the support element console.

Classic style user interface

The support element console classic style user interface is designed to provide
the functions you need through an object-oriented design. Through this design, you
can directly manipulate the objects that are defined to the support elment console,
and be aware of changes to hardware status as they are detected.

The classic style user interface is the original user interface of the support element
console. You can work with objects on the workplace using the mouse to select

4 Support Element Operations Guide

 them. One way to do this is to left-click an object to select it and double-click the
task. An alternate method is known and drag and drop technique. This involves
using the mouse to pick up one or more objects, dragging then to a task, and then
dropping them. These techniques are examples of what is known as direct
manipulation.

See Chapter 2, “Using the tree style user interface,” on page 9 if you want to use
the classic style user interface for the support element console.

Enabling users to change interface style

If the UI Style tab is not displayed when you open the User Settings task, then you
are not allowed to change the interface style on the support element console. Your
access administrator has the ability to enable users to change interface styles and
to change the default interface style of the support element console by performing
the following steps:
1. Log onto the support elemet on the hardware management console through
Single Object Operations in access administrator role
2. Log on the support element console using the ACSADMIN default user ID or a
user ID that has the predefined Access Administrator roles.
3. Open the Console Default User Settings task.
v Using the tree interface: Open Console Default User Settings from the SE
Management work pane.
v Using the classic interface: Open Console Actions under Views, then open
Console Default User Settings.
4. The Console Default User Settings window is displayed
5. Click the UI Style tab.
v To enable users to change the user interface style, select Allow user to
change th UI style, then click Apply.
v To control the default user interface style for the support element console,
select Tree Style or Classic Style, then click Apply
6. Click OK when you have finished.

Changing interface style

If the support element console is configured to enable you to change the user
interface style, you can change interface styles by using the User Settings task.

To change from the tree style interface back to the classic interface, perform the
following steps:
1. Log onto the support elemet on the hardware management console through
Single Object Operations in access administrator role
2. Open User Settings (from the SE Management or Task Index work panes or
click on the user ID from the task bar). The User Settings window is displayed.
3. Click the UI Style tab. The User Style Information window is displayed.
4. Select Classic Style, then click Apply.
The interface style changes to classic.

To change from the classic interface back to the tree interface, perform the following
steps:
1. Log onto the support elemet on the hardware management console through
Single Object Operations in access administrator role

Chapter 1. Introduction 5
 2. Open User Settings (under Console Actions in the classic interface). The
User Settings window is displayed.
3. Click the UI Style tab. The User Style Information window is displayed.
4. Select Tree Style, then click Apply.
5. Click OK.

Context sensitive help

Context sensitive help allows you to view abbreviated help information for input
areas or selectable fields that appear on the task window. To enable this function:
1. Click on the blue i that appears in the upper right corner of the task window.
(see ). Every time a new task window opens you need to click the blue i to
enable context sensitive help.

Figure 3. Context sensitive help not enabled

2. Once context sensitive help is enabled, the blue i in the upper right corner of
the task window changes to an orange ? . As you place your cursor over the
input areas or selectable fields, the abbreviated help text appears in a small box
within the task window (see ). Using the Tab key also allows you to view the
help for each field. As you tab to each field, context sensistive help is displayed.

Figure 4. Context sensitive help enabled

6 Support Element Operations Guide

 Notes:
a. You have the capability to move the help box if it hides some of the
information on the task window. As you move your cursor into the help box
area the cursor will change from an arrow to a yellow cross arrow. Hold the
left mouse button down within the box allowing you to drag the box to a
more convenient area in the task window.
b. You can close the help box by clicking on the X in the upper right corner.
This will not disable the context sensitive help for the task window, it just
removes the help box for the item you were getting help on.
c. Scroll bars can be used on the bottom and side ofr the task window for
expanding the task window and allowing more area to view the help box.
d. You can continue to perform task options while the context sensitive help is
enabled.
3. When you are ready ti disable context sensitive help for the task window, click
on the ?.

Disruptive tasks
Some of the support element consoel tasks are considered disruptive. Performing a
disruptive task on the CPC or its objects may disrupt its operation.

You may want to lock an object to prevent accidently performing a disruptive task
on it and then unlock the object only when you want to perform a disruptive task on
it.

For more information on locking objects see the Console Actions“Setting object
locking” on page 257.

USB flash memory drive

The support element console version 2.10.0 and later is no longer provided with a
diskette drive. The available media is DVD-RAM, CD-ROM, and USB flash memory
drive (formerly referred to as the memory key).

Note: If you are using a USB flash memory drive, plug it into the console. If it is
properly inserted, the console beeps three times and a message is displayed
indicating the drive was successfully added. The device is ready and can be
accessed. Otherwise, the console will not beep three times and a message
is displayed indicating the drive was not added and that you should remove
the device and try again.

The supported USB flash memory drives included:

v IBM USB 2.0 High Speed Memory Key - 128MB (part number (22P9229)
v Lenovo USB 2.0 Memory Key - 512MB (part number 40Y8596)
v Lenovo USB 2.0 Security Memory Key - 1GB (part number 41U5118).

Chapter 1. Introduction 7
8 Support Element Operations Guide
Chapter 2. Using the tree style user interface
This chapter explains how to use the tree style user interface to perform tasks on
the support element console or on the system resources. The tree style user
interface is comprised of several major components as shown in Figure 5: the
banner, the task bar, the navigation pane, the work pane, and the status bar.

The banner, across the top of the workplace window, identifies the product and
logo. Use the User Settings task to turn the banner on or off.

The task bar, located below the banner, displays the name of any tasks that are
running, the user ID you are logged in as, online help information, and a link to
logoff or disconnect from the console.

The navigation pane, in the left portion of the window, contains the primary
navigation links for managing your system resources and the support element
console. The items are referred to as nodes. Displayed above the navigation pane
is the navigation toolbar.

The work pane, in the right portion of the window, displays information based on the
current selection from the navigation pane or status bar. For example, when
Welcome is selected in the navigation pane, the Welcome window content is
displayed in the work pane, as shown in Figure 5.

The status bar, in the bottom left portion of the window, provides visual indicators of
current overall system status. It also contains a status overview icon which may be
selected to display more detailed information in the work pane.

Figure 5. Tree style user interface support element console workplace window

© Copyright IBM Corp. 2008 9

 You can resize the panes of the support element console workplace by moving the
mouse pointer over the border that separates the navigation pane from the work
pane until the mouse pointer changes to a double-pointed arrow. When the pointer
changes shape, press and hold the left mouse button while dragging the mouse
pointer to the left or right. Release the button and your navigation pane or work
pane is now larger or smaller in size. You can also do this within the Systems
Management work pane border that separates the resources table from the tasks
pad.

Task bar

Figure 6. Task bar

The task bar, located below the banner, provides the capability of an active task
switcher. The task bar may be used as a navigation aid to move between tasks that
were opened and have not yet been closed. The task switcher does not pause or
resume existing tasks. Clicking on a task in the task bar brings that task’s window
forward and gives it focus. The right end of the task bar also contains the following
information as shown in Figure 6.
v user ID that you are logged in as. By clicking the user ID you launch the User
Settings task.
v Help initially displays information on how to use the tree style user interface on
the support element console. It also provides information on all the support
element console tasks.
v Logoff launches the Logoff or Disconnect task.

Navigation pane
The navigation pane, as shown in Figure 5 on page 9, contains the primary
navigation links for managing your system resources and the support element
console. These include:
v Welcome
v System management
v SE management
v Service management.
v Tasks index

It also includes the following navigation methods you can use when working the
tree style workplace:
v Navigation toolbar
v Navigation pane collapse/expand controls

Navigation pane collapse/expand controls

The navigation pane collapse and expand controls are provided on the border
between the navigation pane and the work pane. You can click on these controls to
collapse or expand the navigation pane allowing you more work area in the work

10 Support Element Operations Guide

 pane, if required. Hovering over these controls indicates whether you will be hiding
or displaying the navigation pane. You can see an example of these controls in
Figure 7 on page 12.

Navigation toolbar

The navigation toolbar, located above the navigation pane, consists of:
v Forward and backward buttons that allow you to move forward and backward in
the selection history for the work pane.
v Home page and set home page buttons that allow you to return to the home
page during your session and establish a home page to return to every time you
log on to the support element console.
v Expand and collapse buttons that allow you to expand and collapse all of the
nodes of the navigation pane.

You can point your mouse over the icon buttons to get a description of the function.

Welcome
Welcome work pane displays navigation information, the support element console
version information, and other helpful documentation (see Figure 5 on page 9 ).

To see the level of the support element console you are currently working with and
other information, point your mouse over SE Version found at the top of the work
pane.

Additional Resources include:

v Online Information provides a listing of the following online resources. Click on
each item to access them.

Note: This information is only available when you are accessing the support
element console remotely.
– Resource Link as a Web-based solutions site for more information on
planning, installing, and maintaining System z servers and software.
– Online Education for education on training and updating your support
element console skills.
– Tutorials for additional information on using the support element console tree
style user interface.
v Library to open the following online books provided with the support element
console application:

Note: If you are accessing the support element remotely, a PDF version of the
document is available. If you are accessing the support element locally, an
HTML version of the document is available.
– Application Programming Interfaces provides information for developing
system management applications that will provide integrated hardware and
software system management solutions using the application programming
interfaces.
– Support Element Operations Guide is the publication you are currently using.
It provides information about the Support Element Console Application and
about using the support element workplace to monitor and operate your
system.

Chapter 2. Using the tree style user interface 11

Systems management

Systems Management contains a tree view of system resources. Resources may

include:
v CPC
v Central processors (CP)
v Channels
v Cryptos
v Partitions
v Custom groups.

Locating groups and objects

Use the navigation pane to locate objects. Objects are divided into groups of
objects of the same type. To locate a particular object, you must locate and open
the group that contains it. Opening a group displays its object in the work pane.

Figure 7. Systems management object window

Locating the CPC: The CPC node represents the CPC that has been defined for
this support element console. Tasks cannot be performed on a CPC until it is
activated.

When you select the CPC from the navigation pane a listing of hardware resources
for the CPC are displayed in table form in the work pane and under the CPC node
in the navigation pane, as shown in Figure 7. To work with the CPC, you can
perform one of the following actions:
v Select the CPC name in the navigation pane
v Click in the Select column next to the CPC name in the work pane table.

Locating central processors (CPs): On the support element, both physical and
logical processors are referred to as central processors (CPs). When you click the
CPC from the navigation pane, the Processors node displays under the CPC, as

12 Support Element Operations Guide

shown in Figure 7 on page 12. To work with the CPs, select the Processors node
in the navigation pane. A listing of CPs is displayed in table form in the work pane.
The table identifies the ID, status, and state of each CP.

Locating channels: The object that represents the server (CPC) contains objects
that represent all channels configured and not configured in the input/output (I/O)
configuration. When you click the CPC from the navigation pane, the Channels
node displays under the CPC, as shown in Figure 7 on page 12. To work with the
channels, select the Channels node in the navigation pane. A listing of channels is
displayed in table form in the work pane. The table identifies the physical channel
identifier (PHICD), CSS.CHPID, status, state, hardware type, and how the CHPID is
defined in the IOCDS.

Locating cryptos: The object that represents the server (CPC) contains objects
that represent all channel paths defined in its input/output (I/O) configuration. When
you click the CPC from the navigation pane, the Crypto node displays under the
CPC, as shown in Figure 7 on page 12. To work with the crypto, select the Crypto
node in the navigation pane. A listing of cryptos is displayed in table form in the
work pane. The table identifies the crypto ID, physical channel identifier (PHICD),
status, state, and crypto type.

Locating logical partitions: When the CPC is activated, the Partitions node,
contains objects that represent the logical partitions. Logical partitions are referred
to also as images. An image is a set of server (CPC) resources capable of running
a control program or operating system. When you click the CPC from the navigation
pane, the Partitions node displays under the CPC, as shown in Figure 7 on page
12. To work with the partitions, select the Partitions node in the navigation pane. A
listing of logical partitions is displayed in table form in the work pane. The table
identifies the logical partition name, status, CP status, CHPID status, activation
profile, and image mode.

Custom groups: Groups are comprised of logical collections of objects. You can
report status on a group basis, allowing you to monitor your system in a way that
you prefer.

The Custom Groups node includes any user-defined groups that your created
using the Grouping task.

You can select a group from the custom groups work pane table and perform tasks
on the objects in that group by clicking in the Select column on that group and then
choosing a task from the tasks pad.

User-defined groups: There may be one or more user-defined groups already

defined on your support element console. You can use the Grouping task under the
Daily group on the tasks pad to create your own group that you want to work with.
This task allows you to create new groups and manage existing ones.

To create a group you can:

1. Select one or more objects that you want to include in the group you want to
work with.
2. Open the Grouping task from the Daily tasks pad.
The Manage Groups window is displayed.
3. Select Create a new group from the Manage Group window.
4. Specify a group name and description.
5. Click OK to complete.

Chapter 2. Using the tree style user interface 13

 6. The new user-defined group appears in the navigation pane under the Custom
Groups node.

You can also create a group by using the pattern match method:
1. Without selecting an object you can open the Grouping task from the Custom
Groups or System Management task pad. The Create Pattern Match Group
window is displayed.
2. Select one or more group types that you want to create from the Create Pattern
Match Group window.
3. Select the type of group you want to create from the Create Pattern Match
Group window.
4. Specify a group name, description, and the pattern used to determine if an
object should be part of the group.
5. Click OK on the Create a New Group window to complete.
6. The new user-defined group is displayed in the navigation pane under the
Custom Groups node.

Online Help is available for more information on grouping.

Opening tasks
The available task group depends on the object selected from the navigation pane
(CPC, CP, channels, cryptos, partitions). Task groups are simple categorization
nodes and are not tasks themselves. The following is the task groups that may be
available for the CPC:
Daily
CPC Recovery
Service
Change Management
CPC Remote Customization
CPC Operational Customization
CPC Configuration
CHPID Operations
Channel Operations
Crypto Service Operations.

You can select a task from these task groups in a variety of ways. Appropriate tasks
for selected objects are listed in the tasks pad, in context menus, and in the tasks
drop-down menu.

Note: With this interface if a particular task cannot be performed on an object the
task will not appear.

Tasks pad: The tasks pad appears below the work pane after you have selected
the object(s) with which you want to work with (See Figure 8 on page 15). This view
contains available tasks for selected managed object(s).
Notes:
1. Resize the tasks pad by moving the mouse pointer over the border that
separates the work pane table from the tasks pad.
2. Optionally, display the tasks pad by using the User Settings task. You can use
the collapse and expand controls that are provided on the border between the
tasks pad and the work pane. You can click on these controls to collapse or
expand the tasks pad allowing you more work area in the work pane, if
required. Hovering over these controls indicates whether you will be hiding or
displaying the tasks pad.

14 Support Element Operations Guide

 3. Expand or collapse all the task groups in the tasks pad by selecting the Expand
All icon or the Collapse All icon from the tasks pad heading.
4. Organize the tasks pad display by using the Settings icon from the tasks pad
heading. This option allows you to arrange the displayed tasks in a viewing
format you prefer.

Figure 8. Tasks pad

The tasks contained in this view meet the following characteristics:

v Tasks are available for the currently selected target object(s) in the navigation
pane tree or the work pane table view. If multiple objects are selected in the work
pane table, the intersection of the selected objects’ tasks is displayed. If there are
no selections in the table, tasks are displayed for the object selected in the
navigation pane.
v Tasks available by the role of the user currently logged in.

An example of using the tasks pad method:

v Select the CPC in the work pane table (click in the Select column).
v Select a task group from the tasks pad (click in the expand button or click on the
group name).

Note: After you have expanded the task groups those groups remain open so
that you can repeatedly open other tasks without having to reopen the
task groups again.
v Select a task that is displayed under the task group that you want to perform on
that CPC.
v The task window is displayed.

Context menus: The context menu is a pop-up menu that lists the task groups
appropriate for the selected object. Context menus are only available for table
selections. For example, in the Select column of the CPC work pane table select
the object(s) you want to work with. The context menu button (double right arrows)

Chapter 2. Using the tree style user interface 15

 is displayed next to the object name you have selected. Click the button and the
task groups menu is displayed for that particular object, as shown in Figure 9. Then
select a task to open for the object. If more than one object is selected, the tasks
that are displayed in the context menu apply to all selections.

Figure 9. Context menu

Task menu: The task menu is displayed on the work pane table toolbar that
appears on the table toolbar, as shown in Figure 10 on page 17. The tasks menu is
only available for table selections. For example, in the Select column of the CPC
work pane table, select the object(s) you want to work with. Click Tasks for the list
of the applicable task groups for the selected objects in the table. Select a task
group, then select a task to open for the object. If more than one object is selected,
the tasks that are displayed in the tasks menu apply to all selections.

16 Support Element Operations Guide

Figure 10. Drop-down menu

Status: The Status column of the CPC work pane table displays the current
status of the CPC. If you select the status text, the help information for that status
displays. Status icons can also appear in the status column next to the status text.
Depending on the icon that appears, you can get the Hardware Messages task
window or the Operating Systems Messages task window. You can see a sample of
the status icon in the Status column in Figure 10.

Displaying an object’s details: To display details about an object, you can select
the object by clicking in the Select column of the objects work pane table. Then you
can either, click on the objects’s Details in the tasks pad or click on the arrow icon
next to the objects name and click the object’s Details from the context menu. In
both cases the objects’s Details window displays.

Chapter 2. Using the tree style user interface 17

 While you are in the Details window, you can also lock out disruptive tasks, as
described in “Object locking for disruptive tasks” on page 34.

When selecting details for channels or cryptos, the Advanced Facilities... and
Channel Problem Determination... buttons display to provide a link to the
Advanced Facilities and Channel Problem Determination tasks for additional
information on the selected channel or crypto.

When selecting details for CHPIDS, the Channel Problem Determination button
displays to provide a link to the Channel Problem Determination task for
additional information on the selected CHPID.

18 Support Element Operations Guide

SE management

SE Management work pane contains a view of the support element management

tasks and their description. These tasks are used for setting up the support element
console and securing the support element console. Most likely, you will not use
these actions on a regular basis.

To see what level o the support element console you are currently working with,
point your mouse over the SE Version found at the top of the work pane.

To display the tasks in the work pane:

1. Select the SE Management node in the navigation pane.
2. By default, a categorized listing of the tasks is displayed. The tasks are
arranged in groups which include:
v Configuration
v Security.
3. Select the task you want to perform from the work pane.

If you want an alphabetical listing of the tasks, go to the View menu drop-down, in
the upper right corner of the work pane, and click Alphabetical . Click Categorized
to go back to the task categories.

In addition, for each of the Alphabetical and Categorized sorts you can also
choose a style of view:
v Detail displays the tasks in the original tree style user interface style with a small
task icon following by the task name and description in two columns.
v Icon displays large task icons above the task name, similar to the classic style
user interface task display.
v Tile displays tasks using large icons next to each task’s name and description to
help you find tasks by icon while still providing task descriptions.

See Figure 11 for an example of an alphabetical view of the support element tasks
using the icon style.

Chapter 2. Using the tree style user interface 19

Figure 11. Tasks in alphabetical view with icon style

Service management

Service Management contains a categorized view of tasks and their descriptions

used to service the support element.

To see what level o the support element console you are currently working with,
point your mouse over the SE Version found at the top of the work pane.

To display the tasks in the work pane:

1. Select the Service Managementnode in the navigation pane.
2. By default, a categorized listing of the tasks is displayed. The tasks are
arranged in groups which include:
v Console logs.
3. Select the task you want to perform from the work pane.

If you want an alphabetical listing of the tasks, go to the View menu drop-down, in
the upper right corner of the work pane, and click Alphabetical. Click Categorized
to go back to the task categories.

In addition, for each of the Alphabetical and Categorized sorts you can also
choose a style of view:
v Detail displays the tasks in the original tree style user interface style with a small
task icon following by the task name and description in two columns.
v Icon displays large task icons above the task name, similar to the classic style
user interface task display.

20 Support Element Operations Guide

 v Tile displays tasks using large icons next to each task’s name and description to
help you find tasks by icon while still providing task descriptions.

See Figure 12 for an example of a categorized view of the service management

tasks using the tile style.

Figure 12. Tasks in categorized view with tile style

Tasks index

Tasks Index work pane contains an alphabetical listing of the tasks available for
the user ID you are logged in as. You can open these tasks by clicking on the task
name from the table. The table includes the following information:
Name Names the task. The icon associated with the task can be hidden by
disabling the work pane icons from the User Settings task.
Permitted objects
Lists the objects for which the task is applicable. The SE Management and
Service Management tasks require no targets, therefore permitted objects
are not specified.
Count Displays the number of times the task was opened by you.
Description
Describes the task.
Notes:
1. If a task is applicable to one or more targets, for example the Activate task, a
secondary panel is displayed to you for target selection.
2. The SE Management and Service Management tasks are opened without
prompting.

Chapter 2. Using the tree style user interface 21

 3. Each time you open a task, the count increments by one. The values in the
Count column may be reset by clicking on the Reset Task Launch Count in
the Tasks menu in the table toolbar.
4. You can use the work pane table toolbar icons for selecting, filtering, sorting,
and arranging the information in the table. See “Working with the work pane
table toolbar” on page 30 for more detailed information about using the icons.

Figure 13. Tasks index

Work pane
The work pane displays information based on the current selection in the navigation
pane or status bar.

The work pane described in this section discusses the functions of the Systems
Management work pane. This work pane displays a resources (configurable) table.

Selecting an object displays a resources (configurable) table in the work pane as

shown in Figure 14 on page 23. This figure identifies some of the areas of the
configurable table.

22 Support Element Operations Guide

Figure 14. Work pane table

Work pane title and breadcrumb trail

The work pane title appears directly above the work pane configurable table. It
identifies the Systems Management group you are working with. Once you begin
drilling down to more specific objects, a breadcrumb trail is displayed on the work
pane title line. These breadcrumbs identify the navigation path that led you to the
current work pane resources table. You can use the links from the navigation path
to go to the previous pages.

Work pane table footer

The table footer located at the bottom of the work pane table includes information
about the number of pages of information included for the displayed table. It also
displays additional summary information such as the number of items selected in
the work pane table, filtered total, or the row count of the number of rows displayed
in the current page. Figure 14 shows an example of this information.

You can change the number of items you want displayed on each page of the table
by specifying a number in the Max Page Size input field, then press Enter. If more
than one page of information is available, a page count is displayed and you have
the ability to go to a page directly by specifying a page number in the entry field,
then press Enter.

Work pane views

To the far right of the work pane title (see Figure 14) you can select how you want
your resources (configurable work pane) displayed. Select your preference of Table
(which is currently the default), Tree, or Topology from the View: drop-down list
(see “Table view” on page 24, “Tree view” on page 26, and “Topology View” on
page 28). These additional views allow more options for navigation and visualization
of resources. Figure 15 on page 24 displays the table options.

Chapter 2. Using the tree style user interface 23

Figure 15. Work pane table view selections

Table view
This display of information allows you to view managed objects such as servers and
partitions in separate homogenous tables. All table views provide sorting, filtering,
and column configuration of the data to provide customization of which managed
objects are displayed in which order. “Working with the work pane table toolbar” on
page 30 for customization of the managed objects.

For an example of the work pane table view, see Figure 7 on page 12.

Creating a custom work pane table view: If you selected Table (default) as your
work pane view, you can create your own user defined column sets by selecting the
Manage Views option from the menu.

If you are creating a new table view for the first time, perform the following steps:
1. Select the Manage Views option from the toolbar’s Views menu.
2. Click New from the Manage Views Dialog that appears above the resources
table (see Figure 16 on page 25).
3. Specify a unique name for your custom table view in the View Name: input
field.
4. Select the items from the Configure columns: list you want included in your
view. Use the arrows to manage the order of the columns.
5. Click OK when you have completed the customization of your view. The new
table view that you created is displayed when you select the Views menu.

24 Support Element Operations Guide

Figure 16. Customize table view

You can also reorder the columns of the table view work pane table by using the
drag and drop method:
1. Place the cursor on the heading of the column you want to move. You will see
the cursor change to a cross hair indicating it can be moved.

Note: The Select column is the only column that cannot be moved.
2. Hold down the left mouse button and drag the column to the desired placement
in the table. You cannot drag a column pas the Select column.
3. The column settings are saved for you. If you want to go back to the original
column settings, click the Reset Column Order, Visibility, and Width icon.

Renaming a custom work pane table view: To rename a work pane table view,
perform the following steps:
1. Select the Manage Views option from the toolbar’s Views menu.
2. Select the custom table view name that you want to rename from the Custom
Table Views list.
3. Click Rename in the Manage Views Dialog.
4. Specify a unique name for the selected custom table view name.
5. Click OK to save your new custom table view name.
6. The new name will appear in the View menu.

Deleting a custom work pane table view: To delete a work pane table view,
perform the following steps:
1. Select the Manage Views option from the toolbar’s Views menu.
2. Select the custom table view name that you want to delete from the Custom
Table Views list.
3. Click Delete in the Manage Views Dialog.
4. If a confirmation panel appears, Click OK to confirm the deletion.
5. The selected name is not displayed in the Views menu.

Chapter 2. Using the tree style user interface 25

 Configuring a custom work pane table view: To load the selected custom view
and configure the columns in the table view, perform the following steps:
1. Select the Manage Views option from the toolbar’s Views menu.
2. Select the custom table view name that you want to configure from the Custom
Table Views list.
3. Click Configure in the Manage Views Dialog.
4. The table is displayed as specified by your selections.

Tree view
This display of information allows you to view an object and its children in the same
work pane table including its hierarchical relationships. It functions the same way as
the work pane table view (see Figure 15 on page 24) with the following exceptions:
v Additional Expand All and Collapse All buttons are available from the toolbar.
These buttons work on all those objects that have additional objects associated
with them in the table.
v If an object in the Name column contains additional objects, a button to expand
(+) or collapse (-) the item appears before the object name. This allows you to
view all the additional objects within the main object. You can continue to perform
tasks on the expanded objects.

For an example of the work pane tree view, see Figure 17.

Figure 17. Tree view

You can also reorder the columns of the tree view work pane table by using the
drag and drop method:
1. Place the cursor on the heading of the column you want to move. You will see
the cursor change to a cross hair indicating it can be moved.

Note: The Select and Name columns are the only columns that cannot be
moved.
2. Hold down the left mouse button and drag the column to the desired placement
in the table. You cannot drag a column past the Name column.

26 Support Element Operations Guide

 3. The column settings are saved for you. If you want to go back to the original
column settings, click the Reset Column Order, Visibility, and Widths icon.

Creating a custom work pane tree view: If you selected Tree as your work pane
view, you can create your own user defined column sets by selecting the Manage
Views option from the menu.

If you are creating a new tree view for the first time, perform the following steps:
1. Select the Manage Views option from the toolbar’s Views menu.
2. Click New from the Manage Views Dialog that appears above the resources
table (see Figure 18).
3. Specify a unique name for your custom view in the View Name: input field.
4. Select the items from the Configure columns: list you want included in your
view. Use the arrows to manage the order of the columns. Note that Name
cannot be moved or hidden in the column configuration.
5. Click OK when you have completed the customization of your view. The new
tree view that you created is displayed when you select the Views menu.

Figure 18. Custom tree view

Renaming a custom work pane tree view: To rename a work pane tree view,
perform the following steps:
1. Select the Manage Views option from the toolbar’s Views menu.
2. Select the custom tree view name that you want to rename from the Custom
Table Views list.
3. Click Rename in the Manage Views Dialog.
4. Specify a unique name for the selected custom tree view name.
5. Click OK to save your new custom tree view name.
6. The new name will appear in the View menu.

Deleting a custom work pane tree view: To delete a work pane tree view,
perform the following steps:

Chapter 2. Using the tree style user interface 27

 1. Select the Manage Views option from the toolbar’s Views menu.
2. Select the custom tree view name that you want to delete from the Custom
Table Views list.
3. Click Delete in the Manage Views Dialog.
4. If a confirmation panel appears, Click OK to confirm the deletion.
5. The selected name is not displayed in the Views menu.

Configuring a custom work pane tree view: To load the selected custom view
and configure the columns in the tree view, perform the following steps:
1. Select the Manage Views option from the toolbar’s Views menu.
2. Select the custom tree view name that you want to configure from the Custom
Table Views list.
3. Click Configure in the Manage Views Dialog.
4. The table is displayed as specified by your selections.

Topology View
This display of information allows you to view the objects using a graphical
relationship based model. It is composed of the Toolbar, Framed image, and
Support areas, some of which are identified in Figure 19.

Note: When an object’s status changes or new objects have been added or
removed, the image is updated and the new content automatically fits in the
current work pane area.

Figure 19. Topology view

Toolbar: This area of the topology work pane consists of several icons and
drop-down menus for controlling the appearance and actions of the topology view.
You can mouse over the toolbar icons for short descriptions of the respective
actions.

The toolbar icons are divided into the following groups:

v Content zoom and fit control - used for enlarging and shrinking the images and
automatically fitting the image content within the work pane area:
28 Support Element Operations Guide
 – Zoom In
– Zoom Out
– Fit Contents to Viewport.
v Mouse modes - controls the function of the mouse.
– Select Mouse Mode (default) - clicking on an object causes it’s selection to
be toggled.
- When a node is selected, the tasks context menu icon is displayed and the
tasks in the Tasks drop-down menu are also updated.
- When multiple selection is enabled, press (Ctrl +) left mouse button to
select multiple nodes. Left clicking in a blank area of the work pane area
deselects all selected nodes.
– Pan Mouse Mode- scroll the objects in the frame up, down, left, or right using
direct manipulation. After you release the mouse button, the mouse mode is
automatically changed back to the selection mode.
– Zoom Mouse Mode - creates a viewport to zoom into. The mouse is used to
select a rectangular area (a blue box is displayed to indicate the area) as part
of the image frame to zoom into. The objects in the area are enlarged. After
you release the mouse button, the mouse mode is automatically changed
back to the selection mode.
v Toggle Support Area Visibility icon - toggles the visibility of the support area,
which displays the image Overview (see Figure 19 on page 28.
v Expand All / Collapse All icons -expand (display) or collapse (hide) the children of
all objects.

The drop-down menus include:

v Tasks - when one or more objects are selected the selected the tasks available
for the objects are displayed. These same tasks are displayed in the context
menu and tasks pad.
v Selection - allows you to select all the objects, deselect all the objects, or invert
selection.
v Zoom - allows you to change the content size:
Fit Content
Automatically fits the objects in the framed image area.
50% Size of each object is displayed as half it’s actual size.
100% Size of each object is displayed as the actual size.
200% Size of each object is displayed as twice the actual size.
v Layout - allows you to select the preferred object layout.
Rerun Current
Redraws the image using the current layout.
Tree Displays objects in a hierarchical tree format.
Hierarchical
Arranges the nodes so that the majority of links are short and flow
uniformly in the same direction.
Circular
Objects are automatically grouped into either a ring or star topology.
Uniform length
Searches for a configuration of the graph where the length of the links
are the same.
Grid Objects are placed into a grid.

Framed image: This area displays graphical representations of managed objects.

Each object is represented with a graphic which displays the object’s name, it’s

Chapter 2. Using the tree style user interface 29

 status, it’s tasks (in a context menu), and an expand/collapse button if it has
children. Note some of the following characteristics as you work in the framed
image:
v If an object is selected, the label uses black font color and blue background
color, the background of the object icon also turns blue. The
acceptable/unacceptable state is still displayed by the status overlay of the icon.
v The status icon overlay is a combination of the system status icon, hardware
messages icon, and the operating system messages icon.
v If an object is locked, the lock icon is displayed.
v If an object is busy, the busy icon is displayed.
v Clicking on a frame segment redraws the image that has been panned in the
associated direction.
v Clicking the right mouse button in an empty area of the images frame displays a
pop-up menu with the following options (similar to the Toolbar functions):
– Collapse All
– Expand All
– Selection
– Zoom
– Layout
– Center here - centers you on the current mouse position.
– Move here - moves the selected object into the current mouse position. (this
option appears only when exactly one object is selected)
v Clicking the right mouse button of an object displays a pop-up menu with the
following options:
– Zoom To - zooms into the object in the center of the viewer display area.
– Center here - centers you on this object.
– Expand - expands the object by displaying any children if an object is
collapsed.
– Collapse - collapses the object by hiding it’s children if an object is expanded.

Support: This optional area (click Toggle Support Area Visibility icon on the
toolbar) is used to display an overview of the topology image. Each node in the
overview displays the status of the associated managed object. The blue rectangle
indicates the visible portion being shown within the framed image area. Dragging
the rectangle changes what is displayed in the image viewer area.

Working with the work pane table toolbar

The tool bar at the top of the System Management work pane resources table
contains icons used to select, filter, sort, and arrange the entries in the resources
table. Hovering over the toolbar buttons displays their functions. The toolbar also
includes Tasks and Views menus that can be used with the information displayed
in the resources tables.

Selecting rows

You can select more than one table row at any given time. Rows can be individually
selected or a block of rows can be selected at once by first left-clicking the
selection box of the first row in the desired block and then shift-clicking the
selection box of the last row in the desired block. The Select All or Deselect All
icons can be used to select or deselect all objects in the table. The table summary
at the bottom of the table (work pane table footer) includes the total number of
items that are selected. To set the object selection use the User Settings task.

30 Support Element Operations Guide

Export data

The Export Data icon allows for table data to be downloaded in a Comma
Separated Values (CSV) file. This downloaded CSV file can then be imported into
most spreadsheet applications.

Note: This function is only available when you are accessing the support element
console remotely.

Filtering

If you select the Filter Row icon a row appears under the title row of the table.
Select Filter under a column to define a filter for that column to limit the entries in a
table. Tables can be filtered to show only those entries most important to you. The
filtered view can be toggled on and off by selecting the check box next to the
desired filter in the filter row. Select the Clear all Filters icon to return to the
complete listing. The table summary includes the total number of items that pass
the filter criteria in addition to the total number of items.

Sorting

The Edit Sort and Clear all Sort icons are used to perform multi-column sorts of
objects in the table in ascending or descending order. Click Edit Sort to define
sorts for columns in a table. Alternatively, single column sorting can be performed
by selecting the ^ in the column header to change from ascending to descending
order. Click Clear All Sorts to return to the default ordering.

Column configuration

The column configuration icons give you the ability to select which columns to
display for folders in the System Management tree view. Click the Configure
Columns icons to arrange the columns in the table in a desired order or hide
columns from view. All available columns are listed in the Columns list box by their
column name. You select the columns you want displayed or hidden by selecting or
deselecting the box next to the column names. The column order is manipulated by
clicking on a column name from the list box and using the arrow buttons to the right
of the list to change the order of the selected column. When you have completed
the configuration of the columns, click OK. The columns appear in the table as you
specified. If you want to go back to the original layout of the table, click the Reset
Column Order, Visibility, and Widths icon from the table toolbar. Select one or
more of the properties to be reset back to their original layout, (click OK to save.

Quick filter

The quick filter function allows you to enter a filter string in the input field, then click
Enter to apply the filter. By default, all the columns are filtered, showing only rows

Chapter 2. Using the tree style user interface 31

 containing a cell whose value includes the filter text. When you select the
drop-down arrow a menu is displayed that allows you to restrict the columns to
which the filter is applied.

Tasks menu
The Tasks menu is displayed on the work pane table toolbar and is only available
for table selections when working with managed objects and custom groups. See
“Task menu” on page 16 for more information.

Views menu
The Views menu is displayed on the toolbar and is only available for table
selections when working with managed objects and custom groups. This menu
allows you to display different set of attributes (columns) in the tables.

Status bar

The status bar in the bottom left pane provides an ″at a glance″ view of overall
system status, including managed system resources and the support element
console. A status-sensitive title, background color, and icons are part of the status
bar. The Status Overview icon is always available in the status bar. Indicators
(icons) appear in the work pane table next to a managed object when it is in an
Exception State or when it receives a Hardware or Operating System Message.

Click any of the individual icons in the status bar to view a listing of resources. For
example, select the Exceptions icon to view all resources with an exception state.
The results appear in a table in the work pane.

Status: exceptions

If any managed object is in unacceptable state, the Exceptions indicator (icon)

appears on the status bar. When you select the Exceptions indicator (icon) it
displays a table in the work pane of only the objects in an unacceptable state.

Status: hardware messages

If a managed object or the support element console receives a hardware message,

the Hardware Message indicator (icon) appears on the status bar. When you select
the Hardware Messages icon it displays a table in the work pane of only the
objects with hardware messages. The table that appears includes the object name,
status, and description. To view the hardware message for a particular object you
can click on the Hardware Message icon in the Status column or you can select
the object by clicking in the Select column next to the object name(s), click Daily in
the tasks pad, and click Hardware Messages. The Hardware Messages window is
displayed. Now you can work with your messages.

32 Support Element Operations Guide

Status: operating system messages

If a managed object receives an operating system message, the Operating System

Message indicator (icon) appears on the status bar. When you select the
Operating System Messages indicator (icon) it displays only objects with unviewed
operating system messages requiring attention. The table that appears includes the
object name, status, and description. To view the operating system messages for a
particular object you can click on the Operating System Messages icon in the
Status column or you can select the object by clicking in the Select column next to
the object name(s), click Daily in the tasks pad, and click Operating System
Messages. The Operating System Messages window is displayed. Now you can
work with your messages.

Status overview

When you select the Status Overview icon it displays a more detailed view of
overall status in the work pane, as shown in Figure 20. It summarizes the total
number of exceptions, hardware messages, and operating system messages by
objects. Then you can select a link from the work pane table to display all objects
with the particular state in the work pane.

Figure 20. Status Overview

Chapter 2. Using the tree style user interface 33

Object locking for disruptive tasks
You can tell when a server or server image is locked because a small lock appears
next to the server name in the work pane table.

The setting of the CPC or CPC object’s toggle lock determines whether you can
perform a disruptive task on the CPC or CPC objects. You can lock an individual
object or automatically lock all objects.

To individually lock (or unlock) the CPC or CPC objects:

1. Select the CPC from the table that you want to lock (or unlock).
2. Click CPC Details from the task pad. The CPC Details window is displayed.
3. You can select Yes or No for Lock out disruptive tasks.
4. Click Apply to make the change.

There is also an automatic way to lock the CPC and CPC objects that are displayed
on the workplace at one time. Unlike the previous ways for locking an object, using
this method can cause the object to be relocked automatically if it was unlocked to
perform a task on it. To use this method, you must have a user ID with the
predefined user roles of an Advanced Operator, System Programmer, Access
Administrator, or Service Representative for the support element console.
1. Open the Object Locking Settings task from the SE Management work pane.
The Locking window is displayed.
2. Select Automatically lock all managed objects or Relock after a task has
been run or both.

34 Support Element Operations Guide

Chapter 3. Using the classic style user interface
This chapter explains how to use the classic style user interface for performing
tasks on the support element console or on a CPC.

Support element workplace

The support element workplace is the window where you start tasks for monitoring
and operating your system.

If you have experience using other systems, you will find that the workplace
supports functions, facilities, and controls that are similar to those you have used to
monitor and operate similar systems. The workplace presents tasks and their
targets graphically, as icons. Using the workplace to get information and start tasks
is often a matter of monitoring and manipulating icons, rather than, for example,
typing commands or using menus.

Icons that represent the functions, facilities, and controls you use to monitor and
operate the system and console are referred to as tasks. A single icon that
represents a set of one or more related tasks is referred to as a task list.

Icons that represent the physical and logical elements of the system, which are
often the targets of tasks, are referred to as objects. The console’s objects include:
v Central processor complex (CPC)
v Physical channels (PCHIDs)
v Central processors
– This includes: General processors, Internal Coupling Facility (ICF), Integrated
Facility for Linux® (IFL), zSeries® Application Assist Processors (zAAPs), and
IBM System z9® Integrated Information Processors (zIIPs).
v Logical channels (CSS.CHPIDs)
v Images (An image is a set of CPC resources capable of running a control
program or operating system. One or more images is created during a power-on
reset of a CPC. Each logical partition is an image.

A single icon that represents a set of one or more objects of the same type is
referred to as a group.

© Copyright IBM Corp. 2008 35

 The workplace is divided into three areas to organize its icons. The three areas are
your means of locating the icons to get information or start tasks. The three areas
are:
Views Located along the top left side of the workplace, this area contains icons
you can use to change the type of icons displayed in the work area below
it.
Work area
Located below the Views area, this area contains icons in the current view.
Depending on the view, the work area contains either groups, objects, tasks
in progress, task lists, tasks for monitoring and operating the console, or
online books.
Tasks area
Located along the right side of the workplace, this area displays the current
task list that contain tasks for monitoring and operating the system.

36 Support Element Operations Guide

Monitoring and operating the system
There are three general ways to use the workplace for monitoring and operating the
system:
v Monitoring summarized system status.
v Getting detailed system status.
v Starting tasks for monitoring and operating the system.

Monitoring summarized system status

Use the Views area to monitor summarized system status by monitoring the
background color of the area.

The system includes all console objects that represent physical and logical
elements of the system. The status of the system is summarized in one of two
ways:
No exceptions
This is the summarized system status when all objects have acceptable
statuses. An acceptable status is any object status that is normal, is as
expected, or does not require your immediate attention or intervention. That
is, an object with an acceptable status is OK as is.
Exceptions
This is the summarized system status when one or more objects have
unacceptable statuses. An unacceptable status is any object status that is
not normal, is not as expected, or requires your immediate attention when it
occurs. That is, an object with an unacceptable status is not OK, and may
require your intervention to make it OK again.

An exception occurs when the status of an object becomes unacceptable. The

object is referred to as an exception while its status remains unacceptable.

When an exception occurs, the status of the system also becomes unacceptable.
But rather than monitoring the system’s status by monitoring whether its individual
objects become exceptions, you can recognize when an exception occurs by
monitoring the background color of the Views area. The default colors, green and
red, are set for indicating no exceptions and exceptions, respectively. The colors are
used for the Views area, to indicate the summarized status of the system, as
follows:
v When there are no exceptions, the area’s background color is green, the color
set for indicating there are no exceptions.

Chapter 3. Using the classic style user interface 37

 v When an exception occurs, the area’s background color changes to red, the color
set for indicating there are exceptions.

v The area remains red, the color set for indicating there are exceptions, until you
open the Exceptions view. Upon opening the view, the area’s background color
returns to green, the color set for indicating there are no exceptions, to indicate
there are no new exceptions.

Note: The Exceptions view is described in the next section; see “Locating
objects with unacceptable status” on page 48.

38 Support Element Operations Guide

Getting detailed system status
Use Views and the work area to get detailed system status by checking the
individual status of the following objects that represent physical or logical elements
of the system:
v Central processor complex (CPC)
v Central processors
v Channel paths
v Images

Like the background color of the Views area, the background color of an object’s
icon indicates whether its status is acceptable or unacceptable. The background
color of an object’s icon indicates the object’s status in one of two ways:
No color
This indicates the object’s status is acceptable. An acceptable status is any
object status that is normal, is as expected, or does not require your
immediate attention or intervention. That is, an object with an acceptable
status is OK as is.
Color This indicates the object’s status is unacceptable. The specific color
indicates the object’s specific, unacceptable status. An unacceptable status
is any object status that is not normal, is not as expected, or requires your
immediate attention when it occurs. That is, an object with an unacceptable
status is not OK, and may require your intervention to make it OK again.

Therefore, checking whether the individual status of an object is acceptable or

unacceptable requires locating a group that contains the object, then checking the
background color of the object’s icon.

Chapter 3. Using the classic style user interface 39

Locating groups and objects
Use Views and the work area to locate objects. Objects are divided into groups of
objects of the same type. To locate a particular object, you must locate and open
the group that contains it. Opening a group displays its objects in the work area.

To open a group:
1. Open Groups from Views.
2. Locate the group that contains the type of objects you want to locate in the
Groups Work Area.
3. Double-click on the group to open it.

Locating the CPC

One of console’s default groups, the CPC group, contains the object that represents
the central processor complex (CPC).

To locate the CPC:

1. Open Groups from Views.
2. Locate the group labelled CPC in the Groups Work Area.
3. Double-click on the CPC group to open it.

Locating logical partitions

When the central processor complex (CPC) is activated, one of console’s default
groups, the Images group, contains objects that represent the logical partitions.

Logical partitions are referred to also as images. An image is a set of CPC

resources capable of running a control program or operating system.

To locate logical partitions:

1. Open Groups from Views
2. Locate the group labelled Images in the Groups Work Area.

40 Support Element Operations Guide

3. Double-click on the Images group to open it.
This displays the objects that represent logical partitions in the Images Work
Area.

Locating physical processors and logical processors

The object that represents the central processor complex (CPC) contains objects
that represent its physical processors.

Each object that represents a CPC image contains objects that represent a logical
processor:
v When the CPC is activated, each logical partition is an image. Each CPC image
contains objects that represent a logical partition’s logical processors.

On the support element workplace, both physical processors and logical processors
are referred to as central processors (CPs).

To locate physical processors:

1. Open the CPC Work Area.
For instructions, see “Locating the CPC” on page 40.
2. In the CPC Work Area, locate the CPC.
3. Right click on the CPC to open its pop-up menu.
4. Select the CPs menu choice.
This displays the objects that represent the CPs in the work area.

To locate logical processors:

1. Open the Images Work Area.
For instructions, see“Locating logical partitions” on page 40.
2. In the Images Work Area, locate the image that represents the logical partition
to which the logical processors are assigned.

Chapter 3. Using the classic style user interface 41

 3. Right click on the image to open its pop-up menu.
4. Select the CPs menu choice.
This displays the objects that represent the image’s logical processors in the
work area.

Locating channels
The object that represents the central processor complex (CPC) contains objects
that represent all channels configured and not configured in the input/output (I/O)
configuration.

To locate all channels in the CPC’s I/O configuration:

1. Open the CPC Work Area.
For instructions, see “Locating the CPC” on page 40.
2. In the CPC Work Area, locate the CPC.
3. Right click on the CPC to open its pop-up menu.
4. Select the Channels menu choice.
This displays the objects that represent the channels in the work area. Each
channel is labelled with its physical channel identifier (PCHID).

Locating channel paths

The object that represents the central processor complex (CPC) contains objects
that represent all channel paths defined in its input/output (I/O) configuration.

42 Support Element Operations Guide

 To locate channel paths assigned to a specific logical partition:
1. Open the Images Work Area.
For instructions, see “Locating logical partitions” on page 40.
2. In the Images Work Area, locate the image that represents the logical partition
to which the channel paths are assigned.
3. Right click on the image to open its pop-up menu.
4. Select the CHPIDs menu choice.
This displays only the objects that represent the image’s channel paths in the
work area. Each channel path is labelled with its channel path identifier
(CSS.CHPID).

Determining the exact status of an object

After locating an object, check the background color of its icon to determine
whether its status is acceptable or unacceptable:
v The icon’s background has no color when the object’s status is acceptable.
v When the object’s status is unacceptable, the icon’s background displays the
color that identifies the unacceptable status.

Note: If you are not certain which unacceptable status is indicated by the
background color of the CPC’s icon, double-click on it to open the CPC’s
Details window.

Background color of the CPC

The background color of the icon of the central processor complex (CPC) indicates
whether the statuses of the CPC, its central processors (CPs), and its channel
paths are acceptable or unacceptable. While the statuses are acceptable, the
background of the CPC icon has no color. Otherwise, the background color of the
CPC indicates unacceptable statuses as follows:

Chapter 3. Using the classic style user interface 43

 v Until CPC power is turned on and a power-on reset is performed, the background
color of the CPC indicates an unacceptable CPC status.
v After CPC power is turned on and a power-on reset is performed:
– The background color of the left side of the CPC indicates an unacceptable
CP status.
– The background color of the right side of the CPC indicates an unacceptable
channel path status.

The background color of the CPC’s icon also indicates whether its support element
received hardware messages from the CPC. When the support element receives a
hardware message, the background color of the CPC changes to the color set for
indicating a hardware message was received. The default color is blue.

Note: If the status of the CPC, its CPs, or its channel paths is unacceptable, and
the CPC’s support element received hardware messages, then:
v The color of the top half of the CPC’s icon indicates the unacceptable
status.
v The color of the bottom half of the CPC’s icon indicates the support
element received hardware messages.

Background color of images

The background color of an image’s icon indicates whether the statuses of the
image, its central processors (CPs), and its channel paths are acceptable or
unacceptable. While the statuses are acceptable, the background of the image icon
has no color. Otherwise, the background color of the image indicates unacceptable
statuses as follows:
v While the image is not activated, the background color of the image indicates an
unacceptable image status.
v After the image is activated:
– The background color of the left side of the image indicates an unacceptable
CP status.
– The background color of the right side of the image indicates an unacceptable
channel path status.

The background color of the image’s icon also indicates whether its support
element received operating system messages from the image. When the support
element receives an operating system message, the background color of the image
changes to the color set for indicating an operating system message was received.
The default color is cyan.

Note: If the status of the image, its CPs, or its channel paths is unacceptable, and
the image’s support element received operating system messages, then:
v The color of the top half of the image’s icon indicates the unacceptable
status.
v The color of the bottom half of the image’s icon indicates the support
element received operating system messages.

Background color of CPs

The background color of the icon of a central processor (CP) indicates whether the
status of the CP is acceptable or unacceptable. While the status is acceptable, the
background of a CP icon has no color. Otherwise, the background color of the CP is
the color that indicates its specific unacceptable status.

44 Support Element Operations Guide

Background color of channel paths
The background color of the icon of a channel path indicates whether the status of
the channel path is acceptable or unacceptable. While the status is acceptable, the
background of a channel path’s icon has no color. Otherwise, the background color
of the channel path is the color that indicates its specific unacceptable status.

Opening an object’s details window

If you want to determine the exact acceptable status of an object, or if you are not
certain which unacceptable status is indicated by the background color of an
object’s icon, you can open the object’s Details tabbed window.

When selecting Details for channels or cryptos, the Advanced Facilities... and
Channel Problem Determination... buttons display to provide a link to the
Advanced Facilities and Channel Problem Determination tasks for additional
information on the selected channel or crypto.

Chapter 3. Using the classic style user interface 45

 When selecting Details for CHPIDS, the Channel Problem Determination button
displays to provide a link to the Channel Problem Determination task for
additional information on the selected CHPID.

To open an object’s Details tabbed window:

1. Locate the object.
For instructions, see the topics that follow “Locating groups and objects” on
page 40.
2. In the object’s work area, double-click on the object.
This opens the object’s Details window.

The Details window includes the following tabbed information:

Instance Information
Includes instance information and task information.
Acceptance Status
Shows the various states and their associated colors and indicates the
current state.
Product Information
Shows CPC information and machine information.
STP Information
Shows the current Server Time Protocol (STP) status for the CPC.

Note: This tab is only available when STP is enabled and in the operating
state.
Busy Status
Specifies the reason why the object is busy

Note: This tab is only available when an object is busy.

Determining conditions causing test status

If the CPC’s performance is affected, an object’s icon displays Test. This indicates a
conditions exists, such as PSW even compare or Address compare are enabled. To
determined the exact conditions test status:

46 Support Element Operations Guide

1. Locate the object.
For instructions, see the topics that follow “Locating groups and objects” on
page 40.
2. In the object’s work area, double-click on the object.
This opens the object’s Details window.
3. To determine the object’s degraded status, select the Test Mode tab on the
Details window.
The Test Mode window displays the condition(s) for tests.

Use the online Help for more information on the test indicator.

Determining conditions causing Service Required or Degraded

status
There are two types of status messages that cause the CPC to display status that
may require attention.
1. Service Required
This status displays in the Acceptable CP/PCHID Status tab on the Details
window of the CPC. This indicates that the spare hardware shipped with the
CPC has been depleted. When a part fails causing the use of the last redundant
parts of that type, you now have just the required number of parts to keep the
CPC running. This message is a reminder to you and the service representative
that repairs should be made at the earliest possible time before addition. Some
of the conditions that cause this message to be displayed are:
v Loss of one bulk power assembly (BPA)
v Loss of communications to the alternate support element
v No more spare processing units (PUs)
v Not enough spare PUs to support either Capacity BackUp or Disaster
Recovery Assurance (if either feature is installed)
v Memory sparing threshold reached
v An Oscillator/ETR card is defective
v The alternate support element is fenced
v A multiple chip module (MCM) is defective.
2. Degraded
This status message displays under the CPC icon in the Groups Work Area.
This indicates that, although the CPC is still operating, some hardware is not
working.
Some of the conditions that cause this message to be displayed are:
v Loss of channels due to CPC hardware failure
v Loss of memory
v One or more books are no longer functioning
v The ring connecting the books is open
v Capacity Backup resources have expired
v Processor frequency reduced due to temperature problem
v CPC was IMLed during temperature problem.

To view what conditions caused the degraded status message to display:

1. Locate the object.
For instructions, see the topics that follow “Locating groups and objects” on
page 40.
2. In the object’s work area, double-click on the object.
This opens the object’s Details window.

Chapter 3. Using the classic style user interface 47

 3. To determine the object’s degraded status, select the Degraded tab on the
Details window.
The Degraded Details window displays the current list of reasons why the
selected CPC is degraded.

Locating objects with unacceptable status

You can check the status of an object at any time by locating and opening a group
that contains it. Rather than locating exceptions this way, you can use Views and
the work area to immediately locate all current exceptions.

To locate objects that are exceptions:

1. Open Exceptions from Views.

This displays all objects with unacceptable statuses in the Exceptions Work
Area. (Not all logical objects are displayed. For example, Image CPs.)
2. In the Exceptions Work Area, the background color of each object’s icon
indicates its current status. If you are not certain which status is indicated by the
background color of an object’s icon, double-click on the object to open its
Details window.
This window includes detailed information about the object, including a list of the
colors used to indicate its statuses.

Recognizing exceptions
After the background color of the Views area returns to green, indicating there are
no new exceptions, you can still recognize current exceptions by the background
colors of the Exceptions icon and of each group that contains an exception:
v Upon opening the Exceptions view, the background color of the Views area
returns to green, but the Exceptions icon remains red, the color set for indicating
there are exceptions.
The Exceptions icon remains red until the last of all current exceptions is
returned to an acceptable status.
v When an exception occurs, the background color of each group that contains the
exception changes to red, the color set for indicating there are exceptions.
A group that contains exceptions remains red until all of its exceptions are
returned to an acceptable status.

Note: Within a group, the background color of each object that is an exception is
the color set to indicate its specific unacceptable status, as described
previously in the topics that follow “Determining the exact status of an
object” on page 43. An exception remains the color of its unacceptable
status until it is returned to an acceptable status.

Returning an exception to an acceptable status

After you locate an exception and check its unacceptable status, you can use any
appropriate task to return the exception to an acceptable status. The target object
of the task can be either:
v The exception from the Exceptions Work Area.
v The same exception from any group that contains it.

48 Support Element Operations Guide

 Locating the exception in the Exceptions Work Area likely is the quickest way to
locate a target for the task.

Note: When activation is the task you intend to use to return an exception to an
acceptable status, you should consider the activation profile assigned to the
target object. Whenever an object is activated, it is activated according to the
information in its assigned activation profile.

The exception in the Exceptions Work Area is automatically assigned the activation
profile used in the most recent attempt to activate the object. To activate the
exception with a different activation profile, you can either:
v Assign the exception in the Exceptions Work Area the activation profile you want
to use.
v Locate an instance of the same exception, in any group that contains it, that is
already assigned the activation profile you want to use.

For more information about activation and assigning activation profiles, see
“Activating the CPC” on page 62 and “Assigning activation profiles to objects” on
page 132, respectively.

Starting tasks
Use Views, the work area, and the tasks area to start tasks for monitoring and
operating the system. Starting a task includes the following general steps:
1. Locating the task.
2. Locating and selecting the task’s targets.
3. Starting the task on its targets.

Locating a task
Use Views, the work area, and the tasks area to locate system tasks. System tasks
are divided into lists of related tasks. To locate a particular system task, you must

Chapter 3. Using the classic style user interface 49

 locate and open the task list that contains it. Opening a task list displays its tasks in
the tasks area along the right side of the workplace.

To open a task list:

1. Open Task List from Views.
2. In the Task List Work Area, locate the list that contains the type of system task
you want to start.
3. Double-click on the task list to open it.
4. Locate the task list on the right side of the Support Element Workplace.

Begin with the task in the upper left corner of the area, and move left to right
through each row of task lists. Consider this order a ring. To complete the ring, the
last task list in the last row is followed by the first task list in the first row. After you
become familiar with this order, you may prefer to open a task list by using the
controls, referred to as ring buttons, located in the lower right corner of the tasks
area.

To use ring buttons to open a task list:

v Click on the left ring to open the next task list in the ring.
v Click on the right ring to open the previous task list in the ring.

Note: To view the rings on the support element console, click the maximize icon in
the upper right hand corner of the support element workplace.

Until you become familiar with the tasks contained in each task list, use the index of
this operations guide to locate instructions for starting the task you want to perform.
The instructions will identify the name of the task and the name of the task list that
contains it.

Locating task targets

Objects, which represent the physical and logical elements of the system, are
typical targets of tasks. The console’s objects include:
v Central processor complex (CPC)
v Physical channels (PCHIDs)
v Central processors
v Logical channels (CSS.CHPIDs)
v Images

Groups of objects can also be the targets of some tasks. Starting a task on a group
performs the task on each object in the group.

After locating the task, use Views and the work area to locate the groups or objects
you want to use as the task’s targets. Instructions for locating groups and objects
are provided in previous topics; see the topics that follow “Locating groups and
objects” on page 40.

Selecting task targets

After locating the groups or objects you want to use as the task’s targets, you may
have to select them to identify them as targets. Selecting objects prepares them for
further action.

50 Support Element Operations Guide

 Selecting a single task target: If you intend to start a task on a single target,
selecting the target is optional. Instead, you can start the task immediately after
locating the target. For instructions, see “Starting a task on its targets” on page 52.

Selecting multiple task targets: Unlike starting a task on a single target, starting
a task on multiple targets requires selecting the targets first. The default setting for
selecting objects displayed in the Work area is Single object selection; however,
to select more than one object at a time, allows you to perform tasks on them as a
dynamic group, you can do the following:
1. Open Console Actions from the Views area.
2. Open User Settings from the Console Actions Work Area.
The User Setting window is displayed.
3. Select the Controls tab on the User Settings window.
4. Deselect Single object selection by clicking on the check mark to remove it,
click Apply, then click OK when you are finished with the task.

In the Work area, if selection of multiple objects is allowed, you can use one o the
following methods for selecting multiple objects:
v Click on each object to be selected.
v Select or deselect all objects in a view.

To select all objects:

1. Display the objects you want to select. For example, Channels so those objects
are displayed in the Work area.
2. Right-click on a spot on the Channels Work Area without an icon. This displays
the menu for the Work area.
3. Click Select All. This selects all the objects in the Work area.

To deselect all objects, if all objects are selected:

1. Right-click on a spot on the Channels Work Area without an icon. This displays
the menu for the Work area.
2. Click Deselect all. This deselects all the objects in the Work area.

Figure 21. Work area menu

Clicking individual objects that are already selected deselects the objects.

Note: There are times when you may only want to work with one object at a time
and you do not want to worry than an additional object(s) is selected
accidentally. Use the User Settings task to make sure the Single object
selection option is selected (a check mark appears).

Chapter 3. Using the classic style user interface 51

 To select each target individually:
1. Locate the objects or groups.
For instructions, see the topics that follow “Locating groups and objects” on
page 40.
2. Click on each object or group you want to select.
The background color of their icons becomes gray to indicate they are selected.

Deselect a selected object or group, to undo its selection, if you do not want it to be
a task’s target. Click on a selected object or group to deselect it.

Starting a task on its targets

After locating a task, and locating and selecting its targets, you can start the task on
the targets. There are several ways to start tasks. You can use whatever way is
easiest for you or most appropriate for the task.

To start a task on a single target:

1. Locate the task.
2. Locate the target object or group.
3. Start the task on the target by any of the following:
v Dragging and dropping the task on the target.
v Dragging and dropping the target on the task.
v Selecting the target and double-clicking on the task.
v Selecting the target, selecting the task, and clicking Enter.

To start a task on multiple targets:

1. Locate the task.
2. Locate and select the target objects or groups.
3. Start the task on the targets by any of the following:
v Dragging and dropping the task on any one of the selected targets.
v Dragging and dropping any one of the selected targets on the task.
v Double-clicking on the task.
v Selecting the task, and clicking Enter.

Minimizing and restoring a task in progress

A task is considered to be in progress, and is referred to as active, until it is
completed and its completion is acknowledged.

Completing a task typically requires using one or more windows and messages to
provide information for performing the task or to acknowledge information about its
intermediate and final outcomes. A window or message that requires you to provide
or acknowledge information remains open until you do so. Ordinarily, the window or
message also remains displayed. Some tasks provided for monitoring and operating
the system allow you to temporarily set the task aside, while it is still active, by
minimizing its open window or message. This is referred to as minimizing an active
task.

Consider minimizing an active task whenever either:

v The console is busy processing the task and does not require your interaction or
attention for several minutes.
v Or you want an unobstructed view of the workplace.
For example, you may want to monitor its objects or areas for status changes.

52 Support Element Operations Guide

v Or you want to use the workplace to do something else, but do not want to
complete or cancel the task first.
For example, you may want to use the console’s 3270 emulator, check or change
the console’s settings, or open one of the console’s online books.

To minimize an active task:

1. Click on the minimize icon of the active task’s open window or message.

Note: The minimize icon is located in the upper right corner of the window or
message.
This minimizes the window or message, which minimizes the active task. The
task is still active, and its current window or message remains open, but it is
temporarily not displayed.

After you minimize an active task, it will remain minimized until either:
v The console restores the task automatically when it completes processing the
task and displays a window or message with information about the task’s final
outcome.
Close the window or message to acknowledge receiving the information and to
end the completed task.
v Or you restore the task, at any time, to either complete it, cancel it, or check its
progress.
Use Views and the work area to restore a minimized active task.

To restore a minimized active task:

1. Open Active Tasks from Views area.

Note: An empty Active Tasks Work Area indicates there are no minimized
active tasks.
2. In the Active Tasks Work Area, locate the minimized active task you want to
restore.
3. Double-click on the task to restore it.
Restoring the task again displays its open window or message. Follow the
instructions on the window for completing, cancelling, or continuing the task.

Restoring a minimized open window: The windows and messages displayed

during active tasks remain open until you provide or acknowledge information as
required to complete the tasks. Not all open windows indicate an active task.

For example, open windows that provide options for starting tasks, changing
settings, or viewing information, are not considered active tasks. While you can
minimize an open window the same way you minimize an active task, minimized
open windows will not be included in the Active Tasks view.

To restore a minimized open window:

1. Click on the maximize icon located in the upper right corner of the workplace.
Restoring the open window again displays it. Follow the instructions on the
window for using it or use its controls to close it.

Completing active tasks and closing open windows before logging off: You
cannot log off the console while tasks are active or windows are open. The console

Chapter 3. Using the classic style user interface 53

 will notify you if there are active tasks or open windows when you attempt to log off.
You must complete or cancel each active task and close each open window before
the console will allow you to log off:
v If an active task is minimized, restore it, then follow the instructions on an active
task’s open window or message to complete or cancel the task.
Completing an active task may often be only a matter of acknowledging the
completion of the task.
v If an open window is minimized, restore it, then use its controls to close it.

Setting object locking for disruptive tasks on an object

Some of the Support Element Console tasks are considered disruptive. Performing
a disruptive task on a CPC or CPC image may disrupt its operation. For example,
activating a CPC and loading an image are disruptive tasks. You may want to lock
an object to prevent accidentally performing disruptive tasks on it and then unlock
the object only when you want to perform a disruptive task on it.

Depending on whether the Lockout disruptive task setting is set to Yes or No

determines if you can perform a disruptive task on a CPC or CPC object. You can
either lock an individual object or a group of objects at one time.

Note: The Lockout disruptive task only affects operations from the Support
Element Console workplace you are currently working at. It does not affect
most operations from the Support Element (for example, scheduled
operations and CPC operations management commands, etc.), and
operations initiated from other sources (for example, from Hardware
Management Consoles).

To individually lock the CPC or CPC object:

1. Locate the object you want to lock in the Work Area.
2. Right-click on the object’s icon.
3. Click CPC Details from the menu.
The CPC Details window opens.
4. Set Lockout disruptive tasks to Yes or No.
5. Click Apply to lock the object.

To lock or unlock all the objects in the Work are:

v Right-click on a spot on the Work are without an icon. This displays the menu for
the Work area. See Figure 21 on page 51.
v Click Lock all to lock all the objects in the Work area, click Unlock all to unlock
all the objects in the Work area.

If you want to lock the CPC or CPC images at one time, there is an automatic way
to lock all them displayed on the workplace at one time. If using this method, you
will cause an object to be relocked automatically if it was unlocked to perform a
task on it.
1. Locate the objects you want to lock in the Work Area.
2. Open Console Actions from Views.
This displays the console actions in the Console Actions Work Area.
3. Open the Support Element Settings task from the Console Actions Work Area.
This displays the Support Element Settings Work Area.
4. Open the Object Locking Settings task from the Support Element Settings
Work Area.

54 Support Element Operations Guide

 5. Select Automatically lock all managed objects or Relock after a task has
been run or both. All objects currently in the work area are now locked.

When the object(s) are locked, a small lock in the lower left hand corner of the icon
indicates that the disruptive tasks are locked for that object. If you attempt to
perform a disruptive task on a locked object, a window is displayed indicating the
object is locked.

If you want to unlock an object or a group of objects, you still need to follow the
previously described unlocking procedure.

Monitoring and operating the support element console: an overview

Use Views and the work area to start tasks for monitoring and operating the support
element console. These tasks are referred to as console actions to distinguish them
from tasks the console provides for monitoring and operating the system. Unlike the
system tasks, the implied target, and only target, of a console action is the support
element console itself.

To start a console action:

1. Open Console Actions from Views.
This displays the console actions in the Console Actions Work Area.
2. In the Console Actions Work Area, locate the console action you want to start.
3. Double-click on the console action to start it.
Starting the console action displays the windows and messages you must use
to complete the console action.

See Chapter 16, “Console actions,” on page 241 for specific descriptions of all
console actions.

Chapter 3. Using the classic style user interface 55

Opening an online book
Use Views and the work area to open online books provided with the Support
Element Console Application. The books provide information about using the
application and support element workplace. The books include:
Application Programming Interfaces
This online book, SB10-7030, provides information for developing system
management applications that will provide integrated hardware and software
system management solutions using the application programming
interfaces.
Support Element Operations Guide
This online book is the publication you are currently using. It provides
information about the Support Element Console Application and about using
the support element workplace to monitor and operate your system.

To open an online book:

1. Open Books from Views area.

2. In the Books Work Area, locate the book you want to open and double-click on
the book icon. The book remains open until you close it.

Getting online help

Provides both general and specific information. Any icon can be dragged and
dropped on the Help icon for information, or the Help icon can be dragged and
dropped on any of the icons in the Views, Tasks, or Work areas of the Support
Element Console window.

Help will display the section of this online document that describes the object that
the help icon was dropped on. Once that information is displayed, you may go to
any other part of the document for other information.

To display Help for an object or Support Element Console area:

1. Drag and drop the Help icon on the object or the area of the Support Element
Console that you want help information for.

The Help window displays help information for the object or area of the Support
Element Console where you dropped the help icon.

Displaying hover help for workplace objects

Online help provides extensive, comprehensive information for the areas and
objects on the support element workplace. As you become more familiar with
workplace objects, and if you have less frequent need for the amount and depth of
information provided by online help, consider using hover help instead. Hover help
is a brief description of an object’s, contents, usage, or purpose. The help is
displayed in a compact pop-up window that hovers above the object. You can set
hover help either on or off, depending on what you want. Initially, hover help is set
off.

56 Support Element Operations Guide

 To set hover help on for your workplace:
v Open Console Actions from Views.
This displays the console actions in the Console Actions Work Area.
v Open the User Settings task from the Console Actions Work Area.
This User Settings window is displayed.
v Select the Controls tab on the User Settings window.
v Select Show hover help from the menu choice. This places a check next to it
and sets hover help on. If you want to set hover help off, uncheck the choice by
selecting it from the menu.
v Click Apply, then click OK to enable hover help.

Note: Hover help is not displayed immediately. The cursor must remain placed on
a workplace object for several seconds to display the help.

You can work with the objects on the workplace using the mouse to select them.
This is known as the drag and drop technique. This involves using the mouse to
pick up one or more objects, dragging them to a task, and then dropping them.
These techniques are examples of what is known as direct manipulation.

Opening the workplace pop-up menu

This pop-up menu is a shortcut for navigating the workplace. The menu choices in
the pop-up are the names of the Console Actions in the Work Area and the Groups
in the Work Area. An arrow to the right of a menu choice indicates additional
choices are available on a cascaded menu. A cascaded menu provides additional
menu choices and may include additional cascaded menus. Each cascaded menu
provides a more direct shortcut for locating and opening icons in a particular view.

To open the pop-up menu, click the right mouse button once on any empty area in
the workplace. When the pop-up menu displays, select the view you want to see.

Chapter 3. Using the classic style user interface 57

 The pop-up menu provides shortcuts for:
v Locating groups and objects
v Opening a CPC or image details windows
v Starting console actions

To open the workplace pop-up menu:

1. Right click on empty space in any area of the workplace.

Note: You must right click on an empty space to display the workplace pop-up
menu. It will not be displayed if you right click on an icon or icon label.

58 Support Element Operations Guide

Chapter 4. Daily operation of the system
This section describes the tasks from the Daily task list used most often on a daily
basis for monitoring and operating the system.

To launch the tasks from the Daily task list using the classic style user interface,
see Chapter 2, “Using the tree style user interface,” on page 9, or if you are using
the tree style user interface, see Chapter 3, “Using the classic style user interface,”
on page 35.

Starting the system

If you have experience using other systems, the steps you took to start the system
and make it operational may have included:
1. Turning on system power
2. Performing a power-on reset of the system
3. Allocating system resources
4. Initializing logical partitions
5. Allocating logical partition resources
6. Loading a control program or operating system for the system or each logical
partition. (This step may be referred to as an initial program load (IPL) on other
systems).

Furthermore, the steps you took may have depended on:

v The current operational status of the system.
v The operational capabilities and characteristics you wanted the system to have.

Using the support element workplace, starting the system, and making it operational
requires only to activate the system.

When you activate the system, you do not need to consider its current status to
determine the steps you must take to make it operational. Activating the system,
referred to also as system activation, automatically determines the system’s current
status and then performs the steps necessary to make it operational.

Successfully activating the system still requires you to define the operational
capabilities and characteristics you want the system to have, but you can set up
and save that information in advance, and assign it to the system. Then, activating
the system automatically uses the assigned information rather than requiring you to
provide it manually during the process.

Activation
Activation is a process that makes an object operational, where the object can be a
central processor complex (CPC) or an image, and operational means either:
v The object is ready to have a control program or operating system loaded.
v The object has loaded and is running a control program or operating system.

Activation makes an object operational by:

v Using predefined information, referred to as an activation profile, to set the
operational capabilities and characteristics of the object.
v Checking the current status of the object, and then performing only the
operations necessary to make it operational.

© Copyright IBM Corp. 2008 59

 So using activation is not limited to starting the system. Using activation is
recommended whenever you want to make the CPC or its images operational.

A complete activation activates the CPC and its images completely and in a single
step. The result of a complete activation is an operational CPC with images loaded
and running operating systems. The current status of the CPC and its images
determines which operations are performed during activation to make them
operational. Activation may include:
1. Turning CPC power on.
2. Performing a power-on reset, which includes allocating system resources to the
CPC.
3. Then either:
v Loading a single image of the CPC with a control program or operating
system.
v Or activating logical partitions to support multiple images.
Activating each logical partition includes:
a. Initializing it.
b. Allocating system resources to it.
c. Loading it with a control program or operating system.

Since the status of the CPC and its images determines which operations must be
performed during activation to make them operational, one or more operations listed
above may not be performed during activation. For example:
v Activating the CPC does not perform a power-on reset if the CPC has already
been power-on reset and the applicable settings in its assigned activation profile,
such as the operating mode and active input/output configuration data set
(IOCDS), are already in effect.
v Activating the CPC does not perform any operations if the CPC is already
operational and all settings in its assigned activation profile are already in effect.
Notes:
1. To determine which operations were performed during an activation, view the
support element’s console events. See “Viewing console events” on page 259
for instructions.
2. Activation performs a power-on reset and a load only if necessary. If you want
to perform a power-on reset or a load unconditionally, you can use tasks in the
CPC Recovery task list. But it is recommended that these tasks be used only
for error recovery. For more information, see Chapter 5, “Error recovery,” on
page 81.

Activation profiles
The predefined information used to activate an object is referred to as an activation
profile. There are four types of activation profiles:

60 Support Element Operations Guide

v A reset profile is used to activate a central processor complex (CPC) and its
images.
v An image profile is used to activate an image of a CPC previously activated.
v A load profile is used to load a previously activated image with a control program
or operating system.
v A group profile is used to define the group capacity value that can be customized
in determining the allocation and management of processor resources assigned
to the logical partition group.

You will customize activation profiles to define the information that sets the
operational capabilities and characteristics of the objects you want to activate.

Activating with a reset profile

To support your normal, day-to-day system operations, you will activate a central
processor complex (CPC) with a reset profile. Activating a CPC with a properly
customized reset profile includes initializing its images, if necessary, and can
include loading the images. That is, a properly customized reset profile includes the
load profile or image profiles necessary to perform a complete activation of a CPC
and its images.

Activating with other profiles

After activating a central processor complex (CPC) with a reset profile, you can use
the other types of activation profiles to establish a different or alternate operational
capabilities and characteristics for the CPC’s images, but without performing a
complete activation of the CPC again. You can:

Chapter 4. Daily operation of the system 61

 v Activate an image with a load profile to load a different control program or
operating system.
v On a CPC, activate an image with its image profile to activate it individually
rather than by activating the CPC.

Getting ready for an activation

To successfully activate a central processor complex (CPC), you’ll need:
v A properly customized reset profile assigned to the CPC and customized to meet
your unique needs for operating the CPC.
v Access to resources referred to in the reset profile:
– An input/output configuration data set (IOCDS) for defining the CPC’s
input/output (I/O) configuration.
– Operating systems for loading images.

Preparing an IOCDS
You must build an IOCDS and it must be stored on a CPC’s support element before
you can activate the CPC.

An IOCDS is used during a power-on reset to define your I/O configuration to the
channel subsystem of the CPC. The I/O configuration is the set of all I/O devices,
control units, and channel paths available to the CPC.

You can build an IOCDS by using an input/output configuration program (IOCP):

v An IOCP may be available as a batch program with your operating system.
For information about using the IOCP, see: Input/Output Configuration Program
User’s Guide, SB10-7037.
v A stand-alone IOCP also is available with the support element.
For information about using the stand-alone IOCP, see: Stand-Alone IOCP User’s
Guide, SB10-7040.

Preparing to load images

To load an image during the activation of the CPC or logical partition that supports
it, you must make an operating system or control program available for loading the
image.

An operating system or control program is available for loading an image if it can be

loaded by using I/O devices defined in the IOCDS used to activate the CPC. For
example, with a properly defined I/O configuration, the operating system or control
program could be:
v Read from a DASD.
v Read from a tape device to a DASD, then read from the DASD.
v Read from a tape device directly.

Note: Activating a coupling facility, which loads an image with coupling facility
control code (CFCC), does not require using devices in the CPC’s I/O
configuration. The CFCC is loaded from the CPC’s support element.

Activating the CPC

Use the support element workplace to start the task for activating the central
processor complex (CPC).

62 Support Element Operations Guide

Note: Activating a CPC can be considered disruptive. If the CPC is locked, unlock
it. See “Setting object locking for disruptive tasks on an object” on page 54.

To activate the CPC:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user mode (see “Establishing a support element
console session from a Hardware Management Console” on page 3).
2. You must customize a reset profile and assign it to the CPC. See “Getting ready
to operate the system: customizing activation profiles” on page 89.
3. The CPC must have access to the input/output configuration data set (IOCDS)
and operating systems referred to in the reset profile. See “Getting ready for an
activation” on page 62.
4. Locate the CPC to work with.
5. Locate and open the Daily task list
6. Locate and open the Activate task.
7. Review the information on the Activate Task Confirmation window to verify the
object you will activate is the CPC, and the activation profile it will use is the
one you want.
8. If the information is correct, click Yes to perform the activation.
The Activate Progress window indicates the progress of the activation, and the
outcome.
9. Click OK to close the window when the activation completes successfully.
Otherwise, if the activation does not complete successfully, follow the directions
on the window to determine the problem and how to correct it.

After the CPC is activated, you can use the Activate task again, if necessary, to
selectively activate its images.

Activating an image
Use the support element workplace to start the task for activating an image of the
central processor complex (CPC).

An image is a set of CPC resources capable of running a control program or

operating system. One or more images is created during a power-on reset of a
CPC. Each logical partition is an image.

To activate an image:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system
programmer, or service representative user mode (see “Establishing a support
element console session from a Hardware Management Console” on page 3).
2. You must activate the CPC, and the activation must complete with at least a
successful power-on reset of the CPC.

Chapter 4. Daily operation of the system 63

 3. You must customize an activation profile and assign it to the image. See
“Getting ready to operate the system: customizing activation profiles” on page
89.
4. The system must have access to the operating system referred to in the
activation profile. See “Getting ready for an activation” on page 62.
5. Locate the Image to which you assigned the activation profile.

Note: Activating an image can be considered disruptive. If the CPC image is

locked, unlock it. See “Setting object locking for disruptive tasks on an
object” on page 54.
6. Locate and open the Daily task list.
7. Locate and open the Activate task .
8. Review the information on the Activate Task Confirmation window to verify
the object you will activate is the image, and the activation profile it will use is
the one you want.
9. If the information is correct, Click Yes to perform the activation.
This displays the Activate Progress window. The window indicates the progress
of the activation, and the outcome.
10. Click OK to close the window when the activation completes successfully.
Otherwise, if the activation does not complete successfully, follow the
directions on the window to determine the problem and how to correct it.

Checking hardware messages from the CPC

The central processor complex (CPC) and Support Element Console Application
send messages to the support element console to notify you of significant events
that involve or affect the use of CPC hardware and licensed internal code. The
messages are referred to as hardware messages.

Hardware messages may be sent to the support element console at any time. The
support element console receives the messages automatically, stores them in a
message log, and turns on several console indicators to help you recognize that
hardware messages were received.

The support element console can store a maximum of five hundred messages in its
hardware message log. If the message log becomes full, the support element
console continues to receive and store new messages, but deletes the log’s oldest
message for each new message that is received. Promptly view, act on, and delete
hardware messages to avoid filling the message log and losing messages.

Recognizing when hardware messages were received

While the Support Element Console Application is running, it changes the
background color of one or more icons to indicate the support element console
received a hardware message from the central processor complex (CPC).

The type and number of icons changed upon receiving a hardware message
depends on whether anyone is logged on the console at the time:
v While logged on, the background color of the following icons changes when the
support element console receives a hardware message:
– The background color of the CPC changes to blue, the color set for indicating
a hardware message was received.
– The background color of each group that contains the CPC changes to blue.

64 Support Element Operations Guide

 – The background color of the Hardware Messages task flashes blue. That is,
its background color alternates between blue and the color of the tasks area.
This is the task you will use to view the hardware messages.
v While logged off, the background color of the Hardware Messages icon on the
logon window flashes blue when the support element console receives a
hardware message. That is, its background color alternates between blue and
the color of the logon window.

Note: The logon window is titled Support Element Logon. The Hardware
Messages icon is located in the Message indicators area of the window.

In addition to changing the background colors of icons, the support element console
beeps once when it receives a hardware message, regardless of whether anyone is
logged on or logged off the console at the time.

The Hardware Messages icon continues to flash blue until you acknowledge
receiving the new hardware messages by taking action on any one of them. The
background color of the CPC and the groups that contain it remains blue until you
take action on each new hardware message. Taking action on hardware messages
begins with viewing them.

Viewing hardware messages

View hardware messages to remain informed of events that involve or affect the
use of the central processor complex (CPC). Upon viewing hardware messages,
you can also:
v Get more details for messages to determine what actions to take in response.
v Delete messages you no longer need.
v After you open the hardware messages notebook, use the online Help for more
information on using it to view and delete hardware messages.

To get more details for messages:

1. Locate the CPC to work with.
2. Locate and open the Hardware Messages task.
3. Select each message for which you want more details, then click Details.
This opens a Details window, one at a time, for each selected message for
which details are available.
4. Read the information and follow the directions on each details window to
determine what action to take in response to a message. In many cases, you
can use a details window itself to start the action.

Using the support element console as an operating system console

Console integration is a facility of the support element console. An operating system
that supports console integration can be customized to allow using the support
element console, if necessary, as an operating system console.

Under normal conditions, while other operating system consoles are available, the
support element console should not be used as an operating system console. That
is, the console integration facility is not intended to make the support element
console the primary user interface to an operating system.

The console integration facility is intended instead to allow using the support
element console as an operating system console only when other operating system

Chapter 4. Daily operation of the system 65

 consoles are not available. Other operating system consoles are not available, for
example, during initialization of the operating system, or when they become
unavailable due to outages or failures.

Refer to the publications provided with your operating system for more information
about whether it supports console integration, and how to customize it to allow
using the support element console as an operating system console.

Checking operating system messages from images

An image is a set of central processor complex (CPC) resources capable of running
a control program or operating system. An operating system running in an image
sends messages to operating system consoles to notify you of significant events
that involve or affect the use of the operating system. The messages are referred to
as operating system messages.

If an operating system running in an image supports console integration and is

customized to allow using the support element console as an operating system
console, then the support element console can also receive operating system
messages.

An operating system may issue any number of messages at any time. The support
element receives the messages automatically and stores them in a message log.
The support element also turns on several console indicators to help you recognize
that priority or held operating system messages were received. A priority or held
operating system message either requires a response from the console operator or
notifies the console operator of a critical condition that requires immediate attention.

The support element can store an average of approximately 200 (depending on the
length of each message) messages in its operating system message log per image.
If the message log becomes full, the support element continues to receive and store
new messages, but deletes one or more of the log’s oldest non-held, non-priority
messages to make room for each new message. If there are not any non-held,
non-priority messages, the oldest non-held priority, held, or priority message will be
deleted.

Recognizing when priority or held operating system messages

were received
While the Support Element Console Application is running, it changes the
background color of one or more icons to indicate the support element received a
priority or held operating system message from an image supported by the central
processor complex (CPC).

The type and number of icons changed upon receiving a priority or held operating
system message depends on whether anyone is logged on the console at the time:
v While logged on, the background colors of the following icons change when the
support element receives a priority operating system message:
– The background color of the image that supports the operating system
changes to cyan, the color set for indicating that a priority or held operating
system message was received.
– The background color of each group that contains the image changes to cyan.
– The background color of the Operating System Messages task flashes cyan.
That is, its background color alternates between cyan and the color of the
tasks area. This is the task you will use to view the operating system
messages.

66 Support Element Operations Guide

 v While logged off, the background color of the Operating System Messages icon
flashes cyan when the support element receives a priority or held operating
system message. That is, its background color alternates between cyan and the
color of the logon window.

Note: The logon window is titled Support Element Logon. The Operating
System Messages icon is located in the Message indicators area of the
window.

The Operating System Messages icon continues to flash cyan until you
acknowledge receiving the new priority or held operating system messages by
viewing them. Likewise, the background colors of the image and the groups that
contain it remain cyan until you acknowledge receiving the new priority or held
operating system messages by viewing them. While viewing operating system
messages, you have the option of responding to them.

Viewing operating system messages

View operating system messages to remain informed of events that involve or affect
the use of images supported by the central processor complex (CPC). Upon
viewing operating system messages, you can also:
v Send responses to messages.
v Delete messages you no longer need.
v Use the online Help for more information to view, respond to, or delete operating
system messages.

To view operating system messages:

1. Locate the images for which you want to view operating system messages.
2. Locate and open the Operating System Messages task.
3. This opens the Operating System Messages notebook. Each page lists the
operating system messages from each image in the target group or among the
selected images. The notebook provides push buttons for responding to
messages and for deleting them.
The color of each message indicates its type:
Black Indicates an informational message that normally does not
require a response from the console operator.
Blue Indicates a held message that requires a response from the
console operator.
Red Indicates a priority message about a critical condition that
requires immediate attention.

Responding to an operating system message requires receiving an operating

system message first. You can use Operating System Messages also to send
commands to an operating system, regardless of whether you’ve received
messages from it.

Sending commands to operating systems

You can use a support element console to send commands, at any time, to
operating systems running in images supported by the central processor complex
(CPC).

To send commands to an operating system:

Chapter 4. Daily operation of the system 67

 1. Locate a target: either a group of images or individual images. Using a group of
images will allow sending commands to each operating system running on
images in the group, while using individual images will allow sending commands
to their operating systems only.
2. Locate and open the Operating System Messages task.
This opens the Operating System Messages notebook. Each page lists the
operating system messages, if any, from each image in the target group or
among the selected images. The window provides a Send command for
sending commands to the operating systems running on the images.
Use the online Help for more information to send commands to an operating
system.

Note: The Send command is not available if the operating system running on
an image does not support receiving commands from the support
element console.

Monitoring system activity

Successfully activating the system makes it capable of doing work. The operating
systems and applications running on the system determine its workload. Over any
period of time, and depending on its workload, the system will spend some of the
time doing work and the rest of the time waiting to do work. That is, the system will
be either busy or idle, respectively. System activity is a measurement of how busy
the system is over a period of time. Since system activity is likely to vary over
consecutive periods of time, you need to see those consecutive variations in activity
to get an accurate idea of how busy the system is.

Note: The utilization reported by Activity for most channel types coincides with the
utilization reported by Resource Management Facility (RMF™). For Fiber
Channels, the Activity task considers the channel to be busy any time an
operation is pending, even if the channel is waiting for a device to respond.
RMF looks at the amount of work done versus the amount of work that could
be done by the channel. Therefore, if you have devices that are relatively
slow to respond, leaving the channel waiting for a response that would be
otherwise idle, Activity shows a utilization that is significantly higher than that
reported by RMF

Your system is the central processor complex (CPC) and the physical and logical
resources it uses to do work. The CPC’s support element provides a function,
referred to as system activity analysis, for monitoring system activity by monitoring
the activity, or usage, of a subset of the CPC’s physical and logical resources:
v Central processors (CPs)
– General purpose processors
– Internal Coupling Facility (ICF) processors
– Integrated Facility for Linux (IFL) processors
– zSereis Application Assist Processors (zAAPs)
– IBM System z9 Integrated Information Processors (zIIPs)
v System assist processors (SAPs)
v Channels
v Logical partition(s) and logical processor(s)
v Power consumption usage
v Air input temperature.

68 Support Element Operations Guide

 Note: Central processors (CPs) include the General purpose processors, Internal
Coupling Facility (ICF) processors, Integrated facility for Linux (IFL)
processors, zSeries application assist processors (zAAPs), and IBM System
z9 Integrated Information Processors (zIIPs).

Monitoring system activity does not require monitoring the usage of all CPC
resources at once. Instead, you can use a system activity profile to define the
particular resources you want to monitor. For each resource you choose to monitor,
you can use the system activity profile to:
v Set conditions for which you want the resource’s usage reported or ignored.
v Indicate how you want the resource’s usage presented.

System activity analysis

System activity analysis is a function of the Support Element Console Application
that:
v Monitors and quantifies the activity of a subset of physical and logical resources,
or system resources, used by the central processor complex (CPC).
Quantified activity is referred to here as an activity summary.
v Uses graphics to present activity summaries of monitored resources.
v Regularly and automatically updates activity summaries with current information.
v Monitors the power consumption and input termperature.

The system resources monitored during system activity analysis, and how their
activity summaries are presented, are determined by the information in a system
activity profile.

System activity profiles

A system activity profile is a set of information that defines:
v The system resources you want to monitor during system activity analysis.
v How you want activity summaries of the monitored resources presented.

More specifically, the information in a system activity profile:

v Identifies the central processors (CPs), system assist processors (SAPs), logical
partitions, logical processors, and channels for which you want to monitor activity.

Note: Central processors (CPs) include the General purpose processors,

Internal Coupling Facility (ICF) processors, Integrated facility for Linux
(IFL) processors, zSeries Application Assist Processors (zAAPs), and IBM
System z9 Integrated Information Processors (zIIPs).
v Focuses the measurement of processor activity on specific program status word
(PSW) keys or on a specific operating state, if applicable.
v Sets thresholds for processor and channel activity, to emphasize activity that
does not meet a minimum amount of expected use, or exceeds a maximum
amount of expected use.
v Indicates the amount and arrangement of information presented in activity
summaries, and how often to update the activity summaries with new information
from the system resources being monitored.

A set of sample system activity profiles is provided by IBM with the Support
Element Console Application. Consider using the sample system activity profiles for

Chapter 4. Daily operation of the system 69

 system activity analysis until you become familiar with their contents and purpose.
Then you can use the sample profiles as templates for customizing your own
system activity profiles.

Sample system activity profiles

A set of sample system activity profiles is provided by IBM with the Support
Element Console Application. You can use the sample profiles to monitor your
system activity. You can use them also as templates for creating new profiles.

The following table shows the name of each sample system activity profile,
describes its intended use, and identifies the system activities it is set to display
during system activity analysis.
Table 1. Sample system activity profiles
DEFAULT This profile is useful for monitoring the activity of all physical processors and the
busiest channels. It is customized for displaying the individual and average activity
of all central processors (CPs), the individual and average activity of all system
assist processors (SAPs), and the activity of the 31 most active channels.
CHANHIGH This profile is useful for monitoring the activity of the busiest channels. It is
customized for displaying the activity of the 49 most active channels.
CHANLOW This profile is useful for monitoring the activity of the least busy channels. It is
customized for displaying the activity of the 49 least active channels.
LPARSUMA This profile is useful for monitoring the activity of up to 30 logical partitions and
some physical processor activity. It is customized for displaying the individual activity
of all logical partitions, the individual and average activity of all CPs, and the
individual and average activity of all SAPs.

LPARSUMB This profile is useful for monitoring the activity of up to 10 logical partitions, all
physical processors, and the busiest channels. It is customized for displaying the
individual activity of all logical partitions, the average activity of all CPs, and the
activity of the 37 most active channels.
Note: You can customize this profile, or a copy of it, to display activity for up to 30
logical partitions.
PROCESSOR This profile is useful for monitoring the activity of all physical processors. It is
customized for displaying the individual and average activity of all CPs, and the
individual and average activity of all SAPs.
PROCLIST This profile is useful for monitoring the activity of all physical processors and the
busiest channels. It is customized for displaying the individual and average activity
of all CPs, the individual and average activity of all SAPs, and the activity of the 31
most active channels.
PROCUSAGEBYKEY This profile is useful for situations, like tuning applications, that require monitoring
CP activity while the program status word (PSW) key is set to a specific value. It is
customized for displaying the average activity of all CPs while the PSW key is X'0',
the average activity of all CPs while the PSW key is X'1', the average activity of all
CPs while the PSW key is X'2', and so on for each of the possible values of the
PSW key: X'0' through X'F'. The profile is customized also for displaying the average
activity of all CPs, regardless of the value of the PSW key.
VMPROCESSOR This profile is useful for monitoring the activity of all physical processors while using
an operating system, like some versions of VM, that may put CPs in an active wait
state. It is customized for displaying the individual and average activity of all CPs
(excluding activity in active wait states), and the individual and average activity of all
SAPs. For more information, see “Effect of an active wait state on processing
activity” on page 72.

70 Support Element Operations Guide

Table 1. Sample system activity profiles (continued)
VMPROCLIST This profile is useful for monitoring the activity of all physical processors and the
busiest channels while using an operating system, like some versions of z/VM® and
VM, that may put CPs in an active wait state. It is customized for displaying the
individual and average activity of all CPs (excluding activity in active wait states), the
individual and average activity of all SAPs, and the activity of the 31 most active
channels. For more information, see “Effect of an active wait state on processing
activity” on page 72.

You can use any sample system activity profiles immediately to start system activity
analysis if the profiles suit your needs for monitoring system activity. For
instructions, see “Starting system activity analysis.”

If you want to monitor other types of system activity, or if you simply want to see
the exact information in a system activity profile, you can use the support element
workplace to work with system activity profiles as needed.

Starting system activity analysis

Start system activity analysis of the central processor complex (CPC) from its
support element console to monitor the CPC’s system activity. System activity
includes the channel activity and physical processing activity that has been defined
in the system activity profiles that are stored in the selected CPC. For more
information about assigning and customizing activity profiles for the CPC, see
“Getting ready to monitor the system: customizing system activity profiles” on page
142.

Because you are selecting a single object for the task, both a summary window and
a details window appear. This details window shows the detailed System Activity
Display (SAD) for an object as a rectangular chart.

The Summary window displays the system activity for each object is on a single
line. The activity displayed as a blue bar is the average of all reported physical
processor processing activity for the CPC. The activity displayed as a green bar is
the average of all reported channel activity for the CPC. One or both types of
activities can be displayed for the selected objects. A red bar indicates that activity
data is not available for the object.

Starting the Activity task when another instance of the task is already running does
not stop the previous task instance.

Note: The utilization reported by the Activity task for most channel types will agree
with the utilization reported by Resource Measurement Facility (RMF™). For
fiber channels, however, this task considers the channel to be busy any time
an operation is pending, even if the channel is waiting for a device to
respond. Whereas, RMF looks at the amount of work done versus the
amount of work that could be done by the channel. This means that if you
have response but otherwise idle, Activity will show a utilization that is
significantly higher than that reported by RMF.

To start system activity analysis:

Chapter 4. Daily operation of the system 71

 1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user mode (see “Establishing a support element
console session from a Hardware Management Console” on page 3).
2. Open a list of system activity profiles, using either:
v The same task you use to work with system activity profiles. For instructions,
see “Opening a list of system activity profiles” on page 142.
v Or the task provided on the support element workplace specifically for
monitoring system activity.
3. Locate the CPC to work with.
4. Locate and open the Daily task list.
5. Locate and open the Activity task.
6. Starting system activity analysis displays the System Activity window. The
window uses labels to identify the types of activity being monitored, and
graphics to indicate the amounts of activity as percentages, from 0% to 100%.
Use the online Help for more information on using the window to monitor
system activity.
Notes:
a. To monitor the true processing activity while using an operating system that
uses an active wait state, like some versions of z/VM and VM, start system
activity analysis with a system activity profile customized to exclude
processing activity during an active wait state. For more information, see
“Effect of an active wait state on processing activity.”
b. Although the System Activity window’s range for displaying activity
graphically is 0% to 100%, the processing activity of logical partitions that
share processors may exceed 100%. For more information, see “Processing
activity for logical partitions using shared processors” on page 73.
c. You can use the System Activity window to view a detailed snapshot of a
shared channel’s usage by each logical partition that shares it. For more
information, see “Channel activity for logical partitions using shared
channels” on page 74.

Effect of an active wait state on processing activity

By using an active wait state, an operating system does not yield idle processing
resources to the system. This affects how you should monitor processing activity for
such systems.

During system activity analysis of all processing activity, central processors (CPs) in
an active wait state are considered busy rather than idle. Since the CPs are either
actually busy, or in an active wait state that is considered busy, activity summaries
of such CPs always indicate 100% usage.

To monitor the true processing activity, you can customize a system activity profile
for monitoring processing activity that excludes a CP’s activity while it is in an active
wait state. Two of the sample system activity profiles, named VMPROCESSOR and
VMPROCLIST, are examples of such profiles. They are customized, as follows, for
monitoring processing activity while using a z/VM and VM operating system that
uses an active wait state:
v Processing activity includes the individual and average activity of all CPs.
v But excludes CP activity in the supervisor state while the program status word
(PSW) key is X'3'. These conditions are true while a CP is in an active wait state.

72 Support Element Operations Guide

Refer to the documentation provided with your operating system to determine
whether it uses an active wait state, and if so, to determine also the processor state
and PSW key value of a CP while it is in an active wait state.

Processing activity for logical partitions using shared

processors
A logical partition is assigned logical processors by the activation profile used to
activate it. The activation profile also determines whether the logical processors are
supported by dedicated processing resources:
v Logical partitions activated with dedicated processing resources have exclusive
use of a central processor (CP) for each of its assigned logical processors.
v Logical partitions activated without dedicated processing resources share the use
of non-dedicated CPs. A logical partition’s processing weight and its setting for
whether the processing weight is capped, which are both set by the activation
profile also, determine the logical partition’s share of non-dedicated processing
resources.

Note: For instructions for locating this information in an activation profile, see
“Assigning initial logical or reserved processors” on page 110.

If a logical partition’s processing weight is not capped, its processing weight is the
minimum share of non-dedicated processing resources guaranteed to the logical
partition when all non-dedicated processing resources are in use. But when
non-dedicated processing resources are available, the logical partition can borrow
them, if necessary, in excess of the share ordinarily provided by its processing
weight.

During system activity analysis, the processing activity of a logical partition that
shares non-dedicated processing resources is normalized. Normalized processing
activity is 100% while the logical partition is using the full share of processing
resources provided by its processing weight. If a logical partition’s processing
weight is not capped, its processing activity exceeds 100% whenever the logical
partition uses non-dedicated processing resources in excess of the share provided
by its processing weight.

During system activity analysis, the System Activity window uses labels to identify
the types of activity being monitored, and graphics to indicate the amounts of
activity as percentages. Since the window’s range for displaying activity graphically
is 0% to 100%, actual amounts of normalized processing activity that exceed 100%
are not displayed graphically. Instead, labels and graphics are altered, as follows, to
identify and indicate normalized processing activity that exceeds 100%:
v The label is altered to display the actual percentage of normalized processing
activity.
v The graphics are colored differently while normalized processing activity exceeds
100%.
v If the processing activity being monitored includes activity in both the problem
state and the supervisor state, the graphics indicate the ratio of activity in each
state, rather than the actual percentage of activity in each state, while the total
normalized processing activity exceeds 100%.
For example, if the total normalized processing activity is 200%, and the graphics
indicate 60% activity in the problem state and 40% activity in the supervisor
state, then the actual activity in the problem state is 120% (60% of 200%), and
the actual activity in the supervisor state is 80% (40% of 200%).

Chapter 4. Daily operation of the system 73

 Note: Open the legend for the System Activity window for more information about
the labels and graphics used to identify and indicate processing activity that
exceeds 100%:
1. Select Actions from the window’s menu bar.
2. Select Show legend from the menu to display the window’s legend.

Channel activity for logical partitions using shared channels

A shared channel can be online or configured online to more than one logical
partition at the same time. An input/output configuration data set (IOCDS) defines
whether a channel is shared, and which logical partitions can share it. The
activation profile used to activate a central processor complex (CPC) determines
which IOCDS is used to define the input/output (I/O) configurations of the CPC’s
logical partitions.

During system activity analysis, the label for a channel activity summary includes an
S to indicate the channel is shared. The graphics for a shared channel activity
summary displays in two portions:
v The first portion of the activity summary displays channel usage by one logical
partition: either a specific logical partition or the logical partition for which the
channel usage is highest.

Note: The system activity profile used to start system activity analysis
determines which logical partition has its individual channel usage
displayed.
v The second portion of the activity summary displays the combined channel usage
by all other logical partitions that share it.

While monitoring shared channel activity, you can use the System Activity window
to view a detailed snapshot of a shared channel’s usage by each logical partition
that shares it.
1. Locate the label and graphics that identify and indicate activity on the shared
channel.
2. Double-click with the left mouse button on the shared channel’s graphics.
This displays the System Activity EMIF Details window. It displays a pie chart
graphic that shows the channel usage by each logical partition that shares it,
and the channel’s unused capacity, if any.

Note: System activity analysis is suspended while you view the details of a
shared channel’s usage. As such, the window displays a snapshot of the
shared channel’s usage at the time you requested it. The snapshot will
not be refreshed with new information.
3. Click OK to close the window and resume system activity analysis.
4. Repeat these steps to view another detailed snapshot of the shared channel’s
usage, if needed.

Resetting the system or logical partitions

A reset normal initializes a system or logical partition by:
v Clearing its pending interruptions.
v Resetting its channel subsystem.
v Resetting its processors.

74 Support Element Operations Guide

 If you have experience using other systems, a reset normal may have been referred
to as a system-reset-normal.

A reset normal prepares a system or logical partition for loading it with an operating
system. On the support element workplace, images support operating systems,
images are your targets for resets. An image represents a logical partition, while the
CPC is activated.

A reset normal is one of several recovery tasks that you can use to attempt to
recover from hardware or software errors. A reset normal is often effective but less
disruptive than other tasks, which typically makes it the first task attempted to
recover from errors when they occur. Follow your local error recovery procedures
for determining when to perform a reset normal.

To perform a reset normal:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user mode (see “Establishing a support element
console session from a Hardware Management Console” on page 3).
2. Locate the Image you want to work with.

Note: Performing a reset normal on an image can be considered disruptive. If

the CPC image is locked, unlock it. See “Setting object locking for
disruptive tasks on an object” on page 54.
3. Locate and open the Daily task list.
4. Locate and open the Reset Normal task.
5. Review the information on the confirmation window to verify the image you will
reset.
6. If the information is correct, Click Perform reset to perform the reset normal.
7. Click OK to close the progress window when the reset completes successfully.
Otherwise, if the reset does not complete successfully, follow the directions on
the window, or on any messages that may display, to determine the problem
and how to correct it.

Note: For more information about all recovery tasks, including reset normal, see
Chapter 5, “Error recovery,” on page 81.

Shutting down and turning off the system

Deactivation is an orderly process for shutting down and turning off the system.

Shutting down and turning off the system, referred to also as deactivating the
system, includes:
v Ending hardware and software activity.
v Clearing, releasing, and deallocating hardware resources.
v Turning off power.

Chapter 4. Daily operation of the system 75

Deactivating the CPC
You can use the support element workplace to start the task for deactivating the
central processor complex (CPC). The target, or object, of a deactivation can be a
CPC or an image. For more information about deactivating individual logical
partitions, see “Deactivating an image.”

Note: Although you can use the power switch on the CPC itself to turn it off, you
should turn off CPC power by deactivating it instead. Unlike using the CPC’s
power switch, deactivating the CPC includes clearing, releasing, and
deallocating its hardware resources before turning off its power.

To deactivate the CPC:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user mode (see “Establishing a support element
console session from a Hardware Management Console” on page 3).
2. End all operating systems supported by the CPC’s images.
Important: If you do not end all operating systems before deactivating the CPC,
operating system activity will be abruptly ended during deactivation, resulting in
a possible loss of data.
3. Locate the CPC to work with.

Note: Deactivating a CPC can be considered disruptive. If the CPC is locked,

unlock it. See “Setting object locking for disruptive tasks on an object” on
page 54.
4. Locate and open the Daily task list.
5. Locate and open the Deactivate task.
6. Review the information on the Deactivate Task Confirmation window to verify
the object you will deactivate is the CPC.
7. If the information is correct, click Yes to perform the deactivation.
The Deactivate Progress window indicates the progress of the deactivation, and
the outcome.
8. Click OK to close the window when the deactivation completes successfully.
Otherwise, if the deactivation does not complete successfully, follow the
directions on the window to determine the problem and how to correct it.

After the CPC is deactivated, it and its images are no longer operational.

Deactivating an image
You can use the support element workplace to start the task for deactivating an
image of the central processor complex (CPC).

An image is a set of CPC resources capable of running a control program or

operating system. One or more images is created during a power-on reset of a
CPC. Each logical partition is an image. You can use one or more images as
deactivation targets to deactivate individual logical partitions.

To deactivate an image:

76 Support Element Operations Guide

 1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user mode (see “Establishing a support element
console session from a Hardware Management Console” on page 3).
2. Locate the Image you want to deactivate.

Note: Deactivating an image can be considered disruptive. If the CPC image is

locked, unlock it. See “Setting object locking for disruptive tasks on an
object” on page 54.
3. Locate and open the Daily task list.
4. Locate and open the Deactivate task.
5. Review the information on the Deactivate Task Confirmation window to verify
the object you will deactivate is the image.
6. If the information is correct, click Yes to perform the deactivation.
The Deactivate Progress window indicates the progress of the deactivation, and
the outcome.
7. Click OK to close the window when the deactivation completes successfully.
Otherwise, if the deactivation does not complete successfully, follow the
directions on the window to determine the problem and how to correct it.

After the image is deactivated, the logical partition it supported is no longer

operational. The CPC and images previously activated to support other logical
partitions remain operational.

Logging off the support element console

Log off the support element of each system that is to be powered off:

v Locate and open the Logoff or Disconnect task.

v Click OK.

After logging off the integrated support element, shutdown the Hardware
Management Console, see “Turning Off the Hardware Management Console” in the
Hardware Management Console Operations Guide.

Managing groups of objects

Managing groups enables you to create, delete, add to, and delete from
user-defined groups of objects. You may want to create a group when you want to
perform the same task on several CPC images simultaneously instead of repeating
the task on each individual CPC image. This task also allows you to group one or
more user-defined groups into other groups.

To group images:

Chapter 4. Daily operation of the system 77

 1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer user role (see “Establishing a
support element console session from a Hardware Management Console” on
page 3).
2. Locate the Images that you want to work with.
3. Select one or more objects.
4. Locate and open the Daily task list
5. Locate and open the Grouping task. The Manage Groups window displays to
allow you to add the selected object(s) to an existing group, delete the selected
object(s) from a group, create a new group, create a pattern match group, or
delete the group.

Use the online Help if you need additional information for working with groups.

You may want to group one or more user-defined groups into other groups if you
have many groups in your Groups Work Area and need additional work area space.
However, if you group user-defined groups into other groups, you cannot perform
any task other than Grouping on these groups.

To group groups of user-defined images:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer user role (see “Establishing
a support element console session from a Hardware Management Console” on
page 3).
2. Locate the images that you want to group.
3. Select one or more objects.

78 Support Element Operations Guide

 4. Locate and open the Daily task list
5. Locate and open the Grouping task.
The Manage Groups window displays.
6. Click Create a new group in the Group Action box.
7. Enter a group name in the New group name box.
8. Click OK. A Create a New Group pop-up window displays stating you
successfully created a new group.
9. Click OK. The new group is now displayed in the Group Work Area.
10. Select another group that you want to add to the group you just created above.
11. Locate and start the Grouping task.
The Grouping window displays.
12. Click Add to an existing group in the Group Action box.
13. Select the group name you created in step 9 above from the Group Name
box.
14. Click OK. The Add to an Existing Group pop-up window displays telling you
successfully added a group to another group.
15. Click OK. The group is no longer displayed in the Group Work Area because it
is now part of the group you created in step 9.
16. Repeat steps 12 through 17 for as many groups that you want to add to the
new group.

Chapter 4. Daily operation of the system 79

80 Support Element Operations Guide
Chapter 5. Error recovery
This section describes the tasks from the CPC Recovery task list typically needed
to attempt to recover from hardware or software errors. The recovery tasks, from
least to most disruptive, are:
v Processor operations: stop all and start all
v Resets: normal and clear
v Load
v Power-on reset

If you have experience using other systems, you may find that some recovery tasks
are the same as or similar to tasks you have used not only for error recovery on
similar systems, but also for starting the system under normal circumstances. But
using the support element workplace, you should activate the system instead of
using recovery tasks for starting the system under normal circumstances. Activating
the system, referred to also as system activation, automatically determines its
status and then performs all of the tasks necessary to make it operational. For more
information about activation, see “Starting the system” on page 59.

Use recovery tasks only while following your local procedures for error recovery.

To launch the tasks from the CPC Recovery task list using the classic style user
interface, see Chapter 2, “Using the tree style user interface,” on page 9, or if you
are using the tree style user interface, see Chapter 3, “Using the classic style user
interface,” on page 35.

Processor operations: start all and stop all

Start all and stop all are processor operations you can use, together, to control
whether processors can process instructions. If you have experience using other
systems, you may have used START and STOP commands or Start and Stop keys
to start and stop processors.

On the support element workplace, images are supported by physical processors or

logical processors. An image represents a logical partition, while the CPC is
activated.

By using start and stop on all processors that support an image, you can control the
processing activity of the image, and thereby control the activity of the software
running on the image:
v Stop all processors for an image to suspend its processing activity. This
effectively suspends the activity of the software running on the image.
v Start all previously stopped processors for an image to resume its processing
activity. The activity of the software running on the image also is resumed.

Follow your local error recovery procedures for determining when to stop all
processors, what to do afterwards, and when to start all processors again.

Note: If your local error recovery procedures direct you to work with individual
processors, use tasks in the CP Toolbox task list. See the topics that follow
Chapter 12, “Processor and storage operations,” on page 215, for more
information about tasks for working with individual processors:
v Processor operations: stop and start
v Changing a processor’s operation rate.

© Copyright IBM Corp. 2008 81

 v Using display/alter.
v Performing a PSW restart.
v Setting conditions for stopping a processor.
v Tracing processor activity.
v Interrupting processor activity.
v Using store status.

Stopping all processors

Follow your local error recovery procedures for determining when to stop all
processors. Generally, stopping all processors for an image is effective only when
the image and its processors are operating.

To stop all processors for an image:

1. Log onto the support element on the hardware management console through
Single Object Operations in advanced operator, system programmer, or
service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
2. Locate the Image you want to work with.

Note: Stopping an image can be considered disruptive. If the CPC image is

locked, unlock it. See “Setting object locking for disruptive tasks on an
object” on page 54.
3. Locate and open the CPC Recovery task list.
4. Locate and open the Stop All task to stop all processors for the image.
This immediately performs the operation; all processors for the image are
stopped.

Starting all processors

Follow your local error recovery procedures for determining when to start all
processors. But generally, starting all processors for an image is most effective after
you’ve used the Stop All task to stop all processors for the image.

To start all processors for an image:

1. Log onto the support element on the hardware management console through
Single Object Operations in advanced operator, system programmer, or
service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
2. Locate the Image you want to work with.

Note: Starting an image can be considered disruptive. If the CPC image is

locked, unlock it. See “Setting object locking for disruptive tasks on an
object” on page 54.
3. Locate and open the CPC Recovery task list.
4. Locate and start the Start All task to start all processors for the image.

82 Support Element Operations Guide

 This immediately performs the operation; all processors for the image are
started and resume operating.

Resets: normal and clear

A reset initializes a system or logical partition by:
v Clearing its pending interruptions.
v Resetting its channel subsystem.
v Resetting its processors.

Such a reset is referred to as a reset normal; if you have experience using other
systems, a reset normal may have been referred to as a system-reset-normal. Like
a reset normal, a reset clear clears interruptions, resets channels, and resets
processors for a system or logical partition, but a reset clear also clears main
storage for the system or logical partition. If you have experience using other
systems, a reset clear may have been referred to as a system-reset-clear.

A reset prepares a system or logical partition for loading it with an operating

system. On the support element workplace, images support operating systems, so
images are your targets for resets. An image represents either:
v A central processor complex (CPC)
v A logical partition (LPAR).

Follow your local error recovery procedures for determining when to perform a reset
normal or reset clear.

Reset normal
To perform a reset normal:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
2. Locate the Image you want to work with.

Note: Performing a reset normal on an image can be considered disruptive. If

the CPC image is locked, unlock it. See “Setting object locking for
disruptive tasks on an object” on page 54.
3. Locate and open the CPC Recovery task list.
4. Locate and open the Reset Normal task.
5. Review the information on the confirmation window to verify the image you will
reset.
6. If the information is correct, Click Yes to perform the reset normal.
The progress window indicates the progress of the reset, and the outcome.
7. Click OK to close the window when the reset completes successfully.
If the reset does not complete successfully, follow the directions on the window,
or on any messages that may display, to determine the problem and how to
correct it.

Chapter 5. Error recovery 83

Reset clear
To perform a reset clear:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the Image you want to work with.

Note: Performing a reset clear on an image can be considered disruptive. If the

CPC image is locked, unlock it. See “Setting object locking for disruptive
tasks on an object” on page 54.
3. Locate and open the CPC Recovery task list.
4. Locate and open the Reset Clear task.
5. Review the information on the confirmation window to verify the image you will
reset.
6. If the information is correct, Click Yes to perform the reset clear.
The progress window indicates the progress of the reset, and the outcome.
7. Click OK to close the window when the reset completes successfully.
If the reset does not complete successfully, follow the directions on the window,
or on any messages that may display, to determine the problem and how to
correct it.

Load
A load resets a system or logical partition, to prepare it for loading an operating
system, and then loads the operating system. If you have experience using other
systems, a load may have been referred to as an initial program load or IPL.You
can have up to four Load types: Normal, Clear, SCSI, and SCSI dump.

For daily or routine loading of images, it is recommended that you customize

activation profiles to specify how you want to load images, and then use a profile
with the Activate task to perform all the operations necessary to make an image
operational, including loading it with a control program.

Load (except for a coupling facility image) causes a program to be read from a
designated device and initiates the execution of that program. On the support
element workplace, images support operating systems, so images are your targets
for loads. An image represents a logical partition, while the CPC is activated.

Follow your local error recovery procedures for determining when to perform a load.

To perform a load:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).

84 Support Element Operations Guide

 2. Locate the Image you want to work with.

Note: Loading an image is considered disruptive. If the CPC image is locked,

unlock it. See “Setting object locking for disruptive tasks on an object” on
page 54.
3. Locate and open the CPC Recovery task list.
4. Locate and open the Load task.
5. On the Load window:
a. Use the controls to identify the operating system you want to load, and to
indicate how you want to perform the load.
b. Click OK to perform the load using the information you provided.
The Load Task Confirmation window is displayed.
6. Review the information on the confirmation window to verify the image you will
load and the information you provided for performing the load. If the information
is correct, click Yes to perform the load.
The progress window indicates the progress of the load, and the outcome.
7. Click OK to close the window when the load completes successfully.
If the load does not complete successfully, follow the directions on the window,
or on any messages that may display, to determine the problem and how to
correct it.

Power-on reset
A power-on reset initializes a system by:
v Initializing all processors.
v Initializing the channel subsystem.
v Allocating storage.
v Loading the hardware system area (HSA) with licensed internal code.
v Establishing logically partitioned (LPAR) mode.
v Defining the input/output (I/O) configuration to the channel subsystem.

If you have experience using other systems, a power-on reset may have been
referred to as an initial microcode load or IML.

On the support element workplace, the central processor complex (CPC) is the
system, so the CPC is your target for a power-on reset.

Follow your local error recovery procedures for determining when to perform a
power-on reset.

To perform a power-on reset:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. You must have an input/output configuration data set (IOCDS) available on your
support element which defines the I/O configuration for the CPC.
3. Locate the CPC to work with.

Chapter 5. Error recovery 85

 Note: Performing a power-on reset to a CPC is considered disruptive. If the
CPC is locked, unlock it. See “Setting object locking for disruptive tasks
on an object” on page 54.
4. Locate and open the CPC Recovery task list.
5. Locate and open the Power-on reset task.
The Power-On reset notebook pages provide controls for customizing the
information used to perform a power-on reset of the CPC.
6. Use the controls on each page to customize the power-on reset information as
needed:
a. Use the General page to select an operating mode and IOCDS for the CPC.
b. Use the Dynamic page to establish the hardware support required to use
dynamic input/output (I/O) configuration.
c. Use the Options page to set the operating environment and enable or
disable the global input/output (I/O) priority queuing for the CPC.
d. Use the CP/SAP page to select a CP/SAP configuration to optimize the
performance of the CPC.
7. Select Perform power-on reset to perform the power-on reset using the
information you provided in the window.
8. Click Power-on reset to perform the power-on reset.
The progress window indicates the progress of the power-on reset, and the
outcome.
9. Click OK to close the window when the power-on reset completes successfully.
If the power-on reset does not complete successfully, follow the directions on
the window, or on any messages that may display, to determine the problem
and how to correct it.

Use the online Help for more information on performing a power-on reset.

Installing software from a CD-ROM, DVD or FTP server

This task allows you to install system software or utility programs from a
CD-ROM/DVD or from an FTP server. You can specify only one software source.

Note: The installation of some software, such as certain levels of z/VM, requires
you to not remove the CD-ROM, DVD from the Hardware Management
Console’s drive until directed. Refer to the installation instructions that come
with your software for more information.

To install software from a CD-ROM/DVD or FTP server:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative
user role (see “Establishing a support element console session from a
Hardware Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the CPC Recovery task list.
4. Locate and open the Load from CD-ROM, DVD, or Server task.
The Load from CD-ROM, DVD, or Server Task Confirmation window displays.
5. Click Yes to continue.

86 Support Element Operations Guide

 The Load from CD-ROM, DVD, or Server window displays.
6. Select the source of the software that you want to load from.
If you select the FTP Source, you must enter the FTP Host computer, your
User ID, and your password.
7. Click Continue
The Load from CD-ROM, DVD, or Server - Select the software to load window
displays.
8. Select the file or program that you want to load.
9. Click Continue to complete the task.
The progress window indicates the duration and elapsed time of the program
loaded.
10. Click OK to close the window when the task completes successfully.

Chapter 5. Error recovery 87

88 Support Element Operations Guide
Chapter 6. Settings for system operations
This section describes the tasks from the CPC Operational Customization task list
you can use to customize settings that control how the system operates. Some
settings affect system operations directly, while other settings are input for other
tasks you use to monitor and operate the system.

To launch the tasks from the CPC Operational Customization task list using the
classic style user interface, see Chapter 2, “Using the tree style user interface,” on
page 9, or if you are using the tree style user interface, see Chapter 3, “Using the
classic style user interface,” on page 35.

Getting ready to operate the system: customizing activation profiles

Customize activation profiles to define the information that sets the operational
capabilities and characteristics of the objects you want to activate. There are four
types of activation profiles:

v A reset profile is used to activate a central processor complex (CPC) and its
images.
v An image profile is used to activate an image of a CPC previously activated.
v A load profile is used to load a previously activated image with a control program
or operating system.
v A group profile is used to define the group capacity value for all logical partitions
belonging to that group.

© Copyright IBM Corp. 2008 89

Default activation profiles
A set of default activation profiles is provided by IBM with the Support Element
Console Application. There is one default profile of each type:
Type Default profile name
Reset DEFAULT
Image DEFAULT
Load DEFAULTLOAD
Group DEFAULT

The default profiles are not meant to be used to activate your central processor
complex (CPC) or its images; the information in them may not be correct for your
configuration or needs. Instead, customize the default profiles to meet your needs.
Or customize the default profiles to meet your general needs, then use them as
templates for creating new profiles that meet your specific needs.

Using the right profiles

You can perform a complete activation of a central processor complex (CPC) and
its images by using a properly customized reset profile:
v When a reset profile is customized for activating the CPC, the reset profile
includes the image profiles necessary to activate and load the images. That is,
you can customize reset and image profiles at once for performing a complete
activation of the CPC and its images:
– Customize the reset profile for activation.
– Customize the image profiles included in it for activating and loading one or
more images during CPC activation.

In summary:
v You must customize reset profiles for activating the CPC.
v Then while you are customizing a reset profile, you have the option of
customizing the image profiles included in it.
v To use a reset profile to perform a complete activation of the CPC and its
images, you must properly customize image profiles included in it.

Other options for using profiles

You can customize load profiles and image profiles. After you use a reset profile to
activate the central processor complex (CPC), you can use individual load profiles
or image profiles as follows:
v You can use an image profile to activate a logical partition.
Activating the logical partition with its image profile, rather than activating the
CPC again with a reset profile, allows activating only the logical partition, while
maintaining current operational capabilities and characteristics of the CPC and
other logical partitions. You can activate an image this way whether you are
activating it for the first time, or activating it again.
v You can use a load profile to load its image with an operating system.
Activating the image with a load profile, rather than activating the logical partition
again with an image profile, allows loading the image, while maintaining the rest
of the logical partition’s current operational capabilities and characteristics. You
can load an image this way regardless of whether you are loading it for the first
time, or loading it again but with a different operating system.

90 Support Element Operations Guide

 Customizing unique profiles
Customize unique activation profiles for each different way you want to activate the
central processor complex (CPC) and its images. You can customize unique
activation profiles by giving them unique names. That is, all reset profiles, load
profiles, and image profiles you create must have unique names.

Recall that a reset profile includes one or more image profiles. A reset profile
includes an image profile by referencing its unique profile name. While you are
customizing a reset profile, you have the option of customizing the image profiles
included in it. You can also customize load profiles and image profiles individually.
Regardless of whether you customize them within reset profiles or individually, load
profiles and image profiles remain unique.
v Example 1: a reset profile named LPARMODE includes image profiles named
LP01 and LP02.
While customizing the LP01 image profile individually, any changes you make
also affects the LPARMODE reset profile. While customizing the LP01 image
profile included in the LPARMODE reset profile, any changes you make also
changes the individual LP01 image profile.
While customizing the LP02 image profile individually any changes you make
also affects the LPARMODE reset profile. While customizing the LP02 image
profile included in the LPARMODE reset profile, any changes you make also
changes the individual LP02 image profile.

Developing an activation strategy

Until you become familiar with the different types of activation profiles and their
purposes, you should concentrate on customizing reset profiles, and the image
profiles included in them, for performing a complete activation of the central
processor complex (CPC) and its images. After you become more familiar with
activation profiles, developing an activation strategy may help you determine the
types of activation profiles you should customize and use to meet your needs.

To fully exploit the advantages of using activation to start your CPC, IBM
recommends customizing activation profiles for activating the CPC and its images
completely and in a single step. IBM recommends this strategy for establishing the
CPC’s normal, day-to-day operational capabilities and characteristics because it
saves time and requires minimal action by the operator.

Complete activation
A complete activation activates the central processor complex (CPC) and its images
completely and in a single step. The result of a complete activation is an
operational CPC with images loaded and running operating systems.

A properly customized reset profile includes the image profiles necessary to perform
a complete activation of the CPC and its images. Using a properly customized reset
profile for performing a complete activation is the recommended activation strategy
for establishing the CPC’s normal, day-to-day operational capabilities and
characteristics.

Information and instructions for customizing reset profiles are provided in the topics
that follow “Profiles for complete activation” on page 92.

Staged activation
A staged activation activates the central processor complex (CPC) and its images in
steps:

Chapter 6. Settings for system operations 91

 v An initial activation of the CPC and one or more images.
v And any number of subsequent, selective activations of images.

Staged activations are useful for changing the operational capabilities and
characteristics of the CPC’s images, but without performing a complete activation of
the CPC. They allow meeting different processing needs at different times of day or
on different days of the week. For example, you may want to use one logical
partition as a production system during first shift, and use other logical partitions as
batch and test systems on second shift.

You could perform a complete activation of the CPC each time you want to change
the operational capabilities and characteristics of its images. You can get the same
results by planning and performing staged activations instead. Staged activations
will not require performing a complete activation of the CPC each time you want to
change its operational capabilities and characteristics of its images. Instead, you
can activate the CPC once, and then activate only its images when you want to
change their operational capabilities and characteristics.

A reset profile is required for performing the initial activation of a staged activation.
Afterwards, you can use image profiles to selectively activate logical partitions, and
load profiles to selectively load images.

Information and instructions for customizing reset profiles, image profiles, and load
profiles are provided in the topics that follow “Profiles for staged activations” on
page 122.

Profiles for complete activation

You can perform a complete activation of a central processor complex (CPC) and
its images by using a reset profile.

A complete activation means customizing a reset profile to activate the CPC, then
load them with operating systems.
v See “Activating CPCs” on page 95, “Activating logical partitions” on page 104,
and “Loading operating systems” on page 117.

Reset profiles
Customize a reset profile for activating a central processor complex (CPC) and its
images.

Opening a reset profile: You can use the support element workplace to start the
task for customizing reset profiles for a central processor complex (CPC). Starting a
task is referred to also as opening a reset profile.

To open a reset profile:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer user role (see “Establishing a
support element console session from a Hardware Management Console” on
page 3). A reset profile must be assigned as the CPC’s activation profile.
2. Locate the CPC you want to work with.
3. Locate and open the Customize/Delete Activation Profiles task to start it.

92 Support Element Operations Guide

 When the profile list of profiles is initially displayed, the highlighted profile is the
currently assigned profile.
4. Select from the list the name of the reset profile you want to customize.
5. Click Customize to open the selected reset profile.
After you start the task, use the online Help for more information about the
control.

Checking the CPC’s assigned activation profile: You can assign a central
processor complex (CPC) as its activation profile. Whenever the CPC is activated, it
is activated according to the information in its assigned activation profile.

To check and change a CPC’s activation profile:

1. Locate the CPC to work with.
2. Open a CPC details window of information about the CPC
3. Click Change options.

4. Locate the Profile name field from the Change Object Options window.
It displays the name of the profile currently assigned as the CPC’s activation
profile.
5. Locate the same name in the Profile name column in the list of profiles below
the field. Then check the profile’s type in the Type column.

Note: The list includes all the reset profiles and load profiles that can be
assigned to the CPC.
6. If the assigned profile’s type is Reset, then no further action is required.
7. Otherwise, the assigned profile’s type is Load. If you want to assign the CPC a
reset profile, use the window to select and save a reset profile.
To assign the CPC a reset profile instead, use the window to select and save a
reset profile.

Navigating a reset profile notebook: A reset profile includes information for

activating a central processor complex (CPC) and its images.

Opening a reset profile displays its information on the windows that are organized
as pages in a notebook.

Chapter 6. Settings for system operations 93

 The pages are identified in a profile tree view on the left side of the window with a
description label. If the reset profile activates the CPC with multiple images, the
profile tree view list the names of each image section with the identifying name. The
information in each section is used to activate a single object either the CPC or a
logical partition.

To use the profile tree view to open each page on the window:
v Click on the description label for each page within a section of the profile you
want to open.
v Click on the ’+’ for each image to get a list of pages in the section of the profile.
v To save the changes made, click Save.
v To close the window, click Cancel.

Creating a new reset profile: You are responsible for creating reset profiles that
meet your unique needs.

You can use the default reset profile as a template for creating new profiles. After
you create a new profile, you can customize it as needed. After you create and
customize your own reset profiles, you can use them as templates for creating more
new profiles.

To create a new reset profile:

1. Open a reset profile.
For more information, see “Opening a reset profile” on page 92.
2. Select the General page.
The Profile name field identifies the reset profile you opened. It will be used as
a template for the new reset profile.
3. To use a different reset profile as a template:
4. Select the list button beside the Profile name field.

94 Support Element Operations Guide

 This opens a list of the names of all the CPC’s reset profiles. The reset profile
named DEFAULT is the default reset profile provided by IBM.
5. Select from the list the name of the reset profile you want to use as a template.
This opens the selected reset profile. Its information replaces the previous
profile’s information on the pages of the window.
6. Enter a unique name for the new profile in the Profile name field.
7. To save the profile with the new name, click Save.

Note: Saving the new profile does not change the reset profile you used as a
template.

Assigning a reset profile: After you open a reset profile, you can assign it to the
central processor complex (CPC) as its activation profile. Whenever the CPC is
activated, it is activated according to the information in its assigned activation
profile.

To assign an open reset profile as a CPC’s activation profile:

1. After opening and customizing a reset profile, select the General page.
The Profile name field identifies the reset profile that will be assigned to the
CPC.
2. To assign the reset profile as the CPC’s activation profile, click Assign profile.

Saving a reset profile: You must save a reset profile to save the information you
customized on its pages.

To save an open reset profile:

1. After opening and customizing a reset profile, select the General page.
The Profile name field identifies the reset profile that will be saved.
2. To save the reset profile and close it, click Save.

Activating CPCs
The topics in this section provide tips for customizing a reset profile for activating a
central processor complex (CPC).

Supporting LPAR mode operation: The reset profile you use to activate a
central processor complex (CPC) can establish the support required to operate the
CPC. The reset profile must identify:
v An input/output configuration data set (IOCDS) that supports LPAR mode and the
logical partitions you want to activate.
v LPAR mode as the operating mode you want to establish.

An IOCDS is used during a power-on reset to define your input/output (I/O)

configuration to the channel subsystem of the CPC. The I/O configuration is the set
of all I/O devices, control units, and channel paths available to the CPC. Performing
a power-on reset also establishes the operating mode of the CPC.

To customize a reset profile to support operating the CPC:

1. Open a reset profile.
For more information, see “Opening a reset profile” on page 92.
2. Select the General page.
3. Select from the Input/Output Configuration Data Set list an IOCDS that
defines the logical partitions you want to activate.

Chapter 6. Settings for system operations 95

 Notes:
a. The Type column indicates the operating mode supported by each IOCDS.
The column displays Partition to indicate an IOCDS supports LPAR mode.
b. The Partitions column displays the names of logical partitions supported by
the IOCDS.
4. Select Logically partitioned from the Mode list as the operating mode you
want to establish.

Use the online Help for more information.

Selecting an IOCDS: The reset profile you use to activate a central processor
complex (CPC) can identify the input/output configuration data set (IOCDS) you
want to use. The IOCDS must be compatible with the operating mode you want to
establish. That is, the IOCDS you select must support the type of operating mode
you select.

An IOCDS is used during a power-on reset to define your input/output (I/O)

configuration to the channel subsystem of the CPC. The I/O configuration is the set
of all I/O devices, control units, and channel paths available to the CPC. Performing
a power-on reset also establishes the operating mode of the CPC.

You can use the Image Profile Configuration window to set up initial parameters
when you selected an IOCDS that contains two or more images that were defined
in the IOCDS, but currently do not exist in the list of image profiles. The Image
Profile Configuration window allows you to automatically assign unique logical
partition identifiers to each new image profile and enter a profile description to the
new image profiles. You can select an existing image profile and have the existing
profile’s data copied to all new image profiles that are to be created.

You can customize the reset profile to use either a specific IOCDS or the active
IOCDS (if you intend to use dynamic I/O configuration, for example). Follow the
instructions below for using a specific IOCDS; see “Using the active IOCDS” on
page 97 for more information about using the active IOCDS.

To customize a reset profile to select an IOCDS and operating mode:

1. Open a reset profile.
For more information, see “Opening a reset profile” on page 92.

96 Support Element Operations Guide

2. Select the General page.
Use the online Help for more information.
3. Select an IOCDS from the Input/Output Configuration Data Set list.
4. Select an operating mode from the Mode list that is compatible with the IOCDS
you selected.
Note the type of operating mode supported by the IOCDS you selected. The
Type list column indicates the operating mode supported by each IOCDS:
IOCDS type Operating mode
Partition Logically partitioned
Currently ID The operating mode of the IOCDS is not known because the
reset profile will use the active IOCDS when activation is
performed; the ID identifies the current active IOCDS. Select an
operating mode from the Mode list that is compatible with the
IOCDS you intend to make active. For more information, see
“Using the active IOCDS.”

Using the active IOCDS: The reset profile you use to activate a central processor
complex (CPC) can be customized for using the active IOCDS rather than a specific
IOCDS. The active IOCDS is the IOCDS used for the most recent power-on reset. If
you use dynamic I/O configuration, you can change the active IOCDS at any time
without performing a power-on reset.

You should customize a reset profile to use the active IOCDS if you intend to use
dynamic input/output (I/O) configuration. At least one of the images activated on the
CPC must be loaded with an operating system that supports an application or
facility for using dynamic I/O configuration. Dynamic I/O configuration is supported
by:
v The Hardware Configuration Definition (HCD) application on some z/OS® and
OS/390® operating systems.
v The dynamic I/O configuration facility of some z/VM and VM operating systems.

To customize an activation profile to use the active IOCDS:

1. Open a reset profile.
For more information, see “Opening a reset profile” on page 92.
2. Select the General page.
3. Select Use active IOCDS from the Input/Output Configuration Data Set list.
When activation is performed using this reset profile:
v The last active IOCDS is used if the CPC is not operational.
v The active IOCDS is used if the CPC is already operational and if a power-on
reset must be performed to make at least one other profile setting take effect.
For more information, see “How using the active IOCDS affects CPC
activation” on page 98.
4. Note the identifier of the IOCDS that is currently active. See Currently ID
displayed in the Type list column for the Use active IOCDS selection. The ID is
the IOCDS identifier.
With dynamic I/O configuration, you can change the active IOCDS anytime prior
to using this reset profile to activate the CPC.
5. Select an operating mode from the Mode list that is compatible with the IOCDS
you’ve made active or intend to make active.

Chapter 6. Settings for system operations 97

 To determine the type of operating mode supported by the IOCDS, locate it in
the Input/Output Configuration Data Set list. The Type list column indicates
the operating mode supported by the IOCDS.
IOCDS type Operating mode
Partition Logically partitioned

How using the active IOCDS affects CPC activation: When a reset profile is used
to activate the central processor complex (CPC), several profile settings take effect
when a power-on reset is performed during activation. Such settings are referred to
here as power-on reset settings and include, for example, the CPC’s storage
allocations. If the CPC is already operational and the reset profile’s power-on reset
settings are already in effect when activation is performed using the profile, then a
power-on reset is not performed during activation. That is, a power-on reset is
performed during CPC activation only if it is necessary to make one or more of the
reset profile’s power-on reset settings take effect.

The input/output configuration data set (IOCDS) setting is one of the reset profile’s
power-on reset settings, unless it is set to Use active IOCDS. Activating the CPC
with a reset profile customized for using the active IOCDS affects CPC activation as
follows:
v If the CPC is not operational, then a power-on reset is performed and the last
active IOCDS is used.
v If the CPC is already operational, then:
– A power-on reset is performed and the active IOCDS is used only if one or
more of the reset profile’s other power-on reset settings are not already in
effect. For example, a power-on reset is performed if the CPC’s global
input/output (I/O) priority queuing flag is not the same as the global I/O priority
queuing flag set in the reset profile.
– A power-on reset is not performed and the active IOCDS is ignored if all of
the reset profile’s other power-on reset settings are already in effect.
This may be the case when you use dynamic input/output (I/O) configuration.
Using dynamic I/O to change the active IOCDS will not affect whether a
power-on reset is performed during CPC activation. Only changing the reset
profile’s other power-on reset settings will cause a power-on reset to be
performed.

Delaying the load while devices power-on: The reset profile you use to activate
a central processor complex (CPC) can set a load delay for power sequencing.

Activating a CPC includes initializing its images and can include loading the images.
The operating systems are loaded from devices in the input/output (I/O)
configuration of the CPC.

If the devices are attached to control units that are powered-on by the CPC during
activation, operating systems cannot be loaded from the devices until powering-on
their control units is complete.

If you know or can estimate the amount of time it takes for control units to be
powered-on, you can delay starting the load for that amount of time, up to 100
minutes. The delay may allow the powering-on to complete before the load begins.

To customize a reset profile to delay the load while control units power-on:
1. Open a reset profile.

98 Support Element Operations Guide

 For more information, see “Opening a reset profile” on page 92.
2. Select the General page.
3. Enter the amount of time to delay the load, from 0 to 59 seconds or 1 to 100
minutes, in the Load delay for power sequencing fields.

Use the online Help for more information.

Supporting dynamic I/O configuration: The reset profile you use to activate a
central processor complex (CPC) can establish the hardware support required to
use dynamic input/output (I/O) configuration.

Your I/O configuration is the set of all I/O devices, control units, and channel paths
you define to your hardware and software.

Performing a power-on reset establishes the hardware I/O definition. That is, it
defines the I/O configuration to the hardware. Loading the software establishes the
software I/O definition. That is, it defines the I/O configuration to the software.

Changing the hardware I/O definition requires performing another power-on reset,
and changing the software I/O definition requires loading the software again. If the
hardware and software support dynamic I/O configuration, you can dynamically
change their I/O definitions. Changes made dynamically, referred to as dynamic I/O
changes, take effect immediately. Yet they do not require a power-on reset or load
to make them take effect.

Hardware support for dynamic I/O: Your hardware is the CPC. Dynamic I/O
configuration, or simply dynamic I/O, is a facility of the CPC’s licensed internal
code. The hardware support required for using dynamic I/O can be established
during power-on reset of the CPC:
v The IOCDS used during power-on reset must support dynamic I/O. The IOCDS
must be either:
– Built using the Hardware Configuration Definition (HCD) application of an
z/OS and OS/390 or other operating system that supports dynamic I/O.
– Written using the DYN option of the input/output configuration program (IOCP)
utility of a z/VM and VM operating system that supports dynamic I/O.
v Dynamic I/O must be enabled for the CPC. That is, the CPC must allow
dynamically changing its I/O definition.

Note: Only a power-on reset of the CPC, performed directly or during CPC
activation, can initially enable dynamic I/O. Afterwards, you can use the
support element workplace at any time, if necessary, to change the
dynamic I/O setting. For more information, see “Enabling or disabling
dynamic I/O without performing a power-on reset” on page 100.
v Dynamic I/O must be enabled for a logical partition.

To customize a reset profile for hardware support of dynamic I/O:

1. Open a reset profile.
For more information, see “Opening a reset profile” on page 92.
2. Select the General page.
3. Select an IOCDS that supports dynamic I/O from the Input/Output
Configuration Data Set list.

Chapter 6. Settings for system operations 99

 Note: The Allow Dynamic I/O column displays Yes to indicate an IOCDS
supports dynamic I/O.
4. Select the Dynamic page.
5. Mark the Allow dynamic changes to the channel subsystem input/output
(I/O) definition check box.
The check box displays a check mark when you mark it. The check mark
indicates you want to enable dynamic I/O for the CPC.

Use the online Help for more information on Dynamic I/O.

Enabling or disabling dynamic I/O without performing a power-on reset: Performing

a power-on reset of the central processor complex (CPC), either directly or by
activating the CPC, establishes many of its initial operational capabilities and
characteristics, including whether dynamic input/output (I/O) configuration is enabled
or disabled. After a power-on reset of the CPC is performed, changing its
operational capabilities and characteristics requires performing another power-on
reset.

If a power-on reset of the CPC initially enables dynamic I/O configuration, a task
becomes available on the support element workplace for changing the CPC’s
dynamic I/O setting without performing another power-on reset.

To change the CPC’s dynamic I/O setting without performing a power-on reset:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3). The most recent CPC power-on reset must
have enabled dynamic I/O.
2. Locate the CPC to work with.
3. Locate and open the Enable/Disable Dynamic Channel Subsystem task to
start it.
The Customize Dynamic Channel Subsystem window displays.
4. Use the window’s controls, as follows, to enable or disable dynamic I/O for the
CPC:
a. Review the CPC’s current setting for dynamic I/O. The selected Enabled or
Disabled, indicates the current setting.
b. While dynamic I/O is enabled, select Disabled to change the setting to
disabled.
c. Or while dynamic I/O is disabled, select Enabled to change the setting to
enabled.
d. Click OK to save the setting and close the window.
Use the online Help for more information on using the window to change the
CPC’s dynamic I/O setting.

Optimizing the performance of an application: You can optimize the

performance of an application by selecting a CP/SAP configuration for the central
processor complex (CPC) that best suits the instruction processing requirements.

100 Support Element Operations Guide

The physical processor units installed in the CPC are used either as central
processors (CPs) or system assist processors (SAPs). The model of your machine
determines its default configuration of CPs and SAPs. The SAPs, if any, are used
exclusively for input/output (I/O) instruction processing.

If other CP/SAP configurations are available, selecting a configuration that

configures one or more CPs as additional SAPs may improve the performance of
some types of applications (applications that have greater needs for I/O instruction
processing, for example). Selecting a non-default CP/SAP configuration may affect
how the CPC can be activated.

Effects of changing the CP/SAP configuration: If you intend to activate a CPC, a

reduction in the number of available CPs will reduce the number of logical
processors you can assign to logical partitions. Activation of a logical partition will
fail if the number of logical processors you attempt to assign exceeds the number of
CPs available.

To avoid a logical partition activation failure, verify the number of logical processors
assigned to a logical partition by its activation profile does not exceed the number
of CPs available. For more information about customizing an activation profile to
assign logical processors to a logical partition, see “Assigning initial logical or
reserved processors” on page 110.

Planning for a fenced book: The reset profile you use to activate a central
processor complex (CPC) can determine how the available system processors
would be assigned when a hardware problem occurs with one of the system books
that cause the book to be fenced or become unavailable for use.

Note: To display this Fenced page, select Display fenced book page on the
CP/SAP page.

Chapter 6. Settings for system operations 101

 To customize a reset profile to let the system determine the processor assignment:
1. Open a reset profile.
For more information, see “Opening a reset profile” on page 92.
2. Select the Fenced page.
3. Locate the Processor Assignment group box.
4. Select the Determined by the system radio button.

To customize a reset profile to set a processor assignment by the user:

1. Open a reset profile.
For more information, see “Opening a reset profile” on page 92.
2. Select the Fenced page.
3. Select the Determined by user radio button.
4. Locate the Processor Assignment group box.
5. Select the radio button to either:
v Display processor assignment when a 17 processors book is fenced.
v Display processor assignment when a 20 processors book is fenced.
6. Type the values in the Value Used when Book is Fenced field.

Use the online Help for more information about using it.

Enabling or disabling the global input/output (I/O) priority queuing: The reset
profile you use to activate a CPC can enable or disable the global input/output (I/O)
priority queuing.

To customize a reset profile for enabling or disabling global input/output (I/O) priority
queuing:
1. Open a reset profile.

102 Support Element Operations Guide

 For more information, see “Opening a reset profile” on page 92.
2. Select the Options page.
3. Locate the Enable global input/output (I/O) priority queuing check box. Then
either:
v Mark the check box to enable global input/output priority queuing. The check
box displays a check mark when you mark it.
v Or unmark the check box to disable global input/output priority queuing. The
check box becomes empty when you unmark it.

Use the online Help for more information about using it.

Releasing I/O reserves under error conditions: The reset profile you use to
activate a central processor complex (CPC) can enable automatically resetting the
input/output (I/O) interface under particular error conditions.

In a multiple CPC environment, several objects, which can be CPCs or logical

partitions, may share the control units, channel paths, and I/O devices included in
their I/O definitions.

The following error conditions may cause shared control units to hold reserves on
their devices:
v A machine check places the CPC in a check-stopped state.
v Or the control program places an image of the CPC or a logical partition in a
non-restartable wait state.

The reserves are held for the CPC or logical partition affected by the error
condition. Holding reserves provides the affected object with exclusive use of
devices, preventing them from being used by other objects that share the control
units.

To release reserves held by shared control units assigned to an object, you must
reset the I/O interface. Although resetting the I/O interface will not recover the
object from its error condition, it will make the devices attached to shared control
units available to other objects.

To customize a reset profile to enable automatically resetting the I/O interface:

1. Open a reset profile.
For more information, see “Opening a reset profile” on page 92.
2. Select the Options page.
3. Mark the Automatic input/output (I/O) interface reset check box.
The check box displays a check mark when you mark it. The check mark
indicates you want to enable resetting the I/O interface automatically.

Use the online Help for more information.

Setting processor running time: The reset profile you use to activate a central
processor complex (CPC) can set whether you or the CPC determines the
processor running time.

When the CPC is activated, the logical processors of logical partitions activated
without dedicated processor resources share the remaining processor resources.

Chapter 6. Settings for system operations 103

 Each logical processor is given the same processor running time. Processor
running time is the amount of continuous time allowed for a logical processor to
perform jobs using shared processor resources. Processor running time is referred
to also as a timeslice.

The processor running time can be dynamically determined by the CPC. That is,
the CPC can automatically recalculate the running time whenever the number of
active logical processors changes.

You can set the running time to a constant amount. To get optimal use of shared
processor resources, IBM recommends letting the CPC dynamically determine the
running time.

To customize a reset profile to let the CPC dynamically determine processor

running time:
1. Open a reset profile.
For more information, see “Opening a reset profile” on page 92.
2. Select the Options page.
3. Locate the Processor running time group box.
4. Select the Dynamically determined by the system radio button.

To customize a reset profile to set a constant processor running time:

1. Open a reset profile.
For more information, see “Opening a reset profile” on page 92.
2. Select the Options page.
3. Locate the Processor running time group box.
4. Select the Determined by the user radio button.
5. Type the constant running time, from 1 to 100 milliseconds, in the Running
time field.

Note: After activating the CPC, you can use the support element workplace to
dynamically change its settings for processor running time. See “Logical
partition controls” on page 167 for more information.

Activating logical partitions

The topics in this section provide tips for customizing an activation profile for
activating a logical partition.

The tips are applicable to customizing reset profiles and image profiles unless
indicated otherwise.

Activating logical partitions during CPC activation: The reset profile you use to
activate a central processor complex (CPC) can also activate one or more logical
partitions.

To customize a reset profile to activate logical partitions during CPC activation:

1. Open a reset profile.
For more information, see “Opening a reset profile” on page 92.
2. If you have not already done so, customize the reset profile to activate the CPC.
For more information, see “Supporting LPAR mode operation” on page 95.
3. Select the Partitions page.
4. Review the logical partition name in each Partition field.

104 Support Element Operations Guide

 The fields are initialized with the names of logical partitions defined in the
input/output configuration data set (IOCDS) selected on the General page of the
reset profile.
5. Review the numbers in the Order fields beside the logical partition names.
The fields are initialized with the default activation order of the logical partitions.
The logical partition with an order of 1 will be activated first, the logical partition
with an order of 2 will be activated second, and so on.
6. Optionally, enter a new order number in the Order field of a logical partition to
change its activation order.

Note: If you intend to operate one of the logical partitions in coupling facility
mode, it should be activated first. That is, you should change the
activation order of a coupling facility logical partition to 1.
7. Optionally, delete the order number of a logical partition to not activate it during
activation of the CPC.

Note: The names of logical partitions that are not activated will not be saved in
the profile. That is, if you delete the order number of a logical partition,
its name will be discarded.

The information used to activate a logical partition, though it is included in a reset

profile, is actually the logical partition’s image profile.

The name of an image profile is the same as the name of the logical partition it
activates. So each logical partition has only one image profile.

Since each reset profile that activates a logical partition includes the logical
partition’s only image profile, changing the logical partition’s information in any
activation profile changes the same information in all the other profiles as well. That
is, if you customize a reset profile for activating a logical partition, for example,
changing the reset profile also changes the logical partition’s information in its
image profile and in every other reset profile that activates the same logical
partition.

Assigning a logical partition identifier: The activation profile you use to activate
a logical partition must assign it a unique logical partition identifier.

The logical partition identifier becomes part of the central processor identifier of
each logical processor assigned to the logical partition. The central processor
identifier is used by subsystems and control programs to distinguish between logical
processors.

To customize an activation profile to assign a logical partition identifier:

1. Open a reset profile or open an image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree on the left side of the window.
3. Select the General page.
4. In the Partition identifier field, type the hexadecimal digit to assign as the
logical partition identifier.
Notes:
a. The partition identifier can be from X'0' to X'3F'.

Chapter 6. Settings for system operations 105

 b. The partition identifier must be unique among the identifiers of other logical
partitions activated at the same time. If necessary, verify the partition
identifier assigned to this image is unique by checking the Partition
identifier fields on the General pages of the other logical partitions you
intend to activate.

Selecting an operating mode: The activation profile you use to activate a logical
partition must identify the operating mode you want to establish.

The operating mode describes the architecture that supports the operating system
or control program you intend to load. Coupling facility and Linux Only are
examples of operating modes.

To customize an activation profile to select an operating mode:

1. Open a reset profile or open an image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree from the left side of the window.
3. Select the General page.
4. Select the operating mode you want to establish from the Mode list.

Activating a coupling facility logical partition: The activation profile you use to
activate a logical partition can establish the support required to use it as a coupling
facility.

A coupling facility is a logical partition that supports data sharing among

applications running on other systems or logical partitions. A logical partition
operating as a coupling facility is referred to here as a coupling facility logical
partition.

To customize an activation profile to support and activate a coupling facility logical

partition:
1. Open a reset profile or an image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile:
a. To activate the coupling facility logical partition during central processor
complex (CPC) activation, customize the reset profile to activate the
coupling facility logical partition first.
For more information, see “Activating logical partitions during CPC
activation” on page 104.
b. To customize the information used to activate the coupling facility logical
partition, select the name of the logical partition from the profile tree on the
left side of the window.
3. Select the General page.
4. Select Coupling facility from the Mode list.
5. Customize the activation profile to allocate storage to the coupling facility logical
partition.
For more information, see “Allocating central storage (main storage)” on page
116.

106 Support Element Operations Guide

Changing the group profile name for the logical partition: A logical partition
can become a member of a group which allows determining the allocation and
management of processor resources assigned to logical partitions in a group
activated by the profile.

To customize the group profile name assigned to the logical partitions:

1. Open a reset profile or open an image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree on the left side of the window.
3. Select the Processor page.
4. Locate the Group name drop-down box.
5. Select the arrow beside the field to list the names of existing group profiles.
6. Select a new group or create your own group profile name.

Note: If the group profile name is blank, then the logical partition is not
assigned to a group.

Using internal coupling facility processors: If internal coupling facility

processors are installed in the CPC, you can assign a coupling facility logical
partition either central processors, internal coupling facility processors, or dedicated
coupling facility processors and shared central processors.

To customize an activation profile to assign logical processors to a coupling facility

logical partition:
1. Open a reset profile or open an image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree on the left side of the window.
3. Select the General page.
4. If you select Coupling Facility from the Mode list, select the Processor page.
5. Select the type of processors you want assigned to the coupling facility logical
partition:
a. Dedicated internal coupling facility processors
b. Not dedicated internal coupling facility processors
c. Dedicated internal coupling facility processors and not dedicated central
processors.
d. Dedicated and not dedicated internal coupling facility processors.

Note: There are other options for assigning processors to the partition that are
available, but these other options DO NOT use Internal coupling facility.
6. If you select z/VM from the Mode list, select the Processor page.
7. Use the Logical Processor Assignments group box to:
a. Select Central processors, Dedicated processors, and Internal coupling
facility processors if you want to assign dedicated Internal coupling facility
processors to each logical partition.
b. Select Central processors and Internal coupling facility processors to
assign not dedicated Internal coupling facility processors to logical partitions
when the logical partition is activated.

Chapter 6. Settings for system operations 107

 8. Use the controls available to complete the logical partition assignment for the
coupling facility logical partition.

Assign both internal coupling facility processors and not dedicated central
processors to the coupling facility logical partition if you want to enable dynamic
coupling facility expansion.

You can enable dynamic coupling facility dispatching for the coupling facility logical
partition by:
1. Starting the Operating System Messages task on its image.
2. Using the task to send it the coupling facility control code command: DYNDISP
ON

Using integrated facilities for Linux processor: If integrated facilities for Linux
processors are installed in the CPC, you can assign a integrated facilities for Linux
logical partition either central processors or integrated facilities for Linux processors.

To customize an activation profile to assign logical processors to an integrated

facilities for Linux logical partition:
1. Open a reset profile or open an image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree on the left side of the window.
3. Select the General page.
4. If you select LINUX only from the Mode list, select the Processor page.
5. Select the type of processors you want assigned to the integrated facilities for
Linux logical partition:
a. Dedicated integrated facilities for Linux
b. Not dedicated integrated facilities for Linux

Note: There are other options for assigning processors to the partition that are
available, but these other options DO NOT use integrated facilities for
Linux.
6. If you select z/VM from the Mode list, select the Processor page.
7. Use the Logical Processor Assignments group box to:
a. Select Central processors, Dedicated processors, and Integrated
facilities for Linux processors if you want to assign dedicatedIntegrated
facilities for Linux processors to each logical partition.
b. Select Central processors and Integrated facilities for Linux processors
to assign not dedicated Integrated facilities for Linux processors to logical
partitions when the logical partition is activated.
8. Use the controls available to complete the logical partition assignment for the
integrated facilities for Linux logical partition.

Using zSeries application assist processor: If zSeries application assist

processors are installed in the CPC, you can assign a zSeries application assist
processor to a logical partition either central processors or zSeries application assist
processors.

To customize an activation profile to assign logical processors to an zSeries

application assist logical partition:
1. Open a reset profile or open an image profile.

108 Support Element Operations Guide

 For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree on the left side of the window.
3. Select the General page.
4. Select ESA/390 or z/VM from the Mode list.
5. Select the Processor page.
6. Use the Logical Processor Assignments group box to:
a. Select Dedicated processors, Central processors, and zSeries
application assist processors if you want to assign dedicatedzSeries
application assist processors to the logical partition.
b. Select Central processors, zSeries application assist processors to
assign not dedicated zSeries application assist processors to logical
partitions when the logical partition is activated.
7. Use the controls available to complete the logical partition assignment for the
zSeries application assist processors logical partition.

Note: There are other options for assigning processors to the partition that are
available, but these other options DO NOT use zSeries application assist
processors.

Using System z9 integrated information processors: If the System z9

integrated information processors are installed in the CPC, you can assign a
System z9 integrated information logical partition either central processors or
System z9 integrated information processor.

To customize an activation profile to assign logical processors to a System z9

integrated information logical partition:
1. Open a reset profile or open an image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree on the left side of the window.
3. Select the General page.
4. Select ESA/390 or z/VM from the Mode list.
5. Select the Processor page.
6. Use the Logical Processor Assignment group box to:
a. Select Dedicated processors and Central processors, and System z9
integrated information processors if you want to assign dedicatedSystem
z9 integrated information processors to the logical partition.
b. Select Central processors and System z9 integrated information
processors to assign not dedicated System z9 integrated information
processors to logical partitions when the logical partition is activated.
7. Use the controls available to complete the logical partition assignment for the
System z9 integrated information logical partition.

Setting WorkLoad Manager (WLM) controls: The activation profile you use to
activate a logical partition can manage your defined capacity for a logical partition.
See “Setting defined capacity” on page 116 to set defined capacity for logical
partitions. WorkLoad Manager allows you to run all of your work concurrently while
allocating system resources to the most work first. WorkLoad Manager constantly
monitors your system, automatically adjusting the resource allocation as necessary.

Chapter 6. Settings for system operations 109

 Note: To customize Internal coupling facility processors (ICFs), Integrated facilities
for Linux (IFL), zSeries application assist processors (zAAPs), and System
z9 integrated information processors (zIIPs) you must select the processor
type from the Not Dedicated Processor Details section prior to setting the
processing weight values.

To customize an activation profile to allow WorkLoad Manager to manage logical

partitions:
1. Open a reset profile or open an image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree on the left side of the window.
3. Select the General page.
4. Select ESA/390, LINUX Only, or z/VM from the Mode list.
5. Select the Processor page.
6. Unmark the Initial Capping box. If there are more than one processor types
selected in the processor table, you may need to return to the Not Dedicated
Processor Details for each processor type and unmark the Initial Capping box.

Note: You cannot mark the Initial Capping box if the Enable WorkLoad
Manager is enabled. You must unmark it to allow Initial Capping to be
marked.
7. Mark the Enable WorkLoad Manager check box to enable WorkLoad Manager.
A check box displays a check mark when you mark it.
8. Enter the processing weight values for the logical partition that you want to be
managed by WorkLoad Manager.

Assigning initial logical or reserved processors: The activation profile you use
to activate a logical partition can assign it initial logical or reserved processors.

An initial logical processor is the processor resource defined to operate in a logical

partition as a physical central processor. Initial logical processors are the
processors a control program uses to perform jobs for the logical partition.

Reserved processors can be defined at partition activation time, but not used during
partition activation. The reserved processor is not available when the system is
activated, but can become available during concurrent central processor (CP)
upgrade.

To customize an activation profile to assign initial logical processors to a logical

partition:
1. Open a reset profile or open an image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree on the left side of the window.
3. Select the Processor page.
4. Enter the number of initial logical processors to assign to the logical partition or
the number of reserved processors.

110 Support Element Operations Guide

 Note: You cannot specify initial zSeries application assist processors (zAAPs)
prior to installation of zSeries application assist processors.
5. Use the controls in the Logical processor assignment group box to allocate
processor resources to logical partitions.

Note: After activating logical partitions, you can use the support element
workplace to dynamically change its settings for sharing processor
resources. See “Logical partition controls” on page 167 for more
information.

Controlling access to performance data: The activation profile you use to

activate a logical partition can control whether it has global access to performance
data.

A logical partition has access to only its own performance data. A logical partition
with global access also has access to the performance data of all other logical
partitions activated on the same central processor complex (CPC). Performance
data includes central processor usage and input/output processor usage by each
logical partition.

To customize an activation profile to control global access to performance data:

1. Open a reset profile or open an image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile, select the page tab that displays the name of the
logical partition.
3. Select the Security page.
4. Locate the Global performance data control check box. Then either:
v Mark the check box to give the logical partition global access to performance
data. The check box displays a check mark when you mark it.
v Or unmark the check box to give the logical partition access to only its own
performance data. The check box becomes empty when you unmark it.

Note: After activating logical partitions, you can use the support element workplace
to dynamically change their security settings, including global performance
data control. See “Logical partition security” on page 165 for more
information.

Controlling I/O configuration changes: The activation profile you use to activate
a logical partition can control whether it can change the input/output (I/O)
configuration of the central processor complex (CPC) on which it is activated.

Allowing a logical partition to change the I/O configuration enables:

v Reading and writing any input/output configuration data set (IOCDS) of the local
CPC.
v Writing an IOCDS to a remote CPC.
v Using dynamic I/O configuration.
v Using the OSA Support Facility to view OSA configuration for other logical
partitions.

To customize an activation profile to control changing the I/O configuration:

1. Open a reset profile or open an image profile.

Chapter 6. Settings for system operations 111

 For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree view on the left side of the window.
3. Select the Security page.
4. Locate the Input/output (I/O) configuration control check box. Then either:
v Mark the check box to allow using the logical partition to change the I/O
configuration. The check box displays a check mark when you mark it.
v Or unmark the check box to prevent using the logical partition to change the
I/O configuration. The check box becomes empty when you unmark it.

Note: After activating logical partitions, you can use the support element workplace
to dynamically change their security settings, including I/O configuration
control. See “Logical partition security” on page 165 for more information.

Using dynamic I/O configuration: Dynamic input/output (I/O) configuration is

supported by:
v The Hardware Configuration Definition (HCD) application on some z/OS and
OS/390 operating systems.
v The dynamic I/O configuration facility of some z/VM and VM operating systems.

Input/output configuration control must be enabled for the logical partition that you
want to use dynamic I/O configuration. That is, you must mark the Input/output
(I/O) configuration control check box on the Security page of the activation profile
used to activate the logical partition.

Authorizing control of other logical partitions: The activation profile you use to
activate a logical partition can control whether it can be used to issue a subset of
control program instructions to other logical partitions activated on the same central
processor complex (CPC).

Allowing a logical partition to issue instructions to other logical partitions enables:

v Using it to reset or deactivate another logical partition.
v Using the automatic reconfiguration facility (ARF) to backup another logical
partition.

To customize an activation profile to authorize control of other logical partitions:

1. Open a reset profile or open an image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree view on the left side of the window.
3. Select the Security page.
4. Locate the Cross partition authority check box. Then either:
v Mark the check box to allow using the logical partition to control other logical
partitions. The check box displays a check mark when you mark it.
v Or unmark the check box to prevent using the logical partition to control other
logical partitions. The check box becomes empty when you unmark it.

Note: After activating logical partitions, you can use the support element workplace
to dynamically change their security settings, including cross partition
authority. See “Logical partition security” on page 165 for more information.

112 Support Element Operations Guide

Using the automatic reconfiguration facility (ARF): The automatic reconfiguration
facility (ARF) is supported by z/OS and OS/390. A logical partition using the ARF
can serve as a backup for other logical partitions. The backup logical partition can:
v Deactivate a primary logical partition on which a problem has occurred.
v Automatically reconfigure storage previously allocated to the logical partition it
deactivates.

Note: See Processor Resource/Systems Manager Planning Guide, SB10-7036 for

more information about ARF.

Cross partition authority must be enabled for the logical partition on which you want
to use the ARF. That is, you must mark the Cross partition authority check box on
the Security page of the activation profile used to activate the logical partition.

Controlling use of reconfigurable channel paths: The activation profile you use
to activate a logical partition can control whether it has exclusive use of its
reconfigurable channel paths.

A logical partition has exclusive use of its reconfigurable channel paths only while
they are configured on. If the channel paths are configured off, they can be
configured on to another logical partition.

Isolating a logical partition’s reconfigurable channel paths reserves them for the
logical partition while they are configured off, and prevents them from being
configured on to other logical partitions.

To customize an activation profile to control the use of reconfigurable channel

paths:
1. Open a reset profile or open an image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree view on the left side of the window.
3. Select the Security page.
4. Locate the Logical partition isolation check box. Then either:
v Mark the check box to isolate the logical partition’s offline reconfigurable
channels paths. The check box displays a check mark when you mark it.
v Or unmark the check box to make the logical partition’s reconfigurable
channels paths available to other logical partitions when the channel paths
are configured off. The check box becomes empty when you unmark it.

Note: After activating logical partitions, you can use the support element workplace
to dynamically change their security settings, including logical partition
isolation. See “Logical partition security” on page 165 for more information.

Authorizing basic counter set control: The basic counter set authorization
control allows authorization to use the basic counter set in analysis of cache
performance, cycle counts, and instruction counts while the logical CPU is running.

To customize an activation profile to indicate whether authorization is allowed to use

the basic counter set:
1. Open a reset profile or open an image profile.

Chapter 6. Settings for system operations 113

 For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree view on the left side of the window.
3. Select the Security page.
4. Locate the Basic counter set authorization control check box. Then either:
v Mark the check box to indicate whether authorization is allowed to use the
basic counter set authorization control in analysis of cache performance,
cycle counts, and instruction counts while the logical CPU is running.
v Or unmark the check box not to allow authorization to use the basic counter
se authorization control.

Authorizing problem state counter set control: The problem state counter set
authorization control allows authorization to use the problem state counter set in
analysis of cache performance, cycle counts, and instruction counts while the
logical CPU is in problem state.

To customize an activation profile to indicate whether authorization for problem state

counter set is allowed:
1. Open a reset profile or open an image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree view on the left side of the window.
3. Select the Security page.
4. Locate the Problem state counter set authorization control check box. Then
either:
v Mark the check box to indicate whether authorization is allowed to use the
problem state counter set authorization control in analysis of cache
performance, cycle counts, and instruction counts while the logical CPU is in
problem state.
v Or unmark the check box not to allow authorization to use the problem state
counter set authorization control

Authorizing crypto activity counter set control: The crypto activity counter set
authorization control allows authorization to use the crypto activity counter set to
identify the crypto activities contributed by the logical CPU and the blocking effects
on the logical CPU.

To customize an activation profile to indicate whether authorization for crypto activity

counter set authorization control:
1. Open a reset profile or open an image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree view on the left side of the window.
3. Select the Security page.
4. Locate the Crypto activity counter set authorization control check box. Then
either:
v Mark the check box to indicate whether authorization is allowed to use the
crypto activity counter set authorization control to identify the crypto activities
contributed by the logical CPU and the blocking effects on the logical CPU.

114 Support Element Operations Guide

 v Or unmark the check box not to allow authorization to use the crypto activity
counter set authorization control.

Authorizing extended counter set control: The extended counter sets

authorization control allows authorization of the model-dependent extended counter
set.

To customize an activation profile to indicate whether authorization for extended

counter set authorization control:
1. Open a reset profile or open an image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree view on the left side of the window.
3. Select the Security page.
4. Locate the Extended counter set authorization control check box. Then
either:
v Mark the check box to indicate whether authorization is allowed to use the
extended counter set authorization control. The counters of this set are model
dependent.
v Or unmark the check box not to allow authorization to use the extended
counter set authorization control.

Authorizing coprocessor group counter sets control: The coprocessor group

counter set authorization control allows authorization to count the crypto activities of
a coprocessor.

To customize an activation profile to indicate whether authorization for coprocessor

group counter sets authorization control:
1. Open a reset profile or open an image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree view on the left side of the window.
3. Select the Security page.
4. Locate the Coprocessor group counter sets authorization control check
box. Then either:
v Mark the check box to indicate whether authorization is allowed to use the
coprocessor group counter sets to count the crypto activities of a
coprocessor.
v Or unmark the check box not to allow authorization to use the coprocessor
group counter sets authorization control.

Authorizing basic sampling control: The basic sampling authorization control

allows authorization to use the basic sampling function. The sample data includes
an instruction address, the primary ASN, and some state information about the
CPU. This allows tooling programs to map instruction addresses into modules or
tasks, and facilitates determination of hot spots.

To customize an activation profile to indicate whether authorization for basic

sampling authorization control:
1. Open a reset profile or open an image profile.

Chapter 6. Settings for system operations 115

 For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree view on the left side of the window.
3. Select the Security page.
4. Locate the Basic sampling authorization control check box. Then either:
v Mark the check box to indicate whether authorization is allowed to use the
basic sampling authorization control function.
v Or unmark the check box not to allow authorization to use the basic sampling
authorization control.

Allocating storage: The activation profile you use to activate a logical partition
can allocate its storage.

Allocating central storage (main storage): The central storage allocated to a logical
partition upon activation is its initial storage. You must allocate initial central storage
to each logical partition you intend to activate.

To customize an activation profile for allocating central storage to a logical partition:

1. Open a reset profile or open an image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree view on the left side of the window.
3. Select the Storage page.
4. Use the Central storage group box to allocate the logical partition’s central
storage and to set its central storage origin.

Setting I/O priority queuing values: The activation profile you use to activate a
logical partition can control the I/O priority queuing assignment of logical partitions.

To customize an activation profile for I/O priority queuing:

1. Open a reset profile or open an image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile, select the page tab that displays the name of the
logical partition.
3. Select the Options page.
4. Use the controls to set minimum and maximum I/O priority queuing values.

Setting defined capacity: The activation profile you use to activate a logical
partition can control the defined capacity for a logical partition. A defined capacity is
the portion of your processor resources you order from IBM.

Your defined capacity can be associated with:

v A license software product. You specify a defined capacity for a product on the
product certificate.
v An LPAR. You specify a defined capacity for an LPAR using the appropriate
LPAR controls. A defined capacity applies to the entire LPAR, no matter how
many applications it contains.

To customize an activation profile to set defined capacity:

116 Support Element Operations Guide

1. Open a reset profile or open an image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree view on the left side of the window.
3. Select the Options page.
4. Enter the defined capacity value for your logical partition.

Loading operating systems

The topics in this section provide tips for customizing an activation profile for
loading an image with an operating system. The tips are applicable to customizing
reset profiles, image profiles, and load profiles unless indicated otherwise.

Loading an operating system during activation: The activation profile you use
to activate an object can also load its image with an operating system. The object is
a central processor complex (CPC) activated in a logical partition.

To customize an activation profile to load an operating system during an object’s

activation:
1. Open an applicable activation profile:
v If the object is a logical partition, either open a reset profile or open its image
profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.

Note: The activation profile must not be customized to activate the logical
partition as a coupling facility. For more information, see “Selecting an
operating mode” on page 106.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree view on the left side of the window.
3. Select the Load page.
4. Mark the Load during activation check box.
The check box displays a check mark when you mark it. The check mark
indicates activation will include loading the object’s image with an operating
system.
5. Use the other controls on the page to provide information about which operating
system to load and how to load it.

Setting load attributes: The activation profile you use to load an image can set
the load address and load parameter used to perform the load.

The load address is the address of the input/output (I/O) device that provides
access to the operating system you want to load. The I/O device must be in the I/O
configuration that is active when the load is performed. The I/O device may store
the operating system or may be used to read the operating system from a storage
device.

The load parameter is additional information operating systems support to provide

you with additional control over the performance or outcome of a load. Check the
configuration programming and reference documentation for the operating system to
determine the load parameters that are available, and their effect on a load.

To customize an activation profile to set the load address and load parameter:

Chapter 6. Settings for system operations 117

 1. Open an activation profile:
v Open a reset profile or open its image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.

Note: The activation profile must not be customized to activate the logical
partition as a coupling facility. For more information, see “Selecting an
operating mode” on page 106.
v Or open a load profile.
For more information, see “Opening a load profile” on page 128.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree on the left side of the window.
3. Select the Load page.

Note: If you opened a load profile, the Load page is the first and only page.
4. Enter the load address in the Load address field.
5. Enter the load parameter in the Load parameter field.

Using dynamic I/O to set load attributes: The activation profile you use to load an
image can enable using dynamic input/output (I/O) configuration, rather than the
activation profile, to set the load address and load parameter used to perform the
load.

The image must be activated on a CPC that supports dynamic I/O configuration.
The image, or at least one of the images activated on the CPC, must be loaded
with an operating system that supports an application or facility for using dynamic
I/O configuration. Dynamic I/O configuration is supported by:
v The Hardware Configuration Definition (HCD) application on some z/OS and
OS/390 operating systems.
v The dynamic I/O configuration facility of some z/VM and VM operating systems.

To customize an activation profile to enable using dynamic I/O to set the load
address and load parameter:
1. Open an activation profile:
v Open a reset profile or open its image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.

Note: The activation profile must not be customized to activate the logical
partition as a coupling facility. For more information, see “Selecting an
operating mode” on page 106.
v Or open a load profile.
For more information, see “Opening a load profile” on page 128.
2. If you opened a reset profile and the object is a logical partition, select the
name of the logical partition from the profile tree on the left side of the window.
3. Select the Load page.

Note: If you opened a load profile, the Load page is the first and only page.
4. Mark the Use dynamically changed address check box.

118 Support Element Operations Guide

 The check box displays a check mark when you mark it. The check mark
indicates activation will perform each load using the load address set for the
image using dynamic I/O configuration.
5. Mark the Use dynamically changed parameter check box.
The check box displays a check mark when you mark it. The check mark
indicates activation will perform each load using the load parameter set for the
image using dynamic I/O configuration.

Setting a time limit for performing the load: The activation profile you use to
load an image sets a time limit for performing the load.

A time limit, or time-out value, is the amount of time allowed for performing the load.
The load is cancelled if it cannot be completed within the time limit.

To customize an activation profile to set the time limit for performing the load:
1. Open an activation profile:
v Open a reset profile or open its image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.

Note: The activation profile must not be customized to activate the logical
partition as a coupling facility. For more information, see “Selecting an
operating mode” on page 106.
v Or open a load profile.
For more information, see “Opening a load profile” on page 128.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree view on the left side of the window.
3. Select the Load page.

Note: If you opened a load profile, the Load page is the first and only page.
4. Enter the time limit, from 60 to 600 seconds, in the Time-out value field.

Setting SCSI attributes: The activation profile you use to load an image can set
the SCSI parameters used to perform the load.

The Worldwide port name is the number identifying the Fibre Channel port of the
SCSI target device. This field contains the 64-bit binary number designating the port
name, represented by 16 hexadecimal digits.

The Logical unit number is the number of the logical unit as defined by FCP. This
field contains the 64-bit binary number designating the unit number of the FCP I/O
device, represented by 16 hexadecimal digits. This field is required for SCSI IPL
and SCSI dump.

The Boot program selector is a decimal value number specifying the program to be
loaded from the FCP-load device during SCSI IPL or SCSI dump. Valid values
range from 0 to 30.

The Boot record logical block address is the load block address field represented by
16 hexadecimal characters, designating the logical-block address of a boot record
on the FCP-load device. If no block address is specified, the logical-block address
of the boot record is assumed to be zero.

Chapter 6. Settings for system operations 119

 The OS specific load parameters is a variable number of characters to be used by
the program that is loaded during SCSI IPL or SCSI dump. This information will be
given to the IPLed operating system and will be ignored by the machine loader. The
IPLed operating system has to support this.

To customize an activation profile to set the SCSI parameters:

1. Open an activation profile:
v Open a reset profile or open its image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.

Note: The activation profile must not be customized to activate the logical
partition as a coupling facility. For more information, see “Selecting an
operating mode” on page 106.
v Or open a load profile.
For more information, see “Opening a load profile” on page 128.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree view on the left side of the window.
3. Select the Load page.

Note: If you opened a load profile, the Load page is the first and only page.
4. Enter the worldwide port name in the Worldwide port name field.
5. Enter the logical unit name in the Logical unit number field.
6. Enter the boot program number in the Boot program selector field.
7. Enter the boot record logical block address in the Boot record logical block
address field.
8. Enter the OS specific load number in the OS specific load parameters field.

Using the Crypto Express2 feature: The activation profile you use to activate a
logical partition can prepare it for running software products that utilize the Crypto
Express2 feature. Using the feature’s cryptographic facilities and functions requires
customizing the logical partition’s activation profile to:
v Give it access to at least one X2 coprocessor or X2 accelerator. This is
accomplished by selecting from the Usage Domain Index and the Cryptographic
Candidate list.
v Load it with an operating system, such as z/OS, that supports using
cryptographic functions.
v Install the CP Assist for Cryptographic Facility (CPACF) DES/TDES Enablement
feature if planning to use ICSF.

For more information about the cryptographic feature, see “The Crypto Express2
feature” on page 189.

To customize an activation profile to allow a logical partition to use cryptographic

facilities and functions:
1. Open a reset profile or open an image profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. If you opened a reset profile, select the name of the logical partition from the
profile tree view on the left side of the window.
3. Select the General page.

120 Support Element Operations Guide

4. Select ESA/390 , ESA/390 TPF, LINUX Only, or z/VM from the Mode list.
5. Select Crypto from the profile tree view on the left side of the window. Use the
controls on the Crypto page to indicate whether and how you want the logical
partition to use the cryptographic functions and facilities.
Notes:
a. If you intend to use the Integrated Cryptographic Service Facility (ICSF), see
“Using the z/OS Integrated Cryptographic Service Facility (ICSF)” for
additional instructions for customizing the Crypto page.
b. If you intend to use a Trusted Key Entry (TKE) workstation to manage
cryptographic keys, see “Using the Trusted Key Entry (TKE) Workstation
feature” on page 122 for additional instructions for customizing the Crypto
page.
c. After activating logical partitions customized to use X2 coprocessors and X2
accelerators, you can use the support element workplace to view the
settings of the cryptographic controls set on the Crypto page of their
activation profiles. See “Viewing logical partition cryptographic controls” on
page 171 for more information.
6. Customize the Load page to load an operating system that supports using
cryptographic functions and facilities.
For more information about loading an operating system, see the topics that
follow “Loading operating systems” on page 117.

Using the z/OS Integrated Cryptographic Service Facility (ICSF): The z/OS
Integrated Cryptographic Service Facility (ICSF) is a program product that provides
secure, high-speed cryptographic services in the operating environment. You can
use ICSF services for all logical partitions that are customized for using X2
coprocessors and X2 accelerators.

Note: Some functions of ICSF may fail if you do not have the CP Assist for
Cryptographic Functions (CPACF) DES/TDES Enablement feature installed.
See the ICSF Application Programmer’s Guide or the ICSF System
Programmer’s Guide for complete information.

The activation profile you use to activate a logical partition can prepare it for using
ICSF services. Customize the activation profiles when installing the CP Assist for
Cryptographic Functions (CPACF) DES/TDES Enablement feature.

To customize an activation profile for a logical partition to use the ICSF services :
1. Customize a reset profile or image profile to configure the logical partition
access to the cryptographic facilities and functions.
For more information, see “Using the Crypto Express2 feature” on page 120
2. Select the Crypto page again.
3. If you have not already set the logical partition’s controls, set them now:
a. Select a usage domain index for the logical partition to use for cryptographic
functions from the Usage domain index list. More than one number should
be selected from the Usage domain index when z/VM operating
environment is running in the logical partition with other guests (for example,
Linux) requiring access to the cryptographic hardware.

Note: The cryptographic number, selected from the Cryptographic Candidate

List, coupled with the usage domain index must be unique for each
active partition.

Chapter 6. Settings for system operations 121

 4. Select from the Online List the number which specifies the coprocessors to be
brought online at partition activation. For each number selected in the Online
List, the corresponding number in the Candidate List must be selected.

Using the Trusted Key Entry (TKE) Workstation feature: A Trusted Key Entry (TKE)
is a workstation application supported by ICSF to allow an alternative method of
securely loading cryptographic keys (DES and PKA master keys and operational
keys). A unique set of cryptographic keys is maintained for each domain index
within the cryptographic facility. Only one partition can perform TKE functions at a
time. The logical partition with this control is referred to as the TKE host. The other
partitions that receive key updates from the TKE host are referred to as the TKE
targets.

The activation profile you use to activate a logical partition can prepare it for being
a TKE host or TKE target.

To use a TKE workstation to manage requests for secure information or commands

to a specific X2 coprocessor, permission must be given. See “Changing permission
for TKE commands” on page 192.

To customize an activation profile for a TKE host logical partition:

1. Customize a reset profile or image profile to enable the logical partition to use
cryptographic facilities and functions.
For more information, see “Using the Crypto Express2 feature” on page 120.
2. Select the Crypto again.
3. If you have not already set the logical partition’s controls, set them now:
a. Select a usage domain index for the logical partition to use for cryptographic
functions from the Usage domain index list. It must be the same as the
usage domain index set for the logical partition in the ICSF installation
options data set.

Note: The cryptographic number, selected from the Cryptographic

Candidate List, coupled with the usage domain index must be unique
for each active partition.
4. Select from the Online List the number which specifies the coprocessors to be
brought online at partition activation. For each number selected in the Online
List, the corresponding number in the Candidate List must be selected.
5. From the Control domain index list, also select each index that is the same as
the usage domain index of each TKE target logical partition you want to
manage through a TKE workstation connection to this TKE host logical partition.

Profiles for staged activations

You can perform a staged activation of a central processor complex (CPC) and its
images by using a reset profile for an initial activation of the CPC, and then using
other types of profiles for selective activations of its images.

Typical staged activations include:

v Using a reset profile to initially activate the CPC and to activate and load one or
more logical partitions. Then, at a later time, using load profiles to load one or
more previously activated logical partitions with a different operating system, or
using image profiles to activate and load one or more logical partitions not
previously activated.

122 Support Element Operations Guide

 This type of staged activation allows the operator to change the active logical
partitions while maintaining the rest of the CPC’s current operational capabilities
and characteristics.

Initially activating the CPC

You can perform an initial activation of a central processor complex (CPC) by using
a reset profile.

An initial activation means customizing a reset profile. For more information, see
“Supporting LPAR mode operation” on page 95 and the other topics that follow
“Activating CPCs” on page 95.

Selectively activating logical partitions

You can perform a complete activation of a logical partition, but without again
activating the central processor complex (CPC) that supports it, by using its image
profile.

Before you can use an image profile to individually activate a logical partition, you
must use a reset profile to activate the CPC.

Image profiles
Customize an image profile for activating a logical partition when you want to
activate only the logical partition, after the central processor complex (CPC) that
supports it is initially activated.

Optionally, you can customize the image profile to also load the logical partition
during activation.
Notes:
1. Initially activating a CPC requires customizing and using a reset profile. For
more information, see “Supporting LPAR mode operation” on page 95 and the
other topics that follow “Activating CPCs” on page 95.
2. The name of an image profile is the same as the name of the logical partition it
activates. Each logical partition has only one image profile.
Each reset profile that activates a logical partition includes the logical partition’s
only image profile, so changing the logical partition’s information in any
activation profile changes the same information in all the other profiles as well.
That is, if you customize an image profile for activating a logical partition, for
example, changing the image profile also changes the logical partition’s
information in every reset profile that activates the logical partition.

The information used to activate a logical partition, though it is included in a reset

profile, is actually the logical partition’s image profile.

Opening a logical partition’s image profile: You can use the support element
workplace to start the task for customizing the image profile for a logical partition
supported by a central processor complex (CPC) previously activated. Starting the
task is referred to also as opening an image profile.

To open a logical partition’s image profile:

Chapter 6. Settings for system operations 123

 1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer user role (see “Establishing a
support element console session from a Hardware Management Console” on
page 3).
2. Locate the Images you want to work with.
3. Locate the image with the same name as the logical partition.
4. Locate and open the CPC Operational Customization task list.
5. Locate and open the Customize/Delete Activation Profiles task to start it.
This opens the image profile and the list of load profiles you want to customize.
When the list is initially displayed, the highlighted profile is the currently
assigned profile for the partition.
6. Select from the list the name of the image profile you want to customize.
7. Click Customize.

Checking a logical partition’s assigned activation profile: You can assign a

logical partition either its image profile or a load profile as its activation profile.
Whenever the logical partition is activated, individually rather than with the central
processor complex (CPC), it is activated according to the information in its assigned
activation profile.

In addition, whenever you start the task for customizing the logical partition’s
activation profiles, it opens the logical partition’s assigned activation profile. After
you start the task, you can customize its assigned activation profile. If its assigned
activation profile is a load profile, you can also create new load profiles or open and
customize any other existing load profiles.

For example, to customize the image profile for a logical partition, its assigned
activation profile must be its image profile. You can check, and change if necessary,
the logical partition’s assigned activation profile before you begin customizing its
profiles.

To check or change a logical partition’s activation profile:

1. Locate the Images you want to work with.
2. Locate the image with the same name as the logical partition.
3. Click Change options.
This opens the Change Object Options window.
4. Locate the Profile name field.
It displays the name of the profile currently assigned as the logical partition’s
activation profile.
5. Locate the same name in the Profile name column in the list of profiles below
the field. Then check the profile’s type in the Type column.

Note: The list includes the logical partition’s image profile and all the load
profiles that can be assigned to the logical partition.
6. If the assigned profile’s type is Image, then no further action is required.
Whenever you start the task for customizing the logical partition’s activation
profiles, you will be able to customize the logical partition’s image profile.
7. If the assigned profile’s type is Load, you will be able to customize only load
profiles.
To assign the logical partition its image profile instead, use the window to select
and save the image profile.

124 Support Element Operations Guide

Navigating the image profile network: An image profile includes information for
activating a logical partition.

Opening an image profile displays its information on the window organized in a

profile tree view.

The pages are identified in a profile tree view on the left side of the window with a
description label. The description label for each page is a general description of the
information on the page.

To use the profile tree view to turn to a different page of the image profile:
v Click on description label in the profile tree view that you want to open.
A window opens to that page of the image profile.
v To save the changes made, click Save.
v To close the window, click Cancel.

Creating a new image profile: You are responsible for creating image profiles
that meet your unique needs.

Chapter 6. Settings for system operations 125

 You can use the default image profile as a template for creating new profiles. After
you create a new profile, you can customize it as needed. After you create and
customize your own image profiles, you can use them as templates for creating
more new profiles.

To create a new image profile:

1. Open a image profile.
For more information, see “Opening a logical partition’s image profile” on page
123.
2. Select the General page.
The Profile name field identifies the image profile you opened. It will be used
as a template for the new image profile.
3. To use a different image profile as a template:
4. Select the list button beside the Profile name field.
This opens a list of the names of all the CPC’s image profiles. The image profile
named DEFAULT is the default image profile provided by IBM.
5. Select from the list the name of the image profile you want to use as a
template.
This opens the selected image profile. Its information replaces the previous
profile’s information on the pages of the notebook.
6. Enter a unique name for the new profile in the Profile name field.
7. Click Save to save the profile with the new name.

Note: Saving the new profile does not change the image profile you used as a
template.

Using the wizard profile image: The image profile wizard tool can be used to
modify parameters for one or more of the image profiles that you select on the
customize/delete activation profiles list.

126 Support Element Operations Guide

1. Select the image profiles that you want to change parameters.
2. Click Image profile wizard to display the Image Profile Wizard Welcome
window.
3. Click Next to start.
4. Check the appropriate check box that you want to make changes.
5. Click Finish to confirm your changes.

Assigning an image profile to a logical partition: An image profile is

automatically assigned to the logical partition with the same name. Whenever the
logical partition is activated, it is activated according to the information in its
assigned activation profile.

Saving an image profile: You must save an image profile to save the information
you customized on its pages.

To save an open image profile:

1. After opening and customizing an image profile, select the General page.
The Profile name field identifies the image profile that will be saved.
2. Click Save to save the image profile and close it.

Customizing image profiles: The best way to customize an image profile is to go

through the image profile window, page by page, control by control. As you become
familiar with image profiles you should be able to customize them quickly and
easily.

Use the online Help for more information on the image profile window. It provides
additional information about each page and its controls.

Chapter 6. Settings for system operations 127

 The online Help is meant to assist you while you are actually customizing an image
profile. It explains the purpose of each page and its controls, and how to customize
them to activate a logical partition the way you want it activated.

Note: Tips for activating logical partitions apply to customizing reset profiles and
image profiles unless indicated otherwise.

Selectively loading images

You can load an image with an operating system, but without performing another
complete activation of the central processor complex (CPC) or logical partition that
supports it, by using an load profile.

Before you can use a load profile to load an image, you must use a reset profile to
activate the CPC, and use the reset profile or an image profile to initialize the
image.

Load profiles
Customize a load profile for loading an object when you want to only load the object
after it is initially activated.

Loading a logical partition

Customize a load profile for loading a logical partition when you want to only load
the logical partition again, after it is initially activated on a CPC activated.

Note: Initially activating a logical partition requires customizing the reset profile that
activates the CPC. For more information, see “Activating CPCs” on page 95,
and the topics that follow “Activating logical partitions” on page 104.

Opening a load profile: You can use the support element workplace to start the
task for customizing load profiles for an object. The object can be a central
processor complex (CPC) or logical partition. Starting the task is referred to also as
opening a load profile.

To open a load profile:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer user role (see “Establishing a
support element console session from a Hardware Management Console” on
page 3).
2. Locate the CPC to work with.
3. Locate and open the CPC Operational Customization task list.
4. Locate and open the Customize/Delete Activation Profiles task to start it.
This opens the profile list that you want to customize. When the list of profiles is
initially displayed, the highlighted profile is the currently assigned profile for the
object.
5. Select from the list the name of the load profile you want to customize.
6. Click Customize.
This opens the selected load profile. Its information replaces the previous
profile’s information on the notebook page.

128 Support Element Operations Guide

Use the online Help for more information.

Choosing a CPC load type: normal, clear, SCSI, or SCSI dump: The activation
profile you use to load a central processor complex (CPC) can perform either a
normal, clear, SCSI, or SCSI dump load.

To customize an activation profile to choose a CPC load type:

1. Open a load profile.
For more information, see “Opening a load profile” on page 128.
2. Locate the Load type controls. Then either:
v Select Normal to perform a normal load, which performs the load without
clearing main storage.

Note: If you intend to perform the store status function during the load, it
must be a normal load.
v Or select Clear to perform a clear load, which clears main storage during the
load.
v Select SCSI to perform a SCSI load (from certain types of channels), which
clears main storage during the load.
v Or select SCSI dump to perform a SCSI dump (to do a standalone dump
from a SCSI IPL type of device).

Performing store status before a normal load: The activation profile you use to
load a central processor complex (CPC) can perform the store status function
before performing a normal load.

The store status function stores the current values of the processing unit timer, the
clock comparator, the program status word, and the contents of the processor
registers in their assigned absolute storage locations.

Note: For this reason, store status can be performed only before a normal load; a
clear load would clear main storage during the load, including the information
stored by the store status function.

Attention: Do not customize an activation profile to perform store status if the

profile is customized to load an operating system that already automatically
performs store status upon being loaded.

To customize an activation profile to perform store status before a normal load:

1. Open an activation profile:
v Open a load profile.
For more information, see “Opening a load profile” on page 128.
2. Select the Load page.

Note: If you opened a load profile, the Load page is the first and only page.
3. Locate the Load type controls. Select Normal to perform a normal load, which
performs the load without clearing main storage.
4. Mark the Store status check box.
The check box displays a check mark when you mark it. The check mark
indicates activation will perform the store status function before performing the
load.

Chapter 6. Settings for system operations 129

 Creating a new load profile: You are responsible for creating load profiles that
meet your unique needs.

You can use the default load profile as a template for creating new profiles. After
you create a new profile, you can customize it as needed. After you create and
customize your own load profiles, you can use them as templates for creating more
new profiles.

To create a new load profile:

1. Open a load profile.
For more information, see “Opening a load profile” on page 128.
2. Locate the Profile name field.
The field identifies the load profile you opened. It will be used as a template for
the new load profile.
3. To use a different load profile as a template:
a. Select the list button beside the Profile name field.
This opens a list of the names of all the load profiles. The load profile
named DEFAULTLOAD is the default load profile provided by IBM.
b. Select from the list the name of the load profile you want to use as a
template.
This opens the selected load profile. Its information replaces the previous
profile’s information on the notebook page.
4. Enter a unique name for the new profile in the Profile name field.
5. Click Save to save the profile with the new name.

Note: Saving the new profile does not change the load profile you used as a
template.

Assigning a load profile: After you open a load profile for an object, either a
central processor complex (CPC) or logical partition, you can assign it to the object
as its activation profile. Whenever the object is activated, it is activated according to
the information in its assigned activation profile.

To assign an open load profile as an object’s activation profile:

1. After opening and customizing a load profile, the Profile name field identifies
the load profile that will be assigned to the object.
2. Select the Assign profile push button to assign the load profile as the object’s
activation profile.

Saving a load profile: You must save a load profile to save the information you
customized on its page.

To save an open load profile:

1. After opening and customizing a load profile, the Profile name field identifies
the load profile that will be saved.
2. Select the Save push button to save the load profile and close it.

customizing load profiles: The best way to customize a load profile is to go

through the one-page load profile window, control by control. As you become
familiar with load profiles you should be able to customize them quickly and easily.

Use the online Help for more information on the load profile window.

130 Support Element Operations Guide

The online Help is meant to assist you while you are actually customizing a load
profile. It explains the purpose of the page and its controls, and how to customize
them to load a central processor complex (CPC) or logical partition the way you
want it loaded.

Note: Tips for loading operating systems apply to customizing reset profiles, image
profiles, and load profiles unless indicated otherwise.

Group profile
Customize a group profile for activating a logical partition group after the central
processor (CPC) that supports it is initially activated.

Opening a logical partition group profile: You can use the support element
workplace to start the task for customizing the group profile for a logical partitions
assigned to a group.

To open a group profile:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer user role (see “Establishing a
support element console session from a Hardware Management Console” on
page 3).
2. Locate the CPC to work with.
3. Locate and open the CPC Operational Customization task list.
4. Locate and open the Customize/Delete Activation Profiles task to start it.
This opens the profile list that you want to customize. When the list of profiles is
initially displayed, the highlighted profile is the currently assigned profile for the
object.
5. Select from the list the group profile to customize.
6. Click Customize.
This opens the selected group profile.

Use the online Help for more information.

Creating a new group profile: To customize a logical partition group name, enter
a new name in the field. To view or customize an exiting logical partition group
name, select the arrow beside the field to list the names of existing group names.

You can use the default group name as a template for creating a new group name.

To create a new group name:

1. Open the group profile.
For more information, see “Opening a logical partition group profile”
2. The Group name field identifies the group profile name. It can be used as a
template for the new group name.
3. Select the drop-down list button beside the Group name field to use a different
group name as a template.
This opens a list of the names of all the group names. The group named
DEFAULT is the default group name provided by IBM.
4. Select from the list the name of the group you want to use as a template.

Chapter 6. Settings for system operations 131

 5. To create a new group name, enter a unique name for the new logical partition
in the Group name field.
6. Enter a description of the new group name in the Group description field.
7. Click Save to save the group profile with the new.

Use the online Help for more information.

Setting a group capacity value: The group capacity value can be specified in
determining allocation and management of processor resources assigned for a
logical partition group. The activation profile you use to activate a logical partition
group can control the defined capacity for the logical partition group.

To customize an activation profile to set group capacity:

1. Open the group profile.
For more information, see “Opening a reset profile” on page 92 or “Opening a
logical partition’s image profile” on page 123.
2. Enter the group capacity value for your logical partition group.
3. Click Save to store the values.

Use the online Help for more information.

Viewing activation profiles

If you want to only browse activation profiles, rather than customize them, you can
instead use the support element workplace to start the task for viewing activation
profiles previously customized for a central processor complex (CPC).

To view an activation profile:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, or service
representative user role (see “Establishing a support element console session
from a Hardware Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the CPC Operational Customization task list.
4. Locate and open the Customize/Delete Activation Profiles task to start it.
This opens a list of all activation profiles currently customized for activating the
CPC and its images.
5. Select from the list the name of the activation profile you want to view, then click
View.
This opens the selected activation profile.

Use the online Help for more information.

Assigning activation profiles to objects

Whenever an object on the support element workplace is the target of an activation,
it is activated according to the information in its assigned activation profile.

You can assign activation profiles to either the central processor complex (CPC) or
images.

132 Support Element Operations Guide

 To assign an activation profile to an object:
1. Locate the object you want to assign an activation profile.
2. Double-click on the object.
3. Locate the Instance information group box in the object details window.
4. Locate the Activation profile field in the group box.
It displays the name of the profile currently assigned as the object’s activation
profile.
5. To assign a different activation profile to the object, click Change options.
6. Locate the Profile name field from the Change Object Options window.
It displays the name of the profile currently assigned as the object’s activation
profile.
7. Locate the same name in the Profile name column in the list of profiles below
the field. Then check the profile’s type in the Type column.

Note: The list includes all the activation profiles that can be assigned to the
object.
8. To assign the object a different activation profile, select the profile from the list,
then click Save.
This sets the selected profile as the object’s assigned activation profile, and
returns to the object details window.
9. Click Save on the object details window to save the settings, including the
object’s newly assigned activation profile.

Grouping objects for activation

Creating a group, or grouping, is a way to assign more than one activation profile to
an object, rather than changing the object’s assigned activation profile every time
you want to activate it differently.

Grouping creates copies of objects on the support element workplace. The objects
can be the central processor complex (CPC) or its images. Different groups can
contain the same object, such as the CPC, but the object’s settings in one group
can be customized independently of its settings in other groups. One such setting is
the activation profile assigned to the object.

Grouping the CPC for complete activations

You can customize more than one reset profile for performing complete activations
of the CPC and its images. You can customize a reset profile for a complete
activation of the CPC.

To use a reset profile for activating the CPC, you must assign it to the CPC before
performing the activation. Afterwards, to use a different reset profile for activating
the CPC, you could assign it to the CPC, replacing the previously assigned profile.

Rather than changing the reset profile assigned to a CPC each time you want to
use a different one, you can instead create a unique group with the CPC for each
reset profile you want to assign to it.

To assign the CPC a reset profile for activating it:

1. Create a group with the CPC for activating it:
a. Give the group a meaningful name, like LPARMODE.
b. Assign the group’s CPC the reset profile for activating it in LPAR mode.

Chapter 6. Settings for system operations 133

 Then to activate the CPC with either profile, simply activate the appropriate group.

Grouping the CPC for staged activations

You can customize a reset profile for performing an initial activation of the CPC and
customize a load profile for performing a subsequent activation that only loads it.
For example, you may:
v Customize the reset profile to activate the CPC and load the operating system
used for production.
v And customize the load profile to only load the CPC with the operating system
used for performing dumps.

To use the reset profile for activating the CPC, you must assign it to the CPC
before performing the activation. Afterwards, to use the load profile for activating the
CPC, you could assign it to the CPC, replacing the previously assigned profile.

Rather than changing the activation profile assigned to a CPC each time you want
to use a different one, you can instead create a unique group with the CPC for
each activation profile you want to assign to it.

For example, to assign the CPC both a reset profile for activating it initially, and a
load profile for only loading it:
1. Create a group with the CPC for activating it initially:
a. Give the group a meaningful name, like PRODUCTION.
b. Assign the group’s CPC the reset profile.
2. Create another group with the CPC for only loading it:
a. Give the group a meaningful name, like LOADFORDUMP.
b. Assign the group’s CPC the load profile.

Then to activate the CPC with either profile, simply activate the appropriate group.

Grouping images for staged activations

You can customize more than one activation profile for performing staged
activations of the CPC and its images. For example, you may:
v Customize a reset profile for an initial activation of the CPC, with support for
activating three logical partitions, but initially activating only of one of the logical
partitions to support your production environment.
v And customize image profiles for activating the other two logical partitions to
support batch processing and testing environments.

Using the reset profile for activating the CPC and one logical partition still
automatically assigns each logical partition an image profile of the same name as
its activation profile. Afterwards, you may want to deactivate the first logical
partition, and then activate the other two logical partitions.

To help distinguish between the different purposes of the logical partitions, you can
create a unique group with the logical partitions that support each purpose.

So, for example, to use one logical partition for production, and the other two logical
partitions for batch processing and testing:
1. Create a group with the logical partition used for production.
Give the group a meaningful name, like PRODUCTION.

134 Support Element Operations Guide

 2. Create another group with the logical partitions used for batch processing and
testing.
Give the group a meaningful name, like BATCHANDTEST.

Then to establish either environment, simply activate the appropriate group after
deactivating the other group.

Note: The logical partitions in either group will be activated according to the
information in the image profiles automatically assigned to them by the initial
activation of the CPC.

Starting the system automatically after a power outage

Follow your local procedures for recovering from a power outage that is the result of
a utility power failure. You may be able to speed recovery from such power outages
by enabling automatic activation for the central processor complex (CPC).
Automatic activation is a CPC setting that controls whether the CPC is activated
automatically when power is restored following a utility power failure:
v When automatic activation is enabled, and a utility power failure occurs, the CPC
is activated automatically when utility power is restored. The CPC is activated
using the same reset profile used most recently to activate the CPC before the
power outage.
v When automatic activation is disabled, and a utility power failure occurs, the CPC
power remains off when utility power is restored. You can activate the CPC at
any time, but manually, after utility power is restored.

To enable or disable automatic activation:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the CPC Operational Customization task list.
4. Locate and open the Automatic Activation task to start it.
5. Use the Customize Automatic Activation window’s controls to enable or disable
automatic activation:
a. Select the CPC name from the list.
b. Select Options from the menu bar.
c. While automatic activation is disabled, select Enable automatic activation
from the menu to change the CPC’s setting to enabled.
d. While automatic activation is enabled, select Disable automatic activation
from the menu to change the CPC’s setting to disabled.
e. Click Save to save the setting and close the window.

Use the online Help for more information on using the window to enable or disable
automatic activation.

Chapter 6. Settings for system operations 135

Automating system operations
System tasks are the tasks you use to monitor and operate the central processor
complex (CPC). You must use the CPC’s support element console to manually start
a task each time you want it performed.

There is a subset of tasks that you can perform automatically instead. The subset
includes tasks, referred to here as operations, that are typically performed often or
on a regular basis. The operations are:
v Changing licensed internal code:
– Accepting internal code changes.
– Installing and activating internal code changes.
– Retrieving internal code changes from the IBM Service Support System.
– Removing internal code changes and activating the previous change levels.
These operations automate some of the tasks you perform manually by using the
Change Internal Code task.
v Activating the CPC.
This operation automates the task you perform manually by using the Activate
task.
v Deactivating the CPC.
This operation automates the task you perform manually by using the Deactivate
task.
v Accessing external time source for the CPC.
This operation automates the task you perform manually by using the System
(Sysplex) Time task.
v Transmitting system availability data to IBM.
This operation automates one of the tasks you perform manually by using the
Transmit Service Data task.

You can perform the operations automatically by setting up a schedule of operations

for the CPC. This is referred to as scheduling operations. Consider scheduling an
operation when you want to:
v Start the operation while the support element is unattended.
v Have the support element, rather than an operator, start the operation.
v Delay starting the operation until a later time.
v Perform the operation repetitively.

Note: The Lockout disruptive task does not affect a scheduled operation.

Scheduling operations
You can use the support element workplace to start the task for scheduling
operations for the central processor complex (CPC).

To schedule operations for the CPC:

136 Support Element Operations Guide

 1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the CPC Operational Customization task list.
4. Locate and open the Customize Scheduled Operations task to start it.
Select a menu from the menu bar.
5. To schedule an operation for the CPC, select the Options menu from the menu
bar, then select New from the menu.
6. Use the Add a Scheduled Operation window and subsequent windows to
select the operation you want to perform, and to set a schedule for performing it
automatically.
Use the online Help for any window for more information about using it to
schedule the operation.

Setting the CPC time-of-day clock

If you have experience using other systems, you may have used SET CLOCK or a
similar operating system command to set the system’s time-of-day (TOD) clock
during system initialization. The CPC TOD clock is synchronized automatically to
either the support element TOD clock or a time synchronization source.

Synchronizing the CPC TOD clock to a time synchronization source

A Sysplex Timer® is a device that provides a time source to the time-of-day (TOD)
clocks of Central Processor Complexes (CPCs) attached to it and the operating
systems or control programs running on that server (CPC). A feature called an
External Timer Reference (ETR) installed in the CPC provides two ETR attachment
facility (EAF) ports for attaching Sysplex Timers. Both ports may attach the same
Sysplex Timer, or each port may attach a separate Sysplex Timer when configured
with 9037 Expanded Availability.

An ETR network consists of one Sysplex Timer or coupled Sysplex Timers

(Expanded Availability), and the links from this source to the system. Each system
has two ETR attachment facility (EAF) ports which can be connected by a link to
the Sysplex Timer.

Server Time Protocol (STP) is a time synchronization architecture designed to

provide the capability for multiple servers (CPCs) to maintain time synchronization
with each other and to form a Coordinated Timing Network (CTN). STP is designed
for servers (CPCs) that have been configured to be in a Parallel Sysplex® or a
sysplex (without a Coupling Facility), as well as servers (CPCs) that are not in a
sysplex, but need to be time synchronized. STP is designed as a message-based
protocol allowing time keeping information to be sent between servers (CPCs) and
Coupling Facilities (CFs) over InterSystem Channel-3 (ISC-3) links configured in
peer mode, Integrated Cluster Bus-3 (ICB-3) links, Integrated Cluster Bus-4 (ICB-4)
links, or Infiniband.

While the CPC is attached to an operational Sysplex Timer or is using Server Time
Protocol (STP), and if the CPC’s operating or control program supports using the
Sysplex Timer or Server Time Protocol (STP) as a time source:
v The Sysplex Timer or Server Time Protocol (STP) is used as a time source for
the CPC TOD clock.

Chapter 6. Settings for system operations 137

 v The CPC TOD clock maintains clock synchronization with the Sysplex Timer or
Server Time Protocol (STP). When the Sysplex Timer is the time source, the
CPC TOD clock steps at the same rate as the Sysplex Timer. When STP is the
time source, the CPC TOD clock continuously steers the TOD to the correct time.
v The CPC TOD clock is automatically synchronized to the Sysplex Timer or
Server Time Protocol (STP) whenever the time or date at the Sysplex Timer or at
the Current Time Server of an STP-only Coordinated Timing Network is changed.

Synchronizing the CPC TOD clock and the support element TOD clock
Both the central processor complex (CPC) and its support element have time-of-day
(TOD) clocks. The time and date of both TOD clocks should be the same or very
nearly the same. For this reason, the TOD clocks are automatically synchronized
with each other as follows:
v If the CPC does not or cannot use a Sysplex Timer or Server Time Protocol
(STP) as a time source, the CPC TOD clock is synchronized with the support
element TOD clock whenever a power-on reset of the CPC is performed.
v If the CPC uses a Sysplex Timer or Server Time Protocol (STP) as a time
source, changing the time or date at the Sysplex Timer or at the Current Time
Server in an STP-only Coordinated Timing Network automatically synchronizes
the CPC TOD clock to the new time.
v At 11:00PM on the support element TOD clock, it is synchronized with the CPC
TOD clock if:
– The CPC is operating.
– And the support element TOD clock was not set manually since the TOD
clocks were last synchronized.
Otherwise:
– If the CPC is not operating, the support element TOD clock remains
unchanged.
– The support element TOD clock is updated with local time adjustments
(daylight saving time offset, leap seconds offset, and time zone offset) when
they occur, if it is synchronized with the CPC TOD clock.
– Or if the CPC is operating, but the support element TOD clock was set
manually since the TOD clocks were last synchronized, then both TOD clocks
remain unchanged and are not synchronized.

Using a Sysplex Timer or Server Time Protocol (STP) as a time source for the CPC
is intended to prevent manually setting the support element TOD clock.

If the CPC does not or cannot use a Sysplex Timer or Server Time Protocol (STP)
as a time source, you can manually set the support element TOD clock. See
“Setting the support element time-of-day clock manually” on page 259.

Allocating storage
The model of your system determines the minimum, standard, and maximum
storage capacity of the central processor complex (CPC).

Installed storage is part of the CPC’s hardware configuration; it is provided by one

or more storage cards physically installed in the CPC. Allocated storage is installed
storage that is in use for a specific purpose:
v The hardware system area (HSA) is storage only the CPC can use. It stores the
CPC’s licensed internal code and input/output (I/O) definition while the CPC is
activated.

138 Support Element Operations Guide

 v Central storage includes main storage and internal disk subsystem cache.
Operating systems and applications can use main storage; only the CPC can use
the cache.
v Expanded storage is a buffer some operating systems can use for high-speed
paging to and from main storage.

Storage is allocated to a CPC when it is activated.

When the CPC is activated, much of the storage allocated to the CPC can be
allocated to the logical partitions activated on it:
v The central storage allocated to the CPC is the central storage initially available
to logical partitions.
v The expanded storage allocated to the CPC is the expanded storage initially
available to logical partitions.

Like the CPC, storage is allocated to a logical partition when it is activated. So to

allocate storage to the CPC or a logical partition, you must customize the activation
profile you use to activate it.

Reviewing current storage allocations

You can use the support element workplace to start the task for reviewing the
current storage allocations of the central processor complex (CPC) and its logical
partitions.

To review the current storage allocations:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3). The CPC must be
activated or power-on reset.
2. Locate the CPC to work with.
3. Locate and open the CPC Operational Customization task list.
4. Locate and open the Storage Information task to start it.
v Page tabs along the top of the window identify its pages. Select a page tab to
display that page.
v The first page of the window displays information about storage installed and
allocated for the CPC. Its page tab is labelled: Base system storage
allocation.
v If the CPC is activated, the window includes a second tab that displays
information about storage allocated for logical partitions currently activated on
the CPC. Its page tab is labelled: Logical partition storage allocation.
Use the online Help for more information about using the window to review the
current storage allocations.

Degraded storage mode

Degraded storage mode is the result of a hardware failure that prevents the central
processor complex (CPC) from using all of its installed storage. Activating the CPC

Chapter 6. Settings for system operations 139

 fails if a hardware failure that affects its storage occurs. Like all hardware failures,
the CPC automatically analyzes it, then reports it by issuing a hardware message.

The details of the hardware message will instruct you to customize the CPC’s
activation profiles to attempt activating the CPC and its images with half the amount
of its installed storage. Activate the CPC with the newly customized activation
profiles. If the activation succeeds, the CPC resumes operating, but with a reduced
amount of installed storage. This condition, referred to as degraded storage mode,
allows the CPC to continue operating until the hardware failure is corrected by you
or your service provider.

Recognizing degraded storage mode

The support element workplace indicates whether a CPC is operating in degraded
storage mode:
1. Locate the CPC to work with.
2. Check the CPC name:
v If the CPC is operating in degraded storage mode, the term Degraded is
displayed below the CPC name.
v Open the CPC Details window to view the Degraded Reasons.
v Otherwise, if the CPC is operating in normal storage mode, with all of its
installed storage, only the CPC name is displayed.

Determining the degraded mode storage amount

In degraded storage mode, the amount of installed storage available for allocating
central and expanded storage is temporarily reduced. The reduced amount of
available storage is referred to here as the degraded mode storage amount.

Upon activating a central processor complex (CPC) in degraded storage mode,

central storage, and expanded storage are allocated from the degraded mode
storage amount.

To determine the degraded mode storage amount, use the support element
workplace to review the current storage allocations after the CPC recovers in
degraded storage mode.

To determine the degraded mode storage amount:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3). The CPC must be
activated or power-on reset.
2. Locate the CPC to work with.
3. Locate and open the CPC Operational Customization task list.
4. Locate and open the Storage Information task to start it. The window displays
the current storage allocation of the CPC and its logical partitions.
5. Page tabs along the top of the window identify its pages. Select the page tab
labelled Base system storage allocation, if necessary, to display that page.
6. Locate the Customer Storage amount available when your system is in
degraded storage mode.

140 Support Element Operations Guide

 Note: If storage is degraded, a message displays indicating that system
storage is degraded and the amount of customer storage available for
allocating central and expanded storage is temporarily reduced.

Use the online Help for more information about using the window to review the
current storage allocations.

Allocating storage in degraded storage mode

You can change the central or expanded storage allocated to a central processor
complex (CPC) while it remains in degraded storage mode. The total storage you
allocate to the CPC cannot exceed the degraded mode storage amount.

You can also activate logical partitions and allocate storage to them while the CPC
is in degraded storage mode. The total storage allocated to a logical partition
cannot exceed the degraded mode storage amount. Furthermore, the sum of
storage allocations for all activated logical partitions cannot exceed the degraded
mode storage amount.

Allocating CPC storage in degraded storage mode

You can change the central and expanded storage allocated to a CPC operating in
degraded storage mode by customizing a reset profile with new storage amounts,
then using it to activate the CPC:
1. Since degraded storage mode is a temporary condition, you may want to create
a new, temporary reset profile for the CPC, rather than temporarily changing an
existing reset profile.
For more information, see “Creating a new reset profile” on page 94.
2. Activate the CPC with the profile to make the new storage allocations take
effect.
For more information, see “Activating the CPC” on page 62.

Allocating logical partition storage in degraded storage mode

It may be necessary to change the central and expanded storage allocated to a

logical partition before you can activate it on a CPC operating in degraded storage
mode. Check the activation profile you use to activate the logical partition to verify
that its central and expanded storage allocations do not exceed the reduced
amounts of central and expanded storage allocated to the CPC. If necessary,
customize the activation profile to change the central and expanded storage
allocated to a logical partition.
v Check a CPC’s reset profile for the amounts of central storage and expanded
storage allocated to each logical partition activated during CPC activation.
If necessary, customize a reset profile to change the storage allocations of the
logical partitions:
1. Since degraded storage mode is a temporary condition, you may want to
create a new, temporary reset profile for the CPC, rather than temporarily
changing an existing reset profile.
For more information, see “Creating a new reset profile” on page 94.
2. Customize the reset profile to allocate central and expanded storage for each
logical partition activated by the profile.
For more information, see “Allocating storage” on page 116.
3. Activate the CPC with the profile to activate the logical partitions and to make
the new storage allocations take effect.

Chapter 6. Settings for system operations 141

 For more information, see “Activating the CPC” on page 62.
v For each logical partition defined but not activated during CPC activation, check
the logical partition’s image profile for the amounts of central storage and
expanded storage allocated to it.
If necessary, customize the image profile to change the storage allocations of the
logical partitions:
1. Customize the image profile to allocate central and expanded storage for
each logical partition activated by the profile.
For more information, see “Allocating storage” on page 116.
2. Activate the logical partition with the profile to make the new storage
allocations take effect.
For more information, see “Activating the CPC” on page 62.

Whether you activate logical partitions during or after CPC activation, the sums of
central storage and expanded storage allocated to each activated logical partition
cannot exceed the reduced amounts of central and expanded storage allocated to
the CPC.

Getting ready to monitor the system: customizing system activity

profiles
To prepare for using system activity profiles to start system activity analysis, you
can use the support element workplace to work with the profiles as needed.
Working with system activity profiles includes:
v Viewing a profile.
v Customizing a profile.
v Creating a new profile.
v Deleting a profile.
v Preparing to use profiles for monitoring system activity from a Hardware
Management Console.

Regardless of what you want to do with system activity profiles, you will begin by
opening a list of system activity profiles.

Opening a list of system activity profiles

You can use the support element workplace to begin tasks for working with system
activity profiles for a central processor complex (CPC) by opening a list of its
profiles.

To open a list of system activity profiles:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3). The CPC must be
activated or power-on reset.
2. Locate the CPC to work with.
3. Locate and open the CPC Operational Customization task list.
4. Locate and open the System Activity Profiles task to start it.

142 Support Element Operations Guide

 The Customize System Activity window displays.
Use the online Help for more information about using it to work with system
activity profiles.

Viewing a system activity profile

View a system activity profile to determine:
v The particular system resources it is customized to monitor.
v The conditions for which a resource’s usage is reported or ignored.
v How a resource’s usage is presented.

To view a system activity profile, follow the instructions for customizing a system
activity profile, but do not make or save any changes. For instructions, see
“Customizing a system activity profile.”

Note: After starting the task for customizing a profile, you can open various
windows to get detailed information about the contents of the profile. To
avoid changing a profile while you view it, close the first window, Customize
System Activity Profile, by clicking Cancel. If you did inadvertently change
any information in the profile, closing the window in this way will give you an
opportunity to discard the changes.

Customizing a system activity profile

Customize a system activity profile to:
v Define the particular system resources you want to monitor.
v Set conditions for which you want each resource’s usage reported or ignored.
v Indicate how you want each resource’s usage presented.

To customize a system activity profile:

1. Open a list of system activity profiles. For instructions, see “Opening a list of
system activity profiles” on page 142.
This opens the Customize System Activity Profiles List notebook. Its page lists
the CPC’s system activity profiles, and it provides push buttons for working with
them.
2. Select from the list the system activity profile you want to customize, then click
Customize.
This opens the profile. Its information displays on the Customize System Activity
Profile window.
3. Generally, use the window’s controls to customize the profile information.
4. Review the window’s list of activity lines, labelled Line, Component, and
Description, to determine which system resources the profile is currently
customized to monitor.

Note: Central processors (CPs) include the general processors, internal

coupling facility processors, integrated facility for Linux processors, and
integrated facility for application processors.
Change one or more activity lines to:
v Define the particular system resources you want to monitor.
v Set conditions for which you want each resource’s usage reported or ignored.
v Indicate how you want each resource’s usage presented.

Chapter 6. Settings for system operations 143

 5. To change an activity line, use the list, the controls labelled Modify line
options, and click OK as follows:
a. From Modify line options, select the radio button labelled Change line.
b. From the list of activity lines, select the line you want to change.
c. Click OK.
This opens the Change Line window.
d. Locate the list labelled New component for this line; it lists radio buttons
that describe the particular system resources you can monitor.
e. Select the radio button that describes the particular system resource you
want to monitor, then click OK.
This opens an additional window, referred to as an options window, for the
resource you selected to monitor.
f. Use the controls on the options window to set conditions for which you want
the resource’s usage reported or ignored, and to indicate how you want the
resource’s usage presented.
g. Click OK to set the options and complete customizing the activity line.
This returns you to the Customize System Activity Profile window, and
updates its list of activity lines with your changes.
Repeat these steps as needed to customize up to 50 lines of activity.

Note: The activity lines you change are not saved until you save the entire
system activity profile. Save the profile, after you finish customizing it, by
clicking Save on the Customize System Activity Profile window.
6. In addition to changing activity lines, you can use the other line options on the
Customize System Activity Profile window at any time to edit and arrange the
list of activity lines as needed. Use the list, the controls labelled Modify line
options, and click OK as follows:
a. From Modify line options, select the radio button that describes how you
want to modify the activity lines. For example, if you want to delete a line
from the list, select Delete line.
b. From the list of activity lines, select the line you want to modify with the
option you selected.
c. Click OK to use the selected option to modify the selected line.
7. When you finish changing and arranging activity lines, you are ready to finish
customizing the system activity profile and save it. Use the Customize System
Activity Profile window as follows:
a. Optionally, enter in the Description field a brief description of the types of
activity the profile can be used to monitor.

Note: Providing a profile description is recommended. Whenever a list of

system activity profiles is opened, either to work with the profiles or to
start system activity analysis, profile names and descriptions are
listed to help you distinguish between the different profiles and their
purposes.
b. Click Save to save the system activity profile and close it.

Creating a new system activity profile

You are responsible for creating system activity profiles that meet your unique
needs for monitoring system activity.

144 Support Element Operations Guide

 You can use any default system activity profile as a template for creating new
profiles. After you create a new profile, you can customize it as needed. After you
create and customize your own system activity profiles, you can use them as
templates for creating more new profiles.

To create a new system activity profile:

1. Open a list of system activity profiles. For instructions, see “Opening a list of
system activity profiles” on page 142.
This opens the Customize System Activity Profiles List window. Its page lists the
CPC’s system activity profiles, and it provides controls for working with them.
2. Select from the list the system activity profile you want to use as a template for
the new profile, then click Customize.
This opens the profile. Its information displays on the Customize System Activity
Profile window. The Profile name field identifies the system activity profile you
opened. It will be used as a template for the new system activity profile.
3. To create a new profile from the template, enter a new, unique name for the
new profile in the Profile name field.
4. Customize any other information in the profile as needed. For instructions, see
“Customizing a system activity profile” on page 143.
5. Click Save to save the profile with the new name and any other information you
customized.

Note: Saving the new profile does not change the system activity profile you
used as a template.

Preparing to monitor system activity

A hardware management console typically is used to operate and monitor multiple
central processor complexes (CPCs). If you use a hardware management console
to operate and monitor your CPC, in addition to its support element console, then
you can use the hardware management console to monitor the CPC’s system
activity.

Chapter 6. Settings for system operations 145

 The system activity profiles assigned to the CPC are referred to as its active
profiles. The active profile initially assigned to the CPC is the default system activity
profile named DEFAULT. You can assign the CPC other active profiles as needed,
to choose in advance the system activity you want to monitor.

To assign profiles for monitoring system activity:

1. Open a list of system activity profiles. For instructions, see “Opening a list of
system activity profiles” on page 142.
This opens the Customize System Activity Profiles List notebook. Its page lists
the CPC’s system activity profiles, and it provides push buttons for working with
them.
2. Review the information in the list column labelled Status to determine which
profiles are currently assigned to the CPC for monitoring system activity.

Note: The column displays Active for HWMCA to indicate the profile is
assigned to the CPC for monitoring its activity. Otherwise, the column
displays Not active for HWMCA. You may have to scroll the column to
see the entire status.
3. Select from the list the system activity profiles you want to use for monitoring
system activity.

Note: Select all profiles you want to assign as the CPC’s active profiles,
including profiles that are already active.
4. Deselect the active profiles, if any, that you no longer want to use for monitoring
system activity.
5. Click Change status to assign the selected profiles as the CPC’s active
profiles.
This sets the status of each selected profile to Active for HWMCA. Afterwards,
starting system activity analysis will use the active profiles.

Note: If system activity analysis of the CPC is already in progress, it will begin
using the CPC’s newly assigned active profiles shortly after their status is
changed.

146 Support Element Operations Guide

Chapter 7. Settings for remote connections and
communications
This section describes the tasks from the CPC Remote Customization task list you
can use to customize settings that control whether, how, and for what purposes
connections are established and communications are conducted between remote
systems and the support element of the central processor complex (CPC).

To launch the tasks from the CPC Remote Customization task list using the
classic style user interface, see Chapter 2, “Using the tree style user interface,” on
page 9, or if you are using the tree style user interface, see Chapter 3, “Using the
classic style user interface,” on page 35.

Connecting and communicating with a remote service support system

Remote service is two-way communication between the support element of a
central processor complex (CPC) and a remote, automated service support system
provided and maintained by the CPC’s service provider. For example, when IBM is
the CPC’s service provider, IBM provides and maintains the remote, automated IBM
Service Support System.

Note: If you are familiar with IBM service, you may have heard the IBM Service
Support System referred to as RETAIN.

The CPC’s remote service settings control whether and how its support element
uses remote service. When the CPC’s remote service settings are customized for
using remote service, the CPC’s support element uses a feature called the remote
support facility (RSF) to establish a remote connection through its phone server to
your service provider’s service support system. Whenever a connection is
established during a support element operation, it can send information to the
service support system or receive information from it.

Using remote service is optional, but has the following benefits:

v You can let the support element automatically report problems and get service
through the service support system.
v You can use the service support system as a source for retrieving internal code
changes.
v You can use the service support system as a destination for transmitting service
data.

The remaining topics in this section describe these benefits in more detail and
provide instructions for getting them by customizing the CPC’s remote service
settings.

Getting ready to report problems and get service

The support element automatically and continuously monitors itself and the central
processor complex (CPC) for problems. If the support element detects a problem, it
uses a knowledge-based expert system called Problem Analysis to automatically:
v Analyze the problem, attempt to determine its cause, and determine whether
service is required to correct the problem.

© Copyright IBM Corp. 2008 147

 v Issue a hardware message to notify you of the problem. Information provided
with the message includes a detailed description of the problem and instructions
for correcting it or calling for service.
v Send problem information for optical errors to a designated console, if available,
for additional analysis.

If service is required to correct the problem, it is your responsibility to contact your

service provider, report the problem, and request service to correct it. You can do
this manually by calling your service provider on the telephone and using the
information provided with the hardware message to describe the problem.

If your service provider has an automated service support system for receiving and
processing problem reports and service requests, you can report problems and
request service automatically by customizing the support element’s remote service
settings as follows:
v Enable remote service to allow the support element to establish remote
connections through its phone server to your service provider’s service support
system.
v Enable automatic service calling to allow the support element to automatically
report problems and get service through the remote connection to the service
support system.

If the support element detects a problem while remote service and automatic
service calling are enabled, the support element uses its phone server to transmit
the problem report and service request to the service support system, which
receives and processes them according to the service policies of your service
provider. For example, when your service provider is IBM, the IBM Service Support
System analyzes your problem report, then forwards it accordingly:
v When the cause of the problem is known, the IBM Service Support System
forwards the problem report to a service representative, who is then sent to your
location with the instructions, parts list, and other information necessary to
correct the problem.
v When the cause of the problem is not yet known, the IBM Service Support
System forwards the problem report to an IBM Support Center for further
analysis.

To customize the support element for automatically reporting problems and getting
service, see “Customizing remote service settings” on page 149 for instructions for
enabling remote service and automatic service calling.

For more information about the support element’s phone server and optical error
analysis, respectively, see:
v “Providing modem services to the support element” on page 256.
v “Performing problem analysis of optical errors” on page 255.

Getting ready to retrieve internal code changes

Licensed internal code, referred to also as internal code, controls many of the
operations available on a central processor complex (CPC) and its support element.
IBM provides internal code changes to change the internal code of a CPC or its
support element. Changing the internal code may be necessary to add new
functions, improve existing functions, or correct problems.

IBM provides internal code changes by delivering them on a DVD-RAM or diskette,

and by making them available on the IBM Service Support System. Although the

148 Support Element Operations Guide

 same internal code changes are available from each source, the most direct source
is the IBM Service Support System. But you can use the IBM Service Support
System as a source only by customizing, in advance, the CPC’s remote service
settings to enable remote service.

While remote service is enabled, the IBM Service Support System is another source
for manually retrieving internal code changes; that is, DVD-RAM and diskettes
remain eligible sources. If you intend to schedule an operation for retrieving internal
code changes regularly and automatically, the IBM Service Support System is the
only eligible source. You must enable remote service before scheduling an
operation for retrieving internal code changes.

To use the IBM Service Support System as a source for retrieving internal code
changes, either manually or during a scheduled operation, see “Customizing remote
service settings” for instructions for enabling remote service.

Getting ready to transmit service data

Service data is a set of system information, such as program and event traces and
storage dumps, collected by the support element of the central processor complex
(CPC). When IBM is the service provider for your system, service data assists IBM
in servicing it.

You can send service data to IBM either by copying it to a DVD-RAM or diskette for
delivery to IBM, or by transmitting it to IBM through a remote connection to the IBM
Service Support System. Although the same service data is sent to IBM through
each destination, the most direct destination is the IBM Service Support System.
You can use the IBM Service Support System as a destination only by customizing,
in advance, the CPC’s remote service settings to enable remote service.

While remote service is enabled, the IBM Service Support System is another
destination for manually transmitting service data; that is, DVD-RAM and diskettes
remain eligible destinations. If you intend to schedule an operation for transmitting
service data regularly and automatically, the IBM Service Support System is the
only eligible destination. You must enable remote service before scheduling an
operation for transmitting service data.

To use the IBM Service Support System as a destination for transmitting service
data, either manually or during a scheduled operation, see “Customizing remote
service settings” for instructions for enabling remote service.

Customizing remote service settings

You can use the support element workplace to customize the remote service
settings of the central processor complex (CPC). The settings control whether and
how the CPC’s support element uses the remote support facility (RSF) to establish
a remote connection through its phone server to your service provider’s service
support system. Whenever a connection is established during a support element
operation, it can send information to the service support system or receive
information from it.

To customize remote service settings:

Chapter 7. Settings for remote connections and communications 149

 1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the CPC Remote Customization task list.
4. Locate and open the Remote Service task.
5. Use the Customize Remote Service window to set the CPC’s remote service
settings.
6. To enable remote service:
a. Check Enable remote service.
The check mark displays when you mark it. The check mark indicates you
want to enable remote service, which allows the CPC’s support element to
establish remote connections to your service provider’s remote service
support system.
b. Identify the Customer Service Center Telephone Number which the support
element can establish a connection to the service support system, if
available, managed by the service provider for the CPC’s peripheral
products.
7. To enable automatic service calling, check Authorize automatic service call
reporting.
The check mark indicates you want to enable automatic service calling, which
allows the CPC’s support element to automatically report problems and get
service through its remote connection to the service support system.
8. Click OK to save the settings and close the window.

Use the online Help for more information about using the window to customize the
settings.

Assisting service providers with contacting your company

Typically, if the service support system cannot determine the cause of the problem,
it forwards the problem report and service request to a support center for further
analysis by service personnel. The analysis may require a service representative to
contact your company, preferably the person responsible for the CPC at the site
where the CPC is located. So problem reports and service requests transmitted
from the CPC’s support element to the service support system also include such
information.

You can use the support element workplace to customize information, referred to
here as account information, that the CPC’s service providers can use to contact
your company and the person responsible for the CPC.

To customize account information:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.

150 Support Element Operations Guide

3. Locate and open the CPC Remote Customization task.
4. Locate and open the Customer Information task.
5. Select one of the following tabs from the Customer Information window:
v Administrator
v System
v Account.
6. Enter the information in the fields provided.
If the selected objects do not all have the same customer information, the
information displayed on the Customer Information window will be information
that applies to the first selected object. The information for the other objects will
be displayed by tabs on the right.
7. Click OK to save the information and close the notebook.

Use the online Help for more information about using the page to customize the
information.

Chapter 7. Settings for remote connections and communications 151

152 Support Element Operations Guide
Chapter 8. System testing, problem determination, and
service
This section describes the tasks from the Service task list you can use to test,
report problems, and get service for the central processor complex (CPC).

To launch the tasks from the Service task list using the classic style user interface,
see Chapter 2, “Using the tree style user interface,” on page 9, or if you are using
the tree style user interface, see Chapter 3, “Using the classic style user interface,”
on page 35.

Enabling service status

You can enable this task to allow a service representative to perform service tasks
on the CPC or support element. Many of the CPC service tasks require that the
CPC is first placed in service status. Repair and verify, for example, cannot be run
on a CPC until that CPC is placed in service status.

When in service, the CPC status displayed on its Details window will be Service
and no other status will be reported by the CPC until service status is disabled. The
background of the support element workplace also displays Service while service
status is enabled. During a service action, status changes (for example, no power)
that would normally cause an execution due to an unacceptable status will not
cause an exception when the status is service.

Service status also prevents messages indicating the loss of communication to the
support element from displaying while the support element is powered off or during
licensed internal code load.

To enable or disable service status:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the Service task list.
4. Locate and open the Service Status task.
5. Select one or more objects using the check boxes.
6. Point to Options from the menu bar and then click Enable service status,
Disable service status, or Display error message to enable or disable service
status or display error messages, respectively
7. Click Save to save your changes.
8. Click Yes when you are ready to save your changes.

Use the online Help for more information about using the window to set service
status.

© Copyright IBM Corp. 2008 153

Testing the CPC hardware
Checkout tests are test programs typically run by service representatives to test the
central processor complex (CPC) hardware and determine whether it is operating
correctly.

Running checkout tests will require all CPC resources. That is, you will not be able
to run other control programs or operating systems of the CPC while checkout tests
are running.

Checkout tests are fully automated. Once you start them, they require no input or
interaction until they are completed. Checkout tests begin with a power-on reset of
the CPC and with the diagnostic (D0) input/output configuration data set (IOCDS),
followed by loading and running the test programs.

Note: The power-on reset cancels all operations in progress on the CPC, and
loading the checkout tests replaces the CPC’s current control program or
operating system. When the checkout tests are completed, activate the CPC
to perform a power-on reset and load the previous control program or
operating system.

Checkout tests include testing the CPC’s processors and storage, and running
internal wrap tests on its channels.

Note: Other hardware in the CPC’s input/output (I/O) configuration, such as drivers,
receivers, interface cables, control units, and I/O devices, are not tested.

To start checkout tests:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
2. Locate the CPC to work with.

Note: Starting checkout tests on a CPC can be considered disruptive. If the

CPC is locked, unlock it. See “Setting object locking for disruptive tasks
on an object” on page 54.
3. Locate and open the Service task list.
4. Locate and open the Checkout Tests task.
5. Click Run test from the Checkout Tests window to start the checkout tests.
When checkout tests are completed, the results are displayed. The results
provide information about errors that were detected or problems that occurred, if
any, during testing.

Reporting problems and getting service

The support element automatically and continuously monitors itself and the central
processor complex (CPC) for problems. If the support element detects a problem, it
uses a knowledge-based expert system called Problem Analysis to automatically:

154 Support Element Operations Guide

 v Analyze the problem, attempt to determine its cause, and determine whether
service is required to correct the problem.
v Issue a hardware message to notify you of the problem. Information provided
with the message includes a detailed description of the problem and instructions
for correcting it or calling for service.

If service is required to correct the problem, it is your responsibility to contact your

service provider, report the problem, and request service to correct it. You can do
this manually by calling your service provider on the telephone and using the
information provided with the hardware message to describe the problem.

But if your service provider has an automated service support system for receiving
and processing problem reports and service requests, you can report problems and
request service automatically by customizing the support element’s remote service
settings.

Settings for reporting problems and getting service automatically

If your service provider has an automated service support system for receiving and
processing problem reports and service requests, you can report problems and
request service automatically by customizing the support element’s remote service
settings as follows:
v Enable remote service to allow the support element to establish remote
connections to your service provider’s service support system.
v Enable automatic service calling to allow the support element to automatically
report problems and get service through its remote connection to the service
support system.

To customize the support element for automatically reporting problems and getting
service, see “Customizing remote service settings” on page 149 for instructions for
enabling remote service and automatic service calling.

Using hardware messages to report problems and get service

The central processor complex (CPC) and Support Element Console Application
send messages to the support element to notify you of significant events that
involve or affect the use of CPC hardware and licensed internal code. The
messages are referred to as hardware messages. Promptly view hardware
messages as the support element receives them to determine their source and
subject. See “Recognizing when hardware messages were received” on page 64 for
more information about the support element’s hardware message indicators.

Problem Analysis issues hardware messages to notify you of problems detected by

the support element. A hardware message issued by Problem Analysis typically is a
brief, general description of a problem with hardware or licensed internal code.
Information provided with the message includes a detailed description of the
problem and instructions for either correcting the problem or reporting the problem
and getting service.

Problem Analysis issues the hardware messages regardless of whether the support
element’s remote service settings are customized for automatically reporting
problems and getting service. The remote service settings determine only how
problem reports and service requests are transmitted:
v If remote service and automatic service calling are enabled, and if Problem
Analysis determines service is required to correct a problem, it automatically
transmits a problem report and service request to your service provider.

Chapter 8. System testing, problem determination, and service 155

 v If remote service or automatic service calling is not enabled, you must use the
hardware message issued by Problem Analysis to report the problem and get
service.

To use a hardware message to report a problem and get service:

1. Locate the CPC to work with.
2. Locate and open the Hardware Messages task.
The Hardware Messages window pages list the CPC’s hardware messages and
provides controls for working with them.
Use the online Help for more information to view and delete hardware
messages.
3. Select the message that describes the problem for which you want more details,
then click Details.
For hardware messages issued by Problem Analysis, this opens a Problem
Analysis window that displays the message details.
4. Read the information and follow the directions on the Problem Analysis window
to determine what action to take in response to the message.
5. If service is required to correct a problem, click Request service to report the
problem to your service provider and to request service. The support element’s
remote service settings determine how the service request is made:
v If remote service is enabled, requesting service transmits a problem report
and service request to your service provider’s automated service support
system.
v If remote service is not enabled, requesting service displays a window that
provides all the information you need to call your service provider on the
telephone, describe the problem, and request service.

Starting problem analysis manually for suspected problems

The support element starts Problem Analysis automatically only upon detecting a
problem. While the support element provides very comprehensive error detection, if
it does not detect a problem you suspect is affecting the central processor complex
(CPC) or support element, you can use the support element workplace to start
Problem Analysis manually.

To start Problem Analysis manually:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, or system
programmer user role (see “Establishing a support element console session
from a Hardware Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the Service task list.
4. Locate and open the Perform Problem Analysis task.
5. Use the Perform Problem Analysis window to start Problem Analysis manually.
Problem Analysis will issue a hardware message to notify you if it identifies a
problem.
6. Click View All Errors... to view details on all error in the display list.
7. Click View Selected Errors... to view details on a selected error in the display
list.
156 Support Element Operations Guide
 8. Click Cancel to exit the window.

Reporting and getting service manually for suspected problems

Problem Analysis provides the means for reporting a problem and requesting
service only if it identifies the problem and determines service is required to correct
the problem. While Problem Analysis provides very comprehensive problem
identification and determination, if it does not identify or does not determine service
is required for a problem you suspect is affecting the central processor complex
(CPC) or support element, you can use the support element workplace to report the
problem and request service anyway, independently of the results of Problem
Analysis.

To report a problem and request service independently of Problem Analysis:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the Service task list.
4. Locate and open the Report a Problem task.
5. Select the type of the problem you have from the list provided and enter a
description of the problem in the Problem Description box.

Note: If you are just testing problem reporting, select Test automatic problem
reporting and enter This is just a test in the Problem Description box.
6. Click Request Service.

To test problem reporting from the Report a Problem window:

1. Select Test automatic problem reporting and enter This is just a test in the
Problem Description input field.
2. Click Request Service. The Report Problem window is displayed.
3. Click OK to complete this task.

Use the online Help for more information about using the window to report the
problem and request service.

Sending service data to IBM

Service data is a set of system information, such as program and event traces and
storage dumps, collected by the support element of the central processor complex
(CPC). When IBM is your service provider for the CPC, service data assists IBM in
servicing it.

Sending service data to IBM is necessary only when service data is requested by
IBM, usually through either your service representative or IBM Support Center.
Typically, IBM will request service data after a problem is reported if analyzing the
service data is necessary to determine the cause of the problem.

You can send service data to IBM either by copying it to a DVD-RAM for delivery to
IBM, diskette (if one is available), or USB flash memory drive for delivery to IBM, or
by transmitting it to IBM through a remote connection to the IBM Service Support
System.

Chapter 8. System testing, problem determination, and service 157

 Notes:
1. Although the same service data is sent to IBM through each destination, the
most direct destination is the IBM Service Support System. You can use the
IBM Service Support System as a destination only by customizing, in advance,
the CPC’s remote service settings to enable remote service. See “Customizing
remote service settings” on page 149 for instructions for enabling remote
service.
2. If you are using a USB flash memory drive, plug it into the console and then
wait for the console to beep three times. This indicates that the device is ready
and can be accessed. If it does not been three times, unplug the device and try
again.

To send service data to IBM:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the Service task list.
4. Locate and open the Transmit Service Data task.
5. Use the Transmit Service Data window, as directed by your service
representative or IBM Support Center, to select the service data requested by
IBM.
6. Click Send to transmit the selected data.

Use the online Help for more information about using the window to select service
data and send it to IBM.

Dumping data in LPAR or coupling facility mode

Most service data is collected and stored automatically by the support element of
the central processor complex (CPC). This includes logical partition dump data and
coupling facility logical partition dump data.

Logical partition dump data is control area information that is automatically collected
and stored if logical partition errors are detected. Collecting and storing information
is often referred to as dumping data.

Coupling facility logical partition dump data is control area information that is
automatically collected and stored if coupling facility logical partition errors are
detected while a logical partition is operating in coupling facility mode.

Like other types of service data, logical partition dump data and coupling facility
logical partition dump data assist IBM in servicing the CPC. Like other types of
service data, sending dump data to IBM is necessary only when dump data is
requested by IBM.

If the dump data requested by IBM is not available, or if it is available but was not
dumped recently, you can manually dump the data first, then send it and any other
requested service data to IBM.

158 Support Element Operations Guide

Note: If you are not certain whether dump data is already stored on the support
element, or whether it was dumped recently, you can use the Delete LPAR
Dump Data task to check. Starting the task displays a window that lists the
types of dump data, if any, already stored on the support element, and
displays the time and date the data was dumped. See “Deleting dump data”
for instructions for starting the task. After you’ve checked the type, time, and
date of previously dumped data, you will be able to cancel the task without
deleting the previously dumped data.

To manually dump data in LPAR or coupling facility mode:

1. To dump logical partition data, the CPC must be power-on reset.

2. To dump coupling facility logical partition dump data, the CPC must be power-on
reset, and a logical partition must be activated in coupling facility mode.
3. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
4. To dump logical partition dump data, locate the CPC:
a. Locate the CPC to work with.
b. Locate and open the Service task list.
5. To dump coupling facility logical partition dump data, locate the coupling facility
logical partition.
a. Locate the Image you want to work with.
b. Locate and open the Service task list.
6. Locate and start the Dump LPAR Data task.
This opens the dump window for the target object.

Note: If a message notifies you that dump data is already stored on the support
element, you must delete it before you can manually perform another
dump. For more information and instructions, see “Deleting dump data.”
7. Use the window’s controls to select the type of dump you want to perform, then
click OK to start the dump.

Deleting dump data

Dump data remains stored on the support element until it is either:
v Replaced by new dump data during an automatic dump.
v Deleted manually.

Ordinarily, you will not need to delete dump data manually. Deleting dump data is
necessary only if the dump data prevents you from manually dumping new data:
v If a logical partition data dump is already stored on the support element, you
must delete it before you can manually dump new logical partition data.
v If two coupling facility logical partition data dumps are already stored on the
support element, you must delete at least one of them before you can manually
dump new coupling facility logical partition data.

Note: Starting the task for manually deleting dump data is useful also to check the
types of dump data, if any, already stored on the support element, and to

Chapter 8. System testing, problem determination, and service 159

 check the time and date the data was dumped. After you’ve checked the
type, time, and date of previously dumped data, cancel the task to end it
without deleting the previously dumped data.

To manually delete dump data:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the Service task list.
4. Locate and open the Delete LPAR Dump Data task.
5. Use the window’s controls to select the types of dump data you want to delete,
then click Delete to delete them.
Otherwise, if you only wanted to check the type, time, and date of previously
dumped data, click Cancel to end the task without deleting the previously
dumped data.

Dumping SCSI IPL data

SCSI IPL machine loader data is stored automatically by the support element of the
central processor complex (CPC). The first 32 MB of storage in the targeted logical
partition is gathered and sent to IBM.

Like other types of service data, SCSI IPL machine loader data assist IBM in
servicing the CPC. Like other types of service data, sending SCSI IPL machine
loader data to IBM is necessary only when dump data is requested by IBM.

To dump SCSI IPL machine loader data:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the Service task list.
4. Open the Images group, or any group that contains the image.

Note: Performing a dump SCSI IPL on an image can be considered disruptive.

If the CPC image is locked, unlock it. See “Setting object locking for
disruptive tasks on an object” on page 54
5. Locate and start the Dump Machine Loader Data task.
The Dump SCSI IPL Loader Data Confirmation window displays.
6. Click Yes to perform the dump.

160 Support Element Operations Guide

Keeping records of problems and service
The support element automatically keeps records of problem reports and service
requests. Each record, referred to simply as a problem, includes detailed
information about the problem, and indicates whether service is required to correct
the problem is still pending or already completed.

A problem is opened when either:

v Problem Analysis determines service is required to correct a problem detected by
the support element.
v A console operator uses the Report a Problem task to report a suspected
problem not detected by the support element.

The problem and service information is referred to as the service history of the
central processor complex (CPC).

Viewing the CPC’s service history

You can use the support element workplace to display the service history of the
central processor complex (CPC). This task displays a list of current problems for
the CPC. The problems may be opened or closed with the most recent entry at the
top of the list.

To view the CPC’s service history:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the Service task list.
4. Locate and open the View Service History task. The Service History window is
displayed.
5. From the menu bar you can:
v Select View for the following choices:
Problem summary
Displays detailed information about the selected problem including
machine type, model, and serial number information.
Problem analysis panels
Redisplays the Problem Analysis (PA) windows that were created
when the selected problem was originally reported.
Repair information
Displays repair information for the selected problem.
Exit Ends the task.
v Select Close for the following choices:
Selected problem
Changes the current status of the selected problem to be closed.
All problems
Changes the current status of all open problems to be closed.
v Select Sort for the following choices:

Chapter 8. System testing, problem determination, and service 161

 By date
Lists problems in the order of the dates on which problems occurred,
starting with the most recent problem.
By system name
Lists problems by the alphabetical order of the names of the objects
on which they occurred.
By status
Lists all open problems, followed by all closed problems.
v Select Help to display additional tasks information.

Use the online Help for more information about the problem and service information
on it.

Offloading virtual RETAIN data to the HMC DVD

This task allows you to copy problem data onto a hardware management console
DVD media when there is no external connections for your hardware management
console to send problem data.

To offload Virtual RETAIN® data to the HMC DVD:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
access administrator, or service representative user role (see “Establishing a
support element console session from a Hardware Management Console” on
page 3).
2. Locate the CPC to work with.
3. Locate and open the Service task list.
4. Locate and start the Offload Virtual RETAIN Data to HMC DVD task.
The Virtual Retain Data Offload window displays.
5. Select the problem number of the subdirectory you want to offload from the list
A formatted DVD must be loaded in the hardware management console DVD
drive.
6. Click OK to initiate the offload.
This offload process takes several minutes, depending on the size and quantity
of the files to be transferred to DVD-RAM.
Use the online Help for more information on offloading RETAIN data.

Checking InfiniBand multiport status

This task allows you to check the state and status of the InfiniBand® interfaces and
chain links. An option is also available to display which PCHID/CSS.CHPIDs are
controlled by the selected InfiniBand channel.

To check InfiniBand multiport status:

162 Support Element Operations Guide

 1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
mode (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the Service task list.
4. Locate and open the InfiniBand multiport Status and Control task.
The InfniBand multiport Status and Control window displays.
5. Click Display PCHID/CSS.CHPID to display details for both sides of the
InfiniBand.
6. Click Search PCHID/CSS.CHPID to search for a specific PCHID/CSS.CHPID.
7. Click Cancel to close the window.
Use the online Help for more information on checking InfiniBand multiport
status.

Setting OSA-Express network traffic analyzer (NTA) controls

Use this task to select an OSA-Express network traffic analyzer (NTA) support
element control to enable or check the current authorization to trace network traffic.
This task allows you to select:
v Customize OSA-Express network traffic analyzer settings
v Check current OSA-Express network traffic analyzer authorization.

To customize or check the OSA-Express NTA settings:

1. Log onto the support element on the hardware management console through
Single Object Operations in access administrator user mode (see
“Establishing a support element console session from a Hardware Management
Console” on page 3).
2. Locate the CPC you want to work with.
3. Locate and open the Service task list.
4. Locate and open the OSA-Express NTA SE Controls task.
The OSA-Express Network Traffic Analyzer Controls window displays.
5. Select the control to work with:
v Customize OSA-Express Network Traffic Analyzer Settings... provides the
capability to allow or disallow the support element to change authorization to
allow host operating systems to enable the Network Traffic Analyzer to trace
outside their own partition.
v Check current OSA-Express Network Traffic Analyzer authorization... allows
the support element to scan all the OSAs and reports back which OSAs are
authorized for NTA to trace outside its own partition.
6. Click OK to change the current OSA-Express NTA control.

To set the OSA-Express host NTA authorization, see “Using advanced facilities for
OSA-Express channels” on page 228.

Use the online Help for more information on customizing OSA-Express NTA
settings.

Chapter 8. System testing, problem determination, and service 163

Displaying global OSA status
This task allows you to display the global OSA status for all networking OSA
channels on the CPC. The window displays the PCHID, status, CHPID, and other
information associated with each listed channel and an option to display more
detailed information.

Note: This information should be used only under the guidance of IBM product
engineering.

To display the global OSA status:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
mode (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC you want to work with.
3. Locate and open the Service task list.
4. Locate and open the Global OSA Status task.
The Global OSA Status window displays.
5. Click Details to display additional information on a selected OSA channel.
6. Click OK to exit the window.

Use the online Help for more information on global OSA status.

164 Support Element Operations Guide

Chapter 9. LPAR mode operations
This section describes the tasks from the CPC Operational Customization task list
for operating logical partitions.

To launch the tasks from the CPC Operational Customization task list using the
classic style user interface, see Chapter 2, “Using the tree style user interface,” on
page 9, or if you are using the tree style user interface, see Chapter 3, “Using the
classic style user interface,” on page 35.

Changing how logical partitions operate: alternatives to activation

The operational capabilities and characteristics of the central processor complex
(CPC) and its logical partitions are established by the activation profiles used to
activate them. After the CPC is activated, changing the operational capabilities and
characteristics of its logical partitions requires opening and customizing their image
profiles, and then using the profiles to activate the logical partitions.

The following tasks on the support element workplace allow dynamically changing
some of the operational capabilities and characteristics of the CPC and logical
partitions without opening their activation profiles or activating them:
Change LPAR security
Use this task to review or change the settings that determine the extent of
interaction between logical partitions that can be activated on the CPC.
Change LPAR Controls
Use this task to review or change the settings that determine how
processor resources are assigned to, used by, and managed for logical
partitions that can be activated on the CPC.
Change LPAR Group Controls
Use this task to review or change a group assignment and a group capacity
value that can be customized in determining the allocation of processor
resources assigned to the group.
Change LPAR Cryptographic Controls
Use this task to select cryptographic settings to be changed dynamically on
the system, in the image profile, or both
View LPAR Cryptographic Controls
Use this task to review information about the active logical partitions that
use the X2 coprocessors or X2 accelerators assigned to them.
Logical Processor Add
Use this task to select logical processor definitions to be changed
dynamically on the system, in the image profile, or both. Dynamic changes
will take effect without performing a reaction of the logical partition.

Logical partition security

The settings that determine the extent of interaction between logical partitions that
can be activated on the central processor complex (CPC) are referred to here as
security settings.

A logical partition’s security settings are:

© Copyright IBM Corp. 2008 165

 Performance data control
This setting controls whether a logical partition has global access to
performance data.
Input/output configuration control
This setting controls whether a logical partition can change the input/output
(I/O) configuration of the CPC on which it is activated.
Cross partition authority
This setting controls whether a logical partition can issue a subset of control
program instructions to other logical partitions activated on the same CPC.
Logical partition isolation
This setting controls whether a logical partition has exclusive use of its
reconfigurable channel paths.
Basic counter set authorization control
The basic set authorization control can be used in analysis of cache
performance, cycle counts, and instruction counts while the logical CPU is
running.
Problem state counter set authorization control
The problem state set authorization control can be used in analysis of
cache performance, cycle counts, and instruction counts while the logical
CPU is in problem state.
Crypto activity counter set authorization control
The crypto activity counter set authorization control can be used to identify
the crypto activities contributed by the logical CPU and the blocking effects
on the logical CPU.
Extended counter set authorization control
The counters of the extended counter set authorization control are model
depedendent.
Coprocessor group counter set authorization control
The coprocessor group counter set authorization can be used to count the
crypto activities of a coprocessor.
Basic sampling authorization control
The basic sampling authorization control allows tooling programs to map
instruction addresses into modules or tasks, and facilitates determination of
hot spots.

A logical partition’s initial security settings are established by the activation profile
used to activate the logical partition. See“Getting ready to operate the system:
customizing activation profiles” on page 89 for more information about customizing
activation profiles for establishing a logical partition’s initial security settings:

Changing logical partition security

You can use the support element workplace to start the task for reviewing or
changing the security settings of logical partitions that can be activated on the
central processor complex (CPC).

To review or change logical partition security settings:

166 Support Element Operations Guide

 1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.

Note: Changing logical partition security settings on a CPC can be considered

disruptive. If the CPC is locked, unlock it. See “Setting object locking for
disruptive tasks on an object” on page 54.
3. Locate and open the CPC Operational Customization task list.
4. Locate and open the Change LPAR Security task.
The Change Logical Partition Security window displays. The window lists the
logical partitions that can be activated on the CPC and displays check boxes
that indicate their current security settings:
v Performance data control
v Input/output configuration control
v Cross partition security
v Logical partition isolation
v Basic counter set authorization control
v Problem state counter set authorization control
v Crypto activity counter set authorization control
v Extended counter set authorization control
v Coprocessor group counter sets authorization control
v Basic sampling authorization control
Use the online Help for more information about changing logical partition
security.
5. Use the check boxes to change the logical partitions’ security settings, then use
the controls to indicate what you want to do with the new settings.
Use the online Help for more information about changing logical partition
security.
Tips for supporting specific applications:
v Dynamic I/O configuration: Although more than one logical partition can run
an application that supports dynamic I/O configuration, you should allow
using only one logical partition to dynamically change the I/O configuration.
The I/O configuration control setting of the logical partition you choose must
display a check mark. The I/O configuration control setting of all other logical
partitions should be blank.
v Automatic reconfiguration facility (ARF): To use a logical partition for running
an application that supports the ARF, its cross partition authority setting must
display a check mark.

Logical partition controls

The settings that determine how processor resources are assigned to, used by, and
managed for logical partitions that can be activated on the central processor
complex (CPC) are referred to here as control settings. More specifically, control
settings determine:
v Whether logical partitions are assigned dedicated or shared processor resources.
v How each logical partition activated with shared processor resources shares
them with other logical partitions activated with shared processor resources.
v How the CPC manages logical partitions’ use of shared processor resources.

Chapter 9. LPAR mode operations 167

 Both the CPC and its logical partitions have control settings. A logical partition’s
control settings apply to it only. The CPC’s control settings apply to all of its logical
partitions. The control settings are:
Logical processor assignment
These logical partition settings control how many logical processors are
assigned to the logical partition, how they are assigned as either dedicated
or shared processor resources, and the processing weights of logical
partitions. The settings control how a partition is workload managed and
whether software pricing is to change based on the number of defined
capacity.
Processor running time
These CPC settings control how its logical partitions’ processor running time
is determined. The processor running time, referred to also as a timeslice,
is the amount of continuous time allowed for each logical partition’s logical
processors to perform jobs on shared central processors.

The initial control settings of the CPC and each logical partition are established by
the activation profiles used to activate them. See the following topics for more
information about customizing activation profiles for establishing initial control
settings:
v “Getting ready to operate the system: customizing activation profiles” on page 89
v “Assigning initial logical or reserved processors” on page 110
v “Setting processor running time” on page 103
v “Setting defined capacity” on page 116
v “Setting WorkLoad Manager (WLM) controls” on page 109

Changing logical partition controls

You can use the support element workplace to start the task for reviewing or
changing the control settings of the central processor complex (CPC) and the
logical partitions that can be activated on it.

To review or change control settings:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.

Note: Changing logical partition control settings on a CPC can be considered

disruptive. If the CPC is locked, unlock it. See “Setting object locking for
disruptive tasks on an object” on page 54.
3. Locate and open the CPC Operational Customization task list.
4. Locate and open the Change LPAR Controls task.
The Change Logical Partition Controls window displays.
5. Depending on the physical processors installed in your system (CPs, ICFs,
IFLs, IFAs, and zIIPs), select the processor assignment tab to display the
processor assignment window. Each processor assignment window lists the
logical partitions that can be activated on the CPC and displays check boxes,
entry fields, and other controls that indicate their current control settings:

168 Support Element Operations Guide

 v Each logical partition’s settings for logical processor assignments, including
the number of logical processors assigned to each logical partition, and how
they are assigned as either dedicated or shared processor resources. The
defined capacity weights and current weight. Workload manager (WLM) the
current, minimum, and maximum processing weight.
v The CPC’s settings for processor running time.
6. Use the controls to change the control settings of the logical partitions or the
CPC, then proceed to indicate what you want to do with the new settings.
7. Use the controls to change:
v One or more logical partition’s settings for how logical processors are
assigned as either dedicated or shared processor resources.
v The processing weights of logical partitions that share central processors
(and whether they are capped).
v A logical partition to be workload managed with minimum and maximum
weight values to set.
v Defined capacity values for software pricing.
v The CPC’s settings for processor running time.

Use the online Help for more information about changing logical partition controls.

Logical partition group controls

The group assignment for logical partitions determines how allocation and
management of processor resources assigned to the logical partitions in a group
can be activated on the central processor complex (CPC).

Changing logical partition group controls

You can use the support element workplace to start the task for reviewing or
changing the group assignment for logical partitions. The group name, member
partitions, and group capacity value display. A logical partition can become a
member of a group which allows determining the allocation and management of
processor resources assigned to logical partitions in a group. You can change a
group assignment dynamically for the active logical partitions.

To review or change logical partition group controls for the selected CPC:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.

Note: Changing logical partition group controls can be considered disruptive. If

the CPC is locked, unlock it. See “Setting object locking for disruptive
tasks on an object” on page 54.
3. Locate and open the CPC Operational Customization task list.
4. Locate and open the Change LPAR Group Controls task.
The Change Logical Partition Group Controls window displays.
5. Use the controls to change the group capacity or logical partition group
members.

Chapter 9. LPAR mode operations 169

Logical partition cryptographic controls
The settings that determine how the activated logical partition uses the X2
coprocessors and X2 accelerators assigned to are referred here as cryptographic
controls. The logical partition’s cryptographic controls are:
Control domain index numbers
This number identifies the cryptographic domains the logical partition uses
for remote secure administration functions.
Usage domain index numbers
This number identifies the usage domains the logical partition uses for
cryptographic functions. The usage domains cannot be removed if they are
online.
Cryptographic Candidate List
These numbers identify which cryptos will be assigned to the logical
partition. Cryptos cannot be removed if they are online.
Cryptographic Online List
These numbers identify which cryptos will be brought online at the next
logical partition activation. Changes to the online list do not affect the
running system.

Logical partition’s initial cryptographic controls are established by the activation

profile used to activate the logical partition. See “Getting ready to operate the
system: customizing activation profiles” on page 89 for more information about
customizing activation profiles for establishing a logical partition’s initial
cryptographic controls:

Changing logical partition cryptographic controls

You can use the support element workplace to start the task to select cryptographic
control settings to be changed dynamically on the system, in the image profile, or
both.

To dynamically change logical partition cryptographic controls:

1. The Crypto Express2 feature must be installed.

2. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
3. Locate the image to work with.
4. Locate and open the CPC Operational Customization task list.
5. Locate and open the Change LPAR Cryptographic Controls task.
6. Use the Change LPAR Cryptographic Controls window to change the crypto
configuration for a logical partition then proceed to indicate what you want to do
with the new settings.
7. Use the cryptographic controls to dynamically:
v Add crypto(s) and usage domain index(es) to a logical partition for the first
time.
v Add crypto(s), crypto(s) and usage domain index(es), or a usage domain
index(es) to a logical partition that is already using crypto.
v Remove crypto(s), crypto(s) and usage domain index(es), or usage domain
index(es) from a logical partition.

170 Support Element Operations Guide

 v Add and remove crypto(s), crypto(s) and usage domain index(es), or usage
domain index(es) from a logical partition.

Use the online Help for more information on changing logical partition cryptographic
controls.

Viewing logical partition cryptographic controls

You can use the support element workplace to start the task to review information
about the active logical partitions that use the X2 coprocessors or X2 accelerators
assigned to them. You can review:
v A summary tab page of information on all active logical partitions.
v Individual tab pages for each logical partition’s cryptographic controls.

To review the logical partition’s cryptographic controls:

1. The Crypto Express2 feature must be installed.

2. At least one activated logical partition must have at least one X2 coprocessor or
X2 accelerator assigned to it.
3. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
4. Locate the CPC to work with.
5. Locate and open the CPC Operational Customization task list.
6. Locate and open the View LPAR Cryptographic Controls task.
The View LPAR Cryptographic Controls window displays. The window includes
a summarized view tab for cryptos on all partitions and individual tabs for each
logical partition’s cryptographic controls.
7. Click OK when you have finished.

Use the online Help for more information about viewing the cryptographic controls.

Adding logical processors

You can use the support element workplace to start the task that allows you to
select logical processor definitions to be changed dynamically on the system, in the
image profile, or both. Dynamic changes will take effect without performing a
reactivation of the logical partition.

The initial control settings of each logical partition are established by the activation
profiles used to activate them. See the following topics for more information about
customizing activation profiles for establishing initial control settings:
v “Assigning initial logical or reserved processors” on page 110.
v “Setting WorkLoad Manager (WLM) controls” on page 109.

To dynamically add one or more logical processors to a logical processor:

Chapter 9. LPAR mode operations 171

 1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the image to work with.
3. Locate and open the CPC Operational Customization task list.
4. Locate and open the Logical Processor Add task.
The Logical Processor Add window displays.
5. Based on the current logical partition configuration, change the logical processor
definitions for the partition:
v Increase the initial values, reserved values, or both for installed logical
processor types.
v Add a reserved value and set weight capping indicators for logical processor
types that have not yet been installed and have no reserved CPs defined.
v Increase the reserved value for logical processor types that have not been
installed and already have reserved CPs defined.
6. To have the new changes take effect immediately, click Change Running
System.
7. To have the new changes take effect when the logical partition is activated with
the modified profile, click Save to Profiles.
8. To have the new changes take effect immediately and also when the logical
partition is activated with the modified profile, click Save and Change.

Use the online Help for more information on adding a logical processor.

Setting the system time offset

The Logical partition system time offset provides for the optional specification of a
fixed system time offset (specified in days, hours, and quarter hours) for each
logical partition activation profile. The offset, if specified, will be applied to the time
that a logical partition will receive from an External Time Source. This support can
be used to address the following customer environment:
v Multiple local time zones with a single sysplex timer (or sysplex timer network).
It is sometimes necessary to run multiple parallel sysplexes with different local
time and run with the time set to GMT=LOCAL. This causes the results returned
in the store clock (STCK) instruction to reflect local time. With logical partition
system time offset support, logical partitions on each CPC in a Parallel Sysplex
that need to do this can specify an identical system time offset that will shift the
ETR time in the logical partition sysplex members to the desired local time.
Remaining logical partitions on the CPCs, as well as logical partitions on other
CPCs or CPCs in basic mode, can continue to participate in current date
production parallel sysplexes utilizing the sysplex timer(s) with the time provided
by the External Time Source.

To customize the image profile for the system time offset:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer user mode (see “Establishing
a support element console session from a Hardware Management Console” on
page 3).
2. Open an activation profile customized for activating a CPC.
3. Select Logical partition system time offset in the Clock type assignment box
4. Select the Time Offset from the window tree view to set the offset and to choose
how you want it applied when the logical partition’s clock is set.

172 Support Element Operations Guide

 5. Click Save.
6. Activate the CPC.

Use online Help to guide you through completion of this task.

Enabling I/O priority queuing

This task allows you to enable or disable I/O priority queuing for the system.
Enabling the I/O priority queuing allows the system to specify a priority to be
associated with an I/O request at start subchannel time. See “Enabling or disabling
the global input/output (I/O) priority queuing” on page 102 to customize the reset
profile for the CPC.

To enable or disable the I/O priority queuing:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the CPC Operational Customization task list.
4. Locate and open the Enable I/O Priority Queuing task.
The Enable Input/Ouput (I/O) Priority Queuing window displays.
5. Click the drop-down menu under Settings to make your selection:
Enabled
Activates I/O priority queuing for the CPC.
Disabled
Deactivates I/O priority queuing for the CPC.
6. Click Save to save the setting.

Use online Help to guide you through completion of this task.

Changing LPAR I/O priority queuing

This task allows you to review or change the minimum or maximum input/output
(I/O) priority queuing value assignments of logical partitions. These values are
passed on to the I/O subsystem for use when queuing decisions with multiple
requests. You can dynamically (new settings take effect without customizing profiles
or activating objects) change the minimum and maximum input/output (I/O) priority
queuing values. See “Setting I/O priority queuing values” on page 116 to customize
the activation profile for each logical partition.

To change LPAR I/O priority queuing:

Chapter 9. LPAR mode operations 173

 1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the CPC Operational Customization task list.
4. Locate and open the Change LPAR I/O Priority Queuing task.
The Change Logical Partition Input/Output (I/O) Priority Queuing window
displays. The window lists the I/O priority queuing values for logical partitions
defined by this IOCDS.
5. Use the window to dynamically change the minimum and maximum I/O priority
queuing values.

Note: If global input/output I/O priority queuing is Enabled, changes made for
the minimum or maximum values will take effect immediately. If the
global value is Disabled, changes will be saved by the system, but will
not take effect until the global value is changed to Enabled.
6. Make a selection to indicate what you want to do with the new setting.

Use online Help to guide you through completion of this task.

Exporting and importing profile data

This task allows you to export or import activation profiles or system activity profiles
for the CPC to a diskette, to your hard drive, or USB flash memory drive. Exporting
and importing profiles is necessary only when you intend to have your current
system and support element replaced with a new system and support element.
When a Capacity Backup Upgrade (CBU) is activated, more processors (CPs,
SAPs, ICFs) are activated in the system. In most cases, this requires you to change
your activation profiles to include these new processors in the next activation.
Otherwise, the CP/SAP split in the reset profile and the number of dedicated
CPs/ICFs and other processor options in the Image profile won’t specify the correct
options.

To export/import profile data:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3). The CPC must be activated or power-on
reset.
2. Locate the CPC to work with.
3. Locate and open CPC Operational Customization the task list.
4. Locate and open the Export/Import Profile Data task to start it.
The Export/Import Profiles window displays.
5. Select from the options to export/import your activation profiles or system
activity profiles for the CPC to a DVD-RAM, hard drive, or USB flash memory
drive.
6. Click OK.
Use the online Help for more information about exporting/importing profile data.

174 Support Element Operations Guide

Chapter 10. CPC configuration management
This section describes tasks from the CPC Configuration task list and some
elements of the physical and logical configuration of the central processor complex
(CPC). It also describes tasks you can use to get or change information that
describes or defines the CPC configuration.

To launch the tasks from the CPC Configuration task list using the classic style
user interface, see Chapter 2, “Using the tree style user interface,” on page 9, or if
you are using the tree style user interface, see Chapter 3, “Using the classic style
user interface,” on page 35.

Getting information about the hardware configuration

Hardware configuration information stored on the support element of the central
processor complex (CPC) is information about the CPC’s frame and parts in the
frame. Information about the frame includes the machine type, model number, and
serial number of the frame’s machine, and the CPC’s location in the frame. The
information for each part in the frame includes its:
v Location
v Custom card identifier (CCIN)
v Description
v Part number
v Serial number
v Engineering change (EC) number

You can use the support element workplace to display the hardware configuration
information.

To view the hardware configuration:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
2. Locate the CPC you want to work with.
3. Locate and open the CPC Configuration task list.
4. Locate and open the View Hardware Configuration task.
Information is displayed about the CPC’s frame and lists the location, CCIN, and
a description of each part in the frame.
Use the online Help for more information about the display fields and list.
5. To display the part number, serial number, and EC number for a specific part,
select the part from the list, then click Details.
This displays the selected part’s detailed information on the Part Details window.

© Copyright IBM Corp. 2008 175

Displaying the InfiniBand adapter ID
Use this task to display the adapter ID, location, and fanout type assigned to the
InfiniBand channels.

To display the InfiniBand adapter ID:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the CPC Configuration task list.
4. Locate and open the Display Adapter ID task.
5. The Display Assigned Adapter ID window lists the InfiniBand cage-card slot,
location, fanout type and assigned adapter ID.
6. Click OK to exit the window.

The I/O configuration

The input/output (I/O) configuration of the central processor complex (CPC) is the
set of all I/O devices, control units, and channel paths available to the CPC. During
each power-on reset of the CPC, an input/output configuration data set (IOCDS) is
used to define the I/O configuration to the channel subsystem.

You must build an IOCDS and store it on the CPC’s support element before you
can use it during power-on reset to define the CPC’s I/O configuration. You can
build an IOCDS by using an input/output configuration program (IOCP):
v An IOCP may be available as a batch program with your operating system.
For information about using the IOCP, see: Input/Output Configuration Program
User’s Guide, SB10-7037.
v A stand-alone IOCP also is available with the support element.
For information about using the stand-alone IOCP, see: Stand-Alone IOCP User’s
Guide, SB10-7040.

Defining the I/O configuration using the stand-alone IOCP

You can use the support element workplace to start the support processor
input/output configuration program (IOCP) available with the support element of the
central processor complex (CPC).

To start the stand-alone IOCP:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the Image you want to work with.

176 Support Element Operations Guide

 3. Locate and open the CPC Configuration task list.
4. Locate and open the Input/output (I/O) Configuration task.
The Input/Output Configuration window displays.
5. Click Options from the menu bar to display the following menu options:
v Enable Write Protection
v Disable Write Protection
v Copy Configuration
v Export Source File
v Import Source File
v Open Source File
v Delete Source File
v Print Data Set Report
v Write Report to Tape
v Build Data Set
v Disassemble Data Set.
6. Click View from the menu bar to display the following menu options:
v Channel Path Configuration
v Partition Images Configured
v Dynamic Information
v Configuration Program Level
v Support I/O Mask.
7. Click Tools (Service role only) from the menu bar to display the following menu
options:
v Save Data Files on Hardware Management Console...
v Save Data Files to USB Flash Memory Drive
v Restore Data Files from Hardware Management Console...
v Restore Data Files from the USB Flash Memory Drive...
v Restore only IOCDS Data Files from USB Flash Memory Drive
v Restore Only Channel Configuration Files from USB Flash Memory Drive
v Erase Data Files from Hardware Management Console.
8. Click Exit from the Options menu bar to exit the window.

Use the online Help for more information on defining the input/output (I/O)
configuration.

Determining PCHIDs assignments to channels

This task allows you to display the physical locations of all the installed and
configured physical channels and the assigned physical channel identifier (PCHID)
mapping. The CSS.CHPID associated with the PCHID and a description of the
channel hardware type are displayed. The CSS.CHPID identifies the channel
subsystem that the CHPID belongs to. You can view the front and back details of a
specific cage. An action to write the view to a USB flash memory drive allows you
to print the cage view.

To view the channel to PCHID assignments:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. The central processor complex (CPC) must be power-on reset.
Chapter 10. CPC configuration management 177
 3. Locate the CPC to work with.
4. Locate and open the CPC Configuration task list.
5. Locate and open the Channel to PCHID assignment task.
Channel to PCHID assignment window displays.
6. Click View from the menu bar to display the following menu options:
v Sort by Channel Location
v Sort by Cage and PCHID Number
v Sort by Card Type and PCHID Number
v Sort by Book-Jack-MBA
v Sort by Channel State
v Sort by PCHID Number
v Sort by Configured CSS.CHPIDs
v View Cage Details
7. Click Search from the menu bar to display the following menu options:
v SEARCH PCHID
v SEARCH CSS.CHPID
8. Click Exit from the Options menu bar to exit this window.

Use the online Help for more information on determining PCHID assignments.

Viewing the input/output (I/O) configuration data

Use this task to view and analyze your current I/O configuration. The data can be
viewed in several different arrangements giving emphasis to one item. You may
filter the data and it will be applied to all applicable views.

To view and analyze your current I/O configuration:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. The central processor complex (CPC) must be power-on reset.
3. Locate the CPC to work with.
4. Locate and open the CPC Configuration task list.
5. Locate and open the System Input/Output Configuration Analyzer task.
System Input/Output Configuration Analyzer window displays.
6. Select a choice from the following menu bar:
v File to save data to a USB flash memory drive, refresh the display window, or
exit the current window.
v View to display different views for the current I/O configuration data.
v Filter to filter out or to display specific information for the current I/O
configuration.
v Sort to sort the current view using parameters specified.
7. Select Exit from the File menu bar to exit the task.

Use the online Help for more information on completing this task.

178 Support Element Operations Guide

Hardware configuration upgrades and model conversions
Some central processor complex (CPC) configuration tasks support performing
system upgrades and model conversions. Follow your normal order process for
ordering an upgrade or model conversion for your system.

Hardware upgrades
This hardware upgrade option is used in adding memory or book upgrades to
hardware on the system.

To select an option for hardware upgrades:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the CPC Configuration task list.
4. Locate and open the Perform Model Conversion task.
The Model Conversion window displays.
5. Select Hardware upgrades.

Chapter 10. CPC configuration management 179

 6. Select one of the following hardware upgrade choices from the Model
Conversion window:
v Add Book hardware
v Fanout card Rebalance
v Prepare for Enhanced Book Availability

Note: This option is a prerequisite to the Perform Enhanced Book Availability

option and will determine the readiness of the system for the targeted
book. The configured processors and the in-use memory will be
evaluated for the evacuation from the targeted book to the unused
resources available on the remaining books within the system
configuration.
v Perform Enhanced Book Availability

Note: This option allows for the evacuation of system resources from the
targeted book, removal of the book, removal of memory hardware,
addition of new memory hardware, reinstallation of the targeted book,
and finally the restoration of the targeted book into the system
configuration.
v Display Previous Prepare Enhanced Book Availability Results
v System Anchor Record (SAR) upgrade data from media
v Add I/O drawer
v Remove I/O drawer.

Use the online Help for more information on installing hardware upgrades to your
system.

Permanent upgrades
The permanent upgrade option allows you to order permanent capacity upgrades to
processors, memory, and the Crypto Assist Feature (CAF) to your system. Retrieve
your upgrade data from the IBM Service Support System or from a media source.

To select a permanent upgrade option:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the CPC Configuration task list.
4. Locate and open the Perform Model Conversion task.
The Model Conversion window displays.
5. Select one of the following permanent upgrade choices from the Model
Conversion window:
v Retrieve and apply
v Retrieve processor/memory upgrade data but do not apply
v Apply processor/memory upgrade data (previously retrieved)
v Display processor upgrade data (installed and staged)
v Remove processor/memory upgrade data (previously retrieved)
v Retrieve and apply channel upgrade.

180 Support Element Operations Guide

 Use the online Help for more information on installing permanent upgrades to your
system.

Temporary upgrades
The temporary upgrade options allows you to temporarily increase, add, or replace
processor capacity on your system. Retrieve, install, and activated tasks for
temporary records (On/Off CoD, CBU, or Planned Event) are all separate records
located on the IBM Service Support System or media device.
v Installed records include information on the current state of all the installed
temporary upgrades on your system. You can review the information under
Installed Records. Optionally, click Details, Add processors, Remove
processors, or Delete to change the temporary installed upgrades on your
system.
v Stage records include information on temporary upgrades retrieved from the IBM
Service Support System or selected media. The staged records window requires
moving temporary upgrades to the installed area when there is availability of less
than 4 installed upgrades. You can review the information under Staged
Records. Optionally, click Details, Install, or Delete to change the temporary
staged upgrades on your system.

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the CPC Configuration task list.
4. Locate and open the Perform Model Conversion task.
The Model Conversion window displays.
5. Select one of the following temporary upgrade choices from the Model
Conversion window:
Retrieve
To retrieve your upgrade data from the IBM service support system or
other media device.
Manage
To change the state of the installed and staged temporary upgrade
selected records.
View To view installed and staged temporary upgrade records without making
changes.
History
To view the history of actions performed on all temporary upgrade
records.

Use the online Help for more information on installing temporary upgrades to your
system.

Chapter 10. CPC configuration management 181

Time Synchronization features
A Sysplex Timer is a device that provides a time source to the time-of-day (TOD)
clocks of Central Processor Complexes (CPCs) attached to it and the operating
systems or control programs running on that server (CPC). A feature called an
External Timer Reference (ETR) installed in the CPC provides two ETR attachment
facility (EAF) ports for attaching Sysplex Timers. Both ports may attach the same
Sysplex Timer, or each port may attach a separate Sysplex Timer when configured
with 9037 Expanded Availability.

An ETR network consists of one Sysplex Timer or coupled Sysplex Timers

(Expanded Availability), and the links from this source to the system. Each system
has two ETR attachment facility (EAF) ports which can be connected by a link to
the Sysplex Timer.

Server Time Protocol (STP) is a time synchronization architecture designed to

provide the capability for multiple servers (CPCs) to maintain time synchronization
with each other and to form a Coordinated Timing Network (CTN). STP is designed
for servers (CPCs) that have been configured to be in a Parallel Sysplex or a
sysplex (without a Coupling Facility), as well as servers (CPCs) that are not in a
sysplex, but need to be time synchronized. STP is designed as a message-based
protocol allowing timekeeping information to be sent between servers (CPCs) and
Coupling Facilities (CFs) over InterSystem Channel-3 (ISC-3) links configured in
peer mode, Integrated Cluster Bus-3 (ICB-3) links, Integrated Cluster Bus-4 (ICB-4)
links, or Infiniband.

There are two types of CTNs supported by STP:

1. Mixed CTN is a timing network that contains a collection of servers and has at
least one STP-configured server stepping to timing signals provided by the
Sysplex Timer. The CTN ID must be a valid STP network ID and the ETR
network ID must be in the range of 0 to 31.
2. STP-only CTN is a timing network that contains a collection of servers
configured to be in STP timing mode. None of the servers in an STP-only CTN
can be in ETR timing mode.

The feature(s) you have installed on the server (CPC) determines what options are
available for the System (Sysplex) Time task.
v If only the ETR cards are installed, the System (Sysplex) Time window displays
the current configuration and the status of the ETR Attachment Facility (EAF)
ports that allow you to synchronize to the Sysplex Timers for your Central
Complex (CPC). The available tab options are:
– ETR Configuration
– ETR Status.
v If both the ETR features are installed and the Server Time Protocol (STP) feature
enabled, the System (Sysplex) Time window displays the following available tab
options:
– Timing Network
– Network Configuration
– ETR Configuration
– ETR Status
– STP Configuration
– STP Status
– ETS Configuration.

182 Support Element Operations Guide

 v If only the Server Time Protocol (STP) feature is installed, the System (Sysplex)
Time window displays the following available tab options:
– Timing Network
– Network Configuration
– STP Configuration
– STP Status
– ETS Configuration.

Use the online help if you need additional information about the System (Sysplex)
Time task. You can also go to Resource Link, http:/www.ibm.com/servers/
resourcelink click Education in the Navigation bar, under System z9 click z9 EC
(formerly z9-109), and select Introduction to Server Time Protocol (STP).

Setting up time synchronization

Use the System (Sysplex) Time task to setup time synchronization for a server
(CPC) using the Sysplex Timer and/or the Server Time Protocol (STP).

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
mode (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the CPC Configuration task list.
4. Locate and open the System (Sysplex) Time task.
The System (Sysplex) Time window displays.

Note: Depending on the features you have installed and enabled, use the
appropriate tabs that appear at the top of the System (Sysplex) Time
window.

Use the online help if you need additional information about the System (Sysplex)
Time task.

You can also go to Resource Link, http:/www.ibm.com/servers/resourcelink click

Education in the Navigation bar, under System z9 click z9 EC (formerly z9-109),
and select Introduction to Server Time Protocol (STP)

Chapter 10. CPC configuration management 183

Figure 22. System (sysplex) time window

Timing network
Select the Timing Network tab to display the overall timing information for the ETR
network or Coordinated Timing Network (CTN) including the current date and time,
local offsets, and general network information. The information displayed is identical
on each server in the same ETR network or CTN.

In an STP-only CTN adjustments can be made for the management of time, leap
seconds, and time zones. These adjustments are available on every server in the
STP-only CTN but are only enabled on the Current Time Server to ensure all time
and offset adjustments are done at the server providing time information to all
members of the STP-only CTN. Any changes that are made are sent to the Current
Timer Server (CPC) or the CPC being set up to be the Current Time Server. From
there they are distributed throughout the timing network. Depending on the state of
the coordinated timing network and the role of the server (CPC) in the Coordinated
Timing Network (CTN) the following adjustments can be made:
v Adjustment Steering... allows you to view detailed steering information for an
entire STP-only CTN that indicates the amount of time the clock needs to be
adjusted. The server (CPC) is gradually adjusting its clock by steering towards
the new Coordinated Server Time (CST).
Adjustment steering could be the result of the following:
– Setting the time manually on the console
– Dialing out to the External Time Source via the Hardware Management
Console
– Migrating from an STP-only CTN to a Mixed CTN

184 Support Element Operations Guide

 – Accessing the External Time Source (ETS) via Network Time Protocol (NTP).
v Adjust Time... allows you to make a slight adjustment to current Coordinated
Server Time (CST). Click Access External Time Source to get the adjustment
amount from an external time source (if one is set up) or manually enter an
amount. Click OK to send the amount specified to the STP facility.
v Adjust Leap Seconds... allows you to display or change the current leap
seconds to a new leap second offset and when that adjustment should happen.
Click OK to have the new leap second amount or changed schedule time take
affect.
v Adjust Time Zone...allows you to display or change the current time zone and
daylight saving time. Click Define... to set up a time zone not found in the list of
time zones. Make further changes to the daylight saving time start and end, then
click OK to save the changes.

Network configuration
Select the Network Configuration tab to manage or view the STP-only CTN
configuration and any configuration in progress including migration from an
STP-only CTN to a Mixed CTN. The changes are sent to the Current Time Server
(CPC) or the CPC being set up to be the Current Time Server. The changes are
then distributed throughout the network. The Network Configuration window allows
you to:
v Select Apply when you are ready to send a new configuration for the STP-only
CTN to the STP facility or to migrate from an STP-only CTN to a Mixed CTN.
Apply is disabled until the initial values are set in the STP-only CTN.
v Initialize Time... to set up initial time values (leap second offset, time zone, or
date and time) for a CPC that will act as the Current Time Server for a CTN.
v Deconfigure to deconfigure the Preferred Time Server, Backup Time Server, and
Arbiter.

Note: This action is extremely disruptive and should only be done in order to
shut down your STP-only CTN.
v Cancel Migration to Mixed CTN if you decide not to proceed with the migration
of an STP-only CTN to a Mixed CTN.

ETR configuration
If ETR features are installed on your server (CPC), select the ETR Configuration
tab to set the configuration for the ETR attachment facility (EAF) ports to
synchronize your Sysplex Timer. Configuration changes made only affect this
particular server (CPC). They are not applied to an entire timing network. The ETR
Configuration window allows you to:
v Set the configuration for the ETR Attachment Facility (EAF) ports to synchronize
your Central Processor Complex (CPC) to your Sysplex Timer.
v Configure your CPC to participate in a Mixed CTN by specifying an ETR network
ID.
v Migrate your CPC from a Mixed CTN to an STP-only CTN by removing the ETR
network ID.
v Remove the ETR network ID to no longer be part of an ETR network or Mixed
CTN.

ETR status
If the ETR cards are installed on your server (CPC), select the ETR Status tab to
display the configuration and operational state of the ETR connections as viewed by

Chapter 10. CPC configuration management 185

 the server (CPC). Any modifications that need to be done to the ETR configuration,
such as setting the ETR network ID and ETR Unit IDs must be done using the
Sysplex Timer console.

STP configuration
Select the STP Configuration tab to allow you to:
v Configure this server (CPC) or remove it from participating in a Mixed CTN.
v Configure this server (CPC) or remove it from participating in an STP-only CTN

Configuration changes made only affect this particular CPC. They are no applied to
an entire timing network.

Note: When a CPC does not have the ETR feature installed, a decimal number
from 0 to 31 can be specified in the ETR network ID portion of the CTN ID
so that the CPC can participate in a Mixed CTN.

STP status
Select the STP Status tab to display the following STP status information for a
specific CPC:
v Timing state indicates the timing state the CPC is operating in. If it has a value of
anything other than Synchronized then the server is not actively participating in
an ETR network or CTN.
v Usable clock source indicates whether a usable STP-clock source is available in
order to synchronize the server TOD.
v Timing mode indicates the timing mode of your server (CPC) within the ETR
network or CTN.
v Stratum level indicates the hierarchy of this server within the timing network. A
stratum level of 0 indicates the server has no time source.
v Maximum timing stratum level indicates how far a CPC can be from the active
Stratum 1 and still be in a synchronized state
v Maximum STP version indicates the highest level of STP facility code that the
server (CPC) is capable of using.
v System Information identifies the CPCs that are directly attached to the CPC for
STP purposes. The CPC’s Infiniband and coupling links that are initialized to
transport STP messages are listed using the PCHID addresses and are grouped
according to the system that is directly attached to the links. Additionally, the
stratum level, active STP version, and maximum STP version for each directly
attached system is shown.
v Local Uninitialized STP links identifies the possible Infiniband and coupling links
defined in the IODF that may be used by this server to exchange STP
messages.

186 Support Element Operations Guide

Figure 23. STP status page

ETS configuration
If the Network Time Protocol (NTP) support is available, select the ETS
Configuration tab to view or modify the ETS configuration for your server (CPC).
See Figure 25 on page 189.

How this page is used depends on the role of the CPC in the STP-only CTN. The
note that appears on the page indicates the role o the CPC and recommends the
actions that should be taken.

You can:
v Use dial out if configured on Hardware Management Console to allow the
server (CPC) to dial out to the External Time Source (ETS) via the Hardware
Management Console. Use the Hardware Management Console to select the
External Time Source tab from the Customize Outbound Connectivity window,
then set up the parameters to be used when dialing an ETS in support of the
server (CPC) that is participating in the STP-only CTN.
v Use NTP if the server (CPC) needs to access an NTP server as the External
Time Source (ETS). It allows up to two NTP servers to be configured for use and
displays information about these servers.

Chapter 10. CPC configuration management 187

Figure 24. ETS configuration page using the NTP option

v If the server (CPC) does not require an External Time Source (ETS) to be
configured, Use dial out if configured on Hardware Management Console is
the default setting.
v Use NTP with pulse per second (PPS) to configure an External Time Source
(ETS) which provides enhanced time accuracy for the CTN. A highly stable and
accurate pulse per second (PPS) output from the NTP server, that precisely
indicates the start of a second, should be attached to the PPS port of the System
z server in the CTN. One NTP server can be configured to each PPS port.

188 Support Element Operations Guide

Figure 25. ETS configuration page using NTP with PPS option

The Crypto Express2 feature

The Crypto Express2 Feature is an orderable feature.
v The Crypto Express2 Feature works with the Integrated Cryptographic Service
Facility (ICSF) and the IBM Resource Access Control Facility (RACF®) (or
equivalent software products) in an z/OS or OS/390 operating environment to
provide data privacy, data integrity, cryptographic key installation and generation,
electronic cryptographic key distribution, and personal identification number (PIN)
processing. The Crypto Express2 Feature is used also with the IBM Processor
Resource/System Manager (PR/SM™) to establish a logically partitioned (LPAR)
environment in which multiple logical partitions can use cryptographic functions.
v The Crypto Express2 Feature works with the Integrated Cryptographic Service
Facility (ICSF) in an z/OS or OS/390 operating environment to provide support
for RSA (PK) cryptographic operations. The Crypto Express2 Feature is used
with the IBM Processor Resource/System Manager (PR/SM) to establish a
logically partitioned (LPAR) environment in which multiple logical partitions can
use cryptographic functions.

Working with the Crypto Express2 feature

Use the support element to monitor the X2 coprocessors and X2 accelerators by
loading their configuration data during CPC activation.

Chapter 10. CPC configuration management 189

 To work with the Crypto Express2 feature:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. The Crypto Express2 feature must be installed, and the CPC must be
powered-on.
3. Locate the CPC to work with.
4. Locate and open the CPC Configuration task list.
5. Locate and open the Cryptographic Configuration task.

The Cryptographic Configuration window lists the X2 coprocessors and X2

accelerators installed in the CPC and provides controls for working with them.

Configuring and monitoring the Crypto Express2 feature

Upon completing the configuration and initialization of the Crypto Express2 feature,
you can monitor and manage it by:
v Checking the status of the X2 coprocessors or X2 accelerators.
v Testing the random number (RN) generators of the X2 coprocessors.
v Zeroizing the X2 coprocessors.
v Indicate whether you want TKE commands permitted for the X2 coprocessors.
v Import and activate a UDX for any X2 coprocessor installed in your system.
v Select a crypto configuration type for your system.

Checking status for the Crypto Express2 feature

You can use the support element workplace to monitor the status of the Crypto
Express2.

To check the status of the Crypto Express2 feature:

1. Start the Cryptographic Configuration task for working with X2 coprocessors
and X2 accelerators. For instructions, see “Working with the Crypto Express2
feature” on page 189
The Cryptographic Configuration window lists the X2 coprocessors and X2
accelerators installed in the CPC and provides controls for working with them.

Note: The Crypto Express2 has completed its initialization when the status
indicates Configured. After initialization is complete, you need to refresh
the Cryptographic Configuration window. If initialization is ongoing, you
may need to refresh the Cryptographic Configuration window to see the
current status until Configured is indicated.
2. Select from the list the X2 coprocessors or X2 accelerators that you want more
information for.
3. Click View Details.
The Cryptographic Details window displays information on the selected X2
coprocessors or X2 accelerator.

190 Support Element Operations Guide

Testing the RN generator
Each X2 coprocessor includes a random number (RN) that may be used as a key
for encryption. Testing a RN generator verifies whether the numbers it generates
are sufficiently random.

Ordinarily, a RN generator is tested automatically when it is initialized. But you can

use the support element workplace at any time to manually test a RN generator.

You can select to run a RN generator test on individually selected X2 coprocessors

or run a test on all X2 coprocessors.

To test a X2 coprocessor’s RN generator:

1. A power-on reset of the CPC must be complete.
2. The X2 coprocessor must be online and assigned to a logical partition.
3. Log onto the support element in the system programmer or service
representative user mode.
4. Start the Cryptographic Configuration task for working with X2 coprocessors.
For instructions, see “Working with the Crypto Express2 feature” on page 189
The Cryptographic Configuration window lists the X2 coprocessors and X2
accelerators installed in the CPC, and provides push buttons for working with
them.
To manually test a specific X2 coprocessor:
v Select from the list a configured X2 coprocessor that you want to test.
v Click Test RN Generator to test it.
A message is displayed to indicate the results of the test.
To manually run the test on all X2 coprocessors:
v Click Test RN Generator on All X Coprocessors to test it.
A message is displayed to indicate the results of the test.

Zeroizing X2 coprocessors manually

Zeroizing a X2 coprocessor clears all configuration data and cryptographic keys by
resetting them to binary zeroes.

Attention: Zeroizing one or all X2 coprocessor clears its configuration data and
clears all cryptographic keys. Zeroizing all also erases configuration data from the
support element hard drive (for example, UDX files). X2 coprocessors should be
zeroized manually only when absolutely necessary, typically when X2 coprocessors
configuration data must be erased completely.

For example:
v You must zeroize X2 coprocessors prior to selling or transferring ownership of the
CPC.
v A service representative may zeroize X2 coprocessors prior to upgrading the
CPC, if required.
v You may want to zeroize X2 coprocessors if, in an emergency, it is the only way
to maintain the security of encrypted data.

To manually zeroize X2 coprocessors:

1. A power-on reset of the CPC must be complete.
2. The X2 coprocessor must be online and assigned to a logical partition.

Chapter 10. CPC configuration management 191

 3. Start the Cryptographic Configuration task for working with X2 coprocessors.
For instructions, see “Working with the Crypto Express2 feature” on page 189
This displays the Cryptographic Configuration window. The window lists the X2
coprocessors and X2 accelerators installed in the CPC, and provides controls
for working with them.
To manually zeroize a specific X2 coprocessors:
v Select from the list the configured X2 coprocessor you want to zeroize.
v Click Zeroize to zeroize the selected X2 coprocessor.
A Zeroize Warning window is displayed to notify you of the consequences for
clearing the configuration data.
v Click Zeroize to confirm your request to zeroize the selected X2 coprocessor.
To manually run zeroize on all X2 coprocessors:
v Click Zeroize All X Coprocessors to zeroize all the X2 coprocessors and
erase configuration data from the support element hard drive.
A Zeroize Warning window is displayed to notify you of the consequences for
zeroizing all the X2 coprocessors.
v Click Zeroize All to confirm your request to zeroize them.
A message is displayed to indicate the results of the function.

Zeroizing a usage domain

Zeroizing a usage domain clears the cryptographic keys for a selected logical
partition by resetting them to binary zeroes.

To zeroize a logical partition usage domain:

1. A power-on reset of the CPC must be complete.
2. The X2 coprocessor must be offline.
3. Start the Cryptographic Configuration task for working with X2 coprocessors.
For instructions, see “Working with the Crypto Express2 feature” on page 189
This displays the Cryptographic Configuration window. The window lists the X2
coprocessors and X2 accelerators installed in the CPC, and provides controls
for working with them.
To zeroize a usage domain:
v Select from the list the configured X2 coprocessor you want to zeroize.
v Click Usage Domain Zeroize.
A Usage Domain Zeroize window is displayed
v Select the logical partition and usage domain index(es) to zeroize.
v Click Zeroize to confirm your request to zeroize the selected usage domain
indexes.
A message is displayed to indicate the results of the function.

Changing permission for TKE commands

The TKE workstation can manage secure functions of a specific Crypto Express2
feature only if permission is given. If permission is denied, all requests for
information or commands to a specific X2 coprocessor from the TKE workstation
will not be allowed. You can use the support element to dynamically permit or deny
TKE commands to the X2 coprocessor from the TKE workstation.

To permit or deny TKE commands:

1. A power-on reset of the CPC must be complete.
2. The X2 coprocessor must be online and assigned to a logical partition.
192 Support Element Operations Guide
 3. Start the Cryptographic Configuration task for working with X2 coprocessors.
For instructions, see “Working with the Crypto Express2 feature” on page 189
The Cryptographic Configuration window lists the X2 coprocessors and X2
accelerators installed in the CPC and provides controls for working with them.
4. Select from the list the X2 coprocessors that you want to view or modify TKE
command permission.
5. Click TKE Commands.
The TKE Commands Configuration window displays information on the TKE
commands for the selected X2 coprocessors.
6. Locate the Permit TKE Commands check box. Then either:
v Mark the check box to permit TKE commands. The check box displays a
check mark when you mark it.
v Or unmark the check box to deny TKE commands. The check box becomes
empty when you unmark it.
v Click OK to change the permission.
Use the online Help for more information on TKE commands configuration.

Selecting a crypto type configuration

The Crypto Express2 feature can be configured to run as a X2 coprocessor or X2
accelerator. The Crypto Express2 must be deconfigured prior to changing the crypto
configuration type. If you select Accelerator, you can zeroize the selected X2
coprocessor by indicating Zeroize the Coprocessor on the Crypto Type
Configuration window.

To select a crypto type configuration:

1. A power-on reset of the CPC must be complete.
2. The X2 coprocessor or X2 accelerator must be online and assigned to a logical
partition.
3. Start the Cryptographic Configuration task for working with X2 coprocessors
and X2 accelerators. For instructions, see “Working with the Crypto Express2
feature” on page 189
The Cryptographic Configuration window lists the X2 coprocessors and X2
accelerators installed in the CPC and provides controls for working with them.
4. Select from the list the X2 coprocessors or X2 accelerator that you want to
change the crypto type configuration.
5. Click Crypto Type Configuration.
The Crypto Type Configuration window displays information on the selected
Crypto Express2.
6. Select a crypto type configuration for the Crypto Express2.
7. Zeroize the X2 coprocessor when selecting an X2 accelerator crypto type.
8. Click OK to change the crypto type configuration.

Use the online Help for more information on crypto type configuration.

Configuring the User Defined Extensions (UDX)

The UDX allows you to add customized operations to the X2 coprocessor installed.
The UDX provides the capability to develop your own UDX Segment 3 image file
and load your custom Segment 3 image file onto one or more X2 coprocessors. To
view the Segment 3 details, click View Details on the Cryptographic Configuration

Chapter 10. CPC configuration management 193

 window. The Segment 3 image file is built and loaded onto a DVD-RAM using a
Windows NT® workstation. For more information on building a UDX Segment 3
image file go to the following Web site at:
v http://www.ibm.com/security/cryptocards
v Click on Library on the navigation bar.

To configure for User Defined Extension (UDX):

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative
user role (see “Establishing a support element console session from a
Hardware Management Console” on page 3).
2. The Crypto Express2 feature must be installed, and the CPC must be
power-on reset to activate the UDX. Otherwise, to import a UDX file:
3. Locate the CPC to work with.
4. Locate and open the CPC Configuration task list.
5. Locate and open the Cryptographic Configuration task.
The Cryptographic Configuration window lists the X2 coprocessor and X2
accelerators installed in the CPC and provides controls for working with them.
6. Click UDX Configuration to configure the X2 coprocessors for UDX.
The UDX Configuration window displays detailed information for the X2
coprocessor configured for UDX capability and provides controls for working
with them.
7. Insert the UDX DVD-RAM into the hardware management console diskette
drive.
8. Click Import to import the UDX file from the DVD-RAM to the support element
hard drive.
The Import window displays.
9. Click OK.
10. Click Activate to load the UDX data to the X2 coprocessor.

Use the online Help for more information on UDX configuration.

Releasing a X2 Coprocessor or X2 Accelerator

If a Crypto Express2 card is removed from the system, this task allows you to break
the association of the cryptographic number and the card serial number. This is
necessary because the cryptographic number assigned to that card continues to be
associated with the card’s serial number, unless the card is released, preventing
reuse of the cryptographic number.

This task also allows you to view X2 coprocessor and X2 accelerator configuration
of:
v All installed cards with their X2 coprocessor and X2 accelerator assignment,
crypto number, card location, and PCHID.
v All fenced cards.

To release a cryptographic number from the card serial number:

194 Support Element Operations Guide

 1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
access administrator, or service representative user role (see “Establishing a
support element console session from a Hardware Management Console” on
page 3).
2. Locate the CPC to work with.
3. Locate and open the CPC Configuration task list.
4. Locate and open the Cryptographic Management task.
The Cryptographic Management window list the cryptographic number
assignments in the current system configuration.
5. Select the cryptographic number to be released from the card serial number list.
6. Click Release.
The Cryptographic Management window confirms the cryptographic number you
selected to be released.
7. Click Confirm.
A message is displayed to indicate the release was successful.

Releasing NPIV port names

The N Port Identifier Virtualization (NPIV) for Fibre Channel Protocol (FCP)
channels allows sharing of a single physical FCP channel among operating system
images.

Use this task to:

v Display all N Port Identifier Virtualization (NPIV) port names currently assigned to
FCP subchannels
v Release all port names previously assigned to FCP subchannels that are now
locked
v Release a subset of the port names previously assigned to FCP subchannels
that are now locked.

To enable the NPIV mode for selected channel paths see “Enabling NPIV mode” on
page 235.

To release NPIV port names:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the CPC Configuration task list
4. Locate and open the Display NPIV Configuration task.
The FCP Channel - FCP NPIV Port Names window displays.
5. Click Release Assigned Port Names... from the window.

Chapter 10. CPC configuration management 195

 v Select from the list to display all assigned port names, all assigned ports for
an LPAR, or all assigned ports for a PCHID.
v Click OK from the Display FCP NPIV Port Names window after making your
selection.
v Select the appropriate checkbox from the Display Assigned Port Names
window to show only entries with current configuration or only entries with
NPIV on.
v Click Apply to display information on the selected entry.
6. Click Release All Locked Port Names to release the locked port names.
7. Click Release Subset Of Locked Port Names...to release only a subset of
locked port names.
8. Click Cancel to close the current window and exit the task.

Use the Online Help for more information on releasing a NPIV port name.

196 Support Element Operations Guide

Chapter 11. Internal code change management
This section describes tasks from the Change Management task list that you can
use to manage internal code changes provided by IBM for changing the licensed
internal code of the central processor complex (CPC) and its support element. After
describing licensed internal code and internal code changes in more detail, this
section provides instructions for starting the tasks.

Licensed internal code

Licensed internal code, referred to also as internal code, controls many of the
operations of the hardware with which it is provided. For example, internal code is
provided with the central processor complex (CPC) and support element of each
system, and is often provided with other system components such as channels and
optional features.

Activating internal code makes it operational. If you have experience using other
systems, you may have performed an initial microcode load (IML) to make a
system’s internal code operational. Though their names are different, the principle
and purpose of the processes are the same: to load internal code so the system
can use it.

Internal code is stored on system hardware by IBM during manufacturing. After IBM
delivers and installs your system, it may be necessary to change its internal code to
add new functions, improve existing functions, or correct problems. For those
purposes, IBM provides internal code changes.

Internal code changes

IBM provides internal code changes to change the internal code provided with
system hardware. Changing the internal code may be necessary to add new
functions, improve existing functions, or correct problems.

One unit of internal code is called an engineering change (EC). An internal code
change level, referred to also as a change level, is a group of internal code
changes provided to change all or part of the internal code in an EC. The internal
code changes in a change level may replace one or more single bytes of internal
code in an EC, or may entirely replace one or more modules of internal code.

Changing internal code directly affects the internal code already stored on system
hardware, which is the internal code that the system uses when the hardware is
made operational. So following an orderly process in a timely manner is essential
for managing internal code changes correctly.

IBM recommends following the internal code change process described in the next
topic.

Internal code change process

This is a summary of the process you should follow to correctly manage the internal
code changes for a system. Ordinarily, an IBM service representative will provide
new internal code changes and manage their initial use. For internal code changes
already stored on the support element, IBM recommends that you manage these
changes only under the supervision of an IBM service representative or with the
assistance of the IBM Support Center.

© Copyright IBM Corp. 2008 197

 Note to service representatives: Use the system’s service guide to follow service
procedures for changing internal code.

The internal code change process is a sequence of tasks you perform upon
receiving internal code changes from IBM. Changing the internal code may be
necessary to add new functions, improve existing functions, or correct problems.

The goal of the internal code change process is to make the system operate with
the most current internal code available.

If you have multiple systems, IBM recommends you complete the process to your
satisfaction on one system before distributing the changes to the other systems.

The process begins when IBM either delivers new internal code changes to you on
a DVD-RAM or makes changes available on the IBM Service Support System. Then
you should:
1. Backup critical data of the system’s support element.
2. Accept previous internal code changes, if any, that you retrieved, installed, and
activated the last time you used this process.
3. Retrieve all new internal code changes from their source to the support element.
4. Install and activate all new internal code changes to make them operational.
5. Mirror data from the primary support element to the alternate support element.
6. Operate the system to determine whether it is operating correctly and
satisfactorily with the new internal code changes.
7. If you have multiple systems: When you are satisfied with the operation of the
new internal code changes on one system, distribute the changes to other
systems and repeat the internal code change process.

You should use a Hardware Management Console, if available, to follow the

recommended internal code change process for changing a system’s internal code
and distributing its internal code changes to other systems. See“Defining clonable
internal code levels” on page 207 for more information on distributing internal code
levels to multiple systems. If a Hardware Management Console is not available, you
can use each system’s support element console to change its internal code.

Changing internal code

If the system’s central processor complex (CPC) is connected to and managed by a
Hardware Management Console, it is recommended you use the Hardware
Management Console, rather than the CPC’s support element console, to change
the system’s internal code. Refer to the documentation provided with the Hardware
Management Console for more information and instructions.

Otherwise, if you do not have or do not use a Hardware Management Console to

manage the CPC, you can use schedule operations on the support element to
automate much of the process.

Automating the process

You can use the support element of a central processor complex (CPC) to automate
much of the process IBM recommends following for managing internal code
changes.

You can automate the process by:

198 Support Element Operations Guide

v Identifying the task, or operations, you want performed automatically.
v Scheduling when you want each operation performed.
v Customizing how often you want the schedule of operations repeated.

IBM recommends using regularly scheduled operations for managing internal code
changes. The advantages include:
v Installing and activating changes promptly, which may correct internal code errors
before they occur or cause problems on your system.
v Accepting changes regularly, which makes installing and activating subsequent
changes possible.
v Performing a potentially disruptive operation, like activating the CPC, when its
interruption of system availability has the least impact.

Scheduled operations
Use the support element to customize scheduled operations for automatically
performing the following operations in the recommended process for managing
internal code changes.
v Backup critical data of the support element.
v Accept previous internal code changes, if any, that were retrieved, installed, and
activated.
v Retrieve the new internal code changes from the IBM Service Support System to
the support element.
v Install and activate concurrent internal code changes to make them operational.

The operations that can be scheduled on the support element are:

Activate the CPC
Makes the installed code changes operational in place of their
corresponding licensed internal code. Activating the changes does not
permanently modify the internal code and they may be removed until the
time that they are accepted. Activating internal code changes that are not
concurrent may cause the support element(s) to reload its licensed internal
code without warning. If no licensed internal code changes are installed, the
CPC will be activated with the current licensed internal code.
Deactivate (Power-off) selected CPC
Stops the operating system, deallocates resources, clears associated
hardware and powers off the CPC.
Accept internal code changes
Schedules an operation to make activated internal code changes a
permanent working part of the licensed internal code of the selected CPC.
Install and activate concurrent code changes
Schedules an operation for installing and activating internal code changes
retrieved for the selected CPCs.
Remove and activate concurrent code changes
Schedules an operation for removing and activating internal code changed
installed for the selected CPCs.
Retrieve internal code changes
Schedules an operation to copy internal code changes from a remote
service support system to the support element hard disk.

Chapter 11. Internal code change management 199

 Transmit system availability data
Sends service data generated by the selected object to IBM. This data is
used to ensure a high level of availability.
Activate or deactivate processed resources in an OOCoD record
Sends an operation to activate or deactivate a processed OOCoD record.
Change LPAR weights
Schedules an operation to change the processing weight for processor
types assigned to one or more active logical partitions. Specify only the
weights for partitions that you want to change. If a partition specified does
not exist or is not active at the time the operation runs, then that change is
ignored.

To schedule operations for managing internal code changes:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC you want to work with.
3. Locate and open the CPC Operational Customization task list.
4. Locate and open the Customize Scheduled Operations task.
The Customize Scheduled Operations window displays.
5. Click Options from the menu bar to display the following menu options:
v To add a scheduled operation, click New...
v To delete a scheduled operation, select the operation you want to delete,
then click Delete.
v To return to the support element console workplace, click Exit.
6. Click View from the menu bar to display the following menu options:
v To view a scheduled operation, select the operation you want to view, point to
View and then click Scheduled Details...
v To change the time of a scheduled operation, select the operation you want
to view, point to View and then click New Time Range...
7. Click Sort from the menu bar to sort the scheduled operations and select a sort
category that you prefer.
8. Use the online Help to get additional information for scheduling an operation.

Making changes manually

Use the hardware management console of a central processor complex (CPC) to
manually change the internal code of the system.

Note: If the system’s central processor complex (CPC) is connected to and

managed by a Hardware Management Console, it is recommended you use
the Hardware Management Console, rather than the CPC’s support element
console, to change the system’s internal code.

Checking dependencies
Internal code is organized into units called engineering changes (ECs), which are
referred to also as streams.

200 Support Element Operations Guide

Internal code changes may provide new internal code, or correct or improve existing
internal code, for particular streams. If internal code changes for multiple streams
are needed, together, to complete an addition, correction, or improvement of the
internal code, then the internal code changes have dependencies. For example, if
engineering change (EC) E12345, change level 001, must be installed and
activated before EC E54321 level 005 can be installed and activated, then EC
E54321 level 005 has a dependency on EC E12345 level 001.

The dependencies of internal code changes are designated by IBM when the
changes are created. After internal code changes are retrieved to the support
element of the central processor complex (CPC), their dependencies, if any, are
checked automatically whenever you start an operation that will change the
system’s internal code. Such an operation will be attempted only if all dependencies
of the internal code changes are met.

You can use the support element to also manually check the dependencies of
internal code changes. Manually checking dependencies is useful:
v Before you perform an operation for changing the system’s internal code.
By manually checking the dependencies of internal code changes you intend to
select while performing the operation, you may get a detailed list of the
dependencies that would not be met, but which you must meet before or while
actually attempting the operation.

Note: This is especially important if you intend to use specific internal code
changes, rather than all changes, while performing the operation. Using
specific changes increases the possibility of not specifying one or more
dependencies of the specific changes.
v After automatic dependency checking notifies you, upon attempting an operation,
that one or more dependencies are not met.
By manually checking the dependencies of internal code changes you selected
while attempting the operation, you get a detailed list of the dependencies that
were not met, but which you must meet before or while attempting the operation
again.

Ordinarily, only an IBM service representative checks the dependencies of internal

code changes, typically while following a service procedure for changing the
system’s internal code. If you are not following a service procedure, IBM
recommends that you check dependencies only with assistance from IBM Product
Engineering, provided through your IBM service representative or IBM Support
Center.

To manually check dependencies:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. One or more internal code changes must be eligible for being either accepted,
installed, or removed.
3. Locate and open the Change Management task list.
4. Locate and open the Check Dependencies task.
5. Select the radio button that describes the operation and internal code changes
for which you want dependencies checked, then click OK to begin the
dependency checking.

Chapter 11. Internal code change management 201

 6. Wait until a window indicates the dependency checking is complete. The
window also indicates whether all dependencies were met for performing the
selected operation:
v If all dependencies were met, you can return to the service procedure you
are following and proceed with its instructions for actually performing the
operation.
v If one or more dependencies were not met, the window lists messages that
describe each dependency that was not met, identify the operations you must
perform to meet the dependencies, and identify the EC number and change
level of each internal code change you can or must use with the operations
to meet the dependencies. Upon returning to the service procedure you are
following, you can proceed with its instructions and refer to its recovery
actions for meeting failed dependencies described by the messages.
In either case, click OK to close the window.

Use the online Help for more information for any radio button and the operation it
describes and the dependency checking it performs.

Considerations when activating internal code changes

Internal code changes for a system may include changes for the central processor
complex (CPC), its support element, and other system components such as
channels and optional features.

Activating internal code makes it operational after it is changed. The topics in this
section describe how activating internal code affects the system component for
which internal code was changed.

Activating changes for the CPC

Installing or removing internal code for the central processor complex (CPC) may
require activating the CPC.

The types of internal code changes that you install or remove determines whether
activating the CPC is necessary to activate its internal code. There are two types of
internal code changes:
v Concurrent changes
You do not need to activate the CPC to activate internal code that is changed by
installing or removing concurrent changes.
v Disruptive changes
The CPC will be activated when installing or removing disruptive changes.

Since activating a CPC ends its operating system activity, you may want to consider
that consequence when you choose and use workplace tasks to install or remove
changes and activate the internal code:
v Schedule an operation to automatically change and activate concurrent internal
code changes.

Note: Installing or removing disruptive changes must be done from the Change
Internal Code task window on the hardware management console.
v Or use the hardware management console to manually change and activate
internal code to control whether the CPC is activated by choosing the type of
changes to make.

202 Support Element Operations Guide

 Note: The task you use to manually change internal code will indicate whether
internal code changes include concurrent or disruptive changes. You can
choose the type of changes you want installed or removed based on
whether it is OK to activate the CPC to activate the changes:
– If it is OK to activate the CPC, you can install or remove both
concurrent and disruptive internal code changes.
– Otherwise, if it is not OK to activate the CPC, you can either install
concurrent changes up to the first disruptive change, or remove
concurrent changes down to the first disruptive change.

The online Help for the task’s windows provides information and instructions for
choosing the type of changes you can install or remove.

Activating changes for the support element

Activating internal code for the support element after installing or removing internal
code changes may require reinitializing the support element.

Since you do not need to activate the central processor complex (CPC) to activate
support element internal code that was changed, support element internal code
changes are considered concurrent changes. The CPC and its operating systems
continue to operate while the support element internal code is activated.

However, support element operations are interrupted and its applications are ended
when its internal code is activated. You may want to consider those consequences
when you choose and use workplace tasks to install or remove changes and
activate the internal code:
v Schedule an operation to automatically change and activate internal code for a
day and time when the support element is not in use.
v Or manually change and activate internal code when the support element can be
reinitialized without interrupting other operations or ending other applications.

Remote connections to the support element from another console are disrupted
when the support element’s internal code is activated.

Activating changes for channels

Activating internal code for channels after installing or removing internal code
changes will require reinitializing the channels.

In most cases, channel internal code can be activated concurrently. That is, the
central processor complex (CPC) can continue operating while channel internal
code is activated.

Channel internal code cannot be activated concurrently for channels that are in
continuous use. Channels in continuous use are referred to here as continuous
usage channels.

Activating the channel internal code is held pending for continuous usage channels,
rather than interrupting and ending their activity, until either:
v Channel activity stops.
v A power-on reset of the CPC is performed.

Stopping channel activity: The internal code for continuous usage channels will
be activated when the channels are no longer in use. When changes for continuous

Chapter 11. Internal code change management 203

 usage channels are installed, a hardware message is displayed explaining which
types of channels need to be configured off and on again to activate the changes.
To stop channel activity, you can either:
v Use an operating system facility to end channel activity.
v Use tasks from the Channel Operations task list of the support element
workplace to end channel activity.

Note: The operating system may not be notified when channel activity ends. For
this reason, it is recommended you use an operating system facility rather
than the workplace to end channel activity.
v Wait for channel activity to end.

Note: This action may be impractical. Typically, channels with activation of

internal code pending are always in use.

Performing a power-on reset: The internal code for continuous usage channels
will be activated when a power-on reset of the CPC is performed. To perform a
power-on reset, you can either:
v Use the Activate task from the Daily task list to activate the CPC.
v Use the Power-on reset task from the CPC Recovery task list to perform a
power-on reset of the CPC.

Keeping records of internal code changes

The support element automatically keeps records of information about the internal
code changes stored on it. The record-keeping begins when changes are retrieved
from their source to the support element.

For each internal code change, the information identifies:

v Its engineering change (EC) number.
v The change level most recently retrieved.
v The highest retrieved internal code change level that can be installed and
activated concurrently.
v The change level most recently installed.
v The change level most recently activated.
v The change level most recently accepted.
v The lowest installed change level that can be removed and activated
concurrently.
v The lowest change level that can be activated after removing installed change
levels.
v Additional details include the most recent date and time each task was
performed.

The information may assist you with planning and managing internal code changes.
For example, review the information to either:
v Determine whether the central processor complex (CPC) is operating with your
latest available levels of internal code changes.
v Determine which tasks you must perform next to make the CPC operate with
your latest available levels of internal code changes.

Use the support element to view the internal code change information for the CPC.

204 Support Element Operations Guide

Viewing internal code change information
You can use the support element of a central processor complex (CPC) to display
information about the internal code changes stored on it. It also lists the part
number, engineering change (EC) number and state levels of each set of licensed
internal code associated with the support element.

Licensed internal code controls many of the operations available on the support
element. Internal code changes may provide new operations, or correct or improve
existing operations.

The part number and EC number are assigned to a set of licensed internal code by
IBM product engineering. The numbers identify the licensed internal code and its
purpose.

If a set of licensed internal code is modified, its EC number is supplemented with a

state level. A state level distinguishes between different versions of the same set of
licensed internal code.

To view internal code change information:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
access administrator, or service representative user role (see “Establishing a
support element console session from a Hardware Management Console” on
page 3).
2. Locate the CPC to work with.
3. Locate and open the Change Management task list.
4. Locate and open the System Information task.
The System Information window displays. It displays internal code change
information.
5. Select the internal code information you want and then click EC Details... to
view the additional information about this internal code.
6. Click Query Additional Actions... to display information about further actions
that may be needed.
7. Click OK when you have completed this task.

Use the online Help for more information on the internal code change information.

Settings for internal code change management

Both the remote service settings and change management settings of a central
processor complex (CPC) affect how you can use its support element for internal
code change management:
v The CPC’s remote service settings control whether you can use the IBM Service
Support System as a source for retrieving internal code changes to the support
element.
v The CPC’s change management settings control whether and how you can use
retrieved internal code changes to change the internal code of the CPC and its
support element.

Chapter 11. Internal code change management 205

Settings for retrieving internal code changes from the IBM service
support system
IBM provides internal code changes by delivering them on a DVD-RAM or diskette,
and by making them available on the IBM Service Support System. Although the
same internal code changes are available from each source, the most direct source
is the IBM Service Support System. But you can use the IBM Service Support
System as a source only by customizing, in advance, the remote service settings of
a central processor complex (CPC) to enable remote service.

While remote service is enabled, the IBM Service Support System is another source
for manually retrieving internal code changes; that is, DVD-RAM and FTP remain
eligible sources. If you intend to schedule an operation for retrieving internal code
changes regularly and automatically, the IBM Service Support System is the only
eligible source. You must enable remote service before scheduling an operation for
retrieving internal code changes.

To use the IBM Service Support System as a source for retrieving internal code
changes, either manually or during a scheduled operation, see “Customizing remote
service settings” on page 149 for instructions for enabling remote service.

Settings for changing internal code

The change management settings of a central processor complex (CPC) include:
Internal code change authorization
Controls whether you can use retrieved internal code changes to change
the internal code of the CPC and its support element.
This setting is referred to also as the change management services setting.

The change management setting is enabled by default. That is, the setting allows
both:
v Using retrieved internal code changes to change the internal code of the CPC
and its support element.
v And activating concurrent internal code changes concurrently.

Normally, the default change management settings should remain enabled. But the
support element’s change management tasks include tasks for changing the
settings if necessary.

Authorizing internal code changes

When the internal code change authorization setting is enabled, you can use the
support element console to install and activate internal code changes and to
perform subsequent change management operations:
v Accept internal code changes to make them permanent internal code.
v Remove internal code changes to resolve problems.
v Delete internal code changes to attempt error recovery.

Normally, the setting is enabled, which allows changing the internal code of the
CPC and its support element. You can manually disable the setting if there is any
reason you do not want internal code to be changed.

The support element console also disables the setting automatically if it detects
errors after activating new internal code changes, to prevent accepting the

206 Support Element Operations Guide

 erroneous internal code changes. If this happens, you can manually enable the
setting again when you want to install and activate new internal code changes that
correct the previously detected error.

To change the setting for internal code change authorization:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the Change Management task list.
4. Locate and open the Authorize Internal Code Changes task.
5. Use the Authorize Internal Code Changes window controls to enable or disable
the setting for internal code change authorization:
a. While the setting is enabled, the Do not allow installation and activation
of internal code changes check box is empty.
To disable the setting of the next activation, click once on the check box to
mark it.
b. While the setting is disabled of the next activation, the Do not allow
installation and activation of internal code changes check box displays a
check mark.
To enable the setting, click once on the check box to unmark it.
c. Click Save to save the setting and close the window.
Use the online Help for more information to enable or disable the setting for
internal code change authorization.

Defining clonable internal code levels

The Define Clonable Internal Code Levels task allows you to define internal code
levels to save and send to RETAIN. The defined clonable internal code levels from
a system are saved with an identifying name and password and sent to RETAIN,
then later retrieved using the hardware management console to bring another
system to the identical internal code level. The Define Clonable Internal Code
Levels window displays a list of all clonable internal code levels that have been
defined. Click Details... to display the engineering change numbers and levels
associated with a selected defined clonable internal code level. You can use the
Define Clonable Internal Code Levels task to:
v Create a new defined clonable internal code level to be saved and sent to
RETAIN
v Replace an existing defined clonable internal code level with an updated level
and send to RETAIN
v Delete an existing defined clonable internal code level that is no longer needed.

Note: The Define Clonable Internal Code Levels window displays the machine
serial number for the support element. You will need this machine serial
number when retrieving the clonable level definition data from the hardware
management console.

To define a clonable internal code level:

Chapter 11. Internal code change management 207
 1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the Change Management task list.
4. Locate and open the Define Clonable Internal Code Levels task.

The Define Clonable Internal Code Levels window includes push buttons to perform
tasks when working with defining a clonable internal code level. You can use the
window to:
1. Type an identifying alphanumeric name and alphanumeric password of 1 to 8
characters in the Name and Password entry fields. Then, click Create to save
a clonable internal code level to send to RETAIN.
2. Select a defined internal code level from the list to be replaced, then click
Replace to replace the selected existing defined internal code level with an
updated level to send to RETAIN.
3. Select a defined clonable internal code level from the list that is no longer
needed, then click Delete to delete the existing defined clonable internal code
level.

Use the online Help for more information on defining clonable internal code levels.

Forcing channel internal code change

Internal code changes are pending for all channel, if any, that were busy during the
most recent concurrent internal code change operation, and have remained busy
since then.

The internal code change operation may have been either an installation and
activation, or a temporary removal and activation of concurrent internal code
changes. Rather than interrupting and ending activity on busy channels, their
internal code was not updated, and the channel internal code changes were held
pending for them.

When internal code changes are pending for one or more channel paths in the
input/output (I/O) configuration of the central processor complex (CPC), you can
forcibly update their licensed internal code with pending changes using the Force
Channel Internal Code Change task.

Note: Forcibly updating the licensed internal code of a channel path will interrupt
and end channel activity on busy channels that have internal code changes
pending and may disrupt the operation of the CPC if it is using the
interrupted channels.

To forcibly update licensed internal code with pending changes:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.

208 Support Element Operations Guide

 3. Locate and open the Change Management task list.
4. Locate and open the Force Channel Internal Code Change task.
The Force Channel Internal Code Change window displays.
5. Select the channels with changes pending that you want to force a licensed
internal code update.
6. Click Force to forcibly update the licensed internal code of the channels with
changes pending.

Use the online Help for more information on forcibly updating internal code changes
pending.

Selective channel apply controls

Use this task to selectively define which OSA Express channels will have new
channel loads applied via a concurrent code update.

To select channel apply updates:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the Change Management task list.
4. Locate and open the Selective Channel Patch Control task.
The Selective Channel Patch Control window displays.
5. Select the channel type you want to apply updates.

Note: The selected channel type will require a configure off/on of each channel
for the selected channel type.
6. Click OK to perform the operation.
7. Click Cancel to exit the window without performing the operation.

Use the online Help for more information on defining clonable internal code levels.

Querying channel/crypto configure off/on pending

Use this task to select a condition to either:
v Query channel/cryptos currently requiring a configure off/on action in order to
perform a code load.
v Query channel/cryptos that will require a configure off/on action after the next
install and activate of a channel/crypto in order to perform a code load.

To query channel/cryptos that are configure off/on pending:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).

Chapter 11. Internal code change management 209

 2. Locate the CPC to work with.
3. Locate and open the Change Management task list.
4. Locate and open the Query Channel/Crypto Configure Off/On Pending task.
The Query Channel/Crypto Configure Off/On Pending window displays.
5. Click Current conditions to display a list of channel/cryptos that have configure
off/on current conditions pending.
6. Click Conditions in the next Inst/Act to display a list of channel/cryptos that
have configure off/on conditions pending in the next nondistruptive code load.
7. Click OK to return to the previous window.

Use the online Help for more information on reviewing pending channel and/or
cryptos to configure Off/On.

Querying internal code changes pending power-on reset

Use this task to select a condition to either:
v View internal code changes currently pending a power-on reset.
v View summary of internal code changes pending power-on reset.

To query internal code changes pending power-on reset:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the Change Management task list.
4. Locate and open the Query Internal Code Changes Pending Power-on Reset
task.
The Query Internal Code Changes Pending Power-on Reset window displays.
5. Select the condition you want to view from the window.
6. Click OK to view the selected condition.

Use the online Help for more information on querying internal code changes
pending power-on reset.

Querying coupling facility reactivations

This task allows you to query what coupling facility current code level changes need
to be deactivated and then reactivated in order to be applied to your CPC.

To query coupling facility reactivation:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).

210 Support Element Operations Guide

 2. Locate the CPC to work with.
3. Locate and open the Change Management task list.
4. Locate and open the Query Coupling Facility Reactivations task.
The Query Coupling Facility Reactivations window displays.
5. Review the list of coupling facility code level change to be reactivated.
6. Click OK to exit the window.

Use the online Help for more information on query coupling facility reactivations.

Specifying a concurrent upgrade sync point

Use this task to restrict specific internal code changes from being installed and
activated on the system. The concurrent upgrade of Engineering Changes requires
the system to transition from a specific code point to another specific code point.
This start point from and transition point to is called the sync point level. By setting
a sync point level, a higher level of the Engineering Changes data stream that
defines the sync points is prevented from being installed and activated.

To specify a sync point level for internal code changes :

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the Change Management task list.
4. Locate and open the Specify Concurrent Upgrade Sync Point task.
The Specify Concurrent Upgrade Sync Point window displays.
5. Enter the sync point level that you want the internal code changes restricted to.
6. Click Reset to remove the level restriction that was previously set.
7. Click OK to exit the window.

Performing an alternate support element action

This task allows you to perform the following actions for the primary/alternate
support elements:
v Forcing mirroring of data prior to switching support elements
v Querying whether a switch between support elements can take place
v Switching support elements.

One support element is used for the primary, the other as the alternate. The primary
support element is used for all hardware service. The alternate support element has
a special workplace window with limited tasks available.

Forcing an immediate mirroring of the primary support element to the

alternate support element
Notes:
1. Mirroring is suppressed if the support element has service status enabled.

Chapter 11. Internal code change management 211

 2. Mirroring is suppressed if the alternate support element was loaded with a
different CD-ROM from the primary support element.
3. Mirroring is suppressed if the alternate support element is fenced because of an
automatic switch.
4. The primary support element is scheduled for automatic mirroring at 10 a.m.
each day with a one-hour window for starting the operation. A record is added to
the support element’s event log to indicate the outcome of the operation.

This action mirrors support element data for the central processor complex (CPC).
Mirroring support element data copies it from the CPC’s primary support element to
its alternate support element. By regularly mirroring support element data, you can
help ensure that the alternate support element looks and works the same as the
primary support element in case you need to switch to the alternate support
element (for example, because of a hardware failure on the primary support
element).

Ordinarily, support element data is mirrored automatically each day or when you
install internal code changes through single step internal code changes, but you can
use this action to mirror support element data immediately, at any time, and for any
reason. The following are examples of when you would want to mirror support
element data instead of waiting for the automatic mirroring default times:
v Licensed internal code changes
v Input/output configuration data set (IOCDS) changes
v Hardware configuration definition (HCD) changes
v Dynamic I/O changes
v Dynamic load address and parameter changes
v LPAR data
v Profile changes
v Lockout disruptive tasks
v Scheduled operations

To mirror the primary support element data:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the Change Management task list.
4. Locate and open the Alternate Support Element task.
The Alternate Support Element window displays.
5. Select the Mirror the Primary Support Element data to the Alternate
Support Element radio button.
6. Click OK to perform the action.

Use the online Help for more information on the alternate support element actions.

Querying switch capabilities between support elements

The query switch capability action provides a quick check of the communication
path between the support elements, the status of the automatic switch action, and

212 Support Element Operations Guide

 their status. You can use this action before attempting a switch to the alternate
support element or for checking the status of the automatic switch action.

To query switch capabilities:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the Alternate Support Element task.
The Alternate Support Element window displays.
4. Select the Query Switch capabilities radio button.
5. Click OK to perform the action.

Use the online Help for more information on the alternate support element actions.

Switching to the alternate support element

You can use this action to switch to the alternate support element when the primary
fails. When the manual switchover action is started, the system checks that all
internal code levels are the same and that the CPC is activated. If the switch can
be made concurrently, the necessary files are passed between the support
elements, and the new primary support element is rebooted. If a disruptive switch is
necessary, the CPC will be deactivated before completing the switch.

There are several conditions, when in progress, that will prevent a switchover:
v A mirroring task
v An internal code update
v A hard disk restore
v An engineering change.

The system automatically attempts a switchover for the following conditions:

v Primary support element has a serious hardware problem
v Primary support element detects a CPC status check
v Alternate support element detects a loss of communications to the primary over
both the service network and the customer’s LAN.

Note: To disable the automatic switchover, See “Enabling automatic support

element switchover” on page 251.

To switch to the alternate support element:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open the Alternate Support Element task.

Chapter 11. Internal code change management 213

 The Alternate Support Element window displays.
4. Select the Switch the Primary Support Element and the Alternate Support
Element radio button.
5. Click OK to perform the action.

Use the online Help for more information on the alternate support element actions.

214 Support Element Operations Guide

Chapter 12. Processor and storage operations
This section describes tasks from the CP Toolbox task list you can use to monitor
and control the operation and storage of specific central processors (CPs) in the
central processor complex (CPC).

To launch the tasks from the CP Toolbox task list using the classic style user
interface, see Chapter 2, “Using the tree style user interface,” on page 9, or if you
are using the tree style user interface, see Chapter 3, “Using the classic style user
interface,” on page 35.

Processor operations: start and stop

Start and stop are processor operations you can use, together, to control whether a
processor can process instructions. If you have experience using other systems,
you may have used START and STOP commands or Start and Stop keys to start
and stop a processor.

You can use the support element workplace to start and stop any eligible processor.
Eligible processors include:
v Physical processors that support the image of a central processor complex
(CPC).
v Logical processors that support logical partitions activated in operating modes
other than coupling facility mode.

Stopping processors

Follow your local procedures for determining when to stop processors. Generally,
stopping processors for an image is effective only when the image and processors
are operating.

To stop processors for an image:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user roles (see “Establishing a support element
console session from a Hardware Management Console” on page 3).
2. Locate CPs you want to stop.
3. Locate and open the CP Toolbox task list.
4. Locate and start the Stop task.
This immediately performs the operation; the processor is stopped.

Starting processors

Follow your local procedures for determining when to start processors. But
generally, starting processors for an image is most effective after you’ve used the
Stop task to stop processors for the image.

To start processors for an image:

© Copyright IBM Corp. 2008 215

 1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
2. Locate the CPs you want to start.
3. Locate and open the CP Toolbox task list.
4. Locate and start the Start task.
This immediately performs the operation; the processor is started and resumes
operating.

Displaying or altering data in processor storage

A processor stores data in the following storage locations:
v Registers, which are special-purpose storage locations:
– Program status word (PSW)
– General purpose registers
– Control registers
– Floating point registers
– Access registers
– Prefix register
v Main storage locations:
– Real storage
– Real storage key
– Primary virtual storage
– Secondary virtual storage
– Absolute storage
– Home virtual storage
– Virtual storage identified using access registers

Displaying or altering data in processor storage locations typically is done only by

system programmers with experience in interpreting and altering the data. Follow
your local procedures for determining when to display or alter data. You can use the
support element workplace to display or alter the data in storage locations used by
any eligible processor. Eligible processors include:
v Physical processors that support the image of a central processor complex
(CPC).
v Logical processors that support the images of logical partitions activated in
operating modes other than coupling facility mode.

To display or alter data in processor storage:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate the CPs you want to work with.

216 Support Element Operations Guide

 3. Locate and open the CP Toolbox task list.
4. Locate and open the Display or Alter task.
5. Use the Display or Alter window controls to display or alter the data in the
processor’s storage locations.
Use the online Help for the window for more information about using its controls
to display or alter the data.

Restarting a processor
A restart or PSW restart is a processor operation you can use to restart a
processor. If you have experience using other systems, you may have used a
RESTART command or Restart key to restart a processor.

Restarting a processor typically is done during a software error recovery procedure.

Follow your local procedures for determining when to restart a processor. You can
use the support element workplace to restart any eligible processor. Eligible
processors include:
v Physical processors that support the image of a central processor complex
(CPC).
v Logical processors that support the images of logical partitions activated in
operating modes other than coupling facility mode.

To restart a processor:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
2. Locate the CPs you want to work with.

Note: restarting a processor on an image can be considered disruptive. If the

CPC image is locked, unlock it. See “Setting object locking for disruptive
tasks on an object” on page 54.
3. Locate and open the CP Toolbox task list.
4. Locate and open the PSW Restart task.
5. Select a reason for restarting the processor, then click OK to continue.
6. Review the information on the PSW Restart Confirmation window to verify the
processor that you will restart is the one you want.
7. If the information is correct, click OK to perform the restart.
This begins the restart; a message displays when it is completed.
8. Click OK to close the message when the restart completes successfully.
Otherwise, if the restart does not complete successfully, follow the directions in
the message to determine the problem and how to correct it.

Interrupting a processor
An interrupt is a processor operation you can use to present an external interruption
to a processor. If you have experience using other systems, you may have used an
IRPT command or an Irpt key to interrupt a processor.

Chapter 12. Processor and storage operations 217

 Follow your local procedures for determining when to interrupt a processor. You can
use the support element workplace to interrupt any eligible processor. Eligible
processors include:
v Physical processors that support the image of a central processor complex
(CPC).
v Logical processors that support the images of logical partitions activated in
operating modes other than coupling facility mode.

To interrupt a processor:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
2. Locate the CPs you want to work with.
3. Locate and open the CP Toolbox task list.
4. Locate and start the Interrupt task.
This immediately performs the operation; an interrupt request is generated for
the processor.

Stopping CPs on address matches or events

The processing and input/output (I/O) activity of central processors (CPs) is
reflected in how the activity affects the contents of main storage, the status of I/O
devices, and the contents of program status word (PSW). That is, CP activity is
indicated by the conditions of main storage, I/O devices, and the PSW.

Monitoring these conditions provides another means for monitoring and controlling
CP activity. By setting an address match or event that identifies the specific
condition you want to watch for, all CPs are automatically stopped when the actual
condition of main storage, I/O devices, or the PSW matches the condition you set.
You can set the following condition for stopping CPs:
CP address match
Set for monitoring main storage and stopping all CPs when a CP accesses
a specific main storage location while processing non-I/O operations.

Follow your local procedures for determining when to set conditions for stopping
CPs. You can use the support element workplace to set conditions for stopping
CPs.

To set conditions for stopping CPs:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer user role (see “Establishing a
support element console session from a Hardware Management Console” on
page 3).
2. Locate the CPs you want to work with.

218 Support Element Operations Guide

 3. Locate and open the CP Toolbox task list.
4. Locate and open the Stop on CP Address Match task.
The window displays controls for setting the conditions that you want to stop the
CP.
Use the online Help for the window for information about using its controls to set
conditions for stopping the CP.

Performing store status

Store status is a processor operation you can use to store the contents of a
processor’s registers, excluding the time-of-day (TOD) clock, in assigned storage
locations. The contents of the following registers are stored by the store status
operation:
v CPU timer
v Clock comparator
v Current program status word (PSW)
v Access registers 0-15
v Prefix
v Floating point registers 0-6
v General registers 0-15
v Control registers 0-15

If you have experience using other systems, you may have used a store-status key
to initiate the store status operation for a processor.

Follow your local procedures for determining when to perform the store status
operation. You can use the support element workplace to perform the store status
operation for any eligible processor. Eligible processors include:
v Physical processors that support the image of a central processor complex
(CPC).
v Logical processors that support the images of logical partitions activated in
operating modes other than coupling facility mode.

To perform the store status operation:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
2. Locate the CPs you want to work with.
3. Locate and open the CP Toolbox task list.
4. Locate and start the Store Status task.
A message displays when it is completed.
5. Click OK to close the message when the operation completes successfully.
Otherwise, if the operation does not complete successfully, follow the directions
in the message to determine the problem and how to correct it.

Chapter 12. Processor and storage operations 219

220 Support Element Operations Guide
Chapter 13. Channel operations
This section describes tasks from the Channel Operations task list you can use to
monitor and control the operation of specific channels, identified with a physical
channel identifier (PCHID). A channel path (CSS.CHPID) is associated with a
physical channel identifier (PCHID).

To launch the tasks from the Channel Operations task list using the classic style
user interface, see Chapter 2, “Using the tree style user interface,” on page 9, or if
you are using the tree style user interface, see Chapter 3, “Using the classic style
user interface,” on page 35.

Configuring channel paths on or off

Configure on and configure off are channel operations you can use to control
whether channel paths (CSS.CHPIDs) are online or on standby in the active
input/output (I/O) configuration. You can use the Channel Operations task list to
configure channel paths (CSS.CHPIDs), associated with a specific physical channel
identifier (PCHID), on and off. A channel path is identified with a CSS.CHPID. The
CSS.CHPID is a single-digit number that identifies the channel subsystem followed
by a decimal point followed by a two-digit number that identifies the channel path.
See Chapter 14, “CHPID operations,” on page 231 for more information on
configuring CSS.CHPIDs on and off.

To use the workplace to configure channel path’s on or off:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3). The CPC must be
power-on reset.
2. Locate the Channel, identified with a physical channel identifier (PCHID), that
you want to configure on or off.
3. Locate and open the Channel Operations task list.
4. Locate and open the Configure On/Off task.
The Configure On/Off window displays. The window lists the CSS.CHPIDs,
current state, target state, and messages associated with the channel you
selected.
5. Initially, each channel’s current state and target state are the same. Use the
window’s controls to change the target states of the channel paths you want to
configure on or off:
v If the current state of a channel path is Online, toggle its target state to
Standby if you want to configure off the channel path.
v If the current state of a channel path is Standby, toggle its target state to
Online if you want to configure on the channel path.

Note: If you attempt to change the target state of a channel path that cannot be
configured on or off, a message is displayed in the Messages list column

© Copyright IBM Corp. 2008 221

 to indicate changing the changing path is not allowed. Double-click on
the message for more information about why the channel path state
cannot be changed.
6. When you finish changing the target states of the channel path you want to
configure on or off, click Apply to make each channel path’s new target state its
current state.

Configuring reconfigurable channel paths in LPAR mode

When the central processor complex (CPC) is power-on reset, the active
input/output configuration data set (IOCDS) determines which logical partition each
channel path is assigned to and whether any of the channel paths are
reconfigurable. Ordinarily, channel paths assigned to a single logical partition are
available only to that logical partition. That is, the channel paths cannot be
configured on to other logical partitions, even after they are configured off from their
assigned logical partition. Channel paths assigned to a single logical partition and
defined as reconfigurable can be reassigned to other logical partitions. That is,
reconfigurable channel paths can be configured off from their assigned logical
partitions and configured on to other logical partitions.

The logical partition to which a reconfigurable channel path is currently assigned is

referred to here as the owning logical partition. The logical partition that you want to
reassign the channel path is referred to here as the target logical partition.
Reassigning the channel path requires:
1. Configuring off the channel path from the owning logical partition, if the channel
path is currently configured on.
2. Releasing the channel path from the owning logical partition, if the channel path
is currently isolated.
3. Configuring on the channel path to the target logical partition.

It is recommended you use operating system facilities rather than the support
element workplace, whenever possible, to perform the steps necessary to reassign
reconfigurable channel paths. However, if you must use the workplace, you can
either:
v Perform each step for multiple channel paths:
1. Use the Configure On/Off task to configure off the channel paths that are
online. For instructions, see “Configuring channel paths on or off” on page
221.
2. Use the Release task to release the channel paths that are isolated. For
instructions, see “Releasing reconfigurable channel paths.”
3. Use operating system facilities to configure on the channel paths to other
logical partitions.
v Or perform all steps at once for a single channel path by using the Reassign
Channel Path task. For instructions, see “Reassigning reconfigurable channel
paths” on page 223.

Releasing reconfigurable channel paths

Release is a channel operation you can use to free reconfigurable channel paths
(CSS.CHPIDs), associated with a physical channel identifier (PCHID), from their
assignment to isolated logical partitions.

Channel paths that are both reconfigurable and isolated are eligible for being
released. You can use the Channel’s Work Area to locate reconfigurable channel

222 Support Element Operations Guide

 paths assigned to isolated logical partitions. The icon label for any reconfigurable
channel path displays Reconfigurable and either Isolated or Not isolated to
indicate whether it is assigned to an isolated logical partition. For more information
on releasing channel paths, see “Releasing reconfigurable channel paths” on page
232

To release channel paths:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
2. The central processor complex (CPC) must be power-on reset.
3. The channel paths must be defined as reconfigurable in the active input/output
(I/O) configuration.
4. The channel paths must be assigned to isolated logical partitions.
5. The channel paths must be configured off.
6. Locate the reconfigurable channel paths you want to release.
7. Locate and open the Channel Operations task list.
8. Locate and open the Release task.
9. Click Release from the confirmation window to confirm your request to release
the selected channels.
This releases the channel paths.

Note: Upon configuring off and releasing reconfigurable channel paths from
isolated logical partitions, you must use operating system facilities to
configure them on to other logical partitions.

Reassigning reconfigurable channel paths

Reassign is a channel operation you can use to perform at once all the steps
necessary to reassign a reconfigurable channel path from its owning logical partition
to another logical partition:
1. Configuring off the channel path from its owning logical partition, if necessary.
2. Releasing the channel path, if necessary.
3. Configuring on the channel path to the other logical partition.

Any channel path that is reconfigurable is eligible for being reassigned. The icon
label for a reconfigurable channel path displays Reconfigurable.

To reassign a channel path:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system
programmer, or service representative user role (see “Establishing a support
element console session from a Hardware Management Console” on page 3).

Chapter 13. Channel operations 223

 2. The central processor complex (CPC) must be power-on reset.
3. The channel paths must be defined as reconfigurable in the active input/output
(I/O) configuration.
4. Locate one reconfigurable channel, identified with a physical channel identifier
(PCHID), that you want to reassign.
5. Locate and open the Channel Operations task list.
6. Locate and open the Reassign Channel Path task.
The Reassign Channel Path window identifies the logical partition that the
selected channel path is currently assigned, and lists the logical partitions to
which it can be reassigned.
7. Select from the list the logical partition that you want to reassign the channel
path, then click Reassign.
The Select a Partition window displays showing the channel path that is
currently assigned, the owning partition, and a list of logical partitions from
which you can select to reassign the channel path.
8. Click the logical partition in the Target Partition window list to which you want
the channel path reassigned.
9. Click Reassign.
The Confirm the Action window is displayed.
10. Click Reassign from the confirmation window to confirm your request to
reassign the selected channel path to the target logical partition.
This reassigns the channel path to the logical partition.

Note: If the target logical partition is not activated, the channel path is still
configured on, but its status does not immediately become Online. The
status remains Standby instead, and becomes Online only when the
target logical partition is activated.

Use the online Help for more information about using the window to reassign the
channel path.

Setting service on or off for channels

Service on and Service off are channel operations you can use to control whether
channels, identified with physical channel identifiers (PCHIDs) are on standby in, or
reserved from, the active input/output (I/O) configuration:
v A channel is on standby while service is set off. It is in the active I/O
configuration but it cannot be used until it is configured on. It will remain in the
active I/O configuration until service is set on.
v A channel is reserved while service is on. It is not in the active I/O configuration
and cannot be used. It will remain out of the active I/O configuration until service
is set off.

Setting service on for a channel, which removes it from the active I/O configuration,
allows running diagnostic tests on the channel without disturbing other channels
being used by the system. Setting service on for a channel can be used also to
remove failing channels from the I/O configuration so subsequent power-on resets
will not attempt to initialize the failing channels.

224 Support Element Operations Guide

 If you have experience using other systems, setting service on or off for channels
may have been referred to as taking channels in and out of single channel service
(SCS), for which you may have used an SCS command with IN and OUT
parameters.

To set service on and off for a channel:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3). The CPC must be
power-on reset.
2. Locate the Channel, identified with a physical channel identifier (PCHID), that
you want to set service on or off.
3. Locate and open the Channel Operations task list.
4. Locate and open the Service On/Off task.
5. Initially, each channel’s current state and target state are the same. Use the
Service On/Off window controls to change the target states of the channel that
you want to set the service state on or off:
v If the current state of a channel is Reserved, toggle its target state to
Standby if you want to set service off for the channel.
v If the current state of a channel is Standby, toggle its target state to
Reserved if you want to set service on for the channel.
If you attempt to change the target state of a channel that cannot have service
set on or off, a message is displayed in the Messages list column to indicate
changing the channel’s state is not allowed. Double-click on the message for
more information about why the channel state cannot be changed.
6. When you finish changing the target states of the channels for which you want
to set service on or off, click Apply to make each channel’s new target state its
current state.

Setting the channel LED on

Show LED is a channel operation you can use to find the location of the jack and
card slot in a cage. The light emitting diode (LED) is located below each card slot
and near each jack in the cages that support attachment hardware. You can use
this task for channel problem determination.

To set the show LED on:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3). The CPC must be power-on reset.
2. Locate the Channel, identified with a physical channel identifier (PCHID), that
you want the LED on for.
3. Locate and open the Channel Operations task list.
4. Locate and open the Show LED task.

Chapter 13. Channel operations 225

 The Show LED window displays the PCHID for the LED that is on.
5. Click OK to turn the LED off.

Performing channel problem determination

You can use the Channels Work Area to determine the state and status of specific
channel paths in the input/output (I/O) configuration of the central processor
complex (CPC). The label for each channel path’s icon includes its physical channel
identifier (PCHID), state, and status. When you need more detailed information, you
can use the support element workplace to perform channel problem determination.
Perform channel problem determination to get the following types of information,
referred to here as problem determination information, for a channel path:
v Channel information
v Subchannel data
v Control unit header
v Paths to a device
v Device status
v Serial link status

If you have experience using other systems, you may have performed input/output
(I/O) problem determination to get similar information for a channel path.

To perform channel problem determination:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3). The CPC must be
power-on reset and the image must be activated.
2. Locate the Channels that you want to perform channel problem determination.
3. Locate and open the Channel Operations task list.
4. Locate and open the Channel Problem Determination task.
The Partition Selection window lists the logical partitions which problem
determination can be performed.
5. Select from the list the logical partition that you want to perform problem
determination.
6. Click OK.
The Channel Problem Determination window lists the types of problem
determination information you can get for the selected channel.

Note: The channel you selected to start the task is the task’s initial input. One
or more windows are displayed if additional input is needed to display the
type of information you want.
7. Select the radio button beside the type of problem determination information you
want, then click OK.
Follow the instructions on each subsequent window, if any, to provide the
additional input needed to display the type of information you selected.
Upon providing the additional input, if any, the channel’s problem determination
information is displayed.

226 Support Element Operations Guide

Identifying channel definition errors
Performing a power-on reset of the central processor complex (CPC) includes
defining its input/output (I/O) configuration and allocating its storage. A channel
definition error occurs when either:
v The definition of a channel defined in the I/O configuration does not match the
characteristics of the channel hardware installed in the CPC.
v The channel type of a channel defined in the I/O configuration is incompatible
with the CPC’s storage allocation.

You can use the Channels Work Area to locate channels that have definition errors.
The icon label for any channel that has a definition error displays Definition error
for its status. After locating a channel that has a definition error, perform channel
problem determination to determine the channel’s exact definition error.

To determine a channel’s exact definition error:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
2. The CPC must be power-on reset, the image must be activated, and the status
displayed for the channel must be Definition error.
3. Locate and open the Channel Operations task list.
4. Locate and open the Channel Problem Determination task for one channel
that has a definition error. See “Performing channel problem determination” on
page 226 for instructions for starting the task.
The Channel Problem Determination window lists the types of problem
determination information you can get for the selected channel.
5. Select the Analyze Channel Information radio button, then click OK.
This displays the Analyze Channel Information window. The window displays
channel information for the selected channel path.
6. Click Error details.
This displays a message that describes the selected channel’s exact definition
error.

Note: Error details is not available if the status displayed for the selected
channel is not Definition error.

Working with the Open Systems Adapter (OSA)-Express

The Open Systems Adapter (OSA)-Express is an integrated hardware feature that
provides direct connection to clients on Local Area Networks (LAN). Each
OSA-Express channel can be shared among all images in a single CSS of the
server. This is referred to as the Multiple Image Facility (MIF), sharing of channels
across logical partitions.

For more detailed information on OSA-Express, refer to zSeries Open Systems

Adapter-Express Customer’s Guide and Reference.

An OSA-Express can be a channel type of OSE, OSD, or OSC. An OSC channel is

an OSA Integrated Console Controller (OSA-ICC). For more information on
OSA-ICC, refer to the zSeries Open Systems Adapter-Express Integrated Console
Controller User’s Guide. For OSN, refer to the CDLC Implementation User’s Guide,
SC31-6872.

Chapter 13. Channel operations 227

Using advanced facilities for OSA-Express channels
You can use the Support Element workplace to open a facility for monitoring,
operating, and customizing an OSA-Express channel. To work with an OSA-Express
channel:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3). The CPC must be power-on reset.
2. Locate the OSA-Express channel that you want to work with. See “Locating
channels” on page 13 when using the tree style user interface or “Locating
channels” on page 42 when using the classic style user interface.
3. Locate and open the Channel Operations task list.
4. Locate and open the Advanced Facilities task.
5. The Advanced Facilities window displays a list of actions you can take for the
selected channel path:
6. Click the function of your choice:
View code level
Click this to display the channel ID, channel type, and code level for the
channel card.
Card Trace/Log/Dump Facilities
Click this to select any of the following actions:
v Display or alter trace mask
v Read trace buffer
v Read log buffer
v Read MIB buffer
v OSA-Express Host Network Traffic Analyzer Authorization...
Card specific advanced facilities
Click this to perform any of the following actions:
v Query port status
v View port parameters
v View code level
v Display or alter MAC address
v Enable/disable ports
v Run port diagnostics
v Set card mode
v Display client connections
v Display active sessions configuration
v Display active server configuration
v Panel configuration options
v Manual configuration options
v Activate configuration
v Display activate configuration errors
v Debug utilities
OSA reset to defaults...
Click this to reset OSA to the default configuration.
7. Select the action that you want to start, then click OK.
8. The next window that displays depends on your selection

228 Support Element Operations Guide

 v For the Advanced Facilities window, select one of the tasks, then click OK.
v For the View Code Level window, view the code level for the card, then click
OK.
v For the Card Trace/Log/Dump Facilities window, select one of the tasks, then
click OK.
v For the OSA Reset to Default Configuration window, click Yes to reset OSA
to the default configuration.

Use the online Help to get additional information for working with OSA Advanced
Facilities.

Chapter 13. Channel operations 229

230 Support Element Operations Guide
Chapter 14. CHPID operations
This section describes tasks from the CHPID Operations task list you can use to
monitor and control the operation of specific channel paths with channel path
identifiers (CSS.CHPIDs) defined in the input/output (I/O) configuration of the
central processor complex (CPC). The CSS.CHPID is a single-digit number that
identifies the channel subsystem followed by a decimal point followed by a two-digit
number that identifies the channel path.

To launch the tasks from the CHPID Operations task list using the classic style
user interface, see Chapter 2, “Using the tree style user interface,” on page 9, or if
you are using the tree style user interface, see Chapter 3, “Using the classic style
user interface,” on page 35.

Configuring channel paths on or off

Configure on and configure off are CHPID operations you can use to control
whether channel paths are online or on standby in the active input/output (I/O)
configuration:
v A channel path is online while configured on. It is in the active I/O configuration
and it can be used.
v A channel path is on standby while configured off. It is in the active I/O
configuration but it cannot be used until it is configured on.

If you have experience using other systems, you may have used a CHPID
command with ON and OFF parameters to configure channel paths on and off.

You can use the support element workplace to configure channel paths on and off.
However, operating systems will not be notified when you use the workplace to
configure channel paths on or off. For example, if you configure off a channel path,
the operating system running in any image that owns or shares the channel path is
not notified, and the next operation from the operating system to the channel path
will cause an error. It is recommended you use operating system facilities rather
than the support element workplace, whenever possible, to configure channel paths
on and off.

To use the workplace to configure channel paths on or off:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3). The CPC must be
power-on reset.
2. Locate the Channel Paths you want to configure on or off. See “Locating
channels” on page 13 for the tree style user interface or “Locating channels” on
page 42 for the classic style user interface.
3. Locate and open the CHPID Operations task list.
4. Locate and open the Configure On/Off task.
The Configure On/Off window displays. The window lists the CSS.CHPID,
current state, target state, and messages for each channel path you selected.
© Copyright IBM Corp. 2008 231
 5. Use the window’s controls to change the target states of the channel paths you
want to configure on or off:
v If the current state of a channel path is Online, toggle its target state to
Standby if you want to configure off the channel path.
v If the current state of a channel path is Standby, toggle its target state to
Online if you want to configure on the channel path.

Note: If you attempt to change the target state of a channel path that cannot be
configured on or off, a message is displayed in the Messages list column
to indicate changing the channel path’s state is not allowed. Double-click
on the message for more information about why the channel path state
cannot be changed.
6. When you finish changing the target states of the channel paths you want to
configure on or off, click Apply to make channel path’s new target state its
current state.

Releasing reconfigurable channel paths

Release is a CHPID operation you can use to free reconfigurable channel paths
from their assignment to isolated logical partitions.

The active input/output configuration data set (IOCDS) determines whether channel
paths are reconfigurable, and which logical partition each channel path is assigned
to. Each logical partition’s security settings determine whether it is isolated. A logical
partition’s initial security settings are set by the activation profile used to activate it.
Afterwards, the Change LPAR Security task can be used to change the settings.
For more information, see “Logical partition security” on page 165.

Reconfigurable channel paths assigned to an isolated logical partition do not

become available to other logical partitions when they are configured off. Releasing
such channel paths will make them available to other logical partitions.

Channel paths that are both reconfigurable and isolated are eligible for being
released. You can use the CHPID’s Work Area to locate reconfigurable channel
paths assigned to isolated logical partitions. The icon label for any reconfigurable
channel path displays Reconfigurable and either Isolated or Not isolated to
indicate whether it is assigned to an isolated logical partition.

To release channel paths:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
2. The central processor complex (CPC) must be power-on reset.
3. The channel paths must be defined as reconfigurable in the active input/output
(I/O) configuration.
4. The channel paths must be assigned to isolated logical partitions.
5. Locate the reconfigurable Channel Paths you want to release.
6. Locate and open the CHPID Operations task list.

232 Support Element Operations Guide

 7. Locate and open the Release task.
8. Click Release from the confirmation window to confirm your request to release
the selected channel paths.
This releases the channel paths.

Note: Upon configuring off and releasing reconfigurable channel paths from
isolated logical partitions, you must use operating system facilities to
configure them on to other logical partitions.

Setting the channel LED on

Show LED is a CHPID operation you can use to find the location of the jack and
card slot in a cage. The light emitting diode (LED) is located below each card slot
and near each jack in the cages that support attachment hardware. You can use
this task for channel problem determination.

To set the show LED on:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3). The CPC must be power-on reset.
2. Locate the Channel Path you want the LED on for.
3. Locate and open the CHPID Operations task list.
4. Locate and open theShow LED task.
The Show LED window displays the CSS.CHPID for the LED that is on.
5. Click OK to turn the LED off.

Performing channel problem determination

You can use the CHPID’s Work Area to determine the state and status of specific
channel paths in the input/output (I/O) configuration of the central processor
complex (CPC). The label for each channel path’s icon includes its CSS.CHPID,
state, and status. When you need more detailed information, you can use the
support element workplace to perform channel problem determination. Perform
channel problem determination to get the following types of information, referred to
here as problem determination information, for a channel path:
v Channel information
v Subchannel data
v Control unit header
v Paths to a device
v Device status
v Serial link status

If you have experience using other systems, you may have performed input/output
(I/O) problem determination to get similar information for a channel path.

To perform channel problem determination:

Chapter 14. CHPID operations 233

 1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
2. The CPC must be power-on reset and the image must be activated.
3. Locate one target channel path for which you want to perform channel problem
determination.
4. Locate and open the CHPID Operations task list.
5. Locate and open the Channel Problem Determination task.
The Channel Problem Determination window lists the types of problem
determination information you can get for the selected channel path.

Note: The CSS.CHPID of the channel path you selected to start the task is the
task’s initial input. One or more windows are displayed if additional input
is needed to display the type of information you want.
6. Select the radio button beside the type of problem determination information you
want, then click OK.
Follow the instructions on each subsequent window, if any, to provide the
additional input needed to display the type of information you selected.
Upon providing the additional input, if any, the channel path’s problem
determination information is displayed.

Identifying channel definition errors

Performing a power-on reset of the central processor complex (CPC) includes
defining its input/output (I/O) configuration and allocating its storage. A channel
definition error occurs when either:
v The definition of a channel defined in the I/O configuration does not match the
characteristics of the channel hardware installed in the CPC.
v The channel type of a channel defined in the I/O configuration is incompatible
with the CPC’s storage allocation.

You can use the CHPIDs Work Area to locate channel paths that have definition
errors. The icon label for any channel path that has a definition error displays
Definition error for its status. After locating channel path that has a definition error,
perform channel problem determination to determine the channel path’s exact
definition error.

To determine a channel path’s exact definition error:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
2. The CPC must be power-on reset, the image must be activated, and the status
displayed for the channel path must be Definition error.
3. Locate and open the CHPID Operations task list.
4. Locate and open the Channel Problem Determination task for one channel
path that has a definition error. See “Performing channel problem determination”
on page 226 for instructions for starting the task.

234 Support Element Operations Guide

 The Channel Problem Determination window displays. The window lists the
types of problem determination information you can get for the selected channel
path.
5. Select the Analyze Channel Information radio button, then click OK.
This displays the Analyze Channel Information window. The window displays
channel information for the selected channel path.
6. Click Error details.
This displays a message that describes the selected channel path’s exact
definition error.

Note: Error details is not available if the status displayed for the selected
channel path is not Definition error.

Enabling NPIV mode

Use this task to enable N Port Identifier Virtualization (NPIV) mode for selected
channel paths. When NPIV mode is enabled for selected channel paths, the system
provides a virtual FCP channel for each S/390 device definition for a FCP channel
in the active Input/Output configuration.

Note: The channel paths must be configured offline to enable NPIV mode.

To set the NPIV configuration:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user mode (see “Establishing a support element
console session from a Hardware Management Console” on page 3).
2. Locate the CPC to work with.
3. Locate and open CHPID Operations task list.
4. Locate and open the FCP NPIV Mode On/Off task.
The NPIV Mode On/Off window displays.
5. Click Select All to select all the listed channel paths to enable for NPIV mode.
6. Click Deselect All to deselect all the listed channel paths that are enabled for
NPIV mode.
7. Click Apply to make the changes.

Use the online Help for more information on enabling the NPIV mode.

Chapter 14. CHPID operations 235

236 Support Element Operations Guide
Chapter 15. Crypto service operations
This section describes tasks from the Crypto Service Operations task list you can
use to monitor and control the operation of specific crypto defined in the
configuration of the central processor complex (CPC).

To launch the tasks from the Crypto Service Operations task list using the classic
style user interface, see Chapter 2, “Using the tree style user interface,” on page 9,
or if you are using the tree style user interface, see Chapter 3, “Using the classic
style user interface,” on page 35.

Configuring crypto on or off

Configure on and configure off are crypto service operations you can use to control
whether crypto are online or standby in the active configuration:
v A crypto is online while configured on. It is in the active configuration and it can
be used.
v A crypto is standby while configured off. It is in the active configuration but it
cannot be used until it is configured on.

You can use the support element workplace to configure crypto on and off.
However, operating systems will not be notified when you use the workplace to
configure channel paths on or off. For example, if you configure off a crypto, the
operating system running in any image that owns or shares the crypto is not
notified, and the next operation from the operating system to the crypto causes an
error. When using z/OS operating environment, deactivate the crypto through ICSF
before configuring off crypto.

Note: To determine when crypto initialization has completed after a configure on of

a crypto, see “Checking status for the Crypto Express2 feature” on page 190

To configure a crypto on or off:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3). The CPC must be
power-on reset and the logical partitions must be activated.
2. Locate the Crypto you want to configure on or off.
3. Locate and open the Crypto Service Operations task list.
4. Locate and open the Configure On/Off task.
The Configure On/Off window displays. The window lists the crypto, current
state, target state, and messages for each crypto you selected.
5. Initially, each crypto’s current state and target state are the same. Use the
window’s controls to change the target states of the crypto you want to
configure on or off:
v If the current state of a crypto is Online, toggle its target state to Standby if
you want to configure off the crypto.

© Copyright IBM Corp. 2008 237

 v If the current state of a crypto is Standby, toggle its target state to Online if
you want to configure on the crypto path.

Note: If you attempt to change the target state of a crypto that cannot be
configured on or off, a message is displayed in the Messages list column
to indicate changing the crypto state is not allowed. Double-click on the
message for more information about why the crypto state cannot be
changed.
6. When you finish changing the target states of the crypto you want to configure
on or off, click Apply to make each crypto new target state its current state.

Setting service on or off for crypto

Service on and Service off are crypto service operations you can use to remove
from or add back in crypto, identified with physical channel identifiers (PCHIDs), in
the active configuration:
v A crypto is standby while service is set off. It is in the active configuration but it
cannot be used until it is configured on. It will remain in the active configuration
until service is set on.
v A crypto is reserved while service is on. It is not in the active configuration and
cannot be used. It will remain out of the active configuration until service is set
off.

Setting service on for a crypto, which removes it from the active configuration,
allows running diagnostic tests on the crypto without disturbing other crypto being
used by the system. Setting service on for a crypto can be used also to remove
failing crypto from the configuration so subsequent power-on resets and partition
activations will not attempt to initialize the failing of crypto.

If you have experience using other systems, setting service on or off for crypto may
have been referred to as taking channels in and out of single channel service
(SCS), for which you may have used an SCS command with IN and OUT
parameters.

You can use the support element workplace to set service on and off for crypto.

To set crypto service on and off:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3). The CPC must be
power-on reset.
2. Locate the Crypto that you want to set service on or off.
3. Locate and open the Crypto Service Operations task list.
4. Locate and open the Service On/Off task.
5. Initially, each crypto’s current state and target state are the same. Use the
Service On/Off window controls to change the target states of the crypto that
you want to set the service state on or off:

238 Support Element Operations Guide

 v If the current state of a crypto is Reserved, toggle its target state to Standby
if you want to set service off for the crypto.
v If the current state of a crypto is Standby, toggle its target state to Reserved
if you want to set service on for the crypto.
If you attempt to change the target state of a crypto that cannot have service
set on or off, a message is displayed in the Messages list column to indicate
changing the crypto state is not allowed. Double-click on the message for more
information about why the crypto state cannot be changed.
6. When you finish changing the target states of the crypto that you want to set
service on or off, click Apply to make each crypto’s new target state its current
state.

Performing crypto problem determination

You can use the Crypto Work Area to determine the state and status of specific
crypto in the central processor complex (CPC). The label for each crypto’s icon
includes it crypto, state, and status. When you need more detailed information, you
can use the support element workplace to perform problem determination. Perform
problem determination to get information for a crypto.

To perform crypto problem determination:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3). The CPC must be
power-on reset and the partition must be activated.
2. Locate the image that owns or shares the crypto for which you want to perform
crypto problem determination. One or more images is created and the active
configuration is established during a power-on reset of the CPC.
3. Locate the Crypto Service Operations task list.
4. Locate and open the Channel Problem Determination task.
The Channel Problem Determination window lists the Analyze Channel
Information problem determination you can get for the selected crypto.
5. Select the radio button beside the type of problem determination information,
then click OK.
Follow the instructions on each subsequent window, if any, to provide the
additional input needed to display the type of information you selected.
Upon providing the additional input, if any, the crypto’s problem determination
information is displayed.

Identifying crypto definition errors

Performing a power-on reset of the central processor complex (CPC) includes
defining its input/output (I/O) configuration and allocating its storage. Cryptos are
not defined in the I/O configuration, but are defined when they are installed. A
crypto definition error occurs when:
v The definition of a crypto conflicts with the definition of a channel in the I/O
configuration.

Chapter 15. Crypto service operations 239

 You can use the Crypto Work Area to locate crypto that have definition errors. The
icon label for any crypto that has a definition error displays Definition error for its
status. After locating crypto that have a definition error, perform crypto problem
determination to determine the crypto’s exact definition error.

To determine a crypto’s exact definition error:

1. Log onto the support element on the hardware management console through
Single Object Operations in advanced operator, system programmer, or
service representative user mode (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
2. The CPC must be power-on reset, the image must be activated, and the status
displayed for the crypto must be Definition error.
3. Locate and open the Crypto Service Operations task list.
4. Locate and open the Channel Problem Determination task.
The Channel Problem Determination window lists the types of problem
determination information you can get for the selected crypto.
5. Select the Analyze Channel Information radio button, then select OK.
The Analyze Channel Information window displays. The window displays
channel information for the selected crypto.
6. Click Error details.
This displays a message that describes the selected crypto’s exact definition
error.

Note: Error details is not available if the status displayed for the selected
crypto is not Definition error.

Using advanced facilities for crypto

You can use the support element workplace to open a facility for monitoring,
operating, and customizing a crypto. To work with a crypto:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
role (see “Establishing a support element console session from a Hardware
Management Console” on page 3). The CPC must be power-on reset.
2. Locate the Crypto that you want to work with.
3. Locate and open the Crypto Service Operations task list.
4. Locate and open the Advanced Facilities task.
5. The Standard Channel Advanced Facilities window displays a list of actions
you can take for the selected crypto. The list of tasks include:
v View code level
v Card Trace/Log/Dump Facilities
6. Select the task that you want to start, then click OK.

240 Support Element Operations Guide

Chapter 16. Console actions
This section describes the tasks from the Console Actions task list that you can
use to access information, monitor and operate the support element console, and
customize console settings.

To launch the Console Actions task using the classic style user interface, see
Chapter 2, “Using the tree style user interface,” on page 9, or if you are using the
tree style user interface, see Chapter 3, “Using the classic style user interface,” on
page 35.

Assigning domain security to your support element console

If you want to customize domain security, use this task to establish and maintain
different domains for multiple Hardware Management Consoles and support
element consoles attached to the same local area network (LAN). Ordinarily, to add
or move a CPC from a domain is done from the Hardware Management Console,
but this can be accomplished from the support element console.

The domain name and password of the console authorize its communication with
the objects in its domain. They prevent unauthorized sources attached to the same
local area network (LAN) from communication with other objects.

To define the domain security:

1. Log onto the support element on the hardware management console through
Single Object Operations in access administrator or service representative
user role (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate and open the Domain Security task.

Use the online Help for more information on completing this task.

Blocking automatic licensed internal code change installation

This task allows you to prevent automatically installed licensed internal code
change from being installed outside of an explicitly initiated licensed internal code
change installation operation.

Note: In most cases, this setting should not be changed. If this task is set to block
automatic licensed internal code change installation, it prevents your system
from automatically retrieving critical service or customer alerts, in addition to
future enhanced driver maintenance sync port updates.

To block automatic licensed internal code change installation:

© Copyright IBM Corp. 2008 241

 1. Log onto the support element on the hardware management console through
Single Object Operations in access administrator user role (see “Establishing
a support element console session from a Hardware Management Console” on
page 3).
2. Locate and open the Block Automatic Licensed Internal Code Change
Installation task.
The Block Automatic Licensed Internal Code Change Installation window
displays.
3. Select Block Automatic Licensed Internal Code Change Installation.
A check mark appears indicating the automatic installation of licensed internal
code change is blocked.
4. Click Save to save the new setting.

Use the online Help for more information on completing this task.

Changing your password

Use this task to change your password for logging on the support element console.

The security of information assets is controlled by user identification with

passwords. Access to security functions or sensitive data is restricted by user roles.
The access administrator user role is used to set up user identifications and
passwords, and allow access to a particular user role of operation. The system
programmer user role can access sensitive data and control remote access.

Each user is given access to the system through a user identification and
password. This password should be kept confidential and changed if necessary to
maintain security. Both the user identification and password must have a minimum
of four characters with a maximum of eight characters.

To change your support element logon password:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
2. Locate and open the Change Password task.
The Change Password window displays.
3. Enter your current password and your new password twice, the latter time to
confirm it.
4. Click OK to change your password.

Use the online Help for more information on completing this task.

Console messenger
Use this task to provide a simple person-to-person message communication facility
between users of the support element and Hardware Management Console.

242 Support Element Operations Guide

 Note: To send messages from this task, you must enable Console messenger
from the Customize Console Services task (see “Enabling console
messenger” on page 251). Enabling Console messenger also allows you to
receive messages. The Accept Console Messenger messages and Bring
Chat Window to foreground on new message options become available
from the Controls tab of the User settings task to allow you to customize the
way that the Console Messenger task operates for your user ID.

To send an instant message or broadcast message:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
or service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
2. Locate and open the Console Messenger task.
The Console Messenger window displays.

You can send a broadcast message or you can initiate a two-way chat.

Sending a broadcast message

This function allows you to send the same information to all the users on a console
at the same time. To send a broadcast message:
1. The Console Messenger window allows you to choose the console or user that
you want to send a message to and whether or not you want to send a two-way
chat or send a broadcast message.
2. To send a broadcast message, select a top level console from the Reachable
Consoles tree view list and make sure Broadcast appears as the Message
Type, then click OK. The Send Broadcast Message window is displayed. This
window indicates who the recipient of your message will be and includes a
message area for you to provide information that will be sent to all other user
sessions (logged on and disconnected) of the console.
3. Specify a message in the Message input area, then click Send. The Broadcast
Message Send window is displayed indicating whether or not your message
was received successfully.
4. Click Close to return to the support element console workplace.

If you are receiving a broadcast message, the Broadcast Message Received

window is immediately displayed on your support element console. This window
identifies the user that sent the message and displays the message sent by the
user. From this window you can:
v View more information about where the message came from, click view more
info.
v Begin a two-way chat session with the user session that sent the broadcast
message, click Initiate Chat.
v End the task and return to the support element console workplace, click Close.

Initiating a two-way chat

This function allows you to send a message to an individual user. To initiate a
two-way chat:
1. The Console Messenger window allows you to choose the console or user that
you want to send a message to and whether or not you want to send a two-way
chat or send a broadcast message.

Chapter 16. Console actions 243

 2. To send a two-way chat, select an individual user session located below the
reachable console. This automatically changes the Message Type area to
Two-way Chat, then click OK. The Console Messenger Chat window is
displayed.
This window indicates who you will be sending messages to, a history of the
dialogue you will be having with your chat partner, and a message area for you
to provide information that will be sent to your chat partner.
3. Specify a message in the Message input area, then click Send. The Console
Messenger Chat window is refreshed with the message you entered now
appearing in the History area of the window with the prefix Me.
The message is sent to the partner and their Console Messenger Chat window
is also refreshed, with the message text appearing in the History area with the
prefix Partner added to it.
4. If both partners need to continue sending messages to each other, specify a
message in the Message input area and click Send.

Note: To ensure that chat window comes to the foreground in your support
element console sessions when partners send you messages, select
Bring chat window to foreground on message arrival. (a check mark
appears).
5. When you are done conversing with your chat partner, click Close.

Note: The Status for your chat partner changes to Closed by partner and the
Send option is no longer enabled, indicating that you have closed the
Console Messenger Chat window.

There are other support element console tasks, such as the Users and Tasks task,
that offer an ability to open the Console Messenger task to start a two-way chat or
send a broadcast message. Once the Console Messenger task has been opened,
continue with the steps described in this section for information on the procedure for
sending a broadcast message or initiating a two-way chat.

Use the online Help for more information on completing this task.

Controlling the system exclusively from the support element console

The system’s support element serves both as a console for controlling the system
and as an interface that other supported consoles and applications can use for
controlling the system. For example:
v Properly customized hardware management consoles with network connections
to the support element can be used to monitor and operate the system.
v System control or automation applications, such as System Automation for
OS/390 and z/OS Processor Operations Component (SA OS/390 and z/OS
Procops) and Automated Operations Control (AOC), running on systems with
network connections the support element can be used to send it commands for
controlling the system.

Ordinarily, the support element console does not have exclusive control of the
system. That is, the system can be controlled from the support element console and
from any other supported consoles and applications using the support element as a
system interface, all at the same time.

You can temporarily give the support element console exclusive control of the
system, if necessary, to prevent other consoles and applications from controlling it.
For example, you may want to give the support element console exclusive control

244 Support Element Operations Guide

 to prevent other consoles and applications from starting disruptive operations, such
as a system activation or power-on reset, while you are using the support element
console to perform system operations.

The setting of the exclusive control service of a support element determines

whether it has exclusive control of the system:
v The setting is disabled by default. The system can be controlled from the support
element console and from any other supported consoles and applications using
the support element as a system interface.
v Enable the setting to temporarily allow using only the support element console to
control the system.
v Disable the setting again to resume controlling the system from the support
element console and from any other supported consoles and applications using
the support element as a system interface.

To enable or disabling the support element’s exclusive control service:

1. Log onto the support element on the hardware management console through
Single Object Operations in advanced operator, system programmer, access
administrator, or service representative user role (see “Establishing a support
element console session from a Hardware Management Console” on page 3).
2. Locate and open the Support Element Settings (classic style user interface
only) task.
3. Locate and open the Customize Console Services task.
4. Locate the Exclusive Control choice from the Customize Console Services. It
lists choices for enabling or disabling the exclusive control service. The selected
choice indicates the current setting of the service.
5. Select a different choice to change the setting, click OK to save the setting and
close the window.

Use the online Help for more information on the exclusive control service.

Customizing console default user settings

This task is used by an access administrator or a user ID that has access
administrator roles to customize the default appearance for the users of the support
element console workplace.

To set the console default user settings for the support element console:

1. Log onto the support element on the hardware management console through
Single Object Operations in access administrator user role (see “Establishing
a support element console session from a Hardware Management Console” on
page 3).
2. Locate and open the Console Default User Settings task.
The window displays the support element console’s current settings.
3. Proceed through the tabs to customize the user settings

Chapter 16. Console actions 245

 v Select the Tree style tab (tree style user interface only) to customize the tree
style user interface appearance.
v Select the Confirmation tab to customize the preferences for using
confirmation windows for a subset of console workplace tasks.
v Select the Colors and Patterns tab:
– Modify the default colors (or use gray patterns instead of color) that
indicate processor cluster status changes.
– Associate a color or pattern with any of the status values that you indicate
as unacceptable, thereby allowing you to distinguish between types of
exceptions.
– Change the background color of the Views area for an exception situation
and change the color associated with pending changes.
v Select the Controls tab to select objects controls.
v Select the UI Style tab to set the user interface and determine whether or not
the users are allowed to switch the user interface style.
4. Click Apply on each tabbed page for the change to take effect.
5. Click OK when you have completed the task.

Use the online Help for more information for customizing the user settings

Customizing network settings

This task allows you to view the current network information for the support element
console and to change the network settings as shown in the following list.
Identification
Contains the host name and domain name of the support element console.
Console name:
Your support element console user name, the name that identifies
your console to other consoles on the network. This is the short
host name, for example: seibm1.
Domain name:
An alphabetic name that Domain Name Services (DNS) can
translate to the IP address, For example, DNS might translate the
domain name 222.example.com to 198.105.232.4 (The long host
name consists of console name plus a period plus a domain name,
for example: seibm1.endicott.ibm.com.).
Netid: Displays the SNA network name of the network which the CPC is
attached through. Change this setting only when the network’s SNA
network name is changed or when the CPC is connected to a
different network.
Console description:
This is for your use only. An example might be: Main Support
Element Console for customer finance.
LAN Adapters
A summarized list of all (visible) Local Area Network (LAN) adapters. You
can select any of these and click Details... to open a window allowing you
to work with the basic LAN settings.
Name Services
The Domain Name Services (DNS) and domain suffix values.
Routing
Routing information and default gateway information.

246 Support Element Operations Guide

 The Gateway address is the route to all networks. The default gateway
address (if defined) informs the support element console where to send
data if the target station does not reside on the same subnet as this support
element console. This is needed to allow the support element console to
connect to IBM Service Support System using the internet.
You can assign a specific LAN to be the Gateway device or you can
choose ″any.″
You can select Enable ’routed’ to start the routed daemon.

To customize the network settings:

1. Log onto the support element on the hardware management console through
Single Object Operations in access administrator user role (see “Establishing
a support element console session from a Hardware Management Console” on
page 3).
2. Locate and open the Support Element Settings (classic style interface only)
task.
3. Locate and open the Customize Network Settings task.
The Customize Network Settings window displays to allow you to view or
change settings.

Note: Depending on the type of change that you make, the network or console
automatically restarts or the console automatically reboots.

Use the online Help for more information on completing this task.

Customizing password profiles

Use this task to create, customize, or verify the password rules assigned to the
system users. There are three default password rules that you can choose from if
you do not want to create your own. They are: basic, strict, and standard.

To customize a password profiles:

1. Log onto the support element on the hardware management console through
Single Object Operations in access administrator user role (see “Establishing
a support element console session from a Hardware Management Console” on
page 3).
2. Locate and open the Password Profiles task.
The Password Profiles window displays
3. Select a password rule or create your own and select properties for the
password rule.
4. Click OK once you have defined the password properties to save the settings.

Use the online Help for more information on completing this task.

Chapter 16. Console actions 247

Customizing product engineering access
Use this task to verify or change the settings authorizing IBM Product Engineering
(PE) local or remote access to the support element console.

With access authority, IBM Product Engineering can log on the support element
console in an exclusive user identification that provides tasks and operations for
problem determination.

Product Engineering access is provided by a reserved password and permanent

user identification. You cannot view, discard, or change the password and user
identification, but you can control their use for accessing the support element
console.

Use this task to control whether the support element console accepts the Product
Engineering user identification and password for logging on.

To customize the product engineering access:

1. Log onto the support element on the hardware management console through
Single Object Operations in access administrator user role (see “Establishing
a support element console session from a Hardware Management Console” on
page 3).
2. Locate and open the Support Element Settings (classic style interface only)
task.
3. Locate and open the Customize Product Engineering Access task.
The Customize Product Engineering Access window displays to allow you to
view or change settings.
4. Select the appropriate access for product engineering or remote product
engineering.
5. Click OK to save the changes and exit the task.

Use the online Help for more information for customizing product engineering
access to your support element console.

Customizing user profiles

Use this task to manage your system users that log onto the support element
console. This task enables you to add, remove, copy, or modify user profiles using
the default user roles on the support element console. A user profile consists of a
user ID (user identification), permissions, and a text description. Permissions
represent the authority levels assigned to the user profile for the objects the user
has permission to access.

The user ID and password are used to verify a user’s authorization to log on the
support element console. The user ID can be 4 to 320 characters in length and can
be a combination of letters A-Z, a-z), numbers (0-9), and special characters (< + : #
’ = ″ & * ( ) ; - / , % _ > . ?). The password is determined by the password rule that
is chosen for the user ID. The default choices are basic, strict, and standard;
however, other rules may also be available if they were defined in “Customizing

248 Support Element Operations Guide

password profiles” on page 247. All of these rules have their own set of
specifications for assigning a password. Your Access Administrator determines what
password rule is appropriate for you.

This task also allows you to choose the type of password authentication you want
to assign to the user ID. If you choose the Local Server, then the password
authentication is performed by using the support element console. If you choose the
LDAP Server, then the password authentication is delegated to an enterprise
director (LDAP) server. You will use the “Managing enterprise directory server
definitions” on page 254 task to define the LDAP server.

The user profile includes managed resource roles and task roles that are assigned
to the user. The managed resource roles assign permissions for a managed object
or group of objects and the task roles define the access level for a user to perform
on a managed object or group of objects.

The default managed resource roles include:

v All Managed Objects
v Limited Managed Objects

The default task roles include:

v Access Administrator Tasks
v Advanced Operator Tasks
v Operator Tasks
v Service Representative Tasks
v System Programmer Tasks

To customize a user profile:

1. Log onto the support element on the hardware management console through
Single Object Operations in access administrator user role (see “Establishing
a support element console session from a Hardware Management Console” on
page 3).
2. Locate and open the User Profiles task.
The User Profiles window displays.
3. Select the type of user ID you want to customize.
4. If you are creating a new user ID, point to User on the menu bar.
5. Click Add when the menu is displayed. The Add User window is displayed.
If the user ID already exists in the window, select the user ID from the list and
then point to User on the menu bar. When the menu is displayed, click Modify.
The Modify User window is displayed.
6. Compare or change the fields in the window.
7. Click OK when you have finished.

Use the online Help for more information on completing this task.

Chapter 16. Console actions 249

Customizing user settings
This task enables you to customize settings that control how the support element
console operates. Only a user ID assigned access administrator roles sets the
defaults of the support element console settings by using the “Customizing console
default user settings” on page 245.

Because there are many main users interfaces (one for each logged on user), the
support element console provides each user the ability to change settings, such as
color or patterns and confirmation settings. In other words, if you change
confirmation settings or colors and patterns, this does not cause that same change
for other logged-on users.

Note: Color or pattern settings and hover help are only available in the classic style
user interface.

You can select the user interface style that you want to work with (tree or classic) if
the default has been set to allow you to change the interface. (This option is set by
the access administrator from the Console Default Settings task. You also have
the ability to choose whether or not you want hover help, single object selection,
show tips, or choose when to display or not display confirmation windows.

To change the user settings:

1. Log onto the support element on the hardware management console through
Single Object Operations in access administrator, advanced operator,
operator, system programmer, or service representative user role (see
“Establishing a support element console session from a Hardware Management
Console” on page 3).
2. Locate and open the User Settings task.
The window displays the support element console’s current settings.
3. Proceed through the tabs to customize the user settings
v Select the Tree style tab (tree style user interface only) to customize the tree
style user interface appearance.
v Select the Confirmation tab to customize the preferences for using
confirmation windows for a subset of console workplace tasks.
v Select the Colors and Patterns tab (classic style user interface only):
– Modify the default colors (or use gray patterns instead of color) that
indicate processor cluster status changes.
– Associate a color or pattern with any of the status values that you indicate
as unacceptable, thereby allowing you to distinguish between types of
exceptions.
– Change the background color of the Views area for an exception situation
and change the color associated with pending changes.
v Select the Controls tab to select objects controls.
v Select the UI Style tab to select the user interface.
4. Click Apply on each tabbed page for the change to take effect.
5. Click OK when you have completed the task.

Use the online Help for more information for customizing the user settings

250 Support Element Operations Guide

Enabling automatic support element switchover
You can use the support element workplace to control whether the support element
is to be automatically switched to the alternate support element.

To enable or disable automatic support element switchover:

1. Log onto the support element on the hardware management console through
Single Object Operations in advanced operator, system programmer, access
administrator, or service representative user role (see “Establishing a support
element console session from a Hardware Management Console” on page 3).
2. Locate and open the Support Element Settings (classic style user interface
only) task.
3. Locate and open the Customize Console Services task.
4. Locate the Automatic SE Switchover choice from the Enable Support Element
Console Services window. It lists choices for enabling or disabling Automatic SE
switchover. The selected choice indicates the current setting of the service.
5. Select Enabled or Disabled.
6. Click OK to save the setting.

Use the online Help for more information on the automatic SE switchover.

Enabling console messenger

you can use the support element workplace to control whether the console
messenger is active on the console or not. Console messenger allows users to
send and receive instant messages and broadcast messages to other users

To enable or disable console messenger:

1. Log onto the support element on the hardware management console through
Single Object Operations in advanced operator, system programmer, access
administrator, or service representative user role (see “Establishing a support
element console session from a Hardware Management Console” on page 3).
2. Locate and open the Support Element Settings (classic style user interface
only) task.
3. Locate and open the Customize Console Services task.
4. Locate the Console messenger choice from the Enable Support Element
Console Services window. It lists choices for enabling or disabling Console
messenger. The selected choice indicates the current setting of the service.
5. Select Enabled or Disabled.
6. Click OK to save the setting.

Use the online Help for more information on completing this task.

Chapter 16. Console actions 251

Enabling the network message forwarding
You can use the support element workplace to control whether the support element
console will serve as a network message relay node or not. If the support element
console is configured to act as a relay, it will provide inter-console fowarding of
network messages used by forwarding-enabled support element consoles; services,
such as console messenger service. This forwarding can allow these
forwarding-enabled services to communicate between console nodes that do not
have direct network connectivity with each other.

To enable or disable network message forwarding:

1. Log onto the support element on the hardware management console through
Single Object Operations in advanced operator, system programmer, access
administrator, or service representative user role (see “Establishing a support
element console session from a Hardware Management Console” on page 3).
2. Locate and open the Support Element Settings (classic style user interface
only) task.
3. Locate and open the Customize Console Services task.
4. Locate the Network message forwarding choice from the Enable Support
Element Console Services window. It lists choices for enabling or disabling
Network message forwarding. The selected choice indicates the current setting
of the service.
5. Select Enabled or Disabled.
6. Click OK to save the setting.

Use the online Help for more information on completing this task.

Enabling the application programming interface

You can allow other system management applications to use the Management
Application Programming Interfaces (APIs) to the support element console
application. Management APIs allow applications to exchange information about
objects and send commands to an object managed by the support element console
application. This task allows you to enable or disable an SNMP agent and set up a
community name file and event notification information for an SNMP agent. For
more information see Application Programming Interfaces. An online copy of this
book is available under the Books on the support element console.

To change your application programming interface:

1. Log onto the support element on the hardware management console through
Single Object Operations in access administrator user role (see “Establishing
a support element console session from a Hardware Management Console” on
page 3).
2. Locate and open the Support Element Settings (classic style interface only)
task.

252 Support Element Operations Guide

 3. Locate and open the Customize API Settings task.
The Customize API Settings window displays.
4. From this window you can:
v Enable SNMP API
v Allow capacity change API request
v Add, change, or delete community names
v Add, change, or delete SNMPv3 users
v Add, change, or delete event notification information.
5. Click Apply to save the SNMP configuration and continue the configuration.

Use the online Help for more information on completing this task.

Logging off the support element console

Once you have completed your tasks on the support element, log off the console.
The Logoff or Disconnect task allows you to end the current user session and
logs off the support element console or to disconnect while your tasks continue
running. If you disconnect, you can reconnect at a later time to continue working.
However, a disconnect session is eventually ended (This is because disconnect
sessions exist only while the support element console application is running. If the
support element console is restarted or the console is shut down or rebooted, all
session information is lost).

Select the log off operation when you no longer need access to the support element
console. Logging off the console does not affect the status of the CPC or Images.
After you log off or disconnect, the Welcome to the Primary Support Element
Console window is displayed. If you chose to disconnect rather than logoff, when
you logon again, the Choose a Disconnected Session window is displayed. You
can select the disconnected session to continue working or you can begin a new
session. (The number of windows displayed depends on the state of the session
when it was disconnected. One of the windows is the main user interface; additional
windows are for each task that was running when the session was disconnected.)

The support element workplace window closes and the Hardware Management
Console workplace window is displayed.

To log off the support element console:

1. Open the Logoff or Disconnect task. The Choose to Logoff or Disconnect

window is displayed.
2. Select Log off.
3. Click OK to end your session on the support element console.

To disconnect from the support element console:

1. Open the Logoff or Disconnect task. The Choose to Logoff or Disconnect
window is displayed.
2. Select Disconnect.
3. Click OK to disconnect from your session on the support element console with
the intent of returning at a later time.

Use the online Help for more information on completing this task.

Chapter 16. Console actions 253

Managing enterprise directory server definitions
Use this task for creating new enterprise server (LDAP) definitions or editing and
removing existing enterprise directory server definitions.

The Lightweight Directory Access Protocol (LDAP) support allows you the option to
configure your support element console to use an LDAP server to perform user
ID/password authentications at logon time. An LDAP server maintains a
tree-structure database serving as a convenient place to put hierarchical
information, such as corporate employee directory. Each level of the LDAP tree
generally represents a different type of information.

To add, edit, or remove an enterprise directory (LDAP) server:

1. Log onto the support element on the hardware management console through
Single Object Operations in access administrator user role (see “Establishing
a support element console session from a Hardware Management Console” on
page 3).
2. Locate and open the Manage Enterprise Directory Server Definitions task.
The Manage Enterprise Directory Server Definitions window displays.
3. Select the server you want to edit.
4. Click Edit... or Add... to add a new enterprise directory server.
The Edit Enterprise Directory (LDAP) Server window is displayed.
5. Enter the appropriate information.
6. Click OK when you have finished.

Use the online Help for more information on completing this task.

Managing print screen files

This task allows you to capture screen prints of the entire contents of the console or
of individual task windows and then allowing you to manage these files. Managing
your print screen files allows you to view, copy, or delete files that have been
screen captured.

To capture and manage print screen files:

1. Log onto the support element on the hardware management console through
Single Object Operations in access administrator user role (see “Establishing
a support element console session from a Hardware Management Console” on
page 3).
2. Locate and open the Manage Print Screen Files task.
The Manage Print Screen Files window displays.
3. Select a file type from the list that you prefer to have the screen capture saved
as.
4. You can capture a window or screen by clicking one of the following:

254 Support Element Operations Guide

 Print Window
Creates a copy of a task window and gives it a unique file name and
the selected file type. A message window is displayed explaining how to
get the preferred window to the foreground.
Print Screen
Creates a copy of the entire contents of the screen and gives it a
unique file name and the file type you selected. A message window is
displayed explaining the amount of time you have to arrange the
windows on the screen before it is captured.
Your screen capture will appear in a table within the task window once the
process is complete.
5. You can select a file from the table and then proceed with an option to view the
file, copy the file to media, or delete the file.
6. When you are done and ready to exit, click Cancel.

Use the online Help for more information on managing the print screen task.

Migrating channel configuration files

This task allows you to copy the channel’s configuration information that was stored
under a previous (source) PCHID number to a new (target) PCHID number. If you
change the location of the channel card so that it is assigned a new PCHID
number, this task can be used to copy the channel’s configuration information that
was stored under the previous PCHID number to the new PCHID number.

To migrate channel configuration information to a new PCHID:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
roles (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate and open the Migrate Channel Configuration Files task.
The Migrate Channel Config Files window displays.
3. Enter the new target PCHID number for the corresponding source PCHID
number.
4. Click OK to perform the operation.
5. Click Use CD if you have a CD with the channel configuration move records to
update the target PCHID list.

Use the online Help for more information on completing this task.

Performing problem analysis of optical errors

The support element automatically and continuously monitors itself and the central
processor complex (CPC) for problems. If the support element detects a problem, it
uses a knowledge-based expert system called Problem Analysis to automatically:
v Analyze the problem, attempt to determine its cause, and determine whether
service is required to correct the problem.

Chapter 16. Console actions 255

 v Issue a hardware message to notify you of the problem. Information provided
with the message includes a detailed description of the problem and instructions
for correcting it or calling for service.
v Send problem information for optical errors to a designated console, if available,
for additional analysis.

Optical errors are problems that may affect more than one CPC in a Parallel
System Complex (Parallel Sysplex). Currently, optical errors for which additional
analysis is available include:
v ESCON® channel problems
v Coupling facility channel problems

Only a Hardware Management Console can analyze optical errors for integrated
support elements. A Hardware Management Console analyzes optical errors for a
support element if:
v The Hardware Management Console is configured as a Problem Analysis Focal
Point.
v The support element’s CPC is defined to the Hardware Management Console.
v And the Hardware Management Console’s Optical and I/O Error Analysis setting
is enabled.

See Hardware Management Console Operations Guide for instructions for enabling
or disabling a Hardware Management Console’s optical and I/O error analysis
setting.

Performing problem analysis on system I/O errors

Some system I/O devices, mostly tape and DASD products, report errors to the
local operating system as they occur. The operating system may record the errors
in its error recording data set and may also report the problem to the support
element.

If there are no hardware management consoles that have the Problem Analysis
Focal Point function enabled (by enabling Optical and I/O Error Analysis setting),
then the support element problem analysis function will analyze the error report and
possibly report it as a hardware message.

If there is a hardware management console that has the Problem Analysis Focal
Point function enabled and the support element is configured to it, then the I/O error
reports will be forwarded to that hardware management console for analysis and
potential reporting under the Optical Network and System I/O message icon.

Either the support element or the hardware management console may determine
that the I/O error needs to be reported to the service representative and will
automatically initiate the report, if so configured.

Providing modem services to the support element

When performing a support element task or operation requires establishing a
communication link to a remote system, a request to establish the link is sent to the
phone server for the support element.

256 Support Element Operations Guide

 Only a Hardware Management Console can be a phone server for integrated
support elements, since such support elements are not equipped with a modem. A
Hardware Management Console serves as the support element’s phone server if:
v The support element’s central processor complex (CPC) is defined to the
Hardware Management Console and, in the CPC’s definition, the Hardware
Management Console is set to act as the CPC’s phone server.
v And the Hardware Management Console’s phone server service is enabled.

See Hardware Management Console Operations Guide for instructions for defining
CPCs and for enabling or disabling a Hardware Management Console’s phone
server service.

Setting object locking

Some of the support element console tasks are considered disruptive. Performing a
disruptive task on a CPC or CPC image may disrupt its operation. For example,
activating a CPC and loading an image are disruptive tasks. You may want to lock
an object to prevent accidentally performing disruptive tasks on it and then unlock
the object only when you want to perform a disruptive task on it.

Depending on whether the Lockout disruptive task setting is set to Yes or No

determines if you can perform a disruptive task on a CPC or CPC object. You can
either lock an individual object or a group of objects at one time.

Note: The Lockout disruptive task only affects operations from the Support
Element Console workplace you are currently working at. It does not affect
most operations from the Support Element (for example, scheduled
operations and CPC operations management commands, etc.), and
operations initiated from other sources (for example, from Hardware
Management Consoles).

To individually lock the CPC or CPC object:

1. Locate the object you want to lock.
2. Click CPC Details.
The CPC Details window opens.
3. Set Lockout disruptive tasks to Yes or No.
4. Click Apply to lock the object.

If you want to lock the CPC or CPC objects at one time, there is an automatic way
to lock all them displayed on the workplace at one time. If using this method, you
will cause an object to be relocked automatically if it was unlocked to perform a
task on it.
1. Locate and select the objects you want to lock.
2. Open the Support Element Settings task (classic style interface only).
3. Open the Object Locking Settings task.
4. Select Automatically lock all managed objects or Relock after a task has
been run or both. All objects currently in the work area are now locked.

If you attempt to perform a disruptive task on a locked object, a window is displayed

indicating the object is locked.

If you need to unlock an object or a group of objects, you must unlock each one
individually. To do this:
1. Locate the object you want to unlock.
2. Double click on the object’s to open its Detail page.

Chapter 16. Console actions 257

 3. Set Lockout disruptive tasks to No.
4. Click Save to unlock the object.
5. Repeat steps 1 through 4 for every object you want to unlock.

Use the online Help for more information on completing this task.

Shutting down or restarting the system

This task enables you to shut down (power off the console) or to restart the
application or the console.

To shut down or restart the application or console:

1. Log onto the support element on the hardware management console through
Single Object Operations in system programmer or service representative user
roles (see “Establishing a support element console session from a Hardware
Management Console” on page 3).
2. Locate and open the Shutdown or Restart task.
The Shutdown or Restart window displays.
3. You can select one of the following:
v Restart application
v Restart console
v Power-off/shutdown console.
4. Click OK to perform the selected action.

Use the online Help for more information on completing this task.

Synchronizing the support element TOD clock and the CPC TOD clock
Both the central processor complex (CPC) and its support element have time-of-day
(TOD) clocks. The time and date of both TOD clocks should be the same or very
nearly the same. For this reason, the TOD clocks are automatically synchronized
with each other as follows:
v If the CPC does not or cannot use a Sysplex Timer or Server Time Protocol
(STP) as a time source, the CPC TOD clock is synchronized with the support
element TOD clock whenever a power-on reset of the CPC is performed.
v If the CPC uses a Sysplex Timer or Server Time Protocol (STP) as a time
source, changing the time or date at the Sysplex Timer or at the Current Time
Server in an STP-only Coordinated Timing Network automatically synchronizes
the CPC TOD clock to the new time.
v At 11:00PM on the support element TOD clock, it is synchronized with the CPC
TOD clock if:
– The CPC is operating.
– And the support element TOD clock was not set manually since the TOD
clocks were last synchronized.
Otherwise:
- If the CPC is not operating, the support element TOD clock remains
unchanged.

258 Support Element Operations Guide

 - The support element TOD clock is updated with local time adjustments
(daylight saving time offset, leap seconds offset, and time zone offset)
when they occur, if it is synchronized with the CPC TOD clock.
- Or if the CPC is operating, but the support element TOD clock was set
manually since the TOD clocks were last synchronized, then both TOD
clocks remain unchanged and are not synchronized.

Using a Sysplex Timer or Server Time Protocol (STP) as a time source for the CPC
is intended to prevent manually setting the support element TOD clock.

If the CPC does not or cannot use a Sysplex Timer or Server Time Protocol (STP)
as a time source, you can manually set the support element TOD clock.

Setting the support element time-of-day clock manually

You can use the support element workplace to start the console action for manually
setting the support element time-of-day (TOD) clock when the CPC does not or
cannot use a Sysplex Timer or Server Time Protocol (STP) as a time source.

To set the support element TOD clock:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
access administrator, or service representative user role (see “Establishing a
support element console session from a Hardware Management Console” on
page 3).
2. Locate and open the Customize Support Element Date/Time task.
The Customize Console Date and Time window displays the current date, time,
and time-zone offset set for the support element TOD clock.
3. Click Cancel if no corrections are necessary.
4. Enter corrections, if needed, then click Customize.
5. Click OK.
6. Click Refresh to display the new changes.
7. Click Cancel to close the window.

Use the online Help for more information on setting the support element TOD clock.

Viewing console events

The support element console automatically keeps records of significant operations
and activities, referred to as console events, performed either:
v Manually by a console operator.
v Through Management-type Application Programming Interfaces (APIs) to the
Support Element Console Application.
v Automatically by the Support Element Console Application.

Some console events simply indicate an operation or activity occurred. For

example, a console event is logged when a console operator logs on the console.

Other console events are logged in pairs, to indicate when an operation or activity
began and when it ended. For example, a console event is logged when a
power-on reset is started, and another console event is logged when the power-on
Chapter 16. Console actions 259
 reset ends. Console events logged when an operation or activity ends typically also
indicate whether the operation or activity succeeded or failed.

When an event occurs, the date and time occurs and a brief description of the
event are recorded in the Console Event Log. This information is listed on the
View Console Events window under the Date, Time, and Console Event headings,
respectively.

To view console events:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
access administrator, or service representative user role (see “Establishing a
support element console session from a Hardware Management Console” on
page 3).
2. Locate and open the View Console Events task.
The View Console Events window displays.
3. Initially, all events are displayed in descending order, from the most recent
events to the oldest event. You can work with the table by using the table icons
or Select Action from the table tool bar. If you place your cursor over an icon,
the icon description appears (each icon description matches the list in the
Select Action drop-down). The icons perform the following functions:
Show Filter Row
Displays a row under the title row of the table. Select Filter found under
a column title to define a filter for that column. This limits the entries in
the table. Tables can be filtered to show only those entries most
important to you. Click OK when you have defined your filter. The
filtered view can be toggled on and off by selecting the check box next
to the desired filter in the filter row. If you no longer want the Filter row
to appear, click Hide Filter Row.
Clear All Filters
Returns the table back to the complete listing.
Edit Sort
Performs multi-column sorts of objects in the table in ascending or
descending order. Click OK when you have defined your preferred
order.
Clear All Sorts
Returns the table back to the default order.
Configure Columns
Allows you to select which columns you want displayed. Arrange the
columns in the table in a desired order or hide columns from view. All
available columns are listed in the Columns list box by their column
name. You select the columns you want displayed or hidden by
checking or unchecking the list box and using the arrow buttons to the
right of the list to change the order of the selected column. When you
have completed the configuration, click OK. The columns appear in the
table as you specified.
4. From the menu bar you can do the following:

260 Support Element Operations Guide

 v List events in a certain time range, by clicking View, then selecting Using a
different time range. The Change Time window displays.
v Update information listed in the window, by clicking View, then selecting
Refresh.
v Select Exit to close the window.
5. Click View from the menu bar when you have finished reviewing the console
events.
6. Select Exit when you have finished.

Use the online Help for more information on viewing console events.

Viewing licensed Internal code

You can use the support element workplace to start this task to view the licensed
internal code (LIC) that you have agreed to for this support element console. This
list does not include program and code provided under separate license
agreements. This task window appears after the initialization window or to view the
license

To view licensed internal code:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
access administrator, or service representative user role (see “Establishing a
support element console session from a Hardware Management Console” on
page 3).
2. Locate and open the View Licenses task.
The View Licenses window displays.
3. Click on any of the license links to get more information.
4. Click OK when you are done.

Use the online Help for more information on completing this task.

Viewing network diagnostic information

You can use the support element workplace to start the task to display network
diagnostic information for the console’s TCP/IP connection and send an echo
request (ping) to a remote host.

To view information concerning the networking configuration on this support element

console:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
access administrator, or service representative user role (see “Establishing a
support element console session from a Hardware Management Console” on
page 3).

Chapter 16. Console actions 261

 2. Locate and open the Network Diagnostic Information task.
The Network Diagnostic Information window displays.
3. Use the following tabs to view the network information:
v Ping
v Interfaces
v Ethernet Settings
v Address
v Routes
v Address Resolution Protocol (ARP)
v Sockets
v Transmission Control Protocol (TCP)
v User Datagram Protocol (UDP)
v Internet Protocol (IP)
v Native Connections.
4. Click OK when you are done viewing the information.

Use the online Help for more information on viewing the network diagnostic
information.

Pinging the TCP/IP address

To ping a TCP/IP address:
1. Open the Network Diagnostic Information window.
2. Select the Ping tab.
3. Enter the TCP/IP address to ping.
4. Click Ping.

Viewing security logs

You can use the support element workplace to start this task to view security events
logs for the CPC. The support element automatically keeps a default security log of
security events that occur while the support element application is running. A
security event occurs when an object’s operational state, status, or settings change
or involves user access to tasks, actions, and objects.

To view security logs:

1. Log onto the support element on the hardware management console through
Single Object Operations in access administrator, system programmer or
service representative user role (see “Establishing a support element console
session from a Hardware Management Console” on page 3).
2. Locate and open the View Security Logs task.
The View Security Logs window displays.
3. The window displays the Security Event and the Date and Time the security
log is created.
4. From the menu bar you have the following options for viewing information:
v To open security logs, click File, then one of the following options:
– To open an archived security log on a DVD, select Open Security Log,
New.

262 Support Element Operations Guide

 – To open the support element console’s default security log, select Open
Security Log, Default.
– To close the window and end the task, select Exit.
v To search the security log that is currently open, click Search, then one of
the following options:
– To search events by the time and date they occurred, select By Date.
– To search for an event by its description, select By Event.
– To search for events by a certain category, select By Category.
v To view or alter the security log options, click Options, then one of the
following options:
– To enable the creation of a hardware message when the security log is
approaching the maximum size, select Create hardware message when
approaching maximum, On.
– To disable the creation of a hardware message when the security log is
approaching the maximum size, select Create hardware message when
approaching maximum, Off.
– To enable the creation of a security log event when the underlying network
firewall denies a network connection, select, Log security event for
network denial events, On.
– To disable the creation of a security log event when the underlying
network firewall denies a network connection, select Log security event
for network denial events, Off.
v To display help for the current window, click Help.
5. When you are done viewing the security log, click File, Exit.

Use the online Help for more information on reviewing the console events.

Viewing users and tasks information

Use this task to display a list of the users and tasks that are currently logged onto
the support element console.

To view users and tasks information:

1. Log onto the support element on the hardware management console through
Single Object Operations in operator, advanced operator, system programmer,
access administrator, or service representative user role (see “Establishing a
support element console session from a Hardware Management Console” on
page 3).
2. Locate and open the Users and Tasks task.
The Users and Tasks window displays.
3. The following information is displayed
v Users ID you are logged in as and the other user IDs that are logged into the
console
v Time the user ID logged in
v Number of tasks running
v User ID access location
v Information about tasks that are running:
– Task ID
– Task name
– Targets (if any)

Chapter 16. Console actions 263

 – Session ID
Notes:
a. If you are assigned a user ID with access administrator roles, you can:
– Logoff or disconnect any user from the session (click Logoff or
Disconnect.
– Terminate any user from the session (click Terminate).
b. You can only switch to another task in your own session.
c. You can terminate your own session.
4. You can initiate a two-way chat with another user by selecting the user name
and clicking Chat With. You can also switch to another task that is running in
your session by selecting the task and clicking Switch To.
5. When you have finished, click Close.

Use the online Help for more information on completing this task.

264 Support Element Operations Guide

Notices
This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may be
used instead. However, it is the user’s responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you any
license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS

PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF NON-INFRINGEMENT, 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. IBM 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 non-IBM Web sites 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
IBM product and use of those Web sites is at your own risk.

IBM 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.

© Copyright IBM Corp. 2008 265

 Information concerning non-IBM products was obtained from the suppliers of those
products, their published announcements or other publicly available sources. IBM
has not tested those products and cannot confirm the accuracy of performance,
compatibility or any other claims related to non-IBM products. Questions on the
capabilities of non-IBM products should be addressed to the suppliers of those
products.

All statements regarding IBM’s future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM’s 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 softcopy, the photographs and color illustrations
may not appear.

Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corporation in the United States, other countries,
or both. If these and other IBM trademarked terms are marked on their first
occurrence in this information with a trademark symbol ( ® or ™ ), these symbols
indicate U.S. registered or common law trademarks owned by IBM at the time this
information was published. Such trademarks may also be registered or common law
trademarks in other countries. A current list of IBM trademarks is available on the
Web at “Copyright and trademark information” at www.ibm.com/legal/
copytrade.shtml.

INFINIBAND, InfiniBand Trade Association and the INFINIBAND design marks are
trademarks and/or service marks of the INFINIBAND Trade Association.

Linux is a trademark of Linux Torvalds 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.

Java and all Java-based trademarks and logos are trademarks of Sun
Microsystems, Inc. in the United States, other countries, or both.

Other company, product, and service names may be trademarks or service marks
of others.

266 Support Element Operations Guide

Electronic emission notices
The following statements apply to this IBM product. The statement for other IBM
products intended for use with this product will appear in their accompanying
manuals.

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 instructions contained in the
installation 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, by installation or use of this equipment other than as specified in
the installation manual, or by any other unauthorized changes or
modifications to this equipment. Unauthorized changes or modifications could
void the user’s 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.

Canadian Department of Communications Compliance Statement

This Class A digital apparatus complies with Canadian ICES-003.

Avis de conformlté aux normes du ministère des Communications du Canada

Cet appareil numérique de la classe A est conform à la norme NMB-003 du

Canada.

European Union (EU) Electromagnetic Compatibility Directive

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 equipment were derived for commercial and industrial environments
to provide reasonable protection against interference with licensed communication
equipment.

Notices 267
 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.

European Community contact:

IBM Technical Regulations
Pascalstr. 100, Stuttgart, Germany 70569
Telephone: 0049 (0) 711 785 1176
Fax: 0049 (0) 711 785 1283
email: tjahn@de.ibm.com

EC Declaration of Conformity (In German)

Deutschsprachiger EU Hinweis: Hinweis für Geräte der Klasse A EU-Richtlinie

zur Elektromagnetischen Verträglichkeit

Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie 89/336/EWG

zur Angleichung der Rechtsvorschriften über die elektromagnetische Verträglichkeit
in den EU-Mitgliedsstaaten und hält die Grenzwerte der EN 55022 Klasse A ein.

Um dieses sicherzustellen, sind die Geräte wie in den Handbüchern beschrieben zu

installieren und zu betreiben. Des Weiteren dürfen auch nur von der IBM
empfohlene Kabel angeschlossen werden. IBM übernimmt keine Verantwortung für
die Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung der
IBM verändert bzw. wenn Erweiterungskomponenten von Fremdherstellern ohne
Empfehlung der IBM gesteckt/eingebaut werden.

EN 55022 Klasse A Geräte müssen mit folgendem Warnhinweis versehen werden:

″Warnung: Dieses ist eine Einrichtung der Klasse A. Diese Einrichtung kann im
Wohnbereich Funk-Störungen verursachen; in diesem Fall kann vom Betreiber
verlangt werden, angemessene Maßnahmen zu ergreifen und dafür aufzukommen.″

Deutschland: Einhaltung des Gesetzes über die elektromagnetische

Verträglichkeit von Geräten

Dieses Produkt entspricht dem “Gesetz über die elektromagnetische Verträglichkeit

von Geräten (EMVG)“. Dies ist die Umsetzung der EU-Richtlinie 89/336/EWG in der
Bundesrepublik Deutschland.

Zulassungsbescheinigung laut dem Deutschen Gesetz über die

elektromagnetische Verträglichkeit von Geräten (EMVG) vom 18. September
1998 (bzw. der EMC EG Richtlinie 89/336) für Geräte der Klasse A.

Dieses Gerät ist berechtigt, in Übereinstimmung mit dem Deutschen EMVG das
EG-Konformitätszeichen - CE - zu führen.

Verantwortlich für die Konformitätserklärung nach Paragraf 5 des EMVG ist die IBM
Deutschland GmbH, 70548 Stuttgart.

Informationen in Hinsicht EMVG Paragraf 4 Abs. (1) 4:

Das Gerät erfüllt die Schutzanforderungen nach EN 55024 und EN 55022

Klasse A.

update: 2004/12/07

268 Support Element Operations Guide

People’s Republic of China Class A Compliance Statement

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 actions.

Japan Class A Compliance Statement

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.

Korean Class A Compliance Statement

Taiwan Class A Compliance Statement

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.

Notices 269
270 Support Element Operations Guide
Index
A background color (continued)
image icon, of 44
account information task
views area, of 37
instructions for starting 150
blocking automatic licensed internal code change
account information, about 150
installation 241
activate task
books view, opening 56
instructions for starting 63, 153, 154, 156, 157, 158
books work area, contents of 56
activate, about 59
activating an integrated coupling facility processor 107,
108
dynamic integrated coupling facility expansion 107,
C
108 central processor complex
activation activating 62
other profiles 61 activating, tips for 95
profiles 60 activity, starting analysis of 71
activation profiles background color, meaning of 43
about 60, 89 deactivating 76
customizing 89 details window, opening 45
default profiles 89, 90 hardware messages from, checking 64
image profiles, customizing 123 images of, about 35
load profiles, customizing 128 load image, performed automatically during system
reset profiles, customizing 92 activation 60
types of 60, 90 load image, performing manually for error
types to use, choosing the right 90 recovery 84
activation, about 59 power-on reset, performed automatically during
activatione system activation 60
reset profile 61 power-on reset, prforming manually for error
active tasks view, opening 53 recovery 81
active tasks work area, contents of 53 reset clear of image, performing for error
activity task recovery 83
instructions for starting 71 reset normal of image, performing for daily
activity, about system 68 operation 74
adding logical processors 171 reset normal of image, performing for error
advanced facilities 227 recovery 83
PCI crypto 240 start all image’s processors, performing for error
alternate support element 212, 213 recovery 81
API,enabling 252 status of, determining 43
application programming interface,enabling 252 stop all image’s processors, performing for error
assigning domain security 241 recovery 81
assigning logical partition group name 131 central processors
authorize concurrent internal code changes task locating on the workplace 41
instructions for starting 208, 209, 210, 211 central storage 139
authorize internal code changes task change LPAR controls task
instructions for starting 207 instructions for starting 168
automatic activation task change LPAR security task
instructions for starting 135 instructions for starting 166
automatic activation, about 135 change management task list, instructions for starting
automatic licensed internal code change tasks in 197
installation,blocking 241 authorize concurrent internal code changes 208,
209, 210, 211
authorize internal code changes 207
B system information 205
changing group controls,logical partition 169
background color
changing group profile name 107
CHPID icon, of 45
changing internal code 198
CP icon, of 44
changing logical partition cryptographic controls 170
CPC icon, of 43
changing LPAR I/O priority queuing 173
exceptions icon, of 48
changing password 242
group icon, of 48
channel configuration files,migrating 255

© Copyright IBM Corp. 2008 271

channel operations task list, instructions for starting configuring
tasks in 226 channel paths on or off 221, 231
advanced facilities 228 console actions view, opening 54, 55, 57
channel paths console actions work area, instructions for starting
channel information, displaying 226, 233, 239 actions in 54, 55, 57
control unit header, displaying 226, 233, 239 console actions work area, instructions for starting
definition errors, identifying 227, 234 actions in
device status, displaying 226, 233, 239 customize date/time 259
locating on the workplace 42 enable console services 245
paths to a device, displaying 226, 233, 239 logoff 3, 253
problem determination 226, 233, 239 view console events 260
reassigning reconfigurable 223 console default user setting,customizing 245
releasing reconfigurable 222, 232 console messenger 242
serial link status, displaying 226, 233 console, support element from a hardware management
subchannel data, displaying 226, 233 console 3
channel problem determination 226, 233, 239 context sensitive help 6
channel problem determination task, instructions for control settings for logical partition 168
starting 226, 233, 239 coupling facility 106
channel problem determination task, instructions for coupling facility logical partition 106
starting in 226, 233, 239 CP toolbox task list, instructions for starting tasks
channel to PCHID assignment 177 in 215
channels display or alter 216
locating on the workplace 42 interrupt 218
checking InfiniBand status 162 PSW restart 217
checkout tests task start 215
instructions for starting 154 stop 215
checkout tests, about 154 stop on CP address match 218
CHPID operations task list, instructions for starting tasks store status 219
in 233 CPC
advanced facilities 240 activating 62
channel problem determination 226, 233, 239 activating, tips for 95
configure on/off 221, 231, 237 activity, starting analysis of 71
reassign channel path 223 background color, meaning of 43
release 223, 232 deactivating 76
service on/off 225, 233, 238 details window, opening 45
CHPIDs hardware messages from, checking 64
channel information, displaying 226, 233 images of, about 35
control unit header, displaying 226, 233 load image, performed automatically during system
definition errors, identifying 227, 234 activation 60
device status, displaying 226, 233 locating on the workplace 40
locating on the workplace 42 power-on reset, performed automatically during
paths to a device, displaying 226, 233 system activation 60
problem determination 226, 233 power-on reset, performing manually for error
reassigning reconfigurable 223 recovery 85
releasing reconfigurable 222, 232 reset normal of image, performing for daily
serial link status, displaying 226, 233 operation 74
subchannel data, displaying 226, 233 reset normal of image, performing for error
clonable internal code levels 207 recovery 83
color, background start all image’s processors, performing for error
CHPID icon, of 45 recovery 81
CP icon, of 44 CPC configuration task list, instructions for starting tasks
CPC icon, of 43 in 175
exceptions icon, of 48 input/Output configuration 176
group icon, of 48 view hardware configuration 175
image icon, of 44 CPC group, opening 40
views area of 37 CPC operational customization task list, instructions for
concurrent internal code change 202 starting tasks in 89
configure Off/On,querying a channel/crypto 209 automatic activation 135
configure on/off task change LPAR controls 168
instructions for starting 221, 231, 237 change LPAR security 166
customization activation profiles 92

272 Support Element Operations Guide

CPC operational customization task list, instructions for domain security,assigning 241
starting tasks in (continued) dump data, about 158
customize/delete activation profiles 132 dump LPAR data task
enable/disable dynamic channel subsystem 100 instructions for starting 159, 162
scheduled operations 136, 200 dynamic I/O configuration
storage information 139, 140 about 99
system activity profiles 142 CPC, activating to support using 99
view activation profiles 132 IOCDS, using to select 97
view LPAR cryptographic controls 171 load attributes, using to set 118
CPC recovery task list, instructions for starting tasks logical partition, activating to support using 111
in 81 dynamic integrated coupling facility expansion 107,
load 84 108
Load 84
power-on reset 85
reset clear 84 E
reset normal 83 enable console services console action
start all 82 about 244
stop all 82 instructions for starting 245
CPC remote customization task list, instructions for enable/disable dynamic channel subsystem task,
starting tasks in 147 about 100
account information 150 enabling automatic se switchover 251
remote service 149 enabling console messenger 251
CPC work area, contents of 40 enabling I/O priority queuing 173
CPs enabling NPIV 235
locating on the workplace 41 enabling the application programming interface 252
stopping 218 enabling the network message forwarding 252
cryptographic controls for logical partitions engineering change 197
customizing in activation profiles 120 enterprise directory server definitions,managing 254
viewing 171 exceptions
customize date/time console action indicators of, recognizing 48
instructions for starting 259 locating on the workplace 48
customize/delete acivation profiles task recovering from 48
instructions for starting 92, 123 exceptions view, opening 48
customizing console default user settings 245 exceptions work area, contents of 48
customizing network settings 246 expanded storage 139
customizing product engineering 248 exporting and importing profile data, instructions for
starting task 174

D
daily task list F
activate 63, 153, 154, 156, 157, 158 forcing channel internal code change 208
activity 71
deactivate 76
reset normal 75 G
deactivate 75 group controls, logical partition 169
deactivate task group profile name, changing 107
instructions for starting 76 group profiles 131
deactivation 75 assigning names
defining clonable internal code levels 207 defining group capacity 131
definition errors, identifying for channel paths 227, 234 groups
definition errors, identifying for PCI crypto 239 about 35
degraded status background color, meaning of 48
conditions causing 47 locating on the workplace 40
degraded storage mode 140
delete LPAR dump data task
instructions for starting 160
details window, opening an objects 45
H
hardware messages 155
display or alter task
about 64
instructions for starting 216
indicators of, recognizing 64
displayng the infiniband adapter ID 176
viewing, instructions for 65
disruptive internal code change 202

Index 273
hardware messages task licensed internal code,viewing 261
flashing icon, meaning of 65 load 84
reporting a hardware problem, instructions for 156 performed automatically during system activation 60
help performing manually for error recovery 84
hover help, displaying 56 load profile
workplace, getting for 56 about 61, 89
HSA 138 assigning to CPC 130
assigning to logical partition 130
customizing 128
I customizing, tips for 130
ICSF 121 new, creating 130
image profile opening 128
about 61, 89, 123 saving 130
assigning to logical partition 127 load profiles
customizing 123 preparing 62
customizing, tips for 127 load task
navigating the notebook pages 125 instructions for starting 84
opening 123 loading software from a CD-ROM or FTP server 86
saving 127 lockout for disruptive tasks 54, 257
image profile configuration 96 logging off the support element console 77
images closing open windows before 53
activating 63 completing active tasks before 53
background color, meaning of 44 logical partition cryptographic controls 170
deactivating 76 logical partition group capacity 132
details window, opening 45 logical partition group controls 169
operating system messages from, checking 66 logical partition group name, assigning 131
Images logical partitions
details window, opening 45 activating, tips for 104
locating on the workplace 40 as CPC images 35
images work area locating on the workplace 40
contents in LPAR mode 41 logical processor assignment 167
IML 59, 85 logically partitioned mode
infiniband adapter ID,displaying 176 activating the CPC in 95
InfiniBand status, checking 162 LPAR mode
initial microcode load 59, 85 activating the CPC in 95
initiating a two-way chat 243
input/output configuration data set 176
CPC activation, prerequisite for 62 M
dynamic I/O, selecting an IOCDS that supports 99 managing enterprise directory server definitions 254
reset profile, customizing to select for CPC managing groups of objects
activation 96 groups, managing 77
input/output configuration program 176 manually setting the support lement TOD clock 259
input/output configuration task migrating channel configuration files 255
instructions for starting 176 mirroring support element to alternate support
internal code 197 element 212
checking dependencies 200 monitoring and operating
considerations when activating 202 support element 55
keeping records 204
viewing internal code changes 205
internal code changes 197 N
internal code,changing 198 network diagnostic information, viewing 261
interrupt task pinging TCP/IP address 261
instructions for starting 218 network settings,customizing 246
IOCP 176 NPIV port names,releasing 195
IPL 59 NPIV,enabling 235
NTA settings 163

L
LED (light emitting diode)
setting on 225, 233
licensed internal code 197

274 Support Element Operations Guide

O power, system (continued)
on, switched automatically during system
object locking for disruptive tasks 54, 257
activation 60
off-loading RETAIN data to the hardware management
outage, recovery options for automatic system
console DVD 162
activation after 135
open system adapter (OSA)
print screen
using advanced facilities 227
managing print screen files 254
opening and online book 56
problem analysis, about 154, 155
operating environment
problem analysis,optical errors 255
setting for CPC 100
problem analysis,performing 256
operating system commands, about 67
problems, reporting 154
operating system messages
processor running time 167
checking 66
processor storage
indicators of, recognizing 66
displaying or altering data 216
viewing, instructions for 67
product engineering,customzing 248
operating system messages task
profiles for complete activation 92
flashing icon, meaning of 66
PSW restart task
sending commands, instructions for 67
instructions for starting 217
viewing messages, instructions for 67
operation, scheduled 136
OSA-Express NTA 163
Q
query coupling facility reactivations 210
P query internal code changes pending power-on
reset 210
password profiles,customizing 247
querying channel/crypto 209
password,changing 242
querying switch capabilities between support
PCi crypto
elements 212
advanced facilities 240
PCI crypto
channel information, displaying 239
channel problem determination 239
R
configuring on 237 reassign channel path task, instructions for
control unit header, displaying 239 starting 223
definition errors, identifying 239 reconfigurable channel paths
serial link status, displaying 239 configuring 222
setting service on or off 238 release task 223, 232
subchannel data, displaying 239 releasing a PCI fryptographic feature 194
PCI cryptographic features 189 releasing NPIV port names 195
status, monitoring 190 remote service task
PCI X cryptographic coprocessor feature instructions for starting 149
pseudo-random number (PRN) generator 191 remote service, about 147
zeroizing 191 report a problem task
perform model conversion 179 instructions for starting 157
perform problem analysis task reporting problems 154
instructions for starting 156 reset clear task
performing an alternate support element action 211 instructions for starting 84
performing problem analysis 256 reset clear, about 83
performing problem analysis of optical errors 255 reset normal task
permanent upgrades, model conversion 180 instructions for starting 75, 83
physical and logical processors reset normal, about 74, 83
locating on the workplace 41 reset profile
pinging the TCP/IP address 261 about 61, 89
power-on reset 85 asigning to CPC 95
performed automatically during system activation 60 customizing 92
performing manually for error recovery 85 navigating the notebook pages 93
power-on reset task new, creating 94, 125
instructions for starting 85 opening 92
power, system saving 95
off, switched automatically during system restarting a processor 217
deactivation 75

Index 275
S stop processor operation, about 81, 215
stop task
sample profiles 70
instructions for starting 215
SAPs (system assist processors)
stopping CPs 218
configuring CPs as 101
storage information task
scheduled operations 136, 199
degraded storage amount, instructions for
scheduled operations task
determining 140
instructions for starting 136, 200
storage Information task
security settings for logical partitions
storage allocations, instructions for reviewing
changing dynamically 166
current 139
cross partition authority 112, 165
storage, about 138
customizing in activation profiles 111, 112
store status task
global performance data control 111, 165
instructions for starting 219
input/output configuration control 111, 165
support element console
logical partition isolation 113, 165
from a hardware management console 1
security, view logs 262
support element console application
selecting a crypto type 193
starting 1
selective channel apply controls 209
support element modem services,providing 256
sending a broadcast message
support element TOD clock 138
broadcast message 243
support element workplace 35
server time protocol (STP) 137, 182
switching to the alternate support element 213
service
sync point 211
setting on or off 224
synchronizing
service data, about 157
support element TOD clock and CPC TOD
service history, about 161
clock 258
service on/off task
sysplex timer 182
instructions for starting 225, 233, 238
system
service required
activation 59
conditions causing 47
monitoring 68
service status 153
operating daily, tasks for 59
service task list
problem determination, tasks for performing 153
checkout tests 154
recovering from errors, tasks for 81
service task list, instructions for starting tasks in 153
resetting 74
checkout tests 154
service, tasks for getting 153
delete LPAR dump data 160
settings for remote connections and communication,
dump LPAR data 159, 162
tasks for customizing 147
perform problem analysis 156
settings for system operations, tasks for
report a problem 157
customizing 89
transmit service data 158
shutting down 75
view service history 161
starting 59
setting defined capacity 116
status, getting detailed 39
setting group capacity 132
testing, tasks for 153
setting the system time offset 172
system activity analysis 69
setting up time synchronization 183
system activity profile 69
ETR configuration 185
system activity profiles task
ETR status 185
instructions for starting 142
network configuration 185
system activity, about 68
STP configuration 186
system assist processors (SAPs)
STP status 186
configuring CPs as 100
timing network 184
system information task
setting workload manager controls 109
instructions for starting 205
shutting down or restarting the system 258
system input/output configuration analyzer 178
specify concurrent upgrade sync point 211
start all task
instructions for starting 82
start processor operaiton, about 81
T
start task task list view, opening 50
instructions for starting 215 task list work area, contents of 50
stop all task task list, about 35
instructions for starting 82 tasks
stop on CP address match task about 35
instructions for starting 218 locating 49

276 Support Element Operations Guide

tasks (continued)
minimizing, while in progress 52
restoring, if previously minimized 52
starting 49
targets, locating 50
targets, selecting 50
temporary upgrades 181
time synchronization features 182
time synchronization source
synchronizing the CPC TOD clock 137
time-of-day clock 138
TKE commands
changing permission 192
TOD clock 138
TOD clock,manually setting 259
transmit service data task
instructions for starting 158
trusted key entry (TKE) feature
logical partition cryptographic controls, required
settings for
customizing in activation profiles 122
two-way chat 243

U
UDX
configuring user defined extensions (UDX) 193
upgrades,temporary 181
usage domain,zeroizing 192
USB flash memory drive 7
user profiles,customizing 248
user settings, customizing 250
users and tasks information,viewing 263

V
view activation profiles task
instructions for starting 132
view console events console action
about 259
instructons for starting 260
view security logs 262
view service history task
instructions for starting 161
viewing licensed internal code 261
viewing the input/output configuration data 178
viewing users and tasks 263

W
wizard profile image,using 126
work area, about 35
workplace pop-up 57

Z
zeroizing usage domain 192

Index 277
278 Support Element Operations Guide



Printed in USA

SC28-6879-00