There's a device driver I wrote that allows you to use IUCV as if it's a file and do open/close/read/write type operations. It has ioctls that allow you to specify things:
- Set target class - Get target class - Set source class - Get source class - Set message tag - Get message tag - Set answer buffer size for 2way reply - Get name of partner user - Get name of partner node It also lets you connect to the * services. The RPM has a sample program that connects to *MSG. A source RPM for ClefOS kernel 3.10.0-957.12.2 is available at http://download.sinenomine.net/fsiucv/fsiucv-3.10.0-957.12.2.el7.src.rpm. It is simply a matter of building it against your own kernel level to produce working binaries: 1. rpm --install 2. Edit fsiucv.spec to change Version/Release specs 3. rpmbuild --ba fsiucv.spec (there will be dependencies that rpmbuild will report) The binaries for the RPM will appear in the EPEL repo of ClefOS: http://download.sinenomine.net/epel over the next day or so. Neale On 6/14/19, 16:15, "Linux on 390 Port on behalf of Alan Altmark" <[email protected] on behalf of [email protected]> wrote: On Friday, 06/14/2019 at 07:13 GMT, "Frank M. Ramaekers" <[email protected]> wrote: > Yes, that was more like I was thinking of (except in REXX). I suspect that Neale might have been referring to the base IUCV support in Linux upon which AF_IUCV and the vmlogrdr are built, but I don't find any documentation for it other than <net/iucv/iucv.h>. (Egad! I had forgotten that I worked on that back in 2000! Has it really been that long?!?) But I don't see any benefit to using that instead of AF_IUCV sockets. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
