About LinusH

LinusH

Here on SAS Communities you usually get help on how to use SAS, not how to stop using SAS... Highly doubt there exists supported migration tools. Usually it's the new supplier (which you for some hasn't told us - Azure based could pretty much be anything that runs in cloud) that supplies migration tools, so contact them/their community for support.

LinusH

There are a few options you can play with to prevent the log to grow as fast: NOMPRINT NOSYMBOLGEN NOMLOGIC NOSOURCE NOSOURCE2 NONOTES

LinusH · ‎06-26-2026

Yes, the short CPU timings tells us something is going on in SQLS, not SAS.

LinusH · ‎06-25-2026

It seems you try to create a report in a SAS dataset/table, which is not optimal. If you have somewhat structured source data, there are several SAS procedures to create reports, like PRINT and REPORT. You can even use a data step with PUT statements for high degree of customization. Please share a sample of your source data and we could suggest a proper tool to use for your report.

LinusH · ‎06-25-2026

Agree, it seems weird. Don't know what's going on, but adding more logging/tracing might give some hints: Compare real and CPU time, gives a hint whether the extra time is spent in SAS or SQLS. msglevel=i, verifies if the join etc is sent to SQLS You could platy with some of the other SASTRACE options, like ,,,s and ,,t, If you don't get closer to an understanding, open a track to SAS could be an option.

LinusH · ‎06-17-2026

1. Since there's an explicit OUTPUT when last.code, you need to retain the value of firstsnow across observations. All variables are reset for each observation, RETAIN prevents that to happen for selected variable. 2. This set of statements makes sense only to execute when you are at the last observation for your by group /code). 3. In a regular data step, there is an implicit OUTPUT at the end - usually at RUN. When introducing an explicit OUTPUT, there is no implicit OUTPUT any more, and you only write an observation at the OUTPUT statement. In this case when the condition last.code is true.

LinusH · ‎06-11-2026

With some trial and error and AI conversation, I got all lines visible from your example: data HAVE; x = catx( '0A'x , '0000000000', '4445566778','9999999999','9991123456'); run; ods excel file="print.xlsx" options(sheet_name='Test' flow="Tables" row_heights="0,0,0,0,0"); proc print data=HAVE noobs ; var x / style(column)={width=2.5cm vjust=top tagattr="wrap:yes" }; run; ods excel close; But as you can guess, the setting of width= needs to be correlate with the actual length of your strings, which probably will make this hard to use in every day applications....?

LinusH · ‎06-10-2026

As I understand it you could mount it to your Kubernetes cluster, but maybe that's not what you are looking for?

LinusH · ‎06-02-2026

There are probably many ways of doing this, so it may come down to your requirements. How many teams are there that need separate autoexec? First, I don't think you should bypass the existing set up with the central ones. The different option within EG will distribute the logic from the server. This will be question of governance. On the server you could create separate compute contexts (e.g. other SASApp's). This a quite a change and feasible if you don't too many groupings and want other separation between you user groups. Maybe you could have a %include code in your central autoexec (with some kind of logic that pickup users group and select the appropriate .sas file), or %if %then %else sections in your autoexec code.

LinusH · ‎05-27-2026

This looks like some kind of a bug, report it to SAS tech support.

LinusH · ‎05-05-2026

Please provide the query (and log) so we can help analyze it, ideally with using the options in the link from @Tom.

LinusH · ‎04-21-2026

Just to fix the output issue, you could use the of _all_ construct with catx: data _null_; set &Lib..&Mem; length out $1000; out = cats(catx(';', of _all_),';'); file "&outfile" mod lrecl=32767 encoding="utf-8"; put out; run;

LinusH · ‎04-17-2026

It's pretty much in the message, you need to specify on which server your SAS PC Files Server is executing. This information should be documented for your environment.

LinusH · ‎04-17-2026

I don't have the "Bulk Load" tab in my advanced settings, probably because we are using SAS/ACCESS to SQL Server, not ODBC. I'm on 9.4M8 Linux. Not sure what you refer to when you say "advanced option in ODBC set up". Do you mean ODBC Manager (Ican't fins an advanced option here)? I think it should be enough to set it on the libname, the important thing is to generate the BULKLOAD=YES when your LIBNAME statement is being generated.

LinusH · ‎03-27-2026

There are lot of coding challenges on internet. You can use those even if they aren't SAS specific, just use SAS to solve them. One example I've couple of years is "Advent of Code".