DataDirect's OCA-TCP/IP provides the IDMS developer access to IBM's Socket Extended API. The high performance implementation of TCP/IP sockets offers new integration flexibility into IDMS functionality and options for communicating from IDMS to other sockets applications.
Product Description
DataDirect's IDMS Extension OCA-TCP/IP closely follows IBM's implementation of sockets under CICS. All socket calls are identical under both products (IDMS and CICS). OCA-TCP/IP supports all IBM Socket Extended API calls. The interface program can be invoked using either a static CALL or a dynamic #LINK. Because the OCA socket interface program can be invoked either statically or dynamically, all programming languages supported by IDMS can be used, including ADS/Online.
Key Features
Easy communication with other platforms
Communicating with other platforms using sockets is very easy. All platforms have a socket interface that can be invoked using most programming languages. Even though the socket calls themselves are not identical on all platforms, they use the same underlying protocol, so all programs that have access to a socket interface can communicate with each other.
In some cases, an ASCII-EBCDIC conversion has to be performed for character strings. Routines are provided as part of IBM's TCP/IP to convert to and from ASCII. Both routines can be safely called from within IDMS.
Perfect integration with your Internet/Intranet strategy
Because the Internet is a TCP/IP network, any language application or applet can communicate directly with an IDMS application through the Internet or your Intranet. Direct communication is possible between the client and the server without any need for protocol conversion.
Two OCA listeners provided for added convenience
A Listener is a program that bides its time, waiting for connection requests. When a remote program wants to initiate an IDMS task, the OCA Listener sends a specially formatted packet that contains, amongst other things, the task id and optional data such as security information. The Listener receives the packet, initiates the task and passes the new socket to the new task. Then it proceeds to wait for additional connection requests.
There are two listeners provided with OCA-TCP/IP. One listener expects incoming data in EBCDIC format and the other expects ASCII data. These concurrent listeners can handle multiple concurrent requests. Requests from many concurrent users can be processed in parallel instead of queued one after each other.
OCA-TCP/IP has been designed to take advantage of multiprocessing. Almost all of the additional cycles required by socket calls are executed by MVS subtasks. The result is that the additional workload can be shared between all the processors in the partition, with minimal impact on the CA-IDMS environment.
Custom security
When security has to be enforced, the Listeners can invoke a user-written security exit before initiating the requested task. The exit can perform the security check itself and/or provide a user id under which the task will be executed.
| More Information | |||||||||||||||||||||||||||
|