"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 03/31/2016
12:15:07 PM:
I agree, but then I would have had to add the code to examine the error
code structure. By setting QUSBPrv to 0 you'll get an escape returned to
the application (which will make it very clear that you have an error).
How is this "escape" detected? In my experience, having bytes
provided set to zero simply causes errors to be ignored with no indication
either to the program or to the joblog.
PS - you don't have to set QUSBAvl to 0. The APIs will do that for you
when
there is no error (and QUSBPrv >= 8.
Apparently, not all of the APIs are so nice. I have run into the
situation where a "ghost" error was being detected from an API where there
was not actually an error because the error code data structure still had
information in it from a previous API that had reported an error. When I
started setting the bytes available to zero the "ghost" error detection
went away.
Sincerely,
Dave Clark
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300
Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331
*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please
immediately notify the sender and delete and destroy the message and all
copies. All unauthorized direct or indirect use or disclosure of this
message is strictly prohibited. No right to confidentiality or privilege
is waived or lost by any error in transmission.
*********************************************************************************************
midrange.com
