Glossary

This glossary contains terms relevant to both CICS Service Flow Runtime and service flow project tools.

A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | #

A

access pattern
See deployment pattern.
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.
asynchronous
Pertaining to events that are not synchronized in time or do not occur in regular or predictable time intervals.
asynchronous processing
A means of distributing the processing of an application between systems in an intercommunication environment. The processing in each system is independent of the session on which requests are sent and replies are received. No direct correlation can be made between requests and replies and no assumptions can be made about the timing of replies.
auditing
Collecting and recording information about the state of the CICS Service Flow Runtime for the purpose of diagnostics and tracing. CICS Service Flow Runtime uses BTS facilities for auditing.
authentication
In computer security, verification of the identity of a user or process and the construction of a data structure that contains the privileges that were granted to the user or process.

B

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 process
A group of logically related activities that use the resources of the organization to provide defined results in support of the organization's objectives.
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 many 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.

C

CICS Business Transaction Services (CICS BTS)
A CICS domain that supports an application programming interface (API) and services that simplify the development of business transactions. Using BTS, each action that comprises the business transaction is implemented as one or more CICS transactions.
communication area (COMMAREA)
A CICS area that is used to pass data between tasks that communicate with a given terminal. The area can also be used to pass data between programs within a task.
compensation
The act of modifying the effects of a completed activity. How this is implemented is decided by the application designer, but often means the undoing, or reversing, of the actions that the activity took.
connector
A connector is a well-defined, durable communication or programming interface to an Enterprise Information System. A connector provides a means of accepting data in a definable format, invoking an operation, and receiving results in a definable format.

D

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 it is a container. An activity can have any number of containers, if they all have different names.
data conversion
The process of changing data from one form of representation to another.
deployment pattern
Sometimes referred to as an access pattern, a deployment pattern refers to the way in which a service flow complies with a set of well-defined usage patterns for processing in a supported runtime environment.
distributed program link (DPL)
A function of CICS intersystem communication that enables an application program to ship LINK requests to another application program on a different instance of CICS.

E

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
Represents 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 can model and compose these interfaces into a more SOA-compliant programmatic 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.

F

FEPI
See front end programming interface.
flow
See service flow.
flow navigator
A program that performs server adapter processing, managing states during the microflow processing and invoking server adapters in the correct order. The flow navigator is generated by service flow project tools.
front end programming interface (FEPI)
A separately installable function of CICS that enables CICS programs to interact with other 3270-based applications through virtual terminal sessions.

H

host
A computer system, such as a mainframe transaction processing system, on which EIS applications reside.
host application
An application residing on the host computer system.

I

importer
A component in the service flow project tools that is used to populate parts of the information model from existing resources. These resources can be data format definitions for messages or control blocks used by host applications, screen format definitions, for either entire screens or parts of screens, existing navigation information such as emulator macros, or captures of actual screens.
inline DPL
The use of a DPL command within a FEPI service flow that is modeled using the service flow project tools. This feature allows the generation of a FEPI server adapter that not only performs 3270 screen navigation, but also can connect to a back-end program for data access and processing using a distributed program link. See distributed program link.
interface
The contract between the service requester and the service provider expressed as a defined set of operations and the defined message formats for each operation. An Interface component describes sequences of messages that a service sends or receives or both. It does so by grouping related messages into operations. An operation is a sequence of input and output messages, and an interface is a set of operations. Thus, an interface defines the design of the application.

J

journal
A set of one or more data sets to which records are written during a CICS run.
journaling
The recording of information onto any journal (including the system log), for possible subsequent processing by the user.
Link3270 bridge
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 used 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.

M

message
A set of data that is passed from one application to another. A message can be modeled by a message definition, which describes the structure and content of the message. Messages must have a structure and format that is agreed by the sending and receiving applications.

O

operation
A service that can be requested from an object to effect behavior. A Web service can have multiple operations. An operation has a signature, which might restrict the actual parameters that are possible. EIS operations are generally not independent of each other.

P

persistence
An instance state 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 BTS can work and has a unique name by which it can be referenced and invoked.
process container
A data-container associated with a process. Process containers can be read by all the activities that make up the process. Note that they are not the same as the root activity's containers.

R

request message
A message sent by the service requester to invoke a service flow to process a business transaction.
Resource Access Control Facility (RACF®)
An IBM® licensed program that provides access control by identifying users to the system, verifying users of the system, authorizing access to protected resources, logging detected unauthorized attempts to enter the system, and logging detected accesses to protected resources. RACF is included in z/OS® Security Server and is also available as a separate program for the MVS™ and VM environments. In CICS Service Flow Runtime, RACF is used to make sure that a user has the authority to run a particular CICS DPL bridge task.
root activity
The activity at the top of the activity tree; 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 supported environment to which a service flow can be deployed.
run time
The time period during which an instance of a service flow is operational, where a business transaction is processed and completed in the CICS region.

S

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 as “green screens” on 3270 or 5250 terminals.
screen navigation
A form of data transfer between two application programs in which the first program accesses the second program through a terminal emulator or other communications program, and obtains data that appears at known screen locations if the second program was being accessed by a human operator.
server adapter
A program that is invoked to perform the business transaction activity defined in a service flow at build time.
service flow
A graphical representation of the sequence of activities that are 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 Flow Modeler
An eclipse-based application integration toolset that enables users to expose their existing applications as a service-like interface, facilitating the move to Service Oriented Architecture (SOA). Service Flow Modeler is available in the IBM Developer for z System z® product.
service provider
The collection of software that provides a Web service.
service provider application
An application that is used in a service provider. Typically, a service provider provides the business logic components of a service provider.
service requester
The collection of software that requests a Web service from a service provider.
service requester application
An application that is used in a service requester. Typically, a service requestor application provides the business logic component of a service requester.
synchronous
Relating to two or more processes that depend upon the occurrences of specific events, such as a common timing signal.

T

target application
An application that contains the data or information required to fulfill the business transaction.
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
To change 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 facilitate participation of EIS applications in an SOA.

W

Web service
A software system that supports interoperable machine-to-machine interaction over a network. It has an interface described in a machine-processable format; specifically, Web Service Description Language, or WSDL.
Web service description
An XML document by which a service provider communicates the specifications for invoking a Web service to a service requester. Web service descriptions are written in Web Service Description Language (WSDL).
Web Services Definition Language (WSDL)
An XML application for describing Web services. It separates the descriptions of the abstract functions offered by a service and the concrete details of a service, such as how and where that function is offered.

#

3270 data stream
The commands, control codes, orders, attributes, and data or structured fields for 3270 devices that are transmitted between an application program and a terminal. Data being transferred from or to an allocated primary or tertiary device, or to the host system, as a continuous stream of data and 3270 Information Display System control elements in character form.


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