RE: Proper way to die...

[Rich Duzenbury <rduz-midrange@xxxxxxxxxxxxxxxxxxx>]

On Thu, 2005-03-17 at 14:15 -0600, Bob Cozzi wrote:
> Have you tried this?
> 
> Callp(e)  Die('Crush, kill, destroy...')
> If  %Error()   //  Die procedure ended in error.
> Endif
> 
> (Sorry, you've had to have been a fan of the old Lost in Space show to
> appreciate that one.)
> 
> You're problem is that you need to send the message to the control boundary
> not *PRV or *SAME as we're used to. Use *CTLBDRY or whatever that value is,
> in stead of '*' and see if it works. 

Bob, thanks for the suggestion.

I found that using the above code with the stack entry set to '*' and
the count at 0 is a good way to lock up the device.  The call stack for
the job shows that it's calling 'sleep'.  After about a minute, the
sleep times out and finally shows the message 'The call to DIE ended in
error'.

I also tried *CTLBDY and *PGMBDY, they work the same as setting the call
stack entry to the program name, and the call stack count to 1.  That
is, the application doesn't throw an inquiry message, but instead a
CEE9901 INFO message on the message line after the program ends -
'Application error. CPF9898 ummonitored by ZZZ_PH at statement *N,
instruction x'0000'.

--
Regards,
Rich

Current Conditions in Des Moines, IA
Overcast
Temp 57.2F
Winds out of the Northeast at 9mph