Defining intrapartition transient data queues

An intrapartition transient data queue can be defined as shown:

Figure 73. Defining an intrapartition transient data queue
DEFINE
  TDQUEUE(name)
  GROUP(groupname)
  DESCRIPTION(text)
  TYPE(Intra)
  Intrapartition Attributes
  ATIFACILITY(terminal)
  RECOVSTATUS(logical)
  FACILITYID (terminal)
  RECOVSTATUS(name)
  TRANSID ()
  TRIGGERLEVEL(value)
  USERID(userid)
  Indoubt Attributes:
  WAIT(yes)
  WAITACTION(reject)
        ...

For further information about defining transient data queues, see the CICS® Resource Definition Guide. This section is concerned with the CICS intercommunication aspects of queues that:

Transactions

A transaction that is initiated by an intrapartition transient data queue must reside on the same system as the queue. That is, the transaction that you name in the queue definition must not be defined as a remote transaction.

Principal facilities

The principal facility that is to be associated with a transaction started by ATI is specified in the transient data queue definition. A principal facility can be:

Local terminals

A local terminal is a terminal that is owned by the same system that owns the transient data queue and the transaction.

For any local terminal other than an APPC terminal, you need to specify a destination of terminal, and give a terminal identifier. If you omit the terminal identifier, the name of the terminal defaults to the name of the queue.

Remote terminals

A remote terminal is a terminal that is defined as remote on the system that owns the transient data queue and the associated transaction. Automatic transaction initiation with a remote terminal is a form of CICS transaction routing (see CICS transaction routing), and the normal transaction routing rules apply.

For any remote terminal other than an APPC terminal, specify a destination of terminal and a terminal identifier.

The terminal itself must be defined as a remote terminal (or a shipped terminal definition must be made available), and the terminal-owning region must be connected to the local system either by an IRC link or by an APPC link.

Local sessions and APPC devices

You can name a local connection definition in the definition for the transient data queue. The remote system can be connected by IRC, LUTYPE6.1, or APPC link. In the APPC case, "system" can be a hard-coded terminal-like device.

CICS allocates a session on the specified system, which becomes the principal facility to transid. The transaction program converses across the session using the appropriate DTP protocol. Read Distributed transaction processing for an introduction to DTP.

The transaction starts in ‘allocated’ state on its principal facility. Then it identifies its partner transaction; that is, the process to be connected to the other end of the session. In the APPC protocol, it does this by issuing the EXEC CICS CONNECT PROCESS command, a command normally only used to start a conversation on an alternate facility.

The partner transaction, having been started in the back end with the conversation in receive state, also sees the session as its principal facility. This is unusual in that CICS treats either end of the session as a principal facility. On both sides, the conversation identifier is taken from EIBTRMID if needed, but it is also implied on later commands, as is the case for principal facilities.

Remote APPC sessions and devices

A remote connection is defined as remote on the system that owns the transient data queue and the associated transaction. Automatic transaction initiation with a remote APPC connection is a form of CICS transaction routing (see CICS transaction routing), and the normal transaction routing rules apply.

You can name a remote connection in the definition for the transient data queue.

The connection itself must be defined as a remote connection (or a shipped connection definition must be made available), and the terminal-owning region must be connected to the local system either by an IRC link or by an APPC link. The remarks in Local sessions and APPC devices about handling the link after transaction initiation apply also to routed transactions.

Related concepts
Architected processes
Related tasks
Defining communication profiles
Selecting required resource definitions for installation
Defining local resources for DPL
Defining remote resources
[[ Contents Previous Page | Next Page Index ]]