RE: VB.Net and Data Queue Example

>From the redbook on the .NET providers:

Data queues: For data queues, you can use the IBMDA400 OLE DB provider included 
with iSeries Access for Windows. Testing of data queues through the 
System.Data.OleDb bridge has not been performed.
This helps support your suggestion, to use stored procedures. I suppose this 
still allows for waiting on the queue, as the stored procedure would not return 
until something shows up.

The number for this redbook is SG24-6440. There are examples, as well as 
extensive materials on converting to .NET technology from OLE/DB, etc.

HTH
Vern
-------------- Original message -------------- 

> I've never been a big fan of IBM's sample code, but it does show how 
> it's done. However, that is COM and VB6 code, not VB.NET. Yes, via 
> COM-Interop you could call the Client Access COM objects, but I would 
> suggest a different way, especially from .NET. 
> 
> Create an RPG (or CL, or Cobol, or whatever) program that retrieved a 
> DataQ entry and returned the value as a parameter. Then simply describe 
> that program to SQL as a stored proc. Then tell your VB.Net programmers 
> to call the stored proc via the .NET data provider just like any other 
> stored proc and just like they are reading/updating data. There's no 
> reason to special case the dataq access. In fact, the VB.Net programmers 
> don't even have to know a DataQ is involved. 
> 
> -Walden 
> 
> 
> ------------ 
> Walden H Leverich III 
> Tech Software 
> (516) 627-3800 x11 
> WaldenL@xxxxxxxxxxxxxxx 
> http://www.TechSoftInc.com 
> 
> Quiquid latine dictum sit altum viditur. 
> (Whatever is said in Latin seems profound.) 
> 
> 
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list 
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> To subscribe, unsubscribe, or change list options, 
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> Before posting, please take a moment to review the archives 
> at http://archive.midrange.com/midrange-l. 
>