In CICS® ONC RPC, the CICS programs are identified by a 4-tuple.
- Program number--same as the ONC RPC program number
- Version number--same as the ONC RPC version number
- Procedure number--same as the ONC RPC procedure number
- Protocol--determined by the protocol
used to communicate between the client system and TCP/IP for MVS™.
When a client request arrives, the CICS program chosen to service it is the one
associated with the 4-tuple just described. Figure 34 shows a
state of CICS ONC RPC in which five 4-tuples are associated with three CICS programs.
The program numbers are given in hexadecimal. The protocols are U for UDP
and T for TCP.
- If a client request arrives for program 24127AC0, version 5, procedure
1, the CICS program PROGA is used to service it whether the protocol is TCP
or UDP.
- If a request arrives for program CE00457F, version 3, procedure 1, and
the protocol is UDP, the CICS program PROGB is used to service it. But if the same
request arrives and the protocol is TCP, PROGC is used to service it.
It is, however, usual to use the same program, version, and procedure irrespective
of the protocol used to transmit the request.
- The CICS program PROGC is also used for procedure 2 of the same program and
version if the protocol is TCP.
How you set up and control the relationship between 4-tuples and CICS programs is
described in Configuring CICS ONC RPC using the connection manager.
The CICS program might be in one of three places:
- In the same CICS region as CICS ONC RPC
- In a different CICS region on the same host
- On a different host that supports CICS and inbound DPL
The CICS programs can reside on any CICS system accessible by means of DPL from
the CICS region running CICS ONC RPC. DPL operation is described in the CICS Intercommunication Guide.
[[ Contents Previous Page | Next Page Index ]]