ZIOMON_MGR(8)

💅 ZIOMON_MGR(8) — like, the message queue server for the ziomon framework, bestie

okay so real talk: this is a page from the System Manager's Manual, section 8 (that's the admin/system commands girlies ✨), and it's all about ziomon_mgr. Buckle up 🎀

---

✨ NAME ✨

ziomon_mgr — the message queue server for the ziomon framework. she's the middleman, the group chat admin, the one who holds everybody's messages 💅

---

🌸 SYNOPSIS 🌸

ziomon_mgr [-h] [-v] [-V] [-e] [-f] [-l <size>] [-x <version>] -o
<filename> -i <length> -Q <msgq_path> -q <msgq_id> -u <util_id> -r
<ioerr_id> -b <blkiomon_id> -z <zfcpdd_id>

like yes, that's a lot of flags. she's high maintenance but worth it 🫶

---

🦋 DESCRIPTION 🦋

so ziomon_mgr starts up a message queue — that's the spot where all the clients of the ziomon framework drop their data off 📬 anything that shows up gets written to a file you specify. iconic.

optionally you can set an upper limit on that file. and if the limit gets exceeded? the oldest data gets aggregated into a separate file to make room for the newest stuff. like cleaning out your closet but keeping the vintage pieces 👑

for consistent data, all the clients should schedule their interval lengths to the same duration. and generally, clients should send their data at the same time. synchronized slay ⏰✨

⚠️ lowkey important: this command is not meant to be run on its own. don't be a main character about it — instead use the ziomon command. iykyk 💀

---

🎀 OPTIONS 🎀

• -h, --help — prints help info and then dips out. exit stage left 💨
• -v, --version — prints version info, then exits. identity check ✨
• -V, --verbose — be verbose. she talks. a lot. we love her for it 🗣️
• -e, --binary-offsets — the lengths of the raw data structures.
• -f, --force — forces message queue creation even if one already exists. no cap, it just bulldozes through 💥
• -o, --output — the basename of the file to write data to. respective suffixes get appended for the aggregated and regular data file names 🏷️
• -l, --size-limit — upper limit of the output file, in MB. this does not include the space for the aggregated data file — but honestly the size of the aggregated data file is usually negligible, so like, don't stress 🍓
• -x, --enforce-version — enforces a specific file format for .log and .agg files. currently supports versions 2 (blkiomon version 0.2) and 3 (blkiomon version 0.3 or higher). pick your era 💜
• -i, --interval-length — the expected elapsed time between messages sent by the clients, in seconds. the samples get aggregated over this period. defaults to the duration. this should be a multiple of the sample length 👀
• -Q, --msg-queue-name — the name for the message queue to start.
• -q, --msg-queue-id — the id for the message queue to start. must be an integer >0.
• -u, --util-id — id of the utilization messages that ziomon_util will send. must be an integer >0.
• -r, --ioerr-id — id of the ioerr messages that ziomon_util will send. must be an integer >0.
• -b, --blkiomon-id — id of the messages that ziomon_util will send. must be an integer >0.
• -z, --ziomon_zfcpdd-id — id of the messages that ziomon_zfcpdd will send. must be an integer >0.

---

🌈 EXAMPLES 🌈

okay so picture this: you wanna start a message queue named /tmp/ziomon.23943 with id 95. utilization messages from ziomon_util carry the id 17, ioerr messages 18, messages from ziomon_zfcpdd 47, and messages from blkiomon 59. the interval between each set of messages is 20 seconds. and the output files should base their names on trace_data. so:

ziomon_mgr -i 20 -Q /tmp/ziomon.23943 -q 95 -u 17 -r 18 -b 47 -z 59 -o
trace_data

literally that's it. copy, paste, serve 💅🔥

---

⭐ SEE ALSO ⭐

ziomon(8), ziomon_util(8), ziomon_zfcpdd(8) — go read those too, bestie, they're the supporting cast 🫶

---

and that's the whole vibe check 💖 this page ships with s390-tools, dated Jul 2008 — yeah she's vintage but she still ate. periodt 🌸✨