Release Notes for IBM Transformation Extender Pack for Healthcare V.9.0.1

Content

© Copyright IBM Corporation, 2006, 2016. All Rights Reserved.

=====================================================================
CONTENTS
=====================================================================

1. About this release (HIPAA, HL7, NCPDP)
2. Installation and configuration information (HIPAA, HL7, NCPDP)
3. Known limitations, problems, and workarounds (HIPAA)
4. New and changed behavior (HIPAA, HL7)
5. Resolved Authorized Program Analysis Reports (APARs) (HIPAA)
6. Contacting customer support (HIPAA, HL7, NCPDP)
7. Notices and trademarks (HIPAA, HL7, NCPDP)

=====================================================================
1. ABOUT THIS RELEASE (HIPAA, HL7, NCPDP)
=====================================================================

Where to find the software to download

To download the software for this pack, go to Passport Advantage® Online.

System requirements

For details about supported hardware and software for this pack, see the system requirements.

What's new in this release

See the New and changed behavior section.

Documentation

• Online documentation is provided for the pack in the IBM Knowledge Center. Note the previous versions of the HIPAA EDI, HL7, and NCPDP components were documented as separate packs.
• Documentation for this release is provided in English (United States) only.

====================================================================
2. INSTALLATION AND CONFIGURATION INFORMATION (HIPAA, HL7, NCPDP)
====================================================================

Installation prerequisites

Before you install this version of the pack, you must install one of the versions of the WebSphere Transformation Extender or IBM Transformation Extender core product that are listed in the following table.

If you are installing the pack from the ESD site, install the component using the executable (*.exe) file associated with your core product, as indicated in the following table:

WebSphere Transformation Extender or IBM Transformation Extender core product	ESD site executable files
8.4.0.5	hipaa4417_84.exe hl74417_84.exe ncpdp4417_84.exe
8.4.1.4*	hipaa4417_841.exe* hl74417_841.exe ncpdp4417_841.exe * Note: The maps that are included with the HIPAA EDI Component might have spurious warnings when they are built. Although these warnings will not impact execution of the product, they can be resolved by applying the fix for RTC45679 to the WTX Transformation Extender 8.4.1.4 core product. Contact Customer Support for this patch.
9.0.0.0	hipaa4417_900.exe hl74417_900.exe ncpdp4417_900.exe

Installing the components on Windows systems

To install the IBM Transformation Extender components for HIPAA EDI, HL7, and NCPDP, perform the following procedures:

1. Obtain the image from the Support Downloads page.
2. Run the setup.exe command. If you are installing the components from the ESD site, run the .exe command that is associated with your WebSphere Transformation Extender or IBM Transformation Extender base product (see table).
3. Follow the instructions in the installation program.

Installing the HIPAA EDI component on z/OS

After installing the HIPAA EDI Component on a Windows workstation, perform the following steps for each z/OS execution platform prior to porting and executing the HIPAA X12 Compliance Check application on that platform:

1. Transfer the load library module file: install_dir/packs/healthcare_vn.n.n/hipaa/platform_support/zos/hcsvu.loadlib 
   
   as binary to a z/OS dataset of 80-byte fixed length records named 'my.hipaa.upload'. There should be no ASCII to EBCDIC translation and no elimination of carriage return or line feed characters.
2. After the file is on z/OS, issue the TSO Receive command to create a load library:
   
   At the prompt, enter the following: ready
   Enter the following: receive inda ('my.hipaa.upload'}
   
   The following messages are displayed:
   
   INMR901I Dataset HCSVU, UPLOAD from USER on NODENAME
   INMR906A Enter restore parameters or 'DELETE' or 'END' +
3. Enter the name of the load library to be created as follows:
   
   da ('my.hipaa.loadlib')
   
   Messages indicating that the load library is being created are displayed.
4. In the JCL responsible for executing the HIPAA X12 Compliance Check application, include a STEPLIB for the created load library that appears before the WebSphere Transformation Extender Core Install loadlib. For example:
   
   //STEPLIB DD DSN=MY.HIPAA.LOADLIB,DISP=SHR
   // DD DSN=MY.WTX.INSTALL.LOADLIB,DISP=SHR

