Browse Prior Art Database

Direct Talk to CICS Resource Access

IP.com Disclosure Number: IPCOM000112757D
Original Publication Date: 1994-Jun-01
Included in the Prior Art Database: 2005-Mar-27
Document File: 2 page(s) / 91K

Publishing Venue

IBM

Related People

Edwards, M: AUTHOR [+3]

Abstract

Disclosed is a connection between DirectTalk* and CICS*. It employs an architected and published interface between Voice Processing and Transaction Processing systems in place of 3270 emulation. Specifically, it uses CICS OS/2* and CICS/6000* to provide an interface (IF) between DirectTalk/2* and DirectTalk/6000*. Avoided is a less efficient IF, subject to constant change and maintenance costs.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 51% of the total text.

Direct Talk to CICS Resource Access

      Disclosed is a connection between DirectTalk* and CICS*.  It
employs an architected and published interface between Voice
Processing and Transaction Processing systems in place of 3270
emulation.  Specifically, it uses CICS OS/2* and CICS/6000* to
provide an interface (IF) between DirectTalk/2* and DirectTalk/6000*.
Avoided is a less efficient IF, subject to constant change and
maintenance costs.

      Current access to central hosts, especially CICS and its
pervasive applications and databases, from Voice Processing units
such as DirectTalk is via batch transaction interfaces, 3270
Emulation Servers or call transfer to CallPath*/MVS or VSE.  These
methods are error prone, slow in comparison to the needs of voice
telephony requirements, cumbersome to implement/maintain and not
available to all CICS platforms, e.g., no CP/CICS on AS/400*, RS/6000
or PS/2*.  There are also limitations in the number of simultaneous
sessions and hence transactions that can be handled.  The solution is
to connect Voice Processing Units such as DirecTalk to CICS
Transactions by making use of the facilities of the workstation,
through the CICS workstation products CICS/OS2 and CICS/6000.  Data
can be placed into or retrieved from the remote CICS system by means
of a CICS transaction generated locally by the Voice Processing Unit
that is executed on either the local workstation CICS or on the
remote CICS System using the LU6.2, TCP/IP or TR/EN protocols.  Local
access to CICS can be via the planned External Program Interface
(Transaction Routing) or External Call Interface (Function Shipping),
or even faster interaction can be achieved by using more direct
specific interfaces such as Inter Region Communication (or
equivalents).

      Some code is needed at the workstation to interface to the CICS
product in a 'transaction' input and 'data blocks' output mode.  This
requires application/CICS programming skills which are more likely to
be available than those to process the existing alternatives which
involve 3270 emulation screen capture and response by field
interrogation.  To interface to the direct interfaces would require
more specialist and scarce ISC or specific product interface skills.
In addition, the consent and participation of the products would be
required for details of any private interfaces and flows, as well as
commitmen...