@sassy_seb wrote: Yes I used GUESSINGROWS=MAX, and yes we were also discussing what will happen once we get to longer values like AA-10000 like you mentioned.   Do NOT use PRIC IMPORT to read CSV files.  It is fine if you are just exploring.  But if you need re-read the same updated file(s) over and over you should just write your own data step(s) to read the file(s). ... View more

Depending on how "tall" your output is you might consider the system option  Orientation=Landscape; instead of the default portrait. Set this before the ODS RTF statement. You can also use OPTIONS PAPERSIZE= before the ODS RTF output is generated to create a wider/taller logical page to display output. I recommend providing a unit such as IN or CM with the option so you know what to expect.   Options papersize=(10in, 8in); would set the page to 10 inches wide and 8 inches high for example. The option also takes some paper names but that varies by location and system.     ... View more

if there is a way to accomplish this without proc sql, im all ears! Thanks! ... View more

Thanks to all for your responses! ... View more

I think it won't help much since the other(second) DoW-loop takes all data in the end, and SAS will likely caches the data in memory to save some I/Os after the first loop. So even if the first DoW-loop "narrows" data, the second will have to do the "missing" I/O. ... View more

Not Clearly. My target is to do the same thing as INTCK but by using Existing formula.   ... View more

@ShanshanCheng Make it a habit to provide sample data as text - ideally shared via a data step that creates it. Screenshots are not very useful if you're after tested code as solution.   Does below return what you're after?  data have; infile datalines truncover dlm=',' dsd; input subject_id:$5. avalcn:best32. adtm:e8601dt.; format adtm datetime20.; datalines; A,1,2024-04-14T01:36 A,1,2024-04-14T08:36 A,0,2024-04-14T20:05 A,1,2024-04-15T08:38 A,1,2024-04-15T20:03 A,1,2024-04-16T08:50 B,1,2024-05-14T01:36 B,1,2024-05-14T08:36 B,1,2024-05-15T08:38 B,1,2024-05-15T20:03 B,1,2024-05-16T08:50 ; data want(drop=_:); set have nobs=_nobs; by subject_id adtm; if avalcn=0 then return; retain _start_obs; _start_obs=max(_start_obs,_n_+1); do i=_start_obs to _nobs; set have(keep=subject_id avalcn adtm rename=(subject_id=_subject_id avalcn=_avalcn adtm=_adtm)) point=i; if _avalcn=0 or _subject_id ne subject_id then leave; if _adtm-adtm>=24*3600 then do; select_flag=1; _start_obs=i; leave; end; end; run; proc print data=want; run;     ... View more

Based on what I can find on the Internet here it looks like this could work. As @LinusH suggested I would first confirm with SAS before you spend money and effort on this.   Another option would be to store this Parquet file in an environment that can read the Parquet file and that you can access via a SAS Access engine that's licensed at your site. I've worked for example in the past with Parquet files stored under Hadoop that we could access via SAS Access to Hadoop and SAS Access to Impala. ... View more

Do you have values of that variable that contain just a single period? That is what you will get if you used the PUT() function to generate the string and the MISSING option was set to a period. 323 do now=datetime(),.; 324 LBDTC=put(now,e8601dt16.); 325 now2 = input(LBDTC,e8601dt16.); 326 format LBDTC $quote. now: e8601dt16. ; 327 put (_all_) (=); 328 end; 329 run; now=2024-05-16T00:14 LBDTC="2024-05-16T00:14" now2=2024-05-16T00:14 NOTE: Invalid argument to function INPUT at line 325 column 12. now=. LBDTC=" ." now2=. now=. LBDTC=" ." now2=. _ERROR_=1 _N_=1 NOTE: Mathematical operations could not be performed at the following places. The results of the operations have been set to missing values. Each place is given by: (Number of times) at (Line):(Column). 1 at 325:12 NOTE: DATA statement used (Total process time): real time 0.00 seconds cpu time 0.00 seconds   ... View more

You could start with the SAS supplied macro %MDSECGO and then amend the script as you need it. https://go.documentation.sas.com/doc/en/bicdc/9.4/bisecag/n1imi9yor986fsn1o25wd6l582ex.htm    Your need is not that uncommon and if you search a bit you should find something that comes already close to what you need. Here for example.   ... View more

Any scripted approach that worked in with your locally installed SAS version will still work under SAS Viya (Compute). The big difference for you will be that you need to use directory paths that are accessible to your remote SAS server - which is not a local path. You can try a path that you see under Files in SAS Studio.   If you want to export a table that's loaded into CAS then you can still use your existing scripts as long as the source CAS table is accessible via a libname that uses the CAS engine (if you can see the table under SAS Studio then that's what you can use). The process will then first pull the data from CAS to Compute and then create the Excel file on the Compute side.  If you want to directly write a CAS table to Excel you would need to use Proc Casutil or CAS action table.save   Using SAS Studio you can download files from the server to the client side by right clicking on the file to get the download option in the drop down menu.  ... View more

If you haven't done so already then inspect the SAS supplied script importad.sas. This script contains a macro %ldapextrpersons that should give you pointers. Usage Note 40628: Automating the addition of users and groups to a SAS® Metadata Repository   The importad.sas script should be available under: Windows: SAS-installation-directory\SASFoundation\9.4\core\sample\importad.sas Unix: SAS-installation-directory/SASFoundation/9.4/samples/base/importad.sas    ... View more

@Puspita_1 wrote: While executing the macro the error comes like  WARNING: Apparent invocation of macro SYSFUNCT not resolved. ERROR: Required operator not found in expression:  ne 1  ERROR: The macro PERFEND will stop executing. Specially for this macro.PERFEND.the macro is executing multiple times and at last this msg pops up.   That warning most likely means there is a typo of %SYSFUNCT instead of %SYSFUNC somewhere in the code. Fix it.   The %syfunc did not execute and anything relying on the result will not have the expected input. ... View more

Like this? data have; input entry_date :datetime20.; format entry_date datetime20.; datalines; 16FEB2021:07:02:19 28MAR2023:11:52:22 29MAR2023:11:52:22 06JAN2024:17:23:51 21APR2024:23:02:38 ; proc freq data=have; table entry_date ; format entry_date dtmonyy7.; run; ... View more

It's the same with CAS. data work.demo_compute; format dt_1 tod. dt_2 time.; dt_1='30:22:00't ; dt_2='30:22:00't ; run; title 'demo_compute'; proc print data=work.demo_compute; run; data casuser.demo_cas; set work.have; run; title 'demo_cas'; proc print data=casuser.demo_cas; run; proc casutil; alterTable casdata="demo_cas" columns={{name="dt_1" format="time."}} ; quit; title 'demo_cas after changing format'; proc print data=casuser.demo_cas; run;   ... View more