A statistics API application, and the Gateway daemon providing
the statistics, might be from different versions of the CICS® Transaction Gateway.
API
and protocol version control helps ensure that a statistics API application
can issue meaningful requests to a
CICS Transaction Gateway daemon,
and get meaningful responses in return. API and protocol versions have a format
of four digits, separated by the underscore character. For example:
1_0_0_0Note: The
API and protocol versions might look like the product version, but they are
not related. The statistics API can only be used to collect statistical data
from Gateway daemons at version 7.0 or higher.
A statistics API application can:
- Find the protocol version that it was compiled with by using the compile-time
string CTG_STAT_PROTOCOL_VER, defined in ctgstdat.h.
- Find the API version that it was compiled with by using the compile-time
string CTG_STAT_API_VERSION, defined in ctgstats.h.
Find which protocol version is used by a CICS Transaction Gateway daemon,
by using the openGatewayConnection or openRemoteGatewayConnection function.
- Find which API version is provided by a CICS Transaction Gateway daemon,
by using the getStatsAPIVersion function.
The API version of the statistics API application must have the same major
version number as the CICS Transaction Gateway daemon.
If the major version numbers differ, API calls might fail. The minor version
number of the CICS Transaction Gateway API
version must be the same or greater than the API version of the statistics
API application, otherwise some new API functions might not be available.
The protocol version of the statistics API application must have the same
major version number as the CICS Transaction Gateway daemon.
The minor protocol version number of the statistics API application must be
the same or greater than the minor protocol version number of the CICS Transaction Gateway daemon. Otherwise,
the statistics API application might be unable to interpret responses from
function calls.