Re: If MSGTYPE has *NEXT or *PRV specified, MSGKEY is required.

On Wed04-Apr-2011 10:23 , CRPence wrote:

On Wed04-Apr-2011 08:36 , Rusling, John wrote:

<<SNIP>>

<<SNIP>> Though more likely, I believe that as I had suggested
previously, the spooled joblog to show the "To program" information
would best be reviewed to determine how the message might best be
retrieved.

FWiW the "suggested previously" was from a different thread "Trap CPF4128 message via ...":
http://archive.midrange.com/midrange-l/201104/msg00895.html

Again, perhaps the joblog from a job that experienced the originally described problem with the CPF4128 could be provided.? Very probably the attempt to use CPF1002 from ALCOBJ to model what will need to be effected for the CPF4128 issue will give no joy. A quick test showed the CPF4128 was being sent to a program message queue that no longer on the stack and thus would not be available to "normal" RCVMSG requests unless the "3rd party software" is sending that message to your program.

Regards, Chuck