Re: Message ID CPF2410?

Bruce,

Thanks for this additional input.  I checked for the additional informational
messages that would indicate that a wrap had taken place and it does not seem
to be the case.  This is a development box that does not get a lot of day
in/day out use and I doubt that the QSYSOPR message queue has ever wrapped in
its entire life.

Rich
  ------------------------------------------------------------------------

Bruce Vining wrote:

Is it possible that QSYSOPR wrapped (the default action)?

From the Information Center:

When the message queue is full, the oldest informational and answered
messages are removed from the message queue to allow space for new
messages to be added. If the removing of the informational and answered
messages does not provide enough space to add the requested message, then
unanswered inquiry messages are removed until there is space to add the
requested message. The default reply is sent before an unanswered inquiry
message is removed. When the message queue is wrapped, CPI2420 or CPI2421
will be sent to the queue that was full to indicate it was wrapped. If
there is no space on the queue to send these messages they are sent to the
joblog of the user that was sending the message to the queue and they are
sent to QHST if the full queue is QSYSOPR.
NOTE:
When a queue uses *WRAP and a job sends a message to the queue that causes
a wrap, messages are removed for the following conditions in order to
perform the wrap:
the queue is in break or notify mode for a job
a job is in a message wait state because it did a receive function on the
queue with a wait time specified
the queue is allocated by a job via the ALCOBJ command
Only the system wrap function can remove messages from queues in these
conditions. Other jobs still are not allowed to remove messages from the
queues during these conditions. With *SNDMSG, these conditions do not
allow another job to remove messages from the queue.
Also when a queue specifies *WRAP and it is in break mode, the wrap
function only removes messages that have been received by the
break-handling program. For example, if the break-handling program did not
receive all messages from the the queue and it was becoming full, CPF2460
could be issued because messages could not be removed to perform the wrap.

Top
This is just a guess and I hope it might help,
Bruce Vining

Rich Loeber <rich@xxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
11/03/2006 08:46 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>

To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: Message ID CPF2410?

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.

--
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.

--
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.