In today’s world, data resides

in different systems and formats

and is queried by various

database management systems

running on different hardware

platforms with different

operating systems.

Data integration brings these

complex environments together.

W H I T E PA P E R

>>

Data Access for Mainframe Data Sources

TOTAL® Integrationa Cincom TIGER™ Component

Extending the Life of Existing Data

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

Accessing VSAM From a Web Browser................................................................ 5

Accessing VSAM From a Desktop Tool................................................................ 6

Steps to Accessing Non-Relational Data............................................................... 7

Mapping Non-Relational Data to TOTAL Integration.......................................... 8

Mapping Non-Relational Data to Relational Format............................................ 9

Security..................................................................................................................14

Starting the Relational Translator ........................................................................14

Don’t Just Manage It: Put Your Data to Work.....................................................15

TOTAL Integration Supported Platforms............................................................15

TOTAL Integration Web Servers.........................................................................16

DBMS Adapter Supported Platforms and Versions.............................................16

Table of Contents

The better the information, the better the decision. To succeed, all businesses need the rightinformation to get to the right people at the right time, regardless of where that informationresides. In business, common data must be shared among all applications and solutions.

In today’s world, data resides in different systems and formats and is queried by variousdatabase management systems running on different hardware platforms with differentoperating systems.

Data integration brings these complex environments together. It provides compatibility andinteroperability between vendors’ hardware, software, and packaged applications. Dataintegration aligns information systems with an enterprise’s business model through a combination of methods, tools, and techniques aimed at modernizing, consolidating, andcoordinating varying applications.

Although data integration solutions for relational data are common, much data is still lockedup in mainframes. This data, crucial to day-to-day operations, resides in pre-relational orflat-file systems, such as VSAM, IMS™, IDMS, Datacom, and Adabas. Access to this datawith relational technologies is crucial.

With commerce moving to the web, access to XML technologies for your mainframe datahas become important as well.

Cincom TIGER is an enterprise data integration manager with non-relational access, datacaching, XML capabilities, and analytics capabilities. Cincom TIGER allows you to store, query,and manipulate information in both relational format and XML format. As a data integrator,Cincom TIGER supports the federated, distributed, relational data model that provides a unified and consistent view of distributed, heterogeneous data. Any relational database system,such as DB2®, Oracle®, etc., can be integrated into a single view. A number of popular non-relational systems such as VSAM, IMS, and IDMS can also be accessed in relational format.

Cincom TIGER has four components:

TOTAL® IntegrationTOTAL Integration federates data from multiple relational and non-relational data sources.TOTAL Integration uses an SQL execution engine and data source-specific adapters tointerface with the various data sources.

TOTAL Integration allows you to integrate your data sources and provide dynamic accessto your data using the industry-standard relational APIs ODBC, JDBC™ and OLEDB.

TOTAL® CacheTOTAL Cache provides data replication services. TOTAL Cache can offload processingfrom the operational systems, especially important for mainframe data sources.Initially, a data source or a subset of a data source (the master) is copied into CincomTIGER (the replicate). Then TOTAL Cache monitors changes being made to the masterdata source and stores them in a journal. Periodically, the journal is written to thereplicate, keeping the replicate closely synchronized with the master.

Introduction

3

4

TOTAL® XMLTOTAL XML provides XML functionality for all data sources, including non-relationaland mainframe data sources. TOTAL XML supports XML tagging, XML document/fragment manipulation, and XPATH support for documents stored within CincomTIGER or external data sources. As an XML data manager, TOTAL XML can store,query, and manipulate any XML document or document fragment. TOTAL XML canprocess the full complexity of XML documents, unlike relational systems that haverestrictions based on the tabular nature of relational data.

TOTAL XML allows you to access your XML documents using industry-standard XMLAPIs DOM™, SAX, XML:DB, and XUPDATE.

TOTAL® AnalyticsTOTAL Analytics provides business analytics functionality.

Accessing Your Mainframe Data

TOTAL Integration delivers simple, efficient access to mainframe non-relational data sources.

The accompanying diagramdepicts how TOTAL Integrationcommunicates with a mainframedatabase such as VSAM. TOTALIntegration communicates withthe VSAM relational translator(or other relational translator)running on the mainframe.

