|
I seem to be getting these in a job log on a program that sits in a never ending loop until a data area tells it to stop. After x number of seconds it checks the data area, then checks for some other stuff, and it neither then waits again. Job gets restarted by the backup. Starts around 3am and starts generating this message around 10am. As far as we can tell, everything is working ok. IBM said that there was an apar on it very early on in V5R3 but it dealt mainly with stored procedures and the genre, and was fixed in new base code. Here, were just using simple imbedded SQL. Can't get the developer in charge of that project to delve into it since 'it seems to be working - just noticed this in the joblog'. Anyone else came across this and what ramifications there were - if any? Job log's from/to programs never seem to point to our programs - only system type programs. Even in message above and below it. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com
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.