IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

What is the best way to debug a Job Fail?


IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
toughmetals

New User


Joined: 10 Jan 2006
Posts: 14
Location: India

PostPosted: Fri Jan 13, 2006 6:41 pm
Reply with quote

Hi Chaps,

I will always get quite problem in debugging if a JCL Fails.

Is their a flow which we should follow or several standard steps so that we can easily track the problem ?

Thanks,
Deeps
Back to top
View user's profile Send private message
Bitneuker

CICS Moderator


Joined: 07 Nov 2005
Posts: 1104
Location: The Netherlands at Hole 19

PostPosted: Fri Jan 13, 2006 6:58 pm
Reply with quote

Try forum ABENDS & Debugging. You'll find a lot of info and documents.
Back to top
View user's profile Send private message
priyesh.agrawal

Senior Member


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

PostPosted: Fri Jan 13, 2006 7:19 pm
Reply with quote

In Broader terms....

1> Identify the step at which job failed.
2> Identify the abend code at the step failed.
3> Identify the related sysout messages for that step.

Did I miss anything.... If you are thru with these steps... & getting problem of having ABEND CODES & reasons explained.....refer to the section suggested by Mr. Bitneuker.

Regards,

Priyesh.
Back to top
View user's profile Send private message
Bitneuker

CICS Moderator


Joined: 07 Nov 2005
Posts: 1104
Location: The Netherlands at Hole 19

PostPosted: Fri Jan 13, 2006 7:25 pm
Reply with quote

In addition: it's not the JCL that abends but the program (seldom a utility) being executed by JCL control statements. It's not a fact the job stops executing following steps in case one program abends. This may occur when one or more following steps contain COND=ONLY meaning these steps may only be executed in case of a prior abend.
Back to top
View user's profile Send private message
priyesh.agrawal

Senior Member


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

PostPosted: Fri Jan 13, 2006 7:57 pm
Reply with quote

Thanks to Mr. George... I got another point which may be useful to you in this topic.
Quote:
it's not the JCL that abends but the program (seldom a utility)

You should always check the job by some pre-specified commands (depends on shop specification like JEM, !JCK etc...) to get any syntactical error which may lead to a JCL ERROR or the ABEND.

Regards,

Priyesh.
Back to top
View user's profile Send private message
Bitneuker

CICS Moderator


Joined: 07 Nov 2005
Posts: 1104
Location: The Netherlands at Hole 19

PostPosted: Fri Jan 13, 2006 8:05 pm
Reply with quote

Hi Priyesh (and others),

Sorry to confuse you about my name. Mazzels is one of the many ways we use to say 'Good by'. I adjusted my profile thus revealing a bit of my true identity. icon_wink.gif
Back to top
View user's profile Send private message
toughmetals

New User


Joined: 10 Jan 2006
Posts: 14
Location: India

PostPosted: Mon Jan 16, 2006 11:58 am
Reply with quote

These was very useful to me.

Many Thanks,
Deeps
Back to top
View user's profile Send private message
pa1chandak
Currently Banned

New User


Joined: 31 Jan 2006
Posts: 55

PostPosted: Wed Feb 01, 2006 8:58 pm
Reply with quote

you can try TYPERUN=SCAN

IT WILL ONLY SCAN THE JCL FOR ERRORS


IF I AM WRONG SOMEWHERE PLEASE CORRECT ME

THANK YOU

DO SEND ME THE REPLY

PAWAN

09822546416

// THE ONE I LOVE , I SHALL NEVER BLAME //
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> JCL & VSAM

 


Similar Topics
Topic Forum Replies
No new posts DEBUG COMMENT command not adding to log IBM Tools 1
This topic is locked: you cannot edit posts or make replies. JCL execution fail COBOL program COBOL Programming 5
No new posts Debug set up for COBOL module but ope... IBM Tools 1
No new posts How to DEBUG DB2 Stored Procedures Us... DB2 0
No new posts Connect Direct - using DEBUG=TRACE Bits All Other Mainframe Topics 4
Search our Forums:

Back to Top