GSMGPRS Alcatel BSS Gateway Configuration Distribution Note

Netcool® Performance Manager for Wireless

Version 3.5.0

GSM/GPRS Alcatel BSS B11 Gateway Configuration Distribution Note

Document Revision Number 2.0

IBM

TIVOLI® NETCOOL® PERFORMANCE MANAGER FOR WIRELESS GSM/GPRS ALCATEL BSS GATEWAY CONFIGURATION DISTRIBUTION NOTE

This edition applies to IBM® Tivoli® Netcool® Performance Manager for Wireless and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation, 2010. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Note: Before using this information and the product it supports, read the information in Notices on page 17.


ALCATEL_BSS-GCDN - iii

Table of Contents

1 About this Documentation................................................................................................................. 1

1.1 Audience ......................................................................................................................................1 1.2 Required Skills and Knowledge ...................................................................................................1

2 Associated Documents ...................................................................................................................... 2

2.1 Referenced Documents ...............................................................................................................2 2.2 Other Related Documents............................................................................................................2

3 Introduction ......................................................................................................................................... 3

3.1 Vendor Gateway Version .............................................................................................................3

4 Release History ................................................................................................................................... 4

4.1 Release 3.5.0 ...............................................................................................................................4 4.2 Release 3.4.0 ...............................................................................................................................4

5 Data type and releases supported .................................................................................................... 5

5.1 Raw input files ..............................................................................................................................5 5.2 Hierarchy input files....................................................................................................................10

6 Configurations .................................................................................................................................. 13

6.1 Transfer Engine configuration....................................................................................................13 6.2 Pre Parser Engine configuration ................................................................................................13 6.3 Parser Engine configuration.......................................................................................................13 6.4 Post Parser user configuration...................................................................................................14 6.5 Known Issues.............................................................................................................................16

Appendix A Notices and Trademarks................................................................................................. 17


ALCATEL_BSS-GCDN - 1

1 About this Documentation

1.1 Audience

The target audience of this document is IBM Performance Manager for Wireless customers. They should be

familiar with telecommunication and IT principles and should also have a good understanding of Solaris.

IMPORTANT: Before attempting an installation of Performance Manager for Wireless you are strongly

advised to read the release notes and any readme files distributed with your Performance Manager for

Wireless software. Readme files and release notes may contain information specific to your installation not

contained in this guide. Failure to consult readme files and release notes may result in a corrupt, incomplete

or failed installation.

Note: Performance Manager for Wireless Administrators should not, without prior consultation and

agreement from IBM, make any changes to the Index Organized tables or database schema. Changes to the

Index Organized tables or database schema may result in corruption of data and failure of the Performance

Manager for Wireless System. This applies to all releases of Performance Manager for Wireless using all

versions of interfaces.

1.2 Required Skills and Knowledge

This guide assumes you are familiar with the following:

• General IT Principles

• Sun Solaris Operating System

• Oracle Database

• Windows operating systems

• Graphical User Interfaces

• Network Operator's OSS and BSS systems architecture

This guide also assumes that you are familiar with your company’s network and with procedures for

configuring, monitoring, and solving problems on your network.



2 Associated Documents

The following documentation accompanies this release:

2.1 Referenced Documents

Document Name Document Description

[Gateways Install Note] This document describes the steps required to install and

run a Gateway.

2.2 Other Related Documents

Document Name Document Description

[Gateway Framework

User Guide]

Gateway Framework User Guide describing the

management and configuration of the Gateway

Framework.

[Alcatel BSS User

Guide]

Alcatel BSS User Guide describing the management and

configuration of the Vendor Gateway.



3 Introduction

You should read this Distribution Note before proceeding to install the Gateway Configuration.

For information on the Gateway Framework, its configuration and use refer to the [Gateway

Framework User Guide].

The Gateway Framework and Vendor Gateway are supplied as separate packages. As part of the

Vendor Gateway installation process, it must reference a Gateway Framework installation. This

separation simplifies the maintenance and version control of multiple vendor Gateway installations

on a single server.

This Distribution Note provides an overview of the release history of the Gateway Configuration.

3.1 Vendor Gateway Version

The Gateway Framework requirement is release 3.5.1.8

This Gateway Configuration requires the following Vendor Gateway:

- Alcatel BSS 3.5.1.4

- Generic CSV 3.5.0.2



4 Release History

4.1 Release 3.5.0

Release date 23 Mar 2010

Listed below are the enhancements to this release.

# Description 1 Configuration for B11

4.2 Release 3.4.0

Release date 10 Mar 2009

Bug# Description

valnt00075362 To include OMC name in PIF filename .

