Installing WDI v3.3 on z/os

Transcription

1 IBM Software Group Installing WDI v3.3 on z/os Jon Kirkwood WDI/WPG L2 support WebSphere Support Technical Exchange

2 Agenda Software requirements Install steps Migration considerations Operational changes Error Notification install step, Java CICS considerations WebSphere Support Technical Exchange 2

3 Software Requirements z/os: Required by WebSphere Data Interchange server operation z/os V1R6 or later (5694-A01) DB2 for z/os or OS/390 V7 or later (5645-DB2) IBM System Modification Program Extended (SMP/E) for z/os V or later (5655-G44) IBM XML Toolkit for z/os, V1.9 (needed for batch Data Transformation or for submitting server commands from WDI Client v3.3) PC: Required for WebSphere Data Interchange Client operation Windows 2000 or Windows XP DB2 Connect v8.2 Software required for network connection WebSphere Support Technical Exchange 3

4 Optional Software CICS Transaction Server for z/os Version 2.3 (5697-E93) or later (required for Online mode) WebSphere MQ for z/os and OS/390 V5.3.1 (5655-F10) IBM SDK for z/os, Java 2 Technology Edition Version 1.4 Service Level SR(6) (PTF UK17574) or higher Used by WDI Common Event Handling Java API Also used for XML Transformation under CICS WebSphere Support Technical Exchange 4

5 Installation overview WebSphere Data Interchange Version 3.3 Installation Guide for z/os (SC ): Use appropriate Table from Installation Guide as a checklist Support for three scenarios: Table 5 - New customer Table 6 - Existing customers: v3.1 or v3.2 Table 7 - CICS CICS customers must first complete New or Existing scenario above WebSphere Support Technical Exchange 5

6 Step 1-10: SMP/E functions Initialize distribution and target zones. Pay close attention to CALLLIB DDDEF entries These resolve external references to products such as DB2, WMQ, and CICS If you do not have optional software, then replace DDDEF library name with EDI.V3R3M0.SEDISTUB Allocate distribution and target libraries RECEIVE, APPLY, and ACCEPT Apply cumulative maintenance WebSphere Support Technical Exchange 6

7 Step 11: Creating v3.3 DB2 Objects Define TSO ID 'EDIENU33' with DB2 SYSADM authority Use this ID to create all objects via: 'SET CURRENT SQLID=EDIENU33' EDIENU33 is also the high-level qualifier (HLQ) Can use a different HLQ, but then SQLID creating objects must match HLQ EDIDB33E database is created with CCSID UNICODE Requires code page conversion services of z/os For details, see DB2 Installation Guide, Customizing support for Unicode WebSphere Support Technical Exchange 7

8 Step 11: (Cont d) Customers migrating from a previous release: Previous release must be executable for the duration of migration Subsequent jobs use v3.2 or v3.1 environment to export configuration data, e.g. maps, data formats, standards, etc. If installing on the same DB2 subsystem, a different SQLID with matching high-level qualifier must be used As provided, EDIENU32 is for v3.2 and EDIENU33 for v3.3 v3.2 customers must be at PTF level UK10658, dated Jan 10, 2006, or higher (in support of Business ID database changes) WebSphere Support Technical Exchange 8

9 Step 11: (Cont d) Sub-bullets 4 and 5 enable new features of v3.3 Support for server command submission from WDI Client v3.3 Remote PERFORM commands Document Store server processing, e.g. translation, transformation, and networking Bullet 4 - Configures DB2 stored Procedures Requires Work Load Manager (WLM) address space Bullet 5 - Adds OMVS external link for WDI command script interpreter If no need for these new features Remove stored procedure definitions from last section in EDI.V3R2M0.SEDISQL1(EDISDB2) Remove BIND PACKAGE(EDI33001) from EDI.V3R3M0.SEDIINS1(EDIJBIND) WebSphere Support Technical Exchange 9

10 Step 12-15: Complete DB2 activity Step 12 - Job EDIJRDLD loads DB2 Tables via DB2 utility procedure DSNUPROC Step 13 - Job EDIJRNST Runs RUNSTATS command via DB2 utility procedure DSNUPROC Step 14 - Job EDIJBIND binds the EDIENU33 DB2 Plan via IKJEFT01 utility EDIENU33 plan used for all WDI batch processing Also includes package bind for DB2 stored procedure Can remove BIND PACKAGE (EDI33001) if you will not be using new feature for server command submission Step 15 Member EDISGRNT grants authorization to DB2 objects via SPUFI WebSphere Support Technical Exchange 10

