|
Support for Deferred Program Switching in Conversational JMP Applications
Version 8: UK00226
Version 9: UK01518
You can now make a deferred program switch in a conversational JMP application. A deferred program switch changes the transaction code in the SPA before the SPA is returned to IMS. When an application makes a deferred program switch, the application replies to the terminal and passes the conversation to another conversational application.
The setTransactionID(String) method of the com.ibm.ims.application.IMSFieldMessage class specifies the transaction code in the SPA.
Detailed information is available in the following guides:
Support for DB2 UDB for z/OS Data Access from JMP and JBP Regions
Version 8: UQ80615
JMP and JBP applications can now access DB2 databases that are on the same z/OS image. For JMP or JBP applications to have DB2 access, attach DB2 to IMS using the DB2 Recoverable Resource Manager Services attachment facility (RRSAF). Unlike other dependent regions, JMP and JBP regions do not use the External Subsystem Attach Facility (ESAF).
A JMP or JBP application can access DB2 databases using the DB2 JDBC/SQLJ 2.0 driver or the DB2 JDBC/SQLJ 1.2 driver.
Detailed information is available in the IMS Version 8: IMS Java Guide and Reference.
Support for IBM WebSphere Application Server V5.0 for z/OS
Version 8: UQ77449
IMS Java Version 8 now supports WebSphere Application Server V5.0 for z/OS. In addition to WebSphere Application Server V4.0.1 for z/OS, EJBs deployed on WebSphere Application Server V5.0 for z/OS can access IMS databases directly through Open Database Access (ODBA).
To deploy an EJB that accesses IMS on WebSphere Application Server V5.0 for z/OS, perform the following steps:
- Configure the WebSphere Application Server for z/OS J2EE server to access IMS, which needs to be done only once.
- Install the IMS JDBC resource adapter, which needs to be done only once.
- Install the custom service.
- Install the data source, which needs to be done for each application.
- Install the application.
Detailed information is available in the IMS Version 8: IMS Java Guide and Reference.
Support for Enterprise COBOL Interoperability
Version 7: UQ75641
Version 8: UQ74520
Enterprise COBOL for z/OS and OS/390 Version 3 Release 2 supports interoperation between COBOL and Java languages when running in a JMP or JBP region. With this support, you can: - Call an object-oriented (OO) COBOL application from an IMS Java application by building the front-end application, which processes messages, in Java and the back end, which processes databases, in OO COBOL.
- Build an OO COBOL application containing a main routine that can invoke Java routines.
You can access COBOL code in a JMP or JBP region because Enterprise COBOL provides object-oriented language syntax that enables you to:
- Define classes with methods and data implemented in COBOL.
- Create instances of Java and COBOL classes.
- Invoke methods on Java and COBOL objects.
- Write classes that inherit from Java classes or other COBOL classes.
- Define and invoke overloaded methods.
In Enterprise COBOL programs, you can call the services provided by the JNI to obtain Java-oriented capabilities in addition to the basic OO capabilities available directly in the COBOL language. In Enterprise COBOL classes, you can code CALL statements that interface with procedural COBOL programs. Therefore, COBOL class definition syntax can be especially useful for writing wrapper classes for procedural COBOL logic, enabling existing COBOL code to be accessed from Java.
Java code can create instances of COBOL classes, invoke methods of these classes, and can extend COBOL classes.
Detailed information is available in the IMS Version 8: IMS Java Guide and Reference.
|
