CICS ONC RPC performance and tuning

This chapter contains Diagnosis, Modification, or Tuning Information.

The performance of a single client request is affected by various aspects of the client, the network, CICS® ONC RPC, the user-replaceable programs, and CICS.

The client

The client time-out interval must take account of the possible delays in dealing with a client request in CICS ONC RPC and in CICS.

If a client request cannot be processed, an error reply is sent to the client.

The network

This manual does not deal with performance problems of TCP/IP networks.

TCP/IP for MVS™ resources

If, while registering 4-tuples, you cause the connection manager to register too many 3-tuples with TCP/IP for MVS, you might reduce the service that CICS ONC RPC can give to incoming client requests. See Limits on registration.

CICS ONC RPC
The allocation of different alias transaction names to different 4-tuples must be coordinated with the priorities given to the transactions in CICS.
The converter URM

Getlengths is called only by the connection manager, and has no effect on the performance of a single client request, or on throughput.

Decode is called by the server controller. Delays here can reduce the throughput of CICS ONC RPC as well as reducing the performance of a single client request. The following recommendations are made:

Encode is called by the alias. Delays here reduce the performance of single client requests, but not the throughput of CICS ONC RPC.

The resource checker URM

The resource checker is called by the alias, so delays here affect the performance of a single client request, but have no effect on throughput.

Related concepts
ONC RPC concepts
CICS ONC RPC problem determination
Related tasks
CICS ONC RPC operational considerations
[[ Contents Previous Page | Next Page Index ]]