iucv_configure(8)

📦 version 2.44.1, in opensuse-leap 16.0

💅 iucv_configure — the glow-up for your z/VM IUCV network adapter

okay bestie, so this little icon is from the System Manager's Manual section 8, and it's about the iucv_configure tool. Think of it as the group-chat moderator for your z/VM Inter-User Communications Vehicle (IUCV) network adapter — it brings it online, takes it offline, and handles the udev paperwork so you don't have to 🎀

✨ NAME ✨

iucv_configure — configures or deconfigures a z/VM Inter-User Communications Vehicle (IUCV) network adapter. yes, the whole name. it's giving "long but iconic" 💅

🌸 SYNOPSIS 🌸

iucv_configure peer_userid online

🦋 DESCRIPTION 🦋

iucv_configure exists to make it stupidly easy to persistently add and remove z/VM point-to-point IUCV network adapters. no cap — that's the whole point.

And like, it doesn't just flip the adapter on or off. It also creates or deletes the necessary udev rules for the adapter, so your setup actually survives a reboot instead of ghosting you. main character energy, honestly 👑

💖 PARAMETERS 💖

  • peer_userid — the z/VM userid of the virtual machine sitting on the other end of the point-to-point connection. your adapter's pen pal, basically 🫶
  • online — a literal 1 to bring the adapter online, or a literal 0 to take it offline. that's it, that's the vibe check 🔥

🎀 FILES 🎀

  • /etc/udev/rules.d/51-iucv-<peer_userid>.rules — this file provides the udev rules necessary to activate a specific IUCV adapter. it's the receipts file, and yes it's got your peer's name on it 💜

🌈 ENVIRONMENT 🌈

  • DEBUG — if set to "yes", some minimal debugging information is output during execution. lowkey chatty, highkey helpful 🙈

⭐ DIAGNOSTICS ⭐

the following messages may be issued on stdout:

  • /sysfs not present — the sysfs file system could not be found in /proc/mounts, so there's literally nothing the script can do. return code 1 is set. it's down bad and it knows it 😭
  • No IUCV user name given — bestie, you didn't specify the z/VM userid of the virtual machine you want to connect to. return code 2 is set. not me forgetting the one required argument 💀
  • Unable to connect to $PEER_USERID — the attempt to connect to the IUCV peer failed. try dmesg to see if there's any indication why. return code 3 is set.
  • Unable to remove device $netdev — the attempt to remove the IUCV adapter failed. try dmesg to see if there's any indication why. return code 4 is set.

and if the environment variable DEBUG is set to "yes", these extras may also be issued on stdout:

  • Configuring IUCV device ${PEER_USERID} — just a little bit of verbosity, since it just indicates that we got past certain error checks and will now try to do something useful. we love a progress update ✨
  • Configured device $iucvdev — the attempt to create the IUCV adapter was successful. slay 💅
  • Removed device $iucvdev — the attempt to remove the IUCV adapter was successful. ate and left no crumbs 🔥

💀 BUGS 💀

gotta be some, I'm sure. if you find one, please open a bug report. we're not perfect, we're just iconic 🙈

heads up bestie: those return codes are the whole personality of this script — 1 no sysfs, 2 no userid, 3 connect failed, 4 remove failed. memorize them and you'll never be confused again 🧚

okay that's the whole page 💖 it's s390-tools, dated July 2013, and this iucv_configure(8) girlie is out. go configure something iconic, periodt 🌸🫶

📦 where this page comes from