Eg TYPE_8-#-8-#-OMC1-#-01Aug2007-#-16:00-#-01Aug2007-#-17:00-#-I-#-CC-#-S.lif

, where OMC name is OMC1 which derived from input_d folder

Sample input_d directory structure is as below :

../spool/input/Network_A/Region_B/OMC1

../spool/input/Network_A/Region_B/OMC2



5 Data type and releases supported

Gateway Configuration

Release Directory

Vendor Performance data Supported Vendor

Version

b011 Alcatel BSS B11, B10, B9

v10.0 Alcatel BSS B10, B9

v9.0 Alcatel BSS B9

5.1 Raw input files

Scope Attended Format/Syntax

Input files names to expect GSM Data: <BSS_file_name>.<BSC_num>.<BSS_name>.<file_cre

ation_date>.<file_creation_time>.<sequence_num>.<BS

S_version>

Where

<BSS_file_name> : PM<YYY>-<tt>.<xx>A

<YYY>: RES for binary file and ASC for ASCII files.

<tt>: raw measurement type number. For type 110, 180

the formats are

PM<YYY>110.<xx>A and PM<YYY>180.<xx>A;

<xx> : version number (01...99) of the file in the BSC.

<BSC_num> : BSC number

<BSS_name> : name of the BSS as it is known

by the OMC (up to 20 characters).

<file_creation_date> : date when the file is created on

the OMC-R. Format: YYYY-MM-DD

<file_creation_time> : time when the file is created on

the OMC-R. Format: HH:MM:SS

<sequence_num> : number (between 1 and 9999)

given by the OMC in order to guarantee the unicity of

the file.

<BSS_version> : BSS phase version

Example:



PMRES-07.43A.2.bss-paris2.2004-06-

11.10:30:00.9999.111

PMRES110.43A.21.Essen1_H.2009-11-

15.03:31:24.634.227

GPRS Data: GPMRES<RR><yyy><mm>

Where

<RR> : ITFVERSION value always

coded on 2 digits.

<yyy> : identification of the MFS,

configured in the ServerFile file (handled by Q3 agent).

Always coded on 3 digits.

<mm> : index of the result file. Always

coded on 2 digits.

Note : GPMRES<RR><YYY><mm> is the official name of the file on the

Alcatel System. Gateway Configuration however will parse raw data as

long as the filename has the wording of “GPMRES” . Eg

Dec-08-GPMRES065042

Input file formats to expect GSM: The files are in Binary format.

The Performance Generic Header Record (_5-) is the

first record (record sequence number 0) of each

performance report file. It has the following counter

block layout.

B11 counter block layout



Where: System Record Header: number of bytes = 74

record sequence number = 00

record type = 12 (PGHR)

file type = 03 or 10 (GPMF or OMPF)

BSS Version: BSS-Phase-Version: BSS B11 must be taken into

account. For the BSS version values please refer to the last

edition of the “OMC-BSS MIB Specification B11” document ref

[3].

BSC Release BSC-Release: (34) for BSC B11

Managed Object Class: Measurement

Managed Object Instance: measurement-ID defined in

Measurement Object Class

File Creation: Time and date given in an ASCII format from tenth

of second to year

Measurement Type: Measurement-Type (ex (110) for

measurement type 110)

Total size: equal to (Record Size) * (Number of Records); Record

Size is

measurement type dependent (see to §3.2.1 to §3.2.34)

Number of Records: Integer

Begin Collection Time: Time and date given in an ASCII format

from tenth of second to year(STARTTIME)

End Collection Time: Time and date given in an ASCII format

from tenth of second to year(ENDTIME)

Sample Percentage: Sample-Rate (value 0 to 100 or 255)

Sample Rate Reduced: Boolean

False = Sample rate not reduced

True = Sample rate reduced during reporting period



B10 counter block layout

Where:

System Record Header: number of bytes = 74

record sequence number = 00

record type = 12 (PGHR)

file type = 03 or 10 (GPMF or OMPF)

BSS Version: BSS-Phase-Version: BSS B8 and BSS B9 must be

taken into account. For

the BSS version values please refer to the last edition of the

“OMC-BSS

MIB Specification B9” document ref [3].

BSC Release BSC-Release: (28) for BSC B8; (30) for BSC B9

Managed Object Class: Measurement

Managed Object Instance: measurement-ID defined in

Measurement Object Class

File Creation: Time and date given in an ASCII format from tenth



of second to year

Measurement Type: Measurement-Type (ex (110) for

measurement type 110)

Total size: equal to (Record Size) * (Number of Records); Record

Size is

