View previous topic :: View next topic
|
Author |
Message |
JCLfreak
New User
Joined: 07 May 2009 Posts: 3 Location: Hagerstown MD
|
|
|
|
What is the best way to detect a loop for a batch job? I believe that the no I/O should indicate this but then there are other issues.. and what about a write loop which would be very difficult to see? |
|
Back to top |
|
|
CICS Guy
Senior Member
Joined: 18 Jul 2007 Posts: 2146 Location: At my coffee table
|
|
|
|
Quote: |
and what about a write loop which would be very difficult to see? |
Not once you start running out of DASD or JES space..... |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Loops may include I/O or not -- a program reading directly the same VSAM record over and over, or writing output to spool -- so the only reliable indicators are (1) CPU time limit is hit, no matter what it is set to, or (2) a debugger is used to watch the execution. A loop with a write will usually generate messages about the number of lines being exceeded but that is determined by the site, and the program may possibly fill the spool space up, but CPU time limit exceeded I have found to be the best red flag to look at what is going on. Sometimes the number of records can cause the CPU to be exceeded, but that's fairly rare. |
|
Back to top |
|
|
JCLfreak
New User
Joined: 07 May 2009 Posts: 3 Location: Hagerstown MD
|
|
|
|
I guess if you are monitoring in TMON then the I/O would not change for the input file? |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Probably not.
d |
|
Back to top |
|
|
JCLfreak
New User
Joined: 07 May 2009 Posts: 3 Location: Hagerstown MD
|
|
|
|
I don't have a copy of the job.. It happened last week. The thing was processing almost 5 hours before someone finally saw that it was looping. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Suggest someone find out why the job was not "timed out" automatically. . . |
|
Back to top |
|
|
|