@Aexor wrote:   I have one requirement of migration activity where I need to store this code  in a macro variables.  I don't even understand the requirement of storing a program in a macro variable. Programs can be stored as simple text files, why can't you just do that? ... View more

@jbibb14 wrote: I am still new to running everything with this software, in your opinion would there ever be a reason to run the code i typed without entering a diff or adjust parameter? Yes, of course you can run the program exactly as you wrote it, without other options. You can use different statistical methods by specifying other options, if you want. There are probably a dozen different ways to compare means that are useful in some situations, as explained in the documentation. ... View more

@T_AR wrote: I think the soultion of adding up* components may have worked  No idea what the above is talking about.   You can also send HTML to a dummy file, so that no actual file is created, and the ODS OUTPUT works properly. Example:   filename fake dummy; ods html file=fake; proc means data=sashelp.class; ods output summary=summary; var height; run; ods html close; ... View more

(The ODS solution doesn't work in the production environment because it must create an HTML file, and that's blocked in production by IT).   Send the output to a text file, and then ODS OUTPUT works fine. ... View more

@pavank    Please listen to @Kurt_Bremser and use PROC PRINT, this is sooooo much easier than writing DATA _NULL_ code to do what you want. And PROC PRINT has many other useful option as well, that you may need on other problems.   To steal again from Kurt, see Maxim 7 Maxim 7 There is a procedure for it. (The exception proves the rule) Learn to use prefabricated procedures for solving your tasks. 5 lines of proc means may equal 20 lines (or more) of data step logic. ... View more

Suggestion: simplify your coding and your titles and make titles more readable. Titles don't need parentheses around the information, and the single-quote or double-quote around LINE is not necessary either. Use actual ENGLISH words in your titles, properly capitalized, instead of variable names like productline   title2 "Product Line = &var2., Sale = &var3., Price = &var4."; The whole point of a title is to convey information to an audience (who may not be computer programmers), if that audience speaks English then the title should be in English and not computerese. ... View more

From the documentation   OUTFCST OUTFORECAST determines whether forecasts are included in certain tables sent to the output data set. If OUTFORECAST is specified, then forecast values are included in the output data set for Tables A6, A7, A8, A9, A10, B1, D10, D10B, D10D, D16, D16B, D18, and E18. The default is not to include forecasts. The OUTFORECAST option can be specified in either the X11 statement or the FORECAST statement with identical results.   You don't have to send output to HTML, you can send output to a text file and then the ODS TRACE and ODS OUTPUT should work fine.   ... View more

I don't understand. Variable names in the log window? Doesn't the log show you the code you execute, which includes the PUT statement with the variable names? ... View more

Or use ODS TRACE to determine how to get the output into a SAS data set https://www.lexjansen.com/nesug/nesug07/cc/cc30.pdf ... View more

@sasuser_8 wrote: I tried with a colleague to transpose this method into my real program but it is too complicated for us. The program from @Kurt_Bremser requires NO changes to the code to run with 12 months. It doesn't get any simpler than that.   If it doesn't work, don't say "It doesn't work", show us the code you tried. ... View more

Instead of using AI, check the documentation! https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.4/etsug/etsug_x13_toc.htm   I think you want to add options to the FORECAST statement, as shown here: https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.4/etsug/etsug_x13_syntax10.htm ... View more

The code from @Kurt_Bremser above makes this easy. No alteration to the code is needed if you have 12 months instead of 5. ... View more

The code from @Kurt_Bremser above makes this easy. No alteration to the code is needed if you have 12 months instead of 5. Better to work from a long data set than a wide data set.   @sasuser_8 wrote: I would like to insert an ARRAY in the PROC REPORT so as not to have to do the COMPUTE for each of my variables (m1,m2,m3,m4,m5). As we can see in this example but I'm not able to do it: https://support.sas.com/kb/43/765.html Please don't tell us "I'm not able to do it" and then provide no other information. We don't know what you tried. We have no idea what went wrong. If there are errors in the log, show us the LOG. If the results are not what you want, show us the code, show us the incorrect output, and explain exactly what you want. ... View more

Given this trivial example, is it safe to assume that sorting always solves the problem? Could there be cases where sorting does not solve the problem? ... View more

So I can't explain why I get the Tukey and you don't, using the exact same code. If no one else here can figure it out, I suggest you contact SAS Tech Support at 1-800-727-0025 (in the USA). If you are outside the USA, you will have to look on the SAS web site to find the proper phone number. ... View more