Deploying the Component on UNIX

After installing the HIPAA EDI Component on a windows workstation, perform the following steps for each UNIX execution platform. This is done prior to porting and executing the HIPAA X12 Compliance Check application on that platform.

1. Copy the UNIX shared library object for the HIPAA X12 structure validation utility, hcsvu.so or hcsvu.sl, from the following path:
   
   install_dir/packs/hipaa/platform_support/os
   
   where os indicates the operating system folder: aix, hp, or sun
   
   to the directory install_dir/libs on the target machine. Ensure that read and execute permissions are set on the shared library.
   
   If the setup script in the WebSphere Transformation Extender or IBM WebSphere Transformation Extender installation library is not run by the profile of the user, then the hcsvu.sl or hcsvu.so file should be copied to the location on the target machine that contains the compiled compliance check application maps.

Uninstalling the Component

Note: The Repair or Remove options are no longer available in the installation program. You must uninstall the components.

1. Click Control Panel > Add/Remove Programs.
2. Select the component that you want to remove.
3. Click Change/Remove and follow the prompts.

=====================================================================
3. KNOWN LIMITATIONS, PROBLEMS, AND WORKAROUNDS (HIPAA)
=====================================================================

HIPAA EDI component

Type 5 tree update requires IBM Transformation Extender examples

When running the type_5_tree_update in the HIPAA EDI components on WebSphere Transformation Extender version 8.4 or 8.4.1 or on ITX V.9.0.0, the WebSphere Transformation Extender or ITX examples must be installed. You must do a custom installation of the core product in order to install these examples.

Set permissions when deploying compliance check components to Sterling B2B Integrator

When deploying compliance check components to Sterling B2B Integrator, make sure that the permissions are set accordingly on the si_pack_dir directory (the location where WebSphere Transformation Extender products are deployed on the Sterling B2B Integrator server), and all subsequent subdirectories, including the compiled maps and the utility module.

Update to the basic steps for running the Configurable Rules Application

When you follow the steps in the "Basic steps for running the Configurable Rules Application" as provided in the component user documentation, be aware that the Extender Project must point to the following location:

install_dir/packs/healthcare_vn.n.n/hipaa

Caution: If the Extender Project does not point to this location, the Configurable Rules application does not run properly. Do not create the Extender Project with the default setting "Use Default Location."

ICD-10 functionality

The use of International Classification of Disease, 10th Revision (ICD-10) in HIPAA had a compliance date of October 1, 2015. In order to be compliant, the type trees in the HIPAA EDI Component have been modified to allow only ICD-10 codes. The HIPAA EDI stand-alone component does not enforce the actual codes, but only the qualifiers that indicate the version of the ICD in the data.

To assist with the ICD-10 transition, the following type trees are now provided in the component to allow both the ICD-9 and ICD-10 qualifiers:

hipaa_x12_type_2_icd9_icd10.mtt
hipaa_x12_icd9_icd10.mtt
hipaa_x12_ruleless_icd9_icd10.mtt
hipaa_x12_segment_icd9_icd10.mtt

If these type trees are required, the following steps must be followed to replace the type trees in the compliance check application.

Replacing the ICD-10 compliant type trees

If both the ICD-9 and ICD-10 codes are required, you must replace the type trees in the following maps as described in the table.

Maps impacted	Input card (number and name)	Default type tree	ICD-9 and ICD-10 type tree compliance check maps
x12t2precontentcheck	#1 X12_Func_Group	hipaa_x12_type_2.mtt	hipaa_x12_type_2_icd9_icd10.mtt
x12t4precontentcheck	#1 X12_Func_Group	hipaa_x12.mtt	hipaa_x12_icd9_icd10.mtt
xhipaasegmentdataaudit	#1 Transaction_Set_Segments	hipaa_x12_segment.mtt	hipaa_x12_segment_icd9_icd10.mtt

