Access CA-IDMS from Java



Java applications may exchange data with any application running under CA-IDMS/DC/UCF.

Client/Server Communication

The VG-Java Client communicates with the VG-Application Server running under CA-IDMS/DC/UCF (see Servers and Client applications and VG-Application Server for more details)

Communication protocol is TCP/IP.


Java Client includes a Type 3 Pure Java JDBC driver.  The driver communicates with the VG-Application Server running under CA-IDMS/DC/UCF. The driver internally uses the Java Client API.

Database Support in JDBC

Applications can access CA-IDMS/SQL (CA Server is not needed) including table procedures and CA-IDMS/DML via stored procedures.
DB2 can be accessed via VEGA DB2 interface for CA-IDMS.

JDBC Driver Features

JDBC Driver Restrictions

JDBC Stored Procedures

JDBC Stored Procedure Functionality

There are always 3 call parameters

Required functions

Procedure output

Procedures write all output to a scratch area. There will always be at least one record that contains SQL Control Area (sqlca) The first record may be followed by optional data records. The last record is end-of-data record where sqlcode=100.
After the procedure returns, the VG-Application Server sends the data to VG-Java Client.

Java Client version 1.1 new features


This class can be used to start any available tool and sample application.


This class can be used to convert a CA-IDD record definition to a Java Class with optional SWING UI and/or to an XML definition.


This class can be used to upload a binary file (e.g. graphics or Java archive) into a CA-IDD load module.


Running the MsgAgent class is highly recommended to show VG-Application Server error messages especially during development and testing. The Server sends error messages to a non-zero port defined in VEGA.PROPERTIES.


This class executes a given DCMT/DCUF command or a selected command file.


The IdmsLogFrm class can be used to view selected CA-IDMS log records.