I wrote a character device driver that allows you to use open/close/ioctl/read/write semantics to do IUCV communications. There are a couple of source RPMs at https://download.sinenomine.net/fsiucv. Use the -3 series. Note, they are tied to a kernel level so the spec file would need adjusting.
Neale Ferguson On 8/19/20, 01:32, "Linux on 390 Port on behalf of Christian Svensson" <[email protected] on behalf of [email protected]> wrote: Thanks Ursula, I wasn't clear if this was a call for me to justify what I am trying to do, but I thought I might mention it. > Probably not: Either there is a good idea why to include message_send2way into the standard socket interface AF_IUCV, My use-case is that I want userspace in zLinux to call other other VMs over IUCV. I would prefer to use a standardized interface to this as much as possible as that would mean I can release general purpose libraries to do IUCV operations in z/VM environments. E.g. in my case I have already contributed support for opening and connecting to IUCV sockets in Go. That is now part of the official Go libraries. The next step I want to do is to be able to do is 2WAY SEND, again preferably in a way that allows me to craft libraries that other developers can use on a zLinux with a new enough kernel. t.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- 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
