You can create multiple files in one pass of the data by using the FILEVAR option on the FILE statment. FILEVAR=variable defines a variable whose change in value causes the FILE statement to close the current output file and open a new one the next time the FILE statement executes. The next PUT statement that executes writes to the new file that is specified as the value of the FILEVAR= variable. For example try this program. %let dataset=sashelp.class ; %let n=10 ; %let prefix=~/temp/split ; proc contents data=&dataset noprint out=contents ; run; proc sql noprint ;   select varnum        , name        , quote(trim(coalesce(label,name)))     into names        , names        , :labels separated by " ',' "   from contents   order by varnum   ; quit; data _null_;   set &dataset ;   _group = 1 + int((_n_-1)/&n) ;   _file = cats("&prefix",_group,'.csv');   file csvfile filevar=_file  dsd lrecl=100000 ;   if mod(_n_,&n)=1 then put &labels ;   put (&names) (:) ; run; ... View more

You are probably getting errors because you did not force the existence of the macro variables. So when you try to use the %IF statements it cannot resolve the macro variable reference.  When this happens SAS just uses the original string including the ampersand so you end up with the string "&VAR1" which is not equal to the string "". A simple way to define the macro variables is to list them in a %LOCAL statement at the top of the macro. Of course for this application you could just use CALL EXECUTE and eliminate the need for the macro variables or even for the macro %LOOP(). if var = 'x' then call execute(cats('%nrstr(%loop1()',name0,')')); else ... ... View more

Using a format won't resolve the precision issue but will only mask it. I believe what the OP needs to do is to find an explanation why there is such a precision issue and then resolve it. One reason can be that the data originates from a database. Numeric precision has been discussed here in these forums multiple times, it's documented and there are also whitepapers around. ... View more

Jason, To expand on Jaap's comment, you can just copy the entire depot to the USB drive.  I've done it from a Windows server depot and it should also work from a Unix server.  Even though the text line endings are different on the two environments, SAS is able to work transparently.  Our campus OIT people have started distribution the Windows version of SAS 9.3 on USB flash drives; it's easier for them to copy and store than the slew of DVDs, and our Windows based depot can be a bit slow for students and faculty working remotely. You may want to download it to both a USB-2 drive and a USB-3 drive.  The installation speed from a USB-2 drive is markedly slower than a USB-3 one. Doc Muhlbaier Duke ... View more

The use of sasguest is confusing. It was introduced to be an anomyous user. serving the server the login webpage. At this web-page you have to make an autentication as no user is yet known. But this page has to be delivered by using a key.   34261 - The SAS Guest User's identity is required in metadata when you invoke the SAS® Information Delivery Portal You will find all of this back in java environment config files (ear/war) to be deployed to the JAVA part webcontainer of the webserver. Changing this is a lot work. So SASguest is no guest user...   When you need to remove guest users as part of security policies this is to be explained. SASguest and sasanonym are still mentioned wit 9.4 SAS(R) 9.4 Intelligence Platform: Migration Guide I am missing a dedicated key (Original sasguest) of the logonmanager (SAS(R) 9.4 Intelligence Platform: Middle-Tier Administration Guide Looks the Original issue has been bypassed in an other way. Did have no chance to validate this.  The details of users and groups is still changing  SAS(R) 9.4 Intelligence Platform: System Administration Guide (Overview of Initial Roles, Groups, and Users).   SAS(R) 9.4 Intelligence Platform: Web Application Administration Guide (Understanding Portal Authorization) all users are needing read and write access at the default ACT. This implies the need for a well designed security (ACT Acccess control templates) in the metadata.  The name "unchallenged access" SAS(R) 9.4 Intelligence Platform: Installation and Configuration Guide SAS(R) 9.4 Intelligence Platform: Web Application Administration Guide (Enabling Unchallenged Portal Access) is used for "guest" access (no login). ... View more

Hey Paul, Thanks for your reply that helps.I am actually back up admin now and i need to learn as fast i can about admin stuff as my current admin will be gone shortly.I attended the Platform essentials class.So I am learning about my environment and need to know how to maintain it.If there are any questions can i send directly to them. Your help will be greatly appreciated ... View more

It depends what you are using. Local Windows is rather basic, I suppose you are not asking that. BI/DI Server comes in with an other approach. It is only the SAS-admin having those rights. Autoexec and Configs (_user versions) are defined at every Appserver-context and possible at ever WS SP etc context. And you have a generic user version. That gives al lot of autoexec and config files for users processes. They can also be related to each other . You are an Eguide users. Than you can have an autoexec projectflow in every Eguide project. Same autoexec functionality as Eguide starts.   Not the classic autoexec file is at your hands but a projectflow named the same. ... View more

Be aware of what noduprecs is doing versus nodupkey, there are separate options. http://www2.sas.com/proceedings/sugi30/037-30.pdf ... View more

Yes try it Jason and then open the pdf to see if the content appear to be viewed on your screen at 25% or 50% or 100% so you can then have an idea of what the future will be on paper but i  ignore which is the paper format for large printed landscape on a laser photocopier in US Andre ps i 10 minutes ends my work day! ... View more

Your proc sql statement has too many errors and ambiguities to show a correct example, but you can use select * and then, on the 2nd from the bottom line, add (keep=) statements after each filename. ... View more

reformat your where clause so all the work happens on the server: where id in (&my_ids); ... View more

You could see if you can get this libname option to work. MULTI_DATASRC_OPT=in_clause http://support.sas.com/documentation/cdl/en/acreldb/65247/HTML/default/viewer.htm#n0tcetvx1zpnayn1r8actrkjrd5o.htm You might need to reformat the query as a join. If the number of values is small enough then you could put them into a macro variable using SQL query. For character variables: select quote(trim(rep)) into :replist separated by ',' from replist ; For numeric variable select rep into :replist separated by ',' from replist; Then you can use the list with an IN operator. select * from db2.tot where rep in (&replist) ; ... View more

SQL is the easiest. To do it with a data step you do not need any macro variables. data want ;   set persons;   do i=1 to nobs;      set drugtests nobs=nobs point=i;      output;   end; run; If you want to keep the people when there are no drug tests you can add. if nobs=0 then output; ... View more

If it's the NOTE that's bothering you, just ignore it. It is VERY rare to actually want a cartesian join, and I can assure you from years of experience that it's fairly common to code one by accident, so SAS just warns you, in case it's not what you want. The code works fine, and produces the result you want, and there's no better way to do it. Tom ... View more