If you are referring to a SAS autoexec.sas file that runs you will need to make sure the machine/user you transfer the program to also has this file and/or code.   As far as automating the program user(s) will need access to the system scheduler in order to schedule the program to run weekly.   If you are using SAS Enterprise Guide the below SAS note is a great resource   Tips for scheduling a SAS® Enterprise Guide® project ... View more

It looks like some of the pre-requisites are not installed. I would check through all of the products listed in Deployment Manager for any client tools that may not be installed. Later versions of the SAS Add-in come with their own stand-alone installer which makes it a lot easier, for example 6.1 or 7.1. You could request the latest version from SAS (including EG) as these are compatible with SAS versions back to 9.2. ... View more

Whenever I encounter such an error it's always caused exactly by what the error message states: The file does not exist on the server where you're running your code. As Linux/Unix is case sensitive: Are you sure that all your file names are in upper case? What do you get if you run code like below? filename dirlist pipe 'ls -la /sas_user/xxx/test_base'; data _null_;      infile dirlist;      input;      put _infile_; run; ... View more

You autoexec prompt is one coming from the autoexec flow in Eguide. That one is living interactive with you Eguide project start. Scheduling batch jobs on a server is about organizing your code on the server and have that run on your server. As your seever administrators for support in that. ... View more

That does not have anything to do with numeric vs character variables as the "0" variable should have the number of choices, so it should always look like a number. If you included the %SYMEXIST() function test then perhaps there is an old "0" macro variable hanging around that does not contain a number? Now if you want to treat the values of the macro variables as characters rather than numbers then perhaps you want an %CHARGEN() macro to go with the %NUMGEN() macro  so that the returned list is a quoted list of values that you could use in your where clause?  Perhaps something like:  WHERE AGE IN ("OLD" "YOUNG") %macro numgen(parm); %local i ; %if %bquote(&parm)= %then %put ERROR: &sysmacroname - YOU MUST SPECIFY A VALUE FOR PARM ; %else %if not %symexist(&parm.0) %then &&&PARM ; %else %if %datatyp(&&&parm.0) ne NUMERIC %then %put ERROR: &sysmacroname - Non numeric count - &&&parm.0 ; %else %do i=1 %to &&&parm.0; &&&parm&i %end; %mend numgen; %macro chargen(parm); %local i ; %if %bquote(&parm)= %then %put ERROR: &sysmacroname - YOU MUST SPECIFY A VALUE FOR PARM ; %else %if not %symexist(&parm.0) %then %sysfunc(quote(%qsysfunc(dequote(&&&PARM)))) ; %else %if %datatyp(&&&parm.0) ne NUMERIC %then %put ERROR: &sysmacroname - Non numeric count - &&&parm.0 ; %else %do i=1 %to &&&parm.0; %sysfunc(quote(%qsysfunc(dequote(&&&PARM&i)))) %end; %mend chargen; %let age0=2; %let age=45; %let age1=45; %let age2=50; %put %numgen(age); 45 50 %put %chargen(age); "45" "50" ... View more