apsp-pdf

8/8/2019 apsp-pdf

1/24

Tivoli Netcool/OMNIbus Probe for CA Aprisma Spectrum

Reference Guide

December 31, 2008

Version 6.0.5114

SC23-7847

8/8/2019 apsp-pdf

2/24

8/8/2019 apsp-pdf

3/24

Tivoli Netcool/OMNIbus Probe for CA Aprisma Spectrum

Reference Guide

December 31, 2008

Version 6.0.5114

SC23-7847

8/8/2019 apsp-pdf

4/24

NoteBefore using this information and the product it supports, read the information in Notices and Trademarks, on page 11.

Edition notice

This edition applies to version 6.0.5114 of IBM Tivoli Netcool/OMNIbus Probe for Aprisma Spectrum(SC23-7847-01) and to all subsequent releases and modifications until otherwise indicated in new editions.

This edition replaces SC23-7847-00.

Copyright International Business Machines Corporation 2006, 2008.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

8/8/2019 apsp-pdf

5/24

Contents

Document control page . . . . . . . . v

IBM Tivoli Netcool/OMNIbus Probe forAprisma Spectrum . . . . . . . . . . 1Summary . . . . . . . . . . . . . . . 1Installing the probe . . . . . . . . . . . . 2Internationalization support . . . . . . . . . 3

Example multi-byte character set on Solaris . . . 3Example multi-byte configuration on Windows . . 3

Data acquisition . . . . . . . . . . . . . 3Peer-to-peer failover functionality . . . . . . 4

Properties and command line options . . . . . . 5Elements. . . . . . . . . . . . . . . . 6

Elements generated for version 5 of AlarmNotifier 6Elements generated for version 6.x ofAlarmNotifier . . . . . . . . . . . . . 7

Error messages . . . . . . . . . . . . . 8

Appendix. Notices and Trademarks . . 11Notices . . . . . . . . . . . . . . . . 11Trademarks . . . . . . . . . . . . . . 13

Copyright IBM Corp. 2006, 2008 iii

8/8/2019 apsp-pdf

6/24

iv Netcool/OMNIbus Probe for CA Aprisma Spectrum: Reference Guide

8/8/2019 apsp-pdf

7/24

Document control page

Use this information to track changes between versions of this guide.

The IBM Tivoli Netcool/OMNIbus Probe for Aprisma Spectrum documentation isprovided in softcopy format only. To obtain the most recent version, visit the IBM

Tivoli Information Center:

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.tivoli.nam.doc/welcome_ptsm.htm

Table 1. Document modification history

Documentversion

Publicationdate

Comments

01 December 31,2008

Summary table updated.

IPv6 support information added.

FIPS information added.

Installation section added.

Copyright IBM Corp. 2006, 2008 v
http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.tivoli.nam.doc/welcome_ptsm.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.tivoli.nam.doc/welcome_ptsm.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.tivoli.nam.doc/welcome_ptsm.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.tivoli.nam.doc/welcome_ptsm.htm

8/8/2019 apsp-pdf

8/24

vi Netcool/OMNIbus Probe for CA Aprisma Spectrum: Reference Guide

8/8/2019 apsp-pdf

9/24

IBM Tivoli Netcool/OMNIbus Probe for Aprisma Spectrum

The CA Aprisma is a network management platform. The system is an elementmanager for CA Aprisma devices and can also manage third party devices through

specific management modules.

The two core components of Spectrum Enterprise Manager are the SpectroGRAPHand the SpectroSERVER. The SpectroGRAPH is a graphical user interface thatoffers client access to the SpectroSERVER. The SpectroSERVER is a networkmanagement server that the probe collects alarm information from.

This guide contains the following sections:

v Summary

v Installing the probe on page 2

v Data acquisition on page 3

v Properties and command line options on page 5

v Elements on page 6

v Error messages on page 8

Summary

Each probe works in a different way to acquire event data from its source, andtherefore has specific features, default values, and changeable properties. Use thissummary information to learn about this probe.

The following table provides a summary of the Probe for Aprisma Spectrum.

Table 2. Summary

Probe target Aprisma Spectrum

Probe executable name nco_p_spectrum

