Please look at this SAS/Communities post: Accessing Azure Databricks from SAS 9.4 ... View more

Hi @em1535,   As far as I see, your DATA step creating dataset ANALYSIS.COUNT works perfectly on survival data with a discrete time scale like year 1, 2, 3, 4, 5 with corresponding variables TSMK_1, ..., TSMK_5 describing the smoking status in each of those time periods. However, you apply this program to data with time measured on a continuous scale with values ranging at least from 0.1314 to 85.8809.   So, the failed attempt of retrieving the smoking status at time 48 from the five-element array TSMK_ raises the question: What are the five time intervals on your continuous scale that the variables TSMK_1, ..., TSMK_5 correspond to? ... View more

@SASJedi  Thanks for the comparision and helping out with the efficient way to update. Indeed modify satatement is the better option. Thanks Mushy ... View more

Thank you @SASJedi      let me go through this.     ... View more

The elements of a fully-qualified table reference in SAS don't correlate to physical folders in the file system. So, if you have write access to the SASUSER library, it's possible to create a subfolder there, you'd need to assign a different libref instead of using three-level notation. If that's what you want, then you could go about it like this (examples were tested using PC SAS): 1. Identify the physical location of the SASUSER library. The PATHNAME function can do that for you: %put NOTE: The SASUSER library is located in %qsysfunc(pathname(sasuser)); In the log: NOTE: The SASUSER library is located in C:\Users\myUserID\Documents\My SAS Files\9.4 &nbsp You can use the DLCREATEDIR option to make SAS create a folder in the file system when assigning a libref, if the folder does not exist:   options dlcreatedir; LIBNAME SUB "%qsysfunc(pathname(sasuser))\mySubFolder"; options nodlcreatedir; From the log: NOTE: Library SUB was created. NOTE: Libref SUB was successfully assigned as follows: Engine: V9 Physical Name: C:\Users\myUserID\Documents\My SAS Files\9.4\mySubFolder Now, data sets written to the SUB library will be stored in the new mySubFolder folder. data sub.have; set work.have; run;   ... View more

@pdick2    You want  all cases for ID's that have sepsislabel always at zero, or that change from zero to one. You earlier said your data has no instance of going from one to zero. If the above are both true, then you simply want all ID's that start with zero,  That's a simple task.   If the data are sorted by PATIENT_ID/Hour, then:   data want (drop=_:); retain _keep ' '; set have; by patient_id ; if first.patient_id=1 then _keep=ifc(sepsislabel=0,'Y','N'); if _keep='Y'; run; If the data within patient_id are sorted by HR, and the patient_id's are grouped, but not sorted, then change the BY statement to: by patient_id notsorted;     Now if the data are sorted by HR, you don't have to re-sort by patient_id/hr.  And it doesn't matter what the order is within each HR value.  So, if sorting by patient_id/hr is expensive, then you can use a hash object:   data want (drop=_:); set have; by patient_id; length _keep $1; if _n_=1 then do; declare hash h(); h.definekey('patient_id'); h.definedata('_keep'); h.definedone(); end; if h.find()^=0 then do; /*If this is first instance for this ID ...*/ if sepsislabel=0 then _keep='Y'; /*Check the initial sepsislabel value */ else _keep='N'; h.add(); /*Put it in the hash object */ end; if _keep='Y'; run; These are untested. ... View more

Se apenas precisas listar rows que contenham um valor de data/hora dentro de 96 horas de uma data especificada, pode usar PROC SQL e a cláusula BETWEEN. Veja: /* Aqui só estou criando ums dados falsos */ data meus_dados; call streaminit(12345); length Instalacao DataDoNoticia 8 Nota $10; DataDoNoticia='15APR2024:00:00:00'dt; format DataDoNoticia E8601DT18.; array palavra [5] $10 _temporary_ ('Ótimo','Bom','Mal','Locura','Péssimo'); DO Instalacao =1 to 10; do I= 1 to rand('integer',2,5); DataDoNoticia+(86400*I); Nota=palavra[rand('integer',1,5)]; output; end; end; drop i; run; title 'Exemplo dos Meus Dados'; proc print data=meus_dados(obs=5); run; Exemplo dos Meus Dados Obs Instalacao DataDoNoticia Nota 1 1 2024-04-16T0:00:00 Péssimo 2 1 2024-04-18T0:00:00 Mal 3 1 2024-04-21T0:00:00 Péssimo 4 1 2024-04-25T0:00:00 Péssimo 5 2 2024-04-26T0:00:00 Locura     /* Aqui começa o trabalho */ %let comeco="25APR2024:00:00:00"dt; %let fim=&comeco+345600; %put %superq(comeco) %superq(fim); title "Instalações com noticias dentro de 96 horas desde %qscan(%superq(comeco),1,%str(%"))"; proc sql; select Instalacao ,min(DataDoNoticia) format=E8601DT18. as PrimeiraData ,count(*) as Conta from meus_dados where DataDoNoticia between &comeco and &fim group by Instalacao ; quit; Instalações com noticias dentro de 96 horas desde 25APR2024:00:00:00 Instalacao PrimeiraData Conta 1 2024-04-25T0:00:00 1 2 2024-04-26T0:00:00 2   ... View more

Thank you. No worries there. I know for certain that there is no SAS on any server that I have access to. ... View more

I suspect that your SAS session encoding does not match the encoding of your Hadoop connection. By default, Hadoop uses UTF-8 encoding. You can check the encoding of your SAS session using PROC OPTIONS: proc options option=encoding; run; If your SAS session is not UTF-8 and you are running PC SAS, go to the start menu, find the SAS group, and look for "SAS 9.4 (Unicode Support)". Try running your code in that configuration. If you are not running a locally installed SAS, you may not have the ability to change the encoding. In that case, consider using a LIBNAME statement to connect to Hadoop with the SUB_CHAR= option, and then using the CONNECT USING statement in your SQL. Example pseudo-code provided here: libname hdp hadoop user='my-user-name' pwd='my-password' server='hive.server.com' sub_char=QUESTIONMARK; proc SQL; connect using hdp; create table work.Temp as SELECT * FROM CONNECTION TO hdp (SQL Passthrough code) ; disconnect from hdp; quit; May the SAS be with you! Mark ... View more

Is there a way to automate/write code for this data pull from onedrive instead of manually clicking through sas to get to the onedrive folder? ... View more

It works. Excellent !. Thank you so much. ... View more

I would suspect any LIbname that points to a single source that may have Excel, Access, CSV and TXT files in it would have issues. You may be getting the warning about invalid variable columns from something other than a CSV file, or a different CSV then you think is causing it.   Since it is your ODBC connection then you should share the ODBC connection settings. As well as an actual log which I still don't see.   @Lost_Gary wrote: the connection in the libname statement is set up through the Windows ODBC connection and path is set up in the ODBC utility. As long as there is the ODBC driver (and the SAS/Access to ODBC license), SAS can then connect using that libname statement . This would include MS Excel, MS Access, SQL and .csv & .txt sources. Your code is intriguing - where in the macro would i set my external path? As I tinker with it, I seem to be receiving a number of errors trying to figure that out.   ... View more