Joined: 25 Nov 2010 Posts: 70 Location: Sivakasi, India
When sometimes error or abend occurred after the job running i could able to figure out the errors. But for some other jobs, i couldnt able to find the cause of the error. Is there any way of learning thru materials or any other references on how to identify the cause? Simply saying i need to know - how to track the cause of error after a job abends!
The main reason of asking this help is i was given training in mainframes for only 14 days which covered COBOL, DB2, JCL and CICS. But now i am putting my own efforts to study and learn all these thru experience.
Your kind suggestion would get me some knowledge on this.
Joined: 03 Oct 2009 Posts: 1777 Location: Bloomington, IL
There is indeed no way to resolve every abend save by using intelligence guided by experience. However, I urge to you to save links to manuals or information centers for the version of z/OS (or z/VM or other operating system) used at your site (mine uses z/OS 1.11; look particularly at the MVS System Codes and System Messages manuals).
The messages and the abend ("completion") codes will be found in the JES message log (JESMSGLG). Starting from these, many common abends are fairly easy to diagnose and resolve.
Joined: 06 Jun 2008 Posts: 8165 Location: East Dubuque, Illinois, USA
The IBM System Codes manual lists over 600 abend codes possible for just IBM software. There are thousands of other possible abends for ISV (independent software vendor) products. There is no one simple method to resolve all of these -- in some cases, you must contact the vendor and work with them (sometimes, for weeks or even months) to identify the root cause of the abend and fix it.
Generally, the more abends you see and fix (or help fix), the more you can identify. However, it will take you years to gain the experience to resolve most abends in a short time. The mainframe is a very complex, well established architecture of more than 45 years and 14 days of training cannot begin to give you more than a thin layer of knowledge about the various components of the mainframe.
The vendor manuals on abend codes are your bible -- they tell you what the vendor believes to be the cause, and in many cases something about how to fix the abend. Learn where these manuals are at your site and use them for every abend.
Joined: 23 Nov 2006 Posts: 19270 Location: Inside the Matrix
Is there any way of learning thru materials or any other references on how to identify the cause?
As i suggested te someone yesterday:
I'm not aware of any particular publication that covers even most of what you want.
Suggest you look thru some of the many problem topics that have been discussed in our forum. Think back to some problem(s) that have happened on your system and then see if something similar was posted here.
The more problems you are involved with the more easily you will recognize the problem. This will not happen overnight or even over year end - but don't be discouraged. You will most likely be doing this for another 20-30 years
Many of the "opportunities" that will arise have been discussed in topics in the forum. Lots of answers already there for you to use.
If you have the system availability, you could cause some abends of your own to see how these are presented by the system.