PaigeMiller Tracker

Re: ERROR: All variables in array list must be the same type

PaigeMiller — Wed, 15 Apr 2026 12:05:54 GMT

All this variables (FruitWt, Color, Rind, Button, Wtloss) are numeric variables

It sounds like you are just stating this as a fact, rather than confirming this by running PROC CONTENTS. I have a rule here, when SAS says something is false and the human user says it is true, I believe SAS. (In my experience, SAS is right 99.99% of the time) So please check PROC CONTENTS.

Re: Apply "at least" condition in data step

PaigeMiller — Tue, 07 Apr 2026 11:29:32 GMT

The advice from @ballardw to represent Y and N with numeric values 1 and 0 should not be ignored. This applies to all SAS programming that you do now and in the future. If you are creating output (like a report or table) that you need to show others and Y and N is required in the output, then use a custom format to display 1 as Y and 0 as N.

However, I am still unable to understand the stated logic that takes me from the input data to the desired data. It simply is not clear.

Please try to write it again, in a new post in this thread (instead of correcting the original post) explaining the rules (in detail) you want to follow. As @ballardw would say, we need RULES and not EXAMPLES (although sometimes we need both).

Re: I am sorting my sgplot with cohortn and cohort but only want to display cohort information

PaigeMiller — Thu, 02 Apr 2026 11:45:38 GMT

@dsam wrote:
I tried it, but month which is not numeric variable, order is messed up on x axis.

Important concept: months and any calendar information in SAS data sets should be stored in NUMERIC variables. In fact, let me say that even more strongly: any calendar information in SAS data sets MUST be stored in NUMERIC variables. Character variables will not sort in the desired order for calendar information.

Re: Create a new Calclation based on multiple conditions

PaigeMiller — Wed, 01 Apr 2026 20:52:36 GMT

If I am understanding you properly, you will have to sort the data by the season and by the date of the race. Then you want to use the LAST. construct in SAS to in order to identify the last race of the season. Then it is easy to extract the information you want.

See the documentation here, and the examples will be helpful.

Many people (including me) refuse to, or cannot, download attachments. The proper way to include a data set it to provide working SAS data step code (examples and instructions).

Re: why is my x axis going out of order even though i have it sorted with numeric variable ?

PaigeMiller — Wed, 01 Apr 2026 15:39:32 GMT

@dsam wrote:

my code is below: I have x axis values like in months such as D1 D28 2 3 4 6 12 18 24 36 but for one subject it is plotting month 18 after month 48 even though data is sorted properly by numeric variable.

title 'Percent Predicted FEV1 for Individual Subjects in Four 4D-710 Dose Cohorts';
proc sgplot data= combo;
xaxis grid type= discrete discreteorder= data;
series x = month y= RESTRESN/ group=subjid;
scatter x=month y= RESTRESN/ group= subjid ;
xaxis label= 'Month';
yaxis label= 'ppFEV1 (%)';
by cohort;
run;

When you have multiple XAXIS statements, the second one replaces whatever is specified in the first.

Re: Text Wrap in Enterprise Guide?

PaigeMiller — Wed, 01 Apr 2026 13:28:40 GMT

