Options that are most useful for debugging and finding error



JES, JES2, JCL utilities, IDCAMS, Compile & Run JCLs, PROCs etc...

Options that are most useful for debugging and finding error

Postby rravi3421 » Thu Dec 04, 2008 12:43 am

What are the options that are most useful for debugging and finding errors in jcls?
what are different ways we can track the errors in jcls?
what is role of compiler options?
Thank you very much for help.
User avatar
rravi3421
 
Posts: 7
Joined: Sun Nov 16, 2008 3:30 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Options that are most useful for debugging and finding error

 

Re: Options that are most useful for debugging and finding error

Postby dick scherrer » Thu Dec 04, 2008 3:18 am

Hello,

When there is a jcl error, the system shows the error and tells the reason. You will not need to look hard to find them.

What would you want to track? Once corrected (which should be in testing) they will not happen again so there would be nothing to track. Possibly i misunderstand what you are looking for. . .

Compiler options aren't really jcl. They tell the compiler when to behave differently than the system/site defaults. Typically, the defaults should be used.
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 91 times


Return to JCL

 


  • Related topics
    Replies
    Views
    Last post