US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Transcription

1 Service Data Objects (SDO) DFED Sample Application README Copyright IBM Corporation, 2012, 2013 US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. NOTE: Before using this information and the product it supports, read the general information under "NOTICES" in this document. CONTENTS This file includes the following information: 1.0 Introduction 2.0 PreRequisites 3.0 Installing SDO Sample Application 4.0 Customizing SDO Sample Application 5.0 Running SDO Sample Application 6.0 Known Problems and Workarounds 7.0 Other Sources of Information 8.0 Notices 8.1 Trademarks 8.2 Warranty 8.3 Third Party License and Terms 1.0 INTRODUCTION The Service Data Objects (SDO) DFED sample application (driver) demonstrates SDO access to z/tpfdf. That is, it demonstrates how SDO Java applications running on a remote client can be used to access data in z/tpfdf databases. The SDO applications use a combination of z/tpfdf data access service (DAS) application programming interfaces (APIs) and SDO specification APIs. 2.0 PREREQUISITES The following are required in order to run the SDO DFED client driver: o The Java 5 (or higher) JRE o Completing the SDO Access to z/tpfdf installation and setup, as described in the z/tpf InfoCenter. This includes downloading and installing the z/tpfdf data access service (DAS), which can be obtained from INSTALLING THE SDO DFED DRIVER

2 The SDO DFED client can be installed on either a machine running Windows XP, Vista, or Windows 7, or it can be installed on a linux installation. You will need the Java 5 JRE in order to run the DFED Client driver. To install the SDO DFED driver, do the following: 1) FTP the tar file (SDO_DFED_Client.tar.gz) to your linux system. This can be placed in any directory as a holding location, for example: /tmp/ztpftar 2) Create a root directory that will hold the unpacked files, for example: /ztpfdrvs 3) Extract the source code from the tar file by entering the following commands: cd /ztpfdrvs tar -xvzf /tmp/ztpftar/sdo_dfed_client.tar.gz The following driver source files will be extracted: ADDCURR.xml antlr-runtime jar BLKINDEX.xml CREDIT.xml CREDITcase81.xml CREDITcase83_1.xml CREDITcase83_2.xml DASConfig.xml DFEDClient.jar DFED_Client_README.txt DFED_SDO_User_Guide.doc FLIGHT.xml FLIGHTcase76.xml HOTEL.xml HOTELcase78.xml HOTELcase79.xml PUSHDOWN.xml 4) Put the DFEDClient.jar file into a directory on Windows or linux. We will refer to this as the driver directory and use the /DFEDClient directory as an example. 5) Put the antlr-runtime jar file in a directory, for example: /DFEDClient/DFEDClientResources. 6) Put the DASConfig.xml file in the driver directory (for example: /DFEDClient). 7) Do one of the following: - Update the internal DAS configuration file within the DFEDClient.jar file. - Edit the DASConfig.xml file (this may be easier than updating the internal DAS configuration file). Replace all instances of INSERT_IP_ADDRESS_HERE with the IP address of your z/tpf system. Other fields may also need to be updated to match the MQ configuration on your z/tpf system. Then use the following command to change the configuration file being used by the driver: DFED OPTIONS CONFIG-'DASConfig.xml'

3 8) Ensure that the classpath is configured correctly (using the CLASSPATH environment variable or on the command line). In addition to the classpath requirements of SDO Access to z/tpfdf, the classpath must include the DFEDClient.jar file and the antlr-runtime jar file. 9) Load the database metadata (XML) files to the /sys/tpf_pbfiles/ztpfdf/production directory on the z/tpf file system. See the ZUDFM METADATA command in the z/tpf Information Center for more information. Note: If APAR PM89556 is installed on the z/tpf system, these metadata XML files should be transferred without translation. If APAR PM89556 is NOT installed, they should be transferred with ASCII to EBCDIC translation. 4.0 CUSTOMIZING THE SDO DFED DRIVER Before you can customize the SDO DFED driver, you must start the SDO DFED application for the first time. (See section "5.0 RUNNING THE SDO DFED DRIVER" for information about running the driver.) The first time the application is run, a DFED.opts file will be placed in the current directory. This file will be used to load driver options on startup. Also, any option changes will be saved to the file. It is recommended that options be altered using the "DFED OPTIONS" command rather than editing the file by hand. Be sure to set your username to match a name specified in your z/tpfdf access file by issuing the following command: DFED OPTIONS USERNAME-'MyUserName' where your username is substituted for MyUserName. 5.0 RUNNING THE SDO DFED DRIVER To start the SDO DFED client, enter the command: java com.ibm.tpf.dfed.client.dfedclient This will put the application into a command mode. You can enter individual driver commnds for processing. See the "DFED Users Guide.doc" file for more information. To terminate the program on Windows, press Control-z followed by Enter. To terminate the program on Linux, press Control-d. 6.0 KNOWN PROBLEMS AND WORKAROUNDS

4 None. 7.0 OTHER SOURCES OF INFORMATION z/tpf Information Center. 8.0 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 information 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 information. The furnishing of this information 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 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 , Shimotsuruma, Yamato-shi Kanagawa 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 INFORMATION "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.

5 Changes are periodically made to the information herein; these changes will be incorporated in new editions of the information. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this information 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 Department 31BA/Building 008 Mail Drop P South Road Poughkeepsie, NY U.S.A Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. 8.1 Trademarks 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 ****************************************************************************** * NOTE TO AUTHOR: See the "Special attributions list" on the Copyright and * trademark information page * ( * If your information includes any of these non-ibm trademarks, include the * appropriate special attribution statement. Use a separate paragraph for each * special non-ibm company. In each attribution statement, list only the * special non-ibm trademarks that the information actually uses. For example, * if this README contains a reference to Microsoft, Windows and Linux, add the * following special attribution statements: * 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. ****************************************************************************** 8.2 Warranty This package is provided on an "as is" basis. There are no warranties, express or implied, including the implied warranties of merchantability and fitness for a particular purpose. IBM has no obligation to provide service,

6 defect correction, or any maintenance for the package. IBM has no obligation to supply any updates or enhancements for the package to you even if such are or later become available. 8.3 Third Party License and Terms ANTLR 3 License [The BSD License] Copyright (c) 2010 Terence Parr All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. o Neither the name of the author nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ANTLR Project -- Developer's Certificate of Origin From ANTLR v3 and StringTemplate onwards, all substantial and/or active contributors must sign and fax or snailmail a copy of the ANTLR contributors certificate of origin formally agree to abide by it by signing on the bottom with the date. An address and your full name must be included. Mail or fax to: Terence Parr University of San Francisco 2130 Fulton St, HR532 San Francisco, CA Fax: One-off contributions may be made through the feedback page.