cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Kastchei
Saturday
  • 135 Posts
  • 73 Likes Given
  • 2 Solutions
  • 25 Likes Received

Re: Index consuming massive disk space to build

by Pyrite | Level 9 in SAS Programming
Saturday
Saturday
I found out the issue, which I'm embarrassed to admit. In my test code I only had one index being created, but in my real code, I had added a second index, and it was that second index that was taking eons to create. 🤭🤷🏼‍♂️🤦🏼‍♂️ Turns out it was faster to sort by that new index and then index on it than trying to index it unsorted (and the first index was still fast, I think, because it's a much more selective index). Thank you for your time and thoughts! ... View more

Re: Index consuming massive disk space to build

by Pyrite | Level 9 in SAS Programming
3 weeks ago
3 weeks ago
Howdy! Yes, my dataset is compressed, decreasing the size by about 98%. So maybe that's the problem. However, my utility file had nothing in it 🤔 but maybe I was looking at an old utility folder. I do see it now. However, here's another interesting clue. I created my second dataset without any indexes. Creating the index with proc datasets or SQL create index both worked in about 1.5 minutes. When I do another data step just to add the index (e.g. data a (index ...); set a; run;), it also produces the index just fine, just taking a bit longer to do so, but not eating away any excess disk space. It seems to be only when I create the index at the same time of making the dataset that it starts using tons of disk space and never finishes. Of course, my solution is just to make the index afterwards, but I am curious why that's happening. ... View more

Index consuming massive disk space to build

by Pyrite | Level 9 in SAS Programming
3 weeks ago
3 weeks ago
Hello! I have a 5 GB dataset with an index that's about 500 MB. I'm doing some fairly minor data step modifications and saving out as a new dataset with the same index. No rows are added or dropped, but a few variables are dropped. The creation of this second dataset is eating through 85 GB of disk space to create the index. That's 170x the size of the index once created. The input dataset took nearly no disk space to create basically the same index. What's more perplexing is that I have no clue where this is happening. I look at the Work library during this, and there's nothing remotely that huge accumulating. I even searched me entire HD for gigantic files (> 4 GB) and there's nothing that huge on the entire disk. What's going on and how can I stop SAS from eating up so much disk space? ... View more

Graph DPI forcing large dimensions

by Pyrite | Level 9 in Graphics Programming
‎04-01-2025 10:47 AM
‎04-01-2025 10:47 AM
Howdy!   I have to create a 1200 DPI TIFF graph for a colleague for a journal submission.  The graph is very simple, but the file size is huge (> 100 MB).  When I view the properties of the TIFF, it is indeed 1200 DPI.  It is also uncompressed.  Is there a way for SAS to produce a compressed TIFF file?  That might make the file size more manageable.    I can zip it up really well, so no worries if there's not a way.   ods html close; ods listing style = axis_wall image_DPI = 1200; ods graphics / reset width = 6.5in height = 4in scale = off noBorder outputFMT = TIFF; %let xAxis = grid /*type = log*/ label = "Relative Risk with 95% Confidence Limits" labelAttrs = (family = "Calibri" size = 11pt) values = (/*0.4 0.5 0.6 */0.7 to 1.8 by 0.1/* 2.5*/) valueAttrs = (family = "Calibri" size = 11pt) min = 0.4 max = 2.5 offsetMin = 0.03 offsetMax = 0.03; proc sGPlot data = a dAttrMap = GraphAttrMap; refline 1 / axis = x; scatter y = group x = PE / xErrorLower = LL xErrorUpper = UL group = noise attrId = Noise errorBarAttrs = (pattern = longDash thickness = 2); xAxis grid /*type = log*/ label = "Relative Risk with 95% Confidence Limits" labelAttrs = (family = "Calibri" size = 11pt) values = (/*0.4 0.5 0.6 */0.7 to 1.8 by 0.1/* 2.5*/) valueAttrs = (family = "Calibri" size = 11pt) min = 0.4 max = 2.5 offsetMin = 0.03 offsetMax = 0.03; yAxis grid discreteOrder = data reverse display = (noLabel) labelAttrs = (family = "Calibri" size = 11pt) valueAttrs = (family = "Calibri" size = 11pt) offsetMin = 0.1 offsetMax = 0.1 ; keyLegend / titleAttrs = (family = "Calibri" size = 11pt) valueAttrs = (family = "Calibri" size = 11pt); run; ... View more

