Enhancements of CPSM Samples & missing CPSM API DATATYPE meaning

1. CPSM REXX Samples

Using IBM supplied EYU#API1 as an example...

XX = EYUAPI('QUERY OBJECT(PROGRAM) THREAD(W_THREAD)' 'RESULT(W_RESULT) DATALENGTH(W_INTO_OBJECTLEN)' 'RESPONSE(W_RESPONSE) REASON(W_REASON)')
If XX <> 0 Then Signal UNEXPECTED
If W_RESPONSE <> EYURESP(OK) Then Signal NO_QUERY

The last statement is actually incorrect.

Technically, the code "EYURESP(OK)" should actually read "EYURESP('OK')" e.g. the OK should be a String.
The sample as supplied actually is passing the value of an unresolved REXX variable, which fortunately in REXX means "OK" is being passed and therefore the statement works as intended. If the variable OK is validly defined (perhaps not likely) the message EYUAR0025E is issued.
Sample REXX TRACE :-
564 *-* OK = 'test'
565 *-* If W_RESPONSE <> EYURESP(OK)
EYUAR0025E Argument (test) is invalid for function EYURESP.

2. CPSM DATATYPE meanings

DataTypes CNUMERIC & INTTSTP are not listed in "CICSPlex SM: Resource Tables Reference Vol 1" Chapter "Resource table attribute definitions" yet all defined/used in various tables such as MLOCTRAN, MCICSRGN ENQUEUE.

3. MSDISPT Attribute

The MSDISPT field has different attributes in different tables. Perhaps this is by design...
For example...
HTASK & TASK (CLOCK12)
MLOCTRAN (INT16US)
As noted maybe this designed specifically, so of note rather than requesting an enhancement...