It should be flagging the extra ) in the statement and not the date literal. 46 data _null_; 47 if (Incident_Date=.) or (Incident_Date<'01JAN2002'd or Incident_Date>'31DEC2017'd)) - 22 200 ERROR 22-322: Syntax error, expecting one of the following: !, !!, &, *, **, +, -, /, ;, <, <=, <>, =, >, ><, >=, AND, EQ, GE, GT, IN, LE, LT, MAX, MIN, NE, NG, NL, NOT, NOTIN, OR, THEN, ^, ^=, |, ||, ~, ~=. ERROR 200-322: The symbol is not recognized and will be ignored. 48 then Date_Issues='Needs Review'; 49 run; But I was able to get SAS into a state where it did flag the date literal as an error.  825 data _null_; 826 if (Incident_Date=.) or (Incident_Date<'01JAN2002'd or Incident_Date>'31DEC2017'd)) - 390 200 76 ERROR 390-185: Expecting an relational or arithmetic operator. ERROR 200-322: The symbol is not recognized and will be ignored. ERROR 76-322: Syntax error, statement will be ignored. 827 then Date_Issues='Needs Review'; 828 run; Not sure if it was because of some hidden character I copied from your example code or some other previous syntax errors I had made in the same SAS session.   But starting a new SAS session got it back to normal behavior.   ... View more

First let's convert your example listing into an actual dataset so we have something to code against. data have; input section $ (start end) (:datetime.); format start end datetime19.; cards; Aaa 01Jun2025:00:01:10 01Jun2025:00:09:02 Aaa 01Jun2025:00:03:10 01Jun2025:00:12:00 Aaa 01Jun2025:00:10:09 01Jun2025:00:18:08 Bbb 01Jun2025:00:01:02 01Jun2025:00:03:01 Bbb 01Jun2025:00:02:10 01Jun2025:00:09:08 ; Sound like you want to remember the END timestamp from the first of the record in a  block.  You can use a new retained variable to do that. data want; set have; by section start; retain first_end; format first_end datetime19.; if first.section or (start > first_end) then do; group=1; first_end=end; end; else group+1; run; Results: Obs section start end first_end group 1 Aaa 01JUN2025:00:01:10 01JUN2025:00:09:02 01JUN2025:00:09:02 1 2 Aaa 01JUN2025:00:03:10 01JUN2025:00:12:00 01JUN2025:00:09:02 2 3 Aaa 01JUN2025:00:10:09 01JUN2025:00:18:08 01JUN2025:00:18:08 1 4 Bbb 01JUN2025:00:01:02 01JUN2025:00:03:01 01JUN2025:00:03:01 1 5 Bbb 01JUN2025:00:02:10 01JUN2025:00:09:08 01JUN2025:00:03:01 2 ... View more

I know I'm late to the party, but I always like show example of NAMED-INPUT and PARMCARDS   options validvarname=any; filename FT15F001 temp; data test; retain; length dlm $1; infile FT15F001 dlm=dlm stopover; input @; if _infile_ eq ' ' or _infile_ eq: '_' then delete; if find(_infile_,'Patients') then do; dlm = ' '; input site:$5. @'Mags' ('1'n-'5'n)(=); delete; end; else if _infile_ eq: ' ' then do; _infile_ = tranwrd(_infile_,'||','| |'); dlm=' '; input id code:$12. @; dlm='|'; input fts:$2. (dum1 LOS BH pcE pcEP pcLP pcSR dum2 spd X)(:) CONSm:$8. (Heal pc)(:); end; else delete; rename '1'n-'5'n=mag1-mag5; parmcards4; BTP04 Patients Mags 1=23 2=15 3=9 4=6 5=4 ___________________________________________________________________________________ ID Code fts |LOS|BH |pcE |pcEP|pcLP|pcSR|Spd |X| CONSm|Heal|pc| 1 xys H9| | | | | | | || | | | 322|11| 2 v3bwwwr15 m2| | | | 3 | 3 | 3 | || 3 | | 3| 95| 5| 3 qd23 H4| 3 | 2 | 3 | | 1 | 1 | 3 || 21 | | 2 1 3| 228| 3| 4 FRt5 m3| 2 | 3 | 2 | 1 | | | 1 || 23 | | 2 2 1| 142| 3| 5 p002Ft H4| | | | | | | || | | | 361| 9| 6 NNNz13 d1| 1 | 1 | 1 | 2 | 2 | 2 | 2 || 37 | | 3 1 | 48| 1| RRR02 Patients Mags 1=23 2=15 3=9 4=6 5=4 ___________________________________________________________________________________ ID Code fts |LOS|BH |pcE |pcEP|pcLP|pcSR|Spd||X| CONSm|Heal|pc| 1 qus H7| | | | | | | || || | 204|11| 2 w752 m3| | | | 3 | 3 | 3 | || 3 || 3| 95| 5| 3 rsss PT| 3 | 2 | 3 | | 1 | 1 | 3 || 21 || 2 1 3| 228| 3| 4 4562 m3| 2 | 3 | 2 | 1 | | | 1 || 23 || 2 2 1| 142| 3| 5 4862 H4| | | | | | | || || | 361| 9| 6 bVf6RW d1| 1 | 1 | 1 | 2 | 2 | 2 | 2 || 37 || 3 4 | 122| 1| 7 YyPpk8 M3| 2 | 3 | 2 | 1 | 1 | 2 | 3 || 922 || 2 2 3| 100|12| ;;;; run; proc contents varnum; proc print; run; /* Obs site mag1 mag2 mag3 mag4 mag5 id code fts dum1 LOS BH pcE pcEP pcLP pcSR dum2 spd X CONSm Heal pc 1 BTP04 23 15 9 6 4 1 xys H9 . . . . . . . . . . 322 11 2 BTP04 23 15 9 6 4 2 v3bwwwr15 m2 . . . 3 3 3 . . 3 . 3 95 5 3 BTP04 23 15 9 6 4 3 qd23 H4 3 2 3 . 1 1 3 . 21 . 2 1 3 228 3 4 BTP04 23 15 9 6 4 4 FRt5 m3 2 3 2 1 . . 1 . 23 . 2 2 1 142 3 5 BTP04 23 15 9 6 4 5 p002Ft H4 . . . . . . . . . . 361 9 6 BTP04 23 15 9 6 4 6 NNNz13 d1 1 1 1 2 2 2 2 . 37 . 3 1 48 1 7 RRR02 23 15 9 6 4 1 qus H7 . . . . . . . . . . 204 11 8 RRR02 23 15 9 6 4 2 w752 m3 . . . 3 3 3 . . 3 . 3 95 5 9 RRR02 23 15 9 6 4 3 rsss PT 3 2 3 . 1 1 3 . 21 . 2 1 3 228 3 10 RRR02 23 15 9 6 4 4 4562 m3 2 3 2 1 . . 1 . 23 . 2 2 1 142 3 11 RRR02 23 15 9 6 4 5 4862 H4 . . . . . . . . . . 361 9 12 RRR02 23 15 9 6 4 6 bVf6RW d1 1 1 1 2 2 2 2 . 37 . 3 4 122 1 13 RRR02 23 15 9 6 4 7 YyPpk8 M3 2 3 2 1 1 2 3 . 922 . 2 2 3 100 12 */ ... View more