Patch number 6.0

Probe supported on Solaris, AIX, HP-UX, Linux, Windows

For details of the operating system versions on whichthis probe is supported, see the following page on theIBM Tivoli Netcool Information Center:

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/Supported_Platforms.htm

Properties file $OMNIHOME/probes/arch/spectrum.props

%OMNIHOME%\probes\arch\spectrum.props

Rules file $OMNIHOME/probes/arch/spectrum.rules

%OMNIHOME%\probes\arch\spectrum.rules

Requirements A currently supported version of IBM TivoliNetcool/OMNIbus

probe-compatibility-3.x (for IBM TivoliNetcool/OMNIbus version 3.6)

Copyright IBM Corp. 2006, 2008 1
http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/Supported_Platforms.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/Supported_Platforms.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/Supported_Platforms.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/Supported_Platforms.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/Supported_Platforms.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/Supported_Platforms.htm

8/8/2019 apsp-pdf

10/24

Table 2. Summary (continued)

Connection method Executes Spectrums AlarmNotifier program

Remote connectivity Not applicable

Licensing Electronic licensing was deprecated with the release ofIBM Tivoli Netcool V7.2. All IBM Tivoli Netcool V7.2(and later) products use the IBM software licensing

process.Internationalization Available

Note: The probe only supports internationalization onIBM Tivoli Netcool/OMNIbus V7.0, 7.1, 7.2, and 7.2.1.

Peer-to-peer failover functionality Available

IP environment IPv4 and IPv6Note: The probe is supported on IPv6 when runningon IBM Tivoli Netcool/OMNIbus V7.0, 7.1, 7.2 and 7.2.1on Solaris, and on IBM Tivoli Netcool/OMNIbus V7.2and 7.2.1 on all other UNIX plaftorms. The probe issupported on IPv6 when running on IBM TivoliNetcool/OMNIbus V7.2.1 on Windows plaftorms.

Federal Information ProtocolStandards (FIPS) IBM Tivoli Netcool/OMNIbus V7.2.1 uses the FIPS140-2 approved cryptographic provider: IBM Crypto forC (ICC) certificate 384 for cryptography. This certificateis listed on the NIST web site at http://csrc.nist.gov/cryptval/140-1/1401val2004.htm For details aboutconfiguring Netcool/OMNIbus for FIPS 140-2 mode, seeIBM Tivoli Netcool/OMNIbus Installation and DeploymentGuide (SC23-6370).

Installing the probe

All probes follow a very similar installation procedure.

Installing the probe on UNIX platforms

To install the Probe for Aprisma Spectrum on UNIX platforms, run the followingcommand:

$OMNIHOME/install/nco_patch -install patch

Where patch is the file name of the patch that you have downloaded.

Installing the probe on Windows platforms

To install the Probe for Aprisma Spectrum on Windows platforms, use thefollowing steps:

1. Unzip the probe_zip_file file into a temporary location. (Where probe_zip_file isthe file name of the zip file that you downloaded.)

2. Copy the binary (and .dll if present) into your probe binary directory.

3. Copy the default .props and .rules into your probe binary directory if required.

To install the Probe for Aprisma Spectrum as a Windows service, use the followingsteps:

1. Register the probe with the Service Control Manager by running the followingcommand:

probe_name.exe -install

2 Netcool/OMNIbus Probe for CA Aprisma Spectrum: Reference Guide
http://csrc.nist.gov/cryptval/140-1/1401val2004.htmhttp://csrc.nist.gov/cryptval/140-1/1401val2004.htmhttp://csrc.nist.gov/cryptval/140-1/1401val2004.htmhttp://csrc.nist.gov/cryptval/140-1/1401val2004.htm

8/8/2019 apsp-pdf

11/24

(Where probe_name is the name of the executable in the zip file.)

2. If you are running the probe on the same machine as the ObjectServer, run thefollowing command line to register the dependency of the probe on theObjectServer service:

probe_name.exe -install -depend NCOObjectServer

3. Activate the probe by selecting Control Panel Services.

Internationalization support

The probe supports multibyte character sets. To view the character sets correctly,you must configure the locale settings on the host machine correctly. Eachmultibyte character set is configured slightly differently on each platform.

