You make a CICSPlex SM (CPSM) API GET request to gather resource table records. You additionally specify a CRITERIA expression that specifies that you expect a field containing a store clock value to be an exact value.
For example, for a GET request for the HTASK (Task History) resource table. You specify a CRITERIA of "RESPTIME='0000:00:00.008351'.". A NODATA response is returned from the GET request, despite an existing record matching the CRITERIA being returned when the CRITERIA is not applied.
This affects CRITERIA expressions specified with the CICSPlex SM API, either as a result of the CRITERIA being directly specified as part of the API GET request, or as part of a FILTER created using the SPECIFY FILTER command. Both the CMCI (CICS Management Client Inteface) CRITERIA parameter on the HTTP GET request URI and the CICSPlex SM WUI (Web User Interface) attribute filters are also affected.
The format for specifying a CRITERIA expression does not include enough precision to uniquely identify a store clock value. This will cause the API to filter out records that appear to match the CRITERIA.
Resolving the problem
Use less than (<) or greater than (>) operators in your CRITERIA expression instead of equaI (=), when working with store clock based fields. If you are directly using the CICSPlex SM API, or the CMCI and require to select records based on a specific store clock value, a compound CRITERIA expression can be used. For example, "RESPTIME>='0000:00:00.008351' AND RESPTIME<'0000:00:00.008352'.".
The CICS information center in the section on "How to build a filter expression" will be updated to include a note and an example for how to specify a store clock criteria.
CICSPlex SM CICSPlexSM CPSM CP/SM