Changes for each map impacted in compliance_check.mms

For each map impacted in the table above, make these changes:

1. Open compliance_check.mms in the WebSphere Transformation Extender Design Studio.
2. Double click on the executable map to select it for modification.
3. Edit the input card for the map to point to the appropriate *_icd9_icd10 type tree instead of the default type tree.
4. Select YES when prompted, to replace all similar type tree paths in all maps.
5. Build the map.

Pass through maps

Maps impacted	Input card (number and name)	Default type tree	ICD-9 and ICD-10 type tree compliance check maps
hipaa_x12_pass_through	#1 HIPAA_X12_Inbound_Transmission	hipaa_x12.mtt	hipaa_x12_icd9_icd10.mtt
hipaa_x12_pass_through	#2 HIPAA_X12_Outbound_Transmission	hipaa_x12.mtt	hipaa_x12_icd9_icd10.mtt
hipaa_x12_type_2	#1 HIPAA_X12_Inbound_Transmission	hipaa_x12_type_2.mtt	hipaa_x12_type_2_icd9_icd10.mtt
hipaa_x12_type_2	#2 HIPAA_X12_Outbound_Transmission	hipaa_x12_type_2.mtt	hipaa_x12_type_2_icd9_icd10.mtt

Changes to maps impacted in hipaa_x12_pass_through.mms

Follow these steps to change each map impacted in hipaa_x12_pass_through.mms:

1. Use WebSphere Transformation Extender Design Studio to open hipaa_x12_pass_through.mms.
2. Double-click on the executable map to select it for modification.
3. Edit the input card listed to point to the appropriate *_icd9_icd10 type tree instead of the default type tree.
4. Select NO when prompted to replace all similar type tree paths in all maps.
5. Edit the Output card with the same number as the input card just modified to point to the appropriate *_icd9_icd10 type tree instead of to the default type tree.
6. Select NO when prompted to replace all similar type tree paths in all maps.
7. After all maps are updated, build the maps.

Changes to other maps in the HIPAA EDI Component

The following changes must be made for any of the remaining maps:

1. Use WebSphere Transformation Extender Design Studio to open the map source.
2. Double-click on the executable map to select it for modification.
3. Edit the input or output card that is using the hipaa_x12.mtt as the default type tree to point to the hipaa_x12_icd9_icd10.mtt.
4. When prompted, select YES to replace all similar type tree paths in all maps.
5. After all maps are updated, build the maps.

HL7 component
Validating data that is formatted for HL7 2.x EDI poses challenges in the areas of syntax, semantic checking, and reporting. To address these challenges, see the new HL7 validation utility in the "New and changed behavior" section.


=====================================================================
4. NEW AND CHANGED BEHAVIOR
=====================================================================

HIPAA EDI Component

Health care services review information - notification transactions
Support has been added for the following transaction set:
-- 005010X216 - 278N
-- Type tree that supports the rules in the TR3
- hipaa_x12_v5010x216_278n.mtt
There is an example map and data file which can be used for mapping and input validation in the examples directory of the installed product.


HL7 component

There is a new HL7 validation utility.

Overview

Validating data that is formatted for HL7 2.x or EDI poses several challenges. There are many required aspects to the syntax and semantic checking, and to report meaningful information based on flaws in the EDI data requires a stack of checks:

• Is the data enveloped and, optionally, batched correctly?
• Are only the correct loops and segments in the data and are they in the right order?
• Within each segment are the fields in the correct order?
• Is the data in each field the correct size?

A fairly recent addition to the HL7 offering is a set of XML schemas that describe the delimited EDI data as if it were XML tagged data. These schemas are available free of charge from HL7 for their members. If you are an HL7 member organization, you can download these schemas and load them into the ITX HL7 validation directory structure and leverage them for data validation.

The HL7 2.x EDI format is the Intellectual Property of HL7. You must contact HL7 in order to use this feature.

How the utility works

The HL7 Validation utility leverages the information in the provided XSD schemas provided by HL7, and applies the structure and data content rules from the schemas to the EDI data.