You can access such databases as Oracle, SQL Server, DB2, and anything that has an ODBCadapter. Besides VSAM, you can access IMS, IDMS, Adabas, Datacom, and flat files.

Applications can use the following language interfaces:• Microsoft® ODBC • Java™ Custom Mappings • SAX• Microsoft OLEDB • Document Object Model (DOM) • XML:DB• JDBC

The TOTAL Integration Server can support many clients.

VSAMdatabase

TOTAL Integration resides on an

Intel® Windows®

server.

VSAM database resides on an IBM® Mainframe.

relationaltranslator

TCP/IP

TOTAL Integrationsupports access to

a number of differentmainframe database

management systems.

5

Accessing VSAM From a Web Browser

The picture below shows how you access VSAM data from a web browser.

1. The desktop browser requests the proper web page from the web server.

2. The web page has an embedded call to a Java servlet. The Java servlet calls TOTALIntegration using JDBC and an SQL statement.

3. TOTAL Integration sends an SQL statement to the relational translator via TCP/IP.

4. The relational translator decodes the SQL statement, converts the statement to VSAMcalls, and accesses VSAM.

5. VSAM passes each result back to the relational translator, which will return the resultset.

6. As buffers are filled, the relational translator sends the data back to TOTAL Integrationvia TCP/IP, and then to the Java servlet which builds the page.

7. This page is returned to the browser.

1. The desktopbrowser requeststhe web pagefrom the web server.

VSAMDatabase

TCP/IP

2. The web page has an embedded call to a Java servlet. The Java servlet calls TOTAL Integration using JDBC. 4. The

relational translator translates the request into the VSAM calls.

5. VSAM passes the data back to the relational translator, which creates a table of results that TOTAL Integration understands.

VSAMrelational translator

6. The relational translator sends the data to TOTAL Integration server, which sends the data to the Java servlet.

3. TOTAL Integration sends the SQL statement tothe relationaltranslator via TCP/IP.

7. The page isreturned to thebrowser.

Accessing VSAM From a Desktop Tool

6

Accessing VSAM data from the desktop is done in a similar manner to accessing data fromthe web.

1. The PC client with an ODBC-enabled tool sends a SELECT statement to the TOTALIntegration server.

2. The TOTAL Integration server sends an SQL statement to the relational translator viaTCP/IP.

3. The relational translator decodes the SQL statement, converts the statement to VSAMcalls, and accesses VSAM.

4. VSAM passes each result back to the relational translator, which will return the resultset.

5. As buffers are filled, the relational translator sends the data back. TOTAL Integrationreturns it to the PC client.

1. PC client with ODBC-enabledtools sends request to TOTAL Integration server.

VSAMDatabase

TCP/IP

2. TOTAL Integration sends the SQL statementto the relational translator. 3. The

relational translator translates the request into the VSAM calls.

4. VSAM passes the data back to the relational translator, which creates a table of results that TOTAL Integration understands.

VSAMrelational translator

5. ... which sends the data to TOTAL Integration server, which sends the data to the PC client.

7

Steps to Accessing Non-Relational Data

The following steps, typically performed by the database administrator (DBA), arerequired to access your mainframe data.

1. Create the TOTAL Integration database and load TOTAL Integration-resident data2. Tailor TOTAL Integration3. Define the metadata for the mainframe data4. Define the mainframe file to TOTAL Integration

Step 1The DBA creates a database in TOTAL Integration. The TOTAL Integration database has tobe created and initialized using the createdb utility. If all of the data resides on your main-frame system, then only the metadata will reside on TOTAL Integration. The DBA thenruns the loaddb utility to load TOTAL Integration-resident data.

Step 2The DBA sets system parameters for TOTAL Integration. The main parameters describe thedatabase name and location, and give the port number to be used for communication.

Step 3The DBA uses a graphical tool, the Navigator, which is used to define the VSAM metadatato TOTAL Integration. The basis of the metadata is typically a COBOL or PL/1 copybook.

