Thanks. No one can ENDJOBABN, but I have been going over the History reports from both machines and doing some compares.
There were several jobs on both that ended with code 30 (The job ended abnormally). But since one machine is still at Normal and these are the same jobs, I doubt they caused the production server to go into Abnormal.
I did find job 417382/QIBMHELP/QJVACMDSRV that ended with code 80 (The job ended (ENDJOBABN command)), which is probably the culprit. Why it went abnormal is a mystery.
I've got more research to do when I get back Monday.
Jerry C. Adams
IBM System i Programmer/Analyst
I don't see, Mr. Speaker, why we should put ourselves out of the way to serve posterity. What has posterity ever done for us? - Sir Boyle Roche
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