Example multi-byte character set on Solaris

The following steps describe how to configure Solaris to use the Japanese characterset:

1. Install the necessary components for Japanese on to the host machine using the

Solaris CD.2. Set the LANG and LC_ALL environment variables to ja_JP PCK. This uses SJIS

encoding.

Note: You may have to set the LANG in the host machines default settings fileand reboot it to make the changes take effect.

3. Make sure that the file $OMNIHOME/platform/arch/locales/locales.dat hasthe following entry:

locale = ja_JP PCK, japanese, sjis

where ja_JP PCK is the vendor locale, japanese is the Sybase language, andsjis is the Sybase character set.

Example multi-byte configuration on Windows

The following steps describe how to configure Windows to use the Japanesecharacter set:

1. Install the necessary language pack using the Control Panel.

Note: You must reboot the machine to make the character set available.

2. Make sure the file,%OMNIHOME%\locales\locales.dat, has the followingelement:

locale = jpn, japanese, sjis

where jpn is the vendor locale, japanese is the Sybase language, and sjis isthe Sybase character set

Note: You must reboot the machine to be able to use the probe as a service in therequired locale.

Data acquisition

Each probe uses a different method to acquire data. Which method the probe usesdepends on the target system from which it receives data.

IBM Tivoli Netcool/OMNIbus Probe for Aprisma Spectrum 3

8/8/2019 apsp-pdf

12/24

The Probe for Aprisma Spectrum launches the AlarmNotifier program as asub-process, acquires events generated by the program, and forwards them to theObjectServer. For example, to run the probe from the command line, you couldenter:

nco_p_spectrum -exec "AlarmNotifier -r .alarmrc"

In this example, when the probe is run, it runs the AlarmNotifier program and

uses a SPECTRUM configuration file .alarmrc. The AlarmNotifier program readsand outputs SPECTRUM events from the database.

The probe reads the output from the AlarmNotifier program, parses each eventinto a Netcool/ OMNIbus alert and forwards it to the ObjectServer.

Note: There are different elements, properties, and command line options,depending on the version of AlarmNotifier running.

Peer-to-peer failover functionalityThe probe supports failover configurations where two probes run simultaneously.One probe acts as the master probe, sending events to the ObjectServer; the other

acts as the slave probe on standby. If the master probe fails, the slave probeactivates.

While the slave probe receives heartbeats from the master probe, it does notforward events to the ObjectServer. If the master shuts down, the slave probe stopsreceiving heartbeats from the master and any events it receives thereafter areforwarded to the ObjectServer on behalf of the master probe. When the master isrunning again, the slave continues to receive events, but no longer sends them tothe ObjectServer.

Example property file settings for peer-to-peer failover

You set the peer-to-peer failover mode in the properties files of the master and

slave probes. The settings differ for a master probe and slave probe.

The following example shows the peer-to-peer settings from the properties file of amaster probe:

Server : "NCOMS"RulesFile : "master_rules_file"MessageLog : "master_log_file"PeerHost : "slave_hostname"PeerPort : 5555 # [communication port between master and slave probes]Mode : "master"

The following example shows the peer-to-peer settings from the properties file ofthe corresponding slave probe:

Server : "NCOMS"RulesFile : "slave_rules_file"MessageLog : "slave_log_file"PeerHost : "master_hostname"PeerPort : 5555 # [communication port between master and slave probes]Mode : "slave"

Note: The properties file also contains all other properties required to configurethe probe.


8/8/2019 apsp-pdf

13/24

Properties and command line options

You use properties to specify how the probe interacts with the device. You canoverride the default values by using the properties file or the command lineoptions.

The following tables describe the properties and command line options specific to

this probe. For information about default properties and command line options, seethe IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide, (SC23-6373).

Properties and command line options for version 5 ofAlarmNotifier

The following table describes the properties and command line options for version5 of AlarmNotifier.

Table 3. Properties and command line options for version 5 of AlarmNotifier

Property name Command line option Description

EventHeaderPattern string -headerpattern string Use this property to specify aregular expression pattern thatmatches the header in theSPECTRUM event message.

The default is AlarmNotification.*

