Working with Output Queues using WRKOUTQ

Learning Objective

By the end of this lesson, you will be able to explain what WRKOUTQ shows, and how its scope differs from WRKSPLF.

Simple Explanation

The Spool Files and Output Queues lesson introduced an output queue as a holding area that can contain many spool files at once, waiting to be printed. WRKOUTQ (Work with Output Queue) shows every spool file currently sitting on one specific, named output queue, regardless of which user or job originally created each one.

From WRKOUTQ's list, you can hold a spool file, release a held one so it can print, or delete it, similar to the options WRKSPLF offers, but seen from the output queue's point of view rather than from one user's own spool files.

Why It Matters

WRKOUTQ and WRKSPLF answer genuinely different questions: WRKSPLF, covered in the previous lesson, answers "what have I recently generated?" while WRKOUTQ answers "what is currently sitting on this specific output queue, from anyone?" Knowing which question you actually need answered determines which command to reach for.

Practical Example

Imagine an operator responsible for making sure every report destined for a specific printer's output queue actually gets released and printed. Rather than checking every individual user's own spool files with WRKSPLF, they run WRKOUTQ against that specific output queue and see every spool file currently waiting there, from any user or job, letting them release held ones or investigate anything stuck.

This is a simplified, illustrative example rather than a specific real operational task, but it reflects a genuinely common reason WRKOUTQ is used on real IBM i systems.

Common Confusions

"Is WRKOUTQ just WRKSPLF scoped to one output queue?" Close in spirit, but the key difference is whose spool files are shown. WRKSPLF is scoped to your own user profile by default, across whichever output queues your spool files happen to land on. WRKOUTQ is scoped to one specific output queue, showing spool files from any user or job that sent output there.

"Do I need to specify which output queue I want to look at?" Yes. Unlike WRKSPLF's default per-user scope, WRKOUTQ needs a specific output queue name, since its whole purpose is showing what is sitting on that particular queue.

"Can holding a spool file with WRKOUTQ be undone?" Yes. A held spool file can be released from the same WRKOUTQ list, letting it proceed to print normally, exactly the kind of everyday operational task WRKOUTQ is meant for.

Quick Recap

• WRKOUTQ (Work with Output Queue) shows every spool file currently on one specific, named output queue, regardless of who created it.
• WRKSPLF shows your own spool files across output queues; WRKOUTQ shows one output queue's spool files across users.
• Options from WRKOUTQ include holding, releasing, and deleting a spool file, similar to WRKSPLF.
• Choosing between WRKSPLF and WRKOUTQ depends on whether you are asking "what did I generate?" or "what is on this specific queue?"

Try Asking the AI Tutor

Use the AI Tutor to ask follow-up questions about this lesson. For example, try asking:

• "Would WRKOUTQ or WRKSPLF be the better choice for checking on a report a coworker ran, not me?"
• "What happens to spool files already sitting on an output queue if that output queue itself is held?"