ACB—see Application Control Block
ACBGEN—see Application Control Block Generation
alternate program communication block
A TP PCB, defined by the user, that can be used to describe output message destinations other than the terminal that originated the input message. Where SAMETRM=YES is not implicitly or explicitly specified, an alternate PCBs destination can be either a logical terminal or an input transaction queue.
APPC—see Advanced Program-to-Program Communications
APPC/IMS
A part of the IMS Transaction Manager that uses the CPI communications interface to talk to application programs.
APPLCTN Macro
An IMS macro that defines the process resource requirements for an application that runs under the control of IMS/DC and those applications that access databases through DBCTL. An APPLCTN macro combined with one or more TRANSACT macros defines the scheduling and resource requirements for an IMS application program.
Application Control Block Generation (ACBGEN)
The process by which the application control blocks in IMS are generated.
Application Control Block (ACB)
An IMS control block created from the output of DBDGEN and PSBGEN and placed in the ACB library for use during online and DBB region type execution of IMS.
Base Primitive Environment (BPE)
A system-service-layer of IMS that provides a common set of system services (such as storage management, tracing, and dispatching) to various components such as the IMS Common Queue Server (CQS) and IMS Client Server Object Manager (IMS CSobject) and IMS Connect.
Batch Message Processing (BMP) program
An IMS batch processing program that has access to online databases and message queues. BMPs run online, but like programs in a batch environment, they are started with job control language (JCL).
batch-oriented BMP program
A BMP program that has access to online databases and message queues while performing batch-type processing. A batch-oriented BMP does not access the IMS message queues for input or output. It can access online databases, GSAM databases, and MVS files for both input and output. Contrast with transaction-oriented BMP.
batch processing program
An application that has access to databases and MVS data management facilities but does not have access to the IMS control region or its message queues. (See also batch message processing program and message processing program.)
BPE—see Base Primitive Environment
BMP—see Batch Message Processing Program
class
An attribute related to a transaction code and a message region that is used to determine scheduling. (See also message class and region class.)
cold start
An IMS system start type that results in IMS being initialized for the first time or when some error condition prevents a warm or emergency restart. (See also emergency restart and normal restart.)
control program (IMS)
An IMS program that initiates and controls the major IMS facilities, such as IMS database, telecommunications, and message scheduling.
control region
An MVS main storage region that contains the IMS control program.
conversation
A dialog between a terminal and a message-processing program that uses IMS conversational processing facilities. A conversation can also be a dialog between an LU 6.2 program and an IMS application program. (See also conversational processing.)
conversational processing
A programming style letting a user's application program accumulate information acquired through multiple interchanges with a terminal, even though the program terminates between interchanges.
CSQQTRMN
The MQSeries supplied IMS application that monitors an MQSeries initiation queue and starts an IMS transaction when an MQSeries event occurs on that queue.
Data Base Description (DBD)
A collection of macro statements that define the characteristics of a database, such as the database's organization and access method, the segments and fields in a database record, and the relationship between types of segments.
Data Base Description Generation (DBDGEN)
A DBDGEN is the process by which a DBD is created.
Data Base Program Communication Block (DBPCB)
A control block that describes an application program's interface to a database. One DBPCB is required for each database view used by the application program.
Data Communications Control (DCCTL)
A subsystem that lets the IMS Transaction Manager act as a stand-alone, full-function transaction manager that can connect to DB2 or other external subsystems.
DBD—see Data Base Description
DBDGEN—see Data Base Description Generation
DBPCB - see Data Base Program Communication Block
data store
An IMS Transaction Manager system that provides transaction and database processing.
dependent region
An MVS virtual storage region that contains MPPs, BMPs, MDPs, or online utilities.
emergency restart
A restart of IMS following an IMS or MVS failure.
group member
The name of an entity that joins an XCF group and communicates with IMS using the OTMA protocol. A member can be either a server (IMS) or a client.
IMS Connect
An MVS gateway application program that uses TCP/IP communications to TCP/IP clients or Web browsers and IMS OTMA communication to IMS.
IMS Connect Base Primitive Environment (IMS Connect BPE)
A system service component that underlies the address space of IMS Connect.
IMS DB
An IMS licensed program capable of processing concurrent data base calls and offers high performance for a variety of applications, ranging from those with moderate volume and complex data structures to those with extremely high volumes and simple data structures.
IMS—see Information Management System
IMS Open Transaction Manager Access (OTMA)
OTMA is connectionless client/server protocol used to communicate with IMS transaction programs.
IMS request message (IRM)
A structured IMS message that passes required IMS data and user message exit data to IMS Connect. Both the user message exits and IMS Connect use the IRM.
IMS Transaction Manager
The data communication system used within IMS to provide high-volume, high-performance, high-capacity, low-cost transaction processing for both IMS DB and DB2 databases.
Information Management System (IMS)
An IBM transaction processing product that consists of several system environments available with Database Manager and Transaction Manager, capable of managing complex databases and terminal networks.
Input/Output Program Communication Block (I/O PCB)
A DC-PCB provided automatically by IMS to an application program that executes in a communication system with the DC feature. The I/O PCB is the mechanism by which a program obtains an input message from a terminal and returns a reply to the terminal that originated the input message. (See also alternate program communication block.)
IRM—see IMS request message
line response mode
A variation of response mode where all operations on the communication line are suspended while the application program output message is being generated. See also response mode and terminal response mode.
LTERM—see Logical Terminal
Logical Terminal—LTERM
A symbolic name in IMS that is mapped to a VTAM LU or BTAM physical terminal.
message control information
The part of the OTMA message prefix that is not contiguous with the rest of the message prefix.The Message Control Information must be specified for every OTMA message, and contains such information as the transaction pipe name and the message type.
Message Processing Program (MPP)
An IMS application program that is driven by transactions and has access to online IMS databases and message queues. (See also batch message processing program and batch processing program.)
message class
A class, assigned to a transaction code, that determines within which message region an application program is to process that transaction. (See also region class.)
message queue
The data set on which messages are queued before being processed by an application program or sent to a terminal.
MPP—see Message Processing Program
MVS Extended Coupling Facility (XCF)
A component of MVS that provides functions to support cooperation between authorized programs running within a sysplex.
non-persistent socket connection
A connection between the client and IMS Connect that lasts for a single exchange of one input-and-output pair. IMS Connect terminates a non-persistent socket connection after sending each output message. IMS Connect requires the client application to reconnect before sending each input, and to terminate the connection after receiving each output. This socket connection was intended to support IMS Web connections.
normal restart
An IMS system start type that reinitializes and activates IMS. A normal restart can occur after a termination that was initiated by a /CHECKPOINT command.
Open Transaction Manager Access
A connectionless client/server protocol used to communicate with IMS transaction programs.
OTMA—see Open Transaction Manager Access
password security
IMS processing that makes use of system macros and security maintenance utility control statements to restrict the use of IMS resources (databases, application programs, physical and logical terminals, transactions, and commands) to a person or persons who can supply the correct password.
PCB—see Program Communication Block
persistent socket connection
A long-lived connection that exists between the client and IMS Connect and can last for multiple transactions. Either the client or IMS Connect can terminate a persistent socket connection.
primary request
In an MSC network, a message entered into a terminal before it is processed. See also secondary request and response.
Program Communication Block (PCB)
An IMS control block that describes an application program's interface to and view of an IMS database. For message processing and batch message processing programs, a PCB describes the source and destinations of messages. PCBs are defined during PSB generation. (See also data base program communication block and telecommunication-program program communication block.)
Program Specification Block (PSB)
An IMS control block that describes databases and logical message destinations used by an application program. A PSB consists of one or more PCBs.
Program Specification Block Generation (PSBGEN)
An IMS process by which a PSB is created.
PSB—see Program Specification Block
PSBGEN—see Program Specification Block Generation
region class
An IMS class that is assigned to a message region and indicates the message classes that can be processed within the region. (See also message class.)
reply
Synonymous with response in a non-VTAM environment.
response
A response is a message inserted to a logical terminal destination specified by an I/O PCB or an alternate response PCB. When VTAM is used, the term "reply" is substituted for "response" because response has a separate meaning in VTAM communications. (See also primary request, secondary request, and reply.)
Response Alternate PCB
An alternate PCB that is a synonym for alternate response PCB.
response mode
A mode of IMS terminal operation that synchronizes operations between the terminal operator and the application program. When IMS receives an input transaction that causes response mode to be entered, no more input is allowed until the application program response has been transmitted back to the terminal. (See also line response mode and terminal response mode.)
secondary request
In a multi-system environment, a message inserted to a transaction code destination by an application program. See also primary request and response.
server
A member of an XCF group that uses the OTMA protocol.
synchronization phase
An XRF phase, immediately after initialization, when the alternate builds the IMS control blocks to mirror those in the active.
telecommunication-program program communication block (TP PCB)
The PCB that supports communication between an application program and a terminal or other application program. There are two types of TP PCBs: I/O PCB and alternate PCB.
terminal response mode
The type of response mode that suspends all input operations from the terminal until the application program has generated the output message. See line response mode.
termination phase
An XRF phase in which a subsystem shuts down.
TM—see IMS Transaction Manager
Tmember
The name of a client that connects to an OTMA group.
TRANSACT macro
An IMS macro that is used during a PSBGEN to identify the transaction codes associated with an application program previously named in a preceding APPLCTN macro. The applications identified in TRANSACT macros are scheduled for execution in an IMS message processing region. The TRANSACT macro also provides the IMS control program with information that influences the application program scheduling algorithm. It can define a message editing routine. The following TRANSACT macro arguments specify attributes of the associated transaction:
EDIT= Specifies whether the input (ULC) data is to be translated to uppercase. The first parameter of this operand defines whether the transaction is uppercase/lowercase (ULC) as entered from the terminal, or if it is to be translated to uppercase (UC) before being presented to the processing program. The default is UC.
MSGTYPE Specifies the type of transaction code (single or multiple segment), and whether the communication line from which the transaction is entered is to be held until a response is received. The MSGTYPE operands are not position dependent.
MULTSEG Specifies that the incoming message can be more than one segment in length. It is not eligible for scheduling to an application program until an end-of-message indication is received, or a complete message is created by MFS.
SNGLSEG Specifies that the incoming message is one segment in length. It becomes eligible for scheduling when the terminal operator indicates end-of-segment.
NONRESPONSE Specifies that, for terminals specifying or accepting a default of OPTIONS=TRANRESP, input should not stop after this transaction is entered.
RESPONSE Specifies that, for terminals specifying or accepting a default of OPTIONS=TRANRESP, no additional messages are to be allowed after this transaction is entered until this transaction sends a response message back to the terminal. Response mode can be forced or negated by individual terminal definition.
transaction
A specific set of input data that triggers the execution of a specific process or job. A transaction is a message destined for an application program.
transaction code
A 1- to 8-character alphanumeric code associated with an IMS message-processing program. The transaction code is used to invoke the MPP.
transaction command security
IMS processing that makes use of system macros and security maintenance utility control statements to permit specific application programs to issue some of the IMS operator commands.
transaction load balancing
Optional processing within IMS that enables a transaction to be scheduled into more than one message, or batch message, region at the same time.
transaction-oriented BMP
A BMP that performs transaction-type processing in a batch environment. A transaction-oriented BMP gets its input from the IMS message queues and can use the message queues for output. Contrast with batch-oriented BMP.
transaction pipe
A named IMS process management resource. An OTMA client must specify this resource when submitting a transaction to IMS. A Tpipe is analogous to an LTERM.
transaction socket connection
A connection between the client and IMS Connect that lasts for a single transaction. A transaction socket connection is terminated at the end of the transaction.
Unit of Work (UOW)
(1) For IMS DB, unit of work encompasses all the input and output messages associated with a transaction. (2) For IMS TM, UOW is a single IMS message. (3) For CQS, UOW is a client-defined grouping of data objects. (4) In advanced-program-to-program communication (APPC), UOW is the amount of processing that is started directly or indirectly by a program on the source system.
user message exit
An IBM supplied or user-written program that converts client message format to OTMA message format before IMS Connect sends the message to IMS. The same program converts OTMA message format to client message format before sending the message back to IMS Connect to send to the client.
warm start
An IMS start type that is synonymous with a normal IMS restart.
XCF - see MVS Extended Coupling Facility
XCF group
A logical collection of XCF members.The datastore (an IMS MPP) and IMS Connect must join to the same XCF group.
XCF member
An MVS application that joins an XCF group.
|
Copyright © 2014 CA.
All rights reserved.
|
|