STRING is the one thing that I am not familiar with and cannot confirm that it is correct.
What is in DBLWD2 after the CVD? (Packed is pretty "human-readable.") Or you could post the expansion of the STRING macro. I think some of the other replies may be red herrings. Assuming that your program is fairly straightforward with no multitasking or SRB dispatches or DB2 calls then TIMEUSED should give you the CPU time for the one and only task. Charles -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of Mike Hochee Sent: Sunday, September 22, 2019 4:14 AM To: [email protected] Subject: Re: Converting TIMEUSED macro output to printable time used Hi Brian, I looked at a test rtn that does this sort of thing, and it is very similar to yours, up until the STRING macro. The only differences being the shift to get you microsecond aligned (tod vs. mic) and the thousandths vs. hundredths, and those look good. I'm guessing the problem is in your STRING macro, or the invocation.
