Re: Signal API's

[CRPence <CRPbottle@xxxxxxxxx>]

Scott Klement wrote:
> <<SNIP>>
>
> I do write code that's used as external stored procedures and/or
> UDFs quite regularly, and I have a lot of screwy problems when
> code doesn't behave.
>
> For example, I try to use a debugger to step through the code,
> and it ends up locking up the job and the job becomes
> "un-endable".  Meaning ENDJOB doesn't succeed in ending it after
> it locks up.  (Though, sometimes if you wait long enough it'll
> eventually end.)
>
> Or if the program gets stuck in a loop due to a programming
> error, I can neither debug it nor end the job.
>
> <<SNIP>>

  Unstated what debugger, but if using an interactive debugger, 
then at least for any UDF, always activate debug against a separate 
job using STRSRVJOB rather than ever attempting to use an 
interactive debugger in the same job as the job invoking the UDF. 
That is because, irrespective of the ALWMLTTHD attribute, the DB 
will often run multi-threaded when a UDF is activated, but the 5250 
display file processing [which an interactive debugger would use] is 
not thread-safe.

Regards, Chuck