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

Most likely you need to adjust these hard coded increments to reflect the fact that you want to make smaller boxes so they can fit on the page.   %let b_x1 = %eval(&b_x1. + 30); %let b_x2 = %eval(&b_x2. + 30); ... %let b_y1 = %eval(&b_y1-25); %let b_y2 = %eval(&b_y2-25); ... View more

Here’s a polished version of your follow-up message: --- Hi Cynthia, Thanks for your response. I may reach out to SAS Support for further assistance. It seems that SAS Studio version 3.8.2 was released in recent years, so this issue might be version-specific. Best regards, DZ --- Let me know if you want to include any additional technical details. ... View more

You cannot use the same format with two different encodings.  That is because the bytes used to represent the characters differ depending the encoding you are using.  Consider a lower case n with tilde over it.  It is 'F1'x in LATIN1 encoding and 'C3B1'x in UTF-8 encoding. 25 data test; 26 enye = 'F1'x ; 27 put enye= enye $hex2. ; 28 utf8 = kcvt(enye,'latin1','utf-8'); 29 put utf8= $hex4.; 30 run; enye=ñ F1 utf8=C3B1 You will probably want to create two different format CATALOGs.  (They could be in the same LIBRARY if you want, just use different names for the catalogs.) proc format lib=mylib.utf8; value .... Then just change which one you include in your FMTSEARCH system option based on what encoding your current session is using.   Or you could make two different formats and then decide which format to use based on the encoding. proc format ; value latin1f 1='F1'x; value ut8f 1='C3B1'x ; run;   ... View more

Thank you for your reply! @Tom wrote: Adding the format to the PUT statement will allow the data step to make a better guess about how to define MEMNAME.  But that will not solve the issue that MEMNAME has not yet gotten a value at that point in the data step.   The problem is that the PUT statement that uses MEMNAME is BEFORE the SET statement.  So the data step compiler guesses that you wanted MEMNAME as numeric, and then when the first SET statement runs there is a conflict.   For that particular data step the solution would be to make sure the SET statement is before the PUT statement.  Not only will that fix the type conflict it will also mean that MEMNAME actually has a value that can be written by the PUT statement.   You could add another SET statement at the top of the step before the first PUT.  But then the data step would iterate once for each observation in the dataset, writing multiple copies of the data step to the output file.   To fix that you could add a STOP statement to the end of the data step so that it stops after the first iteration.  Or you could add an OBS=1 dataset option to the SET statement. In that case the data step would stop at the top of the second iteration when it tries to read a second observation from an input that only had one observation.  That is how normal data step stop.   Yes, one of the key measures I took to tackle the problem was adding a SET statement after the "data _null_" statement. This informs SAS of where the variable MEMNAME comes from as well as its characteristics like its length and type. I forgot to say that in yesterday's response but that modification is present in the code. In addition, in an attempt to simplify the code conducted today, I found that the format for MEMNAME can actually be removed once the SET statement is added. @Tom wrote: Programming hint:   Note you could also use a FILEREF in the generated code.  In that case the logic to generate the code would not need to change for a different input file. Instead just make sure to define the fileref before running the generated code.   ... * Write data statement and INFILE statement ; set metadata (obs=1); put 'data ' memname '(label=' memlabel :$quote. ');' ' infile csv dsd truncover firstobs=2;' ; ... /*Replace the address of the CSV with a real one */ filename csv 'myfile.csv'; %include code / source2; Thank you for pointing out a way to further simplify the code! Adding yet another FILENAME statement renders a more handy code that can be more easily compiled into a macro. This is very useful. ... View more