RE: QUSRTOOL and asyncIO.h

Vern/Simon:

Sigh. I guess now I'll have to go through whatever it is that gets my 
Registered SKB access working again. It's been a couple years... the 
user/password scheme change that they went through time before last last was 
when it quit working. I tired of trying after the first 90 mins or so of 
digging through their various suggestions and documentation on how to enable it.

Anyway, thanks much.

I was only looking at bits of QUSRTOOL to see what was in there lately. I look 
every few releases and it's been a while.

Tom Liotta


midrange-l-request@xxxxxxxxxxxx wrote:

>   6. Re: QUSRTOOL and asyncIO.h (Vernon/Simon)
>
>Anyone with software support (whatever is equivalent to SupportLine) 
>can register for the locked KB. The article has the entire fixed 
>source member, which I sent the new code to Simon and Tom.
>
>Later
>
>At 04:55 AM 10/17/2005, you wrote:
>
>>On 16/10/2005, at 2:51 PM, qsrvbas@xxxxxxxxxxxx wrote:
>>
>>>I was going to look over a QUSRTOOL example, the TSO sockets tool, 
>>>and found that the compile of one of the C modules failed with this error:
>>>
>>>36 |#include <asyncIO.h>
>>>*=SEVERE==========> CZM0296 #include file <asyncIO.h> not found.
>>>
>>>  QSYSINC has no asyncIO.h in V5R1, R2 or R3. And surprise -- 
>>> InfoCenter has no search references to such an include, although 
>>> there are a couple comments in a couple Apache source modules to asyncIO.
>>>
>>>Does no one compile things from QUSRTOOL anymore?
>>>
>>>  Anyway, does anyone out there have an example of asyncIO.h that 
>>> might be appropriate?
>>>
>>>I suspect it doesn't exist for OS/400, but I might as well ask.
>>
>>Looks like someone screwed up. Probably by compiling and testing on 
>>AIX instead of OS/400 but that's just a guess on my part.
>>
>>If you look at the source from the TSO tool on 530 you'll see that 
>>asyncIO.h has been replaced by qsoasync.h which also exists on 510.
>>
>>There are other things that have changed too but you can get the 510 
>>TSO source to compile by creating your own asyncio.h file which 
>>contains only the Qso_OverlappedIO_t definitions from qsoasync. For example: