PVIMG-INFO(1)

💅 pvimg-info — like, the whole manual, bestie

okay so this is pvimg-info(1) from the Pvimg Manual (yes, that Pvimg Manual) and I'm gonna walk you through it because honestly? it's giving "obscure but iconic" 🎀

✨ NAME ✨

pvimg-info — print information about the IBM Secure Execution image. that's it. that's the whole vibe. 🦋

✨ SYNOPSIS ✨

pvimg info [OPTIONS] <INPUT|--print-schema <FORMAT>>

read it like a little recipe: pvimg info, then your options, then either your INPUT or a --print-schema <FORMAT>. no cap, that's the shape of it. 💅

✨ DESCRIPTION ✨

⚠️ bestie, listen: the API and output format here are experimental and subject to change. so don't go building your whole personality on it, okay? 😭

✨ OPTIONS ✨

• <INPUT> — use INPUT as the Secure Execution image. that's your input file, go off 👑
• --format <FORMAT> — the output format for the Secure Execution image information.

if you don't specify it, the format is automatically determined based on whether stdout is connected to a terminal. cute, right? it just knows. 🌸

Possible values:

• text: Human-readable, unstable text format (default if a terminal is available).
• text:full: Human-readable, full detail text format.
• json: Pretty-printed machine-readable JSON (default if no terminal available).
• json:pretty: Pretty-printed machine-readable JSON.
• json:minify: Minified machine-readable JSON.

(yes, text appears twice in that list up there and I'm not fixing it — that's what the page says, so that's what you get. 💀)

• --hdr-key <FILE> — use the key in FILE to verify the Secure Execution header and optionally use --show-secrets to decrypt it.

the key must be the same key that was specified with --hdr-key when the Secure Execution image was created. the key is used to:

1. Verify the integrity and authenticity of the header
2. Optionally decrypt secrets with --show-secrets

🚨 without this option, the information is displayed, but NOT verified, and a warning is printed. the displayed data should not be trusted without verification. like, at all. fr fr.

• --show-secrets — this option reveals sensitive information that is normally encrypted in the header, such as:
  • Customer communication key (CCK)
  • Image encryption key
  • Other confidential data

😭 SECURITY WARNING: only use this option in secure, trusted environments. the decrypted secrets should never be exposed in untrusted systems. I'm serious, bestie, this is the "don't text your ex" of flags.

this option requires --hdr-key to decrypt the header. no key, no secrets, no exceptions. 🔥

• --print-schema <FORMAT> — print the schema for the info subcommand and exit.

this outputs the schema that describes the structure of the given output FORMAT produced by the info subcommand. the schema can be used for:

• Validating output
• Building tools that parse the output

Possible values:

• text: Human-readable, unstable text format.
• json: JSON format.

• -h, --help — print help (see a summary with -h). short version, long version, pick your fighter 🫶

---

✨ EXIT STATUS ✨

• 0 — Program finished successfully. the command was executed successfully. slay. ✅
• 1 — Generic error. something went wrong during the operation. refer to the error message. it happens to the best of us 💀
• 2 — Usage error. the command was used incorrectly, for example: unsupported command line flag, or wrong number of arguments. read the synopsis again, babe 🙈

✨ SEE ALSO ✨

pvimg(1), zipl(8), qemu(1) — go read those too, they're the friend group 💜

---

and that's the whole page!! ✨ this little gem lives in s390-tools, dated 2026-08-11 — mwah, sending you off with a 🎀 and a pvimg-info(1) kiss 💋