Two SAS jobs we submitted recently ran correctly at first, but didn't end normally. The jobs kept using cpu resources but were not doing any additional useful processing. The firs one abended when the cpu time limit was hit; we canceled the second one. The jobs have only two simple steps, a query to a development DB2 table and a sort of the result set.
Are you running these jobs in batch?
What can you see in the log file?
If yo have trouble to see in what step you jobs is halting, try use the -logparm "write=immediate" system option, and potentially -altlog.
Since you are querying DB2, there might be a log there to whether your queries have been committed or not.
/Linus
Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.