ExecCommand string -exec string Use this property to specify thecommand to be executed by theprobe to allow it to acquire datafrom SPECTRUM. This must beset.

The default is/usr/Spectrum/Notifier/AlarmNotifier-r

/usr/Spectrum/Notifier/.alarmrcLastRecordPattern string -lastrecordpattern string Use this property to specify a

regular expression pattern thatmatches the last record in theSPECTRUM event message.

The default is UserClearable.*

RecordSeparator string -separator string Use this property to specify therecord attribute/value delimiter.

The default is :.

TimeFormat string -timeformat string Use this property to specify thetime and date format.

The default is %m/%d/%y%H:%M%S.

Properties and command line options for version 6.x ofAlarmNotifier

The following table describes the properties and command line options for version6.x of AlarmNotifier.


8/8/2019 apsp-pdf

14/24

Table 4. Properties and command line options for version 6.x of AlarmNotifier

Property name Command line option Description

EventHeaderPattern string -headerpattern string Use this property to specify aregular expression pattern thatmatches the head in theSPECTRUM event message.

The default is Alarm Notificationfrom SPECTRUM.

LastRecordPattern string -lastrecordpattern string Use this property to specify aregular expression pattern thatmatches the last record in theSPECTRUM event message.

The default is EventMessage.

Elements

The probe breaks event data down into tokens and parses them into elements.

Elements are used to assign values to ObjectServer fields; the field values containthe event details in a form that the ObjectServer understands.

This section describes the elements that the Probe for CA Aprisma Spectrumgenerates.

Elements generated for version 5 of AlarmNotifier

This section describes the elements that the Probe for Aprisma Spectrum generatesfor version 5 of AlarmNotifier.

Static alarms

The following table describes the static elements that the probe generates.

Table 5. Static alarm elements for version 5 of AlarmNotifier

Element name Description

$Alarm This element contains the event type, which can be either SET orCLEARed.

$Datestring This element contains a string representing the time.

$UTC This element contains the universal time in seconds.

$Date This element contains the date of the event in mm/dd/yy format.

$Time This element contains the time of the event in hh:mm format.

$Mtype This element contains the model type.$ModelName This element contains the model name.

$AlarmID This element contains the identification number of event.

$Condition This element contains the spectrum severity code.

$CauseCode This element contains the code for identifying the cause of theevent.

$RepairPerson This element contains the name of engineer.

$AlarmStatus This element contains the status of event.


8/8/2019 apsp-pdf

15/24

Dynamic alarms

The following table describes the dynamic elements that the probe generates.

Table 6. Dynamic alarm elements for version 5 of AlarmNotifier


$elementname This element contains any fields that are added to the events from

Spectrum are created as elements by the probe.

Elements generated for version 6.x of AlarmNotifier

This section describes the elements that the Probe for Aprisma Spectrum generatesfor Version 6.x of AlarmNotifier, running with or without SANM Output.

The following table describes the elements that the probe generates with orwithout SANM Output.

Table 7. Elements for version 6.x of AlarmNotifier

Element name Description$Acknowledged This element indicates if the alarm has been acknowledged by a

Spectrum operator.

$Alarm This element contains the event type, which can be either SET orCLEARed.

$AlarmAge This element contains the age of the alarm, in minutes.

$AlarmID This element contains the identification number of event.

$AlarmState This element indicates if this is a new or existing alarm.

$AlarmStatus This element contains the status of event.

$Date This element contains the date of the event in mm/dd/yy format.

$Datestring This element contains the string representing the time.

$EventMessage This element contains the contains all the information that theevent is derived from.

$IPAddress This element contains the IP address of the model.

$Landscape This element contains the landscape identifier for the Spectrumserver. This is a hexadecimal number that uniquely identifies aSpectrum database.

$Location This element contains the location of the model.

$ModelHandle This element contains the hexadecimal number that uniquelyidentifies a model in the Spectrum database.

$ModelName This element contains the model name.

$ModelTypeHandler This element contains the hexadecimal number that uniquelyidentifies a model type in the Spectrum database.

$Mtype This element contains the model type.

$NotificationData This element contains a list of SPECTRUM users who would benotified of the alarm.

