Figure 1 shows the sequence of calls in a CICS® client-remote server setup. The calls are similar to the previous examples.

Figure 1 shows that the server can be on any processor and can run under any operating system, provided that the combined software-hardware configuration supports a TCP/IP server.

For simplicity, the figure shows an iterative server. A concurrent server would need a child server in the remote processor and an adjustment to the calls according to the model in Figure 1.

A CICS server issues a READ call to read the client’s first message, which contains the CICS transaction name of the required child server. When the server is in a non-CICS system, application design must specify how the first message from the CICS client indicates the service required (in Figure 1, the first message is sent by a WRITE call).

If the server is a concurrent server, this indication is typically the name of the child server. If the server is iterative, as in Figure 1, and all client calls require the same service, this indication might not be necessary.