The SAA Communications interface

When an application issues an SAA Communications call, control passes via the DFHCPLC application link-edit stub to the common programming interface program (DFHCPI), which in turn passes the request to the DFHCPIC program load module. DFHCPIC verifies the parameters, checks the conversation state, and (if required) issues a DFHLUC macro call to invoke the LU6.2 application request logic module (DFHZARL). For details of DFHZARL, see Distributed transaction processing.

Figure 1 shows how the SAA Communications interface support relates to CICS® intersystem communication (ISC) using z/OS® Communications Server LU6.2. The numbers in Figure 1 refer to the notes that follow it. CMxxxx represents a program call defined in the SAA Communications interface.
Figure 1. SAA Communications application request processing
When an application makes an EXEC CICS request using distributed transaction processing (DTP), it is handled by the EXEC interface component (involving DFHEIP, DFHEGL, DFHETC and DFHETL). When an application makes a CMxxxx application request, it is handled by the DFHCPIC load module within the CP component. Both the EXEC interface component and the CP component convert the application's requests into DFHLUC macro requests, that call DFHZARL (for a LU6.2 intersystem link). The SAA Communications interface also uses an RDO object called the PARTNER, encapsulated by the PR component.
Note:
  1. Distributed transaction processing (DTP) allows a transaction using EXEC CICS commands to communicate with a transaction running in another system. This is carried out by DFHEIP and related EXEC interface processor modules. For a z/OS Communications Server LU6.2 intersystem link, each request is converted into DFHLUC macro requests that call DFHZARL.
  2. The SAA Communications interface is implemented by the DFHCPIC load module within the CP (or CPI) component. DFHCPIC maps the CMxxxx application requests into DFHLUC macro calls.
  3. To begin a conversation, the SAA Communications interface requires specific information (side information) about the partner program, including its name and system details. This is implemented within CICS as an RDO object called the PARTNER, which is encapsulated by the partner resource manager (PR) component.


dfhs3c00898.html | Timestamp icon Last updated: Monday, 5 June 2017