BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
Babloo
Rhodochrosite | Level 12

I've the post code in DIS Job which calls the .sas file via %INCLUDE Statement. It (post code) is working fine when DIS Job ends with success or warning. However it is not working when the DIS Job Fails and I could see the WARNING as follows. I'm not certain why I'm getting the WARNING only when DIS Job fails.

 

.sas file which was being called in INCLUDE Statement is not taking any value from the final table which was being created from the DIS Job. May I know how to resolve this issue when the DIS Job failes?

 

 

817        /*---- Start of Post-Process Code  ----*/
818        
819        %INCLUDE "/var/sasdata/ifr/SASCode/distudio/metadata_info.sas";
0



WARNING: RUN statement ignored due to previous errors. Submit QUIT; to terminate the procedure.
NOTE: PROCEDURE FORMAT used (Total process time):
      real time           0.02 seconds
      cpu time            0.00 seconds
      
1 ACCEPTED SOLUTION

Accepted Solutions
ErikLund_Jensen
Rhodochrosite | Level 12

Hi @Babloo 

 

This is not tested, but I guess it could be solved by adding  

option NOSYNTAXCHECK ;

as the first line in your includecode.  

View solution in original post

3 REPLIES 3
LinusH
Tourmaline | Level 20

The default behaviour is that no statements are executed in a SAS session when an error occurs.

 

Do you really need to execute your %include program when a job fails?

Please describe your requirement so we may can come up with an alternative approach.

Data never sleeps
Babloo
Rhodochrosite | Level 12
Yes, I really want to execute INCLUDE statements even when the job fails.

Whether I have to place the INCLUDE statement in some other place or can I
wrap up my .sas file which was being called in the INCLUDE statement and
call that macro in some portion of the job?
ErikLund_Jensen
Rhodochrosite | Level 12

Hi @Babloo 

 

This is not tested, but I guess it could be solved by adding  

option NOSYNTAXCHECK ;

as the first line in your includecode.  

SAS Innovate 2025: Call for Content

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!

Submit your idea!

How to connect to databases in SAS Viya

Need to connect to databases in SAS Viya? SAS’ David Ghan shows you two methods – via SAS/ACCESS LIBNAME and SAS Data Connector SASLIBS – in this video.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 3 replies
  • 714 views
  • 0 likes
  • 3 in conversation