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

I have a long program that runs each night in batch mode and last night it encountered an error part way through the program. This is a portion of the log that shows the DATA step that generated the error. The problem is that SAS automatically set OBS=0 after it encountered the error and didn't execute any of the subsequent steps. How can I turn off this behavior so that it continues to execute the rest of the program? I checked the ERRORCHECK SAS system option and it's set to "NORMAL". The program is running on a Windows PC with SAS ver 9.4 TS1M6.

 

Thanks,

Robert Matthews

 

1862 data tabu.fit_pros ;
1863 set fit_pros_190711 ;
1864 run;

ERROR: A lock is not available for TABU.FIT_PROS.DATA.
NOTE: The SAS System stopped processing this step because of errors.
NOTE: Due to ERROR(s) above, SAS set option OBS=0, enabling syntax check mode.
This prevents execution of subsequent data modification statements.
WARNING: The data set TABU.FIT_PROS was only partially opened and will not be saved.
NOTE: DATA statement used (Total process time):
real time 0.10 seconds
cpu time 0.01 seconds

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
Creeback
Fluorite | Level 6

Try:

 

options noerrorbyabend;

View solution in original post

2 REPLIES 2
Creeback
Fluorite | Level 6

Try:

 

options noerrorbyabend;

SAS Innovate 2025: Save the Date

 SAS Innovate 2025 is scheduled for May 6-9 in Orlando, FL. Sign up to be first to learn about the agenda and registration!

Save the date!

Mastering the WHERE Clause in PROC SQL

SAS' Charu Shankar shares her PROC SQL expertise by showing you how to master the WHERE clause using real winter weather data.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 2 replies
  • 1942 views
  • 0 likes
  • 3 in conversation