Re: Error checking upon program entry

["Carel Teijgeler" <coteijgeler@xxxxxxxxx>]

John,

I would think such  errors should be trapped in programme A, before calling 
programme B.

If you want to trap the error at the beginning of programme B, then read the 
record (if it has been written or updated) based on the passed key, and do the 
test all over again. On error return with a MSGID.

But I think that is unnecessary, and perhaps not your intention either.

According to your message the test is done in programme B (calling  user exit 
UMBCOD9R for the first time), so why calling programme B?

Can you elobarate on your request?

Regards,
Carel Teijgeler


*********** REPLY SEPARATOR  ***********

On 15-4-04 at 15:27 John Furniss wrote:

>I'm trying to trap for an error that occurs before my program gets 
>called (eg) "promise date earlier than request date" error in Mapics order
>entry. When this error happens, the user exit UMBCOD9R is getting called for
>the second time at the detail item entry level. I need to trap for this
>immediately upon the start of my program. Is this possible? I tried %error
>and %status, but those appear to only work after performing an operation.