If you insert a piece of REXX in front of the LOOKUP stage it will see return code 12 on an OUTPUT command. Normally you could then do COMMIT 0 to sample the aggregate return code, but that won't work because of the bug (which to some extent has become a feecher). You'd have to guess whether the severance is due to LOOKUP going belly up or something downstream of LOOKUP blowing up, but in the latter case COMMIT is likely to offer information in the form of a non-zero return code.
So, if your REXX code decides that it is LOOKUP that went bellyup, exit nonzero and the rest of the world would not know the difference. Cheers, j. On 1 March 2010 17:11, Alan Winson <[email protected]> wrote: > Thanks for the follow-up, John. I will code around the bug for now and > look > forward to a fix in a new release. > --Alan >
