On 10/19/2011 12:53 PM, Kris Buelens wrote: > Wasn't there a change in REXX when it became SAA to tell that the "old" > TRACE NEGATIVE" was rebaptised to "TRACE FAILURE", and then a 16 is > definitively a traceable event.
OK, that's halfway documented. The description of TRACE FAILURE mentions failure conditions and says FAILURE is identical to NORMAL, but the description of NORMAL still says it traces only negative return codes. Time for an RCF! There's also a section about the return code from the host command environment routine itself that shows anything over 12 or under -12 as indicating a failure. Looks like the PIPE environment routine must be returning the issued command's return code as its own: 'callpipe literal exit -13 | rexx *:' /* raises FAILURE */ 'callpipe literal exit -12 | rexx *:' /* ?! raises ERROR */ 'callpipe literal exit 12 | rexx *:' /* raises ERROR */ 'callpipe literal exit 13 | rexx *:' /* ?! raises FAILURE */ ¬R
