TRUNCATION of QNAMEs to QUEUEs occurs silently for INQUIRE TSQUEUE [NEXT] / missing Error-Code INVREQ RESP2 values: 2

TRUNCATION of QNAMEs to QUEUEs occurs silently for INQUIRE TSQUEUE [NEXT], hence whenever QNAMEs are used there is a possibility of processing the wrong TSQ afterwards (eg DELETEQ)

WRITEQ QUEUE('12345678') ...
WRITEQ QNAME('1234567890123456') ...
INQUIRE TSQUEUE START
INQUIRE TSQUEUE(char8) NEXT RESP(resp)

Returns for char8 and resp/EIBRESP/EIBRESP2
'12345678' 0 0/0
'12345678' 0 0/0

Documentation for both 8.2 and 9.1 give no indication on the expected INQUIRE result;
the TSQNAME variant appeared first in 8.2
https://www.ibm.com/support/knowledgecenter/SSAL2T_8.2.0/com.ibm.cics.tx.doc/reference/r_inquire_tsqueue.html
https://www.ibm.com/support/knowledgecenter/SSAL2T_9.1.0/com.ibm.cics.tx.doc/reference/r_inquire_tsqueue.html
the following return codes are documented:


Conditions
END
RESP2 values:
• No more resource definitions of this type (RESP2=2) exist.

ILLOGIC
RESP2 values:
• You have issued a START command when a browse of this resource type is already in progress, or you have issued a NEXT or an END command when a browse of this resource type is not in progress (RESP2=1).

INVREQ
RESP2 values:
• Inquiring TSQ while it is being deleted or inquiring a remote TSQ (RESP2=4).

QIDERR
RESP2 values:
• The temporary storage queue cannot be found (RESP2=1).

The INVREQ RESP2 values 2 is apparently not implemented, see
https://www.ibm.com/support/knowledgecenter/en/SSGMCP_5.4.0/reference/commands-spi/dfha8_inquiretsqueue.html
INVREQ
RESP2 values:
2