One solution, of course, is to manually add line breaks when the line gets long and might pass the right edge of the window. I have done this in the SAS application workspace (I don't use Enterprise Guide) for the last 700 years. I don't even think about it any more, its a habit.

Re: Every time I try to make a permanent data set I get a library does not exist message

PaigeMiller — Tue, 31 Mar 2026 18:56:32 GMT

Are you running this in SAS/Studio? If so, SAS/Studio cannot access files or folders on your local computer's hard drives.

You have to create libraries on the server where SAS/Studio is running. You mentioned SAS On Demand, here is how I use the LIBNAME statement

libname mydata "/home/paige.miller3";

data mydata.class;
	set sashelp.class;
run;

Of course, you would have to use a different folder than PAIGE.MILLER3, it has to be a folder the exists in your SAS On Demand.

Re: SAS Studio, SAS Server search/navigation bar

PaigeMiller — Tue, 31 Mar 2026 15:27:00 GMT

Agreeing! Let's do this!

Re: SAS Programming Essentials Lesson 3 Demo: filtering rows using macro varaibles

PaigeMiller — Tue, 31 Mar 2026 15:06:07 GMT

Check your syntax in the WHERE statement carefully. You want to use a macro variable but have left off the & in front of the macro variable name.

Re: SAS Programming 1: Essentials Demo: Filtering Rows Using Macro Variables

PaigeMiller — Mon, 30 Mar 2026 16:01:52 GMT

This is great to hear @ivarenho . So many visitors only want the answer to their programming problem and learn nothing useful so next time they have similar problems. So many visitors to this forum receive the same advice about creating a working program without macro variables first, and they ignore the advice and move on to struggle mightily with macros.

Re: proc pls: center and scale

PaigeMiller — Mon, 30 Mar 2026 12:43:52 GMT

@SASdevAnneMarie wrote:

I thought that proc pls centered and scaled variables by default.

Yes it does. My mistake, VARSCALE is an additional option to help with crossproducts of model variables (if you have any).

This was precisely to compare the PCR and PLS outputs.

Outputs as in measures of fit? Because there's really no point in comparing loadings or scores between PCR and PLS.

Re: proc pls: center and scale

PaigeMiller — Mon, 30 Mar 2026 11:27:55 GMT

I believe you want the VARSCALE option in PROC PLS.

VARSCALE: specifies that continuous model variables be centered and scaled prior to centering and scaling the model effects in which they are involved. The rescaling specified by the VARSCALE option is sometimes more appropriate if the model involves crossproducts between model variables; however, the VARSCALE option still might not produce the model you expect. For more information, see the section Centering and Scaling.

For more advanced centering and scaling methods, use PROC STDIZE.

I always feel uncomfortable when PCR is chosen for METHOD, as this logically (based upon the criterion being optimized) will produce worse fits than METHOD=PLS. Maybe there are valid reasons for using PCR instead of PLS, but in general PCR will not fit as well as PLS.

Re: SAS Programming 1: Essentials Demo: Filtering Rows Using Macro Variables

PaigeMiller — Fri, 27 Mar 2026 11:44:08 GMT

@ivarenho wrote:

The date from June 1980, please correct me if I'm wrong but that has to be in the quotation marks because it's making a calculation?

Certain types of calculations can be done in SAS without quotation marks. It depends on whether or not quotation marks are required to create valid SAS code. In some cases, quotation marks are invalid at that point in the SAS code and will cause SAS to generate errors.

This is why @D_Dunlap said you really should first generate working SAS code without macros variables, and hard-code the values that the macro variable will take — and if it works without quotes, then you don't need to quotes when you use the macro variable. If it doesn't work unless you put the quotes in, then you need the quotes when you use a macro variable. This is why @Tom said "The code that results once the macro processor is finished needs to be actual valid SAS code." So please, do yourself a favor and first create working (emphasis on "working") code without macro variables and hard coded values where the macro variables will go. Then using the macro variables correctly will be a much easier task.

Re: PROC REPORT: How to apply same color to group headers and column headers

PaigeMiller — Thu, 26 Mar 2026 17:03:00 GMT

Perhaps this will work for you

https://communities.sas.com/t5/ODS-and-Base-Reporting/Color-background-of-group-name-in-proc-report/m-p/689395#M24539

Re: how to create a new visit date

PaigeMiller — Thu, 26 Mar 2026 09:03:08 GMT

Just a quick addition to the correct answer from @Ksharp : the RETAIN statement, when used properly, allows you to carry data forward to the next row, and allows it to change when your rules require it to change (when PAY=2 do not carry the data forward).

Re: Using REPEAT function to calculate IRR

PaigeMiller — Thu, 26 Mar 2026 08:57:09 GMT

So, @jitb , I would like to briefly summarize the responses so far. In order for you to have the best chance of getting good replies in the future, please keep these things in mind:

When you are having problems, we need a clear explanation of what you are trying to do. Do not assume that because you posted code that doesn't work, we know what you want.
We also need to know you think the correct answer is, or at least the correct thing for the code to be doing.
We need a portion of your SAS data set, or we need made up data as long as it illustrates the problem. Please follow these instructions and examples to provide the data.
If there are errors in the log, please show us the LOG (start to finish) for the DATA step or PROC that you are having errors in. Do not show us tiny portions of the log.

Re: Using REPEAT function to calculate IRR

PaigeMiller — Wed, 25 Mar 2026 21:20:10 GMT

It would be extremely helpful if you showed us the ENTIRE log for this data step (not a small portion of the log).

Also, as far as I can tell, there is no need for %sysfunc here, yet you chose to use it even though no macro variables are present. As far as I can tell, there is no need for %str here, yet you chose to use it even though no macro variables are present. If payment_amount and term are data set variables, %sysfunc and %str cannot access the values of a data set variable. Therefore, %sysfunc sees text as the second argument of the REPEAT function. The text is

term-1

which is not a number, and not a reference to a data step variable, hence the error.

So if you remove %sysfunc and %str and their associated parentheses, this might work.

Re: Daily SAS Problem?

PaigeMiller — Wed, 25 Mar 2026 09:45:39 GMT

Go through the SAS Communities and read the original post in old threads (you can pick the New Users community if that is appropriate for you). Don't read the answers, just read the original post. Provide your own answers.

I think 2018 was a good year.

Re: ERROR: Model is too large to be fit by PROC GLIMMIX in a reasonable amount of time on this syste

PaigeMiller — Mon, 23 Mar 2026 17:58:48 GMT

random intercept / subject=PRVDR_NUM(hrrnum) group=PAC_1 type=vc;

So here HRRNUM is nested within PRVDR_NUM. That's 2943 x 306 = 900,558 different combinations. I can understand why SAS is telling you this will take a very long time. Further, with 160,391 observations, the data will be very sparse in some of the combinations of HRRNUM and PRVDR_NUM; in other combinations of HRRNUM and PRVDR_NUM, there will not be any data. So, this is an overspecified model as well, you can't estimate everything.

Re: ERROR: Model is too large to be fit by PROC GLIMMIX in a reasonable amount of time on this syste

PaigeMiller — Mon, 23 Mar 2026 16:12:29 GMT

It cannot be done in a reasonable amount of time. This probably is not a memory issue (otherwise the error message would specifically say memory), it is most likely a CPU issue.

How many levels are there in each of your CLASS variables? Can some of the levels be combined?

How many observations in data set data.model_df?