NOTIFY parameter - IBM-JCL

Parameter Type

Keyword, optional

Purpose

Use the NOTIFY parameter to request that the system send a message to a user when this background job completes processing.

Considerations for an APPC Scheduling Environment

The NOTIFY parameter has no function in an APPC scheduling environment.

1.Syntax

The NOTIFY parameter for both JES2 and JES3 is the following:

NOTIFY={nodename.userid} {userid }

2.Subparameter Definition for JES2 Systems

nodename.userid
Identifies a node and a TSO/E or VM userid at that node. The nodename is a symbolic name defined by the installation during initialization; nodename is 1 through 8 alphanumeric or national ($, #, @) characters. The first character of nodename must be alphabetic or national ($, #, @). The userid must be defined at the node. It is 1 through 8 alphanumeric or national ($, #, @) characters; the first character must be alphabetic or national ($, #, @).

userid
Identifies the user that the system is to notify. The userid is 1 through 7 alphanumeric or national ($, #, @) characters. The first character must be an alphabetic or national ($, #, @) character. When you specify only a userid, JES2 assumes that the userid is at the origin node.

The userid may also be a valid remote ID in the form Rnnnn or a destid for a remote. If the userid is specified as R1-R9999, JES2 will assume the notify message is intended for a remote and not a userid. If the remote is defined to the system or is less than the highest defined remote for your system, the notify message is queued to the remote. If the remote value is greater than the highest defined remote but less than the maximum allowed remote, the notify message is discarded. If the Rxxxx value specified is greater than R9999, JES2 will consider that as a TSO/E userid and not a remote id.

3.Subparameter Definition for JES3 Systems

userid
Identifies the user that the system is to notify. The userid is 1 through 7 alphanumeric characters and must be a valid TSO/E userid. JES3 assumes that the userid is at the node where the job runs.

4.Receiving Notification of Job Completion

In a JES2 System
If you are logged on to the member of the JES2 multi-access spool from which you submitted the job, the system immediately notifies you when the job completes. If you are not logged on, the system saves the message until you log on to the member from which you originally submitted the job.

In a JES3 System
If you are logged on, the system immediately notifies you at the system you are logged onto when the job completes. If you are not logged on, the system saves the message until you log on to the system from which you originally submitted the job.

If you want to receive notification at a system of your choice, specify the system you want to be notified at on the ACMAIN parameter.

If a job is submitted by another job, the ACMAIN parameter specified for the first job is propagated to the second job.

If a //*ROUTE or XMIT JCL statement follows the JOB statement, you may not be notified when the transmitted job completes.

5.Examples of the NOTIFY Parameter

//SIGN JOB ,TKLOMP,NOTIFY=VMNODE.VMUSERID

When the job SIGN completes processing, the system sends a message to user VMUSERID on node VMNODE.

//SIGN JOB ,TKLOMP,NOTIFY=MVSUSER

When the job SIGN completes processing, the system sends a message to user MVSUSER on the job’s origin node.


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

IBM-JCL Topics