Yes you are right, that will do the same ... View more

Why do you want to store numbers in character variables, which makes it harder to use them? Use numeric variables with a suitable format for display. ... View more

@Ronein wrote: Sometimes there are some problems in data and have duplications. Is it better to select all rows in the query that create sas data set from tera table (not using distinct) and only then use sas proc sort nodupkey? That's what I would do; PROC SORT in SAS is usually the quickest way, unless you can fit the data into memory (hash object). ... View more

Hi Folks!,   I hope this helps!.   This can be done using SAS arrays easily. Below code works fine to find the header of lowest value in  a list.   ... View more

Thank you very much! this was exactly what I needed!!! ... View more

Hello We solved the issue by changing the data structure Thanks everyone The topic can be closed ... View more

Well, the solution would probably work, but you have to be very careful when operating on cp1512 vs utf-8-files.    I like to think that I downgrade to 8.5, but I'm now running EG 8.3 update 6. I won't spend time researching how to get to 8.5. ... View more

Check this: https://support.sas.com/kb/25/006.html https://support.sas.com/kb/69/654.html ... View more

The data step always loops until something stops it.   So I would restate the question as:   How does SAS know when to STOP looping through the data?  What normally stops a data step is when it reads past the end of its inputs.   In your example when the INPUT statement finds there are no more lines to read from Pumpkin.dat.   In the case of a data step that reads in SAS datasets (with SET or MERGE statement for example) it normally stops when the SET or MERGE finds no more observations to read.   Other ways to stop a data step are :  the STOP statement.  a step that has no inputs knows it does not need to loop. A step that does have inputs but because of conditional logic fails to read from any of them in a pass through the implied loop will write a note and stop.   ... View more

It is hard to trouble shoot DI jobs without access to the DI job itself. But it seems you haven't gone through the whole log yourself? If a job work sometimes, consider it not to function. You might have a libnme assignment too late in the code, and the second time it works, but not the first. But, check all the errors in the log and try to fix them one by one.   ERROR: Libref RPTKDC19 is not assigned. ERROR: SQL View WORK.W1MN90FN could not be processed because at least one of the data sets, or views, referenced directly (or indirectly) by it could not be located, or opened successfully. How is this libname (not) assigned, perhaps it's defined as pre-assigned by external configuration, and now this is not done?   LIBNAME report ORACLE PATH=REPOR SCHEMA=tbaadm AUTHDOMAIN="tes" ; %rcSet(&syslibrc); proc _____ 1 61 The SAS System 13:09 Friday, July 18, 2025 3278 ! sql NOPRINT; select count(1) ods_land.ERROR_TEST; %rcSet(&sqlrc); run; ERROR: Specified AuthenticationDomain not found in foundation repository. Misspelling? Or are you running the job in another environment where "tes" authdomain doesn't exist? ... View more