Presumably you are asking to put the report on hold, not the job on hold,
because you do not know until the spool file blows up that this or that job
is responsible.

If you increase to *NOMAX, perhaps the problem is that the program has got
into a loop & will run forever, so you may also need to put some time or
resource constraint on it ... if it does not get to EOJ in some reasonable
time period, then you want to stop it one way or another.

Perhaps the job should be transferred to a different JOBQ so that if you stop
the job, you do not stop whatever was behind it on the same JOBQ.

MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac)


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.