Re: MONMSG CLP Question

On 18 Mar 2013 09:51, CRPence wrote:

On 18 Mar 2013 09:26, Rich Loeber wrote:

<<SNIP>>
Anyone ever run into this?

Most likely there is a defect <<SNIP>>

From some older releases, there was an APAR and PTFs on those releases to correct an issue where RTVMBRD apparently resent a CPF9999 [i.e. *FC] instead of one of the messages capable of being monitored:

http://www.ibm.com/support/docview.wss?uid=nas263cb510ba3f1d4dd8625713100423d3e
"An application exists that monitors for msgCPF3018 when using the RTVMBRD command. This allows the application to trap the condition when the member has been deleted. However, the application started failing with msgMCH3402 t/QWHRMBRD x/2400 effects *FC instead of msgCPF3018."

Whatever is the issue described in this message thread, is likely similar to that APAR; both by origin and effect. Although this message thread implies the *FILE going missing rather than the member. Anyhow, there is a very specific locking protocol for database *FILE objects that every interface must utilize to ensure consistency of the interface to the access of database members. The Where Used component [the WH of QWH* naming] may be properly using this locking protocol, however still could be incorrectly referring to pointers obtained but not verified or pointers referred-to before the LOCK processing was requested... thus causing its processing to terminate abnormally. Within a specific path\stream of activity within the OS code, often a MCH3402 monitor will remain active across some set of instructions knowingly referring to a specific object-pointer, from which the /assumption/ would be made that any x2202 condition sufficiently implies that /the object/ was since deleted.... and thus the handler for that monitor just sends its "not found" condition; and likely the WH code is [like in the APAR above] has some code where such a monitor is not in-effect. Of course with a database *FILE, /the object/ could be the File or Member [and in some cases even other objects that make up the composite DBF object].