Sas invalid file error

Search instead for. Did you mean:. All forum topics Previous Next. Go to Solution. Posted PM views. Was importing a comma-delimited csv file with 12, records and got the following log message.

Further errors of this type will not be printed. The minimum record length was The maximum record length was Examine log. Accepted Solutions. Re: proc import - unsuccessful. Posted PM views In reply to mehong I'm going to highlight a piece of the log for you to illustrate what SAS is trying to tell you. Hope that helps with your debugging. The syntax for the following program is absolutely correct, except for the missing semicolon on the comment:. However, SAS flags them as errors because it fails to read the data statement correctly.

Instead, it reads this statement as part of the comment. Because the first semicolon it encounters is after the word auto2. Consequently the two correct statements are now errors. Sometimes SAS will correct your spelling mistakes for you by making its best guess at what you meant to do. When this happens, SAS will continue execution and issue a warning explaining the assumption it has made.

Consider for example, the following program:. Note that the word "DATA" is misspelled. If we were to run this program, SAS would correct the spelling and run the program but issue a warning.

Sometimes SAS identifies a spelling error in a note, which does not cause the program to fail. Never assume that a program that has run without errors is correct! Always review the SAS log for notes and warning as well as errors. Sometimes missing values are legitimate.

However, when a variable is missing for every record in the file, there may be a problem with the program, as illustrated above. More often, when your program contains spelling errors, the step will terminate and SAS will issue an error statement or a note underlining the word, or words, it does not recognize.

In this example, there is nothing wrong with the var statement. Adding a semicolon to the proc print solves the problem. However, because we misspelled the dataset name in the set statement, the new dataset contains 0 observations. The error message indicates that no dataset exists with the name uato and the warning message hints that the new dataset may be problematic.

Correcting the spelling solves the problem. Consider the following data step. It runs without an error message. But does it give us the intended result?

Obviously, variable " a " has not been created as desired. This is because that " a " should be created as a character variable using the dollar sign specification for character variables. Instead, since the dollar sign is missing, SAS assumes that " a " is of numeric type, such as an integer or a real number and SAS expects to encounter a numeric value whenever it is ready to read in something for " a ".

Indeed, there are no error messages in red. But each NOTE offers some detailed information. The first NOTE says that the data for variable " a " is invalid in line position Since line is the line corresponding to the statement " cards; ", line corresponds to the first line of data which starts with input john.

So the NOTE is basically saying that "john" is not a valid numeric value. I will paste the code I am using below. Does anyone know what to do about this error? Libname xport expects the name of the transport file , not of a directory where the transport file is stored. View solution in original post. Calling all SAS users! We now have even more FREE knowledge journeys.

Learn more. Choose Your Journey. Learn the difference between classical and Bayesian statistical approaches and see a few PROC examples to perform Bayesian analysis in this video.