This filename out zip 'Batchfile 7.6.zip'; is your problem. You did not use a fully qualified path name, so SAS tries to write to its current working directory, which is usually the place where the script file WorkspaceServer.sh is located, and where you do not have write permission. Use a file name that includes the complete path starting at root (like you did for indir) and pointing to your home directory. You can also use the tilde shortcut for this: filename out zip '~/Batchfile 7.6.zip'; ... View more

Something unbalanced (unbalanced quotes, macro definition without a valid %MEND, ...) has caused your SAS session to become unstable. Start a new session and rerun your code, paying attention to the above. ... View more

One must make such transformations (assignment of formats, extraction of sub-values etc.) when the dataset is prepared for analysis. This is a job for your data engineers. ... View more

Are these variables stored as character or numeric in the underlying dataset? ... View more

You tried to use a library reference (libname) as infile in PROC IMPORT, which cannot work. Either use a worksheet like a SAS dataset in your Excel library, or use the correct physical filename in the DATAFILE= option of the PROC IMPORT statement. ... View more

@sfletc30 wrote: Hey so just a followup question for number 3. So I understand what the code is saying now. If last.Code=1, then do these things (which includes writing to the output table with the OUTPUT statement). And last.Code=1 only exists four times in the dataset. So that explains why the rows went from around 140 to only 4.   But why do I have to explicitly tell SAS this? Why doesn't the implicit OUTPUT statement at the end of the code create the four rows that the explicit one does? Because the implicit OUTPUT writes an observation for every iteration of the DATA step, unless the iteration is cut short by a subsetting IF. And the number of iterations is (in your case) determined by the observations read from the input dataset. ... View more

Please show us an example of your input data (just enough observations to illustrate your case), and the expected result from it. ... View more

My solution would have been shorter: data snowforecast; set winter2015_2016; retain FirstSnow; by Code; if first.Code then FirstSnow=Date; if last.Code; LastSnow=Date; WinterLengthWeeks=intck('week', FirstSnow, LastSnow, 'c'); ProjectedFirstSnow=intnx('year', FirstSnow, 1, 'same'); format FirstSnow LastSnow ProjectedFirstSnow date7.; drop Snow Date; run; The code will read all observations, but keep only the value of the first observation in a group in variable firstsnow. Then, it will only proceed further if the last observation in a group has been read. All following statements (including the implicit OUTPUT at the end of each step iteration) are "jumped over" in all other cases. This particular form of an IF statement is called "Subsetting IF"; if the condition is not met, the next iteration of the DATA step is immediately started. ... View more

Since you know the names of the target variables, a simple DATA step will do it: data have; input customer $ flag $ count; datalines; 12345 COE 5 ; data want; set have; length coe non_coe 8; coe = 0; non_coe = 0; select (flag); when ("COE") coe = count; when ("NON_COE") non_coe = count; otherwise putlog "ERROR: non-expected flag!"; end; drop flag count; run; But do you really want that wide dataset, or is this for reporting purposes? What is your final goal, and what is your initial input data? I ask this to avoid having an XY problem. ... View more

This particular message can mean that SAS is not able to create the WORK library/directory. ... View more

UNIX systems have very nice tools for exactly such mass text change operations, e.g. awk. Just run that on the original source codes of the SQL views. If those source codes are not available, someone fucked up big time (see Maxim 27). ... View more

I just ran this on SAS On Demand, which is also on 9.4M8: proc export data=sashelp.class file="~/class.xls" dbms=xls replace ; run; After downloading the file to my Mac, it opened successfully both in MS Excel and LibreOffice.   So it seems that you either have a problem with your particular SAS installation, or with the data itself. Questions to answer: on which particular platform is your SAS server installed? on which particular desktop do you open your files (Windows/Mac/Linux)? which application is used to open the files (include version/maintenance level)? and finally we need to see your data; post it as a self-contained DATA step with DATALINES, so we can exactly recreate your dataset in our environments ... View more

For installation issues, it's best to get in touch with SAS technical support. ... View more

IF(!) you run this on a UNIX system (e.g. SAS On Demand), then the correct shortcut for your home directory is the tilde (~), not the ampersand (&). ... View more

Post the complete log of your code by copy/pasting it into a code box, from the ODS POWERPOINT statement to the ODS POWERPOINT CLOSE statement. Do not change or omit anything. ... View more