View
219
Download
1
Category
Preview:
Citation preview
Introducing IBM z/OS Connect Enterprise Edition V2.0
Madhu B Ananthapadmanabh (madhu.b.a@in.ibm.com)
Sreejith Nalamvathukkal (sreejith.n@in.ibm.com)
Digital Economy
Enterprises must learn to “Innovate like a Startup”
……TO
FROM……..“The ‘Uber syndrome’
– where a competitor
with a completely
different business
model enters your
industry and flattens
you.” Judy Lemke, CIO,
Schneider, United States
“52% of the Fortune 500 firms since 2000 are gone.” – R. Ray Wang http://blog.softwareinsider.org/2014/02/18/research-summary-sneak-peaks-from-constellations-futurist-framework-and-
2014-outlook-on-digital-disruption/
© 2016 IBM Corporation3
Consider Disruption in the Banking Industry
Non-bank entrants
New banks
New payment models
New lending models
New depository
Challenge: Disruptive forces are impacting banking industry dramatically
Opportunity: New ways to partner to create new value chains
Digital disruption fueled by APIs blurring traditional industry lines
© 2016 IBM Corporation4
What do the Following Have in Common?
Coffee company goes
digital, builds $1.6B
payments business, drives
21% of transactions
Car company offers
connected car, improves
driving experience, sells
vehicle data to partners
Bank spurs innovation by
offering hackathons,
integrates rewards program
with retailer partners
New Opportunities enabled by APIs
© 2016 IBM Corporation5
An Example of Innovative Application in Banking
– Mobile Wallet
APIMobile
Opportunity:• Improve consumer experience
• Convenience, Availability,
Usability
• Increased loyalty
• Customer retention
• New customers
• New Mobile Commerce channel
Solution:• Mobile App that will allow you to pay
• Credit / Debit card options
• Use for online shopping
• Use for in-store (NFC/QR code)
• Partner with retailer for special
discounts
$720 billion a year mobile payments by 2017 - Gartner estimate
6© 2016 IBM Corporation
Most Common scenario around APIs
Two Key Requirements for Enabling Digital Transformations
Must be agile in responding to marketplace needs and competitiono Solutions must be developed and deployed quickly, and are likely to be taken down just as quickly when replacing
with newer solutions
o An added requirement for enabling this multi-channel (for example, Mobile) digital presence can be a flexible deployment of this solution that is based on changing demand and available resources; for example, cloud-based solutions All enabled by APIs – exposing (Interaction) APIs for customer facing Mobile and IOT apps, and composing new applications accessing other APIs
(including Systems APIs)
Leverage core competency supported by mainframe assetso SOR Assets are built with a lot of due diligence and over a long period of time
Maintained by transactional systems (Create, Retrieve, Update and Delete) with important qualities of service (Reliable, Scalable, Secure, …)
Accessed by all core business processes, e.g., on-boarding a new customer or partner, introducing a new product, updating customer or product information, looking
up information, etc.
Data quality is maintained with a lot of due diligence in data validation
o New digital presence applications (exposed as interactive APIs) need easy access to SOR data Ease of development of System APIs can provide easy and timely access to SOR data
Related Blog entries: "Changing Industry Landscape with Digital Transformation" and "Digital Transformation with Mainframe Assets"
Interaction & System APIs: Digital Transformation through Multi-Speed IT
Interaction APIs: Invoke one or more System API’s or data sources,
and manipulate the returned data with new logic
Promote reuse across new applications
System APIs: APIs to Retrieve (as well as, Create, Update and
Delete) data from a system of record
App
ESB
System
API
Web
Service
System
API
TH GSINwww
Interaction API
System
API
Speed & Agility
Integration & Scale
Core
Enterprise
Digital
Ecosystem
Fast
Speed
Steady
Speed
Bridging to SOR: Enabling easy access
with System APIs
© 2016 IBM Corporation9
A Hybrid Cloud Architecture for Digital Transformation
Bluemix, API Connect, z/OS Connect EE for modern hybrid Enterprise applications
CICS
IMS
WebSphere
DB2
CICS, IMS, DB2,
WebSphere
IBM z/OS Connect EE
Create & run SoR (System)
APIs
IBM API Connect
Create, run, manage & secure
Enterprise APIs & Micro services
IBM Bluemix, zLinux/LinuxONE
Compose deploy & integrate
applications, services
IBM Mobile First
Tight IntegrationAll components located on
mainframe, and linkages are tightly
coupled
Service
OrientedLoose coupling using network-
based protocols such as
SOAP/WSDL
Web AccessScreen-scraping of 3270
applications
MessagingUsing technologies such as
IBM MQ
API EconomyIntegration based on a set
of well-understood and
easily-accessible APIs,
increasingly based on
REST/JSON patterns
These earlier patterns are still in
use and in many cases are the
best pattern for the application.
Just because they came earlier,
does not mean they are now
obsolete.
Evolution of Mainframe Integration Patterns
So how do we expose z data and services as APIs?
?
Can we do this today?
CTG or CICS SOAP/JSON
Webservices
IMS Mobile Feature Pack
DB2 JSON
CICS
IMS
DB2
MQ
WASJAX RS
Broker
Can we do this today?
CTG or CICS SOAP/JSON
Webservices
IMS Mobile Feature Pack
DB2 JSON
CICS
IMS
DB2
MQ
WASJAX RS
Broker
Completely different
configuration and management
Can we do this today?
CTG or CICS SOAP/JSON
Webservices
IMS Mobile Feature Pack
DB2 JSON
CICS
IMS
DB2
MQ
WASJAX RS
Broker
Completely different
configuration and management
Multiple endpoints for developers
to call/maintain access to
Can we do this today?
CTG or CICS SOAP/JSON
Webservices
IMS Mobile Feature Pack
DB2 JSON
CICS
IMS
DB2
MQ
WASJAX RS
Broker
Completely different
configuration and management
These are typically not RESTful!!!
Multiple endpoints for developers
to call/maintain access to
POST /accounts/create + (JSON with account create information)
POST /accounts/balance + (JSON with account number)
POST /accounts/update + (JSON with account number and deposit)
A collection of individual services
REST interface is very limited, HTTP method is NOT significant.
“Good enough” for some use-cases, but falls short the expectations of REST API consumers.
A naturally RESTful API
/accounts?name=Fred + (JSON with Fred’s information)
/accounts?number=1234
/accounts?number=1234 + (JSON with dollar amount of deposit)
/accounts?number=1234
HTTP verb conveys the operation
against the resources; i.e., POST is
for create, GET is for balance, etc.
URI conveys the resource to
be operated upon; i.e., Fred’s
account with number 1234
The HTTP body encoded in JSON
carries the specific data resulting from the
action (verb) against the resource (URI)
Aligned with API consumer expectations for REST APIs
What’s in a URI ? JSON-RPC style services vs. a “naturally RESTful” API
POST
GET
PUT
DELETE
16
You need an API transformation gateway!
RESTful APIs available from
one endpoint
CICS
IMS
DB2
MQ
WAS
With sophisticated mapping
of true RESTful APIs to
existing mainframe services
and data
CICS
IMS
WAS
MQ1
DB21
REST APIconsumers
z/OS
Create and deliver natural REST APIs for z Systems assets in a unified manner across z/OS subsystems with integrated auditing, security and scalability
API Management
Mobile apps
Web apps
1 see ENUS215-493 Statements of Direction
IBM z/OS Connect Enterprise Edition
Business partner applications
Internal applications
18
Liberty z/OS
z/OS Connect EE
server instance
SoR subsystems
CICS, IMS, WAS,
DB2, MQ, …
IBM 64-bit SDK for z/OS,
Java Technology Edition
V7.1.0 or V8.0.0
z/OS Explorer Aqua V3.0
z/OS Connect EE
API Editor
Windows, Linux or OS/X with
• IBM CICS Explorer V5.3
• IBM IMS Explorer for Development V3.2
• IBM Explorer for z/OS Aqua V3.0
Runtime Server•Includes service capabilities of V1.0
•Adds the ability to hosts APIs
•Integrates with multiple z subsystems
•Liberty + z/OS Connect = “instance”
•You may have multiple instances
Tooling Platform• Integrates with an Eclipse 4.4 environments
• Defines APIs and generates SWAGGER 2.0
• Compose API mapping models
• Deploy APIs to runtime server
• Export API archive for other tools to deploy
1
2
IBM z/OS Connect Enterprise EditionTwo parts to every story
19
Liberty
z/OS
z/OS
Connect EE
V2.0 Server
Backend
Systems(CICS, IMS, DB,
etc.)
• IBM z/OS 2.1 or
higher
• IBM 64-bit SDK for
z/OS, Java
Technology Edition
V7.1.0 or V8.0.0
Eclipse
z/OS
Connect EE
2.0 Tooling
• IBM CICS Explorer V5.3
• IBM IMS Explorer for Development
V3.2
• IBM Explorer for z/OS Aqua V3.0
For connectivity to backend systems:
• CICS -- CICS TS 4.1 or higherThis is based on the minimum level for the WebSphere Optimized Local Adapter (WOLA) support. For
WOLA and Liberty, the minimum CICS TS level is 4.1.
• IMS -- IMS 12.1 or IMS 13.1See IMS Mobile Feature Pack component of IBM IMS Enterprise Suite for z/OS, V3.1.1 announcement letter
214-220, which details the software requirements. The z/OS Connect EE V2.0 requirements for IMS are the
same as are outlined in that announcement letter.
Hardware and Software Prerequisites
21
z/OS Connect dedicated Liberty
z/OS Connect product
feature V2.0
service providerfeatures
WOLA
API composition tooling for Eclipse
RESTclient
API deployment scriptable interface
WOLA service provider
REST client service provider
Angel The Liberty angel runtime is
included with z/OS Connect EEProvides authorized services
Create API packages
and iteratively deploy
for testing
Automate deployment
of API packages with
target-specific
customizations
SMF89
registration &
usage records
Extra SPs
CICS, MQ, DB2 plan to ship
further service provider
implementations for deployment
with z/OS Connect EE
IMS Enterprise Suite 3.2.1
includes IMS Mobile Feature
Pack for z/OS Connect
Enterprise Edition
IBM z/OS Connect Enterprise EditionRuntime component view – extending z/OS Connect EE
z/OS Connect EE API EditorAPI composition
Eclipse Tools for Mainframe DevelopmentComposite update site hosts compatible versions of Eclipse platforms & plugins
23
https://developer.ibm.com/mainframe
Release train delivering
compatible versions of
Eclipse platforms & plugins
for IBM tooling on z/OS.
https://developer.ibm.com/mainframe
z/OS Connect EE API EditorCreate the paths and methods supported by your REST API
24
service to invoke for this path and
method
unique mappings of the service for this path and method
Service archive
SoR-specific
utilities
containing e.g.
CICS WSBind,
IMS meta-data
Import SAR files to z/OS Connect EE API Editor
SoR-specific utilities for SAR generation
IMS Explorer for Development (shown)•IMS Transaction data xforms
BAQJS2LS / BAQLS2JS utilities (supplied)•CICS program data xforms
Ready for API composition….
z/OS Connect EE API EditorComposing an API from service archives
25
z/OS Connect EE API EditorAPI composition: start with service archives
26
z/OS Connect EE API EditorCreate unique RESTful mappings of z/OS Connect services per path and method
27
Map HTTP headers, query parameters,
and path parameters, to the service.
Map static values to fields
API archive includes generated SWAGGER 2.0
Upload the API archive to zFS and deploy using the apideploy command
z/OS Connect EE API EditorAPI composition: export API package as API archive (AAR)
28
z/OS Connect EE API EditorAPI composition: Generated SWAGGER (shown in SWAGGER editor)
29
IBM z/OS Connect Enterprise EditionAPI consumers, API packages, mapping and transformation, description, discovery and invocation!
Consumer view z/OS Connect EE V2 SoR
z-asset APOST
z-asset BGET
z-asset CPUT
z-asset DDELETE
API package
Create-service
Read-service
Update-service
Delete-service
/myapi/resource/{id}
HTTP
Headers
+
JSON AP
I m
ap
pin
g
mo
de
l
Discover APIswith SWAGGER
description
Consumers can use SWAGGERto generate API client code
Service archive SoR-specific
utilities
containing
e.g. CICS
WSBind, IMS
meta-data
Export API
z/OS Connect EE API editor
JSON /
SoR
xforms
(.sar)
(.aar)
Import
30
CICS Catalog Manager: sample API mapping model
VSAM File (EXMPCAT)
CICS
Inquire item
Place Order
z/OS Connect EE V2.0
https/json
DFH0XCMNGET or POST
Inquire
Catalog
GET /items?startItemIDGET /items/{itemID}POST /orders
Services
catalog API
inquireCataloginquireSingleplaceOrder
Designing an API for the CICS Catalog sampleA sample API mapping model
31
DFH0XCP3
Inquire Catalog
DFH0XCP4
Inquire Single
DFH0XCP5
Place Order
DFH0XCMN
CICS Programs
Service for Inquire Catalog
serviceName="inquireCatalog"
Service for Inquire Single
serviceName="inquireSingle"
Service for Place Order
serviceName="placeOrder"
WOLA Information
registerName="CICSREG"
serviceName="DFH0XCMN"
Data transformation information
zosConnectDataXform
GET/items?startItemID=<value>
GET/items/{itemID}
POST/orders
z/OS Connect EE V2.0
API Definitionz/OS Connect EE V2.0
Service Definitions 1
2
3
5
4
6
The API is generated using the z/OS Connect EE V2.0 API Editor in Eclipse
1. CICS program named in WOLA serviceName
2. CICS copybooks used to create data transformation WSBIND files (JSON to
COMMAREA)
3. Service definitions
4. CICS region named in WOLA registerName
5. WOLA DataXform specifies location of WSBIND files
6. API we want to construct with the API
Editor
Designing an APIA sample API mapping built from CICS catalog sample services
32
API ManagementSecure, scale, manage, monitor, and socialize APIs
API Management
• APIs hosted on a zEE server are not “managed”, therefore an API
management (APIm) solution should be used.
• IBM APIm enhances zEE APIs with the following capabilities:
– Secure and scale• manage access to APIs by using API keys and secret keys.
– Manage and monitor• extract API usage and analytics data to quickly react to new opportunities.
– Administration portal• self-registration, quotas, key management and security policies.
– Developer portal• engage application developers and foster use of published APIs.
• customize with branding to advertise, market, socialize and sell APIs.
34
35
A zEE API can be imported into APIm by referencing its
Swagger definition that is hosted on the zEE server.
36
Provide the location of the Swagger definition
on the zEE server.
37
The Swagger definition is parsed and shown
for confirmation.
38
The zEE API is now imported into APIm
and can be managed.
How do I get started?
39
EZSource provides unique application discovery capabilities to reduce
the risk and cost of digital transformation
• Accelerate digital modernization efforts by analyzing business-critical applications– Identify API candidates and embrace micro services architecture
– Identify code quality concerns, including dead code, to improve reliability and maintainability
• Mitigate risk of change through understanding code, data and schedule interdependencies– Aid in the sizing of a change effort
– Automate documentation to improve understanding
– Reduce learning curve as new people are on boarded
• Work smarter through Cognitive DevOps– Add application understanding to DevOps lifecycle information to
identify opportunities for work optimization * Based on EZSource client surveys 2013-15
EZSource Estimated Productivity Improvements* Application Design 26% Application Development/Maintenance 33% Testing/QA 27% Application Support 18%
http://www.ibm.com/press/us/en/pressrelease/49810.wss
IBM apiconnect
on prem
IBM apiconnect
z/OS Connect
Enterprise Edition
All set - Get connected!
z/OS Connect EE pricingInstance based pricing model
43
z/OS Connect EE introduces an innovative new pricing model
on z Systems.
“per instance” pricing metric
•Based upon the maximum number of active concurrent
address spaces
•Tiered usage bands
•provides increasing value as the size of an overall
deployment rises; low cost of entry for small projects
•Auditing is required through SMF89-2 records
•hourly snapshots of the number of concurrent instances,
reports created with utility IFAURP
What about pricing?A new approach
44
Number of
Simultaneous Instances
VUs per Simultaneous Instance
1 to 4 1 VU per Simultaneous Instance
5 to 10 4 VUs + 0.6660 VUs per Simultaneous Instance > 4
11 to 20 8 VUs + 0.4000 VUs per Simultaneous Instance > 10
21 to 40 12 VUs + 0.2000 VUs per Simultaneous Instance > 20
41 to 100 16 VUs + 0.0660 VUs per Simultaneous Instance > 40
101 to 250 20 VUs + 0.0260 VUs per Simultaneous Instance > 100
251 to 500 24 VUs + 0.0160 VUs per Simultaneous Instance > 250
501 to 1000 28 VUs + 0.0080 VUs per Simultaneous Instance > 500
1001 to 3000 32 VUs + 0.0020 VUs per Simultaneous Instance > 1000
>3000 36 VUs + 0.0007 VUs per Simultaneous Instance > 3000
What about pricing?Value Unit exhibit VUE037 (see announcement letter ENUS215-493)
Summary
Evolution of z Asset Integration Capability
Messaging or EAI (MQ)
Enterprise Service Bus(IIB)
API Management
z/OS Connect EE
• Reliable messaging and Transactional invocations of applications, • However, point-to-point hard-coded (adhoc) integration; Lacks agility, and results in complex
integration topology• Asynchronous messaging; Lacking a service view as a request and a response are modeled as separate
messages
• Promotes Service reuse and productivity gain; Business and IT function alignment• Tooling for creating and integrating services; Transformation in ESB for matching client application
needs• Service registry for look up and governance; Policy based control; Loose coupling and flexible
deployment of services• However, lacks consumability and support for client entitlement, and easy set up for external
invocations• Manual mapping required for COBOL Copybook transformation (without z specific tooling)• Inherent complexity due to required round-tripping across app and integration developers
• Simpler (consumable) REST based interfaces and meaningful Swagger based business APIs relating multiple transactions under a single API as operations on a business entity
• Improved consumability with browsable catalog and subscription support• Improved control for enforcing client entitlements (and Insight with usage analytics); Accountability
and support for chargeback• Complements existing SOA investment with improved consumability, control and insight• Support for “Create” and “Run” of Interactive APIs with visual composition tools • Support for API Governance, and developer portal for consuming app developers• z/OS Connect EE makes it very easy to “Create” and “Run” System APIs from z Assets
*Transportation via Planes, Trains & Automobiles can coexist, though not an apt analogy
All three types of integration capabilities may sometimes co-exist* in a single customer environment
•
Analytics run on SoR system for optimal performance
and security
IMS
WebSphere
DB2 An
alyt
ics
System of Record
CICS
Web Services
ESB (IIB)
COBOL
CPYBOOKWeb Services,
Others…
REST APIs
(Open APIs)
REST
RESTREST
Existing SOA Client
Applications
** Other forms of messaging based
integration capabilities may also be
present
*New Managed,
Composite and/or
Systems APIs
REST APIs
Incremental adoption of new z/OS Connect EE based REST APIs and/or managed APIs can co-exist with already deployed SOA based services, and other forms of integration capabilities
Web Svc
APIs
1. Existing investments over the last 10+ years in SOA can be extended with API Connect
2. Provide a first class experience in developing and managing new APIs for z applications and data
MQ, CTG, etc.
z/OS Connect EE
Exposing Mainframe-Based Assets as SOR APIs
48
IBM z/OS Connect Enterprise Edition (EE) V2.0 is the latest evolution of
z/OS Connect! z/OS Connect EE V2.0 is a priced offering, orderable via
Shopz as PID 5655-CEE.
Available now!
Announcement letter ENUS215-493
ibm.biz/zosconnect20_announce
z/OS Connect EE V2.0 includes
A dedicated Liberty profile for z/OS
• GA release includes Liberty V8.5.5.7
New Eclipse-based tooling for API composition with SWAGGER
• Delivered through IBM Explorer for z/OS V3.0 Aqua
The WOLA service provider for access to CICS and BATCH
• Including the WOLA Liberty feature
Utilities to generate service archives for use with CICS programs
• Creates JSON schemas as input for API composition
The REST client for access to “3rd party” REST services
• e.g. JAX-RS applications hosted on WAS for z/OS
IBM z/OS Connect Enterprise EditionProduct summary review
Get ahead of the game! Register your interest todayPreview potential capabilities plus the chance to give direct feedback
49ibm.biz/zosconnectopenbeta
Useful Links
• z/OS Connect EE Knowledge Center
– http://www.ibm.com/support/knowledgecenter/SS4SVW
• z/OS Connect Enterprise Edition Home Page
– http://www-03.ibm.com/software/products/en/zos-connect-enterprise-edition
• Redbook (Building an API Bridge to Your IBM z Systems Applications and Data)
– http://www.redbooks.ibm.com/abstracts/redp5296.html?Open
• z/OS Connect Tooling
– https://developer.ibm.com/mainframe/products/zosconnect/
• IBM API Connect
• http://www-03.ibm.com/software/products/en/api-connect
• EZSource
– http://www.ezsource.com
50
Notices and Disclaimers
51
Copyright © 2016 by International Business Machines Corporation (IBM). No part of this document may be reproduced or transmitted in any form without written permission
from IBM.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM.
Information in these presentations (including information relating to products that have not yet been announced by IBM) has been reviewed for accuracy as of the date of
initial publication and could include unintentional technical or typographical errors. IBM shall have no responsibility to update this information. THIS DOCUMENT IS
DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IN NO EVENT SHALL IBM BE LIABLE FOR ANY DAMAGE ARISING FROM THE
USE OF THIS INFORMATION, INCLUDING BUT NOT LIMITED TO, LOSS OF DATA, BUSINESS INTERRUPTION, LOSS OF PROFIT OR LOSS OF OPPORTUNITY.
IBM products and services are warranted according to the terms and conditions of the agreements under which they are provided.
Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawal without notice.
Performance data contained herein was generally obtained in a controlled, isolated environments. Customer examples are presented as illustrations of how those customers
have used IBM products and the results they may have achieved. Actual performance, cost, savings or other results in other operating environments may vary.
References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in
which IBM operates or does business.
Workshops, sessions and associated materials may have been prepared by independent session speakers, and do not necessarily reflect the views of IBM. All materials
and discussions are provided for informational purposes only, and are neither intended to, nor shall constitute legal or other guidance or advice to any individual participant or
their specific situation.
It is the customer’s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legal counsel as to the identification and
interpretation of any relevant laws and regulatory requirements that may affect the customer’s business and any actions the customer may need to take to comply with such
laws. IBM does not provide legal advice or represent or warrant that its services or products will ensure that the customer is in compliance with any law
Notices and Disclaimers Con’t.
52
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 in connection with this publication 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. IBM does not warrant the quality of any third-party products, or the
ability of any such third-party products to interoperate with IBM’s products. IBM EXPRESSLY DISCLAIMS ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
The provision of the information contained h erein is not intended to, and does not, grant any right or license under any IBM patents, copyrights, trademarks or other intellectual
property right.
IBM, the IBM logo, ibm.com, Aspera®, Bluemix, Blueworks Live, CICS, Clearcase, Cognos®, DOORS®, Emptoris®, Enterprise Document Management System™, FASP®,
FileNet®, Global Business Services ®, Global Technology Services ®, IBM ExperienceOne™, IBM SmartCloud®, IBM Social Business®, Information on Demand, ILOG,
Maximo®, MQIntegrator®, MQSeries®, Netcool®, OMEGAMON, OpenPower, PureAnalytics™, PureApplication®, pureCluster™, PureCoverage®, PureData®,
PureExperience®, PureFlex®, pureQuery®, pureScale®, PureSystems®, QRadar®, Rational®, Rhapsody®, Smarter Commerce®, SoDA, SPSS, Sterling Commerce®,
StoredIQ, Tealeaf®, Tivoli®, Trusteer®, Unica®, urban{code}®, Watson, WebSphere®, Worklight®, X-Force® and System z® Z/OS, are trademarks of International Business
Machines Corporation, 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.
Thank You
Recommended