HOLD parameter - IBM-JCL

Parameter Type

Keyword, optional

Purpose

Use the HOLD parameter to tell the system to hold a sysout data set until it is released by the system operator. When the data set is ready for processing, notify the system operator to release it via a TSO/E NOTIFY parameter, a JES2 /*MESSAGE statement, or a JES3 //*OPERATOR statement.

A TSO/E user can specify HOLD=YES to retrieve a sysout data set and display it on a terminal. For JES3, the TSO/E user can process only work on the hold queue.

Notes:

  1. HOLD is supported only for sysout data sets. If HOLD appears on a DD statement that does not contain a SYSOUT parameter, it is ignored.
  2. HOLD allows the sysout data set to be the internal reader. If the sysout data set is the internal reader, the job being submitted will be held.

1.Syntax

HOLD= {YES} {Y } {NO } {N }

2.Subparameter Definition

YES
Requests that the system hold the sysout data set until the data set is released by the system operator. You can also code this subparameter as Y.

NJE Notes:

  • In a JES2 NJE environment, the system does not hold the data set until it reaches its ultimate destination node.
  • If the destination node is a JES3 node, the system may still not hold the data set if the class of output being transmitted is not defined as a hold class. If the sending node is JES3, the system holds the output data set at that node on the BDT queue (when transmitting to an SNA-attached node) or the WTR queue (when transmitting to a BSC-attached node) if all of the following are true:
  • – The ²// DD SYSOUT=² JCL statement does not contain a DEST=(node,userid) parameter.
    – The SYSOUT= parameter does not contain the WRITER-NAME subparameter and the output class is not defined as a hold class.
    – No WRITER= parameter is coded on the OUTPUT JCL statement.

Example.

The following job executes on NODE1 and results in the SYSUT2 output data set being held on the BDT queue on NODE1. (NODE5 is attached to NODE1 via SNA and output class A is not defined as a hold class.)

Example.

The following job executes on NODE1 and results in the SYSUT2 output data set being held on the WTR queue on NODE1. (NODE5 is attached to NODE1 via BSC and output class A is not defined as a hold class.)

NO
Requests that the system perform installation-defined processing for the sysout data set’s output class. You can also code this subparameter as N.

3.Defaults
If no HOLD parameter is specified, the default is NO. If the HOLD parameter is incorrectly coded, the system assumes the default of NO and issues a warning message; the job continues.

4.Overrides
HOLD=NO is overridden by the unallocation verb of dynamic allocation or the TSO/E FREE command.

HOLD=YES on the DD statement overrides the sysout data set disposition specified on the OUTDISP parameter of the OUTPUT JCL statement.

5.Relationship to Other Parameters
Code the HOLD parameter only on a DD statement with the SYSOUT parameter. JES3 ignores HOLD=YES when

  • DEST=(node,userid) is coded on the SYSOUT= DD statement. Example 1 shows this case. (JES3 does not ignore the HOLD=YES when DEST= is coded on the OUTPUT DD statement. Example 2 shows this case.) or
  • the sysout data set is placed on the hold queue, for example, if SYSOUT=(,writer-name) is coded.

Ignored but permitted DD parameter:

If you specify the SUBSYS DD parameter, the system checks it for syntax and then ignores it.

6.Relationship to Other Control Statements
Code a NOTIFY parameter on the JOB statement to ask the system to send a message to your TSO/E userid when job processing is complete.

JES2 users can use the /*NOTIFY control statement to direct job notification messages and to override a JOB NOTIFY parameter.

7.Examples of the HOLD Parameter

Example

In this example, sysout data set DD1 from JOB01 is held on a queue until the TSO/E user at RMT6 asks the system operator to release the data set.

Example

In this example, if the job is submitted on NODE1, JES3 does not ignore the HOLD=YES. The SYSOUT data set is held at NODE1 and is not transmitted to NODE2 to be held there.


All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

IBM-JCL Topics