The UADriver always changes requested query timeout value to zero therefore not allowing applications to change the timeout value. Why is this?
The driver always changes the query timeout value to 0 because the driver has no way to stop OS 2200-based processing. For example, there is no way for UADriver to cancel processing that is occurring within RDMS 2200 once the command is under the control of RSA. To be consistent, UADriver returns 0 which indicates that the query timeout value is being ignored. back to top Question (UniAccess #935): Sometimes when people do SQL requests using UniAccess, an undeliverable message (see below) comes out. Is there a way to suppress this? ======== Undeliverable Message ======== Name: sp_pkeys Code: 32000 Severity: 15 Text: UARS Library error (UASNDDON returned [16046]: srv_done(): results state error – final done already sent to client.) Answer: There is no way to suppress this message. A workaround would be to send the output from this transaction to a dummy printer and then have a process, such as smart console, periodically delete items from this queue. However, this method is not recommen
Related Questions
- The UADriver always changes requested query timeout value to zero therefore not allowing applications to change the timeout value. Why is this?
- What happens if my requested web design changes will take more time than I have alloted for the current month/quarter?
- How to Modify or Disable ScanDisk Timeout Value on Windows Startup?