measurement type dependent (see to §3.2.1 to §3.2.34)

Number of Records: Integer

Begin Collection Time: Time and date given in an ASCII format

from tenth of second to year

End Collection Time: Time and date given in an ASCII format

from tenth of second to year

Sample Percentage: Sample-Rate (value 0 to 100 or 255)

Sample Rate Reduced: Boolean

False = Sample rate not reduced

True = Sample rate reduced during reporting period

GPRS: The file format is the standardized file format that can

be directly manipulated by the loader. Counters are

grouped in some manner and tagged with the network

element to which they refer such as cell, PVC, etc.

Measurement Items (counters) are typically grouped

according to functionality. The term “measured object

class” is used to identify such a group. The file format is

based on the fact that the measurements are always

collected in sets of one functional group.

A PM file contains the sequence of measurements,

values and related information, in a block-oriented

structure.

It includes a list of measurement types and the

corresponding values, together with the date and time

stamp related to the reporting period, the MFS identifier,

the interface identifier.

The following figure gives the general file format. The

fixed part is exactly the same whatever is the PM

interface version.

The variable part is the list of possible blocks. The

presence of a block is not mandatory. It depends on the

configuration. The order of the blocks given in the

following figure is not necessarily the one in which they

are reported by the MFS. This sequence is given as an

example:



Equipment/devices to expect

data

N/A

Extraction mechanism N/A

Transfer mechanism N/A

5.2 Hierarchy input files

Alcatel provides one configuration file per OMC. This file contains all the configuration/topology of

the elements (e.g. BSC, CELL, TRX, LAPD) managed by this OMC.

These data are:

• the BSS configuration data, which describe all the objects available in the network,

• the BSS PM counters, which are the results of the monitoring of the network activity, this

interface is provided in two versions binary format from the BSC and ASCII post processing by

the OMC-R

• the MFS PM counters, which monitor GPRS network element activity,

• the IMSI trace and observations.

The BSS configuration files are stored in /alcatel/var/share/AFTR/ACME on OMC machine Files are

read using ftp.

Scope Attended Format/Syntax

Input files names to expect The name of the file is: “BSSConf”, the name of the

OMC-R, the date and time

(YYYYMMDDHHMMSS) of generation, each part

being separated by a dot (“.”) character.

Example : BSSConf.bourg.19970818091200

Input file formats to expect The file is made up of two parts:

1. A header containing the version and the OMC-R

name identifier.



In this part, the <carriage return> is used to end each

line.

VERSION

<version_value> :Value of the version, 3 digits (600 for

initial GetBSSConf version).

OMC_NAME

<OMC_name> :OMC-R name

DELTA_TIME

<delta_time_value> :Value of the timezone

(omc_local_time - GMT_time) in

minutes, 3 digits. A negative value is preceded with a

minus sign.

2. A body containing the following sections:

• BSC

• Cell

• BTS

• TRX

• TRXTS (TS object)

• N7SL (Signalling Link object)

• N7LS (Link Set object)

• N7 (Signalling Link Code)

• ADJACENCY

• AIC (A Channel object)

• X25

• LAPDA (LAPD object)

• The Abis topology sections (used by Laser

application)

• ABIS section

• ABIS_BTS section

# BSS configuration file generated 19970818091200

VERSION

600

#

OMC_NAME

Bourg

#

DELTA_TIME

001

#

START BSC_SECTION

# BSC_NUM, BSC_NAME,

BSC_MCC,BSC_MNC,MIB_VERSION, [...];



1, Bourg1, F82, 243, 82, [...];

END BSC_SECTION

START CELL_SECTION [...]

Equipment/devices to expect

data

N/A

Extraction mechanism N/A

Notes: Alcatel Hierarchy data file names contain a timestamp which will produce a unique PIF

filenames for every new interval hierarchy data,

Eg: CELL-#-OMC1-#-BSSConf.omcalc.20081110143500-hierarchy-#-I-#-S.pif

CELL-#-OMC1-#-BSSConf.omcalc.20081208110000-hierarchy-#-I-#-S.pif

User may need to housekeep the hierarchy data to keep only the latest hierarchy PIF in INTER

directory depend on the needs of user.

There are 4 other configuration files also produced by the OMC which are used to extract data for the

LIFs:

• MtpSignPoint.csv which contains BSC_NUM, BSC_NAME and MTP_SPC_Decimal

parameters,

• AlcatelSignLinkSetTp.csv which contains BSC_NUM/BSC_NAME to MSC relationship data,

• AlcatelBts_Sector.csv which is used to determine the Cell description and Cell type of a Cell,

• AlcatelBasebandTransceiver.csv which is used to determine the number of TRX under a Cell.

