DATA Step, Macro, Functions and more

Can help us know why the two LONGJOBs did not finish when SAS appeared to be done running the code in the job?

Reply
Contributor
Posts: 31

Can help us know why the two LONGJOBs did not finish when SAS appeared to be done running the code in the job?

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. 

Super User
Posts: 5,257

Can help us know why the two LONGJOBs did not finish when SAS appeared to be done running the code in the job?

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

Data never sleeps
Ask a Question
Discussion stats
  • 1 reply
  • 127 views
  • 0 likes
  • 2 in conversation