HELD - Held output

Enhanced Definition

`HELD` output, often referred to as "held output," is a status assigned to a SYSOUT dataset within the Job Entry Subsystem (JES) spool. When SYSOUT is held, it is prevented from being immediately processed, printed, or routed to its final destination, allowing for review, modification, or manual release by an operator or authorized user. This mechanism provides control over the flow of job output.

Key Characteristics

- Status Attribute: HELD is a specific attribute of a SYSOUT dataset, indicating it is awaiting explicit action before further processing.
- JCL Control: The HOLD=YES parameter on a DD statement in JCL explicitly directs JES to hold the SYSOUT dataset upon job completion.
- Operator/User Release: Held output must be manually released by a system operator via console commands, or by an authorized user through utilities like SDSF (System Display and Search Facility) or TSO/ISPF.
- Spool Storage: Held output resides in the JES spool until it is released, at which point it becomes eligible for printing, archiving, or other specified processing.
- Viewable While Held: Users can view the contents of held SYSOUT datasets using tools like SDSF without releasing them, which is crucial for verification and troubleshooting.
- Retention Policies: Held output is subject to JES retention policies and can consume significant spool space if not managed properly.

Use Cases

- Pre-Print Review: Holding critical reports or sensitive documents to allow for manual review and verification of content before they are printed or distributed.
- Batch Job Coordination: When a subsequent job or manual process depends on the output of a preceding job, the output can be held until the dependent process is ready.
- Troubleshooting and Debugging: Examining the SYSOUT of a failed or abended job to diagnose issues without immediately printing potentially large volumes of erroneous output.
- Resource Management: Preventing a large report from immediately consuming printer resources, especially during peak hours, by holding it for later, off-peak printing.
- Manual Distribution: Holding reports that require manual sorting, bundling, or specific physical distribution instructions before being sent to a printer.

Related Concepts

HELD output is intrinsically linked to JES (Job Entry Subsystem), which is responsible for managing all job input and output, including the spooling and disposition of SYSOUT datasets. It is a specific state of a SYSOUT dataset, which represents the output generated by a program. The HOLD=YES parameter is specified within JCL (Job Control Language) DD statements to instruct JES to hold the output. Tools like SDSF and TSO/ISPF provide the primary interfaces for users and operators to view, manage, and release held output, thereby controlling its eventual routing to printers or other output devices.

Best Practices:

Explicit Release: Always ensure that held output is explicitly released once its purpose has been served to prevent unnecessary consumption of JES spool space.
Monitor Spool Usage: Regularly monitor JES spool utilization for held output, especially for large or long-running jobs, to avoid performance degradation or spool exhaustion.
Automate Routine Releases: For predictable or recurring held output, consider implementing automation scripts or scheduling tools to release it at appropriate times.
Security Considerations: Restrict permissions for releasing sensitive held output to authorized personnel only, as releasing it makes it available to its final destination.
Document Holding Policies: Establish clear policies and procedures for when and why output should be held, who is responsible for releasing it, and its maximum retention period.