Author: Robert Sample
Posted: Tue Sep 06, 2016 12:18 am (GMT 5.5)
Where is the S0C4 showing up? And you do NOT want to use the WTO on that value -- it is a 64-bit binary value with bit 51 representing 1 microsecond, so without some work you won't see anything human-readable from the WTO.
I suspect you're probably getting the S0C4 right after the STCK instruction, because it is unlikely that the value represents valid z/OS OP codes. You need to move the TODCLOCK definition after your return.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth
Posted: Tue Sep 06, 2016 12:18 am (GMT 5.5)
Where is the S0C4 showing up? And you do NOT want to use the WTO on that value -- it is a 64-bit binary value with bit 51 representing 1 microsecond, so without some work you won't see anything human-readable from the WTO.
I suspect you're probably getting the S0C4 right after the STCK instruction, because it is unlikely that the value represents valid z/OS OP codes. You need to move the TODCLOCK definition after your return.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth