Notes on terminology

In this book, VTAM® refers to ACF/VTAM and IMS™ refers to IMS/VS and IMS/ESA®. The term "CICS", without any qualification, refers to the CICS® element of IBM® CICS Transaction Server for z/OS®.

CICS Transaction Server for z/OS, Version 3 Release 1 supports CICS applications written in:

In this book, the phrase "the languages supported by CICS" refers to the above languages.

KB equals 1024 bytes; MB equals 1024KB.

The following terms have different meanings for FEPI, CICS, IMS, and VTAM:

application
FEPI uses application in the normal sense of a program or suite of programs that do work. VTAM uses application for programs that communicate directly using VTAM; in a FEPI environment, this means the back-end systems on one hand, and FEPI on the other.
conversation
A FEPI conversation is not the same as an IMS conversation, although they would normally coincide, and it is not related to CICS conversational mode. It is analogous to a CICS APPC conversation.
inbound, input
In FEPI and CICS usage, these describe data received by a program from elsewhere. From the point-of-view of the back-end system, this data is outbound or output to a terminal.
message
VTAM and IMS use message to refer to any data transmission, and not just to data displayed for a user’s attention.
node
In VTAM and IMS, a node is a named point in a network. In FEPI, nodes are those points (VTAM nodes) that are the secondary LU terminals simulated by FEPI.
outbound, output
In FEPI and CICS usage, these describe data sent by a program to somewhere else. From the point-of-view of the back-end system, this data is inbound or input from a terminal.
secondary
In VTAM, secondary describes one of the partners of an LU-LU pair; the terminals simulated by FEPI are secondary LUs. This is not the same as the CICS usage of secondary.
[[ Contents Previous Page | Next Page Index ]]