Step 4Once the VSAM metadata is defined, it must be used to create a TOTAL Integration proxy.The proxy maps the non-relational data to TOTAL Integration classes. There is a visualtool to help perform this step.

8

Mapping Non-Relational Data to TOTAL Integration

TOTAL Integration Data Model

Similar to a relational database, the TOTAL Integration conceptual schema comprises all of the views mapped to relational tables. Relational tables are created from non-relationalfiles through a transformation schema. The transformation schema is composed of proxies.Each proxy defines the mapping between a relational table in the transformation schemaand a mainframe file. The proxy performs two functions: 1) It maps between the relationaltable names and non-relational field or external field names; 2) It converts between relationaldomain and non-relational data types.

Mainframe File

Mainframe File

Mainframe File

Mainframe File

Transformation Schema

Conceptual Schema

Proxy

Proxy

Proxy

Proxy

Proxy

Mainframe File

...

Table #1 . . . Table #n

9

Mapping Non-Relational Data to Relational Format

Pre-relational files, such as flat files, IMS, Adabas, and VSAM databases, are very differentfrom relational ones. The actual description of what the file contains is not included withthe data. There is no way to query the file and ask for such information as, “What fieldsare in this file?” The metadata is held external to the actual data.

TOTAL Integration has a Windows-based tool called Navigator to handle the task ofdefining the metadata. All the information input is stored in a component called a“datamap.” Once built, the datamap is moved to the same platform as the source or targetdata. Note that there are no compilations or code-generation processes involved. Once thedatamap is built, it is immediately ready for use.

Where can this metadata come from? Navigator allows the following copybooks to beimported:

• COBOL and PL/1 copybooks• IMS DBDs (database definitions)

The copybooks can be imported from the local PC or directly from another platform usingNavigator’s integrated communications layer.

Building a datamap consists of a three-step process:1. Create the “physical view” of the data, typically done by importing copybooks.2. Take the “physical view” and from it create one or more “logical views,” called tables.3. Test the data source directly by running a row test.

Here is an example of the display created after importing a COBOL copybook:

It shows the field names, their data type and length, and offset from the start of the recordor segment. Group fields and also arrays (COBOL OCCURS) will also be shown in the treestructure. More than one copybook can be imported into a datamap.

10

Here is a table display:

It shows the column names and also the source field on which the column is based.

Here’s the real benefit of this tool: Having done the first two steps, often within a coupleof minutes, you can then directly source data from the remote platform and see theresults. This is the row test feature, and the following is a sample display:

That’s it! Tasks that used to take hours, probably involving a lot of discovery work, pro-gramming, and calling people can now be done within minutes. Cincom has exampleswhere consultants were writing COBOL programs taking one to two weeks per source,and TOTAL Integration was able to accomplish the same results in minutes.

Because the above looks so simple, it is easy to overlook just what a sophisticated solutionTOTAL Integration provides. The diagram on the following page examines what TOTALIntegration is doing under the covers when an IMS database is accessed.

11

TOTAL Integration is driven by standard SQL to request data “select column1 from customer.table. …” It reads in the corresponding datamap, which was built using theNavigator. From this, it works out the data required from the IMS segments, navigatesusing native DL/1 calls through the IMS database, and returns the desired data in a formatthat looks as though the source was a relational database.

When accessing non-relational data sources (IMS, IDMS, VSAM, Datacom, Adabas, and flatfiles), TOTAL Integration has some additional and very powerful technology to enhancethe quality and the content of the data being retrieved. The following highlights some ofthese features.

Bad Data Handling

One of the key problems when accessing legacy data sources is that the quality of the data is uncertain. On many occasions, data is extracted and the attempt to load the datainto a relational database results in all of the rows being rejected, as one or more fields areconsistently in error throughout the database. Use of the Row Test feature in Navigatorwill certainly cut down on this sort of problem, but what about the problem of odd fieldsbeing invalid?

When defining the data source using Navigator, you can specify how much bad data han-dling you want applied. You can choose to abort the retrieval if bad data is found, or havean entry written to the log file. You can select which field types you want checked. Alongwith this, you can set a default date for use with the date/time masking routines and thereplacement for any bad characters found.

