|
Peter, I checked the cable and it is attached .... but your note got me to thinking and I check the system log (DSPLOG) for the time this morning when this happened. At the EXACT same time, a batch job running in QSYSWRK shut down on its own. This is a job that turns itself off and then back on once a day. It must be related in some way to this event. Rich ------------------------------------------------------------------------ Peter Levy wrote:
Hmmm, power dips... Do you have the UPS signal cable hooked up to the system? One time I experienced a situation where the O/S had sent messages to QSYSOPR and then delete it again when a transient situation righted itself. I can't remember now what that situation was, but I wonder if the UPS signal might cause the O/S to send a message and then delete it again right away because the power came back on so quickly. Just grabbing at straws on this. Let us know what you find from the trace. Rich Loeber wrote:Peter, The only thing that comes to mind is that our area has a somewhat unstable power grid by most modern conventional standards. I have seen this message issued when we have a power dip. But I would still expect to see a message in the message queue. Our system is on a UPS that is in good working order. I have activated CL program logging on the job now so that I can get a better trace of program activity if it happens again. Rich ------------------------------------------------------------------------ Peter Levy wrote:Bit-rot? But seriously, I take it that this is a random occurrence that can't be nailed down to some other event in the system. I've only ever gotten this message when the message key was corrupted in some way or the message was deleted. Unless the O/S has some kind of new feature that periodically re-numbers the existing messages giving them new message keys. Rich Loeber wrote:Peter, Well, there is only one user on the system .... me .... and the application locks the message queue so that nobody else can access it to delete messages. I wonder how a key can get corrupted after a wait of an hour and a half .... this one really puzzles me. Thanks for the suggestions. Rich Loeber Kisco Information Systems http://www.kisco.com ------------------------------------------------------------------------ Peter Levy wrote:Sounds like someone deleted a message from the message queue, but you also might have a corrupted message key. Rich Loeber wrote:I have an application that is monitoring the QSYSOPR message queue looking for any messages with a severity of 70 or higher. Every once in a while, like once a week or so, I get a CPF2410 on this job. The details of the error read: Additional Message Information Message ID . . . . . . : CPA0702 Date sent . . . . . . : 11/03/06 Time sent . . . . . . : 07:40:39 Message . . . . : CPF2410 received by procedure WEBMSGMONC. (C D I R) Cause . . . . . : ILE Control language (CL) procedure WEBMSGMONC in module WEBMSGMONC in program WEBMSGMONC in library WEBREPORT detected an error at statement number 0000015700. Message text for CPF2410 is: Message key not found in message queue QSYSOPR. Use F10 (if available) or the Display Job Log (DSPJOBLOG) command to see the messages in the job log for a more complete description of what caused the error. If you still are unable to solve the problem, please contact your technical support person. Recovery . . . : This inquiry message can be avoided by changing the procedure. Monitor for the error (MONMSG command) and perform error recovery within the procedure. To continue, choose a reply value. When I check the QSYSOPR message queue, the last message in the queue is time stamped one hour and twenty minutes before this error happened. So, I have no idea where the message is that the message key was invalid for. I'm open to suggestions. Could this be some sort of a timeout issue? Rich Loeber Kisco Information Systems http://www.kisco.com-- Peter Levy Alliance Shippers, IT Dept Englewood Cliffs, NJ Voice: 201-227-0400 Fax: 201-227-0925 Email: plevy@xxxxxxxxxxxx AIM: pklevyalliance2 --------------- There are 10 kinds of people in the world; Those who understand binary and those who don't. ------------------------------------------------------------------------ -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.-- Peter Levy Alliance Shippers, IT Dept Englewood Cliffs, NJ Voice: 201-227-0400 Fax: 201-227-0925 Email: plevy@xxxxxxxxxxxx AIM: pklevyalliance2 --------------- There are 10 kinds of people in the world; Those who understand binary and those who don't. ------------------------------------------------------------------------ -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.-- Peter Levy Alliance Shippers, IT Dept Englewood Cliffs, NJ Voice: 201-227-0400 Fax: 201-227-0925 Email: plevy@xxxxxxxxxxxx AIM: pklevyalliance2 --------------- There are 10 kinds of people in the world; Those who understand binary and those who don't. ------------------------------------------------------------------------ -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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
