sigexcp

This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
I am/was hoping to use SIGEXCP as a light weight way to halt a pgm in an manner 
similar to ASSERT in C. Where the pgm does not monitor for the exception, 
causing the default exception handler to kick in and send a CPF9999 to the pgm.

But SIGEXCP  CMP('CPF') ExcpId(X'9898')  results in a CPF2524 ( msg text below 
) being sent to the pgm.  Apparently QMHPDEH has a problem with my exception 
msg.

Is is possible to send a CPF msg with SIGEXCP?

I can send an MCH msg ok, but the MCH msg must be an existing msg id.  Are 
there any user reserved MCH msg identifiers?

It looks like there is less code needed to callx to the send msg api than to 
fill the SIGEXCP template, so SIGEXCP is turning out to be a dead end, but I am 
still interested in knowing the answer.

Thanks,

Steve Richter


Here is the CPF2524 msg that my pgm receives:

 Message . . . . :   Exception handler not available because of reason code 1.

 Cause . . . . . :   An error condition was found when an exception was sent.
   The condition did not allow exception processing to complete normally. The
   reason code within the message identifies the condition that was found.
   Possible values for the reason code and their meanings are as follows:
   Reason Code 1: an exception was signaled directly by using the SIGEXCP
     instruction. The exception was not handled and QMHPDEH was called. The
     exception message had compare data that did not allow QMHPDEH to convert
     the exception into an MCH escape exception.



--