Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Expansion of EHLLAPI to Include 3270 Structured Field Functions

IP.com Disclosure Number: IPCOM000102360D
Original Publication Date: 1990-Nov-01
Included in the Prior Art Database: 2005-Mar-17
Document File: 1 page(s) / 44K

Publishing Venue

IBM

Related People

Covey, E: AUTHOR [+3]

Abstract

Disclosed is an addition to the Emulation High Level Language Application Programming Interface (EHLLAPI) product to allow an application running on the workstation to communicate directly with an application running on a 3270-type host using architected 3270-structured field conventions.

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

Expansion of EHLLAPI to Include 3270 Structured Field Functions

       Disclosed is an addition to the Emulation High Level
Language Application Programming Interface (EHLLAPI) product to allow
an application running on the workstation to communicate directly
with an application running on a 3270-type host using architected
3270-structured field conventions.

      Eight new functions have been added to EHLLAPI to allow 3270
destination/orgin and DDM-type structured field communications.
Structured field communications allow for packaging of data into an
architected format for direct transmission between the workstation
and host-based applications. One of the major uses of these functions
is in the development of customized high performance file
transfer-type applications. Data transfer in both directions is
supported over a variety of buffer sizes. Following are a list of the
new functions and a brief description:
     1. Connect for Structured Fields (120)
        - Establish a data transfer session.  Multiple Query Reply
types identifying the type of application are supported.
     2. Disconnect from Structured Fields (121)
        - Sever an existing data transfer session.
     3. Query Communication Buffer Size (122)
        - Determine optimal and maximum transmission sizes for data
transfer.
     4. Allocate Communications Buffer (123)
        - Obtain shared memory for data transmission/reception.
     5. Fre...