The following operators can be used to better focus your queries.
( ) , AND, OR, NOT, W/#
? single char wildcard, not at start
* multi char wildcard, not at start
(Cat? OR feline) AND NOT dog?
Cat? W/5 behavior
(Cat? OR feline) AND traits
Cat AND charact*
This guide provides a more detailed description of the syntax that is supported along with examples.
This search box also supports the look-up of an IP.com Digital Signature (also referred to as Fingerprint); enter the 72-, 48-, or 32-character code to retrieve details of the associated file or submission.
Concept Search - What can I type?
For a concept search, you can enter phrases, sentences, or full paragraphs in English. For example, copy and paste the abstract of a patent application or paragraphs from an article.
Concept search eliminates the need for complex Boolean syntax to inform retrieval. Our Semantic Gist engine uses advanced cognitive semantic analysis to extract the meaning of data. This reduces the chances of missing valuable information, that may result from traditional keyword searching.
This article presents a new concept in the CICS* application programming interface that will enhance the facilities to componentize applications implemented in the major procedural programming languages in that environment.
English (United States)
This text was extracted from a PDF file.
This is the abbreviated version, containing approximately
52% of the total text.
Page 1 of 2
Dynamic interface definition, construction and use in Enterprise Applications
Many Enterprise business applications have been written using procedural
languages such as COBOL or PLI and these applications are still being maintained
and extended today - it will be many years before COBOL application programming
ceases to be a major activity in many businesses.
Today's mechanisms for structuring the interfaces between modules in a
COBOL program are very static and brittle. This makes it difficult to evolve the
modules at the rate demanded by the business environment. As well as being static,
the interface definition mechanisms do not provide useable techniques to structure
the interfaces to promote modularity.
Today, a COBOL service module, particularly when hosted in CICS*, often
has a single flat structure defining its interface (in CICS called a COMMAREA). This
results in a very tight coupling between the calling logic and the service module.
In CICS, such an interface is also limited to passing less than 32K of data
across the interface. Increasing the volume of data passed across the interface
without introducing further structuring is likely to increase the complexity of the
application design and implementation since how to structure the larger amount of
data will be an application developer task.
The invention described provides a simple, yet powerful, structuring
mechanism that can be used to describe interfaces to modules in any procedural
language. The mechanism is a simple evolution of the existing techniques which will
make it easy for current application developers to adopt.
The new mechanism introduces a collection of named flat structures to carry
the data across the module interface boundary. Each flat structure is named and the
collection is named. (In the current CICS implementation in CICS Transation Server
V3.1, the flat structures are called containers and the collection a channel).
The interface can be defined in a file (a copybook in COBOL parlance) in the
same fashion as a COMMAREA. The file defines the names of the containers and
the type declarations of the structures to be placed in the containers. An interface
may also define multiple channel names for...