Service flow runtime terminology

activity
One part of a process managed by CICS business transaction services. Activities implement the business logic. Typically, an activity is part of a business transaction and is executed by a normal CICS® transaction responding to CICS BTS events.
basic mapping support (BMS)
An interface between CICS and application programs that formats input and output display data and routes multiple-page output messages without regard for control characters used by various terminals.
business transaction
A self-contained business function; for example, the booking of an airline ticket. Traditionally, in CICS a business transaction might be implemented as multiple user transactions; the booking of the airline ticket might be undertaken by transactions that inquire about availability, reserve the seat, deal with payment, and print the ticket. Using BTS, a business transaction might be implemented as multiple activities.
Business Transaction Services (BTS)
An application programming interface and set of services for implementing complex business transactions in CICS.
CICS-supplied interface
An interface that is used by a controlling application to initiate a CICS program. An application can use one of three interfaces, ECI, EXCI, and EXEC CICS LINK, that are supplied by CICS.
compensation
The act of modifying the effects of a completed activity. The application designer decides how this is implemented, but it often involves the undoing, or reversing, of the actions that the activity took.
data-container
A named area of storage, maintained by BTS, and used to pass data between activities or between different invocations of the same activity. Each data-container is associated with an activity; it is identified by its name and by the activity for which is it a container. An activity can have any number of containers provided that they all have different names.
deployment pattern
A well-defined usage pattern that describes how a service will run in the target environment. Service flows can comply with a set of simple and complex deployment patterns.
enterprise information system (EIS)
The applications that comprise an enterprise's existing system for handling company-wide information. An enterprise information system offers a well-defined set of services that are exposed as local or remote interfaces or both.
enterprise information system interface
The data source in an enterprise information system; for example, 5250 and 3270 screens, COBOL record descriptions and transactions. Using service flow project tools, developers model and compose these interfaces into a more SOA compliant programming interface, enabling the enterprise to transform or adapt to a new set of operations and methods that move the application towards a service oriented architecture.
Link3270 bridge mechanism
A facility in CICS that provides a simplified interface using LINK, ECI, and EXCI. An application uses the Link3270 bridge to run 3270 transactions by linking to the DFHL3270 program in the router region and passing a COMMAREA that identifies the transaction to be run and contains the data used by the user application. If the target application uses BMS, the reply is presented in the form of an application data structure (ADS), another name for the symbolic map that is generated by the BMS macros used to define the mapping of the 3270 terminal screen.
persistence
A characteristic of data that is maintained across session boundaries, or of an object that continues to exist after the execution of the program or process that created it, usually in nonvolatile storage such as a database system.
process
In BTS, a collection of one or more activities. A process is the largest unit with which CICS business transaction services can work. It has a unique name by which it can be referenced and invoked. Typically, a process is an instance of a business transaction.
root activity
The activity at the top of the activity tree; that is, it has no parent activity. The root activity is the control program for a business transaction that represents the start and the end of the process. It initiates and controls a set of child activities.
runtime environment
The CICS region where the CICS Service Flow Runtime is installed and where a developer can deploy a service flow.
screen
In its native state, a screen represents the user interface to a 3270 or 5250 application on a host system. A single host application can contain many screens, each of which has a purpose in the context of the application. Screens contain both text and control or formatting functions, and traditionally display on 3270 or 5250 terminals.
service flow
A graphical representation of the sequence of activities performed in accordance with the business processes of an enterprise. A service flow consists of a graph of nodes, with defined entry and exit points where each node represents invoking a service operation, controlling the flow of the sequence, or performing reusable business logic.
Service-oriented architecture (SOA)
An architecture pattern that describes at a conceptual level the structure of a software system in terms of its components and the services they provide, without regard for the underlying implementation of these components, services, and the connections between components.
transaction
A unit of processing consisting of one or more application programs, affecting one or more objects, that is initiated by a single request.
transform
A change in the structure and values of data from one form to another. At build time, a developer can use service flow project tools to transform existing interfaces in an EIS to enable participation of EIS applications in an SOA.


dfhcr_htm_terms.html | Timestamp icon Last updated: Sunday, 4 June 2017