Statistics for throughput analysis

Look at these key statistics when considering transaction throughput through the Gateway daemon.

CS_IALLREQ
The number of requests to CICS® servers (successful and failed) that have been processed.
CS_IREQDATA
The amount of request data (in bytes) sent to connected CICS servers. This amount includes both application and CICS protocol data.
CS_IRESPDATA
The amount of response data (in bytes) received from connected CICS servers. This amount includes both application and CICS protocol data.
CS_LALLREQ
The number of requests to CICS servers (successful and failed) that have been processed.
CS_LREQDATA
The amount of request data (in bytes) sent to connected CICS servers. This amount includes both application and CICS protocol data. For IPIC, the data comprises COMMAREA and CICS headers.
CS_LRESPDATA
The amount of response data (in bytes) received from connected CICS servers. This amount includes both application and CICS protocol data. For IPIC, the data comprises COMMAREA and CICS headers.
CSX_IALLREQ
The number of requests to CICS server x (successful and failed) that have been processed.
CSX_IREQDATA
The amount of request data (in bytes) sent to connected CICS server x. This amount includes both application and CICS protocol data.
CSX_IRESPDATA
The amount of response data (in bytes) received from connected CICS server x. This amount includes both application and CICS protocol data.
CSX_LALLREQ
The number of requests to CICS server x (successful and failed) that have been processed.
CSX_LREQDATA
The amount of request data (in bytes) sent to connected CICS server x. This amount includes both application and CICS protocol data. For IPIC, the data comprises COMMAREA and CICS headers.
CSX_LRESPDATA
The amount of response data (in bytes) received from connected CICS server x. This amount includes both application and CICS protocol data. For IPIC, the data comprises COMMAREA and CICS headers.
GD_IALLREQ
The number of API calls (ECI, ESI) and XA requests that have been processed. Successful and failed requests are included. Administrative requests and handshakes are excluded.
GD_ILUWTXNC
The number of extended LUW-based transactions that were committed. This statistic returns information about 1–phase commit transactions.
GD_ILUWTXNR
The number of extended LUW-based transactions that were rolled back. This statistic returns information about 1–phase commit transactions.
GD_IREQDATA
The amount of request data in bytes received from client applications. All requests are included.
GD_IRESPDATA
The amount of response data in bytes sent to client applications. All responses are included.
GD_IRUNTIME
The time in seconds since the last reset event, or age of the current interval.
GD_ISYNCTXN
The number of successful SYNCONRETURN transactions.
GD_IXATXNC
The number of XA commit requests that were successfully processed.
GD_IXATXNR
The number of XA rollback requests that were successfully processed.
GD_LALLREQ
The number of API calls (ECI, ESI) and XA requests that have been processed. Successful and failed requests are included. Administrative requests and handshakes are excluded.
GD_LLUWTXNC
The number of extended LUW-based transactions that were committed. This statistic returns information about 1–phase commit transactions.
GD_LLUWTXNR
The number of extended LUW-based transactions that were rolled back. This statistic returns information about 1–phase commit transactions.
GD_LREQDATA
The amount of request data in bytes received from client applications. All requests are included.
GD_LRESPDATA
The amount of response data in bytes sent to client applications. All responses are included.
GD_LRUNTIME
The length of time in seconds since the Gateway daemon successfully initialized.
GD_LSYNCTXN
The number of successful SYNCONRETURN transactions.
GD_LXATXNC
The number of XA commit requests that were successfully processed.
GD_LXATXNR
The number of XA rollback requests that were successfully processed.