Demo

Enterprise COBOL and Java Interoperation

Nick Tindall Stephen Miller August 14, 2003

Objectives for IBM Object Oriented COBOL
• Enable fine-grained interoperation of COBOL and Java within an address space, both: – COBOL invocation of Java – Java invocation of COBOL Complement existing COBOL:Java interoperation – mediated by middleware, based on connectors – COBOL and Java running indifferent address spaces or machines – only for COBOL transactions Fine-grained interoperation (interlanguage communication) provides: – better performance – use of non-transactional COBOL Improve integration of COBOL with WebSphere Application Server – COBOL client invocation of enterprise beans – Future support for COBOL execution within WebSphere server regions

•

•

•

August, 2003

2Example scenarios
• • • • Enhance existing COBOL routines to access new business logic written in Java Write new business logic in Java, access existing libraries of production COBOL routines New business logic written in Java can invoke COBOL routines to process existing COBOL data in QSAM/VSAM files COBOL programs can invoke Java for full-function XML parsing – (use new direct COBOL supportfor high-speed parsing of input XML documents!) COBOL programs can invoke methods (directly) on enterprise beans running in a WebSphere server region - or COBOL programs can invoke Java routines, which act as J2EE clients accessing enterprise beans Write new IMS message processing or database logic in Java, mixing with COBOL to leverage existing IMS COBOL applications and IMS programming skills
3•

•

August, 2003

Prerequisite technologies for Java interoperation
• • • • • • • Basic C interoperability and DLL support Basic development-time and run-time support for z/OS Unix Multi-thread enablement Asynchronous signal toleration Unicode Function pointers IEEE floating point

August, 2003

4

Delivery
IBM COBOL for OS/390 & VM • C interoperability and DLL support • Basicdevelopment-time and run-time support for z/OS Unix IBM Enterprise COBOL for z/OS and OS/390 V3R1, GA 11/2001 • Multi-thread enablement • Asynchronous signal toleration • Unicode • Function pointers • Java interoperation, USS and batch environments (BPXBATCH) • COBOL client code invoking enterprise beans running in WebSphere 390 IBM Enterprise COBOL for z/OS and OS/390 V3R2, GA 9/2002 • Javainteroperation in IMS environment • COBOL class with "main" method • Parameterized JVM initialization - user-specified JVM options • OPTIMIZE option for programs using OO syntax for Java interoperability • Execution of OO applications from batch JCL
August, 2003 5

Unicode
• Basic run-time Unicode datatype support – USAGE NATIONAL clause – PICTURE character N mapped to UTF-16 – Unicode literals -N'Straße', N'αβγ', NX'03B103B203B3' – Implicit conversions in mixed operations – Binary collation CODEPAGE() compiler option - specifies EBCDIC code page for: – alphanumeric and DBCS data items at run time – alphanumeric, national, and DBCS literals in the source program NSYMBOL(NATIONAL|DBCS) – provides compatibility with existing DBCS support Enable: – Exchange of String data between Java andCOBOL – Invocation of Java methods with Unicode method names – COBOL methods with Unicode method names – Override/overload Java methods that have Unicode method names
6

•

• •

August, 2003

Java Interoperation
• Existing OO COBOL syntax re-based on Java, and the Java Native Interface (JNI) – COBOL INVOKE statement maps onto Java JNI calls – COBOL class and method definitions defineJava native methods – SOM-based OO COBOL support removed - SOMObjects has been removed from z/OS • Documentation and assistance in mapping Java data types to/from COBOL • Support for JNI programming in COBOL • COBOL COPY file analogous to jni.h, enables access to JNI callable services • Java prerequisite: IBM Java 2 Technology Edition SDK 1.3.0

August, 2003

7

Client-side syntax
Declare...