Re: Presorted not working with NoDupRec

by Pyrite | Level 9 in SAS Programming
‎03-27-2025 03:21 PM
‎03-27-2025 03:21 PM
Thank you! I had overlooked this in the documentation. That is unfortunate. I figured if told it was sorted, it would just do the deduplication part. As it stands, it takes as long to deduplicate with presorted as it did to sort the dataset in the first place. I guess deduplication is more costly than I figured it would be. I completely overlooked the first. data step route. I bet it is faster. I will try! (Just FYI, DISTINCT in SQL couldn't complete, because the sort there took too many resources.) ... View more

Re: Presorted not working with NoDupRec

by Pyrite | Level 9 in SAS Programming
‎03-27-2025 09:49 AM
‎03-27-2025 09:49 AM
The same happens with NoDupKey.  I guess the deduplicating process must not properly verify the presorted order. ... View more

Re: Presorted not working with NoDupRec

by Pyrite | Level 9 in SAS Programming
‎03-27-2025 09:47 AM
‎03-27-2025 09:47 AM
Sadly, the issue persists with NoDupKey, too. ... View more

Presorted not working with NoDupRec

by Pyrite | Level 9 in SAS Programming
‎03-26-2025 10:27 PM
‎03-26-2025 10:27 PM
Howdy!   I am trying to use the PRESORTED option of PROC SORT to avoid multiple, very lengthy (~10 minutes) sorts.  However, I am finding that SAS sometimes does not accept that a sorted dataset is truly sorted when also using NoDupRec.   My dataset, labs, I have already sorted by all variables.  When I sort it with no options, SAS tells me it's already sorted.  When I add PRESORTED, it tells me it's already sorted.  But when I add PRESORTED and NoDupRec, it tells me the data is not sorted.  However, the meta data does show the data sorted (of course).  Does anyone know what's going on? 1125 proc sort data = labs; 1126 by _all_; 1127 run; NOTE: Input data set is already sorted, no sorting done. NOTE: PROCEDURE SORT used (Total process time): real time 0.00 seconds user cpu time 0.00 seconds system cpu time 0.00 seconds memory 1456.12k OS Memory 26644.00k Timestamp 03/26/2025 10:21:41 PM Step Count 50 Switch Count 0 1128 proc sort data = labs presorted; 1129 by _all_; 1130 run; NOTE: Input data set is already sorted, no sorting done. NOTE: PROCEDURE SORT used (Total process time): real time 0.00 seconds user cpu time 0.00 seconds system cpu time 0.01 seconds memory 1456.12k OS Memory 26644.00k Timestamp 03/26/2025 10:21:41 PM Step Count 51 Switch Count 0 1131 proc sort data = labs presorted noDupRec; 1132 by _all_; 1133 run; NOTE: Input data set is not in sorted order. When I tried a super simple example, it works fine. 1143 proc sort data = sasHelp.class out = class; 1144 by _all_; 1145 run; NOTE: There were 19 observations read from the data set SASHELP.CLASS. NOTE: SAS sort was used. NOTE: The data set WORK.CLASS has 19 observations and 5 variables. NOTE: Compressing data set WORK.CLASS increased size by 100.00 percent. Compressed is 2 pages; un-compressed would require 1 pages. NOTE: PROCEDURE SORT used (Total process time): real time 0.01 seconds user cpu time 0.00 seconds system cpu time 0.01 seconds memory 1213.43k OS Memory 26636.00k Timestamp 03/26/2025 10:23:46 PM Step Count 56 Switch Count 0 1146 proc sort data = class presorted; 1147 by _all_; 1148 run; NOTE: Input data set is already sorted, no sorting done. NOTE: PROCEDURE SORT used (Total process time): real time 0.00 seconds user cpu time 0.00 seconds system cpu time 0.00 seconds memory 328.28k OS Memory 25860.00k Timestamp 03/26/2025 10:23:46 PM Step Count 57 Switch Count 0 1149 proc sort data = class presorted noDupRec; 1150 by _all_; 1151 run; NOTE: Sort order of input data set has been verified. NOTE: There were 19 observations read from the data set WORK.CLASS. NOTE: Input data set is already sorted, no sorting done. NOTE: PROCEDURE SORT used (Total process time): real time 0.00 seconds user cpu time 0.00 seconds system cpu time 0.00 seconds memory 328.28k OS Memory 25860.00k Timestamp 03/26/2025 10:23:46 PM Step Count 58 Switch Count 0 Thanks, Michael   ... View more

Re: SGPLOT producing wrong font sizes

by Pyrite | Level 9 in Graphics Programming
‎05-14-2024 11:46 AM
‎05-14-2024 11:46 AM
@DanH_sas wrote: Just to make sure this is an "apples-to-apples" comparison, can you generate the output using the WORD destination and set the OUTPUTFMT on the ODS GRAPHICS statement to be SVG? The default DPI for PDF output is 150dpi, whereas WORD is using either 96 or 100dpi. That might be causing variation. Hi Dan.  I tried with the Word destination; however, I got the following warnings.   WARNING: The ODS WORD destination is preproduction in this release. WARNING: Word destination does not support SVG images. Using the default static format. The same difference in font size occurs between gTitle and noGTitle.  That's seen in [test side-by-side Word destination.docx].  Is there another outputFmt you would suggest to try rather than the default static format?   Edit: I tried EMF, and that seems to have fixed the issue.  Now, the comparison looks more or less the same size, just with different smoothing.  That's the [test side-by-side Word EMF.docx] attachment. ... View more

Re: SGPLOT producing wrong font sizes

by Pyrite | Level 9 in Graphics Programming
‎05-10-2024 02:42 PM
‎05-10-2024 02:42 PM
@ballardw wrote: Please describe the tool you are using to determine the font sizes. Not saying you are wrong but the limited tools I have for examining the created document show other values than you get though still not the specified. I copied formatted text for Title 1 and pasted into a Word document which let me see the font and size of 12.5 for example. And font for the X axis labels isn't Arial.   You may need the ODS GRAPHICS/ noscale ; option. Maybe. Supposedly the scaling only changes when you set different Width and/or Height options but since you are seeing some different results for title and footnote text it may be worth trying. I did the same as you.  I copied the text from the PDF to Word which gave the font point sizes I mentioned.  Interesting that you aren't getting the same ones!  I also see that the labels for the axes (both X and Y) are not Arial but Albany AMT.  (Although on my machine those two fonts look identical.)   @Jay54 wrote: Try using ods graphics on / scale=off; See last paragraph here: https://documentation.sas.com/doc/en/vdmmlcdc/8.1/grstatproc/n0yadqm4wsfapgn1hzekfvu1ex0g.htm  Like you both suggest, I tried noScale.  Same problem.   @Cynthia_sas wrote: Hi, My understanding is that the Microsoft name for the Arial font is not the correct way to specify the font for the PDF location. When I need to specify Arial or an Arial-like font for a PDF file, I always use Arial Unicode MS or Albany AMT or Helvetica with PDF. For more information about Arial and PDF, read the article "The Scourge of Arial" https://www.marksimonson.com/notebook/view/the-scourge-of-arial . Cynthia At Cynthia's suggestion, I switched font faces.  I changed to HelveticaNeueforSAS and to Albany AMT.  The font face does change, but the same size problems persist.  They are consistent at least, so 12pt upscales to 13pt with all three fonts: Arial, HelveticaNeueforSAS, and Albany AMT.  I think we're narrowing the issue down to an SGPlot rendering issue.  Perhaps there is some scaling happening despite the noScale option? ... View more

SGPLOT producing wrong font sizes

by Pyrite | Level 9 in Graphics Programming
‎05-10-2024 11:53 AM
‎05-10-2024 11:53 AM
Howdy!   If I specify a font size in SGPLOT, SAS does not seem to actually produce that font size in ODS PDF.  It seems to produce some larger font size.  Here's example code.   ods pdf file = "M:\test.pdf"; ods graphics on / reset; title1 height = 12pt font = 'Arial' 'Title 1'; title2 height = 11pt font = 'Arial' 'Title 2'; title3 height = 10pt font = 'Arial' bold 'Title 3'; footnote1 height = 9pt font = 'Arial' 'Footnote 1'; footnote3 height = 8pt font = 'Arial' 'Footnote 2'; proc sgplot data = sasHelp.class; series x = name y = age; xAxis valueAttrs = (family = 'Arial' size = 9.5pt); run; proc sgplot data = sasHelp.class; series x = name y = age; xAxis valueAttrs = (family = 'Arial' size = 10pt); run; proc sgplot data = sasHelp.class; series x = name y = age; xAxis valueAttrs = (family = 'Arial' size = 10.5pt); run; proc sgplot data = sasHelp.class; series x = name y = age; xAxis valueAttrs = (family = 'Arial' size = 11pt); run; proc sgplot data = sasHelp.class; series x = name y = age; xAxis valueAttrs = (family = 'Arial' size = 11.5pt); run; proc sgplot data = sasHelp.class; series x = name y = age; xAxis valueAttrs = (family = 'Arial' size = 12pt); run; ods pdf close; Title1 comes out as 13 pt. Title2 as 11.5 pt. Title3 as 11 pt. Footnote1 as 9.5 pt. Footnote2 as 9 pt. The x-axis tick values come out as 9.5, 11, 11, 11.5, 11.5, and 13 pt. respectively.   If I add  noGTitle and  noGFootnote  to the ODS PDF statement, then the font sizes for the titles and footnotes are correct.  It seems the problem is with the graphic procedure itself.   I checked the font sizes by copying the text from the PDF and pasting into Word.  I am fairly certain the same happens with ODS RTF; I can't paste the text into Word, but eyeballing it, it looks the same.  Attached are the PDF and RTF outputs each way, plus a screenshot of the side-by-side comparison of the two RTF files showing that the font without noGTitle definitely is bigger than the font with noGTitle.   Does anyone else also get this?  I tested on a SAS session with no other options, custom configuations, etc. but maybe there's still something set on my machine that is messing it up.   Best regards, Michael       ... View more

Stop log from clearing

by Pyrite | Level 9 in SAS Enterprise Guide
‎10-25-2023 03:58 PM
‎10-25-2023 03:58 PM
Howdy, SASers,   My work has moved from SAS code into EG.  However, each time I run a section of code, the log is first cleared.  Thus, the log from any previous sections of the code submitted are lost.  For example, I'll run lines 1-100 and then check output.  I'll then run lines 101-200, and check output again.  At this point, the log only shows lines 101-200, and not everything from 1-200.  Assuming my program has 2000 lines, by the end, I might have a log that only shows the last 10 lines.   Is there any setting to make the log persist when running line-by-line, so that every SAS code that was submitted is shown along with associated notes, warnings, and errors?  Essentially, I want the log to work like it does in SAS.   Thanks! Michael ... View more

Warning with proc FREQ and list outcum options

by Pyrite | Level 9 in SAS Procedures
‎10-13-2023 03:24 PM
‎10-13-2023 03:24 PM
proc freq data = sasHelp.class;     tables Sex*Age / list out = ___temp outCum; run; WARNING: The OUTCUM option is available only for one-way and LIST tables. Should this warning say WARNING: The OUTCUM option is available only for one-way tables. or have I misunderstood the list option?   The output dataset does not have the cumulative variables, although the ODS output does.  The same happens on colleagues' machines.   SAS 9.4 TS Level 1M6 X64_10PRO platform Windows Version 1.0.19041 ... View more

Re: Reset Windows file associations from Enterprise Guide back to base...

by Pyrite | Level 9 in SAS Enterprise Guide
‎07-19-2023 10:50 AM
1 Like
‎07-19-2023 10:50 AM
1 Like
Thank you!!  The registry edit program at the bottom worked for me. ... View more

Reset Windows file associations from Enterprise Guide back to base SAS...

by Pyrite | Level 9 in SAS Enterprise Guide
‎07-18-2023 01:04 PM
‎07-18-2023 01:04 PM
Hello!   IT just updated my Enterprise Guide, and this commandeered all my file type associations in Windows.  For example, if I double-click on class.sas7bdat from Windows Explorer, it opens in Enterprise Guide, and I want it to open in base SAS 9.4.   Windows 10 Enterprise Version 21H2 SAS for Windows SAS 9.4 TS Level 1M6 X64_10Pro platform   I tried right-clicking and selecting "Open with..." and then navigating to C:\Program Files\SASHome\SASFoundation\9.4 and selecting sas.exe.  This does not work.  SAS starts to open with the splash screen, but then it disappears and a log file is created in the folder with the dataset.  The log is attached and pasted below as well.  Also, the icon on the file no longer looks like a little database, but instead is the blue SAS shortcut icon.   In the past, when I've double-checked on a SAS dataset, it would open SAS first, if needed, then assign a library like TMP1, TMP2, TMP3, etc. for the Windows folder, and then open the dataset from that library.  I would like to get that functionality back.   Thanks!   Here's that log that was created, called class.sas7bdat.log (I had to append .txt to the attachment to get the website to upload it).   1 The SAS System 12:58 Tuesday, July 18, 2023 NOTE: Unable to open SASUSER.REGSTRY. WORK.REGSTRY will be opened instead. NOTE: All registry changes will be lost at the end of the session. WARNING: Unable to copy SASUSER registry to WORK registry. Because of this, you will not see registry customizations during this session. NOTE: Unable to open SASUSER.PROFILE. WORK.PROFILE will be opened instead. NOTE: All profile changes will be lost at the end of the session. NOTE: Copyright (c) 2016 by SAS Institute Inc., Cary, NC, USA. NOTE: SAS (r) Proprietary Software 9.4 (TS1M6) Licensed to MOUNT SINAI SCHOOL OF MEDICINE - SFA T&R, Site 70100937. NOTE: This session is executing on the X64_10PRO platform. NOTE: Analytical products: SAS/STAT 15.1 SAS/ETS 15.1 SAS/OR 15.1 SAS/IML 15.1 SAS/QC 15.1 NOTE: Additional host information: X64_10PRO WIN 10.0.19041 Workstation NOTE: SAS initialization used: real time 1.02 seconds cpu time 0.31 seconds WARNING: Truncated record. WARNING: A line of input contains one or more null (hexadecimal 00) characters, which might cause the SAS System to ignore part of the line. The line, with null characters printed as question marks, is: 1 Âê`³Ͻ’ Ç1Œ"" 332 "" 3323#3   SAS __ 180 1 ! FILECLASS DATA 1 ! Ñ"«^جÛAÑ"«^جÛA ”ÑÀ ”ÑÀ    9.0401M6X64_SR12R2 1 ! Ñ"«^lÄ;lÄ;lÄ; 1 ! 8Žp³ Ñ"«^جÛA 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 2 The SAS System 12:58 Tuesday, July 18, 2023 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 3 The SAS System 12:58 Tuesday, July 18, 2023 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 4 The SAS System 12:58 Tuesday, July 18, 2023 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 5 The SAS System 12:58 Tuesday, July 18, 2023 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 6 The SAS System 12:58 Tuesday, July 18, 2023 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 7 The SAS System 12:58 Tuesday, July 18, 2023 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 8 The SAS System 12:58 Tuesday, July 18, 2023 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! ERROR 180-322: Statement is not valid or it is used out of proper order. 217: LINE and COLUMN cannot be determined. NOTE: NOSPOOL is on. Rerunning with OPTION SPOOL might allow recovery of the LINE and COLUMN where the error has occurred. ERROR 217-322: Invalid statement due to first character being unprintable (hexadecimal representation: 9D). 217: LINE and COLUMN cannot be determined. NOTE: NOSPOOL is on. Rerunning with OPTION SPOOL might allow recovery of the LINE and COLUMN where the error has occurred. ERROR 217-322: Invalid statement due to first character being unprintable (hexadecimal representation: 9D). 180: LINE and COLUMN cannot be determined. NOTE: NOSPOOL is on. Rerunning with OPTION SPOOL might allow recovery of the LINE and COLUMN where the error has occurred. ERROR 180-322: Statement is not valid or it is used out of proper order. ERROR: Errors printed on pages 1,8. NOTE: SAS Institute Inc., SAS Campus Drive, Cary, NC USA 27513-2414 NOTE: The SAS System used: real time 1.02 seconds cpu time 0.31 seconds   ... View more
Contact Me
Online Status
Offline
Date Last Visited
Saturday
Group Hubs for Kastchei
View All
Likes given to
Likes from
Quick links