×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I did check for that and, as explained in my initial post, the CPF9999 is
not listed either. In the joblog detail, the only messages showing are
MCH3402 and CPF9999.
Rich
--------------------------------------------------------------------------
On 3/18/2013 12:40 PM, TheBorg wrote:
Rich -
CPF9999 should catch it, but first look at the expanded help text for the
RTVMBRD command for the list for monitorable messages.
Methinks you should be monitoring for one or more of *those* messages, like
CPF9812 (File &1 in library &2 not found.).
-sjl
"Rich Loeber" wrote in message
[1]
news:mailman.18494.1363624034.10847.midrange-l@xxxxxxxxxxxx...
I have a CLP with a CHKOBJ for a specific *FILE object followed by a
RTVMBRD statement for the same file. Immediately after this statement, I
have a MONMSG for a MCH3402just in case the *FILE object is deleted
between when the CHKOBJ and RTVMBRD happen.
The problem is that when this actually does happen, the MONMSG seems to
be
ignored. The CLP throws the MCH3402 immediately followed by a CPF9999.
When I look at the help text for the RTVMBRD, neither the MCH3402 or the
CPF9999 are listed as errors that can be monitored for.
Anyone ever run into this? Would changing the MONMSG to watch for
CPF9999
do the trick?
Rich Loeber - @richloeber
Kisco Information Systems
[1][2]
http://www.kisco.com
References
Visible links
1. [3]
http://www.kisco.com/
References
Visible links
1.
news:mailman.18494.1363624034.10847.midrange-l@xxxxxxxxxxxx
2.
http://www.kisco.com/
3.
http://www.kisco.com/
midrange.com
