× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



When we went to v3r7 a couple of years ago I was testing a program that went
into an infinite loop--naturally, I wrote it--and somehow it managed to
reset an OS flag that prevented other programs getting their turn at the
CPU.  This was IBM's analysis.  Took 'em about a week to look at the dump.
They sent us a PTF.  

I've seen PDF jobs run away like that.  We had one a couple of months ago
when I was on call.  The operator on duty and I managed to slow it down
enough so we were able to get to a place in the nightly batch processing
where we could IPL gracefully.  When the last part of the job was about to
end, I called the computer room to let the operator know that it would be OK
to IPL very soon.  The next operations shift had just started.  The
graveyard operator argued with me about whether or not we needed to do the
nightly backups before the ipl. "We always do the backup before we IPL," he
said.  Meanwhile the PDF job had crept up to over 90% of the CPU at runpty
99 timeslice 1.  He wouldn't budge.  I finally had him call the operations
manager.  She and I had a good laugh the next morning although she wasn't
too pleased to get a call about something she had already told the swing
shift operator to do.   
> -----Original Message-----
> From: Debbie Helms [mailto:DHelms@Lance.com]
> Sent: Thursday, September 23, 1999 8:56 AM
> To: 'MIDRANGE-L@midrange.com'
> Subject: RE: errors
> 
> 
> David - I tried everything to get rid of the jobs.  I could 
> not change,
> hold, or end the jobs.  Where would I look to determine what 
> the problem
> was?  I have sent a main storage dump to IBM - I don't really 
> expect to hear
> from IBM in reference to this dump.  We did run srvtrc on the 
> jobs that were
> running.  I have pages and pages of trace information.  I have wrapped
> joblogs, history, lic logs.  I really don't know what I'm 
> looking for.  I am
> afraid that we will experience this problem again if we don't 
> find the cause
> of this problem.     
> I agree that it sounds like os400 when you can not flush a 
> job - but try to
> argue with IBM.
> 
> 
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

This mailing list archive is Copyright 1997-2024 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.