Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

NOTIFY parameter

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
rahul_desai29

New User


Joined: 15 Mar 2006
Posts: 10
Location: fl;jds

PostPosted: Tue Mar 21, 2006 11:59 am    Post subject: NOTIFY parameter
Reply with quote



If you give NOTIFY=??? what it means?
Back to top
View user's profile Send private message

priyesh.agrawal

Senior Member


Joined: 28 Mar 2005
Posts: 1452
Location: Chicago, IL

PostPosted: Tue Mar 21, 2006 12:24 pm    Post subject: Re: NOTIFY parameter
Reply with quote

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

It means your job is going to fail because of JCL ERROR.
The reason would be Invalid Value for NOTIFY Parameter.

If you would like to go thru complete referrence for Notify...click here...

Regards,
Priyesh.
Back to top
View user's profile Send private message
vasa
Warnings : 1

New User


Joined: 10 Jan 2006
Posts: 9

PostPosted: Tue Mar 21, 2006 1:42 pm    Post subject:
Reply with quote

it direct the error messages to the particular user

/*NOTIFY userid
Back to top
View user's profile Send private message
martijn

New User


Joined: 09 Mar 2006
Posts: 14
Location: The Netherlands

PostPosted: Tue Mar 21, 2006 3:24 pm    Post subject:
Reply with quote

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;
Code:

10.48.45 JOB11564 $HASP165 NEX0015X ENDED AT NME1NJE  MAXCC=0 CN(INTERNAL)
***                                                                       


or if the job failed (and what step it failed in):
Code:

 10.49.30 JOB11565 $HASP165 NEX0015X ENDED AT NME1NJE - TSOBATCH S010 CC=12 CN(I
NTERNAL)                                                                       
 ***                                                                           


N.B.: if you code NOTIFY=&SYSUID, the submitter will be notified!

Regards,
Martijn
Back to top
View user's profile Send private message
Gautam512

Active User


Joined: 05 Oct 2005
Posts: 309
Location: Vizag / US

PostPosted: Tue Mar 21, 2006 5:08 pm    Post subject: Re: NOTIFY parameter
Reply with quote

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.
Back to top
View user's profile Send private message
KS

New User


Joined: 28 Feb 2006
Posts: 91
Location: Chennai

PostPosted: Wed Mar 22, 2006 12:42 pm    Post subject:
Reply with quote

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
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Can DFSPARM override SORTKEYS paramet... ashek15 DB2 2 Tue Jan 31, 2017 11:36 pm
No new posts DDNAME parameter mistah kurtz JCL & VSAM 6 Mon Dec 19, 2016 4:41 pm
No new posts Execessive parameter issue Sumeendar JCL & VSAM 5 Mon Dec 19, 2016 4:35 pm
No new posts TOT & DATE parameter in ICEMAN hemanthj642 DFSORT/ICETOOL 4 Mon Nov 14, 2016 5:19 am
No new posts How to display value of an exit param... lind sh CICS 2 Sun Oct 09, 2016 12:28 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us