In conjunction with this, you can define what is to happen at the field level. The fielderror handling that can be specified is as follows:

• Use the error rules as set for the datamap• Set the field to NULL• Replace the field with a valid default• Skip the field and write an entry to the log file• Terminate the data retrieval process

Datamap provides runtime metadata

SQL request, e.g., select column1 from customer.table

Typical IMShierarchical

database

12

Date and Time Masking

Date and time fields in legacy data are defined as ordinary numeric fields, often IBMpacked decimal. To make these fields more valuable and to avoid further conversionsonce the data is loaded into a relational format, they can be defined as date/time fields atextract time. As many of these fields may only have two digits for the century, Navigatorhas complete masking technology to allow missing date components to be added underrules provided by the user.

Here’s an example. The input data is EBCDIC 4 bytes packed decimal, December 31, 1999,MMDDYY:01 23 19 9C

This can be converted at extraction time to an eight-character field:19991231

Here’s another example. The same input date is in character with embedded hyphens, DD-MM-YY:31-12-99

again to be converted at extraction time to an eight-character field:19991231

Navigator can also handle Julian dates. Here’s the same date in Julian format YYDDD,EBCDIC 3 bytes packed decimal:99 36 5C

again to be converted at extraction time to an eight-character field:19991231

The same concept can be applied to time and timestamp fields using HH, MI, and SS withup to six digits in terms of fractional seconds. Here’s a full example of a character time-stamp field input, the mask defined in the datamap, and the resultant output:

Data Timestamp Mask Output02-28-87 12:01:33 – 123 MM-DD-Y2 HH:MIMM:SS – N3 19870228120133123000

Simple Data Filtering

Often legacy data sets have one or more header records. To avoid having to code SQL toignore these records, you can define in the datamap that a certain number of records atthe beginning of the file can be ignored.

Combined or separate from this is the ability to specify that a field is a “record type” anddefine a list of one or more record types that should be included or excluded. Let’s saythat you have four record types on the file, 01, 03, 07, and 99, and you are only interestedin the 03 types. You can define that only records having 03 in the type field are to beprocessed.

Sourcing Delimited Text Files

TOTAL Integration can source from many different types of flat file from any platform, notjust MVS®. They may be comma- or tab-delimited files, but you can specify the characterstring that is the field delimiter. For such files, a smaller subset of the data types is available,mainly characters and numbers, and TOTAL Integration will strip off edit characters andchange this highly variable data into data ready for relational loading. All the date and timemasking is available, and also the bad data handling can clean up poor-quality sources.

13

OCCURS Clauses

Many old legacy data sources contain OCCURS clauses, often known as arrays. These canbe fixed arrays, i.e., a fixed number of elements, or elements in the array varying in numberaccording to the data content of another field (OCCURS DEPENDING ON). TOTAL Integrationsupports putting all the elements of the array into a single output row. However, muchmore sophisticated is the ability to generate a variable number of rows from the OCCURSDEPENDING ON field. Taking a single row in, TOTAL Integration can break out theOCCURS DEPENDING ON elements into individual output rows, optionally carrying datafrom the input row (like the account number in the diagram) into all the rows’ output:

TOTAL Integration can also take data from multiple OCCURS DEPENDING ON clauses in a single input row and handle multiple rows’ output, setting output fields to NULLwhen their data is exhausted.

Here’s some sample input:

Input Row fld1 - OCCURS DEPENDING fld2 - OCCURS DEPENDING1 3 values 10,20 30 2 values AA, BB2 1 value 55 4 values DD1, DD2, DD3, DD4

This is the output:

Output Row fld1 fld21 10 AA2 20 BB3 30 NULL 4 55 DD15 NULL DD26 NULL DD37 NULL DD4

This one-to-many process can also carry other fields through – such as header informa-tion, etc. – so that every output row is complete.

AccountNumber

LifeInsurance

AccountNumber

HouseInsurance

AccountNumber

MotorInsurance

AccountNumber 1 2 3 ....

Output Rows 1

2

3

Input Row OCCURS DEPENDING ON

14

Security

