MVS has -in VM eyes- special meanings for return codes, or, standards. Going from 4 = Warning, over 8 and 12 to 16 = failure.
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. 2011/10/19 Glenn Knickerbocker <[email protected]> > I finally got fed up enough with the extra step of allocating a new data > set to write myself a front-end to >MVS to do it for me. Before I go > any further with figuring out how much more function I might want in it, > has anybody done this already? > > If not, any recommendations for useful defaults? I picked RECFM(V,B) > LRECL(32756) BLKSIZE(32760) SPACE(10,100) CYL. > > In checking for existence of the data set, I ran into an oddity with the > REXX TRACE setting. With TRACE N, I get trace output not just when the > return code is negative, but also when it's > 12. Any idea what's going > on here? I poked through the TSO REXX books looking for anything > special about TRACE in the MVS address space, but only found a note > about messages in the output file in MVS batch. > > ¬R > -- Kris Buelens, IBM Belgium, VM customer support