First, the delimited HL7 2.x EDI data is transformed into its XML tagged equivalent. Then that XML data (called an XML instance document) is validated against the schema. This leverages the power of an XML parser for error reporting. An HTML formatted error report (with a very XML-centric description of errors) may be produced if desired, as well as an HL7 2.x EDI-formatted ACK with a positive or negative acknowledgement indicator.

This utility also provides transformation of XML-tagged Instance documents to their delimited EDI equivalents for the versions of HL7 2.x EDI that are supported by this implementation.

List of components installed

hl7main.mms
This is the main map source that contains the top level map hl7main.mmc. It consists of the following executables and run maps:

• hl7edigenack - An executable map that generates an HL7 EDI acknowledgement for HL7 EDI input.
• hl7xmlgenack - An executable map that generates an XML HL7 acknowledgment for XML HL7 input.
• xmlscan - An executable map that scans xml data to get key fields. It uses xmllib->XSLTEX, using file GetXMLInfo.xsl to retrieve the data.
• xmlscan2 - An executable map that scans xml data to get key fields needed for generation of the XML acknowledgement. It uses xmllib->XSLTEX, using file GetXMLMSGInfo.xsl to retrieve the data from the MSH Header segment.
• xmlvalidate - Validates the data against the schemas using the xmllib->VALIDATEEX function. It is called with either the EDI HL7 input data that was converted to xml, or with the xml input data as it came in.

hl7editoxml.mms
This map source executes when the input HL7 is EDI and converts it to XML. The following processes occur:

1. Get message information (type, version, etc) from MSH.
2. Run "tag map" to add explicit segment group information, such as message type and version
3. Run generic msg2xml map to convert EDI data to XML.
   - Single map converts any message type and version.
   - Uses explicit segment group information from the previous step.
   - XML output is based on type tree/text, not XML schema.
4. Package the results for the caller.
   - The allows the map to return both status information and data.

hl7xmltoedi.mms
Executed when the input is XML HL7 and converts it toe EDI HL7. Consists of the following steps:
1) Extract/sort dictionary subset.
2) Set up runtime info for later processing.
3) Convert XML input data to native codepage.
4) Run map cvtxmltokens to convert to generic xml:
- Single map converts any message type/version to generic format.
- XML input/output is based on type tree/text, not xml schema.
5) Convert generic XML data on UTF-8 format.
6) Run map genxml2edi to convert to EDI.
7) Package results for caller.

sharedmaps.mms
Contains functional maps that are shared and used throughout the utility:

• taghl7v25.mms - Contains all of the executable maps that format untagged EDI HL7 and tag it for HL7 V.2.5.
• taghl7v2.5.1.mms - Contains all of the executable maps that format untagged EDI HL7 and tag it for HL7 V.2.5.1.
• taghl7v26.mms - Contains all of the executable maps that format untagged EDI HL7 and tag it for HL7 V.2.6.
• taghl7v27.mms - Contains all of the executable maps that format untagged EDI HL7 and tag it for HL7 V.2.7.

Inputs - ..install dir/data

Card #	Card name (FileName)	Description
#1	HL7In	Either EDI HL7 or XML HL7, as determined at run time based on the first few characters in the data. For Code page handling and MVS support, EDI input is expected to be in "Native" format and EDI output is generated as "Native." XML input is expected to be UTF-8 format and XML output is generated as UTF-8 format. All other XML files (schemas, parameter files, etc.) are expected to be in UTF-8 format. All characters in the XML data must be able to be converted to "Native" format.
#2	DictionaryList (hl7_dictionary.txt)	Message entries for each 2.x version of HL7 that is supported by the validation utility. This file should not be changed--it contains all segment, field, datatype and datatype component entries for each message.
#3	Hl7Parms (hl7parms.xml)	Parameter file that contains the values for the options to be used during the validation process. This file is scanned and if any of the values are not correct, a default value is used. See the following table for a description of the configurable parameters.
#4	Debug	Input card with a source of Echo that is used when debugging is needed. Valid vales: Y - Intermediate results in some of the run maps are returned to the main map to assist in the debugging process. N - Default. Sets these same output cards to SINK and the intermediate results are not available.