Because security is a major concern, the level of checking is under your control by meansof settings to the mainframe configuration file. The first critical check is that whenever auser, local or remote, tries to connect to the relational translator, a valid RACF userid andpassword must be supplied. If this combination is not valid, the connection request will berejected. Owing to the RACF checks being carried out, the LOADLIB must be authorized.

There is also a user-defined security table, which can control the features that a particularuserid can access. Thereafter, standard MVS security checking is carried out, depending onthe type of file/database being accessed:

• VSAM and flat files: RACF checks ensure that the userid has authority to read from or write to the dataset.

• DB2: All DB2 requests are run with the userid supplied by the client, or it can default to the listener job userid.

• IMS: All IMS jobs run with the userid from the calling platform. This userid must have any appropriate RACF authorizations to access the IMS databases. For listener-initiated jobs, you define the PSB and PCB that will be used, so that the remote user cannot select this.

Starting the Relational Translator

A relational translator can be run as a standard never-ending batch job or a started task.Once started, it is closed down via an operator console command.

When accessing any non-IMS dataset, the relational translator starts a new subtask, and thistask in the relational translator region carries out the request, hence no jobs are initiated.The maximum number of concurrent tasks that a listener can start is set by a user-definedparameter.

IMS database access requests must be run under the control of IMS, hence these connectionrequests submit via the JES internal reader a standard job running PROC DLIBATCH (oryour installation equivalent). The JCL for this job and the PSB are user-defined. Specialcommunication linkage occurs between the listener and the newly submitted job, so thatthe remote TOTAL Integration client is totally unaware that a new MVS job is now handlingthe request, apart from the small time delay that occurs while the new job is initiated.Once the request is finished, the new job closes down.

Most of the time you will see a single MVS region barely active, just polling the appropriateTCP/IP port(s) and waiting for connection requests.

15

Don’t Just Manage It: Put Your Data to Work

Greater demands are being imposed on your data systems. New business applications for e-commerce require expanded and more efficient use of existing data. The risks ofimplementing another database management system are serious. This can cause stressfulhours and late nights for your staff – a real problem. The answer is to enable your existingdata to meet the challenge with TOTAL Integration. Put your data to work.

Extend the life of your mainframe information and confidently install new systems by integrating and managing all data – structured or not – with TOTAL Integration. TOTALIntegration is the missing link between your existing enterprise data and new applications,including the web. TOTAL Integration reduces the custom code necessary to integrateyour mainframe data into a website, which means less testing, greater reliability, and fasterdevelopment, eliminating those late nights.

TOTAL Integration provides a robust growth path for today’s application environment. It offers mainframe data users a way to extend the life of their current application portfolio.This is critical as you respond to the dramatic transformation of business and the informationavailability requirements it brings.

TOTAL Integration Supported Platforms

The following platforms are supported:

TOTAL Integration ClientHP PA RISC HP-UX® 11INTEL Microsoft Windows NT® 4.0INTEL Microsoft Windows 2000INTEL Microsoft Windows XPSUN SPARC™ Solaris™ 2.6, 7, 8

TOTAL Integration ServerINTEL Microsoft Windows NT 4.0INTEL Microsoft Windows 2000INTEL Microsoft Windows XP

The following table shows the DBMSs that are supported in Release 2.1.0. TOTAL Integrationcan access many other DBMSs if they support ODBC. These include (but are not limited to)Sybase® and Informix®. Subject to change. Please contact your Cincom representative for current versions.

AdabasAdabas C Version 3.1.1 patch 36 HP® PA-RISC HP-UX 11 64-bit Read-onlyAdabas C Versions 6.2 and 7.1.2+ IBM OS/390® V1 and V2 Read-onlyAdabas C Versions 6.2 and 7.1.2+ IBM z/OS® 1.1+ Read-onlyAdabas C Versions 3.1 Intel Windows NT SP4+ Read-onlyAdabas C Versions 3.1 Intel Windows 2000 Read-onlyAdabas C Versions 3.1 Intel Windows XP Read-onlyAdabas C Version 3.1.1 patch 56 Sun SPARC Solaris 2.6 Read-only