Each BSC has a set of the above 4 configuration files. The files can be found in the following

location /ACIE/ACIE_BLexport/ACIE_BSSxxexport_Dir1 on the OMC where xx is the internal BSC

number. Eg: if BSC-A has an internal BSC number of 15, then the location of the configuration files

should be /ACIE/ACIE_BLexport/ACIE_BSS15export_Dir1

There is a 5th

configuration file which must be produced by the customer:

• NSS_Nodes.csv which contains Node_ID, Node_Name and Node_Type information for BSC

data. In this case, the node is the MSC.



6 Configurations

6.1 Transfer Engine configuration

No transfer engine configuration required

6.2 Pre Parser Engine configuration

In Alcatel B10 and B11, there are 5 configuration files in CSV format that need to be parsed to

produce LIFs. These csv are AlcatelBasebandTransceiver.csv, AlcatelBts_Sector.csv,

AlcatelSignLinkSetTp.csv, MTPSignPoint.csv and NSS_Nodes.csv.

3 CSV files (MtpSignPoint.csv,AlcatelSignLinkSetTp.csv,NSS_Nodes.csv) has extra header line that

need to use PreparserEngine to manipulate and retrieve information from Line 1 and added to Line 2

(header block) and Line 3 (data block) of CSV. Line 1 will be skipped.

Eg : AlcatelSignLinkSetTp.csv before PreParser Line1:B10_INFO ACIE 8;2008-12-07;22:30:45;A1353RA_843eaa36;;KL_6;

Line2:Mode;AlcatelSignLinkSetTpInstanceIdentifier;AlarmStatus;CurrentProblemList;AdjPc;AdministrativeState;AlarmSeverityAssi

gnmentProfilePointer;AvailabilityStatus;CongestionControlMethod;CurrentCapacityLS;MaxCapacityLS;OperationalState;PeriodicLin

kTestFlag;UsageState;

Line3:E;2;cleared;{};1527;unlocked;;{};undefined;0;0;enabled;off;active;

6.3 Parser Engine configuration

The Parser Engine is configured to support the following:

� Support two different data types: GSM (Binary) and GPRS (LIF)

� REGION_ID and NETWORK_ID extraction from the directory structure for NA support

• In Alcatel B10 and B11, DIRECTORY_HEADER_FILES is used to get the OMC Name to

be included in the PIF filename

Eg: TYPE_9-#-4-#-OMC1-#-01Aug2007-#-16:00-#-01Aug2007-#-17:00-#-I.pif

Where OMC NAME is OMC1

Sample structure of INPUT_DIR - ../spool/input/NETWORK_ID/REGION_ID/OMC1

Note: When parsing B9 raw data with B9 Gateway Configuration, INPUT_DIR folder structure

remain the same, eg: ../spool/input/NETWORK_ID/REGION_ID



6.4 Post Parser user configuration

The following block post parsing rules are used:

Output Block Names Post Parsing Rules Applied

All GPRS blocks, TYPE_1,

TYPE_7, TYPE_9, TYPE_110,


SGSN_IP_NSVC

FILE_BLOCK_SPLIT: Split up all blocks to 1

block per LIF

TYPE_1110, TYPE_1120,

TYPE_1122, TYPE_1123,

TYPE_1125, TYPE_1130,

TYPE_1135, TYPE_1140,

TYPE_1143, TYPE_1144,

TYPE_1800, TYPE_1810

TYPE_110: Special handling for TYPE_110 and

TYPE_180 block split (refer to [Alcatel BSS User

Guide] for details)

TYPE_1810, TYPE_26, TYPE_27 PERLIZE: Get the MCC and MNC for block

types 1810, 26, 27

BSC and BTS configuration files,

TYPE_1(1|2), TYPE_11\d{2},

TYPE_18, TYPE_19,




TYPE_31\d{2}, TYPE_32,

TYPE_33, TYPE_340,

TYPE_341, TYPE_35\d{1},


TYPE_7(1|2), TYPE_8, TYPE_91,

TYPE_93

COPY_HEADER_N_BODY_COUNTERS:

Move counters from body to header for

NodeBFunction PIFs

BSC, BTS and CELL

configuration files

INFOINSERT: Merge BSC, BTS and CELL

configuration files

TYPE_11, TYPE_12,

TYPE_1110, TYPE_1120,

TYPE_1122, TYPE_1123,

TYPE_1130, TYPE_1810,


TYPE_261, TYPE_271,

TYPE_280, TYPE_290,


TYPE_341, TYPE_340,


TYPE_6

INFOINSERT: Enrich GSM blocks with cell

