Hello,
I am new to the SAS community and I currently have a surprising problem …
When I run the program (.sas file) manually, the output tables (.sas7bdat) weigh :
When the program (.sas file) is started automatically with a batch (ControlM), the output tables (.sas7bdat) weigh :
I ran the tests twice and I get the same results
How is it possible ? Would there be a compression option to enable on the server ?
I need help from experts because I am a bit lost …
Marie-Sophie
First of all, I'm not a friend of using the global compress option, as datasets consisting solely or mainly of numeric data do not profit from compression; instead, the physical file size is often increased.
So I advise you look out for the location where the compress option is set for your interactive process and remove it. Instead use the individual option on datasets when they are created, then inspect the log if compressing makes sense (considerable reduction of phyiscal file size), and remove the compress=yes option if the effect is negligible or counter-productive.
Code written like that will then also compress in batch mode where compression is desired.
Also see Maxim 31, especially the last sentence.
Difficult to help without knowing what happens in the program. The difference could be caused by different config-files. Maybe the compress-option is active in batch, but not in scheduled mode.
I just read the logs of the two program exécutions.
The .sas7bat files are compressed when the program is started manually.
here is the log of manual execution and the log of the batch execution.
Data set is compressed when the program is started manually.
Is there an option to compress the data set when the program is started with a batch ?
Thanks for your help,
First of all, I'm not a friend of using the global compress option, as datasets consisting solely or mainly of numeric data do not profit from compression; instead, the physical file size is often increased.
So I advise you look out for the location where the compress option is set for your interactive process and remove it. Instead use the individual option on datasets when they are created, then inspect the log if compressing makes sense (considerable reduction of phyiscal file size), and remove the compress=yes option if the effect is negligible or counter-productive.
Code written like that will then also compress in batch mode where compression is desired.
Also see Maxim 31, especially the last sentence.
Files are stored as changing electrons, so their weight should be negligible 😉
Maxim 2: Read the log. Comparing the log step-by-step will give you a clue. If not, post the logs here; if they're too big to insert via {i}, attach them to the post as .txt files.
Don't miss out on SAS Innovate - Register now for the FREE Livestream!
Can't make it to Vegas? No problem! Watch our general sessions LIVE or on-demand starting April 17th. Hear from SAS execs, best-selling author Adam Grant, Hot Ones host Sean Evans, top tech journalist Kara Swisher, AI expert Cassie Kozyrkov, and the mind-blowing dance crew iLuminate! Plus, get access to over 20 breakout sessions.
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.