C-ISAMC-ISAM HP PA-RISC HP-UX 11 Read/Insert-onlyC-ISAM IBM AIX® 4.3+ Read/Insert-onlyC-ISAM Intel Windows NT SP4+ Read/Insert-onlyC-ISAM Intel Windows 2000 Read/Insert-onlyC-ISAM Intel Windows XP Read/Insert-onlyC-ISAM Sun SPARC Solaris 2.6 Read/Insert-onlyC-ISAM Sun SPARC Solaris 7+ Read/Insert-only

DB2Datacom 10+ IBM OS/390 V1 and V2 Read/WriteDatacom 10+ IBM z/OS 1.1+ Read/Write

DB2DB2 Universal Database 6.1+ IBM AIX 4.3+ Read/WriteDB2 Universal Database 5.2+ IBM AS/400® 4.3+ Read/WriteDB2 Universal Database 3+ IBM OS/390 V1 & V2 Read/WriteDB2 Universal Database 3+ IBM z/OS 1.1+ Read/WriteDB2 Universal Database 6.1+ Intel Windows NT SP4+ Read/WriteDB2 Universal Database 6.1+ Intel Windows 2000 Read/WriteDB2 Universal Database 6.1+ Intel Windows XP Read/Write

16

TOTAL Integration Web Servers

TOTAL Integration has been tested with the following web servers:

ApacheBorland® JRUNIBM WebSphere®

Microsoft IISSun™ OneTOMCAT

DBMS Adapter Supported Platforms and Versions

17

Flat Files and TapeFlat files HP PA-RISC HP-UX 11 32-bit Read/Insert-onlyFlat files HP PA-RISC HP-UX 11 64-bit Read/Insert-onlyFlat files IBM AIX 4.3+ Read/Insert-onlyFlat files IBM OS/400® 4.3+ Read/Insert-onlyFlat files Intel Windows NT SP4+ Read/Insert-onlyFlat files Intel Windows 2000 Read/Insert-onlyFlat files Intel Windows XP Read/Insert-onlyFlat files Sun SPARC Solaris 2.6 Read/Insert-onlyFlat files Sun SPARC Solaris 7+ Read/Insert-onlyFlat files IBM OS/390 V1 and V2 Read/Insert-onlyFlat files IBM z/OS 1.1+ Read/Insert-onlyTape IBM OS/390 V1 and V2 Read Tape IBM z/OS 1.1+ Read

IDMSIDMS 14.1+ IBM OS/390 V1 and V2 Read-onlyIDMS 14.1+ IBM z/OS 1.1+ Read-only

IMSIMS 5+ IBM OS/390 V1 and V2 Read-onlyIMS 5+ IBM z/OS 1.1+ Read-only

OracleOracle 8.0 and 8.1 All Oracle server platforms Read/Write

that support an 8.0.5 client

Cincom TIGERCincom TIGER 2.1 HP PA-RISC HP-UX 11 32-bit Read/WriteCincom TIGER 2.1 Intel Windows NT SP4+ Read/WriteCincom TIGER 2.1 Intel Windows 2000 Read/WriteCincom TIGER 2.1 Intel Windows XP Read/WriteCincom TIGER 2.1 Sun SPARC Solaris 2.6 Read/WriteCincom TIGER 2.1 Sun SPARC Solaris 7+ Read/Write

SQL ServerSQL Server 7, 2000 Intel Windows NT SP4+ Read/WriteSQL Server 7, 2000 Intel Windows 2000 Read/WriteSQL Server 7, 2000 Intel Windows XP Read/Write

SUPRA® PDMSUPRA PDM 2.3.20a and higher Compaq Alpha™ OpenVMS™ Read/WriteSUPRA PDM 2.3.20a and higher Compaq VAX OpenVMS Read/WriteSUPRA PDM 1.2.3a and higher HP PA-RISC HP-UX 11 32-bit Read/WriteSUPRA PDM 2.4 and higher IBM OS/390 V1 and V2 Read/WriteSUPRA PDM 2.4 and higher IBM z/OS 1.1+ Read/Write

SUPRA SQLSUPRA SQL 2800+ All SUPRA server platforms Read/Write

