View previous topic :: View next topic
|
Author |
Message |
krishnasaikiah
New User
Joined: 14 Mar 2007 Posts: 24 Location: gurgaon
|
|
|
|
Hi all,
I want to know how do I throw an error message into the system log everytime the job abends or the job fails because of JCL error.
I have thought of a solution but is not working as I had desired.
//STEP EXEC PGM=IEBGENER,
COND=ONLY
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD *
JOb ended in error
/*
//*
Can anybody please suggest me a solution?? |
|
Back to top |
|
|
Phrzby Phil
Senior Member
Joined: 31 Oct 2006 Posts: 1042 Location: Richmond, Virginia
|
|
|
|
I don't know how to do it, but I would not expect every line of output from a job to be written to the system log, so no reason this line would be either. |
|
Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004 Posts: 4652 Location: Raleigh, NC, USA
|
|
|
|
I don't understand the problem. Any job that fails with a JCL error IS automatically written to the syslog, usually with the IEF453I or IEFC452I error messages.
However, as far as I know, the only way to write information into the syslog is via a WTO (Write-To-Operator) function from a program. |
|
Back to top |
|
|
krishnasaikiah
New User
Joined: 14 Mar 2007 Posts: 24 Location: gurgaon
|
|
|
|
I want to get the message displayed in the console and not log. Sorry for the inconvenience. |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10873 Location: italy
|
|
|
|
I would say that displaying messages on the console is pretty useless,
the system consoles are usually in roll delete mode and with the usual traffic
messages tend to disappear and
very seldom the operation team have a chance to see them |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
What is the requirement for this request ? |
|
Back to top |
|
|
krishnasaikiah
New User
Joined: 14 Mar 2007 Posts: 24 Location: gurgaon
|
|
|
|
Hi all,
I need to have the message in the console in case of a job abend as because we keep monitoring the console part for support.
In case of a job abend in production it becomes very easy if we get a message on the console otherwise until we get a call from the user we dont know if a job has abended.
Thanks
Krishna |
|
Back to top |
|
|
krishnasaikiah
New User
Joined: 14 Mar 2007 Posts: 24 Location: gurgaon
|
|
|
|
hi all,
Another related problem.
Suppose I have two input datasets. One dataset exists and the other doesnt. And I have declared disposition for both the datasets as SHR. So during execution the job gets failed. In this scenario , I want a last step to get executed where the message will be displayed in the console that my job got abended.
Is there any way of handling this type of problem???
Thanks
Krishna |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10873 Location: italy
|
|
|
|
You are asking again the same thing,
adding the unrelated consideration about two datasets with disp SHR
Keep wondering about the logic
just a note...
if a job gets flushed for jcl error no step will be executed
so nobody will be able to issue any message |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10873 Location: italy
|
|
|
|
I kindly ask...
will You please explain the difference between looking at a user message
and at for example
Code: |
IEF450I any_jobname any_stepname - ABEND=S806 U0000 - REASON=00000004
|
|
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
If you have a scheduling package, then any abnormal terminations are flagged in there.
Why not watch that screen instead of trying to make things more complicated. |
|
Back to top |
|
|
|