Other Inputs

Input	Description
XSLT scripts - ..install dir/maps GetXMLInfo.xsl GetXMLMSHInfo.xsl	Used by xmllib > XSLTEX. Scans input XML data for key values and returns errors if not well-formed data.
Compileallmaps.bat - ..install dir/maps	Batch file that can be used to build all the executable maps that are provided with the installation.

Outputs

Card	Name	Description and notes
#1	DataType	Used by both EDI and XML input - SINK Adapter Determines if input card #1 contains EDI HL7 data or XML data and sets the value accordingly (EDIMSG, XMLDATA).
#2	Parameters	Used by both EDI and XML input - SINK Adapter Reads the parameters from the input parameter file hl7parms.xml and sets the parameters for the map. If any of the parameters are incorrectly set, default options are used.
#3	EDIProcessStep	Used only by EDI input - SINK Adapter If datatype is EDIMSG, this card calls the conversion map to translate HL7 EDI to XML. EDI input is expected to be in "Native" format. A status is set for this step which reflects the results of the conversion to XML
#4	UTF8ConvertedXML	Used only by EDI input - SINK Adapter Converts generated XML data to UTF-8.
#5	ScanXMLStep	Used only by XML input - SINK Adapter If datatype is XMLDATA, then scan the input XML for key values using map xmlscan A status is set for this step which reflects the results of the XML scan.
#6	ValidationParmsStep	Used by both EDI and XML Input - SINK Adapter This card gets the validation parms from the MSH segment for use in later processing from map hl7edi2xml. A status is set for this step which reflects the results ensuring all the fields obtained are available and valid.
#7	ValidationStep	Used by both EDI and XML input - SINK Adapter Validates the XML data against schemas using map xmlvalidate. A status is set for this step which reflects the results of schema validation.
#8	XMLProcessStep -	Used only by XML input - SINK Adapter If datatype is XMLDATA, this card converts the XML to HL7 EDI data using map hl7xml2edi. A status is set for this step which reflects the results of the conversion
#9	FinalStatus	Used by both EDI and XML input - SINK Adapter Determines the overall status of all prior steps.
#10	StatusReportHTML	Used by both EDI and XML input - File Adapter../data/StatusReport.html (CreateOnContent) This report is generated based on the value of the GenerateReport parameter and the FinalStatus. It is an HTML report that displays the following values: - Final Status for process - Message Type - Message Version - XML Scan Status (if input is XMLDATA) - XML Validation Status - XML > EDI or EDI > XML Conversion Status If this step fails, the corresponding error message is also displayed.
#11	XMLOut	Used only by EDI input - File Adapter ../data/HL7Out.xml (CreateOnContent) UTF-8 Converted XML from output card #4
#12	EDIOut	Used only by XML input - File Adapter ../data/HL7Out.edi (CreateOnContent) HL7 EDI converted data from output card #8
#13	HL7_EDI_ACK	Used only by EDI input - File Adapter ../data/hl7_edi_ack.out (CreateOnContent) If input is HL7 EDI and acknowledgement was requested, an Original Mode Acknowledgement is generated in HL7 EDI format.
#14	ScanXMLStep2	Used only by XML input - SINK Adapter If datatype is XMLDATA, this card calls a map to scan the xml and extracts additional key values for the Original Mode Acknowledgement using XSLT. A status is set for this step which reflects the results of the XML scan.
#15	MSH_Fields	Used only by XML input - SINK Adapter If the previous step to extract the data was successful, then the data is converted to a delimited format for use in the acknowledgment generation process.
#16	HL7_XML_ACK	Used only by XML input - File Adapter ../data/hl7_xml_ack.xml (CreateOnContent) If input is HL7 XML and acknowledgement was requested, an Original theMode Acknowledgement is generated in XML format.

