"we know that the forks don't work since we don't see any entries in target table" I'd analyze the SAS Log. May be search for the locations where Signon and Rsubmit get executed. If the Fork doesn't do something different from the Loop here then an unsuccessful Signon or Rsubmit should lead to your job to end with errors. If the Signon/Rsubmit succeed the you should also get somewhere a SAS log with the handle name as part of the log name and you could inspect this log to better understand what's not working. ... View more

If the source have no records, I can't really see the benefit of aborting the job prematurely since the following steps shouldn't require any resource with no observations. Nevertheless, I don't think that there's an out of the box functionality. One of many ways to handle would be to either write user written code to analyse the source table, or insert code to the post process of the extract transformation to check the result set (remember to create table - not view). Check the result and and issue the appropriate abort/abend/endsas statement.   There is a Condition Start/End transformations, but I think they are a bit over the top to use here, I think they make sense if wish to avoid part of the job, not if you wish to terminate immediately. ... View more