NOTIFY parameter

rahul_desai29 · New User Joined: 15 Mar 2006 Posts: 10 Location: fl;jds

If you give NOTIFY=??? what it means?

priyesh.agrawal · Posted: Tue Mar 21, 2006 12:24 pm

vasa · New User Joined: 10 Jan 2006 Posts: 9

it direct the error messages to the particular user

/*NOTIFY userid

martijn · Posted: Tue Mar 21, 2006 3:24 pm

You can code the NOTIFY-parameter on the jobcard, and with it specify the user that will be notified (i.e.: get a message on screen) when the job ends. for instance: if you code NOTIFY=ABC0123, user ABC0123 will be notified that the job has ended. the notification will also tell you if the job ran successfully;

Gautam512 · Posted: Tue Mar 21, 2006 5:08 pm

Here is the complete info of NOTIFY parameter.

** The /*NOTIFY Statement **

The /*NOTIFY statement is used to indicate where JES2 is to send the
notification messages for a job. It is primarily used in a JES2 job
network to route NOTIFY messages between network nodes.

The /*NOTIFY statement is identified by the characters /*NOTIFY in columns 1 through 8, followed by a blank in column 9, and a parameter anywhere in columns 1 through 71. You should insert the /*NOTIFY statement after the JOB statement and before the first EXEC statement in the job.

The JES2 /*NOTIFY statement, if present, is used instead of the
NOTIFY= keyword parameter on the JCL JOB statement.

Statement Syntax:

/*NOTIFY {nodename.userid |
nodename:userid |
nodename/userid |
nodename(userid) |
userid
}

Parameters and their meanings:

nodename

The 'nodename' parameter identifies a network node name at which the 'userid' is located. The 'nodename' portion of the parameter
is a one through eight alphanumeric or national character valid network node name. No commas, a right parentheses, or blanks can appear within the nodename.

userid

The 'userid' identifies a TSO or VM user. When you specify a
userid without a nodename, JES2 assumes that the nodename for the
job is the job's origin node. The 'userid' for TSO/E and for VM
is one through eight (one through seven for TSO systems)
alphanumeric or national characters. No commas, a right
parentheses, or blanks can appear within the userid.

Note: A JOB submitted with a NOTIFY statement or that uses the NOTIFY= parameter on the JOB statement should not also include a

/*JOBPARM SYSAFF= parameter that uses the IND subparameter.
IND changes the owning mode for the job, and the notify would then never
be delivered.

/*NOTIFY Statement Example:

/*NOTIFY LA.C2998

This JES2 /*NOTIFY statement sends all notification messages to
TSO user C2998 on node LA.

/*NOTIFY OPS0001

This JES2 /*NOTIFY statement sends all notification messages to
TSO user OPS0001 at the node where the job was submitted.

KS · New User Joined: 28 Feb 2006 Posts: 91 Location: Chennai

Hi,

In a much simpler way :
NOTIFY - The NOTIFY parameter is used to direct the system, where it has to send the success/failure message after completing the job.
Syntax -> NOTIFY=userid/&SYSUID

//SMYJB JOB (1234Y),'KUTTISATHA',CLASS=8,NOTIFY=&SYSUID
&SYSUID - the userid from which user it has been submited
//SMYJB JOB (1234Y),'KUTTISATHA',CLASS=8,NOTIFY=S22154
It send the sucess/failture message to S22154 userid

Thanks,
KS