I saw this post Re: the MCAR macro. I was trying it but came across the following error and didn't see any discussion on this particular error. Any ideas where to look?   Solved: Little's MCAR macro - Page 2 - SAS Support Communities   NOTE: IML Ready ERROR: (execution) Invalid argument or operand; contains missing values. operation : * at line 619 column 1 operands : mu, Dj mu 1 row 179 cols (numeric) Dj 179 rows 83 cols (numeric) statement : ASSIGN at line 619 column 1 NOTE: Line generated by the invoked macro "MCARTEST". 619 @put (m[i,]) 6.0 _ 180 ERROR 180-322: Statement is not valid or it is used out of proper order.   ... View more

I have a proc append issuing the following notes. I assume none of the notes below would explain why a numeric column would be empty (when the append dataset has it populated)?   What is happening is, the dataset containing the rows to be appended has several numeric columns populated, but when the append executes, those numeric columns in the base dataset are left blank. No warnings or other messages are in the log from the append other than the notes below.   Any ideas on why the numeric columns are blank after the append? Does the large dataset size have something to do with SAS not being able to append? One thought a colleague had was to make the columns character to see if that allows the columns to be populated after the append.   INFO: Engine's fast-append process in use. INFO: 03:26:04 Reading DATA file, updating BASE file INFO: Starting data set size is 1005557 pages INFO: Engine's block-read method cannot be used because: INFO: - The file is compressed INFO: Ending data set size is 1007791 pages, 2234 added. INFO: 00:00:00 Elapsed time INFO: 03:26:04 Finished updating BASE file ... View more

When specifying a format and informat statement on columns in an EMPTY dataset, I'm finding the format and informat don't stick. Is there a way around this issue? I can understand if it's working as designed but am wondering if there is a way to set format and informat on an empty dataset column.   More specifically, the empty dataset is in a "create view" proc sql UNION statement, snippet below. The empty dummy placeholders in the first union select, I believe, is causing the format/informat not to stick? The second union select DOES have data in those columns.   PROC SQL; CREATE VIEW AS SELECT '-' as field1, '-' as field2, 0 as field3, FROM TABLE1 union SELECT  field1, field2, field3   FROM TABLE2 ; --> RESULT: even though field1, field2, and field3 are defined with specific FORMAT and INFORMAT settings in union select #2, those FORMAT and INFORMAT settings don't carry over to the final view. ... View more

I'm researching on how often this kind of definition needs to be done ... (below) Hi, I'm researching views and trying to use them for the first time.  I am wondering if, in each program where I am using the view, I will need a definition like below - or is just a one-time initialization below enough, and then the view name can just be referenced across multiple programs (but not redefining it below each time)?   Because from what I've read, defining it once below means I can then just reference the view name, which will refresh the view automatically in any other program? data lib.vwrefund_detail/view= lib.vwrefund_detail; set lib.dataset1 lib.dataset2; run; ... View more

Hi - I've been trying various approaches to no avail. I have a DATA step that outputs to multiple datasets using an IF statement. The error I keep getting is, ERROR: Rename of temporary member for xxx.xxx failed. (where xxx.xxx is the library.dataset name). I saw a SAS knowledge base article saying to create new datasets instead of updating existing ones in place, but that doesn't seem to be working. Has anyone else come across a solution to this error message? ... View more

Hi - somehow in my code, even though I'm not setting options to compress datasets, the log file says it is such as below. Any ideas how I can turn off this "automatic" compression and instead invoke it at the END of my code?   NOTE: Compressing data set mylib.testdata decreased size by 59.25 percent. Compressed is 5622 pages; un-compressed would require 13796 pages. ... View more

Hi - I feel this is a simple question but wanted to confirm and couldn't seem to find documentation on this:   If I have a pivot table in Excel that uses a SAS dataset as its data source, does the user necessarily need SAS to refresh this pivot table? I was thinking not, but recent testing has made me question my assumption. Maybe SAS is needed for the dataset to be recognized through SAS' OLEDB data source connection used by the pivot table?   Thanks ... View more

I'm trying to open a SAS dataset using the SAS add-in and get the following message. Any ideas? I tried renaming one of the folders to _old (either 9.45 or 9.46), but that didn't work. The path in question per the error is C:\Program Files\SASHome\x86\SASProvidersforOLEDB.   I can refresh existing SAS-connected pivot tables in Excel, using OLEDB 9.45. So I'd like to keep using that, except I cannot open a new dataset into Excel.    ... View more