|
>I had a book (TCP something from midrange computing) >with a good example of a sockets program and even >how to use it with visual basic. But it requires you to >write a second sockets program for every program you >want to run. Ahhh, the crux! Instead of multiple socket programs, you need a single socket program that calls multiple "exit programs" based on the parameter list needed by the target program. David Morris and Scott Klement outlined pretty much everything you need in terms of generic storage of the parameter lists across the PC/iSeries interface and the communications methodology to work with. The only reason I'm adding to this thread is that I'm curious what your PC program can do with the raw returned data. One time, it might call GetItemDescription and get back {"AUTO WAX";"BLUE";1;"LITRE"}. Another time, it might call GetOrderShipDate and get back {"10 Jul 2001"}. Consider how tightly you intend to couple the PC and the iSeries... Of course, this project sounds more like a lark than a mission critical undertaking. In that light, have fun exploring! Buck (on holiday 'til Monday) +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.