Data queue connections have a built-in two-second delay in their responses. This delay can be eliminated by following the process in this document.
Resolving The Problem
Note: The following was copied from the Java Toolbox FAQ. The information applies to any client of the Data Queue host server. This includes the Java Toolbox, Client Access Data Queue APIs, and Microsoft ActiveX objects.
Using DataQueue.read(int time-out) or DataQueue.peek(int time-out) where time-out is greater than zero may result in a 2-second delay before data is returned to the client. The delay happens because of the notification mechanism of the server. If a time-out is specified and no entry exists on the queue, the server sets up a notification mechanism that returns an item when one arrives on the queue or returns control to the client when the time-out period expires. It currently takes 2 seconds to establish this mechanism. Therefore, if an item arrives on the queue just moments after the client request arrives, the item will not be returned to the client for 2 seconds. The server reworked its notification mechanism to avoid the 2-second delay.
To get the new mechanism to avoid the delay, following are the delayed SLIC PTFs with special instructions about how to disable the SLIC short wait:
MF24942 - V4R3
MF24475 - V4R4
MF24728 - V4R5
MF27269 - V5R1
No PTF is required on the V5R2 operating system release nor on subsequent releases.
In V5R2, the default behavior is to enable the short wait. Subsequent releases will default to disabling the short wait.
To enable the system to avoid the delay (disable short wait), call the following program: CALL QSKMAINT PARM(20 x'80')
To revert to the original notification mechanism (enable short wait), call the following program: CALL QSKMAINT PARM(20 x'81')
Internal Use Only
400-12 HOST SUPPORT (5722SS1HS)
17 June 2018