More information from my customer:
On their v5r4 system, they are using Client Access System I Navigator Message Monitors to watch for messages and then sends problems to help desk
On the new v7r3 system they are using Navigator for I to do the same thing.
So the things that have changed are OS level (v5r4 to v7r3) and Navigator version (System I Navigator to Navigator for i)
________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Rob Berendt <rob@xxxxxxxxx>
Sent: Wednesday, March 6, 2019 1:06:57 PM
To: Midrange Systems Technical Discussion
Subject: RE: RCVMSG error key not found
I think we'd have to know more.
How did the message get to the message queue?
How did they determine the message key?
What was the message id?
Or you can forget all this garbage and try something like
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%20Technology%20Updates/page/QSYS2.MESSAGE_QUEUE_INFO%20View
If they are sending a message to a message queue with some data just to get the formatted text I would think there would be a better way.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steve Pavlichek
Sent: Wednesday, March 6, 2019 11:56 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RCVMSG error key not found
I'm trying to help a customer out. They are migrating from a v5r4 system to a v7r3 system and they ran into an issue with a message monitoring app developed inhouse. I'm not a developer and haven't done CL in 20 years so I'm not much help.
Any pointers as to how to troubleshoot?
Same code running on v7r3
Message . . . . : 4300 - RCVMSG MSGQ(*LIBL/EDAVIS) MSGKEY(X'00000002')
RMV(*NO) MSG(&MSG) SECLVL(&MSG4)
40 03/05/19 14:15:30.538938 QMHRCVM QSYS 12A9 ALRMSGMSGN
Message . . . . : Message key not found in message queue EDAVIS.
Cause . . . . . : Message key X'00000002' may have been deleted from mes
queue EDAVIS, or message key X'00000002' may not be valid. Recovery . .
When they run this on the v5r4 system:
Message . . . . : 3300 - RCVMSG MSGQ(*LIBL/EDAVIS) MSGKEY(X'00000180')
RMV(*NO) MSG(&MSG) SECLVL(&MSG4)
03/05/19 14:50:01.232712 QCADRV QSYS 03C4 ALRMSGMSGN EDAVIS 0037
Message . . . . : 3600 - SNDMSG
MSG(X'F0F3F0F5F2F0F1F94040F1F4F5F0F0F140C5C4C1E5C9E2404040404040404040404040
404040C3D7C6F1F1F2F6404040404040404040404040404040D8E2C5C3D6C6D9404040400000
01804040404040404040404040404040404040C3D7C6F1F1F2F640C3A499998595A340938982
998199A8408381959596A340828540D8E3C5D4D74B') TOUSR(EDAVIS)
03/05/19 14:50:01.233088 QCLRTNE QSYS 0058 ALRMSGMSGN EDAVIS 0043
Message . . . . : - RETURN /* RETURN due to end of CL program
Thanks
Steve
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