level information

TYPE_12_AGG, ACCUMULATION: Aggregate stats up to BS



TYPE_3110_AGG,

TYPE_3111_AGG,

TYPE_3112_AGG,

TYPE_3115_AGG,

TYPE_3116_AGG,

TYPE_3117_AGG,

TYPE_3118_AGG,

TYPE_3119_AGG,

TYPE_1130_AGG

level

TYPE_1135, TYPE_1140,

TYPE_1142, TYPE_1145,

TYPE_25, TYPE_30,

TYPE_35[3|4|8], TYPE_72,

TYPE_8, TYPE_91, TYPE_93

INFOINSERT: Enrich GSM blocks with BSC

level information

TYPE_355, TYPE_71 INFOINSERT: Enrich GSM blocks with BTS

level information

TYPE_1144 PERLIZE: Compute the NRI_NUM

TYPE_180, TYPE_181 FILE_SPLIT_BY_COUNTERS: Split TYPE_18

block to TYPE_180 and TYPE_181

BSC JOIN : Join block B30BSCCOM and

B31BSCTDM by counter BSS and FABRIC as

key

BSC, LapD, cell, DistCell INFOINSERT: Enrich GPRS blocks with BSC

level information

BTS INFOINSERT: Enrich GPRS blocks with BTS

level information

JOIN: Join block B10cellPMUCOM,

B11cellPMUTDM, B20cellPTUCOM, LcsCell,

B12cellPMUIP, B41CELLNACC by counter BSS

and FABRIC

cell

AGGREGATE_LINE: Aggregate complex CELL

counters

cell_agg, TYPE_1120_agg,

TYPE_355_AGG, BTS_AGG

ACCUMULATE: Aggregate stats up to BSC

level

pvc_agg ACCUMULATE & PIF_2_OUTPUT: Aggregate

pvc/dlci stats up to BearerChannel

TYPE_1130_CELL ACCUMULATE: Accumulate TRX level data in

TYPE_1130 into Cell level

TYPES_11X0 JOIN: Merging TYPE_1110, TYPE_1120 and



TYPE_1130_CELL and TYPE_1122 for VN

Bearer_pvc JOIN : Bearer_pvc and pvc_AGG for VN

6.5 Known Issues

CR Number: valnt00106637

Issue: Alcatel BSS 3.5.1.4 VG: Compressed raw data was not removed after being parsed thru the GW

Issue Description: This Gateway Configuration requires Vendor Gateway 3.5.1.4 as a minimum requirement. This

Vendor Gateway contains a limitation whereby the compressed raw data file was not removed after

being parsed thru the gateway.

Customer Impact: The raw data will be parsed twice resulting in redundant processing.

Workaround: To overcome the issue above, customer need to decompress the raw data file prior transfer it to the

input directory.



Appendix A Notices and Trademarks

This appendix contains the following:

• Notices

• Trademarks

Notices

IBM may not offer the products, services, or features discussed in this document in other countries. Consult

your local IBM representative for information on the products and services currently available in your area.

Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM

product, program, or service may be used. Any functionally equivalent product, program, or service that

does not infringe any IBM intellectual property right may be used instead. However, it is the user's

responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document.

The furnishing of this document does not grant you any license to these patents. You can send license

inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk NY 10504-1785

U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property

Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing

Legal and Intellectual Property Law

IBM Japan, Ltd.

1623-14, Shimotsuruma, Yamato-shi

Kanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions

are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION

PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER

EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some

states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this

statement may not apply to you.



This information could include technical inaccuracies or typographical errors. Changes are periodically

made to the information herein; these changes will be incorporated in new editions of the publication. IBM

may make improvements and/or changes in the product(s) and/or the program(s) described in this

publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in

any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the

materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without

incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the

exchange of information between independently created programs and other programs (including this one)

and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation

5300 Cork Airport Business Park

Kinsale Road

Cork

Ireland.

Such information may be available, subject to appropriate terms and conditions, including in some cases,

payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by

IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any

equivalent agreement between us.

Information concerning non-IBM products was obtained from the suppliers of those products, their

published announcements or other publicly available sources. IBM has not tested those products and cannot

confirm the accuracy of performance, compatibility or any other claims related to non-IBM products.

Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice,

and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them

as completely as possible, the examples include the names of individuals, companies, brands, and products.

All of these names are fictitious and any similarity to the names and addresses used by an actual business

enterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.



Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business

Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be

trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at

“Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel

SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its

subsidiaries in the United States and other countries.

Other company, product or service names may be trademarks or service marks of others.

IBM®

Printed in the Republic of Ireland.