topic Re: Saving data to a permanent SAS data set - variables required to be certain lengths in SAS Programming

Saving data to a permanent SAS data set - variables required to be certain lengths

Bluekeys49 — Thu, 09 Jul 2020 19:28:32 GMT

Hi. I am saving some data to a permanent SAS dataset. I can easily do that, but notice when I do a "proc contents," my variable fields lengths are not what I want them to be in the saved dataset. For example, I have a variables called GROUP1, GROUP2, and GROUP3 which have values of 1, 2, or 3. Each variable is showing a character type with a length of 3 in proc contents. I would like it to have length of 1 for each. How and where do I indicate this in my program? I tried the code below and it didn't work. Perhaps my GROUP1 - GROUP3 is incorrect syntax?

* output to SAS perm dataset;
data dat1.tempdata;
length GROUP1 - GROUP3 ($1.);
set TWO ;
run;

Re: Saving data to a permanent SAS data set - variables required to be certain lengths

PaigeMiller — Thu, 09 Jul 2020 19:39:14 GMT

length group1-group3 $1;

Re: Saving data to a permanent SAS data set - variables required to be certain lengths

ballardw — Thu, 09 Jul 2020 20:25:42 GMT

@Bluekeys49 wrote:

Hi. I am saving some data to a permanent SAS dataset. I can easily do that, but notice when I do a "proc contents," my variable fields lengths are not what I want them to be in the saved dataset. For example, I have a variables called GROUP1, GROUP2, and GROUP3 which have values of 1, 2, or 3. Each variable is showing a character type with a length of 3 in proc contents. I would like it to have length of 1 for each. How and where do I indicate this in my program? I tried the code below and it didn't work. Perhaps my GROUP1 - GROUP3 is incorrect syntax?

* output to SAS perm dataset;
data dat1.tempdata;
length GROUP1 - GROUP3 ($1.);
set TWO ;
run;

Such things should be fixed or set as early as practical. If you create these variables then the length should be set then, if you are reading them from an external data source that might be the place.

If these are coming from using Proc Import then perhaps another way to read the data should be investigated as there is NO way to know the properties of any variable as the procedure makes guesses separately for each file read.