Hi Thomas You're very right that there is no forum for DI. And it's even worse because with DI problems one would often have to add a screen shot. As for your question: It sounds a bit strange to me that your job doesn't pick up the data. Because there the metadata have no more influence (they are used to generate the SAS code which is executed). Did you have a look at the generated SAS code? May be something with the mapping is not o.k. Did you propagate/remap your objects? It must be something like that. Have a look at your code - and the log to see where you "loose" the data. HTH Patrick ... View more

Hi zouclay To have it precise I assume you would have to use SAS/Graph with the Annotate facility and Proc Ganno. With the Annotate facility you can define the coordinate system you need and place you letters as precise as you want. The output is a picture. But: Unless you're familiar with SAS/Graph and Annotate it will cost you quite a bit of work to reach your goal. Another way could be to forget about being that precise and recreating the past: You could just print your output using a font like courier with an appropriate size. This would only look close to how it had been - but much easier to implement. You can always use a datastep with put statements to have your output in the columns and lines you want to. If your challenge is about printing labels and the like then have a look a Proc Forms: http://support.sas.com/documentation/onlinedoc/base/91/forms.pdf HTH Patrick ... View more

HTH Patrick data _null_; RId = prxparse('s/(.)\1+/$1/io'); text = 'YYYMMDD__YDDDM'; call prxchange(RId, -1, text); put text; run; ... View more

Or just use dcreate: NewDirectory=dcreate(DirectoryName,'/local/u/abcdef/'); http://support.sas.com/onlinedoc/913/getDoc/en/lrdict.hlp/a002332693.htm ... View more

What you want is a cartesian product. That's easiest done with SQL: Data ONE; infile cards; attrib COUNTRY length=$20 label='Country'; input country; cards; Belgium France Germany ; run; Data TWO; infile cards; attrib STOCK length=$20 label='Stock'; input STOCK; cards; Stock1 Stock2 ; run; Data THREE; infile cards; attrib PRODUCT length=$20 label='Product'; input PRODUCT; cards; Product1 Product2 ; Run; proc sql; select * from THREE,(select * from one ,two) ; quit; ... View more

Hi Well: Even at SAS Tech Support work only humans... I hope you didn't accept the answer and let them close the track! As I understand it you're not talking about closing SAS EG clients on client machines but about closing inactive sessions on the Workspace Server. The following paper gives a good overview of the architecture: http://support.sas.com/rnd/papers/sugi30/ServerSoup30_040505.pdf As much as I know there is no setting "close if idle for ... sec" What would be a solution is a process on OS level (on the machine where the Workspace server runs) looking for inactive SAS processes and then kill them - you should also be able to decide whether it is a session spawned by the SAS object spawner (SAS EG, DI and other clients) or started by some other process (i.e. SAS batch). Depending on how you use the server rebooting once a night (let's say at 4 in the morning) could be an other approach which is easy to implement. HTH Patrick ... View more

Just one more thing: Why duplicate data if there are views? And if there are more SAS tables in the future instead of processing everything "physically" you can just rebuild the view. HTH Patrick /*libname MyLib 'path to your directory';*/ libname MyLib (sasuser); proc sql noprint; select catx('.',libname,memname) into :TblList separated by ' ' from dictionary.members where libname='MYLIB' and memtype='DATA' ; %put The following tables are in the library:; %put &TblList; quit; data work.MyView / view=work.MyView; set &TblList; run; ... View more

Have a look at this thread. It might give you an idea how to query the dictionary table and find vars with a certain pattern. HTH Patrick Ooops... Somehow the link got "lost": http://support.sas.com/forums/thread.jspa?messageID=14275㟃 Message was edited by: Patrick ... View more

Hi Johnny After your clarifications I think what you're looking for is solved within the current Proc Import (it used to be different). Have a look at: http://support.sas.com/onlinedoc/913/getDoc/en/proc.hlp/a000312413.htm especially "Getnames" and "Guessingrows" HTH Patrick ... View more

As I understand it the calculation should only happen if the observations match. To control that "in" can be used. Based on the already given example: data file3; merge file1 (in=MyDS1) file2 (in=MyDS2); by X; /* do the following only if there is a matching record */ if MyDS1 and MyDS2 then Z = Y * 1000; run; In case that Y is missing, Z will be missing as well. If you don't want that then just add a bit more logic (have a look at "ifn" in the SAS OnlineDoc). HTH Patrick ... View more

With an array/do loop you're looping for EACH iteration of the datastep (=for each "line of data", observation). That's something you might want to do if you have a lot of columns. What you describe is getting information out of passing through the data, line by line. That's something SAS is very good at. Find below one possibility to get what you want. I used Proc SQL - but it could also be done with Proc Sort and datasteps. HTH Patrick /* create some test data with some duplicate ID 's */ data have; do i=1 to 1000; id=ceil(ranuni(1)*500); output; end; run; /* count per id and write result to variable IDcount */ proc sql; /* create table want as*/ select l.id, r.IDcount from have l left join (select id, count(id) as IDcount from have group by id) r on l.id=r.id order by id; quit; ... View more

I was searching for some kind of %csv2ds macro - but couldn't find anything. I'm almost sure searching with some more patiance would bring a result. If you want to solve it by yourself then you'll end up in some serious programming. It's not only about getting the names for variables, it's also about getting the type and length - and this means first scanning the first x rows and see what data you've got (proc import has also to do something like that). Once you've got that all you could build a macro variable with the necessary input statement and then just use this macrovar in a dataset, i.e: data readall; input &inputlist; .... But as I said: Creating the value for this macrovar means some programming. Better use proc import and cleanse/recode the variables afterwards. HTH Patrick ... View more

Hi saroj Your request would be a task for a SAS Server with the necessary modules installed (I believe a running object spawner, SAS/Integration Technology). You write: „...and stores it in a client computer folder running on windows..“ I assume this doesn’t mean that the Java application has remote access to your client PC but that it writes its output to a Server directory which is mapped on your PC. A cheap work-around could be: You write a little script which runs in a scheduler on your PC and looks for this output file from the Java application. When the files is there then you invoke the SAS program processing this file (as the script runs on your PC this won’t be a problem). Using the Advanced Schedule Options you can run a task in whatever interval you want and for how long that you want. http://support.microsoft.com/kb/308569 HTH Patrick P.S: Don't forget to implement a mechano that the SAS process runs only once when the file is there (i.e. by renaming the file you're looking for after SAS processed it). ... View more

Single quotes is sure the easiest solution here. I think what Peter_c is talking about is %nrstr(....). This means NoResolveString: The macro processor won't resolve the string - especially characters like '&' and '%' with meaning in SAS macro language - but single quotes have the same effect. HTH Patrick ... View more

Hi babaorumi You might think of a SAS dataset as if it were a Excel spreadsheet. The variable names are the column names (and actually they are not that easy to rename) - an observation (record) is a line in the spreadsheet. A cell contains the value of a distinct variable ( a "column") at a specific point of iterating through the dataset. That's what a datastep mainly does. It iterates through the "lines of the spreadsheet", from top to bottom, one line at a time between the "data" statement and the "run" statement. So what you're asking for - changing the value of a variable (a cell value) - is the most basic thing you can do in SAS. Let's assume the following: you have: data have; /* write ten observations (records) to table have with one column (variable) "myvar" */ do myvar=1 to 10; output; end; run; data recode; set have; if myvar=5 then myvar=999; run; proc print data=myvar; run; HTH Patrick ... View more