×
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.
There's been a little bit of a discussion here about the SRVMONxx jobs.
I, too, have 78 of these running but, after the discussion and
investigation, decided they were OK. But this morning, when I checked
QSYSOPR's messages something strange popped out:
Message ID . . . . . . :
CPI3999
Date sent . . . . . . : 07/27/07 Time sent . . . . . . :
05:03:58
Message . . . . : Watch session SRVMON0000 issued by
223998/QUSER/QZRCSRVS
at 07/23/07 11:31:43 has been ended. Reason code:
X'08'
Cause . . . . . : Watch session SRVMON0000 issued by
223998/QUSER/QZRCSRVS
and associated with QSCSWCH has been ended. Reason code: X'08'. The
possible
reason codes
follow:
08 - End Watch (ENDWCH) command or End Watch (QSCEWCH) API was issued.
The above is just a sample of 78 such messages sent between 05:03:58 and
05:05:15.
Now the other side of the coin is that the jobs are running again. The
start times range from 05:05:20 and 05:05:34.
I know that I didn't issue the ENDWCH command. Any clues?
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
