Hello all,
I am working on a task as follows,
1.Need to check what are the JOBs went down in SAR,
2.Collect the reason for the abend jobs - means SYSOUT information
3.format it and send it as mail.
I could able to check the abened JOBs thru SARBCH util, but some one please suggest me how to get the SYSOUT information of that particular job.
I tried googling the utility ISFAFD, but I couldn't find the enough details.
Someone please guide me!!
Many thanks in advance!
Need a help on collecting SYSOUT details from abended jobs
Moderators: Veera, Moderator Group
Need a help on collecting SYSOUT details from abended jobs
Guru:-)
You're never fully dressed without a smile
You're never fully dressed without a smile
- dbzTHEdinosauer
- Moderator
- Posts: 981
- Joined: Mon Oct 02, 2006 8:31 pm
Gurugars,
I realize that you have been tasked by someone for this,
and it is more than likely that you are not at fault for dreaming-up
this misinterpreted ITIL inspired waste of time,
so don't take my comments personally.
You are already at the point where you can identify unsuccessful jobs
and, apparently, identify and direct an email to the appropriate addressee.
Since the sysout often only indicates
but does does not provide enough information
enabling one to solve the problem
(programs must be identified, files/database values must be interrogated)
why waste time with the sysout extract?
Simply send the email with the job identification info to the person responsible for problem solution.
This makes the development of the AUTOMATED NOTIFICATION PROCESS
less resource intensive
and frees up the resources of the developer to attend the actual task that must be addressed:
FIXING THE PRODUCTION CODE.
Gurugars,
I know that the clown that manages you will never be dissuaded from this
idiot notification process,
so, go to the SAR documentation,
which details how these silly processes are accomplished.
I realize that you have been tasked by someone for this,
and it is more than likely that you are not at fault for dreaming-up
this misinterpreted ITIL inspired waste of time,
so don't take my comments personally.
You are already at the point where you can identify unsuccessful jobs
and, apparently, identify and direct an email to the appropriate addressee.
Since the sysout often only indicates
but does does not provide enough information
enabling one to solve the problem
(programs must be identified, files/database values must be interrogated)
why waste time with the sysout extract?
Simply send the email with the job identification info to the person responsible for problem solution.
This makes the development of the AUTOMATED NOTIFICATION PROCESS
less resource intensive
and frees up the resources of the developer to attend the actual task that must be addressed:
FIXING THE PRODUCTION CODE.
Gurugars,
I know that the clown that manages you will never be dissuaded from this
idiot notification process,
so, go to the SAR documentation,
which details how these silly processes are accomplished.
Dick Brenholtz
JCL, SQL and code in programs have an irritating habit of doing what you say,
not what you meant.
JCL, SQL and code in programs have an irritating habit of doing what you say,
not what you meant.
FREE TUTORIALS
Tutorials
Free tutorials from mainframegurukul
- JCL Tutorial
Covers all important JCL concepts. - Cobol Tutorial
This tutorials covers all Cobol Topics from STRING to COMP-3. - DB2 Tutorial
DB2 Tutorial focuses on DB2 COBOL Programming. - SORT Tutorial
This Tutorial covers all important aspects of DFSORT with examples - CICS Tutorial
This CICS tutorial covers CICS concepts and CICS Basics, CICS COBOL Programming.
Interview
Mainframe Interview questions
- Cobol Interview Questions
50+ Interview Questions - JCL Interview Questions
50+ Interview Questions - DB2 Interview Questions
100+ Interview Questions - CICS Interview Questions
70+ Interview Questions - VSAM Interview Questions
27 Interview Questions
Other References
Mainframe Tools and others
- XPEDITER Reference
Explains how we can debug a program - FILEAID Reference
Explains how to browse , edit and delete datasets - Change Man Reference
Quick Start tutorial on Changeman - Abend Reference
Important Abend codes explained - FaceBook Page
MainframeGurukul FaceBook Page - LinkedIn Page
MainframeGurkul Linkedin Page