11 Step 16: Import Default Data Job EDIJDAT1 runs the WDI main utility program EDIFFUT Successful completion is verification that WDI 3.3 was installed correctly Sample Data transformation and functional acknowledgement maps, setup profiles, etc. are imported Does not migrate data from previous release WDI is now in a New Install state WebSphere Support Technical Exchange 11

12 Step 17 18: Migrate prior release data Migrates EDI standards, Data Formats, Maps, Control Strings, XML schemas and DTDs, Profiles, Code lists, and Translation tables Requires batch access to previous release Step 17 Builds a control file to be used to export from prior release (a) Job EDIJXPAD for v3.2 and v3.1 (using DB2) (b) Job EDIJXPAV for v3.1 using VSAM Step 18 Exports from prior release and imports into v3.3 (a) Job EDIJEXPD for v3.2 and v3.1 (using DB2) (b) Job EDIJEXVD for v3.1 using VSAM WebSphere Support Technical Exchange 12

13 Step 19: Verifying the installation WDI main utility program EDIFFUT was already used by EDIJDAT1 in Step 16, thus verifying basic batch processing Install WebSphere Data Interchange Client Set up Client Access to the z/os database client/server mode Uses DB2 Connect For More information see Chapter 2 of the WebSphere Data Interchange User's Guide (SC ) View or open each object type If new customer, default load data contains samples If existing customer, check each object type that would have been migrated from the previous version WebSphere Support Technical Exchange 13

14 Step 20: Operational changes (for prior release customers) Administrator's Menu removed from the z/os interface TSO CLIST and CICS EDIA support removed Functions now performed using WDI Client v3.3 Event logging on View menu Transaction Store replaced by new Document Store Supports similar features as Transactions Store Also captures information and images for Data Transformation (DT) in all three formats: EDI, XML and ADF Administrator s Menu functions for translating, enveloping, and networking, are enabled on WDI Client v3.3 via DB2 stored procedures in Step 11 Familiarize yourself with WDI Client v3.3 features WebSphere Support Technical Exchange 14

15 Step 20: Operational changes (Cont d) DT Functional Acknowledgment and Service Segment Validation maps shipped with WDI First character in names changed from $ to & WDI v3.3 Database is Unicode JCL changes Load library name changed to V3R3M0 DB2 plan name changed to EDIENU33 Point to new XML Toolkit version v3.1 customers Note API control block changes VSAM customers should use sample EDIUTILD in SEDISAM1 to recreate JCL WebSphere Support Technical Exchange 15

16 Step 21: Migrating Operational Data Special migration programs provided to migrate Transaction Store, Management Reporting, and SAP status data from WDI v3.2 No support for migrating from v3.1 Requires PTF UQ80131 / APAR PQ78335 to be applied to v3.2 Appendix B provides specific instructions: B.1 Binding the DB2 Plan for unload B.2 Granting Permission on the DB2 Plan for unload B.3 Unloading the WDI v3.2 Operational Data From WDI v3.2 B.4 Binding the DB2 Plan for Load Processing B.5 Granting Permission on the DB2 Plan for Load B.6 Loading the WDI v3.2 operational data into WDI v3.3 Designed to be re-run, i.e. will REPLACE ALL existing records in v3.3 WebSphere Support Technical Exchange 16

17 Step 22: Java API Support (Optional) Also known as Common Event Handler or Error notification Enables new Java API feature in WDI to send alerts (error notification) Involves USS (Unix System Services) commands from ISPF: ISHELL for menu-driven interface or OMVS for Unix-like interface Requires files to be defined under Hierarchical File System (HFS) Requires a user with an OMVS segment Requires IBM SDK for z/os, Java 2 Technology Edition, Version 1.4 SR(6) or higher WebSphere Support Technical Exchange 17

18 Step 22: Java API Support (Cont d) Jar files provided by WDI: edicevh.jar - Common Event Handling Java API edicevhsample.jar - Sample notification event handler with java source Configuration files requiring customization: env.profile - Java runtime environment variables for Java wdi.properties - default Common Event Handling properties Customize for the desired interface WebSphere Support Technical Exchange 18

