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.

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.



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