Hello - You best bet is to contact SAS Technical Support in my opinion. Thanks, Udo ... View more

How about chenge from:      infile "c:/file.txt";                   To:      infile "c:/file.txt"   LRECL=80   PAD ; in Program B. Ozawa ... View more

Hi gyambqt, You can plot the time varaible in time series as well as bar chart which I had tried.May be there will be lot of other charts which can be used.. If you are getting issue while plotting the chart, try using "New Calculated Item" and use "Hour" or "Time Part" from "Date and Time Part" in operator section to get your variable in the appropriate format. Thanks, Abhishek ... View more

Hello, Are you located in a different place from where your data server is located? As I understand it, time values in VA are adjusted for DST based on the setting at the data server machine. Sam ... View more

Thanks so much Cynthia! ... View more

data a; length line $500; infile cards dlm="*" truncover; input line $150.; cards; 87         %check (t_table_list=CUTP_TPCR_PIMS 88                 CUTP_CTP_CUTG 89                 CUTP_TPCR_PIM 90                 CUTP_TPCR_PIMQ 91                 CUTP_CTP_CUT 92                 CUTP_CTP_CUT_C 93                 CUTP_CTP_CUTN 94                 CUTP_CTP_CUAD 95                 CUTP_CTP_CUTC 96                 CUTP_TPCR_PIML, 97                l_file_list=, 98                s_file_list= 99         ) ; run; data want; set a; length tables $ 40; if prxmatch('/^\d+\s+%check/',strip(line)) then tables=scan(line,-1,'=');   else if prxmatch('/^\d+\s+\w+\,?$/',strip(line)) then tables=scan(line,-1); run; ... View more

I would not use SAS for this type of parsing of a structured text file. Use awk: it is designed for this. Awk is a small program available on almost all operating systems. It is part of unix. If you do not have awk, use perl, which is bigger and more complex. After you have used awk to reorganise the data, read it into SAS. You should be able to run the awk from SAS, or use a command script to run both. I use this method frequently. ... View more

Hi, Well, you are writing out a file that needs to be interpreted by Excel, so there are limitations.  I don't have time at the moment to really follow up on the question.  My suggestion would be to do your formatting in Excel if its really this fixed and non-standard.  I.e. have an Emtpy Excel file in which you create a small macro to do the formatting.  Then open the two files and run the macro over your output.  You can record actions in Excel to get an idea of the needed VBA code.  The other option, although I haven't used it so not sure how limited it would be, is to look at the new XLSX libname engine in 9.4.  Apparently this can write data out to the XLSX format, so in theory you could create a file with all your formatting etc already present, and then a sheet for raw data, write your raw data out to this sheet, and then have it auto populate in the fomatted tab.  If you have 9.4, maybe investigate this first.  Here is some help: http://www.lexjansen.com/nesug/nesug13/89_Final_Paper.pdf ... View more

I don't actually know if you can delete it. But it doesn't matter, you can just repost it in the right place. My guess is that you will get more feedback in the other forum. cynthia ... View more

I would split into weekly and monthly too. Weekly version: Data A;   Input Report $1. Date:DDMMYY10. Frequency $;   Format Date Date9.;   Datalines; a 01/01/2015 weekly a 15/01/2015 weekly a 22/01/2015 weekly b 03/02/2015 weekly b 10/02/2015 weekly b 17/01/2015 weekly c 10/01/2015 monthly c 12/02/2015 monthly c 10/04/2015 monthly c 12/05/2015 monthly ; Proc Sort Data=A;   By Report Date; Run; Data B (Keep=Report Date: Missing_Report_Date);   Length Report $1. Date 8;   Length Date_Previous 8; Format Date_Previous Date9.;   Length Missing_Report_Date 8; Format Missing_Report_Date Date9.;   If _N_ eq 1 Then Do;     Declare Hash H (Dataset:'A (Where=(Frequency="weekly"))',Multidata:'y',Ordered:'y'); Declare Hiter HI ('H'); H.Definekey('Report','Date'); H.Definedone();   End;   Set A (Where=(Frequency="weekly"));   rc=HI.First();   Do While (not rc);     Date_Previous=Date; Report_Prev=Report;     rc=HI.Next(); Delta=IntCK('week',Date_Previous,Date); If (Report_Prev eq Report) Then Do;    Do i=1 To Delta-1;      Missing_Report_Date=IntNX('week',Date_Previous,i,'same');         Output;    End; End;   End;   Stop; Run; ... View more

I have double checked the dataset, the value "Male" is not in the dataset SAShelp.class. It uses "M". ... View more

No. The length statement is just used so that the hash variables have the right attributes. How the keys are used is defined later in the data step. IE you can load the key variable with a value and use x.find() (x being the name of your hash object) to determine if such a key is in your hast object. Or you could define the hash object key exactly like one of your dataset variables (same name), then you only need to use the find() function because the value is automatically loaded when the dataset record is read. ... View more

You are not wrong as the buffering and memory usage is confusing by the needs of understanding being involved. Form Low to high level: 1- The device (SSD NAS) does buffering for file I/O   (going into transport to be shared by many OS machine) 2- The OS does buffering for file I/O                           (shared processes going to each of them) 3- SAS does buffering for files I/O                              (Within your process memory to be shared) It is becoming more dedicated to your process going thought this steps being able more specific on the needs of logical processing. When coming into SAS only with the datastep there is that PDV being used. Procs like SQL and Report do not have that. Old logical solutions like a sorted join (balance line)  Balance Line Algorithm are  the principal solutions still in use often hided in SQL DBMS systems. They are coming from the era that data is big data compared to the amount of available memory. Well big data is hyping these days and very modern. The trade off of usage in available memory vs the best logical approach is en ever lasting returning question.  1- The NAS/SAN behavior is change by hardware evolution. The total size is increasing more rapidly the every parts speed.     The SSD shift is shifting some techniques that are important. 2- The OS buffering should be isolated having an max. Here is some failures with SAS on Unix:      a/ assuming all everything to be unlimited.      b/ The OS is segregating between loadabables and data but many SAS loadables (eg catalog sas files) are stored as data. 3- Wit SAS you can tune some of the busize and bufno but also using sasfile (load-file into memory) design stream processing (uses hashes)  or formats This is all on internal memory usage, this resource: DIMM - Wikipedia, the free encyclopedia  (near to the processing units) Do not confuse that with the memory as this resource Hard disk drive - Wikipedia, the free encyclopedia  (external far to the processing units) Data step merges are using more storage on the hard disk drive (as are doing SQL DMS-systems) as those are using the same approach and less of the ram-type.  ... View more