19 Step 22: Java API Support (Cont d) Verify Java API installation with JCL EDIJCEH in SEDISAM1 Sends hard-coded text string to address in wdi.properties, which defaults to DummyEventHandler //EDIEVDS DD * MSG from: WDI Common Event Handler Java API verification job EDIJCEH. Check STDERRL and STDOUTL dd s for errors or for successful message: *** WDI Event Handler Installation Verified *** Last bullet (5) enables WDI notification (optional) Requires SMPT server URL or IP address, and the account id information Send text string using WDI Notify instead of DummyEventHandler WebSphere Support Technical Exchange 19

20 Chapter 3: Installing WDI for CICS CICS Transaction Server for z/os Version 2.3 (5697-E93) or later is required Enabling Language Environment (LE) in CICS Section Installing CICS support for Language Environment in the CICS Transaction Server for z/os Installation Guide Enabling C++ in CICS Section Language Environment support for C and C++ in the CICS Transaction Server for z/os Installation Guide CSD, DFHRPL, and I/O Stream considerations Section Preparing CICS for Use with z/os Language Environment in the z/os C/C++ Programming Guide WebSphere Support Technical Exchange 20

21 Chapter 3: Installing WDI for CICS (Cont d) For XML translations and/or Error Notification, Java SDK 1.4 Service Level SR(6) or later is required For XML, no need to install separate XML Toolkit embedded XML4J parser is used Follow steps to define various WDI elements to CICS If migrating from prior WDI release, do no use preexisting WDI definitions Step 34 enables XML support under CICS (optional) Step 35 enables Error Notification Support (optional) Some activities may have already been performed if you already enabled XML support WebSphere Support Technical Exchange 21

22 Additional WebSphere Product Resources Discover the latest trends in WebSphere Technology and implementation, participate in technically-focused briefings, webcasts and podcasts at: Learn about other upcoming webcasts, conferences and events: Join the Global WebSphere User Group Community: Access key product show-me demos and tutorials by visiting IBM Education Assistant: View a Flash replay with step-by-step instructions for using the Electronic Service Request (ESR) tool for submitting problems electronically: Sign up to receive weekly technical My support s: WebSphere Support Technical Exchange 22

23 Questions and Answers WebSphere Support Technical Exchange 23

24 Acronyms APAR Authorized Program Analysis Report ADF Application Data Format API Application Programming Interface CCSID Coded Character set identification CICS/TS Transaction Server CLIST Command list under TSO CSD CICS System Definition File DDDEF SMP/E term for dataset definition DT Data Transformation DTD Document Type Definition HFS HLQ ISHELL ISPF JAR LE OMVS PTF SDK SMP/E TSO XML USS WDI WMQ Hierarchical File Structure High-Level Qualifier ISPF Shell Interactive System Productivity Java archive file Language Environment Open MVS Program Temporary Fix Software Developer Kit System Modification Program/Extended Time-Sharing Option extensible Markup Language Unix System Services WebSphere Data Interchange WebSphere Message Queuing WebSphere Support Technical Exchange 24

25 Trademarks, copyrights, and disclaimers The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both: IBM CICS IMS WMQ Tivoli IBM(logo) Cloudscape Informix OS/390 WebSphere e(logo)business DB2 iseries OS/400 xseries AIX DB2 Universal Database Lotus pseries zseries Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are registered trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of Intel 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. Linux is a registered trademark of Linus Torvalds. Other company, product and service names may be trademarks or service marks of others. Product data has been reviewed for accuracy as of the date of initial publication. Product data is subject to change without notice. This document could include technical inaccuracies or typographical errors. IBM may make improvements and/or changes in the product(s) and/or program(s) described herein at any time without notice. Any statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. 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. Any reference to an IBM Program Product in this document is not intended to state or imply that only that program product may be used. Any functionally equivalent program, that does not infringe IBM's intellectual property rights, may be used instead. Information is provided "AS IS" without warranty of any kind. THE INFORMATION PROVIDED IN THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IBM EXPRESSLY DISCLAIMS ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IBM shall have no responsibility to update this information. IBM products are warranted, if at all, according to the terms and conditions of the agreements (e.g., IBM Customer Agreement, Statement of Limited Warranty, International Program License Agreement, etc.) under which they are provided. 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. IBM makes no representations or warranties, express or implied, regarding non-ibm products and services. The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents or copyrights. Inquiries regarding patent or copyright licenses should be made, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. The actual throughput or performance that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput or performance improvements equivalent to the ratios stated here. Copyright International Business Machines Corporation All rights reserved. Template Revision: 04/25/ :09 AM Note to U.S. Government Users - Documentation related to restricted rights-use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract and IBM Corp. WebSphere Support Technical Exchange IBM Corporation