$ProbableCause This element contains the text indicating the probable cause of thealarm.


8/8/2019 apsp-pdf

16/24

Table 7. Elements for version 6.x of AlarmNotifier (continued)


$ProbableCause1,$ProbableCause2,$ProbableCausen

This element is generated from the text in the $ProbableCauseelement field. The number of elements generated will be shown bythe incremental number at the end of the ProbableCause elementname.

$ProbableCauseID This element contains the code for identifying the cause of theevent.

$RecommendedAction This element contains text indicating the recommended action.

$RecommendedAction1,$RecommendedAction2,$RecommendedActionn

This element is generated from the text in the $ProbableCauseelement field. The number of elements generated will be shown bythe incremental number at the end of the ProbableCause elementname.

$RepairPerson This element contains the name of person for repair.

$SecurityString This element contains the Spectrum security string for the model.

$Severity This element contains the Spectrum severity code.

$SpectroSERVER This element contains the host name of the Spectrum server.

$Symptom This element is generated from the text in the $ProbableCauseelement field.

$Time This element contains the time of the event in hh:mm format.

$UserClearable This element indicates if the alarm can be cleared by a Spectrumuser.

$UTC This element contains the universal time in seconds.

Note: If the Symptom element is not located (for the AlarmNotifier running withSANM Output), the probe reads any free flowing text (that is, containing morethan one line, ending in a new line character) until EventMessage is found. If theEventMessage also contains free flowing text, the probe accumulates this until the

end of the event is found.

Error messages

Error messages provide information about problems that occur while running theprobe. You can use the information that they contain to resolve such problems.

The following table describes the error messages specific to this probe. Forinformation about generic error messages, see the IBM Tivoli Netcool/OMNIbusProbe and Gateway Guide, (SC23-6373).

Table 8. Error messages

Error Description Action

Disconnected fromassociated process

The probe hasdisconnected from theassociated process.

Refer to your support contract formore information about contactingIBM Support.

Execd command The probe was unable toissue the Spectrumcommand.

Check that the ExecCommandproperty has been set correctly.

Failed to realloc()record separator

Failed to allocate memoryfor RecordSeparator.

Check RecordSeperator property.


8/8/2019 apsp-pdf

17/24

Table 8. Error messages (continued)

Error Description Action

Regcmp Failed for blankline

Regcmp Failed forheader

Regcmp Failed forlast_record

Internal error causedwhen compiling a regularexpression.

Check that the LastRecordPatternand EventHeaderPatternproperties have been set correctly.


8/8/2019 apsp-pdf

18/24


8/8/2019 apsp-pdf

19/24

Appendix. Notices and Trademarks

This appendix contains the following sections:

v Notices

v Trademarks

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, 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 users responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing 2-31 Roppongi 3-chome, Minato-kuTokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Copyright IBM Corp. 2006, 2008 11

8/8/2019 apsp-pdf

20/24

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct 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 itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM CorporationSoftware Interoperability Coordinator, Department 49XA3605 Highway 52 NRochester, MN 55901U.S.A.

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 information and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreement

between us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have been

estimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBMs future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBMs suggested retail prices, are current and are subjectto change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.


8/8/2019 apsp-pdf

21/24

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operating

platform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

(your company name) (year). Portions of this code are derived from IBM Corp.Sample Programs. Copyright IBM Corp. _enter the year or years_. All rightsreserved.

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

Trademarks

IBM, the IBM logo, ibm.com, AIX, Tivoli, zSeries, and Netcool are trademarks ofInternational Business Machines Corporation in the United States, other countries,or both.

Adobe, Acrobat, Portable Document Format (PDF), PostScript, and all Adobe-basedtrademarks are either registered trademarks or trademarks of Adobe SystemsIncorporated in the United States, other countries, or both.

Intel, Intel Inside (logos), MMX, and Pentium are trademarks of Intel Corporation

in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in theUnited States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

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

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

Appendix. Notices and Trademarks 13

8/8/2019 apsp-pdf

22/24


8/8/2019 apsp-pdf

23/24

8/8/2019 apsp-pdf

24/24

Printed in USA

SC23-7847-01

Documents

apsp-pdf