AS/400 - Service Provider Information
AS/400 - Service Provider Information
Contents v
IBM Cryptographic Coprocessor Card Return
Program . . . . . . . . . . . . . . . 254
Laser compliance
All lasers are certified in the U.S. to conform to the requirements of DHHS 21 CFR Subchapter J for class
1 laser products. Outside the U.S., they are certified to be in compliance with IEC 60825 as a class 1 laser
product. Consult the label on each part for laser certification numbers and approval information.
CAUTION:
This product might contain one or more of the following devices: CD-ROM drive, DVD-ROM drive,
DVD-RAM drive, or laser module, which are Class 1 laser products. Note the following information:
v Do not remove the covers. Removing the covers of the laser product could result in exposure to
hazardous laser radiation. There are no serviceable parts inside the device.
v Use of the controls or adjustments or performance of procedures other than those specified herein
might result in hazardous radiation exposure.
(C026)
CAUTION:
Data processing environments can contain equipment transmitting on system links with laser modules
that operate at greater than Class 1 power levels. For this reason, never look into the end of an optical
fiber cable or open receptacle. (C027)
CAUTION:
This product contains a Class 1M laser. Do not view directly with optical instruments. (C028)
CAUTION:
Some laser products contain an embedded Class 3A or Class 3B laser diode. Note the following
information: laser radiation when open. Do not stare into the beam, do not view directly with optical
instruments, and avoid direct exposure to the beam. (C030)
Before using this information, you should know how to service this particular hardware model. You must
also know how to safely work with electrical components.
Attention: Misuse of service tools or using them with inappropriate security safeguards might result in
loss of data, programs, or other objects on the system.
DST operates in stand-alone, limited, and full paging environments. The DST tools and functions vary
depending on the paging environment and the release level of the operating system. For more
information, see “System paging environments.”
System Service Tools (SST) provides a way to access a subset of the service tools that DST offers without
requiring access to DST. SST is available when i5/OS® is operational, and can be accessed using the
STRSST CL command.
Note: It is a requirement to change the password the first time anyone signs on to DST or SST. The
authorized service provider must provide the new (changed) password to the customer or have the
customer change the password.
Note: When you perform an alternate initial program load (IPL) to DST, you do not need the
load-source disk.
v An operational workstation on bus 1 as either a primary console or an operations console.
v One workstation for each system partition.
v A valid service tools user ID and password to sign on to DST. IBM® supplies service tools user IDs that
have different levels of privileges. For more information, see “Work with service tools user IDs” on
page 27.
To make a printout, attach the printer to the workstation I/O processor or storage media unit that is
performing the service function. The printer that is used with DST for service tool output must be an
SCS-type data stream printer.
You can use this environment only by performing an alternate IPL to DST. For details, see “Performing an
alternate IPL to DST (type D IPL)” on page 6.
The following options are available in the stand-alone environment for all operating systems:
v Install Licensed Internal Code
v Work with disk units
v Work with DST environment
v Start a service tool
v Work with remote service support
Limited paging
The limited paging environment is the first servicing environment you access when you begin to start the
system in Manual mode. This environment contains all the functions of the Licensed Internal Code,
including storage management.
You can use this environment by performing an IPL to DST. For details, see “Performing an IPL to DST”
on page 3.
You can access DST while the system is in the limited paging environment. This environment accesses the
temporary files that are needed and the Licensed Internal Code on the load-source disk. The operating
system is not available.
Attention: For systems with multiple logical partitions, performing an IPL on the primary partition
causes the secondary partitions to be powered down. Failing to power down these secondary partitions
will cause an abnormal power-down on the secondary partitions and possible loss of data.
The following options are available in the limited paging environment for all operating systems:
v Perform an IPL
v Install the operating system
v Work with Licensed Internal Code
v Work with disk units
v Work with DST environment
v Start a service tool
v Work with remote service support
v Work with system capacity
v Work with system security
Note: The following options are operating system-dependent. For a list of the options available for your
operating system, see “DST in i5/OS limited paging environment” on page 211.
v Perform automatic installation of the operating system
v Save Licensed Internal Code
v Select DST console mode
v Work with save storage and restore storage
For a description of each option, see “DST options” on page 8.
You remain in the full paging environment when you perform one of the following:
v Function 21 on the control panel or Work with Partition Status screen to access DST. For details, see
“Selecting Function 21 while the system is operational” on page 5.
All disk units, the Licensed Internal Code, and the operating system are available.
The following options are available in the full paging environment for all operating systems:
v Perform an IPL
v Install the operating system
v Work with Licensed Internal Code
v Work with disk units
v Work with DST environment
v Start a service tool
v Work with remote service support
v Work with system partitions
v Work with system security
Note: The following options are operating system-dependent. For a list of the options available for your
operating system, see “DST in i5/OS full paging environment” on page 210.
v Select DST console mode
v Resume operating system display
v Perform automatic installation of the operating system
v Save Licensed Internal Code
Note: You can also use the function key F16, which is not displayed, while in DST debug mode during a
step-mode IPL.
For secondary partitions, see “Performing an IPL to DST for logical partitions” on page 5.
Service functions 3
1. Select a type B IPL in Manual mode. For information on how to select IPL options, see “IPL type,
mode, and speed options” on page 159.
Attention: For systems with logical partitions, performing an IPL on the primary partition causes the
secondary partitions to be powered down. Failing to power down these secondary partitions will
cause an abnormal power-down on the secondary partitions and possible loss of data.
2. Choose from the following options:
v If there is a problem log entry after powering on the system, perform a delayed power-off. (This is
the data for problem analysis.) When the system is off, press the Power button on the control panel
to perform an IPL. Select Function 03 if the delayed power-off takes longer than 40 minutes to
complete.
Attention: Performing Function 03 may cause damage to objects, and it may also cause data loss.
v If there is an attention light after powering on the system, use the Increment (↑) or Decrement (↓)
button to select control panel Function 03. Press Enter on the control panel to perform an IPL.
v If the system is powered off, press the Power button on the control panel to perform an IPL.
The IPL or Install the System display appears on the primary console.
3. Select the Use Dedicated Service Tools option. The DST Sign On display appears. For more information
on how to identify the primary console, see “Determining a primary or alternative console” on page
125.
4. Sign on to DST with a valid user ID and password.
Remember: Enter a valid user ID and get the password from the customer. If the customer has
changed the full DST authority, user ID, or password, ask the customer for the correct
values.
Notes:
v If prompted for a password, be sure to give the new (changed) password to the customer.
v Starting with V5R1, you are limited to three sign-on attempts to DST. After three
unsuccessful attempts, the service tools user ID will be disabled. A user ID with a service
tool security privilege must reset the ID.
The Use Dedicated Service Tools (DST) display appears.
Restriction: The system is in the limited paging environment. For details, see “Limited paging” on
page 2 and “DST options” on page 8.
This ends the procedure.
Note: If the system security is set to prevent a service tools user ID with a default and expired
password from changing its own password, then you will not be able to sign on to SST until
you first sign on to DST and change your password there.
You must use the Hardware Management Console (HMC) to load logical partitions and to work with
logical partitions.
For information about using the HMC to power on logical partitions, see Activating a partition profile.
For information about using the HMC to power off logical partitions, see Shutting down i5/OS logical
partitions.
For information about working with logical partitions, see Managing i5/OS logical partitions.
For general information about logical partitions, see General concepts for partitioning the server.
Debug mode is an environment to test programs. You can select a function key and access DST during
the IPL process. For details, see “Perform an IPL” on page 9.
Notes:
v If prompted for a password, be sure to give the new (changed) password to the customer.
v Starting with V5R1, you are limited to three sign-on attempts to DST. After three
unsuccessful attempts, the service tools user ID will be disabled. A user ID with a service
tool security privilege must reset the ID.
For details on the DST options, see “DST options” on page 8. This ends the procedure.
Service functions 5
About this task
Notes:
a. If you enter Function 21 and the primary console is powered off or not usable, reference
code A600500x appears on the control panel. Enter Function 21 again to force the DST Sign
On display to appear on one of the alternative consoles.
b. For more information on how to select IPL options, see “IPL type, mode, and speed
options” on page 159.
2. Select Manual mode, then push the Increment (↑) or Decrement (↓) button on the control panel until
21 appears in the Function/Data display. Press the Enter button on the control panel. Primary console
or alternate console will display the DST sign on.
Note: For more information on how to identify the primary console, see “Determining a primary or
alternative console” on page 125.
3. Sign on to DST.
4. Type QSRV as the valid user ID and get the password from the customer. The Use Dedicated Service
Tools (DST) display appears.
If the customer has changed the full DST authority user ID or password, ask the customer for the
correct values.
Notes:
v If prompted for a password, be sure to give the new (changed) password to the customer.
v Starting with V5R1, you are limited to three sign-on attempts to DST. After three
unsuccessful attempts, the service tools user ID will be disabled. A user ID with a service
tool security privilege must reset the ID.
The system is now in the full paging environment. For additional details, refer to “System paging
environments” on page 1 and “DST options” on page 8.
Notes:
a. If SRC A600 500x is displayed on the control panel, the system was not able to locate the
console. Perform the following steps:
1) Ensure that the console is powered on.
2) Repair the console if necessary.
3) Select Function 21 on the control panel to make DST available. For details, see
Function 21: Service tool initiation.
b. If an SRC other than A600 500x is displayed on the control panel, go to the Starting point
for all problems in the Problem analysis information for your system.
The Install Licensed Internal Code display appears on the console.
12. Choose from the following options:
v If you want to access DST, select Work with Dedicated Service Tools (DST) and continue to the
next step of this procedure.
v If you want to install or restore Licensed Internal Code, select Install Licensed Internal Code and
continue with the install or restore instructions. For details, see “Utility to install Licensed Internal
Code” on page 166.
v If you want to define the device from which the system LIC should be installed, select Define
alternate installation device. This option also allows you to enable or disable the alternate
installation device.
13. Reapply PTFs. For information on applying PTFs, see Getting fixes.
14. Sign on to DST as QSRV.
Type QSRV as the valid user ID and get the password from the customer. If the customer has changed
the full DST authority user ID or password, ask the customer for the correct values.
The Use Dedicated Service Tools (DST) display appears.
Notes:
v If prompted for a password, be sure to give the new (changed) password to the customer.
v Starting with V5R1, you are limited to three sign-on attempts to DST. After three
unsuccessful attempts, the service tools user ID will be disabled. A user ID with a service
tool security privilege must reset the ID.
Options are limited because the system is in the stand-alone environment. For more information, see
“System paging environments” on page 1 and “DST options” on page 8.This ends the procedure.
Service functions 7
Using function keys in Dedicated Service Tools
The F3, F12, F16, and System Request function keys allow navigation through DST.
The F3 function key
Returns you to the primary menu of the service tool you are using.
The F12 function key
Returns you to the previous DST display.
The F16 function key
Returns you to the Use Dedicated Service Tools (DST) display from the service function you are
in. The active service function is not canceled. To display the service function again, select the
Work with DST environment option.
The System Request function key
Returns you to the Use Dedicated Service Tools (DST) display (on the console). You must type the
following on the system request line:
DST
To exit DST and end all DST functions, perform the following steps:
1. Press F3 (Exit) on the Use Dedicated Service Tools (DST) display. The Exit Dedicated Service Tools
display appears with the following options:
v Exit dedicated service tools (DST)
v Resume dedicated service tools
2. Select Exit dedicated service tools (DST) to exit and end all DST functions.
To exit DST and allow the DST functions to remain active, perform the following steps:
1. Ensure that the system is operating in debug mode.
2. Select the Select DST console mode option on the Use Dedicated Service Tools (DST) display. For more
information on the DST console mode, see “Select DST console mode” on page 28
DST options
DST options vary depending on the paging environment and how you access DST.
For a list of specific options available in each paging environment, see Table 1. For more information on
the system paging environment options, see “System paging environments” on page 1.
For details on accessing DST, see “Accessing Dedicated Service Tools” on page 3.
Table 1. DST options
Paging environment
DST options D-IPL (non-paging) Limited Full
Install Licensed Internal Code Yes No No
Install the operating system No Yes Yes
Perform an IPL No Yes Yes
If your system is a stand-alone environment, refer to “Utilities to install and restore i5/OS Licensed
Internal Code” on page 165.
Attention: If you have logical partitions, you should not use the utilities to install and restore i5/OS
Licensed Internal Code. It can cause damage to the logical partitions and loss of data.
This option installs the operating system from removable media (for example, tape). The present
operating system (if any) is replaced. Use this option to install a new release of the presently installed
operating system or to install the operating system after a failure. You must run this option from the
primary console.
This option is not available under basic DST authority. For more information about authority, see “Work
with service tools user IDs” on page 27.
Perform an IPL
Select the Perform an IPL option from the Use Dedicated Service Tools (DST) display.
This option allows you to install and start the operating system from the disk. If you have installed the
Licensed Internal Code and there is no operating system installed, install and start the operating system
from the same removable media device as the Licensed Internal Code.
Service functions 9
It also allows you to rebuild the Licensed Internal Code, display the Licensed Internal Code information
and PTFs, and display free space. Select this option from the Use Dedicated Service Tools (DST) display.
For more information on Licensed Internal Code fixes and PTFs, see “Fixes and cumulative PTF
packages” on page 164 and the system operation information.
There can be two versions of some Licensed Internal Code modules on the load-source disk unit. The IPL
type (A or B) determines which version of the modules your system uses. When the system is running on
a type A IPL, it uses the original, permanent version. When a Licensed Internal Code fix, or program
temporary fix (PTF) is temporarily applied, the system creates a second version of the module. The
system uses this second version when it is running on a type B IPL.
When the PTF is permanently applied, the side B of the LIC replaces the original side A version of the
LIC module. The system will then use the PTF version of the LIC module (which is now permanent)
when running on a type A IPL.
For PTFs to be activated on each partition, they must be separately applied to each partition.
To apply a PTF that currently has an earlier version applied temporarily on the system, perform an IPL of
the system from the B side (type B IPL). Then load and apply the PTF. The existing temporarily applied
PTF automatically becomes permanent as the new PTF is loaded. If you do not want the existing
temporarily applied PTF to become permanent, remove it manually. For details, see Using IBM i5/OS to
remove the current server firmware level.
If you perform the IPL on the B side when you apply PTFs to Licensed Internal Code, the system applies
the PTFs to the active copy of the Licensed Internal Code.
To run the system with the PTFs, you must perform an IPL. For normal operations, use type B IPL. Use
type A IPL when the B side is not available or when you want to remove a PTF.
Note: There are two copies of some Licensed Internal Code on the load-source disk unit. It is the IPL
type (A or B) that selects the Licensed Internal Code level with which your system will run.
v Rebuild Licensed Internal Code
10 System i and System p: Service provider information Service functions
This option allows you to rebuild the Licensed Internal Code.
v Display Licensed Internal Code
This option allows you to display the following:
– Replaceable unit information (code or object modules)
– Fix information
– Product information
The Fix information option allows you to display the status of the Licensed Internal Code fix (if it is
permanently or temporarily applied). For more information on displaying fixes, see “Displaying
Licensed Internal Code fixes” on page 165.
v Work with free space
This option displays the space available for storing new modules on the system and allows you to
combine the space that is used.
v Remove fixes
To remove Licensed Internal Code fixes, if the PTF is a delayed PTF, the system must be running on
the copy without the changes (type A IPL). Removing these changes causes the system to load the
primary copy over the changes in the changed copy of Licensed Internal Code.
Immediate LIC PTFs can be removed while running a type B IPL.
v Make fixes permanent
To make Licensed Internal Code fixes permanent, the system must be running on the copy with the
changes. When these changes are made permanent, they are loaded into the primary copy of the
Licensed Internal Code.
v Display status (F6)
Press the F6 function key on the Work with Licensed Internal Code display to view the history log.
For more information on PTFs, see “Displaying Licensed Internal Code fixes” on page 165 and the system
operation information.
This option allows you to do the following from the partition from which DST was entered:
v Work with disk configuration.
– Create and update the disk configuration.
– Display the logical structure (disk unit and auxiliary storage pool (ASP) information).
v Work with disk unit recovery.
Note: A graphical interface is available for you to use. See Manage disk unit configuration located in
the Systems management, Disk pools, Configure and manage disk pools topic in the IBM eServer™
iSeries® (http://ibm.com/eserver/iseries/infocenter).
Options and menu flow for the Work with disk units options vary depending on the system paging
environment. For details, see “System paging environments” on page 1. Use Table 2 on page 12 as a
reference during problem analysis and system repair.
Select the Work with disk units option on the Use Dedicated Service Tools display. Options and menu
flow for this function vary depending on the paging environment.
Service functions 11
Table 2. Paging environments and the work with disk unit options
Paging environment Work with disk unit options
Stand-alone 1. Save load-source disk unit data
2. Copy load-source disk unit data
3. Display/change page data
4. Analyze disk unit surface
5. Initialize and format disk unit
6. Reclaim IOP cache storage
7. Stop device parity protection
Limited paging v 1. Work with disk configuration
– Display disk configuration
- Display disk configuration status
- Display disk configuration capacity
- Display disk configuration protection
- Display non-configured disk units
- Display device parity status
- Display disk hardware status
- Display disk compression status
– Work with ASP threshold
– Work with ASP configuration
- Display disk configuration capacity
- Delete user ASP
- Add units to ASP
- Delete ASP data
- Change ASP storage threshold
- Move units from one ASP to another
- Remove units from configuration
- Add units to the ASP and balance data
– Work with mirrored protection
- Display disk configuration
- Start mirrored protection
- Stop mirrored protection
- Enable remote load-source mirroring
- Disable remote load-source mirroring
– Work with device parity protection
- Display device parity status
- Start device parity protection
- Stop device parity protection
- Include unit in device parity protection
- Exclude unit in device parity protection
– Work with disk compression
- Display disk compression status
- Start compression on disk units
- Stop compression of disk units
Service functions 13
Table 2. Paging environments and the work with disk unit options (continued)
Paging environment Work with disk unit options
Full paging 1. Display disk configuration
v Display disk configuration status
v Display disk configuration capacity
v Display disk configuration protection
v Display non-configured units
v Display device parity status
v Display disk hardware status
v Display disk compression status
2. Work with disk configuration
v Display disk configuration
v Add units to ASPs
v Work with ASP threshold
v Include unit in device parity protection
v Enable remote load-source mirroring
v Disable remote load-source mirroring
v Start compression on non-configured units
v Add units to ASPs and balance data
v Start device parity protection
3. Work with disk unit recovery
v Replace configured unit
v Disk unit problem recovery procedures
– Initialize and format disk units
– Display/change page data
– Analyze disk unit surface
v Suspend mirrored protection
v Resume mirrored protection
v Delete disk unit data
v Rebuild disk unit data
v Rebuild IOP cache storage
Options and menu flow for the Work with disk configuration option vary depending on the system paging
environment see “System paging environments” on page 1. Options are:
Display disk configuration
For details on this option, see “Display disk configuration” on page 15.
Add units to ASPs
For details on this option, see “Work with ASP configuration” on page 15.
Add units to ASPs and balance data
For details on this option, see “Work with ASP configuration” on page 15.
Work with ASPs threshold
For details on this option, see “Work with ASP threshold” on page 15.
Display the disk units that are attached to the auxiliary storage pool (ASP) and the status and capacity of
the system auxiliary storage pool.
You can select the display disk configuration option from the main service tools display or the work with disk
configuration display according to the paging environment. From this option, you can display the disk
units that are attached to the ASP and the status and capacity of the system auxiliary storage pool.
Display disk configuration status
Display the status of all ASPs and the disk units that are configured on the system.
Display disk configuration capacity
Display the following for each ASP and the assigned disk units within each ASP:
v Threshold values
v Overflow values
v Protected storage values
v Unprotected storage values
Display disk configuration protection
Display the type of protection for each ASP and the assigned disk units within each ASP.
Display non-configured units
Display the status of all the disk units that are not configured.
Display device parity status
Display the status of the disk unit subsystems that have device parity protection on the system.
For more information on device parity, see “Work with device parity protection” on page 17.
Disable remote load-source mirroring
For details on this option, see “Work with ASP threshold.”
Display disk compression status
Display the compression status of compressed disk units.
Select this option to display or change the threshold for the system ASP. The system issues a notice when
it reaches the threshold value.
The Work with ASP configuration displays allows you to manage disk configuration capacity, delete a
user ASP, and add units to an ASP.
Service functions 15
The following options appear on the Work with ASP Configuration display:
Display disk configuration capacity
Display the threshold and overflow values of the ASP and the assigned disk units. This display is
also available under the Display disk configuration option. For details, see “Display disk
configuration” on page 15.
Delete user ASP
Delete a user-defined ASP (ASPs 2 through 16).
Add units to ASPs
Add non-configured units to an existing ASP. This increases the amount of storage that is
assigned to the system ASP (ASP 1).
Add units to ASPs and balance data
Add disk units to an existing ASP or to create an ASP and add non-configured disk units to that
ASP.
After the disk units are initialized and configured, the data on the other disk units is moved to
equally balance the capacity of all the disk units in the ASP.
Delete ASP data
Delete the data in the ASP.
Change ASP storage threshold
Display or change the threshold for the system auxiliary storage pool (user ASPs are not
supported). The system notifies you when the threshold value is reached.
Move units from one ASP to another
Change the assignment of a disk unit to another ASP.
Remove units from configuration
Remove a disk unit from the ASP configuration. If the unit being removed has data and there is
space in the ASP, the system copies the data to other units in the ASP. If there is not enough
space in the ASP, the system prompts you to delete the ASP data before removing the disk unit.
The unit that is removed becomes non-configured.
Attention: Removing a disk unit from an ASP configuration is space-dependent. There must be
enough space on the remaining units to accommodate the data from the unit being removed.
Select this option to display or change mirrored protection on the disk units.
Display disk configuration
For details on this option, see “Display disk configuration” on page 15.
Start mirrored protection
This option allows you to start mirrored protection on the selected ASP.
Stop mirrored protection
This option allows you to stop mirrored protection on the selected ASP.
Enable remote load-source mirroring
Select this option to turn on the ability to physically place the two units that make up the
mirrored load-source disk unit (unit 1) on different input-output processors (IOP). This option
does not start mirrored protection.
Device parity protection is a data redundancy feature available on some storage media units.
Select this option to perform the system functions that handle device parity protection on the system. It is
maintained across all the units that are within the parity set. If one unit fails, the units within the set
handle the functions for the failed unit. This type of protection can improve system availability and
reduce the possibility of data loss. The following options are available:
Display device parity status
Select this option to show the status of disk unit subsystems that have device parity protection.
For an example, refer to Figure 2 on page 18.
Start device parity protection
Use this option to begin the process of protecting data on the system. Options include:
v Start device parity protection - RAID 5
v Start device parity protection - RAID 6
v Start device parity protection - RAID 5 with hot spare protection: This option automatically
starts and configures RAID 5 with hot spare protection.
v Start device parity protection - RAID 6 with hot spare protection: This option automatically
starts and configures RAID 6 with hot spare protection.
Stop device parity protection
This option allows you to end device parity protection.
Include unit in device parity protection
This option allows you to add an unprotected disk unit to an existing parity set.
Exclude unit in device parity protection
This option allows you to remove a disk unit from a parity set.
Select parity optimization
This option allows you to optimize parity.For an example of the options, refer to Figure 3 on page
18.
Service functions 17
Examples of device parity status screens
1. Availability
2. Balance
3. Capacity
4. Performance
Select this option to display disk compression status, or select this option to start or stop disk
compression.
Options are available to save and restore disk units, find and assign disk units that are missing from the
configuration, replace disk units, reclaim IOP cache storage, and recover the system configuration if it is
lost, destroyed, or changed.
Select the Work with Disk Unit Recovery display from the Work with disk units option on the Use
Dedicated Service Tools (DST) display. Options are available to save and restore disk units, find and
assign disk units that are missing from the configuration, replace disk units, reclaim IOP cache storage,
and recover the system configuration if it is lost, destroyed, or changed.
Save disk unit data
Run this option when the disk unit reference code (URC) indicates that a disk enclosure should
be exchanged.
Before removing the disk enclosure and installing a new disk enclosure, save the data from the
disk units in the disk enclosure to removable media.
When the system has saved all of the disk unit data to removable media, a menu appears on the
display with the status information.
Notes:
v This procedure does not save the Licensed Internal Code on the load-source disk unit.
v The option is not available for disk units that have device parity protection or mirror
protection (with both units in an active state).
Restore disk unit data
This option reads the data (recorded using the Save disk unit option) from the removable
medium and writes the data on the disk unit. The data can be restored to a disk unit of the same
type or to a different type of disk unit that has the same or larger storage capacity. When all data
is restored to the disk unit, a menu appears on the display with the status information. If the
replaced disk is load source, the system will perform an IPL to DST from the new disk. For the
others, the system will not perform a re-IPL.
For systems with multiple partitions, the partition configuration will have to be restored first.
Replace disk unit
This option is part of the disk unit recovery procedure. It allows you to exchange a configured
disk unit with a non-configured unit. Use the Delete ASP data option to clear the system ASP
before replacing the disk unit only if the disk is not under mirror or device parity protection. You
can make the protection active again after replacing the failed disk by following the Disk Unit
Recovery Procedure.
Assign missing units
This option reports any missing units (units that were part of the system during the last IPL that
have been disconnected accidentally or configured differently). When you select to assign a unit,
the system attempts to find one or more valid non-configured disk units. If no valid
non-configured disk units are found, use the Replace disk unit function.
Recover disk configuration
This option recovers the correct system configuration in cases where the load source was
damaged and the device configuration table on the installation device was lost.
Service functions 19
Disk unit problem recovery procedures
For details on this option, see the main heading “Disk unit problem recovery procedures” on
page 21.
Suspend mirrored protection
Select this option when you want to stop mirrored protection for a unit in a mirrored auxiliary
storage pool.
Resume mirrored protection
Select this option when you want to restart mirrored protection for a unit in a mirrored auxiliary
storage pool.
Copy disk unit data
This option allows you to copy all the data from a configured disk to a non-configured disk unit.
This action can take the place of save disk unit data to tape and a restore disk unit data. After the
operation is complete, the target disk unit (the one copied to) takes the place of the original disk
unit in the system configuration. The original disk cannot be used in the system configuration
without data loss.
Delete disk unit data
This option allows you to delete all the data from a non-configured disk unit.
Attention: If there are several disk unit incompatibilities, make certain that the correct units are
installed.
Reclaim IOP cache storage
When the IOP cache memory fails and needs to be replaced, this option allows you to remove
and destroy the damaged data in the IOP cache.
Data can remain in the IOP cache when failures occur. Occasionally, a situation is so severe that
the system perceives missing units. This prevents the system from performing an IPL. At other
times, a reduction in the amount of usable cache storage occurs. This situation presents itself only
as a warning during a manual mode IPL.
Correct device parity protection mismatch
This option allows you to accept the situation where configured disk units are expected to have
device parity protection enabled but currently have device-parity protection disabled. The
configuration will no longer expect these disk units to be device parity protected.
Recover unknown load source
This option allows recovery from an unknown load-source error where the mate of the load
source in the mirrored pair is missing and the system does not currently recognize the load
source.
Note: For load-source disks in remote load-source mirrored pairs, use the Recover mirrored load
source option.
Recover mirrored load source
This option allows you to recover from a local load-source failure.
Remote load-source mirroring support must be started.
This option allows you to select functions that assist in problem isolation and repair actions.
Note: Only the disk units that are available for a specific function are displayed.
Initialize and format disk units
Use this option when the disk unit reference code indicates that reallocations have failed because
no other space is available. All the ID fields on the disk unit are written again. Running this
option erases all the data from the disk unit. This option is not available for the load-source disk
unit.
Display/change page data
Use this option as follows:
v The results of the Analyze disk unit surface option (under the Work with disk unit recovery option)
show which pages have data check conditions. Use the Display/change page data option to assign
those sectors to new locations on the disk.
v To inspect and change the 64 bytes of page header, if necessary.
v To inspect and change the 4096 bytes of page data, if necessary.
The Display/change page data option has the following functions:
v Reading data from a selected page.
v Displaying the data in hexadecimal and EBCDIC formats.
v Allowing the hexadecimal data to be changed and written to the page again.
v Displaying the 64-byte page header in formatted form.
v Allowing the 64-byte page header to be changed and written to the sector again.
v Allowing the sector to be assigned to a new location on the disk.
v Displaying the disk unit reference code after each operation.
Analyze disk unit surface
This option performs a read/verify operation on the selected units. Pages that report disk URCs
indicating data check errors can be assigned to new locations on the disk using the Display/change
data option. The results of the analysis can be displayed on the console.
Protect your disk units with hot spare device parity protection.
Concepts for using device parity protection with hot spare disk units:
Device parity protection hot spare disk units are spare disk units stored on a system to replace failed
disks in case a disk failure occurs.
A hot spare disk unit is stored on the system as a non-configured disk. When a disk failure occurs, the
system exchanges the hot spare disk unit with the failed disk unit. Both of the disk units must be the
same capacity for a Small Computer System Interface (SCSI) IOA, or the same or larger capacity for a
Service functions 21
Serial Attached SCSI (SAS) IOA, and under the same IOA in order for the exchange to occur. After the
exchange occurs, the system rebuilds the data on the new disk unit.
There are two ways to include the hot spare disk units in your system.
1. You can configure the hot spare disk unit when you initially start device parity protection. For details
on how to include hot spare disk units when starting device parity protection, see “Starting device
parity protection with hot spare protection.” When selecting this option, the system automatically
determines if one or two hot spares should be created and which available disk units are selected
based on the total number and capacity of disk units attached to the IOA.
Note: When you start device parity protection with hot spare disk units, the disk units are not
designated to any particular parity set. The hot spare disk unit protects the first failed disk unit
that has parity protection, is the appropriate capacity for the hot spare, and is under the same
IOA as the hot spare.
2. You can create a hot spare disk unit from non-configured disk units on your system. For details on
how to include hot spare disk units to your system, see “Starting hot spare protection” on page 23.
When selecting this option, you should determine if one or two hot spares are desired and which
available units will become hot spares based on the total number of disk units attached to the IOA
and their capacity.
Costs and limitations of device parity protection with hot spare disk units:
There are costs and limitations to consider when using device parity protection with hot spare disk units.
v Hot spare disk units only protect parity sets with the same capacity disk units for SCSI IOAs, or only
protect parity sets with the same or smaller capacity disk units for SAS IOAs.
v To create a new RAID 6 parity set with hot spare disk units, a minimum of five disk units is needed. If
there are not at least five disk units, then the system will recommend the creation of a RAID 5 parity
set with hot spare instead.
To use hot spare protection for your parity protected disk units, the following requirements must be met:
v The disk units must be parity protected.
v The hot spare disk unit must be under the same IOA as the disk units that you want protected.
v The hot spare disk unit must be the same capacity as the failed parity protected disk unit (for SCSI
IOAs) or must be the same or larger capacity as the failed parity protected disk unit (for SAS IOAs).
v When an IOA controls the load source disk unit, the hot spare disk unit must be in a valid load source
location. This may require additional planning when using a SCSI IOA since the valid load source
locations are typically a subset of the possible disk unit locations within the enclosure. The system will
not allow the Start device parity protection with Hot Spare to occur if this requirement is not met.
v The hot spare disk unit must be a non-configured and unprotected disk unit.
You can use the system service tools (SST) to set up hot spare device parity protected disk units.
You can start device parity protection with hot spare protection using the system service tools (SST).
1. Start System Service Tools (STRSST), and specify the user name and password.
Note: If there is a sufficient number of hot spare disk units already available, the system will not
create any additional hot spare disk units.
You can start hot spare protection using the system service tools (SST).
You can use the system service tools (SST) to manage your hot spare device parity protected disk units.
You can stop hot spare protection using the system service tools (SST).
You can determine which parity sets are hot spare protected using the system service tools (SST).
To determine which parity sets are hot spare protected, follow these steps:
1. Start System Service Tools (STRSST), and specify the user name and password.
2. On the System Service Tools (SST) display, select Work with disk units.
3. On the Work with Disk Units display, select Work with disk configuration.
4. On the Work with Disk Configuration display, select Work with device parity protection.
5. On the Device parity protection display, selectDisplay disk configuration .
6. On the Display disk configuration display, select Display Device Parity Status.
Service functions 23
Displaying hot spare status:
You can use the system service tools (SST) to display hot spare status.
Identify some common conditions associated with hot spare device parity protection and failed drives.
If you are having trouble starting hot spare protection or device parity protection with hot spare
protection
Ensure the following:
v There is an adequate number of disk units attached to the IOA which could become hot spare
disk units.
v The disk units to become hot spares are in Non-configured status (not part of a disk pool).
v The disk units to become hot spares are of appropriate size to protect the disk units in the
parity sets under the IOA.
v If the desired IOA is the load source IOA, the disk units to become hot spares must be installed
in a valid load source location for the specific enclosure.
Notes:
v If you move a non-configured disk unit to a valid load source location and it is not
shown as capable of becoming a hot spare, you may need to initialize or format the
disk unit in its new location in order for it to become a hot spare.
v If the option to start device parity protection with hot spare protection is selected and
the above requirements are not met, the desired IOA will not be shown as capable of
starting device parity protection.
v If the option to start hot spare protection is selected and the above requirements are not
met, the desired disk units will not be shown as capable of becoming hot spares.
To identify a failed disk unit which was automatically replaced by a hot spare
When a device parity protected disk unit fails and the automatic rebuild to the hot spare has
started or completed, the failed disk will have a status of Not operational or Read/Write
protected. Follow normal disk unit service and recovery procedures for replacement of the failed
disk unit.
To identify if a hot spare disk unit itself has failed
When a hot spare disk unit fails, the failed disk will have a status of Not operational or
Read/Write protected. Follow normal disk unit service and recovery procedures for replacement
of the failed disk unit.
The Work with Dedicated Service Tools Environment display includes the following options:
Service functions 25
Work with active service tools:
This option shows the status of the active service functions. Service functions can be started and left
active while you start another service function.
Select this option from the Work with Dedicated Service Tools Environment display.
Note: The Work with active service tools option is also available from the System Service Tools (SST) display.
Use this option to work with a service function you left active. The status of a service tool can be active,
ending, or no. A no status indicates that there are no displays pending.
The following options appear on the Work with Active Service Tools display:
Display
This option allows you to work with an active service tool. You can select only one active service
tool.
End service tool
This option ends an active service function. A service function in the process of ending cannot be
selected.
Option
Type the desired option number in this field next to the active service tool name you are
displaying or ending.
Use this option to select the output printer, tape, or optical device and the console type.
Before you select an option on the Work with System Devices display, ensure the following is true:
v If you have a printer available, ensure that it is connected and configured to the same I/O processor or
storage media unit as the workstation.
v If you have a tape or optical device storage unit available, ensure that it is installed, connected to the
system, and configured correctly.
On the Select Output Printer display, the Select Tape display, or the Select Optical Device display, the
system completes the following fields:
Resource Name
A name that is assigned by the system to identify a specific device, I/O processor, or
communications device.
Type A number that is assigned by the manufacturer to identify the specifics of a printer, tape, or
optical device unit.
Model The model number of the printer, tape, or optical device unit.
Serial A number that is assigned by the manufacturer to identify a specific printer, tape, or optical
device unit.
If no printer is available for this workstation I/O processor, you must select a different output device
(such as a tape unit) for the service tool to use.
If the device you selected is already being used by a job, do one the following:
v Press Enter to cancel the job and use the device for the service tool.
v Press F12 (Cancel) to cancel this device selection and then select a different device.
26 System i and System p: Service provider information Service functions
Selecting console type
This option allows you to choose from the following console types:
Note: These changes will take effect only after performing an unattended IPL.
v 1= twinaxial console
v 2= Operations console (Direct)
v 3= Operations console (LAN)
v 4= Hardware Management Console (HMC)
Service tools user IDs control access to DST functions, System Service Tools (STRSST command), and
Licensed Internal Code service functions. When a Service tools user ID is changed, the old ID is replaced
with the new one.
Service functions 27
Table 3. Service tools user IDs (continued)
Privilege Description QSECOFR QSRV ″22222222″ ″11111111″ default
(full) (basic)
Start Service Tools x x x
Note: The default column is for reference in the event a user creates a new service tools user ID without
changing any of the privileges.
Table 4. Device ID
Privilege Description QCONSOLE default
LAN attached console x x
Remote operator panel x
Remote console panel x
Note: The default column is for reference in the event a user creates a new service tools user ID without
changing any of the attributes.
You can work with system values using the Hardware Management Console (HMC) or the Advanced
System Management Interface.
To work with system values using the HMC, see Viewing information about a managed system.
To work with system values using the Advanced System Management Interface (ASMI), see Viewing vital
product data.
Attention: If the system has logical partitions, contact your next level of support before changing the
system serial number. The logical partition configuration information will be impacted.
Two pieces of media are involved in such an installation: the alternate IPL load source (usually an optical
device) and the alternate installation medium. The alternate installation medium contains the Licensed
Internal Code that will be installed or restored on the system. The alternate installation medium is placed
on any bus.
To enable an alternate installation IPL, select the DST option Work with alternate installation device. This
option is available in DST from control panel function 21 or a type D manual IPL.
Notes:
1. When an alternate bus load source is defined, the LIC also performs an IPL on this bus and
IOP for main storage dump IPLs and as a possible dump device.
2. If no alternate load source is defined for the alternate installation, the LIC performs an IPL
only on the IOPs on bus 1 and uses the IPL load source.
Selecting the Select DST console mode option while you are in the full paging environment causes the
operating system display to be restored. Any active service functions remain active, and any device that
was allocated to the service tool remains allocated.
The DST Console Mode display includes options to exit DST and to start DST in debug mode.
Exit Dedicated Service Tools (DST) on IPL
Service functions will not interrupt the console display unless you have already set debug mode.
Sign-on is necessary to access DST. All active service functions end.
Start DST in debug mode on IPL
Service functions can interrupt the normal operating system process to display debug
information. When an operating display appears, you can enter DST by performing the System
Request Key procedure. This allows the Use Dedicated Service Tools (DST) display to appear
without requiring you to sign on to DST. For more information on the System Request Key
procedure, see “Using the System Request Key” on page 5.
Select the Start a service tool option from the Use Dedicated Service (DST) Tools display.
Note: The Start a service tool option is also available from the System Service Tools (SST) display.
Display/Alter/Dump:
Note: The Display/Alter/Dump option is also available under System Service Tools (SST).
This option allows you to display or change virtual storage data. It also allows you to dump the data to
removable media (tape or optical) or a printer.
You can then use an output device to perform the following tasks:
v To view the data from storage on the screen:
Service functions 29
– Select the Display/alter storage option to display unformatted data and to change the contents of
storage. Use the keyboard to scroll forward or backward to view the storage information.
– Select the Display/alter storage option to generate a formatted dump of the contents in storage. The
screen is inhibited while the format function is running. When the formatting process is complete,
use the keyboard to search, scroll (forward or backward), or shift (left or right) the output.
v To generate a formatted dump of the data in storage to an output device.
– Select one of the following:
- Dump to printer
- Dump to media
When the output device is a printer or media, the actual dump task runs asynchronously with the
Display/Alter/Dump control functions. That is, while a dump is completing on a printer or media,
you can operate the display/alter function (output device is the display), or you can make other dump
requests for a printer or media. The system saves dump requests in a first-in-first-out queue and
processes them one at a time. To display the status of the Display/Alter/Dump asynchronous dump
task, select the Display dump status option on the Display/Alter/Dump Output Device display.
v To generate a printout from media that contains data from the Display/Alter/Dump function or from
other Licensed Internal Code service functions, select the Print media dump file option on the
Display/Alter/Dump Output Device display.
Note: When you exit the Display/Alter/Dump function, the dump request that is running is ended (even
if it has not completed). Unprocessed dump requests are lost.
Note: The Licensed Internal Code log option is also available under System Service Tools (SST).
This option allows you to work with Licensed Internal Code (LIC) log information. Use this option to
perform the following:
v Select specific log entries
v Dump selected Licensed Internal Code log entries to a printer or removable media (tape or optical)
v Change the following Licensed Internal Code log attributes:
– The maximum number of entries
– The size of the note log area and the size of the dump log area
– The maximum size for dump entries
v Clear the Licensed Internal Code log
v Display the status of the Licensed Internal Code log dumps that are not complete
The dump tasks (one for printer and one for media) run asynchronously from the control functions for
this tool. Requests are saved in a first-in-first-out queue, and there is no practical limit to the number of
Note: The Licensed Internal Code trace option is also available under System Service Tools (SST).
This option allows you to activate (resume) or deactivate (suspend) a trace of the Licensed Internal Code
so that you can gather information on the internal operation of Licensed Internal Code. Trace data can be
collected by:
v Component
v Machine interface
v Multi-programming level (MPL)
v Transaction
v Task and thread performance data
The trace is placed in a trace table. Information in the table can be displayed or dumped to a printer. This
command also allows you to create, allocate (size), clear, or delete a table.
Note: The Hardware service manager option is also available under System Service Tools (SST).
This option allows you to display, work with, and print the stored hardware resources information. For
more information on the Hardware Service Manager function, see “Hardware Service Manager” on page
43.
Notes:
v The Main storage dump (MSD) manager option is also available under System Service Tools
(SST).
v The Main Storage Dump Manager display is available when you press Enter on the Main
Storage Dump Occurred display.
The main storage dump manager manages and processes main storage dumps. It allows you to copy
main storage dump information and work with the current main storage dump. The current main storage
dump is the latest dump on the system. It is stored on the load-source disk.
Attention: If you do not copy the dump data on the load-source disk to removable media or the Main
storage dump (MSD) library, it will be replaced by the next main storage dump and lost at the next IPL.
An MSD library is available to access copies of main storage dumps are stored in auxiliary storage. The
dumps that are held in the library can be from the system on which you are working or from another
system.
Service functions 31
v Display or print a copy of a main storage dump
v Copy a current main storage dump to removable media
v Copy a current main storage dump to the MSD library
v Copy a main storage dump from the MSD library to removable media
v Copy a main storage dump from removable media to the MSD library
An MSD library is available to access copies of main storage dumps. The contents of the library are
stored in auxiliary storage. The dumps that are held in the library can be from the system on which you
are working or from another system.
When entered from the Main Storage Dump Occurred display, the Main Storage Dump Manager may
also allow you to:
v Activate the remote service support communication line. For more information, see “Activating remote
service support” on page 42.
v Work with system partitions. For more information, see “Work with system partitions” on page 42.
v Dump all partitions.
You can display a current MSD or an MSD that has been copied to the MSD library. The Display Main
Storage Dump display allows you to display or print:
v MSD summary
v System data
v Processor data
v Hardware data
v Licensed Internal Code module data
v MSD by address
v MSD by data
To ensure that the current MSD information is available for problem analysis, you must copy the dump.
For details on how to use the copy options under the main storage dump manager function, see
“Copying a main storage dump” on page 204.
Program temporary fixes (PTF) repair problems that appear to be hardware problems. Your next level of
support can assist you in determining whether you need to copy a dump or if a PTF is available for your
problem.
For more information on main storage dumps, see “Working with Storage Dumps” on page 203.
Note: The Product activity log option is also available under System Service Tools (SST).
This option allows you to display or print data (system, Licensed Internal Code, software components,
subsystem, and I/O device data) that has been logged. It also provides data summaries, allows data to be
sorted, and allows you to work with removable media statistics. For more information on the functions of
the product activity log, see “Product Activity Log” on page 92.
Note: At the next IPL, a file rebuild might be necessary. For more information on a file rebuild, go to
Collecting reference codes and system information.
This option allows you to gather detailed information about system performance. Select Performance
data collector only if directed by your next level of support.
After you select the Start option, the collector data is placed in temporary storage. When the collector is
stopped, you can copy the data to tape by selecting the Get data option on the Work with Performance
Data Collections display. To delete the data from storage, select the Delete option on the Work with
Performance Data Collections display. The data is automatically erased at the next IPL.
The Work with communications trace option is only available under System Service Tools (SST). Select
this option from the Start a Service Tool display.
This option allows you to start or stop a communications line trace on a configuration object.
After you run the trace, the data can be formatted. You can view the formatted data by printing it.
Running and interpreting the communications trace requires detailed knowledge of communications
protocols. To obtain the most accurate sample of your line status, whenever possible, start the
communications trace before varying on the lines.
Note: Online help from the Work with Communications Trace display allows you to view a list of
protocols.
The Work with Communications Traces display has the following options and function keys:
Service functions 33
Start trace (F6)
This function key allows you to start tracing the data on a communications configuration object.
The Start Trace display appears after you press this function key. For more information, see
“Starting a trace” on page 37.
Stop trace (option 2)
This option appears only on the Work with Communications Traces display. It allows you to end
the trace and stop collecting data. A trace must be stopped before you can format, print, or delete
the data. To ensure that the trace is stopped, press the Refresh function key and check the trace
status field.
Delete trace (option 4)
The trace must be stopped (option 2) before you can use this option. Select this option to delete
the trace information when you no longer need the data. Traces are not automatically deleted
when you leave a communications trace function. Delete trace releases system space so that you
can start other traces without having to increase the maximum amount of storage provided for
the communications trace. Traces that are not deleted are listed on the Work with
Communications Traces display.
Format and print trace (option 6)
Use this option to format and print the trace. For more information on the Format and print trace
option, see page “Format and print trace” on page 35.
Display message (option 7)
Use this option to view a message that indicates the status of the trace that stopped because of an
error.
Restart trace (option 8)
Use this option to start a trace that has been stopped.
Change size (F10)
Use this function key to change the amount of storage that all traces use. You might want to
increase the amount of storage, if your system has many active traces or traces that will be active
for a long time.
Display buffer size or display trace status (F11)
This function key allows you to select and alternate between buffer size and trace status.
Refresh (F5)
This function key updates the data on the display.
Status conditions
After the Work with communications trace option is selected from the Start a Service Tool display, the
Work with Communications Traces display appears.
Configuration
Opt Object Type Trace Description Protocol Trace Status
_ LosAngeles Line Test LosAngeles Line SDLC Active
_ Mpls NWI Test Mpls ISDN Stopped
_ Tucson Line Test Tucson Line ASYNC Waiting
Details of the trace, including status, are displayed. The trace status can be one of the following:
Condition description
Waiting
The trace is waiting for the configuration object to be varied on (not collecting data).
Active The trace data is being collected.
Stopping
The trace is stopping.
Stopped
The trace has stopped (not collecting data).
Error An error occurred on the configuration object while the trace was collecting data. The data might
or might not be collected. The trace stopped.
Starting
The trace is being started by another user. You cannot stop or delete this trace.
Formatting
Trace is being formatted.
You must select the Stop Trace option before you format or print the trace. The Format and print trace
option allows you to select various formatting options and prepare the trace data for printing. The
options vary for each protocol. The following is an example of the Format Trace Data display:
Service functions 35
Format Trace Data
Type . . . . . . . . . . . . . . LINE
Notes:
1. To view all the data associated with the trace, press Enter without changing to the defaults on
the Format a Trace Data display. The information is not in any special format.
2. Select the option to format and print only the data that you want to see.
3. All options available for formatting depend on the protocol of the line that is being traced.
4. Not all combinations of options are valid for all protocols.
5. For more information about these options, use online help.
When the format of the trace data is complete, the output can be printed on the console printer (the
printer that is attached to the same I/O processor as the console). Only SCS-type data streams are
supported. If i5/OS is available, the trace might be in the job spooled files.
The width of the file is 132 characters. The data is in hexadecimal representation and either American
National Standard Code for Information Interchange (ASCII) or EBCDIC character representation. The
columns of the trace output common to all protocols are:
Record number
The number of the trace record. Shows if the record type is sent (S) or received (R).
Notes:
1. The letter C in this column indicates that an X.21 short hold mode connection was
cleared.
2. The letter M in this column indicates a modem change has occurred.
Data length
The amount of data, in decimal, that the record contains.
Record status
The protocol-dependent return code for the trace record. 00000000 is successful; no errors were
found. Other return codes are listed in the functional specification for the protocol that is running
or the port manager.
Record timer
The time that each event occurs. Depending on the communications hardware that is being used,
the record timer will be either:
1. A time of day value, HH:MM:SS.NNNNN (where H=hours, M=minutes, S=seconds, and
N=subseconds), based on the system time when the trace was stopped.
2. A relative time in decimal seconds. This timer value provides the relative time between
events.
Data type
Shows whether the traced data is printed in ASCII or EBCDIC character representation. If the
character representation of the data is mostly periods, you might want to format the data again
using the other option for data representation.
Controller name/number
Indicates which controller originated the frame or record. In some conditions, this data is not
available, and the column remains blank.
Starting a trace:
The Work with Communications Traces display has a Start Trace function key that allows you to select
options for tracing data.
On the Start Trace display, enter the name of a communications configuration object description at the
Configuration object prompt:
v For i5/OS operating systems:
If you do not know the name of the configuration object, the work with configuration status
(WRKCFGSTS) command allows you to view a list. You can view line, controller, or network
information by entering the *LIN, *CTL, *NWI, or *NWS parameter.
You can also use this command to vary off a line and all the I/O processors and devices under it.
Describe the trace in the Trace description field. This field can help you identify the trace.
You can select a buffer size to hold the communications data that the trace collects. The default buffer
size is 1=128K bytes. Base the size of the buffer on the speed of the communications line and on the
amount of time necessary to trace the data. For high-speed lines or long periods of tracing, use a larger
buffer size.
If you specify Yes in the Stop on buffer full field, the trace stops when the buffer is full. This option is
useful for viewing the initial data that is coming across a line. If you specify No, the trace continues until
you stop it. In this case, the data in the buffer will be written over each time the buffer is full.
You can select the direction of data to be traced by specifying one of the three selections in the Data
direction field:
v Only data that the system is sending (option 1)
v Only data that the system is receiving (option 2)
v Both the data sent and received by the system (option 3)
Note: If you specify option 1 (Sent) for lines that are in SDLC short hold mode, the trace does not
include controller names.
You can select how much data is traced in a frame of data. The value that is entered is the amount that is
saved as part of the trace. The minimum value that is allowed for both the beginning and the end value
is 36 bytes. Those 36-byte minimum values include the protocol header. The configuration object you are
tracing determines the maximum value that is allowed.
Notes:
1. The BSC protocol ignores the beginning and ending byte values.
When all required options are complete, press Enter. The Work with Communications Trace display
appears.
If the communications object being traced is in varied off status when you start the trace, the trace
remains in waiting status until you vary the communications object on. If the object is varied on, the trace
will immediately go to the active state, and the system will begin to collect trace data.
Note: While the trace is active, you can exit the communications trace function to do other work.
Traces are not automatically deleted when you exit a communications trace function. To return to the
communications trace:
1. Select the Start a service tool option from the service tools (SST or DST) display.
2. Select the Work with communications traces option.
3. From the Work with Communications Traces display, you can check the status of the trace or select to
stop the trace.
Only two communications traces can run concurrently on one communications controller. Only one trace
can exist for the same configuration object at the same time. If i5/OS is available, access SST to trace
more lines.
Although a communications trace can start before or after the configuration object is varied on, if it is
important to see the starting information coming across the configuration object, you must start the trace
before varying on the configuration object.
Two or more users can select the same trace to format and print. When multiple users attempt to use the
same resources (trace data), one user must wait for the other user to finish before beginning to process
the data.
When the system is configured as an SDLC secondary station on a multipoint configuration object, the
communications controller traces all records or frames.
The records or frames sent to the system include those records and frames intended for other stations.
When you use the communications trace service tool to format the data for this configuration, the
resulting report might show received records that were intended for other stations.
On a single point-to-point line, where only one secondary station is configured, SDLC traces all frames
received before it gets the frames intended for other station addresses. It is not until the secondary SDLC
receives the other station addresses that it knows which single-station address the communications
equipment uses.
Service functions 39
LAN communications trace considerations:
Trace options are provided for some of the LAN protocols that allow you to select, at trace start time,
which data to trace.
For example, you can start a trace to collect data for only a specific remote controller. Selecting one of
these trace options when starting a trace will result in less trace data and reduce the need for a large
trace buffer.
Trace-filtering options are not available for all LAN communications adapters. If the adapter does not
support filtering, all data will be traced, and the following informational message will appear in the
prologue of the formatted trace: Trace Options not supported. All data was traced (no filtering).
Results
This option allows you to install the operating system, selecting from the following devices:
v Tape
v Optical media
v Virtual optical - preselected image catalog
Note: When your system is in the full or limited paging environment (see “System paging environments”
on page 1), the appearance of the Perform an automatic installation of the operating system option
varies depending on the operating system. For more information, see “i5/OS operating system” on
page 210.
You can use the tape or optical device to restore the Licensed Internal Code after a failure.
Note: When your system is in the full or limited paging environment (see “System paging environments”
on page 1), the appearance of the Save Licensed Internal Code option varies depending on the
operating system. For more information, see “i5/OS operating system” on page 210.
The Work with save storage and restore storage option allows you to perform the following:
v Restore all system auxiliary storage (except Licensed Internal Code)
v Resume a restore storage process that was interrupted
v Force the end of an interrupted restore storage process
v Resume a save storage process that was interrupted
Note: When your system is in the limited paging environment, the appearance of the Work with save
storage and restore storage option varies depending on the operating system. For details on
system paging environments, see “System paging environments” on page 1. For more information,
see “DST in i5/OS limited paging environment” on page 211.
The Work with remote service support option allows you to:
v Test remote service communications
v Activate and deactivate remote service support communication line
v Work with the security log (shows remote service activity)
v Change service attributes
Selection
_
F3=Exit F12=Cancel
Through remote service support, DST functions that would typically be available only at the local system
console can be accessed from a remote site. Remote service support requires the following:
v An electronic customer support communications line.
v The system at the local site must be at DST (that is, perform an IPL to DST), or past DST.
v Remote service support must be enabled and activated at the local site. For details, see “Allowing
access for remote service support” and “Activating remote service support” on page 42.
For more information on remote access support, see AS/400® Remote Access Support (SC41-0596).
Before you begin a session, remote service support must be allowed access by the system.
Note: The system is shipped with remote service access disabled (not allowed). After remote access is
set to 1 the first time, it remains set until you select 2 (not allowed) or the system is restored.
The system operates normally with remote access in either state (allowed or not allowed).
3. The system now allows a remote service support session. To activate a remote service support session,
see “Activating remote service support” on page 42.
Service functions 41
This ends the procedure.
Remote service support enables you to securely give the service and support organization access to your
server to enable problem analysis and determination.
Before you can activate a session, you must allow access for remote service support. For details, see
“Allowing access for remote service support” on page 41. After you have allowed access for remote
service support, you can activate remote service in one of the following ways:
v Perform Function 66 (Activate Remote Service) on the control panel. For details, see “Function
66–Activate remote service” on page 148.
v Select the Activate remote service support communication line option on the Work with Remote Service
display by performing the following procedure:
Note: Electronic customer support is not available while DST remote service is active. For more
information on electronic customer support, see the system operation information.
1. Select the Work with remote service support option on the Use Dedicated Service Tools (DST) display.
2. Make a note of the current mode setting on the modem. Then select the Activate remote service support
communication line option from the Work with Remote Service Support display. This activates the
communications line and sets the modem to asynchronous mode.
3. When the service provider ends the remote service session, the console is available for normal DST
operations.
Note: If the console is input-inhibited after the service provider ends the remote service session, select
Function 21 to make DST available again.
4. Select the Work with remote service support option from the Use Dedicated Service Tools (DST) display.
5. Select the Deactivate remote service support communication line option from the Work with Remote
Service Support display to release the communications line.
Note: Releasing the line does not reset the modem mode. Remote service uses asynchronous mode. If
the modem was originally set to a mode other than asynchronous, you must manually select
the mode again.
This ends the procedure.
You must use the Hardware Management Console (HMC) to work with system partitions.
For information on working with logical partitions, see Managing i5/OS logical partitions.
For general information on logical partitions, see General concepts for partitioning the server.
For information on servicing logical partitions, see “Logical partitions” on page 129.
The Work with system capacity option allows you to perform the following:
v Display system capacity information
Through this interface, you can activate additional processors (Capacity Upgrade on Demand) to handle
increased workload.
Select Work with system security from the Use Dedicated Service Tools (DST) display or the System
Service Tools (SST) display to manage system security options. There are three settings that can be
changed on the Work with System Security display:
Allow system value security changes
This option controls whether CHGSYSVAL can be used to change security-related system values (see
the onscreen help for a list of these values).
Allow new digital certificates
This option controls whether the Add Verifier (QYDOADDV) API can add digital certificates and also
whether passwords for digital certificate stores can be reset.
Allow a service tools user ID with a default and expired password to change its own password
This option controls whether service tools user IDs with a default or expired password can
change their password during SST sign-on or with the QSYCHGDS API. When set to ’No,’ the
password can only be changed from DST or by using the QSYCHGDS API with a requesting user
that has the necessary authority.
Select End batch restricted state to end the batch job running in restricted state and start the controlling
subsystem. This option has no effect if the system is not in batch restricted state.
You can select the Hardware service manager option from the Start a Service Tool display. It allows you
to display and work with system hardware (logical or packaging) and debug input-output processors
(IOP) and devices.
Service functions 43
Hardware Service Manager
Bottom
Selection
Figure 8. Example Hardware Service Manager display (in the full and limited paging environments)
Note: The system power control network (SPCN) option appears only on systems with SPCN.
Note: For details on how to interpret the Release field, see “Determining the dominant operating
system” on page 123.
v A list of the Hardware Service Manager options
Note: The options available vary depending on the system type and paging environment. For details,
see “Hardware Service Manager options.”
v Function keys
Note: The function keys vary depending on the display that is shown. For information on how to use
them to collect information, see “Collecting information and performing functions from the
Hardware Service Manager displays” on page 58.
For more information on the system configuration and resources, see “System architecture and
configuration” on page 168 and “Resource names” on page 175.
This option allows you to display and work with packaging resources. Packaging hardware resources are
the physical resources of the system. The display lists them by their physical location within the system.
Some packaging hardware resources contain other packaging hardware resources within them. For
example, a frame might contain a card enclosure, and the card enclosure might contain cards. To display
these resources, select the Hardware contained within package option on the Packaging Hardware
Resources display.
The Packaging Hardware Resources display shows packaging hardware resources in levels that begin
with the system resource. The Packaging Hardware Resource display shows all associated first level
hardware resources. To see the resources contained within a packaging hardware resource, select the
Hardware contained within package option on the packaging resource that has a “+” symbol next to it. For
more information on symbols, see “Symbols on the Hardware Service Manager displays” on page 88.
Service functions 45
Note: The Hardware contained within package option will not be valid for a remote system unit since
no packages for hardware within them will be created. This is because HRI will not see VPD from
any resources within a remote system unit or remote expansion unit.
Type- Resource
Opt Description Model Unit ID Name
System 9406-570 U9406.570.102F1BC SYS01
System Unit + 7879-001 U7879.001.11315CC FR02
System Unit + 7879-001 U7879.001.112F1BC FR01
System Expansion Unit + 0595-002 U0595.002.104741C FR05
Virtual IOP + < 268C-001 U9406.570.102F1BC P51
Tape Unit 6380-001 SD001
Selecting the Display SPCN system information function key will cause the following display to appear.
This display lists the System Power Control Network (SPCN) type and serial number. The SPCN type
and serial number is the type and serial number of the system that controls the power for this resource.
--SPCN Sytem--
Type- Serial
Opt Description Model Unit ID Type Number
System 9406-570 U9406.570.102F1BC 9406 10-2F1BC
System Unit + 7879-001 U7879.001.11315CC 9406 10-2F1BC
System Unit + 7879-001 U7879.001.112F1BC 9406 10-2F1BC
System Expansion Unit + 0595-002 U0595.002.104741C
Virtual IOP + < 268C-001 U9406.570.102F1BC
Tape Unit 6380-001
For more information on how to collect information and perform specific functions by using the options
and function keys from the Packaging Hardware Resources display, see “Collecting information and
performing functions from the Hardware Service Manager displays” on page 58.
The Logical hardware resources (buses, IOPs, controllers,...) option appears on the Hardware Service
Manager display. This option allows you to display and work with logical resources. Logical hardware
resources are the functional resources of the system used by the operating system.
When you select the Logical hardware resources (buses, IOPs, controllers,...) option, the following
Logical Hardware Resources display appears:
Service functions 47
Logical Hardware Resources
Selection
From the Logical Hardware Resources on System Bus display, Display Processor Information display,
Display Main Storage Information display, or the Work with High Speed Link (HSL) Resources display,
you can perform the following:
v Display or change logical hardware resource information
v Display associated packaging hardware resources
v Display logical hardware resource status
Note: The System bus resources option also allows you to perform I/O debug functions and run
verification procedures. For more information on this option, see “Display system bus resources”
on page 75.
The High-speed link resources display also allows you to enable and disable HSL Opticonnect and to
display port information.
For more information on collecting information and performing specific functions using the options and
function keys from the Logical Hardware Resources display, see “Collecting information and performing
functions from the Hardware Service Manager displays” on page 58.
For details on the symbols that appear next to the resource description field, see “Symbols on the
Hardware Service Manager displays” on page 88.
The Locate resource by resource name option appears on the Hardware Service Manager display when
the system is in the full or limited paging environment. It allows you to enter a resource name on the
Locate Resource by Resource Name display:
Resource name . . . . . . . . . .
Service functions 49
Logical Hardware Resources
You can also use the Locate Resource By Resource Name display to find a packaging resource. When the
system finds the packaging resource name, the Packaging Hardware Resources display appears.
Type- Resource
Opt Description Model Name Location
Communications Port 2793-001 P82 P1-C2-T1
For more information on collecting information and performing specific functions by using the options
and function keys from the Logical Hardware Resources display, see “Collecting information and
performing functions from the Hardware Service Manager displays” on page 58.
The Failed and non-reporting hardware resources option appears on the Hardware Service Manager
display when the system is in the full or limited paging environment. It allows you to display a list of
the logical hardware resources that either failed or did not report to the system at the last IPL.
A failed resource that reports to the system at the time of the IPL might have a problem with its
operation. On the Failed and Non-Reporting Logical Hardware Resources display, Failed appears in the
Status column to indicate a failed resource. The failed resources appear at the top of the list.
A non-reporting resource does not report to the system at the time of the IPL. On the Failed and
Non-Reporting Logical Hardware Resources display, a question mark symbol (?) appears next to the
resource description field to indicate a non-reporting resource. The status of a non-reporting resource is
Unknown.
Note: For more information on symbols, see “Symbols on the Hardware Service Manager displays” on
page 88.
A failed or non-reporting resource indicates that one of the following has occurred:
v The resource was removed from the system (non-reporting only).
v The resource was powered off at the time of the IPL.
v There is a problem in the signal path between the system and the device.
v There is a resource failure.
Selecting the Failed and non-reporting hardware resources option is a quick way to display failed and
non-reporting resources on the system. For information on other ways to display failed and non-reporting
resources, see “Display failed resources” on page 67 or “Display non-reporting resources” on page 68.
Resource
Opt Description Type-Model Status Name
_ Communications IOP 2626-001 Failed CC04
_ Communications IOA 2626-001 Failed LIN04
_ Communications Port 2626-001 Failed CMN05
_ Communications IOP ? 2626-001 Unknown CC01
_ Communications IOP ? 2623-001 Unknown CC03
_ Communications IOP ? 2619-001 Unknown CC05
_ Communications IOA ? 2626-001 Unknown LIN01
_ Communications IOA ? 2619-001 Unknown LIN05
_ Communications IOA ? 2609-001 Unknown LIN02
_ Communications Port ? 2619-001 Unknown CMN08
_ Communications Port ? 2626-001 Unknown CMN02
_ Communications Port ? 2609-001 Unknown CMN03
_ Communications Port ? 2609-001 Unknown CMN04
_ Workstation IOP ? 916A-001 Unknown WS01
_ Workstation IOA ? 916A-001 Unknown CTL01
_ Display Station ? 3196-0A1 Unknown DSP001
More...
F3=Exit F5=Refresh F6=Print F12=Cancel
Figure 15. Example Failed and Non-Reporting Logical Hardware Resources display
If no failed resources or non-reporting resources exist, the following informational message appears:
No failed or non-reporting logical hardware resources were found.
If the system finds only non-reporting resources and no failed resources, the Failed and Non-Reporting
Logical Hardware Resources display appears with the list of non-reporting resources and the following
message:
Service functions 51
No failed logical hardware resources
were found.
If the system finds only failed resources and no non-reporting resources, the Failed and Non-Reporting
Logical Hardware Resources display appears with the list of failed resources and the following message:
No non-reporting logical hardware resources
were found.
The options on the failed or non-reporting displays are the same options that are available for logical
resources:
v Change detail
v Remove
v Display detail
v I/O debug
v Verify
v Associated packaging resource
For more information on these options, see “Collecting information and performing functions from the
Hardware Service Manager displays” on page 58.
The System Power Control Network (SPCN) option appears on the Hardware Service Manager display when
the system is in the full or limited paging environment. This option is not available on all systems.
Problems that the SPCN reports to the operating system are logged. Select the System Power Control
Network (SPCN) option to work with the network structure for SPCN. See the Service Action Log to
display and work with the log information. For more information on SPCN features and use of this
option, see “System Power Control Network (SPCN)” on page 168.
When you select this option, the system displays a log of hardware errors that require action from a
service representative. A service representative uses the log as a starting point for hardware problem
analysis. It provides information on how many times a system reference code appears for a specific
resource and shows description and location information for the possible failing items.
The Service Action Log prompts you for a specific time range and allows you to select to view only
entries with NEW status. The Service Actions Log Report display shows the following fields for the log
entries that require service action for the time that you specify:
v Option
v Status
v Date
v Time
v SRC
v Resource
v Isolated
v Count
More...
Notes:
1. The special value *PLATFORM displays for the resource name when the log has come from the
POWER™ hypervisor.
2. The F6 key allows you to deactivate the partition’s Virtual System Attention Indicator (VSA).
This key is shown only if the VSA is activated.
Option field
Status field
This field indicates the status of the entry as one of the following:
v NEW
This indicates that no action has been taken. The entry has not been closed or deleted.
v CLOSED
This indicates that a NEW entry has been fixed and closed.
v DELETED
This indicates that the entry will not appear the next time you view the service action log.
Service functions 53
To remove a CLOSED problem from the service action log, select the Delete a CLOSED entry option
from the Service Actions Log Report display.
These fields display the time and date of the first occurrence of a system reference code (SRC) for a
resource during the time range specified.
SRC field
This field shows the system reference code (SRC) that was logged against the resource.
Resource field
This field displays the resource against which the problem was logged.
Count field
This field indicates the number of SRC occurrences for the resource that is indicated in the Resource field.
The Display label location work sheet option appears on the Hardware Service Manager display when the
system is in the full or limited paging environment. It allows you to display current configuration
location information. You can also print a worksheet that shows location information by selecting the
print function on the Label Location Work Sheet display. The work sheet printout contains a field in
which you can enter label information.
The system uses description labels to identify hardware. It is the customer’s responsibility to configure
and assign labels in the system for cables and devices. The system label must match the (physical) label
on the hardware. Prior to a system upgrade procedure, you can select this option to print the label
location work sheet. Use the work sheet to list the hardware labels and to verify that the system labels
match the hardware labels after the upgrade.
For more information on label locations, see “Work with Hardware Products (WRKHDWPRD) command”
on page 230.
For a configured disk unit device, this concurrent maintenance action is only allowed when the disk unit
device has data storage protection. For example, if the disk unit is one member of a mirrored pair or is a
member of a data parity array. To determine the storage protection status for disk units on your system,
see Disk unit recovery procedures. This function is also available for nonconfigured units without storage
protection.
To perform concurrent maintenance on a device, specify the location of the device by providing the
physical location of the device. If you do not know the location, use the following information to
determine the correct location.
This field represents the position of the device within the enclosure as labelled on the frame.
This field shows the logical name assigned to the resource that is the target of device concurrent
maintenance. An example of the resource name for a disk unit would be ’DD037’. See the information for
the specific resource either in the Hardware Service Manager displays or in the Display Disk
Configuration displays. Refer to Figure 18 for an example of the disk unit hardware resource information
details display.
Type........................: 6713
Model.......................: 050
Level.......................: 3
Serial Number...............: 68-xxxxx
Resource Name...............: DD037
Physical location:
Unit ID....................: U5079.001.10ABCDE
Planar ID..................: P1
Device.....................: D1
Figure 18. Example Disk Unit Hardware Resource Information Details display
In Figure 18, the disk unit has physical location U5079.001.10ABCDE-P1-D1, and a Resource Name of
DD037. To perform device concurrent maintenance on this unit, perform the following steps:
1. Enter the information as shown in Figure 19 on page 56.
2. Enter the information that was gathered from the Disk Unit Hardware Resource Information Details
display.
3. Press Enter.
Service functions 55
Note: If the device is unable to report in or you are installing a device into an empty slot, use
Physical Location instead of Resource Name.
Action to be performed
Enter 00 in this field if you do not want any delay before the process begins. If you enter a value in this
field, the device will wait that long after you press Enter to begin the operation. Typically you will enter
a value if the device is at a different location and it will take you a while to get to that location. The
device might be in a different room, for example.
Figure 19. Example Device Concurrent Maintenance with data for Physical Location
For information on how to perform concurrent maintenance for internal tape or internal optical units, see
Removing and replacing parts.
For information on how to perform concurrent maintenance for internal disk units with storage
protection, see Removing and replacing parts.
For details on IOA or IOP concurrent maintenance, see “Concurrent maintenance” on page 60.
The Work with resources containing cache battery packs option appears on the Hardware Service
Manager display when the system is in the full or limited paging environment. It allows you to display a
list of packaging hardware resources that contain a cache battery pack. It also provides the capability to
force the battery pack into an error state for replacement.
Figure 20. Example Work with resources containing cache battery packs display
For more information on collecting information and performing specific functions using the options and
function keys from the Work with Resources Containing Cache Battery Packs display, see “Collecting
information and performing functions from the Hardware Service Manager displays” on page 58.
This field represents the position of the device within the enclosure as labelled on the frame.
The Force battery pack into error state option, available from the Work with resources containing cache
battery packs display, allows you to force an IOA to put its cache battery pack into an error state. This
IOA state requires replacement of the battery. Typically, this option is performed to ensure that write
caching is stopped prior to replacing a cache battery pack (that is to prevent possible data loss) or when
you are replacing a cache battery pack on one IOA, and want to replace other cache battery packs on
IOAs in the same system which have not yet issued the cache battery warning or cache battery error.
The Display battery information option, only available from the Work with resources containing cache
battery packs display, allows you to access information about the cache battery packs.
Battery Information
Service functions 57
Resource name
This is the resource name that was either created by the system when the hardware was first
detected, or was changed to a new value by the user. The packaging hardware resource name is
different from the logical hardware resource name.
Serial number
This field shows the serial number of the resource as reported by the system or entered manually
by the user. Only serial numbers that were initially detected as zeros can be changed by the user.
Type-model
This field shows the Type and model of the resource as reported by the system or entered
manually by the user.
Frame ID
Hexadecimal identity of the frame enclosure.
Card position
The card position of the packaging hardware resource within the enclosure. This can be followed
by a letter to specify the position of a second level card. This is represented by a decimal
numeral.
Battery type
This field indicates the type of cache battery pack.
Battery state
This field indicates if an error condition currently exists related to the cache battery pack. See the
following for possible values for this field:
v No battery warning/error. No warning or error condition currently exists.
v Warning condition. A warning condition currently exists (an entry has been placed in the PAL).
v Error condition. An error condition currently exists (an entry has been placed in the PAL).
v Unknown. Information is not available to determine whether a warning or error condition
currently exists.
Power-on time (days)
This field indicates the raw power-on time, in units of days, of the cache battery pack.
Adjusted power-on time (days)
This field indicates the adjusted (prorated) power-on time, in units of days, of the cache battery
pack.
Note: Some cache battery packs are negatively affected by higher temperatures and thus are
prorated based on the amount of time they spend at various ambient temperatures.
Estimated time to warning (days)
This field indicates an estimated time, in units of days, until a warning is surfaced indicating that
the cache battery pack replacement should be scheduled.
You can select Packaging hardware resources and Logical hardware resources options from the Hardware
Service Manager display (see “Packaging hardware resources” on page 45 and “Logical hardware
resources” on page 47). This section describes how to collect information and perform specific functions
by using the options and function keys from the various packaging and logical hardware resources
displays.
To view or change detailed information about a specific resource, select the Change detail option or
function key. The information varies depending on the device selected.
The following is a Change detail display for a communications IOP packaging hardware resource:
Type-Model . . . . . . . . . . . . : 2620-001
Serial number . . . . . . . . . . . : 10-3157011
More...
For definitions of the fields that appear on the Change Packaging Hardware Resource Detail display, see
“Display resource details” on page 69.
Note: An asterisk symbol (*) on the left and right side of the value indicates that this resource requires
specific information from the user. For more information, see the section entitled “Display
resources requiring attention” on page 73.
You can change the logical resource name of a specific resource by selecting the Change detail option or
function key. The information varies depending on the device selected.
Service functions 59
Change Logical Hardware Resource Detail
Concurrent maintenance
The Concurrent Maintenance option is available only on the packaging hardware resources displays.
This option provides the capability to power off a subset of the system and perform service actions on
hardware in that subset. Other parts of the system remain powered on and functional. Service actions
supported include replacement, upgrade, removal, addition, and movement of hardware.
The subset of system hardware that you power off in order to shut down a particular piece of hardware
is known as the power domain for that piece of hardware. The power domain of a piece of hardware is
determined by the granularity of the power control system. For example, the power domain of an I/O
processor on an SPD bus is the frame in which the SPD bus resides. This is because the power control
system for SPD buses does not support powering individual I/O processor slots on and off. In contrast,
the power control system for PCI buses does support powering individual I/O card slots on and off.
Consequently, the power domain for an I/O card on a PCI bus is the card itself.
There are some restrictions on hardware resource concurrent maintenance which are enforced by the
operating system.
You can find more information on these restrictions by pressing F1 at the Concurrent Maintenance
display.
Power
Opt Description Type-Model Status Position
System Unit > 7879-001 On
Active Backplane 28DA On P1
Combined Function IOP 2844-001 On P1-C1
Communications IOA 2793-001 On P1-C2
Communications Port 2793-001 On P1-C2-T1
Communications Port 2793-001 On P1-C2-T2
Unknown resource On P1-C3
Occupied Position On P1-C4
Empty Position Off P1-C5
Occupied Position On P1-C6
Empty Position On P1-C7
More...
If you change detail or reserve frame space for a frame ID that currently does not exist, the following
message appears:
Containing hardware resource does not
exist. Press F10 to create.
Note: For details on changing resource details, see “Change resource details” on page 59. For details on
reserving frame space, see “Reserve frame space” on page 79.
Service functions 61
Select Packaging Model
Note: The Create containing hardware resource function key is not available for all resources.
2. After you select the frame information and press Enter, the Define Frame Packaging Detail display
appears. This display allows you to define the following frame information:
v Resource name
v Serial number
v Location text
v Service provider
v Alternate remote telephone
v Alternate service node
v Alternate service telephone
v Owning system type
v Owning system model
v Owning system serial number
3. When you press Enter, the data is verified and used to create a new packaging resource. If no errors
are found, you will return to the original change detail or reserve frame space display.
4. Press Enter from that display to complete the change and return to the previous packaging list
display. You can view this newly created packaging hardware resource in the list of frames on the
Packaging Hardware Resource display.
The Create containing hardware resource function key is available only on the packaging hardware
resources displays. To access this function from the logical displays, select the Associated packaging
resource(s) option. For details, see “Display associated resources” on page 64.
The I/O debug option is available only on the logical hardware resources displays. To access I/O debug
from the packaging displays, you must select the Associated logical resource(s) option. For details, see
“Display associated resources” on page 64.
The I/O debug option is available only on the logical hardware resources displays. This option assists in
debugging selected resources.
The I/O Debug display shows the following options as appropriate for the resource selected:
Read/write I/O processor data
Select this option to read or edit the I/O processor data
Dump I/O processor data
See “Performing an IOP dump” on page 209.
Reset I/O processor
Some debug functions require that the I/O processor be in a disabled state. Select this option to
disable the I/O processor. To enable the I/O processor for normal operation, you must select the
IPL I/O processor option on the Select I/O Debug Function display or IPL the system again.
IPL I/O processor
Select this option to IPL the I/O processor. It allows you to recover from an intermittent problem,
refresh the I/O processor system information, or enable the I/O processor for normal operation
after selecting the reset I/O processor option. Selecting this option performs the same function as
the i5/OS vary command with the reset option. For details, see “How to reset an I/O processor
card while the system is running” on page 223.
Enable I/O processor trace
Select this option to enable IOP trace.
Disable I/O processor trace
Select this option to disable IOP trace.
Enable I/O processor reset
Select this function key to enable IOP reset (one IOP or all IOPs on a bus).
Attention: This function is only for System i development use and is not for use in customer
installations. Using this option can disrupt system operations and lead to unrecoverable system
failures.
Disable I/O processor reset
Select this function key to disable IOP reset.
Attention: This function is only for System i development use and is not for use in customer
installations. Using this option can disrupt system operations and lead to unrecoverable system
failures.
Enable I/O processor IPL
Select this function key to enable IOP IPL (one IOP or all IOPs on a bus).
Attention: This function is for System i development use only and is not for use in customer
installations. Using this option can disrupt system operations and lead to unrecoverable system
failures.
Service functions 63
Disable I/O processor IPL
Select this function key to disable IOP IPL.
Attention: This function is for System i development use only and is not for use in customer
installations. Using this option can disrupt system operations and lead to unrecoverable system
failures.
Enable bus trace
Select this option to enable a bus trace.
Take/Release ownership
If this system presently owns the resource, selecting this option will allow the system to release
its ownership.
If this system does not presently own the resource, selecting this option will allow the system to
take ownership.
For more information on I/O debug, see “Performing an IOP dump” on page 209.
Each packaging hardware resource has associated address information. The address information is
available only on the logical hardware resources displays. To access address information from the
packaging displays, you must select the Associated logical resource(s) option. For details, see “Display
associated resources.”
Select the Display detail option on various logical resources to view address information. For details, see
“Display resource details” on page 69.
Notes:
1. The system configuration list printout shows logical address information. For more
information, see “Printing the System Configuration List” on page 89.
2. You can also view logical address information from the product activity log. For details, see
“Product Activity Log” on page 92.
Some packaging hardware resources have associated logical resources. Logical hardware resources
represent the function of the hardware. Select Associated logical resource(s) to show the logical resources
that are associated with the packaging resource. The packaging resource might have no associated
resources or might be associated with one or more logical resources. For example, the physical hardware
resources for a communications card could have three logical hardware resources associated with it: a
communications I/O processor, a communications I/O adapter, and a communications port.
Note: The logical and packaging hardware resources have unique resource names. Packaging hardware
resource names are used only by the system. Service representatives and customers use the logical
resource names.
Packaging resource:
Type-Model Resource Name
Communications IOP 2620-001 P17
Figure 26. Example Logical Resources Associated with a Packaging Resource display
This display shows all the logical hardware resources that are associated with one packaging resource.
The first line provides a description, type, model, and resource name of the packaging resource with
which all the logical resources are associated.
The options on the Logical Resources Associated with a Packaging Resource display are the same options
that are available for logical resources:
v Change detail
v Remove
v Display detail
v I/O debug
v Verify
v Associated packaging resource(s)
Each logical hardware resource has one or more associated packaging hardware resources. Packaging
hardware resources represent the physical packaging of the system hardware. Select Associated
packaging resource(s) to show physical locations and display the packaging resources that are associated
with the logical resource. For example, the communications I/O processor is shown as the packaging
hardware resource that is associated with the logical communications I/O processor.
Service functions 65
Packaging Resources Associated with a Logical Resource
Logical resource:
Type-Model Resource Name
Communications IOP 2620-001 CC08
Figure 27. Example Packaging Resources Associated with a Logical Resource display
This display shows all the packaging hardware resources that are associated with one logical resource.
The first line provides a description, type, model, and resource name of the logical resource with which
all packaging hardware resources are associated.
Options on the Packaging Resources Associated with a Logical Resource display are the same options
that are available for packaging hardware resources:
v Change detail
v Concurrent maintenance
v Remove
v Display detail
v Associated logical resource(s)
v Hardware contained within package
Note: The logical and packaging hardware resources have unique resource names. Packaging hardware
resource names are used only by the system. Service representatives and customers use the logical
resource names.
The Display card gap information function key appears on the Hardware Service Manager display. I/O
processor cards must be installed in a specified logical order.
Note: SPD system busses require that no empty card positions exist between I/O processors. PCI system
busses may have empty card positions.
Select this option to display the gaps in the logical card sequencing. If the cards are not installed in order,
system performance might be affected, the cards might be unusable, or SRCs that provide incorrect FRU
information might appear.
If the system detects gaps in the logical sequence, the Card Gap Information display appears.
Resource Card
Description Type-Model Frame ID Name Position
System Unit 9406-500 1 FR01 2
6
7
8
The Card Position column shows the card location that is empty. One or more card positions might be
empty for a single card enclosure.
If no gaps are detected, the following message displays: No card position gaps were detected in the
system
The Failed resources function key is available only on the Logical Hardware Resources displays.
The Failed resources function is available only under the Logical hardware resources option. This function key
displays a list of all failed logical hardware resources. A failed resource indicates that one of the following
occurred:
v There is a problem in the signal path between the system and the device.
v There is a resource failure.
You can also select the Failed and non-reporting resources option on the Hardware Service Manager display
to show failed resources (see “Failed and non-reporting resources” on page 50).
The Hardware contained within package option is available only on the Packaging Hardware Resources
displays. Use this option to view the next level of hardware for the packaging hardware resources. This
option functions only when a plus sign (+) appears after the description. For more information on
Service functions 67
symbols, see “Symbols on the Hardware Service Manager displays” on page 88.
The Display hardware contained within package option is available only on the Packaging Hardware
Resources displays. To access this option from the logical displays, you must select the Associated
packaging resource(s) option (see “Display associated resources” on page 64).
If the resource is at the lowest level of packaging (contains no other packages), the following message
displays:
The selected resource cannot be expanded.
Each packaging hardware resource has associated location information. To display specific locations,
select the Display detail option.
Location information that appears on the logical displays shows the logical address. Physical location
information is available only on the Packaging Hardware Resources displays. To access physical location
information from the logical displays, you must select the Associated packaging resource(s) option (see
“Display associated resources” on page 64).
The Non-reporting resources function key appears on the Packaging Hardware Resources display (see
“Packaging hardware resources” on page 45). It allows you to view a list of the hardware that was
detected in the past but is not being detected by the system now. A non-reporting resource indicates that
one of the following has occurred:
v The resource might have been removed from the system. (For more information on removing the
resource, see “Remove non-reporting resource information” on page 78.)
v The resource might be powered off.
v There is a problem in the signal path between the system and the device.
v There is a resource failure.
You can also select the Failed and non-reporting resources option on the Hardware Service Manager display
to view non-reporting resources (see “Failed and non-reporting resources” on page 50).
The Non-reporting resources function key appears on various Logical Hardware Resource displays. It
allows you to view a list of the logical resources that were detected in the past but are not being detected
by the system now. A non-reporting resource indicates that one of the following occurred:
v The resource might have been removed from the system.
v The resource might be powered off.
v There is a problem in the signal path between the system and the device.
v There is a resource failure.
or
No non-reporting packaging hardware resources were found.
The Resources associated with IOP option is available only on the Logical Hardware Resources on
System Bus display. For details, see “Display system bus resources” on page 75. To access resources
associated with the I/O processor, you must select the Logical hardware resources option on the main
Hardware Service Manager display, and then select the System bus resources option.
The Resources associated with IOP option is available only on the Logical Hardware Resources on
System Bus display. For details, see “Display system bus resources” on page 75. This option displays the
selected IOP and lists all devices that are (logically) attached to it. If more than one IOP is selected, the
list contains all the IOPs and their logically attached resources.
Resource
Opt Description Type-Model Status Name
_ Multiple Function IOP * 9162-001 Operational CMB01
_ Disk Controller 6606-030 Operational DC02
_ Disk Unit * 6606-030 Operational DD002
_ Disk Controller 6605-030 Operational DC01
_ Disk Unit 6605-030 Operational DD001
_ Tape Controller 6380-001 Operational DC03
_ Tape Unit 6380-001 Operational TAP01
Figure 29. Example Logical Hardware Resources Associated with IOP display
You can select the Display detail option from various packaging resource displays. This option allows
you to view additional information about a specific resource. Use this option to display the location
information on a specified resource. The information that is displayed varies depending on the type of
resource that is chosen. The display below shows detail for a communications IOP packaging hardware
Service functions 69
resource.
Service functions 71
Manufactured by IBM
This field contains a 1 if the resource was manufactured by IBM or a 2 if it was not.
Shared by multiple systems
This field contains a 1 if the resource is shared between multiple systems or a 2 if it is not.
The Communication Hardware Resource Detail display shows detail for a communications port logical
hardware resource.
Note: The information that is displayed varies depending on the type of resource that is chosen.
The following fields might appear on the detail display. For details on these fields, see “Display resource
details” on page 69.
v Description
v Type-model
v Status
Note: For details on the Status value, see “Display resource status” on page 74.
v Serial number
v Part number
v Resource name (logical)
The information in the fields below varies depending on the type of resource that is chosen.
v SPD or PCI bus
– System bus
– System board
– System card
v Communications
The Display resources requiring attention function key appears on the Hardware Service Manager
display. Most hardware resources automatically report information to the system, but some resources
might require user input. This function scans the system for packaging resources that need more
information in order to be correctly displayed on the packaging displays. User input might be required
for the following:
v EIA location information is missing.
v Frame ID information is missing.
v The resource cannot determine if it is mounted in a frame (rack-mounted) or if it is a stand-alone unit.
If there are resources that need attention, the Hardware Resources That Require Attention display
appears.
To update or change the resource information from the Hardware Resources That Require Attention
display, select the Change detail option. For details, see “Change resource details” on page 59. Asterisks
(*) might appear on both sides of a value that appears on the Change Packaging Hardware Resource
Detail display. This shows the value that is causing the resource to need attention.
Service functions 73
v The resource does not appear on the packaging resource displays or printouts. On some resources
displays you can press the Unresolved locations function key to view the unresolved locations
information.
v The system operates normally. The information requested for these resources is for display purposes
only.
To display detailed messages that indicate why this resource might need attention, select the Display
message(s) option on the Hardware Resources That Require Attention display.
Message
Number Message
0 Frame ID is blank.
1 EIA location is blank.
2 Mounting type needs to be verified.
To update or change the resource information from the Hardware Resources That Require Attention
Messages display, press Enter. For details, see “Change resource details” on page 59.
Resource status information is available only on the Logical Hardware Resources displays. To access
status information from the Packaging displays, select the Associated logical resource(s) option. For
details, see “Display associated resources” on page 64.
The status of each logical hardware resource is shown next to the description, type, and model
information on various Logical Hardware Resources displays. You can also select the Display detail
option to view the resource status. For details, see “Display resource details” on page 69. This indicates
the current status of the resource as reported by the hardware.
Status values:
Unknown
Cannot determine status. The resource may be non-reporting or unable to communicate status.
Operational
Resource is functioning normally.
Failed Resource has failed and is not functional.
You can display serial and part number information on various Packaging Hardware Resources displays
by selecting the Display detail option (see “Display resource details” on page 69). To access address and
status information from the Packaging Hardware Resources displays, select the Associated logical
resource(s) option (see “Display associated resources” on page 64).
The Display serial/part numbers, Display logical address, and Display status/resource name function keys are
available only on the Logical Hardware Resources displays.
The Display serial/part numbers, Display logical address, and Display status/resource name function key is
available only on the Logical Hardware Resources on System Bus and Logical Hardware Resources Associated
with IOP displays. This function key toggles the display to show serial and part number information,
logical address information, or the default status and resource name.
For more information on status, see “Display resource status” on page 74.
The System bus resources option is available only on the Logical Hardware Resources display. For
details, see “Logical hardware resources” on page 47. From the Logical Hardware Resources on System
Bus display, you can perform the following:
v Perform the following I/O debug functions:
– Read/write I/O processor data. For details, see “Debug the resource” on page 62.
– Dump I/O processor data. For details, see “Performing an IOP dump” on page 209.
– Reset I/O processor. For details, see “Debug the resource” on page 62.
Service functions 75
– IPL I/O processor. For details, see “Debug the resource” on page 62.
– Enable I/O processor IPL. For details, see “Debug the resource” on page 62.
– Disable I/O processor IPL. For details, see “Debug the resource” on page 62.
– Enable I/O processor reset. For details, see “Debug the resource” on page 62.
– Disable I/O processor reset. For details, see “Debug the resource” on page 62.
– Enable bus trace. For details, see “Debug the resource” on page 62.
– Take/Release ownership. For details, see “Debug the resource” on page 62.
Resource
Opt Description Type-Model Status Name
_ System Bus - Operational LB01
_ Multiple Function IOP * 9162-001 Operational CMB01
_ Multiple Function IOP ? 9162-001 Unknown CMB02
_ Communications IOP ? 2619-001 Unknown CC05
_ Communications IOP 2619-001 Operational CC02
_ Storage IOP 6512-001 Operational SI01
_ Communications IOP ? 2626-001 Unknown CC01
_ Workstation IOP < 916A-000 Operational WS02
More...
F3=Exit F5=Refresh F6=Print F8=Exclude non-reporting resources
F9=Failed resources F10=Non-reporting resources
F11=Display serial/part numbers F12=Cancel
The Logical Hardware Resources on System Bus display shows the logical hardware resources in levels,
beginning with the system bus. For example, a system bus might have one or more IOPs attached, an
IOP might have an associated controller, or a controller might have an associated device. All associated
first level logical hardware resources are shown. Option nine allows you to see the resources that are
associated with each I/O processor.
For frames with a PCI system bus, the Logical Hardware Resources on System Bus display shows the
logical hardware resources in levels, beginning with the HSL I/O bridge. As depicted in the following
example, an HSL I/O bridge will have one or more bus expansion adapters. A bus expansion adapter
will have one system bus. A system bus will have one or more multi-adapter bridges. A multi-adapter
bridge might control one or more IOPs.
Resource
Opt Description Type-Model Status Name
_ HSL I/O Bridge 3333-333 Operational BC01
_ Bus Expansion Adapter 5533-333 Operational BCC01
_ System Bus 5533-333 Operational SPD03
_ Multi-adapter Bridge 5544-444 Operational PCIO1D
_ Multiple Function IOP * 9162-001 Operational CMB01
_ Communications IOP 2619-001 Operational CC02
_ Communications IOP 2629-001 Operational CC01
_ Communications IOP 2626-001 Operational CC03
_ Workstation IOP < 916A-001 Operational WS01
_ Multi-adapter Bridge 5566-666 Operational PCI16D
_ Communications IOP 2222-222 Operational CC04
_ Bus Expansion Adapter 5577-777 Disabled BCC011
_ System Bus 5577-777 Disabled SPD04
_ Multi-adapter Bridge 5588-888 Disabled PCI02D
_ Communications IOP 1222-222 Unknown CC05
_ Multi-adapter Bridge 5599-999 Disabled PCI30D
_ Communications IOP 3222-222 Unknown CC16
Figure 35. Example Logical Hardware Resources on System Bus display (frames with a PCI system bus)
The Display system information option is available from the Logical Hardware Resources displays. This
option allows you to view the system type and system serial number of the iSeries system that controls
the SPCN (System Power Control Network) for the selected resource. It also allows you to view the
system type and system serial number of the iSeries system that is an alternate owner of the resource. If
no system presently owns the selected resource, the current owner of the resource is indicated. The
iSeries system that last had ownership of the resource is indicated as the owner.
The Unresolved locations function key is available only on the Packaging Hardware Resources displays.
This function key displays the packaging hardware resources for which the system cannot fully
determine the location information. Select this function key to view the hardware resources that may
require user intervention to display correctly on the Packaging Hardware Resources displays.
Service functions 77
When you select the Packaging hardware resources option on the Hardware Service Manager display, the
system scans the packaging resources. If location information is missing, the following message appears:
There are resources with unresolved locations. Press F13 to see list.
Select the Unresolved locations function key to view the Hardware with Unresolved Locations display.
To update or change the location information, select the Change detail option on the Hardware with
Unresolved Locations display.
The Unresolved locations function key is available only on the Packaging Hardware Resources displays. To
access unresolved location information from the logical displays, you must select the Associated packaging
resource(s) option (see “Display associated resources” on page 64).
Print
Print from packaging and logical displays.
The Print function key produces a printout of the information displayed. You can select this option from
various displays.
Select the Print (F6) function key from the Hardware Service Manager display to print the system
configuration list. The system configuration list includes system information and the packaging and
logical information. For more information on printing the system configuration list, see “Printing the
System Configuration List” on page 89.
Select the Refresh function key to access the data again. Use the Refresh function key when a change was
made from this display. For example, select this function key if power is restored to a non-reporting
resource.
This option allows you to remove non-reporting resources (hardware that has not reported to the system)
and user-created frame information. Non-reporting resources are identified with a question mark (?) next
to the description field (see “Symbols on the Hardware Service Manager displays” on page 88). For more
information on non-reporting resources, see “Display non-reporting resources” on page 68. Selecting this
option removes this hardware resource and the associated logical or packaging resources information.
Use this option after performing a hardware upgrade when hardware resources were removed.
The Reserve frame space function key appears only on the Packaging Hardware Resources display. Select
the Reserve frame space function key to access the Reserve Frame Space display. The Reserve Frame Space
display allows you to enter details for a section of a frame (type 9309 or 5044) that you want to reserve
for future use. You can also use the Reserve frame space function key to keep an inventory of hardware
that does not appear on the packaging hardware resources displays.
After you type the requested information, press Enter. The data is verified and used to create a new
packaging resource with the new description.
If no errors are found, the new data is created, and the original Packaging Hardware Resources display
appears. If you enter a Frame ID that does not currently exist, the following message appears:
Containing hardware resource does not exist. Press F10 to create.
For information on creating frame information, see “Create frame information” on page 61.
The Reserve frame space function key appears only on the Packaging Hardware Resources display.
Note: The term High Speed Link (HSL) is interchangeable with the term Remote I/O (RIO).
You can access options for High Speed Link (HSL) resources from the High Speed Link resources option on
the Logical Hardware Resources display.
Service functions 79
Work With High-Speed Link (HSL) Resources
HSL
Resource Hardware Loop OptiConnect
Opt Description Name Status Number Status
_ Local HSL NIC BCC01 Operational Disabled
_ HSL Loop SB01 Operational 256 Not Available
_ HSL Loop SB02 Operational 257 Enabled
_ Local HSL NIC BCC02 Operational Disabled
_ HSL Loop SB03 Operational 258 Not Available
_ HSL Loop SB04 Operational 259 Disabled
_ Local HSL NIC ? BCC03 Unknown Disabled
_ HSL Loop ? SB05 Unknown 260 Not Available
_ HSL Loop ? SB06 Unknown 261 Not Available
Figure 36. Example Work With High Speed Link (HSL) Resources display
The Work With High Speed Link (HSL) Resources display appears when you select the High Speed Link
resources option on the Logical Hardware Resources display.
The Work With High Speed Link (HSL) Resources display allows you to display information and perform
functions that are specific to HSL.
Display detail:
Select Display details on an HSL loop resource. The Display High-Speed Link (HSL) Information display
will appear. This display shows the detail for an HSL loop. It also allows you to display each resource in
the HSL loop. This screen is also displayed when F7 is selected and the previous resource is the
beginning of the loop and when F8 is selected and the next resource is the beginning of the loop.
Select Display details on an HSL I/O bridge resource. The Display High Speed Link (HSL) Information
display will appear. This display shows the details of an HSL I/O bridge resource. This screen is also
displayed when F7 is selected and the previous resource is an HSL I/O bridge or when F8 is selected and
the next resource is an HSL I/O bridge.
Figure 38. Example Display High Speed Link (HSL) Information display
Select Display detail on a remote HSL NIC resource. The Display High Speed Link (HSL) Information
display will appear. This screen is also displayed when F7 is selected and the previous resource is a
remote HSL NIC or when F8 is selected and the next resource is a remote HSL NIC.
Service functions 81
Display HSL Information
Figure 39. Example Display High Speed Link (HSL) Information display
The HSL loop number is the numeric value of the HSL loop to which the resource belongs.
The next several fields display detailed information about the resource:
Type-model
This field contains the type and model numbers as reported by the hardware.
Status This field indicates the current status of the logical resources as reported by the hardware. The
list below states the possible values for this field:
Unknown
The system cannot determine status. The resource may be non-reporting or unable to
communicate status.
Operational
The resource is functioning normally. For HSL loops, this also means that all links are
connected and all resources are operational.
Not operational
This system does not own or control this resource.
Failed The resource has failed or been powered off for concurrent maintenance.
Serial number
This field represents the serial number of the logical hardware resource.
Part number
This field represents the part number of the logical hardware resource.
The resource name is the symbolic name of the logical hardware resource. The resource name was either
created by the system when the hardware was first sensed, or was updated to a new value by a user on a
change screen. The logical hardware resource name is autonomous from the packaging hardware resource
name.
This field represents the status for networking. To be network capable a loop must contain at least two
systems. It may also contain I/O towers. There are five possible values for this field:
Not Available
The loop contains hardware which is not network capable.
Enabled
This logical partition is participating in the HSL OptiConnect system area network on this loop.
Enabling
The user selected option 1 on this resource and the system is performing the function.
Disabled
This logical partition is not participating in the HSL OptiConnect system area network on this
loop.
Disabling
The user selected option 3 on this resource and the system is performing the function.
Mode
The mode field indicates whether or not the ownership of this resource can be switched to another
system. The possible values are Private or Switchable. Private indicates that the ownership of this resource
cannot be changed. Switchable indicates that the ownership of this resource is changeable.
The leading port connects to the next resource in the loop. This field shows the port number to which
another resource in the loop is connected. However, the loop is redundant so indicating direction is
arbitrary. This field will be blank if the link is an internal link.
The trailing port connects to the previous resource in the loop. This field shows the port number to
which another resource in the loop is connected. However, the loop is redundant so indicating direction
is arbitrary. This field will be blank if the link is an internal link.
Link status
Current status of the link as reported by the hardware. Possible values for status are as follows:
Unknown
The system cannot determine status of the resource. A resource may be non-reporting or unable
to communicate its status.
Operational
The link is operating normally.
Failed The link is broken, disconnected, or does not exist. This also may mean that the resource to
which the link is connected may have failed or is powered off.
Service functions 83
Link type
This field shows the type of link to which this port connects. Possible values are optical or copper.
Type
The port may be connected to another resource through two possible connections: internal or external.
Internal
The user cannot see an internal connection. It is internal to the resource. If the connection is
internal, the port number field will be blank.
External
The user can see an external connection. The port number field will contain a value.
Link Speed
This is the present speed at which the link is operating.
The Display HSL System Information screen is available for an HSL I/O bridge resource.
This display shows the connection information for an HSL loop. For each link, the display shows
information about the connection from the previous resource in the loop as well as information about the
connection to the next resource in the loop.
Not all functions are available on all models value of the High Speed Link (HSL) loop to which the
resource belongs.
Service functions 85
From and to information
For each link, the From field shows the connection from the previous resource in the loop. The To field
shows the connection to the next resource in the loop.
Resource name
Port
This field shows the port number to which another resource in the loop is connected. This field is blank if
the link is an internal link.
Type
See Type.
Status
The current status of the link as reported by the hardware. Possible values for the status field are:
Unknown
Cannot determine status. A resource may be non-reporting or unable to communicate status.
Operational
The link is operating normally.
Failed The link is broken, disconnected, or does not exist. This also may mean that the resource to
which the link is connected may have failed.
When the Resources associated with loop option is selected on loops 256 or 257 from the Work With
High Speed Link (HSL) Resources display, the Logical Hardware Associated With HSL Loops display
appears.
Use the Logical Hardware Associated With HSL Loops display to work with the High Speed Link (HSL)
resources associated with an HSL loop.
Resource Loop
Opt Description Name Status Number
_ HSL Loop SB01 Operational 256
_ HSL I/O Bridge BC01 Operational
_ HSL I/O Bridge BC02 Operational
_ HSL I/O Bridge BC03 Operational
_ HSL Loop SB02 Operational 257
_ HSL I/O Bridge BC06 Operational
_ HSL I/O Bridge BC07 Operational
_ Remote HSL NIC BC08 Operational
_ HSL I/O Bridge BC09 Operational
_ HSL I/O Bridge BC10 Operational
Figure 42. Example Logical Hardware Associated With HSL Loops display
For a description of the options on this display, see “Using High-Speed Link (HSL) specific options” on
page 79.
To view tower information, select F11 Display tower information from the Logical Hardware Associated
With HSL Loops display. The Logical Hardware Associated With HSL Loops display appears.
Service functions 87
Logical Hardware Associated With HSL Loops
Resource
Opt Description Name Tower
_ HSL Loop SPD01 9406-XXX
_ HSL I/O Bridge BC01 9406-XXX
_ HSL I/O Bridge BC02 5075
_ HSL I/O Bridge BC03 5075
_ HSL Loop SPD02 9406-XXX
_ HSL I/O Bridge BC06 9406-XXX
_ HSL I/O Bridge BC07 5075
_ Remote HSL NIC BC08 9406
_ HSL I/O Bridge BC09 5075
_ HSL I/O Bridge BC10 5075
Figure 43. Example Logical Hardware Associated With HSL Loops display
The Logical hardware associated with HSL loops display works with the HSL I/O bridge and remote
HSL Network Interface Controller (HSL NIC) resources associated with a High Speed Link (HSL) Loop.
For a description of the options on this display, see “Using High-Speed Link (HSL) specific options” on
page 79.
Verify resources
Verify resources from packaging and logical displays.
The Verify option is available only on the Logical Hardware Resources displays. To access status
information from the Packaging displays, you must select the Associated logical resource(s) option (see
“Display associated resources” on page 64).
The Verify option is available on various Logical Hardware Resources displays. It is used on device-level
resources (see “Display resources associated with IOP” on page 69).
Note: The Verify option is not available on the Logical Hardware Resources on System Bus display.
This option allows you to select hardware diagnostic tests that are defined for the selected logical
hardware resource. The tests are limited to most communication ports, cartridge tape units, optical
storage units, diskette units, and File Server adapters. For information on how to run a verification
procedure, see “Verification procedures” on page 91.
The System Configuration List printout consists of the following sections (80-character width):
1. System information
v System type, model, serial number, and release
For details on how to interpret the Release field, see “Determining the dominant operating system”
on page 123.
2. Packaging hardware resource information
v Resource name, type-model, serial number, part number, frame ID, card position, and device
position
3. Logical hardware resource information
v Resource name, type-model, serial number, and logical address
4. Legend
v Descriptions of the indicators
v Logical address format information
132-character width printouts consist of the following:
v description
v type-module
Service functions 89
v serial number
v location data
– frame ID
– device position
– card position
v logical resource name
v part number
v logical address
You can sort the printout by location or logical address data.
Note: The logical address sort and location sort are available only in 132–character width.
4. Look for the system configuration list printout.
Notes:
a. If you select the Print function key from a display other than the Hardware Service
Manager display, only the information that appears on the display will print.
b. Use the last page of the printout (the legend) to assist in interpreting the information.
c. The logical and packaging hardware resources have unique resource names.
d. You can also view logical address information online from the product activity log (see
“Product Activity Log” on page 92).
This ends the procedure.
Results
To collect more details on the information that is listed on the system configuration list, select the Print
function key from a display other than the Hardware Service Manager display.
Note: The entire system configuration list will not print. Only the information that appears on the
display will print.
For details (that include descriptions) on the system bus, main storage, or processor, perform the
following procedure:
1. Select the Logical hardware resources option on the Hardware Service Manager display.
2. On the Logical Hardware Resources display, select one of the following options to display details:
v System bus resources
v Processor resources
v Main storage resources
v High-speed link resources
Verification procedures
You can check communications and various hardware units and devices for correct operation by
performing verification procedures.
Notes: There are two primary methods used to verify communications and hardware:
1. Hardware Service Manager - Verify
2. Verify Communications (VFYCMN)
Verification support for a hardware type is generally available under one or the other, but not both.
Verification for most Version 4 or newer hardware is available under the Hardware Service Manager -
Verify option, which can be run from either DST or SST. For details, see “Hardware Service Manager —
Verify.” If you need to run the VFYCMN command, you must perform an IPL to start i5/OS. For more
information on running the VFYCMN command, see “Verify communications” on page 236.
To verify communications or devices on any System i model using the Hardware Service Manager Verify
option, perform the following procedure:
Note: Before running a verification test, ensure that the customer is not using the resource you want to
test and that all communication jobs on the resource to be tested are ended.
1. From the Start a Service Tool display, select the Hardware Service Manager option.
2. From the Hardware Service Manager display, select the Logical hardware resources option.
3. From the Logical Hardware Resources display, select the System bus resources option.
This display lists all the I/O processors.
4. Select the Resources associated with IOP option for the attached IOP in the list.
5. Select the Verify option for the communications, tape, optical storage unit, diskette equipment, or File
Server adapter that you want to test.
6. When the test completes, the system responds with either a Test is successful message or a Test
failed message.
This ends the procedure.
Results
Notes:
1. Hardware units might perform automatic self-tests when they are powered on.
2. You can test some workstations by using the Test Request function key while the operating
system Sign On display is shown.
3. See the specific device information for possible off-line tests that you can run.
You can check optical storage units for correct operation by performing the verification procedure. For
details on performing the Verify option, see “Hardware Service Manager — Verify.”
Service functions 91
Optical storage unit test descriptions
When you select the Verify option on an optical resource that supports a verification function, the test
performs the following:
v Writes to the test media if writeable (and supported).
v Reads the test media
v Verifies that the interface between the system and the optical storage unit is valid
Verify tape
You can check tape subsystems for correct operation by performing the verification procedure.
When you select the Verify option on a tape resource that supports a verification function (for example,
type 6380), the test performs the following:
v Runs a read, write, or erase function on the tape.
v Tests the interface between the system and the tape unit.
v Runs simple operations to verify that the tape unit is operating correctly.
If the test fails, the system will display a message that describes the failure. An entry might also be
created in the product activity log. Use the message or the information in the product activity log to
assist in problem analysis (see “Product Activity Log”).
Verify communications
You can check communications for correct operation by performing the verification procedure.
When you select the Hardware Service Manager Verify option (see “Hardware Service Manager — Verify”
on page 91 for details) or run VFYCMN (see “Verify communications” on page 236) on communications,
you can test the correct operation of the following hardware:
v Communications I/O adapter card
v Communications cable
v Local or remote modem
v External token ring
You can get additional problem analysis information by running more than one test.
You can select the Product activity log option from the Start a Service Tool display.
It allows you to display or print system, Licensed Internal Code, software components, subsystem, and
I/O device data that has been logged. It also provides data summaries, allows data to be sorted, displays
reference code descriptions, and allows you to work with removable media statistics.
Use the options and function keys to view the log online. Function keys, such as the Alternate view key,
allow you to page through the various log fields. For more information on the product activity log
1. Analyze log
2. Display or print by log ID
3. Change log sizes
4. Work with removable media lifetime statistics
5. Display or print removable media session statistics
6. Reference code description
Selection
F3=Exit F12=Cancel
The PAL is the general use system log containing entries for informational events, thresholding incidents,
dumps, and errors that need to trigger service actions. The entries are full of basic and detailed
information on the event in a somewhat raw form.
This option is selected from the Start a Service Tool menu. It allows you to display or print data that has
been logged for various components of the system. It also provides data summaries, allows data to be
sorted, and allows you to work with removable media statistics and display reference code descriptions.
It was formerly called the Error Log Utility.
Note: Some PAL entries regarding secondary logical partitions are written to the PAL with respect to the
primary partition.
Service functions 93
v Display information about volume statistics for removable media.
v Review session or lifetime counters for a specific volume or removable media type.
v Delete or print volume statistics lifetime counters.
v Display reference code descriptions
In the limited paging environment, you cannot change PAL area sizes, work with tape or diskette
statistics, or examine session or lifetime counters for a specific volume or removable media type.
To access the SAL, select the following options, in order, from a DST or SST menu:
v Start a service tool
v Hardware service manager
v Work with service action log
The SAL is a utility that scans the PAL and displays entries that require service representative action. It
pulls out the relevant information from those entries and formats it to the display to show service
information, such as failing resource names, field replaceable unit (FRU) part numbers, and FRU
locations. If FRU part numbers and locations cannot be determined, the SAL display shows symbolic FRU
names and isolation procedure names, which then correspond to problem analysis procedures for the
service representative. The SAL runs before the operating system is operational.
A shadow log is maintained by LIC on the load source disk. The 128 K-byte shadow log contains a
duplicate of the most recent or latest Product Activity Log entries that occurred before IPL began and
those entries that were logged since the beginning of IPL. The Product Activity Log option uses the
shadow log when the system is operating in limited paging environment.
If Product Activity Log initialization is not complete, only the shadow log is accessible to this option.
Also, the Product Activity Log menu offers only a few specific Product Activity Log options. The Main
menu informs the user that log initialization has not completed, that all Product Activity Log entries are
not accessible, and to IPL the operating system to complete initialization. If initialization completes after
the Product Activity Log option has been selected, the option must be selected again to make all Product
Activity Log options available for use and to generate reports that show all the log entries.
The Product Activity Log is maintained by the Licensed Internal Code EREP component. The log files can
be stored on any disk unit, so the system must IPL past storage management recovery to view the data.
DST uses the LIC code; however, there is limited operating system support in the DST. Because there is
limited operating system support, there is limited Product Activity Log entry handling support. Most
Paging environment
The product activity log is maintained by the system Licensed Internal Code.
The storage management recovery step of the IPL process must be complete to allow you to view all the
data in the log. If the error log initialization (ELI) IPL step is not complete, only the shadow log is
accessible. The Product Activity Log display under the shadow log contains a subset of the options that are
allowed when the operating system is available. A message on the Product Activity Log display informs
the user that the error log is not initialized and that all log records are not accessible. The log files can be
stored on any disk unit.
The Licensed Internal Code maintains a 128 KB shadow log on the load-source disk. The log contains a
duplicate copy of the latest entries. When you perform an IPL to Dedicated Service Tools (DST), the
Product activity log option uses this shadow log.
Note: The shadow log is not available in the stand-alone environment (Type-D IPL). In the limited
paging environment, some options are not available. For more information on paging
environments, see “System paging environments” on page 1.
The function keys that appear at the bottom of the screen vary for each display. Function keys allow you
to gather more information about the entry. Examples of function keys include the following:
v Sort by...
v Address information
v Display hexadecimal report
Analyze log
Use the analyze log option to display or print log entries in a summarized form. The summary report
contains a one-line entry for each requested group or subgroup of log entries and displays a count of the
log entries.
Select Analyze log on the Product Activity Log display. The following options are available:
v Display or print a list of entries for one or all subsystems in a one-line-per-entry format.
v Analyze entries that have specific reference codes, or sort by reference codes.
Service functions 95
v Analyze entries for specific devices, for groups of devices at the same logical address, or for groups of
devices of the same type.
v Display or print the detailed reports, including the hexadecimal data, for individual entries. You can
display or print the formatted report. For large reports, the print option is recommended.
v Summarize entries by using the following parameters:
– Time and date
– Device type
– Resource name
– Reference code
– Subsystem
v Sort entries by using the following parameters:
– Time and date
– Time of day
– Logical address
Note: To gather information by using the resource name, select the Display summary option. Then
select the F9 key (Sort by...) and sort by resource name. The Log Summary by Resource Name
display appears and shows a summary of the resources and the number of entries. For
details, see Figure 48 on page 99.
Device selection:
Option . . . . . . . . . . 1 1=Types, 2=Resource names
Device types or Resource names
*ALL *ALL...
You can use an asterisk (*) to request log entries for the device and reference code selections on the Select
Analysis Report Options displays. The asterisk symbol must be the rightmost character of the specified
string. The string, including the asterisk symbol, cannot exceed the total number of characters that are
allowed in that string. For example, a request of A00* displays all the log entries that begin with A00.
This option allows you to analyze all data that is associated with the same log ID. The system logs
related events that have the same log ID.
Note: Events that are related use the same log ID. For example, if a workstation controller has an error
that causes an automatic dump, both the permanent error and the IOP dump have the same log
ID.
Note: To change the size of all the logs at one time, select the Change all function.
You can send the output of this option to a printer (if available) or to the console.
Select the Work with removable media lifetime statistics option to display a lifetime entry report. This
report contains information about various volume IDs. The customer might want to exchange media that
has a high number of read or write errors. To ensure accurate statistics, each media must have a unique
volume ID.
Service functions 97
Work with Lifetime Statistics
Removable media . . . . . . : Self-configured tape device and 1/4 inch cartridge tape
If the following symbols appear before the volume ID on the Work with Lifetime Statistics display,
perform the suggested action:
Select this option from the Product Activity Log display. This option allows you to:
v Display or print session statistics for a diskette or tape unit
v Select a specific media type
v Select a time range
v Select a volume ID
v Review session counters for a specific volume or removable media
You can send the output of this option to a printer (if available) or to a workstation.
Select this option from the Product Activity Log display. This option allows you to view a description of
the code that appears in the reference code field.
Each analysis report can be sorted by date, time, logical address, entry classification, or resource name.
The selected sort option determines the order of the log entries and the type of summary report that is
displayed or printed.
The sort option is used for problem analysis and preventive maintenance. The following are examples of
sorted entries:
Figure 47. Example Log Summary by Entry Classification and Reference Code
For details on the logical address format as it appears on the printout, see “Logical address format” on
page 108.
Service functions 99
You can also display logical address information from the Hardware Service Manager function. For
details, see “Hardware Service Manager” on page 43.
Note: The logical address field that appears on the Display Address Information for Resource display
does not list the address in the BBCb format.
Serial Resource
Name Type Model Number Name
LWS 2661 000 00-00000 CTL01
Physical location:
Frame ID . . . . . . . : 1
Card Position . . . . . : 5
Device Position . . . . :
Logical address:
SPD bus:
System bus . . . . . . : 1
System board . . . . . : 0
System card . . . . . . : 2
F3=Exit F12=Cancel
Press the F11 function key to step through screens to view the following information:
v Class (entry classification)
v Library
v Logical address
v Physical location
v Component information
v Reference code description
v Resource name/type
Note: If the SRC you are using occurred more than 24 hours ago, change the “From:” and “To:”
Dates and Times from the 24-hour default.
f. Use the defaults on the Select Analysis Report Options display by pressing Enter.
g. Find the entry in the Product Activity Log that matches that SRC.
2. Select the Display Detail Report for Resource display. See the example of this display below.
Serial Resource
Name Type Model Number Name
STORAGE 6512 001 10-4294009 SI05
Class . . . . . . . . . . : Permanent
System Ref Code . . . . . : 65123400
I/O processor card detected device error
Serial Resource
Name Type Model Number Name
STORAGE 6512 001 10-4294009 SI05
Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F EBCDIC
000000 C5D3F0F4 00000160 00E00180 77B7695E EL04...-.......;
000010 E8A70000 000008C8 20E00602 01320000 Y......H........
000020 34000000 11000000 00000000 009C0000 ................
000030 F6F5F1F2 F0F0F140 F1F060F4 F2F9F4F0 6512001 10-42940
000040 F0F9F6F5 F1F20000 00000001 00060000 096512..........
000050 00020000 FFFFFFFF FFFFFFFF FFFF0000 ................
000060 00000000 00000000 00000000 F4404040 ............4
000070 40000000 00000000 00000000 00000000 ...............
000080 00000000 00000000 00000000 00000000 ................
000090 00000000 00000000 00000000 00000000 ................
0000A0 00000000 00000000 00000000 00000000 ................
0000B0 00000000 00000000 40404040 40404040 ........
More...
Press Enter to continue.
F3=Exit F12=Cancel
Serial Resource
Name Type Model Number Name
STORAGE 6512 001 10-4294009 SI05
Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F EBCDIC
000180 D0007800 65120001 34000620 1100FFFF }...............
000190 FFFFFFFF 31090000 00001100 03C00000 .............{..
0001A0 00000000 00000000 00000000 00000000 ................
0001B0 00000000 00000000 00000000 00000000 ................
0001C0 00000000 00000000 00000000 E0000008 ................
0001D0 00000000 00000000 00000000 00000000 ................
0001E0 00000018 00000002 E00401F0 10002000 ...........0....
0001F0 00000000 40000000 00000000 000002CC .... ...........
000200 CCCC0000 00000000 00800000 00000000 ................
000210 08100000 00000000 F0200040 00800000 ........0.. ....
000220 00000000 04000000 08000040 E000E221 ........... ..S.
000230 800084F3 00000002 0000001B 110003C0 ...3...........{
More...
Press Enter to continue.
F3=Exit F12=Cancel
Figure 52. Hexadecimal Report for Resource Offset Location Example where the rightmost hex digit of offset 000182
is 8
Serial Resource
Name Type Model Number Name
STORAGE 571A 001 10-4294009 DC01
Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F EBCDIC
000180 F8407200 F5F7F1C1 F0F0F0F1 3400031D 8 ..571A0001....
000190 00233104 00FFFFF4 F0F0F0F0 F0F0F0F0 .......400000000
0001A0 1104E255 F0F0F0F0 F0F0F0F0 40404040 ..S.00000000
0001B0 40404000 00FF0000 04440000 A1D0038D ..........}..
0001C0 0713000C 00000000 00000000 70000200 ................
More...
F3=Exit F12=Cancel
Figure 53. Hexadecimal Report for Resource Offset Location Example where the rightmost hex digit of offset 000182
is 2
6. Using hexadecimal arithmetic, add the value in offsets 170 - 173 to the value in offsets 174 - 177. For
example, 000001C8 + 00000410 = 000005D8
If the value of the rightmost hex digit at this offset is 8: Using hexadecimal arithmetic, add 0000000A
to the offset you calculated. This will be the location of the unit address in the form abcdefgh. For
example, 00005DA + 0000000A = 000005E4
If the value of the rightmost hex digit at this offset is 2: Using hexadecimal arithmetic, add 00000010
to the offset you calculated. This will be the location of the unit address in the form abcdefgh. For
example, 00005DA + 00000010 = 000005EA
Record this address information. If you were sent here by another procedure, return to the procedure
that sent you here.
This ends the procedure.
For information on interpreting the hexadecimal report, see “Hexadecimal report” on page 109.
Keep the following in mind while viewing Product Activity Log reports:
v The data in the product activity log wraps.
v The newest log entries overlay the older ones.
v There is not an option to delete or clear data, but you can reduce the log sizes so that they wrap more
quickly.
Figure 54 on page 104 is an example of a printed product activity log report. You can display the same
information online by selecting various options and function keys.
2661B000 05/05/94 08:08:13 PERM 1/ 1/0/ 0-1/1/ 0/ 0/ 0/1 COM1 2661 001 00-010111 80000040
Entries in the log might have been previously resolved (for example, machine check entries).
For more information on resource names, see “Resource name” on page 105.
For more information on interpreting disk storage log entries, see the error information sections under
Recovery Procedures in the Repair and Parts information.
If the system cannot display a character in any of the following fields, it displays an asterisk (*) instead of
that character:
v Resource
v Type
v Model
v Serial number
v Volume ID
You can use the Log Analysis report to analyze problems that occur over a period of time. Look for error
patterns such as multiple I/O processor errors that occur at the same time, or errors caused by the
environment that occur at the same time of the day or week. Figure 55 on page 105 shows an example of
entries that were logged in a 24-hour period. As you cycle through the different views of the Log
Analysis Report screens, note that F11 shows variable text: Such as View Description, View Logical
Address, View Physical Location, View Component Information, and View Resource Identification.
F3=Exit F5=Refresh
F11=View description F12=Cancel
Resource name
You can change the assigned resource name.
The Name or Resource name field contains a description of the resource that is associated with the entry.
Server hardware and server LIC will have the reserved name *PLATFORM.
The system assigns a resource name, but that name might be changed to a new value by the customer.
Depending on the data, the following priority scheme is used for the name field:
1. Device name
2. Controller name
3. Line name
4. Network interface name
5. A name that is created based on the data in the entry
To select the Display report option, type 5 in the Opt (option) field for a specific resource and press
Enter. A detailed report for that resource appears. If more than one entry has the same log ID, they are
presented in the order of occurrence.
Serial Resource
Name Type Model Number Name
LWS 7209 000 00-00000 CTL01
Class . . . . . . . . . . : Permanent
Description . . . . . . . : Battery power unit needs service.
Out of alternate sectors for disk storage.
For more information on resource names, see “Resource names” on page 175.
The Type, Model, and Physical location fields provide entry information that can assist in problem analysis.
The Physical location field contains the location of the resource that is most closely related to the entry.
You can also use the address information function (see “Address information function” on page 99) and
the logical address (see “Logical address format” on page 108) to gather details about the resource type,
model, and location. For more information on resources, see “Hardware Service Manager” on page 43.
Note: When the I/O processor is not known for I/O bus entries, press the Address Information function
key from the Display Detail Report for Resource display to view the configuration information. Use
the configuration information to determine the card position of the I/O processor.
Class
The Class field describes the event that logged the entry.
Some events are related to errors that were detected, and some events are activities that normally occur.
The meaning of Class varies depending on the system, subsystem, or device against which the entry was
logged. Perform a service action only when directed by a system operator message, the directed service
procedures, or your next level of support.
The system reference code identifies a unique logging condition. The system reference code field consists
of a four-character hardware or software error group, followed by a four-character unit reference code.
System Licensed Internal Code entries might appear more than once for a single problem. This occurs
when the original system reference code is permanent or temporary and additional data is logged at the
same time. The additional data can be informational, temporary, an IOP dump, or any other classification.
Errors with the same Log ID are generally associated with the same problem. An exception to this would
be when the Log ID counter reaches the maximum value and starts over, possibly resulting in a new
error being assigned a Log ID that is also used by an existing older entry. Errors that have the same Log
ID, but dates that are months or years apart, are indicative of this situation.
Use the logical address to identify the resource entry. For details, see Figure 54 on page 104.
To sort by logical address, select Analyze log on the Product Activity Log display. Then select the F9 key
(Sort by...) and sort by logical address.
For more information on the address, use the address information function. For details, see “Address
information function” on page 99.
The values of F, G, H, J, and K vary, depending on the unit address type (E). Use the following
information to determine the Unit address data (FGHJK) representation.
Table 6. Unit address (E) definitions
Unit Address
Value Unit Address Data
Unit Address
E Definition F G H J K
0 Reserved - - - - -
1 Communications I/O bus Adapter Port Channel -
2 Storage I/O adapter I/O bus Controller Device -
3 Workstation I/O bus Adapter Port Device Session
4 Auxiliary Processor I/O bus Auxiliary Adapter Port -
Processor
5 Library I/O adapter I/O bus Library Controller Device
6 Cryptography I/O bus Adapter Device - -
The Logical address field contains the bus address and the unit address. The bus address describes the
hardware bus, board, and card information. The unit address describes the subsystem and identifying
data. For details, see Table 6.
Note: To locate a device or card that is within the system unit, use the physical address information.
Sequence number
The sequence number increases by two each time an entry is placed in the log.
The sequence number increases by two each time an entry is placed in the log.
The secondary code is a 4-byte hexadecimal value that provides additional detailed entry information.
The secondary code can be the I/O adapter return code that is used for communications protocol or
Licensed Internal Code problems. The secondary code is used for problem analysis.
Table ID
The table ID identifies a group of reference codes for the system or device.
The table ID identifies a group of reference codes for the system or device. For a complete listing of
reference codes, see List of system reference codes.
IPL source/state
The IPL source indicates the IPL mode (A, B, or D) that was selected at the time the entry was logged,
and the IPL source indicates the IPL mode (A, B, or D) that was selected at the time the entry was
logged.
The IPL source indicates the IPL mode (A, B, or D) that was selected at the time the entry was logged.
The state shows the system status at the time the entry was logged. The values of the State field include:
0 (Not used)
1 During IPL
2 During power down
3 System in full paging
4 During diagnostic tests
5 Occurred prior to IPL
6 During DST
7 System in limited paging
8 System in pre-limited (static) paging
9 System has not entered pre-limited paging
Hexadecimal report
Press F6 (Display hexadecimal report) to view the hexadecimal dump information.
For an example, see Figure 56 on page 106. This function is optional for this report, but it might provide
additional information. Figure 51 on page 102 shows an example of the first page of information logged
in the hexadecimal dump.
Note: If a character in the EBCDIC field cannot be displayed, a period (.) displays instead of that
character.
To interpret the information in the hexadecimal dump, read the Description column in Table 7 on page 110
or Table 8 on page 110 until you find the item you want (for example, reference code). Read across to the
leftmost column to find the hexadecimal offset.
Table 9 on page 111 is generally reserved for engineering use. However, to get additional information for
IOP product activity log entries at DST when using a D-IPL (which begins at offset hex 000180), see
“More information from hexadecimal reports” on page 111.
Table 9. Hexadecimal dump byte assignments for variable component specific data
Hexadecimal Offset Length in Bytes Description
0180 This field is different for each log entry and is intended
for engineering use only. However, see “More
information from hexadecimal reports” for examples of
how the hexadecimal information can be interpreted for
a D-IPL.
You can get additional information for IOP 90xx reference code product activity log entries at DST by
using a D-IPL.
Note: Formatting is available (F4=Additional Information) for IPL from disk (A- or B-IPL). Formatting is
not available in DST from a D-IPL.
Use the information below and the example displays on the following pages to interpret the hexadecimal
dump information that begins at offset hex 000180. Use the following table to determine which figures or
tables to use.
Note: If the rightmost hex digit of offset 000182 is 8, get the format number from offset 00019F. Then use
the following table to determine what figure to use.
Note: If the rightmost hex digit of offset 000182 is 2, get the format number from offset 0001B5. Then use
the following table to determine what table to use.
Table 11. Format table reference
Format number Reference the following figures
01 Table 1. Format 01.
02 Table 2. Format 02.
03 Table 3. Format 03.
04 Table 4. Format 04.
Serial Resource
Name Type Model Number Name
STORAGE 6607 070 00-68753
Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F EBCDIC
000180 F8407800 65320001 90920210 010400FF 8 .......k......
000190 66070000 00001306 87531400 123D0001 ........g.......
0001A0 00000000 00000000 CA000003 00000000 ................
0001B0 65320001 07050011 00000000 00000000 ................
0001C0 00000004 00000003 00000000 00000000 ................
0001D0 F6F6F0F7 13068753 010400FF 00000000 6607..g.........
0001E0 00000000 65320001 07050011 47000001 ................
0001F0 07069205 C0004000 00000021 00000030 ..k.{. .........
000200 00000000 00000000 F6F6F0F7 00071575 ........6607....
000210 010300FF 00000000 00000000 65320001 ................
000220 07050011 47000001 07069205 C0004000 ..........k.{. .
000230 00000000 00000000 00000000 00000000 ................
000240 F6F6F0F7 00259DE8 010200FF 00000000 6607...Y........
000250 00000000 65320001 07050011 47000001 ................
000260 07069205 C0404040 00000000 00000000 ..k.{ ........
000270 00000000 00000000 E2E5C3C4 D6C3E2C3 ........SVCDOCSC
000280 D7D7F2F9 C1F800D5 00000000 00000000 PP29A8.N........
000290 00000000 00000000 00000000 00000000 ................
0002A0 00000000 00000000 00000000 00000000 ................
0002B0 00000000 00000000 00000000 00000000 ................
0002C0 00000000 00000000 00000000 00000000 ................
0002D0 00000000 00000000 C3D7D7F8 F9F2F9D5 ........CPP8929N
0002E0 F6F5F3F2 F9F0F9F2 F0F0F0F0 F0F0F0F0 6532909200000000
0002F0 F0F0F0F0 F0F1F6C3 F0F1F3F3 0000D5D5 0000016C0133..NN
000300 00000000 00000000 00000000 00000000 ................
Figure 57. Example Hexadecimal Report, Device Formatting Log (unformatted information)
Serial Resource
Name Type Model Number Name
STORAGE 6607 070 00-68753
Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F
000180 -------- -------- -------- --------
000190 -------- -------- -------- ------01
0001A0 -------- -------- -------- --------
0001B0 -------- -------- -------- --------
0001C0 # errors # errors -------- --------
detected logged -------- --------
0001D0 Device1 Device1 Device1 New Dev1
Type Serial UnitAddr Type
0001E0 New Dev1 IOP type IOP Cache
Serial & model Serial Type/Mod
0001F0 Cache -------- -------- --------
Serial -------- -------- --------
000200 -------- -------- Device2 Device2
-------- -------- Type Serial
000210 Device2 New Dev2 New Dev2 IOP type
UnitAddr Type Serial & model
000220 IOP Cache Cache --------
Serial Type/Mod Serial --------
000230 -------- -------- -------- --------
-------- -------- -------- --------
000240 Device3 Device3 Device3 New Dev3
Type Serial UnitAddr Type
000250 New Dev3 IOP type IOP Cache
Serial & model Serial Type/Mod
000260 Cache -------- -------- --------
Serial -------- -------- --------
Serial Resource
Name Type Model Number Name
STORAGE 6607 070 00-68753
Device . . . . . . . . . : 1 2 3
Unit Address . . . . : 010400FF 010300FF 010200FF
Type . . . . . . . . : 6607 6607 6607
Serial Number . . . : 13068753 00071575 00259DE8
New Device Information:
Type . . . . . . . . : **** **** ****
Serial Number . . . : 00000000 00000000 00000000
I/O Processor Information:
Type . . . . . . . . : 6532 6532 6532
Serial Number . . . : 07050011 07050011 07050011
Cache Adaptor Card Information:
Type . . . . . . . . : 4700 4700 4700
Serial Number . . . : 07069205 07069205 07069205
Figure 59. Example Hexadecimal Report, Device Formatting (As formatted information for A or B IPL)
Serial Resource
Name Type Model Number Name
STORAGE 6532 001 00-50011
Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F EBCDIC
000180 F4407800 65320001 90210210 0FFFFFFF 4 ..............
000190 00000000 00000000 00001400 12400002 ............. ..
0001A0 00000000 00000000 CA000003 00000000 ................
0001B0 65320001 07050011 00000000 00000000 ................
0001C0 F6F6F0F7 0025ED09 000200FF 000200FF 6607............
0001D0 F6F6F0F7 00158135 000100FF 000100FF 6607..a.........
0001E0 F6F6F0F7 00259DE8 010200FF 00000000 6607...Y........
0001F0 F6F6F0F7 00008326 010100FF 00000000 6607..c.........
000200 F6F6F0F7 00071575 010300FF 00000000 6607............
000210 F6F6F0F7 13068753 010400FF 00000000 6607..g.........
000220 00000000 00000000 00000000 00000000 ................
000230 00000000 00000000 00000000 00000000 ................
000240 00000000 00000000 00000000 00000000 ................
000250 00000000 00000000 00000000 00000000 ................
000260 000000FF 00000004 00000000 00000000 ................
000270 00000000 E2E5C3C4 D6C3E2C3 D7D7F2F9 ....SVCDOCSCPP29
000280 C1F800D5 00000000 00000000 00000000 A8.N............
000290 00000000 00000000 00000000 00000000 ................
0002A0 00000000 00000000 00000000 00000000 ................
0002B0 00000000 00000000 00000000 00000000 ................
0002C0 00000000 00000000 00000000 00000000 ................
0002D0 00000000 C3D7D7C5 C1F0F2D5 F6F5F3F2 ....CPPEA02N6532
0002E0 F9F0F2F1 F0F0F0F0 F0F0F0F0 F0F0F0F0 9021000000000000
0002F0 F0F0C4F4 F0F1F3F3 0000D5D5 00000000 00D40133..NN....
000300 00000000 00000000 00000000 00000000 ................
Figure 60. Example Hexadecimal Report, Array Member Formatting Log (unformatted information)
Serial Resource
Name Type Model Number Name
STORAGE 6532 001 00-50011
Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F
000180 -------- -------- -------- --------
000190 -------- -------- -------- ------02
0001A0 -------- -------- -------- --------
0001B0 -------- -------- -------- --------
0001C0 Member0 Member0 Expected Current
Type Serial Address Address
0001D0 Member1 Member1 Expected Current
Type Serial Address Address
0001E0 Member2 Member2 Expected Current
Type Serial Address Address
0001F0 Member3 Member3 Expected Current
Type Serial Address Address
000200 Member4 Member4 Expected Current
Type Serial Address Address
000210 Member5 Member5 Expected Current
Type Serial Address Address
000220 Member6 Member6 Expected Current
Type Serial Address Address
000230 Member7 Member7 Expected Current
Type Serial Address Address
000240 Member8 Member8 Expected Current
Type Serial Address Address
000250 Member9 Member9 Expected Current
Type Serial Address Address
Figure 61. Example Hexadecimal Report, Array Member Formatting Log Template
Array member formatting log example (as formatted information for A or B IPL)
Serial Resource
Name Type Model Number Name
STORAGE 6532 001 00-50011
Array Member . . . . . . : 0 1 2 3 4
Type . . . . . . . . : 6607 6607 6607 6607 6607
Serial Number . . . : 0025ED09 00158135 00259DE8 00008326 00071575
Unit Address:
Current . . . . . . : 000200FF 000100FF 00000000 00000000 00000000
Expected . . . . . . : 000200FF 000100FF 010200FF 010100FF 010300FF
Array Member . . . . . . : 5 6 7 8 9
Type . . . . . . . . : 6607 **** **** **** ****
Serial Number . . . : 13068753 00000000 00000000 00000000 00000000
Unit Address:
Current . . . . . . : 00000000 00000000 00000000 00000000 00000000
Expected . . . . . . : 010400FF 00000000 00000000 00000000 00000000
Figure 62. Example Hexadecimal Report, Array Member Formatting (As formatted information for A or B IPL)
Serial Resource
Name Type Model Number Name
STORAGE 6532 001 00-50011
Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F EBCDIC
000180 50407800 65320001 90120210 0FFFFFFF & ..............
000190 00000000 00000000 00001400 123C0003 ................
0001A0 00000000 00000000 CA000003 00000000 ................
0001B0 65320001 07050011 00000000 00000000 ................
0001C0 00000000 00000000 47000001 07069205 ..............k.
0001D0 F8F6C7F8 F1F4F9C3 D7D7F8F9 F8F100D5 86G8149CPP8981.N
0001E0 00000000 00000000 00000000 00000000 ................
0001F0 00000000 00000000 00000000 00000000 ................
000200 00000000 00000000 00000000 00000000 ................
000210 00000000 00000000 00000000 00000000 ................
000220 00000000 00000000 00000000 00000000 ................
000230 C3D7D7C5 C1F0F2D5 F6F5F3F2 F9F0F1F2 CPPEA02N65329012
000240 F0F0F0F0 F0F0F0F0 F0F0F0F0 F0F0C4F4 00000000000000D4
000250 F0F1F3F4 0000E8D5 00000000 00000000 0134..YN........
Figure 63. Example Hexadecimal Report, Configuration Formatting log (unformatted information)
Serial Resource
Name Type Model Number Name
STORAGE 6532 001 00-50011
Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F
000180 -------- -------- -------- --------
000190 -------- -------- -------- ------03
0001A0 -------- -------- -------- --------
0001B0 Current Current Current Current
IOP type IOP Cache Cache
& model serial type serial
0001C0 Expected Expected Expected Expected
IOP type IOP Cache Cache
& model serial type serial
Serial Resource
Name Type Model Number Name
STORAGE 6532 001 00-50011
Figure 65. Example Hexadecimal Report, Configuration Formatting Log (As formatted information for A or B IPL)
Serial Resource
Name Type Model Number Name
STORAGE 2757 001 10-0322005 DC03
Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F EBCDIC
000000 C5D3F0F5 000000A0 00E00180 82745D0F EL05........b.).
000010 1FD78000 00002CE0 20100084 049F0000 .P.........d....
000020 902F0000 11000000 00000000 00C70000 .............G..
000030 F2F7F5F7 F0F0F140 F1F060F0 F3F2F2F0 2757001 10-03220
000040 F0F50000 0000F2F7 F5F70002 00020000 05....2757......
000050 00200000 0002FFFF FFFFFFFF 0004FFFF ................
000060 00000000 00000000 00000000 40404040 ............
000070 40404040 40400000 00000000 00000000 ..........
000080 00000000 00000000 00000000 00000000 ................
000090 00000000 00000000 00000000 00000000 ................
0000A0 00000000 00000000 00000000 00000000 ................
0000B0 00000000 00000000 40404040 40404040 ........
0000C0 40404040 40404040 40404040 40404040
0000D0 40404040 40404040 40404040 40404040
0000E0 F2F7F5F7 F0F0F0F1 0000E2D3 C9C3C9D6 27570001..SLICIO
0000F0 4040E5F5 D9F2D4F0 40400000 00000000 V5R2M0 ......
000100 00B90000 00000000 000000C7 00000000 ...........G....
000110 00000000 00000000 00000000 00000000 ................
000120 00000000 00000000 00000000 00000000 ................
000130 00000000 00000000 00000000 00000000 ................
000140 C4C3F0F3 40404040 40404040 40404040 DC03
000150 D5C5C5C4 E5C1D3C9 C4D740D5 00070001 NEEDVALIDP N....
000160 00000000 A0200007 00000000 00000000 ................
000170 00000000 00000000 0003001E 000000A0 ................
000180 A0407800 27570001 902F0200 4FFFFFFF . ...*......|...
000190 00000000 00000000 00001400 623E0004 ................
0001A0 F6F6F0F7 0026121D 410500FF 410500FF 6607............
0001B0 F6F6F0F7 00248B85 410400FF 410400FF 6607...e........
0001C0 F6F6F0F7 0014BE1F 410300FF 410300FF 6607............
0001D0 F6F6F0F7 0014C0F0 410200FF 410200FF 6607..{0........
0001E0 F6F6F0F7 001403C8 410100FF 410100FF 6607...H........
0001F0 F6F6F0F7 0014BEA4 410800FF 410800FF 6607...u........
000200 00000000 00000000 00000000 00000000 ................
000210 00000000 00000000 00000000 00000000 ................
Figure 66. Example Hexadecimal Report, Array Addendum Formatting Log (unformatted information)
Serial Resource
Name Type Model Number Name
STORAGE 6532 001 00-50011
Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F
Figure 67. Example Hexadecimal Report, Array Addendum Formatting Log Template
Serial Resource
Name Type Model Number Name
STORAGE 2757 001 10-0322005 DC03
Array Member . . . . . . : 10 11 12 13 14
Type . . . . . . . . : 6607 6607 6607 6607 6607
Serial Number . . . : 0026121D 00248B85 0014BE1F 0014C0F0 001403C8
Unit Address:
Current . . . . . . : 410500FF 410400FF 410300FF 410200FF 410100FF
Expected . . . . . . : 410500FF 410400FF 410300FF 410200FF 410100FF
Array Member . . . . . . : 15 16 17
Type . . . . . . . . : 6607 **** ****
Serial Number . . . : 0014BEA4 00000000 00000000
Unit Address:
Current . . . . . . : 410800FF 00000000 00000000
Expected . . . . . . : 410800FF 00000000 00000000
Figure 68. Example Hexadecimal Report, Array Addendum Formatting (as formatted information for A or B IPL)
Attention: Customer applications may be sensitive to system date and time settings. Incorrect date and
time settings may cause data loss. Ensure that the customer knows the date and time that you have set.
Note: If the system is logically partitioned, then you must use the Advanced System Management
Interface (ASMI) to set the system date and time. For information on using ASMI to set the system
date and time, see Changing the time of day.
Use one of the following methods to set the date and time:
v If the system is powered off, perform a Manual mode (attended) IPL. You can set the date and time on
the IPL Options display.
v If the system is powered on, perform the following procedure:
1. To set the correct date, enter the system command:
mm = month
dd = day
yy = year
2. Press Enter.
Note: This sample uses the month, day, and year format. To determine the format for your system,
enter DSPSYSVAL QDATE.
3. To set the correct time, enter the system command:
CHGSYSVAL
QTIME VALUE(’hhmmss’)
where:
hh = 24-hour time
mm = minutes
ss = seconds
4. Press Enter. This ends the procedure.
The operating system is a collection of system programs that control the overall operation of the system.
i5/OS is an example of such an operating system. Systems can run one or more operating systems. When
there is more than one operating system, i5/OS is the dominant operating system.
The Hardware Service Manager function (under Start a Service Tool) indicates which operating system is
dominant on the system. The Release field on the Hardware Service Manager display or printout shows the
following values:
0 Unknown
This indicates that an alternate IPL was performed.
1 i5/OS is dominant
For more information on the Hardware Service Manager function, see “Hardware Service Manager” on
page 43.
System password
If a system password is required, the Verification of System Password Failed display appears just prior to
the IPL or Install the System display.
If the Verification of System Password Failed display appears after a repair action, contact your next level
of support for assistance.
Selection
__
F3=Exit F12=Cancel
When customer information is known by manufacturing, the new system will be shipped with the correct
system password.
The system requires a new system password each time someone enters the system serial number and at
each model and processor card feature change. The new system password, which is required at the time
of the first IPL, is provided by IBM if IBM knows the end user. Customers who do not have the system
password when they need it must contact their marketing representative to place a system password
order.
If the correct system password is not entered, you can select a system password bypass period to allow
time to obtain the correct system password from the marketing representative. If the bypass period
expires, the system will not complete the next IPL unless the correct system password is entered. While in
bypass mode, by way of control console messages, the system indicates the amount of time that remains
before the bypass period expiration date.
Note: If the system password was changed at the most recent IPL, performing a fast power off (control
panel function 08) might cause that new password information to be lost.
The SUID is needed only to support SOM software functions. An incorrect SUID does not affect other
system functions. To order a new SUID, contact the marketing representative (hardware feature code
1311).
A console is a workstation that allows you to view and control system operations. The primary console is
the first workstation that the system identifies. It is attached to the first input/output adapter (IOA) or
input-output processor (IOP) that supports workstations. The alternative console is the workstation that
functions as the console when the primary console is not operational. The system can assign up to two
alternative consoles. The first alternative console can only be a twinaxial workstation that is attached to
the same IOP as the primary console. The next alternative console is a workstation that is attached to the
next IOA or IOP that is capable of supporting workstations.
The IOA or IOP that supports a console must be on the system bus (bus 1).
If a workstation is not correctly attached to the first IOA or IOP that is capable of attaching workstations,
the system will not assign a primary console. If it does not assign a primary console, the system displays
a reference code on the control panel. If the system is set for Manual mode, it stops during the IPL.
For more information on how to determine the primary and alternative consoles, see “Identifying the
consoles when the system is operational” on page 126.
For a workstation to be the primary console, it must be operational and attached to the system bus. It
must also have the correct port and address assigned. If the workstation is a personal computer, it must
also have an active workstation emulation program.
When the system is operational, you can determine the primary and alternative consoles by performing
one of the following:
v Look at the display.
– If the dominant operating system is i5/OS, look for a sign-on display that shows DSP01 in the
upper right corner. DSP01 is the name that the system assigns to the primary console.
Note: This resource name might have been changed by the customer.
v Use system commands to assist in identifying the consoles. See the system operation information for
more details on commands.
v Use the Hardware Service Manager function to assist in identifying the consoles:
1. Select the System bus resources option on the Hardware Service Manager display. The System Bus
Resources display allows you to view the logical hardware resources for the system bus.
Look for a (<) symbol next to an IOP. The (<) symbol indicates that the console attaches to this IOP.
2. Select the Resources associated with IOP and the Display detail options to collect more information
about the consoles.
For more details, see “Hardware Service Manager” on page 43.
History file
The history file provides a high-level audit trail of the actions that are performed by the system.
The history file provides a high-level audit trail of the actions that are performed by the system. The
history file information can assist the system operator, the data processing manager, and the service
representative.
The commands that are used to display the history file vary depending on your operating system. For
information on service commands, see “Commonly used i5/OS service commands” on page 224.
Notes:
1. The term fix refers to a program temporary fix (PTF) to the Licensed Internal Code, operating
system, or other licensed programs.
2. You should submit a copy of the history file with every authorized program analysis report
(APAR).
3. 99xx messages can contain SRC information.
The low-level debug functions (Functions 63-70) use sub-functions. This means that these functions have
a function range inside them (00-FF) where you can display or enter information.
For more information on the low-level debug control panel functions, see “Low-Level Debug (LLD) panel
functions” on page 147.
Getting started
About this task
Results
Repeat steps 1 through 9 for additional data that you were instructed to collect.
Call your next level of support and give them the information you collected to write a LIC APAR.
Note: If the system has logical partitions, the terms: console, alternative console, IPL, SST, DST, load source,
alternate load source, power off, power on, panel function, product activity log, service action log, Licensed
Internal Code log, and operating system refer to the logical partition that you are servicing (unless
otherwise stated in a procedure, Failing Item, or Symbolic FRU).
Failed partition
Failures can be reported from the partition that experienced the problem with a resource. Attempt
to service from the failed partition unless otherwise directed.
System Attention Light
For partitions, the system attention light is represented as the partition’s State.
Powering off and on
Read and understand the power-off and power-on procedures referenced when a procedure
directs you to power on or power off a system or partition.
v For information on using the Hardware Management Console (HMC) to power on logical
partitions, see Activating a partition profile.
v For information on using the HMC to power off logical partitions, see Shutting down i5/OS
logical partitions.
Note:
v To perform a main storage dump or platform dump of a partition, you must use the Service
Focal Point. For information on using the Service Focal Point to perform a main storage dump
or a platform dump, see Performing a platform or main storage dump.
v When servicing a logical partition, you must use the service documentation that supports the
version and release of the logical partition. See “Determining the release level of a logical
partition” on page 130.
The following examples show some of the reasons why the system might show missing resources and
corresponding actions to take.
v Residual resource names in primary or secondary partitions after a reconfiguration of resources. When
resources are removed from a partition, there are two options:
– 1=Remove leaves the resource names (usually when switching resources across partitions
temporarily. This option is used when the customer intends to switch the resources back to the
original partition sometime in the future and wants to use the same resource names when the future
switch occurs). If this option is selected, the resource names will show as non-reporting in the
partition that they were removed from following the next IPL of that partition.
– 2=Remove and clear hardware resource(s) removes the resource names (when permanently moving
or removing the resource).
Corrective action: Work with the customer to understand why the option to leave resource names was
selected. These resources should be left as is if the customer intends to switch the resource back to the
partition from which they were removed. If they are removed and the resource is switched back to that
partition, a new resource name is created and the resource name is incremented. This will cause
problems with the device descriptor that uses this resource; for example, TAP01 being used by multiple
partitions.
v The resource has actually failed or has been removed from the system.
Use this procedure to locate a logical partition’s console and load source.
1. In the Navigation Area of the Hardware Management Console (HMC), open Server and Partition.
2. Select Server Management.
3. In the contents area, open the server which contains the partition profile with that you want to work.
4. Open Partitions.
5. Right-click the profile.
6. Right-click Properties.
7. Select the Tagged I/O tab.
Results
Use this procedure to determine the local partition time and date values for the primary partition.
1. From the Main Menu, select Define or change the system.
2. From the Define or Change the System display, select Work with system values.
3. From the Work With System Values display, enter the Display option for the QDATE and QTIME
system values.
Results
Use this procedure to find the SRC history list that is created during an IPL of a logical partition.
1. In the Navigation Area of the Hardware Management Console (HMC), open Server and Partition.
2. Select Server Management.
3. In the contents area, open the server which contains the partition profile with that you want to work.
4. Open Partitions.
Results
For information on using the HMC to perform control panel functions, see Control panel functions.
This procedure helps you locate the logical partition that owns a FRU or system I/O resource. It is used
to direct you to the correct logical partition in which to conduct a repair or exchange action.
Note: If you are locating a FRU, you are required to have the logical address or both the serial and the
part number.
1. In the Navigation Area of the Hardware Management Console (HMC), open Server and Partition.
2. Select Server Management.
3. In the contents area, right click the managed system.
4. Right click Properties.
5. Select the I/O tab.
Results
Use this procedure to set the IPL source and IPL mode for a logical partition.
1. In the Navigation Area of the Hardware Management Console (HMC), open Server and Partition.
2. Select Server Management.
3. In the contents area, open the server that contains the partition profile with which you want to work.
4. Open Partitions.
5. Right click the partition.
6. Right click Properties.
7. Select the Settings tab.
Results
For more information on changing the IPL source for a logical partition, see Changing the IPL type for an
i5/OS logical partition. For more information on changing the IPL mode of a logical partition, see
Changing the operating mode for an i5/OS logical partition.
Note: To perform this procedure, you must have the resource name of the high speed link (HSL) I/O
bridge resource.
1. Move to the console of the system where you know the name of the HSL I/O bridge resource in the
tower.
2. Sign on to the System Service Tool (SST) or Dedicated Service Tool (DST).
3. From the SST or DST, select Start a service tool, then Hardware Service Manager.
4. From the Hardware Service Manager, select Logical Hardware Resources.
5. From the Logical Hardware Resources display, select High Speed Link Resources.
6. From the High Speed Link Resources display, select the function Include non-reporting resources.
7. Move the cursor to the HSL I/O bridge resource of the tower and select the Display detail option.
The Display HSL Information display appears.
Figure 70. Example Display High Speed Link (HSL) Information display
8. At the Display HSL Information display, locate the Mode information of the resource.
Note: If you cannot locate the Mode information, then this HSL resource is not part of a Cluster
Resource Group (CRG) and the tower where this HSL I/O bridge resource is located cannot
be configured as switchable under iSeries OptiConnect.
9. Is the mode listed as Private or is the mode not displayed for this resource?
v Yes = the tower where this HSL I/O bridge resource is located cannot be configured as switchable
under iSeries OptiConnect. This ends the procedure.
v No = the HSL I/O bridge resource has a mode of switchable. The tower is configured as a
switchable tower under iSeries OptiConnect. Continue with the next step of this procedure.
Note: You will need the type-model and serial number to identify the HSL I/O bridge on the other
system that can own this resource.
Results
Determining the resource name and HSL loop number of an HSL I/O bridge
Determine the resource name and HSL loop number of the HSL I/O bridge resource in the alternate
system that can own a selected HSL I/O bridge resource.
1. Move to the console of the alternate system that can own the resources in the tower.
2. Sign on to the System Service Tool (SST) or Dedicated Service Tool (DST).
3. Select Start a Service Tool.
4. Select Hardware Service Manager.
5. Select Logical hardware resources.
6. Select High speed link resources.
7. Select the function Include non-reporting resources.
8. Search for the HSL I/O bridge resource name by selecting the Display detail option for each HSL
I/O bridge resource until you find the HSL I/O bridge resource that has the same type-model and
serial number you recorded for the HSL I/O bridge resource. For details, see “Determining the
power controlling and current logical system ownership of a tower.”
Figure 71. Example Display High Speed Link (HSL) Information display
9. Record the HSL loop number and Resource name for the HSL I/O bridge resource from the Display
HSL Information display.
10. Select the function Display system information from the Display HSL Information display.
Figure 72. Example Display High Speed Link (HSL) Information display
11. Record the local system type and local system serial number with the HSL I/O bridge resource and
the HSL loop number you recorded for this system earlier. This ends the procedure.
You can use the Take/release ownership option on the Select I/O Debug Function display to have the local
system take ownership of a resource or to have the local system release its ownership of a resource.
Ownership of a resource indicates which system controls the functions of a resource. Ownership may be
released only by the system that presently owns it.
The following procedure will direct you to switch ownership of switchable resources in a tower from the
current owner to the alternate system that can own those resources. To perform this procedure, you must
know:
v The system that currently owns the switchable resources in a tower. This is the system that you are
going to release the resources from.
v The alternate system that can take ownership of the switchable resources.
v The resource name of the high speed link (HSL) I/O bridge resource and the HSL loop number on the
currently owning system that will release ownership.
v The resource name of the high speed link (HSL) I/O bridge resource and the HSL loop number on the
system that will take ownership.
Attention: Perform this procedure only if you are not able to switch the ownership of the resource
using the iSeries OptiConnect user interface. Cluster Resource Group (CRG) problems may occur as the
result of using this procedure when the iSeries OptiConnect user interface is available.
1. Determine the current owner of the switchable resources in the tower if you have not already done
so. (See the procedure “Determining the power controlling and current logical system ownership of a
tower” on page 133.)
2. Move to the console of the system that is the current owner of the switchable resources in the tower.
3. Sign on to System Service Tool (SST) or Dedicated Service Tool (DST).
4. Select Start a service tool.
5. Select Hardware Service Manager.
6. Select Logical Hardware Resources.
7. Select High speed link resources.
8. Select the function Include non-reporting resources.
9. Select Resources associated with loop.
10. Move the cursor to the HSL I/O bridge resource in the tower. Search for the resource name that the
currently owning system assigned to the HSL I/O bridge resource.
11. Select the I/O Debug option.
When you select the I/O debug option on an HSL I/O bridge that has the capability of being
switched, the I/O Debug Function display appears.
Note: The following menus are shown for example use only. Due to release updates, the menus that
appear on your display might be slightly different.
Take/release ownership
Selection
F3=Exit F12=Cancel
12. From the Select I/O Debug Function display, select the Take/release ownership option. The Confirm
Release of Resource Ownership display appears.
Resource details
Resource name: BC06
Type-Model . : 1999-999
Serial number: 21-1111111
Warning: You should only attempt this action at the direction of your
service representative.
F12=Cancel
Note: If you select option two to release ownership of the resource and another system currently
owns it, the following message appears at the bottom of the screen:
You have requested that this system take ownership of this resource.
Resource details
Resource name: BC06
Type-Model . : 1999-999
Serial number: 21-1111111
Warning: You should only attempt this action at the direction of your
service representative.
F12=Cancel
25. Press Enter to confirm the ownership change. This ends the procedure.
Note: To perform this procedure, the switchable resources in the tower must be owned by the power
controlling system for the tower. For information on switching ownership of the switchable
resources in a tower, see the procedure “Switching ownership of a tower’s switchable resources”
on page 134.
Attention: Perform this procedure only if you are not able to end the Cluster Resource Group (CRG)
using the OptiConnect user interface. CRG problems may occur as the result of using this procedure
when the OptiConnect user interface is available.
1. Move to the console of the power controlling system of the tower.
2. Sign on to System Service Tool (SST) or Dedicated Service Tool (DST).
3. Select Start a service tool.
4. Select Hardware Service Manager.
5. Select Logical hardware resources.
6. Select High speed link resources.
Resource details
Resource name: BC06
Type-Model: 1999-999
Serial number: 21-1111111
Present value
Tower mode: Switchable
Requested value
Tower mode: Private
Warning: You should only attempt this action at the direction of your
service representative.
F12=Cancel
11. Is the present value of the tower mode a value that you want to change?
v Yes = proceed to the next step.
v No = The power is already in the mode you want it to be in. This ends the procedure.
12. Press Enter to confirm changing the mode of the resource.
If you press Enter at the Confirm Mode Change display, one of the following messages will appear:
v Change mode was successful.
v Unable to change mode for this hardware resource.
This ends the procedure.
Important:
v Continue with this procedure only if you were directed here from the Connect your
expansion unit topic.
v This procedure must be performed by an on-site service provider. If an on-site service
provider is not available, return to the procedure that sent you here and choose a different
option or contact your service provider.
1. Obtain a product engineering shell (PESH) and a celogin password.
Note: If the serial number of the HMC is not registered, you will not be able to generate a
pesh password.
d. Obtain an ASMI celogin password from an authorized support center.
1) Launch the ASMI and record the system date and serial number from the “Welcome” screen.
2) Give the system date and system serial number obtained in the previous step to the
authorized support center. The authorized support center will provide the ASMI celogin
password.
e. Run the pesh command on the HMC.
1) From the restricted shell window, type the following command: pesh <serial number> where
<serial number> is the serial number recorded in step 1c1.
Note: Type all alpha characters used in the serial number in uppercase characters containing
no spaces or dashes.
2) When prompted for a password, type the pesh password provided by the authorized support
center. Ensure that the password is typed using all lowercase letters. When logged in, it will
display role=hmcpe and a command prompt.
f. Switch to root on the HMC.
1) At the pesh prompt, type su - and press Enter. When prompted, type the password for root.
Note: If the password has been lost, log in as hscroot and reset the password. For more
information, refer to Creating an HMC user.
Note: Five minutes of inactivity on a virtual TTY connection allows the debug virtual TTY
connection to timeout and close.
e. Click Save Settings.
f. Telnet to the service processor on port 30002 to obtain the phyp prompt.
1) For the HMC telnet client, you do this by issuing the command telnet <service processor ip>
30002 where <service processor ip> is the name or IP address of the service processor
determined in step 2a. For example, telnet 9.5.32.12 30002
2) After the telnet session is established, wait for the ‘phyp#’ to indicate the phyp prompt is
available. This part of the procedure might take several seconds to complete.
Tip: The debug virtual TTY connection automatically closes after five minutes of inactivity.
Periodically returning to this screen and pressing Enter during this procedure will allow
you to avoid having to reconnect to the phyp prompt to enable SPCN firmware updates.
3. Disable SPCN firmware updates
a. From the phyp prompt enter the spcndownload -disable command to disable SPCN firmware
updates. The disable option will interrupt and disable the SPCN firmware updates.
Note:
v This option will begin an asynchronous process to stop the SPCN firmware updates. The
process usually takes less than one minute to complete. However, in extreme cases
where a large number of SPCN firmware updates are in progress when the stop step is
initiated, the disabled process may take up to an hour to complete.
v Disabling the SPCN firmware updates will not continue across a platform IPL. SPCN
firmware updates will be enabled following a platform IPL.
b. Enter the spcndownload -status command to determine if the disable process has completed.
Attention: Do not proceed to the next step until the disable is complete. Output from the
spcndownload -status command will let you know when the disable is complete.
4. Remove or open the back of the system.
5. Find the connector locations. If you need help finding the connectors on your expansion unit(s) or
system unit, refer to Connector locations.
6. Go to Connect the expansion units with SPCN cables.
7. Connect the ac power cables to the expansion units being added.
Tip: The power cable should be plugged into the power source prior to connecting it at the power
supply of an expansion unit.
If the expansion units have power switches ensure that they are in the on position. The expansion
units will power on automatically. Verify that the expansion units are powered on.
Note: For each expansion unit you just powered on, wait for the green power indicator to light up
on the expansion unit’s control panel. This might take up to ten minutes for each expansion
Note: If the phyp prompt session has been inactive for more than five minutes, it may have timed
out and you will need to reestablish the session using the procedure in step 2 on page 140.
a. After the PHYP prompt has been established, enter the spcndownload -enable command .
Note:
v This command enables the SPCN firmware updates.
v The enable option will enable, but not initiate SPCN firmware updates.
b. Enter the spcndownload - initiate command to start the required SPCN firmware updates. The
initiate option will asynchronously begin any required SPCN firmware updates.
Note: The SPCN firmware updates will continue to be processed after the command has
completed execution.
12. You might see one or more of the following firmware update informational logs. There is no need to
check for these log entries.
Broadcast SPCN firmware updates:
v Informational 10009107 (download started)
v Informational 100091DD (download done)
HSL/RIO SPCN firmware updates:
v Informational 1000910A (HSL/RIO download started)
v Informational 100091DE (HSL/RIO download done)
13. If the system is logically partitioned, you can now assign the new hardware to a partition without
waiting for the completion of the SPCN firmware updates.For more information about AIX®
partitions, refer to Dynamically managing physical I/O devices and slots. For more information
about Linux® partitions, refer to Dynamically managing physical I/O devices and slots on Linux. For
more information about i5/OS partitions, refer to Dynamically managing physical I/O devices and
slots.
For details on using the control panel, see the following information.
Notes:
1. Systems managed by an HMC should use the HMC to perform control panel functions. For
information on performing control panel functions using an HMC, see Control panel
functions.
2. Some control panel functions might not be available on all system types.
3. The x can be any number 0 through 9, any letter A through F, or a blank.
4. If the customer was performing the function, find out why the customer selected the function
and verify whether it is complete.
5. If you cannot change the Function/Data display or complete the selected function, go to Start of
call procedure.
Table 17, Table 18, Table 19 on page 143, and Table 20 on page 143 describe the valid IPL types, system
operating modes, speeds, and firmware IPL modes that are used in control panel functions 01 and 02.
Table 21 on page 143 describes whether the Hardware Management Console (HMC) is active for HMC
managed systems.
Notes:
1. Systems managed by the HMC should use the HMC to perform control panel functions. For
information on performing control panel functions using the HMC, see Control panel
functions.
2. OS IPL types are displayed only when the OS IPL mode has been enabled from the operating
system.
Table 17. OS IPL types
IPL type Action or description
A IPL from disk using copy A of the system Licensed Internal Code.
B IPL from disk using copy B of the system Licensed Internal Code.
C Reserved for hardware service use only under the direction of Rochester development
support.
Attention: Severe data loss can occur with improper use of this function.
D IPL from media other than load-source disk. Alternate IPL for code installation support.
Figure 77 on page 144 shows the control panel for the OpenPower® server model.Figure 78 on page 144
shows the control panel for all other server models.
A LCD screen
B Decrement button
C Enter button
D Increment
A Power push-button
B On/off power symbol
Note: The system attention light does not appear on the control panel on the model 570.
H Decrement
I Enter push-button
J Increment
To select a function number, press the Increment (↑) or Decrement (↓) button on the control panel. To
activate the function, press Enter on the control panel while the desired function number is displayed.
Note: The function that is displayed is not activated until you press Enter on the control panel.
The i5/OS virtual control panel and remote control panel are graphical representations of the physical
control panel. They install through Operations Console and allow you to access control panel functions
using a PC. For information on using a virtual or remote control panel, see Operations Console virtual
and remote control panel.
HMC
If you are managing the system with the HMC, you should use the HMC to perform control panel
functions. The HMC affects the physical control panel in the following ways:
v Except for some limited auto-platform override function, such as Auto Power On Restart and Timed
Power On, the system operating mode value has no meaning.
v The OS IPL type value is disabled in functions 01 and 02.
v Functions 11–19 will not display partition SRCs. It will continue to display SRCs from the platform
LIC.
v Functions 21, 22, 34, and 65-70 are not selectable.
For information on using the HMC to access control panel functions, see Control panel functions.
Note: The primary control panel functions can be found in the Managing the control panel functions
topic.
Notes:
1. When a function has no data to display, FF is shown.
2. The Customer extended panel functions can be found in the Managing the control panel
functions topic.
Service functions 50 through 99 are enabled when you select Manual mode and enter function 25 (service
switch 1), then function 26 (service switch 2). Sub-functions are used with Functions 51 and 57 through
64.
You can disable the service functions by selecting and entering either function 25 (service switch 1) or
function 26 (service switch 2).
To disable functions 50 through 99, select function 25 and press Enter. Functions 50 through 99 are then
no longer available.
Using Sub-functions:
Use this function to view and change dump policy and override variables. This function is available in
manual operating mode when activated by the FSP and when the CE functions have been enabled.
1. Select Function 55 and press Enter to display 55**.
2. Select the function you want to perform (refer to the table below). Use the Increment or Decrement
button to scroll to the appropriate function. Press Enter to display 55nn, where nn is the function that
you selected.
Table 22. Override of platform dump functions in Function 55
Function Action or Description
00 View policy override settings
01 Policy: As Needed
02 Policy: Never
03 Policy: Always
04 Content Override - Maximum
05 Content Override - As Required
06 Content Override - Minimum
07 Content Override - Optimum
Functions 56 to 62–Reserved:
You can enable these functions by selecting Manual mode and selecting Functions 25 and 26. The
following is a list of all the low-level debug (LLD) panel functions and a description of each.
Use this function to view a copy of the first word of the last 25 system status SRCs.
Typically, these are SRCs associated with the IPL sequence or power off sequence.
1. Select Function 63 and press Enter to display 63**.
2. Enter a sub-function between 0x00 and 0x18 to view the SRCs in sequential order, 0x18 being the most
recent. Press Enter to display 63nn, where nn is the function that you selected.
Use this function to view a copy of the first word of the last 25 diagnostic status SRCs.
Typically, these are SRCs associated with problem analysis and main store dump.
1. Select Function 64 and press Enter to display 64**.
2. Enter a sub-function between 0x00 and 0x18 to view the SRCs in sequential order, 18 being the most
recent. Use sub-functions 0x19 and 0x1A to read extended SRC data associated with SRC 00x18. Press
Enter to display 64nn, where nn is the function that you selected.
Use this function to deactivate a remote service session. This function is available in manual operating
mode when activated by the OS.
Use this function to activate a remote service session. This function is available in manual operating
mode when activated by the operating system.
Use this function to initiate an I/O processor dump and a disk unit I/O reset/reload.
Use this function to initiate an I/O processor dump and a disk unit I/O reset/reload. This function is
available in manual operating mode when activated by the OS. This function is enabled only when the
I/O processor of a displayed SRC supports a reset/reload function.
Use this function to power off power domains to affect concurrent replacement of IOPs and IOAs.
Use this function to power off power domains to affect concurrent replacement of IOPs and IOAs. This
function is available in manual operating mode when activated by the OS.
Use this function to power on power domains to affect concurrent replacement of IOPs and IOAs.
Use this function to power on power domains to affect concurrent replacement of IOPs and IOAs. This
function is available in manual operating mode when activated by the OS.
Use this function to initiate IOP dumps. This function is available in manual operating mode when
activated by the OS.
Use this function to initiate IOP dumps. This function is available in manual operating mode when
activated by the OS.
Functions 71 to 99–reserved:
SRCs can display on the control panel, appear in a system console message, or appear in the product
activity log. For details, see “Product Activity Log” on page 92. For details on how SRC information
displays on the control panel, see “SRC formats.”
The system uses the following procedure to gather information about errors:
1. The system gathers information about an error as the system detects the error.
2. The Product Activity Log (PAL) records and stores the error information.
3. An SRC encodes information used to evaluate or identify a system-detected hardware or software
error, failure, or status. The failure information may include the failing condition or part (or unit) that
can be exchanged or replaced and its location.
4. The SRC links to the problem determination procedure when the element detecting the failure cannot
isolate the failing condition.
5. The SRC link completes the isolation process.
In summary, the SRC provides the first-failure-data-capture information. The customer or support
representative uses SRCs during problem determination, repair actions, and verification. The SRC
provides a link to the problem determination procedures (hardcopy or softcopy). Use the SRC and the
problem determination procedures to isolate the problem.
SRC formats
Describes the SRC record structure.
The control panel automatically displays the first word of the SRC and the extended word 1 data in
Function 11 when the panel shows an SRC (see “Word 1 - SRC general information” on page 150). You
can select other SRC words (Functions 12 through 19) by using the control panel Increment (↑),
Decrement (↓), and Enter buttons. Some portions of the SRC might not contain data. SRC records vary in
length (up to 36 bytes for words 1 through 9 and there may be up to 24 bytes of extended word 1 data)
and display as described in the following sections.
SRC records show with a -3 next to the function number in the Function/Data display on System Units
(for example, 11-3 xxxx xxxx).
The SRC record structure provides information about the machine at the time of the failure.
The control panel can display up to four words at a time. The first word of the SRC can consist of ASCII
or hexadecimal characters. The other eight words of the SRC consist of hexadecimal data. Function 11
displays the first word of the SRC, which can contain 8 to 32 characters (expanded word 1). In the
Product Activity Log (PAL) and other software displays, the SRC appears much like it does for earlier
releases, except for the possibility of word 1 containing up to 32 characters. Words display as a number
from 1 to 9 instead of Function 11 to 13, thus disassociating the word number from the function number.
Refer to “Product Activity Log” on page 92 for more information on the PAL and SAL. Refer to Table 23
on page 150 to see the SRC format.
1 – extended 11 9–32 text Additional text about the failure. This text
SRC varies by SRC.
information
5 12 25–32
6 13 1–8
7 13 9–16
8 13 17–24
9 13 25–32
Replacement 14–19 1–2 Hexidecimal FRU call-out data. Displays the replacement
priority data priority, part number, part type, and location
code.
Part number 14–19 3–9
Note: Select Function 20 to display machine type, model number, and processor feature code.
The URC is located in the second half of Word 1 of the SRC. This SRC (including the URC) is used
during problem analysis. You can identify the type of SRC record by the first digit in Word 1 using
Table 24 on page 151.
The type of SRC can be identified by the first digit in the function 11 data display as follows:
Word 2 is available for all SRC formats except power and control panel. The service processor provides
this information at the time the SRC is displayed to the panel.
The first hexadecimal digit that is displayed in Word 2 indicates whether the system started a main
storage dump and if it was successful. The indicator has the following meanings:
M Description
0 Dump was not initiated
Indicates how far the IPL continued before the system displayed the SRC
The second digit that is displayed in Word 2 indicates how far the IPL continued before the system
displayed the SRC. The indicator has the following meanings.
Hex Digit
IPL State Description
0 Service processor IPL from start-up code in progress
1 IPL from random access memory (RAM) is running
2 Service processor task initialized
3 LIC initialization completed
4 Operational load of LIC is complete
5 Bus manager initialized
6 Main Storage initialization is complete
7 Load Source DASD connection established
8 Dedicated Service Tool (DST) or limited paging available
9 Storage management directories verified
A Authority structures verified
B Indexes verified
C Database verified
D LIC hand-off to operating system
E IPL is complete to sign on display
F Power down attempted
The third hexadecimal digit that Word 2 displays indicates the IPL type (IPL mode and environment) of
the last IPL performed, or the IPL running at the time of the failure.
Power-on IPL
Includes the IPL that occurs automatically when someone turns on the main power switch or
starts power after a power failure. It also includes an IPL started by the timer and a remote IPL
started by a communication line.
Programmed IPL
An IPL that results from the PWRDWNSYS command with Restart=Yes*FULL specified.
Function 3 IPL
Uses the selected IPL options to load the system. It is started by selecting function 03 on the
control panel and pressing Enter.
Note: Selecting IPL type A or B (type C is reserved) with Function 02 causes an IPL from different areas
on the load source DASD. IPL type D is from the alternative load-source device, such as a tape or
optical device.
Note: This information does not list all SRCs. Start problem analysis with the Start of call procedure.
Table 24 on page 151 shows how SRCs are grouped. The SRC is a variable length structure.
The SRCs are displayed as a sequence of words that may be displayed by selecting different control panel
functions. Function 11 is shown automatically when an SRC is shown. You may select additional
functions through function 20 by using the Increment/Decrement (↑ ↓) switches and the Enter button.
There is also an option to include reference code details from the Work with Partition Status display. You
can also select SRC history option from the Display Partition Info menu.
The format of the SRC that you see depends on the system or server.
Notes:
1. Other formats exist; if necessary contact your next level of support.
2. For more information on formats 60–63, see “LIC-Detected Problem Reference Code Formats”
on page 156.
Table 26. SRC format examples
Panel
function,
digits x to IOP
SRC y (from Device detected
Word left to IOP SRC IOP SRC SRC a failure LIC SRC LIC SRC LIC SRC LIC SRC
Number right) format 13 format 17 format 27 format 29 Format 60 format 61 format 62 format 63
1 11, 1-8 TTTT TTTT tttt rrrr B0XX A6xx B6xx B6xx A600
RRRR RRRR RRRR RRRR RRRR RRrr or RRRR
B7xx Rrrr
2 12, 1-8 MIGV MIGV MIGV MIGV MIGV MIGV MIGV MIGV
EP13 EP17 EP27 EP29 EP60 EP61 EP62 EP63
3 12, 9-16 BBBB BBBB BBBB BBBB PPPP cccc cccc cccc cccc AAAA
Ccbb Ccbb Ccbb Ccbb 0000 BBBB
4 12, 17-24 aaaa aaaa aaaa aaaa aaaa aaaa SAPP BBBB pppp pppp CCCC
UUFF Ccbb pppp pppp DDDD
5 12, 25-32 TTTT TTTT tttt TTTT aaaa aaaa qqqq qqqq EEEE FFFF
LMMM LMMM lmmm FMMV qqqq qqqq
6 13, 1-8 uuuu tttt lmmm TTTT tttt lmmm tttt qqqq qqqq GGGG
uuuu LMMM mmmm qqqq qqqq HHHH
7 13, 9-16 uuuu ZZZZ rrrr ZZZZ zzzz rrrr ssss ssss 0000 0000 BBBB JJJJ KKKK
uuuu RRRR Ccbb
8 13, 17-24 uuuu ssss ssss ssss ssss 0sss ssss NNNN 0000 0000 TTTT TTTT
uuuu 0000 MMMM 0MMM
9 13, 25-32 uuuu uuuu uuuu uuuu 0000 0000 0000 0000 0000 0000 SSSS SSSS
uuuu uuuu uuuu uuuu
Logical Partition - Work with Partition Status System Reference Code Descriptions and Actions:
For information on logical partition reference codes, see reference codes for logical partitions.
For information on logical partition reference codes, see Reference codes for logical partitions.
Formats 60–63 in Table 1. SRC format examples represent the formats for Licensed Internal Code (LIC)
SRCs.
v Format 60 is used for LIC Attention SRCs.
v Format 61 is used when LIC detects a LIC programming problem.
v Format 62 is used when LIC detects an IOP Bus or IOP programming problem.
RRRR LIC unit reference code (URC).
Notes:
1. For information about Function 11 and 12, refer to “System Reference Code (SRC)
Information” on page 149.
2. Format 60 may contain data in a format other than that shown. Format 60 is an old VLIC
format, which some new LIC components use. It does not have the component reference code
and program reference code that format 61 and 62 have (61 and 62 were specifically defined
for the new LIC). Format 60 is mostly component-specific with no key information to indicate
format (the developer has to interpret it).
3. Refer to Licensed internal code (LIC) isolation procedures and perform the problem isolation
procedure used by the reference code to further define any significant data.
The four-digit unit reference codes follow. These codes are grouped by their first 2 or 4 digits. The groups
are:
Group Number
Description
00-01 Machine Check Handler
02 Storage Mgmt
To determine the meaning and service action for the SRC, see Using system reference codes.
A main storage dump is taken for most of the LIC URCs unless otherwise indicated in the description of
the URC.
For a list of general status SRCs, see List of system reference codes.
For information on performing an IPL using the Hardware Management Console (HMC), see Powering
on and off the system using HMC.
For information on performing an IPL using the Advanced System Management Interface (ASMI), see
Using the system power control.
Note: Systems managed by the Hardware Management Console (HMC) should use the HMC to perform
control panel functions. For information on performing control panel functions using the HMC, see
Control panel functions.
v Use function 01 to display the current IPL option, including IPL speed. This is the option and speed
that the system will use at the next IPL. Refer to Function 01: Display selected IPL type, system
operating mode, and IPL speed for more information about function 01.
v Refer to the information in Table 19 on page 143 for speed override definitions.
v Use the HDWDIAG (hardware diagnostics) parameter of the CHGIPLA command to permanently change the
IPL speed. The values are: The default shipped value *MIN (minimal) for fast diagnostics and *ALL for
all (full) diagnostics.
Service functions 159
IPL speed recommendations
v Use CHGIPLA *MIN, or Function 02 F or V=F for most IPLs (to perform a fast IPL that uses minimum
diagnostics).
v Use CHGIPLA *ALL, or Function 02 S or V=S, if you change hardware or suspect an intermittent hardware
failure (to perform a slow IPL that uses all diagnostics).
v Use CHGIPLA *ALL, or Function 02 S or V=S during the first Install IPL. You can set this at the panel
with Function 02; it affects only the one IPL because the next IPL will again pick up the value set with
CHGIPLA.
You can perform this IPL from either the control panel or the Hardware Management
Console (HMC). For information on the control panel, see Control panel functions. For
information on using the HMC, see Powering on and off the system using HMC.
F03 Attention: No system shutdown is performed before the IPL. The use of this function can
cause loss of data.
Control panel Function 03 starts a Load IPL. This differs from a POR IPL because no power
off and power on sequence is done. This means a system shutdown is not performed and
not all hardware diagnostics are performed during the IPL. Input-output processors (IOP)
are reset using a software POR equivalent.
You can perform this IPL from either the control panel or the Hardware Management
Console (HMC). For information on the control panel, see Control panel functions. For
information on using the HMC, see Powering on and off the system using HMC.
Programmed IPL This IPL is started by the operating system. A PWRDWNSYS command with RESTART
without parameters (*YES) will initiate this IPL.
Remote power on An unattended IPL is started from a remote location. Normal mode must be selected, the
system power must be turned off, and the user must set specific indicators (see the system
operation information).
Automatic restart An unattended IPL is started automatically after a power failure. Normal mode must be
selected and the user must set specific indicators (see the system operation information).
Power on by This IPL is started by an internal clock. Normal mode must be selected and the user must
date/time set specific indicators (see the system operation information).
Results
For information on IPL status SRCs, see “IPL status SRCs” on page 159.
For information on IPL for i5/OS logical partitions, see Restarting and shutting down i5/OS in a logical
partition.
Functions performed
The service processor runs on its own power boundary and continually monitors hardware attributes and
the environmental conditions within the server. The service processor is controlled by firmware and does
not require an operating system to be running to perform its tasks.
When external power is applied to the system, the service processor is activated. The service processor
does the following:
v Runs diagnostic routines to verify its hardware and firmware.
v Gathers vital product data (VPD) from the electronic components in the server.
When the service processor has successfully completed these tasks, it is in the standby state. The control
panel displays 01. You can now power up the server.
When you power on the server using the power button on the control panel, the Advanced System
Management Interface (ASMI), or the Hardware Management Console (HMC), the service processor turns
on the system power. The service processor does the following:
v Runs diagnostic routines to verify the operation of the system processor and system memory.
v Verifies that it can communicate with the environmental sensors and monitors in the system.
When the service processor completes these diagnostics, it turns control over to a system processor.
Server firmware starts executing on the system processor.
The service processor ends an IPL when a condition is detected that prevents the base machine from
functioning. If an IPL stops, an SRC appears on the control panel, and the system attention light goes on.
The SRC indicates the failing condition.
Functions performed
The following list is a high-level description of the functions that are performed by LIC during an initial
program load (IPL):
1. LIC sets the internal processing unit registers and arrays.
2. When the initialization is complete, LIC signals the service processor of the event.
3. LIC enters the disabled state (task dispatcher is disabled). After the service processor starts the
processing unit, the earlier constructed queue is made ready. The LIC then does its normal work-time
functions.
See “IPL status SRCs” on page 159 for information that is displayed on the control panel during an IPL.
Abnormal ending
LIC ends an IPL when a condition is detected that prevents the machine from doing work. The service
processor sends the correct SRC to the control panel.
At any point in the LIC initialization phase, errors that end machine processing during an IPL can occur.
If this occurs, indicators are set to the data function. The machine check error log buffer, LIC log, or the
Product Activity Log contain information about the condition that caused the ending.
Initialization output
The output that is created when the LIC is initialized consists of the following:
v Machine status information saved in the machine initialization status record (MISR).
v Status codes for an initial program load displayed on the control panel for long-running IPL functions.
v Product Activity Log and LIC log information that service personnel need to service the machine.
Log entries:
Logging is a function of Licensed Internal Code and starts during Licensed Internal Code initialization.
Logging is a function of Licensed Internal Code and starts during Licensed Internal Code initialization.
Licensed Internal Code parts (see “Licensed Internal Code” on page 164) send log records to the product
activity log. Licensed Internal Code input/output managers do much of the error machine check
controlling.
The IOPs also have the ability to send data into the product activity log. Log records from the IOPs are
processed by the Reliability Availability Serviceability (RAS) Focal Point Common Class I/O Manager
Task in Licensed Internal Code. The following are the types of log entries from the IOP:
This is a bus-level record that is used when the I/O processor has detected a critical failure. The
asynchronous log report is used when the IOP cannot communicate with Licensed Internal Code or the
service processor.
This is a log record that is reported to the system from the IOP after the RAS connections have been set
up.
This is an information-only record that is reported to the system after the RAS connections have been set
up. The information records (statistics) are logged as product activity log information.
The following list describes the attributes of the product activity log:
v Permanent errors that do not stop the system
v Machine check data when available on the next IPL (if power was not switched off before doing the
next IPL)
v Any temporary errors necessary for problem analysis
v Data in multiple formats
v RAS error information and bus level asynchronous log report
v Device driver reported records
v Some dumps and trace data
v Volume information (statistics) data records
A formatted printout of the product activity log records is available by using the Product activity log
option from the Start a Service Tool display under Dedicated Service Tools (DST).
Status SRCs
Status system reference codes (SRCs) indicate the current state of the system for informational purposes.
Status SRCs appear on the system or partition control panel during the following processes:
v System IPL
v DST functions (local or remote)
Service functions 163
v Dump functions
v System power-down
The term PTF can refer to a Licensed Internal Code, an operating system, or other IBM licensed program
fix. Because some PTFs repair problems that might appear to be hardware failures, your actions with
PTFs are important for both the customer and for IBM. It is often difficult to tell the difference between a
hardware failure and a code problem that is fixed by a PTF.
For information on server firmware, Hardware Management Console (HMC), and operating system fixes,
see Getting fixes.
The customer is responsible for maintaining fixes to Licensed Internal Code and the operating system.
To display the Licensed Internal Code fixes that are on your system, see “Displaying Licensed Internal
Code fixes” on page 165. To display the operating system fixes and cumulative PTF packages that are on
your system, see “Displaying i5/OS PTFs” on page 222.
Some PTFs fix problems that might appear to be hardware failures. Always ensure that the recommended
PTFs are applied before you exchange hardware.
Cumulative PTF packages contain fixes for a given release of the i5/OS operating system and associated
licensed programs. You should install the entire cumulative PTF package after you first load or reload the
operating system and periodically throughout the release as defined in your maintenance strategy.
PSP listings
Obtain information about preventive service planning (PSP) by contacting the customer’s software service
provider.
Before generating a LIC APAR, ask your next level of support to screen the APAR and enter the
symptoms of the problem into the service support system.
Licensed programs
Licensed programs are represented by names in the form xxxxyyy, where xxxx is the base operating
system software and yyy is a unique, 3-character alphanumeric identifier.
To determine the operating system fixes that are on the system, see “Displaying i5/OS PTFs” on page
222.
Use the Start Service Tools (SST) to display Licensed Internal Code (server firmware) fixes. If it is not
available, use the Dedicated Service Tools.
Note: You can also use the HMC if your system is managed by an HMC.
Results
Note: During the normal shut down of the service partition, i5/OS verifies that the firmware level on the
service processor is at the same level as the i5/OS firmware load source (PTF level). If they are
different, then the firmware is updated. This process is known as LS Flash Synching (Firmware
Load Source to Fsp Flash synchronization).
Note: To display PTF requirements, supersede information, and dependent fix information, use the
function keys on the Display Fix Information display.
For more information on fixes, see “Fixes and cumulative PTF packages” on page 164.
For information on fixes for the Hardware Management Console (HMC), see HMC fixes
Installing the Licensed Internal Code erases all information on the load-source disk unit, makes the data
on the remaining disk units (including customer data) inaccessible, and copies the Licensed Internal Code
from removable media to the load-source disk.
The system disk units might not be accessible because data is arranged over multiple drives on the
system. After you complete the install procedure, consider the customer data destroyed. The customer
can install the operating system and the system data from removable media after you complete the install
procedure. To exchange the Licensed Internal Code without destroying customer data, see “Utility to
restore Licensed Internal Code” on page 167.
Use this utility to install Licensed Internal Code when one of the following occurs:
v The load-source disk has been replaced.
v The system does not contain customer data and Licensed Internal Code.
v The instructions for a new Licensed Internal Code release specify that you cannot use the restore
Licensed Internal Code utility.
The system Licensed Internal Code might be on the customer’s system save media, the IBM distribution
IBM Software Manufacture and Delivery (ISMD) media, or the Licensed Internal Code save media.
Notes:
1. If there is a set of distribution or save media, start the installation with the first tape or optical
device.
2. For instructions on loading the optical device, see the System Startup and Problem Handling
information.
3. If the console is not powered on, SRC A600 500x is displayed. Power on the display, then
select Function 21 on the control panel to make DST available. For details, see Function 21:
Service tool initiation.
4. The Licensed Internal Code level (with the PTFs applied) is returned to the level supported at
the time the media was saved.
5. If you use Volume 1 of the IBM distribution media, you do not apply any PTFs. The operating
system reflects that no Licensed Internal Code PTFs have been applied. For more information
on PTF levels, see “Displaying Licensed Internal Code fixes” on page 165.
Installing LIC
1. Perform steps 1 through 9 of the alternate IPL to DST procedure. For details, see “Performing an
alternate IPL to DST (type D IPL)” on page 6.
2. Select the Install Licensed Internal Code option on the Install Licensed Internal Code display.
Attention: The Install Licensed Internal Code and Initialize System option destroys all data on the
system, including customer data. Select the Install Licensed Internal Code and Initialize System option
from the Install Licensed Internal Code display.
3. When the Install Licensed Internal Code - Confirmation display appears, press F10 to continue.
Note: A series of displays appears on the console throughout the process to show the installation
status. User intervention might be required.
4. The system automatically performs a disk IPL and the Install the Operating System display appears.
To install the operating system, select the Continue installing the operating system option. See the system
operation information for details on how to install the operating system.
Note: When the procedure is complete, remove the media from the removable media unit.
This ends the procedure.
Restoring Licensed Internal Code completely exchanges all Licensed Internal Code with a new level of
code. The Restore Licensed Internal Code option copies all system Licensed Internal Code from media
and puts it on a disk.
The system Licensed Internal Code might be on the customer’s system save media, the IBM distribution
(ISMD) media, or the Licensed Internal Code save media.
Notes:
1. If there is a set of distribution or save media, start the installation with the first tape or optical
device.
2. For instructions on loading the optical device, see the System Startup and Problem Handling
information.
3. The Licensed Internal Code level (with the PTFs applied) is returned to the level supported at
the time the media was saved.
4. If you use Volume 1 of the IBM distribution media, you do not apply any PTFs. The operating
system reflects that no Licensed Internal Code PTFs have been applied. For more information
on PTF levels, see “Displaying Licensed Internal Code fixes” on page 165.
Restoring LIC
1. Perform steps 1 through 8 of the alternate IPL to DST procedure (see “Performing an alternate IPL to
DST (type D IPL)” on page 6 for instructions).
Note: Displays appear on the console throughout the process to show the restore status. User
intervention might be required.
4. The system automatically performs a disk IPL and the IPL or Install the System display appears.
To install the operating system, select the Install the operating system option. See the system
operation information for details on how to install the operating system.
Note: When the procedure is complete, remove the media from the alternate IPL unit.
This ends the procedure.
Report problems in the system program or code to IBM. When you find a problem with the Licensed
Internal Code, you can submit a LIC APAR. Program problems are tracked using an authorized program
analysis report (APAR). An APAR is a request for the correction of a program defect. Because operating
system and Licensed Internal Code fixes might solve program and LIC problems, perform the procedures
in “i5/OS or LIC APAR information” on page 222 before submitting the report.
Power supply
Provides power supply description and link to other information.
Power for the iSeries systems is supplied by one or more power supplies. Each power supply provides all
the voltages that are needed in the system. Two or more installed power supplies provide redundancy
and allows power supply replacement with the system powered on. For information on the power
distribution, see Dual power installation configurations.
The battery power unit is available on the 5074 iSeries I/O expansion tower. It provides temporary
auxiliary power to the tower in the event of an ac power loss.
The SPCN is a concept of power distribution and control for the iSeries system. Problems detected by
SPCN are reported to the operating system and logged. You can work with the SPCN information by
Most power components in a system contain an SPCN node. The SPCN node contains a
microprocessor-based controller that controls and monitors the power in that node. The SPCN node
functions in the SPCN network and connects the points necessary for controlling power, sending
commands, and reporting status.
There is one primary node in a system. All other nodes are secondary nodes.
Primary node
The primary node is located in the system unit and is the controlling node in the network. This node is
located on a separate card that is installed in the rear of the system or is part of the backplane in the PCI
cage. The primary node is programmed to issue network commands and poll for status from secondary
SPCN nodes in the network.
The primary node monitors the status of the power supplies, regulators, and backup power (BBU). The
primary node is powered on as long as there is ac power to the frame. It communicates with the
operating system by exchanging commands and network status.
The primary node collects command responses and error status from the secondary nodes and formats
them for return to the operating system.
Secondary node
Each secondary node is programmed to collect unit power status and respond to commands from the
primary node. The secondary node also controls the unit’s display panel. The following information is
displayed on the unit display panel:
v Normal - Type, model, serial number of the unit and type, model, serial number of the power
controlling system
v Error - Type, model, serial number of the unit and power reference code
In frames with a PCI system bus, the secondary node is located on a card in the PCI cage, or on the
backplane.
SPCN addressing
Each unit in the SPCN network is identified and located by a four-character frame address and a
two-character unit address. A frame address is assigned by the primary node or by the operating system
and will usually be 3Cxx, where xx is any hex digit. A unit address is fixed and is either 00 or 01.
Selection
_
Figure 79. Example Hardware Service Manager display for Model 5xx (in the full or limited environment)
Note: For more information on Hardware Service Manager, see “Hardware Service Manager” on page 43.
When you select the System power control network (SPCN) option on the Hardware Service Manager
display, the first System Power Control Network display shows advisory information. It informs you that
there might be a delay before the System Power Control Network main menu display appears. You must
press Enter to continue.
F3=Exit F12=Cancel
The second System Power Control Network display allows you to choose the frame or unit with which
you want to work.
Serial
Opt Frame Unit Type Number Fault
_ 01 0 .... 00-00000 No
_ 01 1 .... 00-00000 No
_ 02 0 5070 10-55555 No
_ 02 1 5070 10-55555 No
_ 03 0 .... 00-00000 No
_ 03 1 .... 00-00000 No
_ 04 0 .... 00-00000 No
_ 04 1 .... 00-00000 No
_ 05 0 .... 00-00000 No
More...
Allows you to work with Opt, Frame, Unit, Type, Serial number, and Fault fields.
Opt
This field allows you to choose to work with the frame or unit components.
The following options are available for the Opt field: 5 (Display detail). For details on this option, see
Display Detail option.
Frame
This field refers to one of the system frames. The value is the SPCN address.
Unit
The unit value is a 01, 0C, or 00; a unit value of zero indicates a system frame node.
Type
Serial number
Fault
This field indicates whether a power fault currently exists on that frame or unit. You can find information
on the fault in either a message to the system operator or a power reference code on the unit.
You can select the Display detail on the System Power Control Network (SPCN) display to show detailed
SPCN information about a frame or unit.
The display detail for frame option shows details for a frame, such as alert status, serial number, and so
on.
If you select the Display detail next to the entry for a frame, the Display detail for frame display
appears.
F3=Exit F12=Cancel
The display detail for unit option shows details for a unit, such as alert status, serial number, and so on.
If you select option 5 (Display detail) next to the entry for a unit, the following display appears with
detailed information about the unit:
Note: The Display status of regulators function key (F6) on the Display Detail for Unit display is not
recommended for service representative use.
HSL/RIO resources are normally configured in loops with the system unit having an HSL/RIO controller
resource that handles routing of the data between the system processor and the system I/O busses.
System I/O busses connect to the loop with HSL I/O adapter or RIO adapter resources. When you view
the logical resources of a High Speed Link loop using Hardware Service Manager, you will see:
v HSL controller resource(s) (called Local High Speed Link Network Interface Controllers (Local HSL NICs)
in V5R1).
v HSL controller resource(s) of other processing units in the RIO loop, called Remote High Speed Link
Network Interface Controllers (Remote HSL NICs).
v HSL loop resource(s) under the controller listed above the loop.
v HSL I/O adapter resource(s) under the loop listed above the adapters.
v The System Bus Adapter Resource(s) under the HSL I/O adapter resource(s) option. From this level and
below, I/O resources appear the same way as they do in the System bus resources option from Display
Logical Resources in the Hardware Service Manager menu.
Loops start and end on the same port pair of an HSL/RIO controller, for example, the A0 and A1 ports.
When you view an HSL/RIO controller or adapter resource in HSM, you can select Display detail option
to view the status and information about the links on that resource.
There are two ports on each HSL/RIO resource. The Leading link usually refers to the connection between
the resource’s 0 port to the next HSL/RIO resource on the loop. The Trailing link usually refers to the
connection between the resource’s 1 port to the next HSL/RIO resource on the loop.
In some cases a link is an internal connection in a system unit or expansion tower. In that case the link
will be labeled as ″internal″ and there will not be port label information.
When port pairs are on a system unit they are labeled on the frame as A0 and A1; B0 and B1; and so on,
or as –Tx. When port pairs are on an expansion tower they are labeled on the frame as 00 and 01, or as
Tx.
Multi-adapter bridge
A multi-adapter bridge is a resource which provides the connection between PCI I/O processors and a
system PCI bus under an HSL I/O or RIO adapter.
A multi-adapter bridge is a resource which provides the connection between PCI I/O processors and a
system PCI bus under an HSL I/O or RIO adapter. The bridge controls a set of card positions that are
labeled “PCI Bridge Set” on the frames of system units and expansion towers. There can be more than
one multi-adapter bridge resource connected to a system bus. Each bridge resource operates
independently from any other bridge on the system bus and the bridge controls only the card positions in
its own PCI bridge set.
Resource names
Covers how to display and change resource names.
Communications lines, I/O processors, and devices are system resources. All system resources are
identified by a resource name. To list the system resources, or display and change resource names:
v See “Hardware Service Manager” on page 43.
v Enter the resources command:
– WRKHDWRSC
During an IPL, all powered-on resources that do not have a name are assigned a name. The Licensed
Internal Code assigns the name according to the order in which the resource reports to the system. The
resource name is used for identification (by the Licensed Internal Code) during the next IPL, on displays,
in printouts, and during system configuration.
Note: Many system resources are identified by both logical and packaging resource names. The logical
and packaging hardware resources have different resource names.
Use the following tables to identify the logical and packaging system resources. For more information on
system resources, see “Hardware Service Manager” on page 43 and “Product Activity Log” on page 92.
v * A system resource (SYS) is a collection of all packaging resources that are contained within, or
attached to the system unit.
The following restrictions apply for the hardware that is associated with resources. For more information,
see “Hardware Service Manager” on page 43.
v If you move a workstation I/O processor (IOP), you must move the attachment cable that is connected
to the IOP to the card position along with the IOP.
Note: The cable must be moved because the configuration for the IOP is tied to the resource name of
the IOP, which follows the serial number of the card.
v If you move a communications I/O adapter (IOA), you must move the cables that are connected to the
IOA along with the IOA.
Note: The cable must be moved because the configuration for the lines is tied to the resource name of
the IOA, which is based on the serial number of the IOA card.
2 to 3 2 XD XD-A XD-A
3 to 2 3 RD RD-A RD-A
4 to 5, 8 4 RTS A to CTS A, CD A
5 to 4 5 CTS A to RTS A
8 to 4 8 CD A to RTS A
9 to 7 9 CID 0 to SGND
18 to 37 18 TD A to RD A
20 to 34 20 RD B to TD B
22 to 21 22 CTS B to RTS B
25 to 21 25 CD B to RTS B
28 to 47 28 RSGND to TSGND
34 to 20 34 TD B to RD B
35 to 39 35 DTR B to DSR B
36 to 38 36 DTR A to DSR A
37 to 18 37 RD A to TD A
38 to 36 38 DSR A to DTR A
39 to 35 39 DSR B to DTR B
43 to 7 43 CID 1 to SGND
47 to 28 47 TSGND to RSGND
49 to 7 49 CID 2 to SGND
50 to 7 50 CI 3 to SGND
3 to 2 3 RD P1 PWI P1 RD-A P1
10 to 9 10 RD P2 PWI P2 RD-A P2
2 to 3 2 FLASHER TRIG
4 to 38 4 OPTO OUT/DEGLITCH IN
5 to 6, 18 5 FLASHER OUT
6 to 5, 18 6 OPTO OUT/DEGLITCH IN
7 to 8, 36 7 VCC OPTO
8 to 7, 36 8 Not Used
11 to 15 11 RES
15 to 11 15 Not Used
17 17 SGND
18 to 5, 6 18 DEGLITCH DISCH
19 to 20 19 Not Used
20 to 19 20 Not Used
21 to 39 21 DEGLITCH BASE
28 to 32 28 Not Used
29 to 16, 30 29 RES
31 to 43, 45 31 RES
32 to 28 32 Not Used
34 34 SGND
36 to 7, 8 36 Not Used
38 to 4 38 JUMPER TO DEGLITCH IN
39 to 21 39 DEGLITCH RST
40 40 CID 2
41 41 CID 1
42 42 CID 0
47 47 CID 3
48 48 CID 2
49 49 CID 1
50 50 CID 0
V.36/EIA 449 high speed communications adapter cable wrap connector wiring
Table 49. V.36/EIA 449 high speed communications adapter cable wrap connector wiring
Signal designation Wrap connector pin to pin
Transmit data A to receive data A 4 to 6
Transmit data B to receive data B 22 to 24
DTR A to DSR A 12 to 11
DTR B to DSR B 30 to 29
RTS A to CTS A and RLSD A 7 to 9,13
RTS B to CTS B and RLSD B 25 to 27,31
TSET A (DTE) to TSET A (DCE) RSET A 17 to 5,8
TSET B (DTE) to TSET B (DCE) RSET B 35 to 23,26
Remote loopback to ring indicate 14 to 15
When terminated by a 100 ohm resistive When terminated by a 100 ohm resistive
load, the differential voltage (B-A) is the load, the differential voltage (A-B) is the
larger of 2.0 volts or 50% of the open larger of 2.0 volts or 50% of the open
circuit voltage. The open circuit voltage is circuit voltage. The open circuit voltage is
between 2.0 and 6.0 volts. between 2.0 and 6.0 volts.
Note: See X.21 cable diagram to find out which pin numbers are A and B.
ISDN Logic 0 Logic 1
The differential voltage (A-B) is less than The differential voltage (A-B) is 0.0 volts
+.75 volts and more than -.75 volts (nominal).
(nominal).
A main storage dump (MSD) is a process of collecting data from the system’s main storage. For more
information on main storage dumps, including POWER5™ platform system dumps, see Performing a
platform or main storage dump.
To check whether the system performed a main storage dump (MSD) or to verify that a current MSD is
on the system, see “Error recovery for dumps” on page 207.
When the service processor begins the main storage dump process, the control panel displays D1xx 3xxx
reference codes. When the initial stages of the MSD are complete, the service processor performs one of
the following:
v Displays a reference code on the control panel (if it cannot continue).
v Begins an MSD IPL and displays C6xx 44xx SRCs along with the IPL SRCs on the control panel.
Note: For more information on C6xx 44xx and D1xx 3xxx SRCs, see “General status SRCs” on page 159.
When the system completes the dump, some of the data for the current MSD is copied to the load-source
disk, and the other data is held temporarily in main storage. The Main Storage Dump Manager (MSDM)
function then starts.
Note: If all disk units do not report in (after about 40 minutes), the Disk Configuration Error Report screen
will appear when the user specifies an action that requires access to auxiliary storage. Note the
error that appears on the display. This can help during problem analysis. Press the F3 (Exit) key to
continue to view the current MSD or copy it to removable media.
Warning: The Main Storage Dump (MSD) must be copied for service.
Failure to copy the Main Storage Dump will limit
the ability to diagnose the failure.
Press Enter to copy the MSD for service or view the MSD.
F3=Exit F12=Cancel
Figure 80. Example MSDM SRC display that appears on the console when an MSD occurs
Attention: Unless the current MSD is copied to removable media or the MSD library, the dump data in
main storage will be lost when the system performs an IPL at the end of the dump process. To copy the
MSD, press Enter. When the Main Storage Dump Manager display appears, refer to “Copying a main
storage dump.”
If you select F3/F12 to exit Main Storage Dump Manager without copying the MSD, the following
message appears:
Main storage dump has not been copied for service.
Selecting F3/F12 a second time ends the main storage dump manager function, and the system performs
an IPL again.
You can copy main storage dump data in the following ways:
v From the current main storage dump to removable media
v From the current main storage dump to the MSD library
v From the MSD library to removable media
v From removable media to the MSD library
If you select the Work with current main storage dump (MSD) option from the Main Storage Dump
Manager display, you can work with the newest MSD taken by the system. The current MSD is stored on
the load-source disk. It gets replaced by the next main storage dump or is lost during the next IPL.
The Work with Current Main Storage Dump display allows you to select the following options:
1. Display/Print
2. Copy to media
3. Copy to ASP
Selection
_
Use this option to display the current MSD. For more information on displaying the current MSD, see
“Main storage dump manager” on page 31.
If you select the Copy to media option, you must load the removable media. A series of displays appears
indicating the progress. When the copy function completes, a success or a failure message appears. When
you exit the Main Storage Dump Manager, the system IPLs again and can be returned to the customer.
If you select the Copy to ASP option, you must provide a description of the dump. When you press
Enter, a series of displays appears indicating the progress. When the copy function completes, a success
or a failure message appears. When you exit the Main Storage Dump Manager, the system IPLs again
and can be returned to the customer.
The following message indicates that the system encountered problems while trying to copy the dump to
MSD library:
Cannot IPL to Storage Management Recovery. Copy dump to media.
If this message appears, you must copy the MSD to removable media.
For descriptions of removable media and the MSD library storage, see “Working with Storage Dumps” on
page 203.
Follow the on-line instructions on the displays to work with an MSD copy.
During a main storage dump, the control panel shows MSD status SRCs (D1xx 3xxx and C6xx 44xx). For
more information on these SRCs, see “General status SRCs” on page 159.
The main storage dump ends successfully if the Main Storage Dump Occurred display appears. The main
storage dump ends unsuccessfully if a terminating SRC appears at the control panel.
For information on using the Hardware Management Console (HMC) to collect reference codes, see
Collecting reference codes and system information.
A lit System Attention light indicates dump termination. The terminating SRC displays after the main
storage dump completes.
v In the case of an automatic dump (system stopping, including a main storage dump), the normal
terminating SRC is the one associated with the system error that started the dump.
v In the case of a manual dump (Function 22), the normal terminating SRC is a service processor
completion code (A1xx 300x or B1xx xxxx):
or 11 B2xx5117
Note: x can be any hexadecimal character (0 through 9, A through F).
Perform the following steps to determine whether a main storage dump data was written to disk:
1. If the Main Storage Dump Occurred display appears on the system console, then the first part of the
main storage dump data has been written to disk. Go to “Copying a main storage dump” on page 204
to save the main storage dump.
2. If the main storage dump terminated with an SRC displayed on the control panel, and the Main
Storage Dump Occurred display does not appear on the system console do the following:
a. Check to see if function 34 is available at the control panel.
b. If function 34 is available, select function 34 at the control panel and press Enter at the control
panel to attempt a retry of the dump IPL.
If the Main Storage Dump Occurred display appears on the system console, function 34 was
successful and the main storage dump data is not lost. Go to “Copying a main storage dump” on
page 204 to save the main storage dump.
The main storage dump failure needs to be reported with all of the data that can be collected. Collect and
record or save the following data:
1. Save the SRC data words:
a. Set the control panel system operating mode to Manual.
b. Record all of the SRC data words available from function 11 through function 20
2. Save the service processor dump.
a. Select control panel function 43 and press Enter. See “Performing a service processor dump.”
Note: You can initiate a service processor dump on a POWER5 system only by using function 43.
3. Save the main storage dump residue.
a. Use SST to enter the Main Storage Dump Manager.
b. Use the Main Storage Dump Manager to save the current main storage dump. See “Copying a
main storage dump” on page 204.
Note: If you are using a volume with a different volume name, use that name in place of SID87.
Press the Enter key.
2. From the Start a Service Tool display, select the Display/Alter/Dump option.
You can perform I/O processor storage dumps by using the I/O debug option on the Logical Hardware
Resources display (under Hardware Service Manager). Use this utility under the direction of your next
level of support. For more information on the Hardware Service Manager function, see “Hardware
Service Manager” on page 43.
The Logical Hardware Resources display (under Hardware Service Manager) lists the logical resources
that are attached to the system bus. Select the I/O debug option to access the IOP dump function. The IOP
dump function allows you to collect, display, print, and save data from the I/O processor. The dump is
written to a temporary disk storage area. When you exit the Hardware Service Manager function, the
dump is lost.
IOP storage dumps occur at the time the system detects the problem. If the IOP failure does not cause a
system failure, the dump information is placed in the product activity log.
1. Search the product activity log for a class of entries that are labeled IOP dump. For more information
on the product activity log, see “Product Activity Log” on page 92.
2. Display the detailed entry.
Note: Multiple entries (with the same log ID) are associated with this dump. Press Enter to display
each entry. Verify the Class field for the IOP dump.
3. To view the entire dump, select the function to print the IOP dump.
The DST tools and functions vary depending on the paging environment and operating system that is
used. For details, see “System paging environments” on page 1.
The full paging environment is used during normal system operation. The following options appear on
the Use Dedicated Service Tools (DST) display for the i5/OS operating system:
v Perform an IPL
v Install the operating system
v Work with Licensed Internal Code
v Work with disk units
v Work with DST environment
v Select DST console mode
v Start a service tool
v Perform automatic installation of the operating system
For details on each DST option, see “DST options” on page 8. For general information on DST, see
“Dedicated Service Tools (DST)” on page 1.
The DST tools and functions vary depending on the paging environment and the operating system used.
For details, see “System paging environments” on page 1.
The limited paging environment is available when you perform an IPL to DST. The following options
appear on the Use Dedicated Service Tools (DST) display for the i5/OS operating system:
v Install the operating system
v Perform an IPL
v Perform automatic installation of the operating system
v Select DST console mode
v Start a service tool
v Work with disk units
v Work with DST environment
v Work with Licensed Internal Code
v Work with remote service support
v Work with system partitions
v Work with save storage and restore storage
v Work with system capacity
v Work with system security
For details on each DST option, see “DST options” on page 8. For general information on DST, see
“Dedicated Service Tools (DST)” on page 1.
The system service tools (SST) run one or more Licensed Internal Code (LIC) or hardware service
functions under the control of the operating system. To determine whether the i5/OS operating system is
running on your system, see “Determining the dominant operating system” on page 123. SST allows you
to perform service functions concurrently with the customer’s application programs. The printer that is
used for output must be an SCS-type data stream printer that is attached to the same workstation
input-output processor (IOP) or storage media unit.
You can access SST only when the system is in the full-paging environment (see “System paging
environments” on page 1). The full paging environment is used during normal system operation. All disk
units, the Licensed Internal Code, and the operating system are available.
What to do next
For more information on SST options, see “SST options.” This ends the procedure.
What to do next
For more information on SST options, see “SST options.” This ends the procedure.
SST options
SST options topic index.
When you access SST (see “Accessing system service tools” on page 211), the following options are
available:
Select this option from the System Service Tools display. It displays all of the service tools that are available
under SST. This option is a subset of the functions available under Dedicated Service Tools (DST). For
information on the Start a Service Tool option under DST, see “Dedicated Service Tools (DST)” on page 1.
The following options are available under SST:
v Product activity log - For details, see “Product Activity Log” on page 92.
v Trace Licensed Internal Code - For details, see “Licensed Internal Code (LIC) trace” on page 31.
v Work with communications trace - For details, see “Work with communications trace” on page 33.
v Display/Alter/Dump - For details, see “Display/Alter/Dump” on page 29.
v Licensed Internal Code log - For details, see “Licensed Internal Code (LIC) log” on page 30.
v Main storage dump manager - For details, see “Main storage dump manager” on page 31.
v Hardware service manager - For details, see “Hardware Service Manager” on page 43.
Select this option from the System Service Tools display. It lists active service tools and their status. You can
start service tools and leave them active while you start another service tool. Use this function to work
with a service tool you left active or to end an active service tool. The status of a service tool shows
whether the service tool is active or ending. For more information, see “Work with active service tools”
on page 26.
It displays tools that can be run for disk units. You can do the following:
v Display disk configuration
v Display checksum configuration
v Calculate checksum configuration
v Work with auxiliary storage pools (ASP) threshold
v Add units to ASPs
v Work with device parity protection
v Work with disk unit recovery
v Work with disk unit information
v Calculate mirroring capacity
This option is a subset of the functions available from dedicated service tools (DST). The complete
function is not available from SST in full paging environment. For more information, see “Work with disk
units” on page 11.
It allows you to read data from a diskette that contains cyclic redundancy check (CRC) errors. CRC errors
occur when the system finds data on a diskette that is not readable during a read operation. Normally,
when the system finds a CRC error, you cannot read the diskette past the point of the failing sector. By
using this option, you can read diskettes that contain sectors with CRC errors.
The iSeries system can use diskettes for saving and restoring system objects. One or more objects can be
stored on a diskette. Whenever the system finds a diskette that contains a bad sector during a read
operation, the operation ends. A bad diskette sector, which causes a CRC error, can result from failure in
the diskette or from wrong handling. The Work with diskette data recovery option allows you to read data
from a diskette, correct any failing sectors present on the diskette, then write the new data to a new
diskette.
Options
v Alter diskette data
This option allows you to change the data in any sector on a diskette. For more information, see “Alter
diskette data” on page 214.
v Read data from diskette
This option reads the contents of a diskette while ignoring diskette sectors with read data CRC errors.
For more information, see “Read data from diskette” on page 215.
v Write data to diskette
Processing restrictions:
This option cannot duplicate diskettes containing data sets that have data set directories in the data area,
and might not read VTOC or data set identification sectors into a space object.
The Alter Diskette Data display allows you to view and alter diskette data.
More...
F3=Exit F5=Refresh F12=Cancel F14=Previous sector
F15=Next sector
1. Select Alter diskette data on the Work with Diskette Data Recovery display. The alter diskette data
window appears.
2. Perform the following actions:
v Press F15 to advance one sector at a time.
v Press F14 to return to the previous sector.
v Type over the Starting sector address to gain access to any sector on the diskette.
This option reads cylinder 0, sector by sector, and cylinders 1 through 74 with one request.
Select this option first. This option reads cylinder 0, sector by sector, and cylinders 1 through 74 with one
request. When the read operation finds a CRC or a deleted or sequentially relocated sector, it builds an
error summary record and continues reading until it reaches an end-of-volume.
This option writes the VTOC and the data sectors from the image that is contained in the system space
object.
This option writes the VTOC and the data sectors from the image that is contained in the system space
object. The diskette is written in either ASCII or EBCDIC, as determined by the read option. If the
operation receives a bad feedback response code from the REQIO instruction, the write data to diskette
operation ends with an error message. If the write operation is successful, the output diskette is given the
same volume serial number and content as the original diskette.
Select Display diskette data on the Work with Diskette Data Recovery display. The display Diskette Data
display appears.
The contents of sector 1 on cylinder 0, track 0 are displayed first. You can advance one sector at a time by
pressing Enter, or you can return to the previous sector by pressing F14. Also, you can type over the
Starting sector address field. This field gives you direct access to any sector on the diskette.
Print reports:
The Print Reports display appears when you select the Print reports option on the Work with Diskette
Data Recovery display. You can print the following reports or select options from the Print Reports
display.
The Print Reports display appears when you select the Print reports option on the Work with Diskette Data
Recovery display. You can print the following reports or select options from the Print Reports display:
v Volume label report
The system space object supplies this report by virtual address in a standard hexadecimal and
character format. This option formats the volume label fields. The volume label field contains a field
description, the hexadecimal field offset into the sector, and the field contents.
v Data set label report
For each data set that is on the diskette, the system space object supplies a report by virtual address in
a standard hexadecimal and character format. This option formats the data set label fields. The data set
label field contains a field description, the hexadecimal field offset into the sector, and the field
contents.
v Load and dump object descriptor report
The system save and restore options specify a list of system objects that contains the database in the
request descriptor (RD) part of the source/sink request (SSR) data used by the REQIO instruction. For
each object that the REQIO instruction specifies, the load/dump I/O manager writes to the diskette a
load/dump object dump descriptor that contains a summary of the system environment from which that
object was dumped.
For each load/dump object dump descriptor contained on the diskette, the system space object dumps the
descriptor sector by virtual address in a standard hexadecimal and EBCDIC format. This option
formats the load and dump object dump descriptor fields. The descriptor field contains a field description,
the hexadecimal field offset into the sector, and the field contents.
v Failing sector report
Warning: Work with Diskette Data Recovery should only be used when
directed to by your service representative.
Opt Device
_ DKT01
_ DKT02
_ DKT03
_ DKT04
_ DKT05
_ DKT06
_ DKT07
_ DKT08
_ QDKT
F3=Exit F12=Cancel
2. Insert a diskette with read errors into the diskette unit with which you want to work.
3. Type a 3 in the Opt field next to the diskette unit in which you inserted the diskette and press the
Enter key. Selecting the read option moves the contents of the diskette to a system space object where
you can display or change them.
4. After the diskette is read into the system space object, select the Print reports option on the Work
with Diskette Data Recovery display to print the contents of the diskette. This helps you find the
failing sectors and the address of the system space object where you can change the contents of the
diskette.
5. Select a diskette summary report. Print the summary reports in any combination by typing a 6 in
front of the summary report you want and pressing Enter.
Note: The type of diskette you are working with determines the type of summary report you want to
print. All diskettes have volume headers and data set headers; therefore, you might want
summary reports for these areas. If you find read errors, you should look at the failing sector
summary. For diskettes that are used in save and restore operations, use the load and dump
object dump descriptor summary.
Some functions are restricted to DST use only and cannot be performed from SST.
For information on the Work with system partitions options, see “Work with system partitions” on page 42.
Note: Some functions are restricted to DST use only and cannot be performed from SST.
Some functions are restricted to DST use only and cannot be performed from SST.
For more information on the Work with system capacity option, see “Work with system capacity” on page
42.
Note: Some functions are restricted to DST use only and cannot be performed from SST.
Some functions are restricted to DST use only and cannot be performed from SST.
For more information on the Work with system security option, see “Work with system security” on page
43.
Note: Some functions are restricted to DST use only and cannot be performed from SST.
Some functions are restricted to DST use only and cannot be performed from SST.
For more information on the Work with service tools user IDs option, see “Work with service tools user
IDs” on page 27.
Note: Some functions are restricted to DST use only and cannot be performed from SST.
Keys F3, F5, F10, F12, and F16 usually have the following functions:
v F3 key ends the SST function.
v F5 key causes the system to ignore input to the display. Use this key to see the same display with the
input erased or a waiting display.
v F10 key causes the command entry display to be shown. You can then enter CL commands.
For information on using the Service Focal Point application on the Hardware Management Console
(HMC) for online problem analysis and resolution, see Using Service Focal Point.
For information on problem analysis and resolution on logical partitions, see Troubleshooting logical
partitions.
Online PAR manages system errors and gives the customer maximum system availability, effective
problem analysis, and a set of software tools for analyzing, repairing, and reporting problems. It runs
concurrently with other customer programs; therefore any part of the system that is not usable by the
customer is also unavailable for a problem analysis task. The customer should be aware of this when
deciding to run Online PAR.
Another part of PAR is the iSeries system problem management functions. This provides automated
problem analysis, automated problem logging and tracking, automated problem reporting, and problem
correction. It quickly and accurately manages problems occurring on the system. For more information on
the automated problem management functions, see “Service attributes (DSPSRVA or CHGSRVA)
commands” on page 228.
The system uses these error notes to create a problem log entry and sends a message to the QSYSOPR
message queue. The problem log entry has a description of the failing device. This description allows a
problem analysis procedure to be called without initial customer input.
For information on using the Service Focal Point application on the Hardware Management Console
(HMC) for online problem analysis and resolution, see Using Service Focal Point.
For information on problem analysis and resolution on logical partitions, see Troubleshooting logical
partitions.
Problem log:
The system operator and other authorized persons use the problem log to manage the problem records
that are made by Online PAR. Functions that the problem log provides include the following:
v Display problem records or print problem records
v Define a new problem
v Analyze an existing problem
v Report a problem
v Add notes to a problem record
v Recover from a problem
v Verify that a problem has been corrected
v Mark a problem as corrected
v Delete one or more problem records
v Query problem analysis status from a remote site
The customer has access to problem log functions in one of the following ways:
v Type the WRKPRB (Work with Problems) command and press Enter.
v On the Main Menu, select the Problem handling option. Then, on the Problem Handling display, select
the Work with problems option.
The WRKPRB command has search parameters available to control the range of problems that is
displayed. Pressing F4 displays the search parameters. One of these parameters is SRVID, which is the
problem management report (PMR) number the remote support system returned when it reported the
problem. Some other examples of search parameters are time range, type of failing hardware, and
resource name of failing hardware.
Each entry in the problem list that WRKPRB displays contains a unique, ten-digit problem identification
(ID). This ID appears on all displays for a specific problem and in the PMR for the problem in the remote
support system. The problem list has a field that you can use to specify the problem ID that you want to
go to directly.
When the system makes an entry in the problem log for each system-detected problem, it also sends a
message to the QSYSOPR message queue. Messages that are associated with system-detected problems
are marked with an asterisk (*) or are highlighted.
Start problem analysis by placing the cursor anywhere on the message line that contains the asterisk and
press F14. For more options, press the Help key to view the Additional Message Information display, then
press F14 (Work with Problem) to view the Work with Problems display. To see available online help, press
the Help key. For more information, see Start of call procedure.
Note: It is possible to have highlighted or marked with an asterisk multiple system messages that are
related to the same failure. For example, a 9335 A01 control unit failure would generate its own
message and two more system messages (one per actuator) for each B01 unit on the A01 device
function processor.
If you have additional messages that are marked with an asterisk from the original failure, you can
remove them by doing the following:
1. Close the problem under “Work with problem” (WRKPRB).
2. Display system messages [(DSPMSG QSYSOPR ASTLVL(*INTERMED)]. Run problem analysis by
moving the cursor to the message that is marked with an asterisk (*) or highlighted and pressing F14
to remove the * or highlighting. Then press F11 or select option 4 to remove the message.
220 System i and System p: Service provider information Service functions
You can use F14 multiple times on one message.
To display the message queue every time a message is logged, put the queue in *BREAK mode.
Putting the QSYSOPR message queue in Break mode lets the customer know immediately when the
system detects a problem. The customer can then choose to analyze the problem or delay analysis until a
later time. System-detected problems can be analyzed later by displaying QSYSOPR or using the
WRKPRB command.
Other messages that describe system problems can be logged in QSYSOPR although they are not
associated with a specific system-detected problem.
The first three letters in the message are the message identifier and indicate the message category. The
following list shows some typical message identifiers that relate to hardware:
CPA Messages that need system operator action
CPD Diagnostic messages
CPI Informational messages
MCH Machine interface
The remaining four digits indicate the sequence number of the message. If an error condition occurs, you
receive an error message that identifies the error.
1. Place the cursor anywhere on the same line as the error message.
2. Press the Help key. The resulting Additional Message Information display contains the message
identifier, the name of the program that is sending the message, and additional message information.
3. Read the additional message information about the error or the description of which corrective action
to take; take the corrective action.
Customer-detected problems
Online PAR guides the customer through a series of panels to solve customer problems, analyze problems
for a failing part, or generate a symptom string for reporting.
Customer-detected problem management is activated when the customer detects a problem that was not
detected by the system.
During the definition of a customer-detected problem, to prevent errors in the procedure, the system
guides the customer. System units supply a problem analysis (PDP) as the entry point from Online PAR.
After the problem is analyzed to a part, Online PAR determines which general entry PDP is requested, if
any. Online PAR generates a symptom string for a software error. The IBM service support system uses
the symptom string to determine whether a software problem already has an available fix.
When problem analysis is complete, online PAR gives the customer the option of reporting the problem.
For many problems, analysis results are shown as a field-replaceable unit. Other analysis procedures
make a symptom string to be reported with the problem.
Between code releases, problems that are found with the code are fixed with program temporary fixes
(PTFs).
The term PTF can refer to a Licensed Internal Code or an operating system fix. For more information on
fixes and cumulative PTFs, see “Fixes and cumulative PTF packages” on page 164.
For information on displaying the operating system PTFs that are installed on your system, see Operating
system fixes.
Use the system operation or the service library information to assist in performing the tasks that are
listed in Table 73. This ensures that the system is current for all known problems before you create an
authorized program analysis report (APAR).
Table 73. Tasks to perform before requesting a new i5/OS or LIC APAR
Task to be performed What to do Location of instructions
Determine whether Use support data: Support
customer-reported symptom is a publications, TIPS, Exception lists, or
problem fixed by a program Support Center recommendations
temporary fix (PTF).
Review the PTF level to see whether DSPPTF 5722SS1 and DSPPTF System operation information, iSeries
a cumulative PTF package needs to 5722999. Look for PTF marker. See Information Center
be installed. PTF levels on back.
Order a cumulative PTF package Send Program Temporary Fix Order System operation information
(SNDPTFORD) SF99VRM
Obtain a list of generally available SNDPTFORD SF97VRM (VRM = System operation information
iSeries PTFs. version, release, modification
example 410).
Determine if a PTF has been SNDPTFORD SF97VRM Find the PTF System operation information
superseded number in the PTF summary listing.
The latest PTF is listed in the
“replaced by” column.
Determine whether the system has all Check for HIPER marker TLYYDDD See “Displaying i5/OS PTFs.”
the LIC HIPER fixes. using DSPPTF 5722999 and compare
with the latest PSP.
Obtain a list of HIPER PTFs not in SNDPTFORD SF98VRM System operation information
the latest cumulative PTF package.
Resetting an IOP restarts and reloads that IOP. Use this procedure to recover from an intermittent error
condition.
Note: You can also perform an IOP reset under the Hardware Service Manager function (see “Debug the
resource” on page 62).
Note: You cannot reset the workstation IOP for the workstation at which you are working or a
workstation that is the only one on the system
1. Do you want to reset the local workstation IOP?
No: Continue with the next step.
Yes: Vary off the local workstation IOP (see “Varying configuration descriptions on and off” on
page 224). Then, go to step 6 on page 224 of this procedure.
2. Do you want to reset the communications IOP?
No: Continue with the next step.
Yes: Vary off all the lines on a communications IOP (see “Varying configuration descriptions on
and off” on page 224). Then, go to step 6 on page 224 of this procedure.
3. Do you want to reset the cryptographic IOP?
No: Continue with the next step.
Results
The Go Hardware display allows you to access all lines, devices, and IOPs and to see and change (vary on
or off) the configuration status for these resources.
The status of all configuration descriptions can also be displayed or changed (varied on or off) using the
WRKCFGSTS (*NWI | *CTL | *LIN | *NWS | *DEV) command. This command is also used for varying off a
line and all the IOPs and devices under it.
Notes:
1. All active jobs must be ended before you can vary off. You might be able to enter the
WRKACTJOB (Work with Active Jobs) command on the command line on the WRKCFGSTS
display or use the Work with Job option to end active jobs.
Note: To end active jobs running on the facsimile IOP, use the ENDFAXSPT command.
2. If a line, IOP, device, network interface (NWI), or nonprogrammable workstation is hung up,
varying its configuration description off, then on (in that sequence) provides recovery for some
intermittent problems.
3. You cannot display or change cryptographic resources by using the WRKCFGSTS command.
To view these resources, use the Work with Hardware Resources (WRKHDWRSC) command.
The following list provides a quick reference to commands that are commonly used in servicing the
System i. For more information on some of these service commands, see the iSeries Information Center.
If you know the name of the system value you want to display or change, you can use the Display
System Value (DSPSYSVAL) or Change System Value (CHGSYSVAL) command.
Changes to this value take effect immediately, and they might affect the system values QHOUR,
QMINUTE, and QSECOND.
QAUTOCFG
The automatic configuration indicator (QAUTOCFG) controls whether the system creates device
descriptions automatically for locally attached devices. The system default, 1, is to perform
automatic configuration. If you do not want the system to create device descriptions, change the
system value to zero (0). You can use the WRKSYSVAL command, or enter the following
command:
CHGSYSVAL SYSVAL(QAUTOCFG) VALUE('0')
QRMTSRVATR
The remote service attribute (QRMTSRVATR) system value controls incoming access to remote
service support through the iSeries electronic customer support line.
Note: You can also set or reset this system value by using the change service attributes command
(see “Service attributes (DSPSRVA or CHGSRVA) commands” on page 228).
You can display the service attributes by entering the Display Service Attributes (DSPSRVA) command or
change the service attributes by entering the Change Service Attributes (CHGSRVA) command.
ANZPRBAUTO:
The automated problem analysis function enables problem analysis routines to run automatically.
Problem analysis routines are programs that attempt to isolate a problem. At the time of the failure, they
run in a background batch job. This function also monitors for selected critical conditions. When it
encounters one, it sends a *BREAK message to users (who are specified by the service attribute,
CRITMSGUSR) to ensure that they recognize the condition.
The system default (*Yes) is to run the automated problem analysis function.
If you do not want the system to perform the automated problem analysis function, change the value to
*NO.
CRITMSGUSR:
When problem analysis routines run automatically, the CRITMSGUSR function specifies who is sent a
*BREAK message at the time of a failure.
Use the CRITMSGUSR (critical message user) function to create an ordered list of user identifiers and user
classes. When the system detects a critical condition, it notifies the first entry in the list by a *BREAK
message. If the user or the user class is not signed on, the system sequentially notifies the entries in the
list until a user is notified. For details on how to set up automatic problem analysis, see
“ANZPRBAUTO.”
The system default *QSYSOPR sends a *BREAK message to the system operator.
You can change the value and create an ordered list of user identifiers and user classes.
RPTPRBAUTO:
When problem analysis routines run automatically at the time of a failure (see “ANZPRBAUTO”), the
RPTPRBAUTO function specifies whether the software service provider is notified. For more information
on the service provider function, see “RPTSRVPVD” on page 229. To change the value of automated
reporting function, type:
CHGSRVA RPTPRBAUTO(*YES)
The system default is to run the automated problem notification (*YES). It runs in a background batch job
at the time of the failure.
RPTSRVPVD:
This function specifies the name of the service provider for your system.
When problems are automatically reported (see “RPTPRBAUTO” on page 228), this function specifies the
name of the service provider for your system.
You can change the service provider. Use the Help key for more information on the specific options.
SNDDTAPKT:
This function sends data that was collected at the time of the failure to the specified service provider.
When problems are automatically reported (see “RPTPRBAUTO” on page 228), this function sends data
that was collected at the time of the failure to the specified service provider.
The system default (*YES) is to send up to 2000 bytes of data to the service provider.
If you do not want the system to send data, change the system value to *NO.
PTFINSTYP:
This function specifies when to apply PTFs. To apply a PTF, use the install PTF command (INSPTF) or
the GO PTF command (select the Install a program temporary fix option from the Program Temporary Fix
(PTF) display).
These commands use the PTFINSTYP service attribute automatically when you do not specify the Type
field.
The system default (*DLYIPL) is to designate all of the PTFs for a delayed type of application, and then
perform an IPL on the system.
Use the Help key for more information on the specific options.
The command exists in library QFAX and is accessible only to users with *SERVICE authority.
Note: Do not change the transmit level unless you have direction from your next level of support.
Notes:
v At each ADDFAXCRD command request, the I/O processor tables are initialized.
v There is no online help information available for the CHGXMTLVL command.
When you run the WRKHDWPRD command, the Work with Hardware Products display appears with
the following options:
Selection
__
F3=Exit F12=Cancel
Using the configuration description label information to prepare for a system upgrade:
Before powering the system down for an upgrade, you must record specific system value information,
verify the system configuration, and create (physical) labels to attach to the system cables and devices.
Note: You must press the F17 key even if a printer is not available. Pressing the F17 key places a
copy of the label locations in the system print spool if a printer is not available. This allows
the label locations to print at another time or at another printer location. You can continue by
copying the information from the displays onto a piece of paper.
6. Use the Display Description Label Locations printout to verify that all of the system cables and
devices are labelled correctly.
--------------Location-------------------
Frame EIA Device Card
ID Location Position Position Port Label
T1 2 CTL01
T1 3 CTL03
T1 4 BLDG6, CTL02
T1 4 TAP01
T1 5 DKT01
T2 2 TCTCONNECT, TRNLINE
T2 3 TRNBACKUP
T2 4A QESLINE, QTILINE,
QTIPASLIN
T2 4B *NONE
T2 5A SANFRAN
T2 5B DALLAS
T2 6A ENDICOTT, LIN003
More ...
F3=Exit F11=Display types/serial numbers F12=Cancel
F17=Print
Note: If no label is attached to the cable, *NONE indicates that it is not necessary to attach a
label to the cable.
8. Find the blank labels that came with the upgrade shipment.
9. Create a label for each cable or device that you identified:
a. On the blank labels that were provided, write the information that appears in the Label column.
10. Use the Card Position, Device Position, Type-Model, and Serial Number columns on the printout to assist
in locating the devices.
Results
After completing the upgrade, verify that labels that are attached to the cables or devices match label
information in the system. For details, see “Using the configuration description label information after a
system upgrade.”
After performing a system upgrade, you must update the configuration description label information in
the system to match the information that appears on the (physical) label that is attached to the cable or
device.
1. Perform an attended IPL:
a. Select Manual mode on the control panel.
b. Power on the system.
c. When the IPL display or the Install display appears, select the Perform an IPL option.
2. The Sign On display appears. Ask the customer to sign on as QSECOFR.
Note: It is important that you perform the following step to correctly update the device resource
names.
3. At the IPL Options display:
a. Set the Start this device only option to Y (Yes).
b. Set the Define or change system at IPL option to Y (Yes).
c. Select System value commands option.
d. Select Change system values option.
e. Ensure that the system value QAUTOCFG is '0'
f. Ensure that the system value QIPLTYPE is '2'
Press F3 twice to continue the IPL.
Note: As the IPL continues, SRC A900 2000 appears. No action is necessary at this time.
4. Have the customer sign off after the IPL is complete.
5. Sign on to the system at the console:
v On the User line of the Sign On display, type QSRV
----------------Location-----------------
Frame EIA Device Card
Opt ID Location Position Position Port Label
T1 2 CTL01
T1 3 CTL03
T1 4 *INCORRECT
T1 5 *NONE
T1 4 *NONE
T1 5 DKT01
T2 2 *NONE
T2 3 *NONE
T2 4A QESLINE, QTILINE, ...
More...
F3=Exit F11=Display types/serial numbers F12=Cancel F17=Print
9. Press the F17 key to print a worksheet. If a printer is not available, continue the procedure by noting
the information from the displays onto a piece of paper.
Note: Do not use the printout from the Display Description Label Locations display.
10. Use the Change Description Label Locations display or worksheet to verify that all of the system
cables and devices are labelled correctly.
11. Compare the label that is attached to the cable or device with the name that appears in the Label
column.
v Label information matches if the following occurs:
a. The name on the label that is attached to the cable or device is the same as the information in
the Label column on the display.
Note: If you replace the previously labeled cable or device during the system upgrade, be sure
to transfer the existing label information to the replacement cable or device.
v Label information does not match if the following occurs:
a. There is information in the Label column, but no label is attached to the cable. (The following
steps of this procedure instruct you to create a label.)
b. The label that is attached to the cable does not match the information in the Label column.
(The following steps of this procedure instruct you to change the system label.)
Note: It is normal for the resource names to change during the upgrade process. Do not use the
resource name information from other displays to match the labels.
No Yes
↓ The system label information is the same as the (physical) label.
Press the F17 key on the Change Description Label display to request a printout of the new
information for your records.
Go to step 23 on page 236 of this procedure.
13. Do you need to create physical labels?
No Yes
↓ Perform the following if there is information in the Label column, but no label is attached to
the cable:
a. Write the information that appears in the Label column on a blank label (labels were
provided with the upgrade).
b. Attach the label to the cable or device.
c. Continue to the next step of this procedure.
14. Do you need to change the description label information in the system?
Yes No
↓ The system label information is the same as the (physical) label. Go to step 20 on page 236 of
this procedure.
15. On the Change Description Label Locations display, type 2 in the Opt column for each location that
requires a label change.
Press Enter.
Note: You can make more than one selection at a time, but if More... appears on the bottom of the
screen, do not press Enter. Page forward to select the remaining labels.
16. The Change Description Label display appears.
A list of possible label names is shown for the first item you selected.
To select the label name (on the display) that matches the label that is attached to that cable or
device, perform the following:
a. Type 1 in the Opt column for each location that you want to change.
b. Press Enter.
Note: If you cannot find (on the display) the label that matches the label attached to that cable or
device, verify that your information is correct. If it is correct, contact your next level of
support for assistance.
17. If you chose to change more than one item, the Change Description Label display appears for the
next label.
A message at the bottom of the display indicates whether the previous change was successful.
18. For all of the labels that require a change, repeat steps 14 through 17.
Verify commands
Use the verify command to check for the correct operation of hardware and communications.
Use the verify command to check for the correct operation of hardware and communications. To display
a menu of the verify commands, type.
GO CMDVFY
You can also use the Hardware Service Manager function to verify hardware and communications. For
details, see “Verification procedures” on page 91.
Verify communications
Use the VFYCMN (verify communications) command to verify correct hardware operation.
Note: Use the VFYCMN command to assist in isolating hardware problems that the system does not
detect.
v Run concurrent Link Problem Determination Aid-2 (LPDA-2) tests. For details, see “Concurrent
LPDA-2 tests” on page 245.
v Run wireless diagnostic tests.
v Monitor telephone lines and modems concurrently.
v Monitor modems interface signals.
v Verify a communications link.
For information on running a trace on a communications interface and other tests that are available, see
“Communications tests” on page 243.
You can verify communications by using the VFYCMN command or the problem handling option.
Note: Before running the verification test (which loads a diagnostic program into the card), ensure
that the customer is not using the resource that you want to test.
Test descriptions:
You can test various resources including modems, cables, I/O adapters, and Local Area Network (LAN)
links.
When you run these tests, the system displays only that the test completed successfully or failed. You can
get additional problem isolation information by running more than one test. For example, if the
communications cable test is failing, before you can isolate positively the cable as the cause of the
problem, you must also run the communications I/O adapter card test. If the communications I/O
adapter card test completes successfully, the communications cable is failing. If the communications I/O
adapter card test fails, the communications I/O adapter card is failing.
The remote modem test verifies that the remote modem is operating correctly.
For this test the remote modem must be compatible with LPDA-1 or LPDA-2 diagnostic tests and must
be attached via a nonswitched telephone line. The MODEM parameter in the line description determines
the diagnostic test to run. Because this test loads a diagnostic program into the card, you must vary off
all lines from the communications I/O adapter before running the test. The diagnostic program takes the
place of the programs that are used for normal operation.
If this test completes successfully, the remote modem and the telephone line are operating correctly.
If this test fails, the remote modem or the telephone line is the cause of the problem.
The local modem test verifies that the local modem is operating correctly. For this test the local modem
must be compatible with LPDA-1, LPDA-2, or V.54 loop 3 diagnostic tests, or support the IBM ability to
wrap.
The MODEM parameter in the line description determines the diagnostic test to run. Because this test
loads a diagnostic program into the card, you must vary off all lines from the communications I/O
adapter before running the test. The diagnostic program takes the place of the programs that are used for
normal operation.
If this test completes successfully, the local modem, the communications cable, and the communications
I/O adapter card are operating correctly. However, modems that are not compatible with LPDA-1 or
LPDA-2 diagnostic tests are not completely tested. It is possible that they are failing, although the local
modem test completes successfully.
If this test fails, the cause of the problem is the local modem, the communications I/O adapter card, or
the communications cable.
To further isolate the cause of the problem, run the communications cable test and the communications
I/O adapter card test.
The communications cable test verifies that the communications cable is operating properly. Because this
test loads a diagnostic program into the card, you must vary off all lines from the communications I/O
adapter before running the test.
For this test, the cable must be an IBM cable with a wrap connector plugged in (note that IBM token-ring
cables are self-wrapping; no external wrap connector is needed).
Notes:
v If this test completes successfully, the communications cable and the communications I/O
adapter card are operating properly.\
v If this test fails, the cause of the problem is the communications cable or the communications
I/O adapter card.
v To further isolate the cause of the problem, run the communications I/O adapter card test.
Test results:
v If this test completes successfully, the communications I/O adapter card is operating correctly.
v If this test fails, the I/O adapter card might be failing.
Notes:
1. Verify that the wrap connector has the correct identifier (as indicated by the display prompt)
and is properly installed.
2. In some conditions, the associated I/O processor is the failing card. Select the I/O processor
test option, if it is available on the display, to verify the I/O processor operation.
The communications I/O processor test verifies the correct operation of the I/O processor card. Because
this test loads a diagnostic program into the card, you must vary off all lines from the communications
I/O processor before running the test.
The communications I/O processor memory test verifies that the storage of the I/O processor card is
operational. Because this test loads a diagnostic program into the card, you must vary off all lines from
the communications I/O processor before running the test.
If the test completes successfully, memory modules on the I/O processor card are operational.
If the test fails, a memory module on the I/O processor card is failing. If the memory modules on the
card are replaceable, exchange the failing memory module. Otherwise, exchange the communications I/O
processor card.
The communications port A modem and coupler test verifies that the modem (which is built into the I/O
adapter card) and the externally attached coupler are operating correctly.
If these tests complete successfully, the modem and the coupler are operational.
If a modem error appears on the Results display, exchange the I/O adapter.
Note: A test is provided for both ports (A and B) on the I/O adapter card. If one port is operational, the
I/O adapter card is still operational.
The External Ring test verifies that all hardware to the network is operational.
Note: The External Ring Test is not supported on token-ring hardware for V4R5.
The External Ring test verifies that all hardware to the network is operational. It is available for
token-ring networks and distributed data interfaces. To run this test, all hardware must be connected as it
would be in normal operation. This test allows a signal to be sent through the network and wrapped (no
wrap connectors are required).
If the test completes successfully, the adapter, cable, and access unit are operating correctly.
For further problem analysis if the test fails, run the cable and I/O adapter tests in the order in which the
display lists them.
The communications and, or local area network link test allows you to send data to remote equipment
using the Ethernet, token-ring, DDI, wireless, SDLC, X.25, or BSC protocols.
This test is useful on multipoint lines to verify that a specific terminal is operating correctly without
interrupting normal operation of the other terminals.
To run this test, you must have the line varied on, and you must make a connection with the remote
equipment. This is necessary because the functional communications program performs this test. If you
are using the BSC protocol and the remote equipment is not a System i, a service representative is needed
at the remote location to start diagnostic programs. When you run a link test against the Local Area
Network, you can enter *NONE in the controller description field to test a specific remote adapter
address.
If this test completes successfully, all equipment within the communications link is operating correctly.
If this test fails and all other devices on the line are operating correctly, one of the following could be the
problem:
v The remote device that is being tested
v The remote modem
v The cabling at the remote site
If this test fails and all devices on the line are not operating correctly, run the cable, modem, and I/O
adapter tests in the order they are listed on the display for further problem analysis.
The wireless network management utility (WNMU) test allows you to monitor the operation of a wireless
network. This utility collects information that assists in analyzing network problems. Before running this
utility, make sure that the line and the attached descriptions are varied on, and a job is active. The
following functions are available:
v Display active network topology
v Collect wireless network statistics
v Display statistics for any node on the wireless network
v Run tests between any wireless network nodes
Note:
1. Running the wireless network management utility might affect the performance of the network
or decrease system performance.
2. For more information on the wireless LAN adapter indicators, see “Wireless LAN adapter card
indicators” on page 243.
The wireless echo back test verifies the correct operation of a device on the wireless network. Because this
test loads a diagnostic program into the card, ensure that all lines from the communications I/O adapter
are varied off before running the test.
Note: If more than one device is not present in the network, the test will fail.
The system allows you to perform the echo back procedure using the following:
v RS-485 cable connection
v Radio connection (that uses the system configuration)
v Radio connection (that uses a test configuration)
The Echo back test on RS-485 cable connection verifies communication to any device on the RS-485 wired
network. If this test completes successfully, the adapter and RS-485 wired link are working correctly. If
this test fails, run the I/O adapter tests in the order they are listed on the display to further analyze the
problem.
The Echo back test on radio connection using system configuration verifies communication to any device on
the radio network by using the configuration for the line selected. If this test completes successfully, the
adapter and radio link are working correctly. If this test fails, run the Echo back test on radio connection
using test configuration.
The Echo back test on radio connection using test configuration verifies communication to any device by using
a test configuration. The device must be within radio range of the antenna that is connected to the
Wireless LAN Adapter card. If this test fails, run the I/O adapter tests in the order they are listed on the
display for further problem analysis. If this test completes successfully, the adapter and radio link work
successfully with the test configuration. If you performed this test after an Echo back test on radio
connection using system configuration test failed and this test passed, a configuration problem exists.
The cryptographic processor test verifies the correct operation of the cryptographic I/O processor.
To run this test, you must also refer to the IBM Common Cryptographic Architecture Services/400 Installation
and Operating Guide, SC41-0102.
Attention: Disconnecting or removing the type 2620 or type 2628 cryptographic I/O processor for any
reason causes the loss of the master encryption key. Before disconnecting or removing the cryptographic
I/O processor, ensure that the customer has access to a record of the master encryption key. The customer
must reinstall the master encryption key after completing any service action that involves disconnecting
or removing the cryptographic I/O processor before the data encryption function can be used again.
Refer the customer to IBM Common Cryptographic Architecture Services/400 Installation and Operating Guide,
SC41-0102, for more information.
If this test completes successfully, the cryptographic I/O processor is operating correctly.
The cryptographic processor card wrap test verifies the correct operation of the cryptographic I/O
processor card. To run this test, you must also refer to the IBM Common Cryptographic Architecture
Services/400 Installation and Operating Guide, SC41-0102.
Before running this test, end the resource by entering the ENDCS (End Cryptographic Services)
command. The test loads a diagnostic program into the cryptographic I/O processor card.
If this test completes successfully, the cryptographic I/O processor card is operating correctly.
If this test fails, verify that the wrap connector is the correct part number (as indicated by the display
prompt) and that it is installed correctly. Then, exchange the cryptographic I/O processor card.
Attention: Disconnecting or removing the type 2620 or type 2628 cryptographic I/O processor for any
reason causes the loss of the master encryption key. Read the important information under “2620/2628
cryptographic processor card test” on page 241 before disconnecting or removing the cryptographic I/O
processor.
The external cryptographic hardware tests verify the correct operation of the hardware that is attached to
the cryptographic I/O processor.
Note: When you have completed testing the external cryptographic hardware, you must perform the
Reset Processor and Exit function to restart the encryption subsystem.
v Security Interface Unit Cable Wrap Test:
This test verifies the correct operation of the security interface unit cable.
If this test completes successfully, the security interface unit cable that is attached to the cryptographic
I/O processor card and the cryptographic I/O processor is operating correctly.
If this test fails, verify that the wrap connector is the correct part number (as indicated by the display
prompt) and that it is installed correctly.
To further isolate the cause of the problem, run the cryptographic processor card wrap test. If the
security interface unit cable wrap test fails and the cryptographic processor card wrap test passes,
replace the security interface unit cable.
v Personal Security Card Test:
The LocalTalk interface test verifies that the workstation I/O adapter card and the cable (connector box
cable) that attaches to the workstation I/O adapter card are operating correctly.
The workstations that support LocalTalk protocol and the connecting cables are not tested. Because the
test loads a diagnostic program into the communications I/O adapter card, you must run the test from a
workstation that is not attached to the I/O adapter you are testing. To run this test, you must have more
than one workstation I/O adapter on the system.
If this test completes successfully, the workstation I/O adapter card and the cable that attaches to the
workstation I/O adapter card are operating correctly.
If this test fails, a display indicates the probable failure rates of the workstation I/O adapter card and the
cable that attaches to the workstation I/O adapter card.
Communications tests
Communications tests include the wireless LAN adapter and indicators test, communications interface
trace, and concurrent LPDA-2 tests.
To achieve the most accurate sample of the lines, start the trace before varying on the communications
lines. This test monitors the following modem interface signals:
Data Terminal Ready (DTR)
Data terminal equipment (DTE) uses this signal to show the modem that the DTE is ready to
transmit and receive data.
Data Set Ready (DSR)
For nonswitched telephone lines, the active DSR signal shows that the modem is powered-on and
ready to transmit and receive data. For switched telephone lines, the active DSR signal shows
that the modem is connected to the telephone line and is ready to transmit data.
Request To Send (RTS)
The request to send trace uses this signal to activate or deactivate the modem’s modulator lines.
If the DSR signal is active, the RTS signal causes the modem to activate the carrier signal.
Ready For Sending (CTS)
The modem activates this signal in response to the Request To Send signal when the modem is
ready to transmit data. When the CTS signal is active, the DTE can send data on the transmitted
data line.
CTS delay is the time between the RTS signal active condition and the CTS signal active
condition. On most nonswitched telephone line modems, there are three CTS delay options,
ranging from 0 to 250 milliseconds (ms). Switched telephone line modems, operating in
half-duplex mode, are normally set for 150 to 250 ms of CTS delay.
Carrier Detect (CD)
The modem uses this signal to show the DTE that the modem is receiving an acceptable carrier
signal. Because of hardware limits on taking short frame samples, the carrier detect signal might
not be accurate. In this condition, an asterisk (*) takes the place of the sample data. The status is
still correct.
This test displays five of the modem interface signals in a graphic format, showing the time
relationship of the signals to each other.
Test description
Use this option to run the Verify Link; it supports the LPDA-2 (VFYLNKLPDA) command. The
concurrent LPDA-2 tests let you retrieve information from the data circuit-terminating equipment (DCEs).
DCEs can be analog (modems) or digital (combined data service units (DSUs) and channel service units
(CSUs)). You can get information from four tests:
v DCEs and line status
v DCEs and line test
v Analyze line
v Send and receive test
You can run the LPDA-2 tests on a line while applications are using the line. The tests do not interrupt
communications but temporarily slow the data transfer.
The DCEs and line status and DCEs and line test options are two modes of the same LPDA-2 request.
The DCEs and Line Status test reports parameters that the local and remote DCEs monitor during normal
communications.
The DCEs and Line Test reports these parameters, runs internal tests, and reports the results. If poor line
conditions are causing problems at normal speed, this test is sent over the communications line to the
remote DCE at a slower transmit speed.
You can run the Analyze line test only on analog DCEs (modems). The test causes the modems to
exchange test patterns on the line. The modems measure parameters of the analog signals. The modems
report:
v Frequency shift
v Second and third harmonic distortion ratios
v Signal to noise ratio
v Phase jitter
v Receive level
v Transmit level
v Round trip delay time
v Modem type, model, address, and transmit speed
v Number of line errors and RLSD losses
The Send and receive test causes the DCEs to exchange several blocks of test patterns and track the errors
that occur during transmission. The test reports the following:
v DCE type, model, address, and transmit speed
v Signal lost condition
v Worst line quality
v Number of line errors
v The number of blocks that are sent, received, and in error
The manufacturer may not offer the products, services, or features discussed in this document in other
countries. Consult the manufacturer’s representative for information on the products and services
currently available in your area. Any reference to the manufacturer’s product, program, or service is not
intended to state or imply that only that product, program, or service may be used. Any functionally
equivalent product, program, or service that does not infringe any intellectual property right of the
manufacturer may be used instead. However, it is the user’s responsibility to evaluate and verify the
operation of any product, program, or service.
The manufacturer may have patents or pending patent applications covering subject matter described in
this document. The furnishing of this document does not give you any license to these patents. You can
send license inquiries, in writing, to the manufacturer.
The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: THIS INFORMATION IS PROVIDED “AS IS” WITHOUT
WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF 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.
The manufacturer may make improvements and/or changes in the product(s) and/or the program(s)
described in this publication at any time without notice.
Any references in this information to Web sites not owned by the manufacturer are provided for
convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at
those Web sites are not part of the materials for this product and use of those Web sites is at your own
risk.
The manufacturer may use or distribute any of the information you supply in any way it believes
appropriate without incurring any obligation to you.
Any performance data contained herein was determined in a controlled environment. Therefore, the
results obtained in other operating environments may vary significantly. Some measurements may have
been made on development-level systems and there is no guarantee that these measurements will be the
same on generally available systems. Furthermore, some measurements may have been estimated through
extrapolation. Actual results may vary. Users of this document should verify the applicable data for their
specific environment.
Information concerning products not produced by this manufacturer was obtained from the suppliers of
those products, their published announcements or other publicly available sources. This manufacturer has
not tested those products and cannot confirm the accuracy of performance, compatibility or any other
claims related to products not produced by this manufacturer. Questions on the capabilities of products
not produced by this manufacturer should be addressed to the suppliers of those products.
All statements regarding the manufacturer’s future direction or intent are subject to change or withdrawal
without notice, and represent goals and objectives only.
This information is for planning purposes only. The information herein is subject to change before the
products described become available.
This information contains examples of data and reports used in daily business operations. To illustrate
them as completely as possible, the examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the names and addresses used by an
actual business enterprise is entirely coincidental.
If you are viewing this information in softcopy, the photographs and color illustrations may not appear.
The drawings and specifications contained herein shall not be reproduced in whole or in part without the
written permission of the manufacturer.
The manufacturer has prepared this information for use with the specific machines indicated. The
manufacturer makes no representations that it is suitable for any other purpose.
The manufacturer’s computer systems contain mechanisms designed to reduce the possibility of
undetected data corruption or loss. This risk, however, cannot be eliminated. Users who experience
unplanned outages, system failures, power fluctuations or outages, or component failures must verify the
accuracy of operations performed and data saved or transmitted by the system at or near the time of the
outage or failure. In addition, users must establish procedures to ensure that there is independent data
verification before relying on such data in sensitive or critical operations. Users should periodically check
the manufacturer’s support websites for updated information and fixes applicable to the system and
related software.
Trademarks
The following terms are trademarks of International Business Machines Corporation in the United States,
other countries, or both:
AIX
eServer
i5/OS
IBM
OpenPower
POWER5
System i
System p
InfiniBand and the InfiniBand design marks are trademarks and/or service marks of the InfiniBand Trade
Association.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Other company, product or service names may be trademarks or service marks of others.
Regulatory notices
Class A Notices
The following Class A statements apply to the IBM System i models and IBM System p servers with the
exception of those that are specifically identified as Class B.
Note: This equipment has been tested and found to comply with the limits for a Class A digital device,
pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against
harmful interference when the equipment is operated in a commercial environment. This equipment
generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with
the instruction manual, may cause harmful interference to radio communications. Operation of this
equipment in a residential area is likely to cause harmful interference, in which case the user will be
required to correct the interference at his own expense.
Properly shielded and grounded cables and connectors must be used in order to meet FCC emission
limits. IBM is not responsible for any radio or television interference caused by using other than
recommended cables and connectors or by unauthorized changes or modifications to this equipment.
Unauthorized changes or modifications could void the 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.
Cet appareil numérique de la classe A respecte est conforme à la norme NMB-003 du Canada.
This product is in conformity with the protection requirements of EU Council Directive 89/336/EEC on
the approximation of the laws of the Member States relating to electromagnetic compatibility. IBM cannot
accept responsibility for any failure to satisfy the protection requirements resulting from a
non-recommended modification of the product, including the fitting of non-IBM option cards.
This product has been tested and found to comply with the limits for Class A Information Technology
Equipment according to European Standard EN 55022. The limits for Class A equipment were derived for
commercial and industrial environments to provide reasonable protection against interference with
licensed communication equipment.
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.
The following is a summary of the VCCI Japanese statement in the box above.
This is a Class A product based on the standard of the Voluntary Control Council for Interference by
Information Technology Equipment (VCCI). If this equipment is used in a domestic environment, radio
disturbance may arise. When such trouble occurs, the user may be required to take corrective actions.
Declaration: This is a Class A product. In a domestic environment this product may cause radio
interference in which case the user may need to perform practical action.
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.
Dieses Gerät ist berechtigt in Übereinstimmung mit Dem deutschen EMVG vom 9.Nov.92 das
EG–Konformitätszeichen zu führen.
Dieses Gerät erfüllt die Bedingungen der EN 55022 Klasse A. Für diese von Geräten gilt folgende
Bestimmung nach dem EMVG:
Hinweis
Dieses Genehmigungsverfahren ist von der Deutschen Bundespost noch nicht veröffentlicht worden.
Class B Notices
The following Class B statements apply to model 9111-520 (stand-alone version), 9131-52A (stand-alone
version), 7047-185 and the 9111-285.
Note: This equipment has been tested and found to comply with the limits for a class B digital device,
pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against
harmful interference in a residential installation. This equipment generates, uses, and can radiate radio
frequency energy and, if not installed and used in accordance with the instructions, may cause harmful
interference to radio communications. However, there is no guarantee that interference will not occur in a
particular installation. If this equipment does cause harmful interference to radio or television reception,
which can be determined by turning the equipment off and on, the user is encouraged to try to correct
the interference by one or more of the following measures:
v Reorient or relocate the receiving antenna.
v Increase the separation between the equipment and receiver.
v Connect the equipment into an outlet on a circuit different from that to which the receiver is
connected.
v Consult an IBM authorized dealer or service representative for help.
Properly shielded and grounded cables and connectors must be used in order to meet FCC emission
limits. Proper cables and connectors are available from IBM authorized dealers. IBM is not responsible for
any radio or television interference caused by using other than recommended cables or connectors or by
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 interferences, and (2) this device must accept any interferences
received, including interference that may cause undesired operation.
This product is in conformity with the protection requirements of EC Council Directive 89/336/EEC on
the approximation of the laws of the Member States relating to electromagnetic compatibility. IBM cannot
This product has been tested and found to comply with the limits for Class B Information Technology
Equipment according to CISPR 22 / European Standard EN 55022. The limits for Class B equipment were
derived for typical residential environments to provide reasonable protection against interference with
licensed communication devices.
Properly shielded and grounded cables and connectors must be used in order to reduce the potential for
causing interference to radio and TV communications and to other electrical or electronic equipment.
Such cables and connectors are available from IBM authorized dealers. IBM cannot accept responsibility
for an interference caused by using other than recommended cables and connectors.
The following is a summary of the VCCI Japanese statement in the box above.
This is a Class B product based on the standard of the Voluntary Control Council for Interference by
Information Technology Equipment (VCCI). If this equipment is used in a domestic environment, radio
disturbance may arise. When such trouble occurs, the user may be required to take corrective actions.
Dieses Gerät ist berechtigt in Übereinstimmung mit Dem deutschen EMVG vom 9.Nov.92 das
EG–Konformitätszeichen zu führen.
Dieses Gerät erfüllt die Bedingungen der EN 55022 Klasse B. Für diese von Geräten gilt folgende
Bestimmung nach dem EMVG:
Hinweis
Dieses Genehmigungsverfahren ist von der Deutschen Bundespost noch nicht veröffentlicht worden.
Personal Use: You may reproduce these publications for your personal, noncommercial use provided that
all proprietary notices are preserved. You may not distribute, display or make derivative works of these
publications, or any portion thereof, without the express consent of the manufacturer.
Commercial Use: You may reproduce, distribute and display these publications solely within your
enterprise provided that all proprietary notices are preserved. You may not make derivative works of
these publications, or reproduce, distribute or display these publications or any portion thereof outside
your enterprise, without the express consent of the manufacturer.
Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either
express or implied, to the publications or any data, software or other intellectual property contained
therein.
The manufacturer reserves the right to withdraw the permissions granted herein whenever, in its
discretion, the use of the publications is detrimental to its interest or, as determined by the manufacturer,
the above instructions are not being properly followed.
You may not download, export or re-export this information except in full compliance with all applicable
laws and regulations, including all United States export laws and regulations.
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 sitio web de IBM http://www.ibm.com/ibm/environment/products/prp.shtml.
Appliances are labeled in accordance with European Directive 2002/96/EC concerning waste electrical
and electronic equipment (WEEE). The Directive determines the framework for the return and recycling
of used appliances as applicable throughout the European Union. This label is applied to various
products to indicate that the product is not to be thrown away, but rather reclaimed upon end of life per
this Directive.
In accordance with the European WEEE Directive, electrical and electronic equipment (EEE) is to be
collected separately and to be reused, recycled, or recovered at end of life. Users of EEE with the WEEE
marking per Annex IV of the WEEE Directive, as shown above, must not dispose of end of life EEE as
unsorted municipal waste, but use the collection framework available to customers for the return,
recycling, and recovery of WEEE. Customer participation is important to minimize any potential effects of
EEE on the environment and human health due to the potential presence of hazardous substances in EEE.
For proper collection and treatment, contact your local IBM representative.
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 California:
The foregoing notice is provided in accordance with California Code of Regulations Title 22, Division 4.5
Chapter 33. Best Management Practices for Perchlorate Materials. This product/part may include a
lithium manganese dioxide battery which contains a perchlorate substance.
Printed in USA