|
Rob wrote: > But they jump up to eating an entire one of > our processors and a big chunk of our > interactive capability. Job still shows on > WRKACTJOB dang near three hours later. > We ended the job *immed and it's gone now. There was a bug in workstation error handling many moons ago, but I think that's pretty much been addressed. I would look to the program that was running at the time. It sounds a lot like an error trap that tries to display a message back to the user: monitor exfmt screen chain z-add eval on-error exfmt errordisplay --buck
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.