Configurable parameters

Parameter name (tag name)	Values	Description
Validation input XML data (ValidateInputXML)	Y[es] N[o]	Valid values: Y - Default. If input data is XML, validate it against the HL7 schemas. N - If the input data is XML, do not validate it against the HL7 schemas
Validate generated XML data after conversion from EDI (ValidateOutputXML)	Y[es] N[o]	Valid values: Y - Default. If input data is EDI, validate the converted XML data against the HL7 schemas. N - If the input data is EDI, do not validate the converted XML data against the HL7 schemas.
Schema root directory (SchemaRootDir)	../hl7schemas	The path of the location of the HL7 schemas in version-specific subdirectories (v2.x). Relative paths are based on the map execution directory. For example, if this is set to ../hl7schemas, the schemas for version 2.7 will be in map directory /../hl7schems/v2.7. The default is ../hl7schema.
Generate an HTML report that describes the messages processing status (GenerateReport)	A[lways] E[rrors]	Valid values: A - Default. Always generate a report for every message, whether processing is successful or not. E - Only generate a report if an error occurs. No report is generated if processing is successful.
Generate an original mode HL7 Acknowledgement that provides the message status (GenerateAck)	A[lways] E[rrors]	Valid values: A - Default. Always generate an acknowledgement for every message, when possible. E - Only generate an acknowledgement if there is an error in the data.
Maximum number of fields per segment (MaxFieldsPerSegment).	100	If this is set too low, fields at the end of some segments may be lost when converting from XML to EDI. If this is set significantly higher than needed, it may impact performance. Default: 100
Maximum number of components per composite datatype (MaxComponentsPerDatatype)	30	If this is set too low, components at the end of some datatypes may be lost when converting from XML to EDI. If this is set significantly higher than needed, it may impact performance. Default: 30

============================================================
5. RESOLVED AUTHORIZED PROGRAM ANALYSIS REPORTS (APARs)
============================================================

For a list of the APARS that are fixed in this version of the product, see the Fix List.



=====================================================================
5. CONTACTING CUSTOMER SUPPORT
=====================================================================

Contact Customer Support at 1-800-IBM-SERV, or go to the support portal.


=====================================================================
6. NOTICES AND TRADEMARKS
=====================================================================

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 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 character set (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.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, 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
577 Airport Blvd., Suite 800
Burlingame, CA 94010
U.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 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.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning 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.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

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

Programming interface information

Programming interface information, if provided, is intended to help you create application software using this program.

General-use programming interfaces allow you to write application software that obtain the services of this program's tools.

However, this information may also contain diagnosis, modification, and tuning information. Diagnosis, modification and tuning information is provided to help you debug your application software.

Warning: Do not use this diagnosis, modification, and tuning information as a programming interface because it is subject to change.

Privacy Policy Considerations

IBM Software products, including software as a service solutions, ("Software Offerings") may use cookies or other technologies to collect product usage information, to help improve the end user experience, to tailor interactions with the end user or for other purposes. In many cases no personally identifiable information is collected by the Software Offerings. Some of our Software Offerings can help enable you to collect personally identifiable information. If this Software Offering uses cookies to collect personally identifiable information, specific information about this offering’s use of cookies is set forth below.

This Software Offering does not use cookies or other technologies to collect personally identifiable information.

If the configurations deployed for this Software Offering provide you as customer the ability to collect personally identifiable information from end users via cookies and other technologies, you should seek your own legal advice about any laws applicable to such data collection, including any requirements for notice and consent.

For more information about the use of various technologies, including cookies, for these purposes, see the IBM Privacy Policy, the IBM Online Privacy Statement section entitled "Cookies, Web Beacons and Other Technologies," and the IBM Software Products and Software-as-a-Service Privacy Statement.

Trademarks and service marks
IBM, the IBM logo and ibm.com are 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.

• Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
• Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
• Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.
• UNIX is a registered trademark of The Open Group in the United States and other countries.

This product includes software developed by the Eclipse Project
(http://www.eclipse.org/).