×
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.
We had a job hang last night and the only way we could kill it was to
follow IBM's advice and IPL the system.
We will never know what the root cause because not enough info was
gathered prior to the IPL and because the system was a 45 minute drive away.
We do know that it was a commitment control issue with some SQL and that
it was related to exceeding the maximum of seq numbers in a journal
receiver. The job was initiated via and ODBC connection.
After two hours the user ended the job with a *immed. The iSeries then
began a rollback using the journal which ran for nine hours before it
was discovered.
All attempts to kill the job outright failed:
endjob *immed
endjob *immed
endjobabn (abnormal)
endhostsvr *all *all
endsbs qusrwrk *immed
Only an IPL could clear the condition. The system did its best to to
apply the journal receiver post IPL but file integrity cannot be
established.
The file was recreated and life goes on.
Jerry
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
