Thanks for the suggestions.
won't work, because I'm trying to see how much CPU time a particular job that has been running for several days taken; I'm not interested in seeing how long some generic command takes to execute. (I started a SAS job several days ago, and one of the ways I'd like to monitor its progress is to see how much CPU time it has taken.)
doesn't seem to work either. The job I started several days ago shows up with time of 00:00:01. The job in question has already produced so much output that I can attest that it has used FAR more than 1 second of CPU time.
It's strange, because in the time it took me to write this message, the top program itself is logging as having a time (in top) of 00:00:82, far more CPU time than the long-running SAS job. Failure to register actual CPU time must be a quirk of the SAS software...