VSAMVSAM IBM OS/390 V1 and V2 Read/Insert-onlyVSAM IBM z/OS 1.1+ Read/Insert-only

UNITED STATES

Atlanta, GA770-441-0550

Chicago, IL847-370-4212

Cincinnati, OH513-612-2300

Columbus, OH614-863-6636

Dallas, TX817-571-9117

Irvine, CA949-752-7220

Kansas City, KS913-451-6969

Minneapolis, MN952-470-1920

New York, NY732-530-1313

Phoenix, AZ480-775-5168

Pittsburgh, PA724-242-0158

Santa Clara, CA408-216-4600

St. Louis, MO314-995-3800

Syracuse, NY315-655-2680

CANADA

Mississauga, Ontario905-279-4220

Montreal, Quebec514-866-8661

EUROPE

Brussels, Belgium+32 2 679 68 11

Lyon, France+33 4 78 63 78 63

Paris, France+33 1 53 61 70 00

Schwalbach, Germany+49 6196 90 03 0

Vianen, The Netherlands+31 347 358 458

Torino, Italy+39 011 5154 711

Monaco+377 93 10 01 20

Barcelona, Spain+34 93 487 49 57

Madrid, Spain+34 91 524 9820

Stockholm, Sweden+46 8 594 605 00

Geneva, Switzerland+41 22 747 75 18

Lymington, UK+44 1590 676138

Maidenhead, UK+44 1628 542300

Manchester, UK+44 1625 535585

GREATER ASIA PACIFIC

Melbourne, Australia+61 3 8601 1116

Sydney, Australia+61 2 9411 9300

New Delhi, India+91 11 2373 7590

Tokyo, Japan+81 3 3438 2791

Kuala Lumpur, Malaysia+60 3 2161 4962

Shanghai, China86 21 6375 8200

BRAZIL

Sao Paulo, Brazil+(55 11) 3097 9555

LATIN AMERICANOPERATIONS

Cincinnati, OH513-612-2672

EUROPE, MIDDLE EAST ANDAFRICA

Monaco+377 93 10 01 20

For countries other than thoselisted on this page, contactCincom World Headquarters.

World Headquarters • Cincinnati, OH USA • US 1-800-2CINCOM • International 1-513-612-2769 • E-mail info@cincom.comhttp://www.cincom.com • For local international offices, go to: www.cincom.com/international

This document contains unpublished, confidential, and proprietary information ofCincom. No disclosure or use of any portion of the contents of these materials may bemade without the express written consent of Cincom.

CINCOM, , Cincom TIGER, SUPRA, TOTAL, and The World’s Most ExperiencedSoftware Company are trademarks or registered trademarks of Cincom Systems, Inc.

Intel is a registered trademark of Intel Corporation.

Java, JDBC, Solaris, SPARC, and Sun are trademarks or registered trademarks of SunMicrosystems, Inc. in the U.S. and other countries.

HP and HP-UX are registered trademarks of the Hewlett-Packard Company.

AIX, AS/400, DB2, IBM, IMS, Informix, MVS, OS/390, OS/400, WebSphere, and z/OS aretrademarks or registered trademarks of International Business Machines Corporation.

Oracle is a registered trademark of Oracle Corporation.

Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporationin the United States and/or other countries.

Alpha and OpenVMS are trademarks of Compaq Computer Corporation.

DOM is a trademark of the World Wide Web Consortium (Massachusetts Institute ofTechnology, Institut National de Recherche en Informatique et en Automatique, or KeioUniversity).

Borland is a registered trademark of Borland Software Corporation.

Sybase is a registered trademark of Sybase, Inc.

All other trademarks belong to their respective companies.

Attention:Some Cincom products, programs, or services referred to in this publication may not beavailable in all countries in which Cincom does business. Additionally, some Cincomproducts, programs, or services may not be available for all operating systems or all product releases. Please see your Cincom representative to be certain the items are available to you.

For trademark and Copyright Terms of Use, please seehttp://www.cincom.com/en/legal/Terms.asp.

© 2003, 2004 Cincom Systems, Inc. FORM TX030508-2r 3/04 Printed in U.S.A. All Rights Reserved

¤