DASDLIST(1)

✨ NAME ✨

dasdlist β€” okay so this is the one that builds you an empty DASD image file πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

dasdinit [-v] [-z] [-bz2] [-0] [-lfs] [-a] [-r] [-linux] filename
devtype[-model] [volser] [size]

So real talk, this manual page is documenting the dasdinit program πŸ’… (yes the page is called dasdlist and the command is dasdinit, we don't make the rules, we just vibe).

And what does it do? dasdlist builds an empty DASD image file ✨ that's the whole assignment, that's the plot.


πŸŽ€ PARAMETERS πŸŽ€

Here's your lineup of things you gotta feed it, in order, no skipping 🫢

  • filename β€” the name of the DASD image file you want it to create. Like, the baby's name, essentially.
  • devtype β€” the emulated device type. Iconic. Necessary.
  • model β€” the emulated device model, and it's optional bestie, breathe 😌
  • volser β€” volume serial number, and it's gotta be 1-6 characters β€” and heads up, you only pass this if you're NOT using the -r option 🚫
  • size β€” number of cylinders (that's for CKD devices) or 512-byte sectors (that's for FBA devices). It's optional if the device is specified 🌸

πŸ’… OPTIONS πŸ’…

Every single flag, coming at you, no cap:

  • -v β€” shows you the version info and the help. The "hey what even is this" flag πŸ’–
  • -z β€” builds a compressed DASD image file using zlib ✨
  • -bz2 β€” builds a compressed DASD image file using bzip2 🌈
  • -0 β€” builds a compressed DASD image file with no compression πŸ’€ yeah it's giving oxymoron, it's giving iconic
  • -lfs β€” builds a large (uncompressed) DASD file, but only if it's supported. If not supported... it's not supported, bestie πŸ™ˆ
  • -a β€” builds a DASD image file that includes alternate cylinders. Lowkey important caveat: this option gets ignored if you manually specify size 😭
  • -r β€” builds a 'raw' DASD image file, meaning no VOL1 and no IPL track 🚨
  • -linux β€” null track images will look like linux dasdfmt'ed images. Heads up: 3390 device type only β€” don't try it anywhere else πŸ’…

πŸ‘€ SEE ALSO πŸ‘€

Go read this one, it's the homework:

  • /usr/share/doc/hercules/html/hercload.html

πŸ‘‘ AUTHOR πŸ‘‘

So the lore is: Hercules was created by Roger Bowler and it's maintained by Jay Maynard πŸ‘‘βœ¨

And Jan Jaeger designed and implemented many of the advanced features of Hercules, including dynamic reconfiguration, integrated console, interpretive execution, and z/Architecture support. Ate, no crumbs 🫢

This manual page was written by Peter De Schrijver p2@debian.org for the Debian GNU/Linux system (but may be used by others) 🌸 Permission is granted to copy, distribute and/or modify this document under the terms of the GPL.


okay that's the whole page bestie, you're officially educated πŸ’–

Signing off from DASDLIST(1), manual page and proud β€” that's the title card, that's the footer, that's the whole ~aesthetic~ πŸŽ€πŸ’…βœ¨