Best practice on this forum is to show us the LOG generated when submitting the code. The exact wording of error or warning messages is important as they often include important clues as to possible solutions.   I suggest that you re-run the code and if the issue persists to copy from the log the code and all messages related to proc http. On the forum open a text box using the </> icon that appears above the message window and paste the copied text.   You don't show a definition for the OUT=resp. Somewhere prior to this you should have a Filename statement creating a reference to a file that the "get" will write to for later processing. ... View more

Generic question gets a generic response: differences arise from different details in the programming and often the machines the code executes on. Things like number of decimal places maintained internally for computations can easily effect results even when using the same algorithms and just because a statistical test has the same name in different packages there is very likely no commonality at all points in the way the algorithm was programmed.   HOW much difference might be the question that you need an answer to.  So perhaps sharing the results in question is place to start.   Also some programs will report the results using different defaults. For instance in a logistic regression with a true/false type outcome one program may default to modeling the "true" value and the other the "false". So same data would tend to report something that looks like a compliment of the other (70% true or 30% false for example).   For serious details you might need to include: Your data Your Code for both approaces The output The research you question you want answered so we can validate that the SAS (at least) approach is using appropriate options.   Some of the SAS procedures will have a section in the online help called details that may include some of the computation details. ... View more

Are you sure that what you are attempting to get power is not available in Proc Power? Or maybe Proc GLMPower? These procedures have options that let you set multiple things like multiple power and generate needed size N or vice versa.   Are you sending Proc Freq output to the default display? As that gets more output then just doing the display refresh may be part of the issue. I would suggest turning off the display using the Proc Freq NOPRINT option and generate data sets from Proc Freq with the desired output.   It may help to post the code of the macro so we don't have to ask a bunch of "do you have this option enabled/disabled" questions.     ... View more

What exactly does " I cannot get the PROC MIANALYZE to work" mean? Do you get errors, unexpected output, no output?   It is more useful to post the LOG with any messages generated and the code as the messages often provide details as to what is happening. Copy the step or procedures in question from the log, on the forum open a text box using the </> icon that appears above the main message window and paste the text in the box. The box will preserve the formatting from the log. ... View more

You will want to repost your examples, input and output both, into a TEXT box on the forum. Open a text box by clicking on the </> icon that appears above the main message window and paste the text. The software of the forum mean that the main message windows will reformat pasted text and replace white space characters which means that we will not see what you want if the examples are pasted into the main message window. ... View more

One think you might consider given your example list of tickmarks without any details of the data might be to use a LOG type axis which would change the spacing between the ticks.  SOME value of TICKVALUEFITPOLICY will always be in effect. If you don't specify then you get the default behavior will is going to do what you describe. Maybe using a TICKVALUEFITPOLICY of Rotate or RotateAlways coupled with TICKVALUEROTATION=Vertical , which is going to minimize the width of values displayed on the X axis would reduce the amount of work to select specific values that don't get thinned.   In general the larger the value required to display the less space between integer values. One way to prevent thinning is to use the range of values in your data, or the plotted subset of the data and do the calculations yourself before setting the value list.   I will give you a simplified version of something I had to do back in the days of SAS 6.08 and early SAS/Graph. I had data that was read from telemetry daily. Some of the data represented the height of the water column in a rain gauge. The data read was actually a cumulative file, i.e. on one day the file held roughly 24 hours of data, the next day about 48, next 72 and so on until about a weeks worth of data was collected then the loggers were reset. The nature of the rain gauges meant there could be noticeable changes either increases, from precipitation or bugs and birds getting into the buckets, or decreases, when serviced. So the daily graphs that I prepared had to be prepared to deal with as little as 0 change for the 7 day period or as much as spike increases of 15 inches when birds got into the buckets.  I wrote code that examined the range of values for the period and if the value was large enough wrote code to subset the graphs with specified 2 inch ranges of the y axis, each with it's own value list. The 2 inch range per graph was to make sure that we could see the behavior of the column when drastic things weren't happening. If we allowed the whole range to appear as the default then the spikes would make the more typical readings appear flat. I'm sure you have encountered something similar with some data.   Also, you want to determine if the Tick marks are clashing or the Tick Labels. Quite often it is the Label that has an issue and use the options to rotate the text, reduce the size of the text and stagger the text appearance will reduce the conflicts for numbers in the range you show. If using time or date values, a common cause of text long enough to collide then use of a different Format might be in order .   There are enough interactions between the ODS Style, your overrides of style such as text size or font, type  of graph template layout (overlay lattice datalattice overlayequated), axis type (discrete log linear time) that just dropping bits of your template can be quite insufficient to tell what will happen. Look at your LABELFITPOLICY and LABEL POSITION option defaults or settings       ... View more

Going back at least as far as SAS 6.08, 1993 or so, the amount of space, whether on a graph sent direct to printers or files, that the graph occupies has impacted the rules for showing tick marks and default spacing between them when the user did not specify.    The graphing procedures "know" the allowed space for a graph and the number of tick marks required, or requested, for a given axis and option the collision determination is pretty simple math once those pieces of information are determined. Example, if you create an axis of 10 inches length and request 10 ticks it is easy to get 1 inch of space between then (actually more if placed close to the other axis but lets skip that bit). If you reuest 1000 ticks then about 100 need to fit into each inch. The width of the tick itself and most likely any label text then doesn't display well so something needs to be done. Yes I have created axis with so much overlap that the ticks were useless and illegible at times.    The defaults generally do a good job of getting something usable for the displayed graph. ... View more

The results from Proc Setinit do not show that SAS/IML is licensed. So any code including macros that make calls to SAS/IML features will not run and will throw errors.   That means finding a work-around to use instead of that macro. If an instructor or other said that macro needs to be used then talk to that person about access to SAS/IML. ... View more

Please run these two procedures and share the LOG results. These will tell us if the SAS/IML product that the macro requires is available to your license and if it was installed.    Proc setinit; run; Proc product_status; run; The error message does state that if the SAS/IML product is not installed that the macro will not execute. So you will not get any IML dependent results. If you describe what you need someone may suggest a work around that doesn't involve IML. May. The conversion of IML to other steps may not be very easy. ... View more

ELSE. You may want an if then/else construct. Otherwise ALL of those ifs get executed. Also you very likely do not want a WHERE as that removes observations for values on the where statement are not true. So the "day7" would never exist in the data set If this doesn't do what you want then  you should provide and example of the input data set and the desired result. Note: the  "else if" may not be needed at all because there is no reason to change the values, but I have shown it as it seems to parallel your thinking.   data new; set long; IF label in('day0', 'day3') and TRT='Jar' then TRT='Air'; Else if label='day7' then do; if TRT='Air' then TRT='Air'; if TRT='Jar' then TRT='Jar'; end; run; other code that would do the same thing: data new; set long; IF label in('day0', 'day3') and TRT='Jar' then TRT='Air'; run; WHERE statement evaluates the values as they are brought into the data set. If the statement is not true then those obsesrvations, label='day7' (or any other value than day0 and day3) would not appear in the result at all. That where the limitation on single WHERE statement comes from.  Most condition operations based on values of variables would usually be better done with IF statements.    ... View more

Best practice when code generates errors is to include the LOG with the code and error, warning or other messages of concern. Copy the text from the log, on the forum open a text box window using the </> icon above the main message window and paste the code and messages. The text box is important because the forum software will refomat text pasted into the main message window resulting in some of the diagnostic information that SAS often supplies.   As a minimum your code should also include a TYPE variable to tell SAS whether the valus in the START variable are numeric or character and display or input. A type of N (character value of the variable type) means Start is supposed to be numeric and is a display format, Type of C means start is Character and is a display format, Type of I (upper case i) is informat for numeric values, type of J is informat for character values, Type P means a PICTURE format.   If your data contains "A1" and "a1" for the variable and want them both to display the same label text then you want both values in the START.    Because you IMPORT the data from Excel you may have issues of same value, i.e. "A1" with multiple values of the label cause by capitalization differences or white space in values (different numbers of spaces can be hard to see) or leading spaces. SAS doesn't like that for formats or informats and will show errors of duplicated ranges.   Suggestion: Write a small, as in two or there value/invalue statements as normal proc format code and use the CNTLOUT option to write a data set of those. That will show values for the variables needed in the data set.   You may want to consider adding and Other = error option to the above example trial code if creating an INFORMAT. The Other option, which would go into a variable named HLO, coupled with the error option means that use of the format with unknown or unexpected values tells you that such a value was encountered in the log with an invalid data message. ... View more

You should be able to use Proc Template to get the code for the define style and then recompile it with your current system.   I ran into some issues in the past with a custom Style that modified a SAS supplied style and when SAS was upgraded the definition of the same named style changed so that my custom style did not use the SAS style correctly.   This code will show the source code for the style Minimal in the log: proc template; source Styles.minimal; run; You could copy that into the editor and recompile the style. Note that I see this in my install's version of Minimal: style Document / doctype = "<!DOCTYPE HTML PUBLIC ""-//W3C//DTD HTML 3.2 Final//EN"">" contenttype = "text/html" protectspecialchars = auto; Which implies that style is intended to create HTML 3 documents which may cause an issue with the Tagset Excelxp. Creating a file with an XLS extension but applied to a different format of file is one of the things Microsoft has made unrelieable as well.  The warning messages you show do not seem to apply to my version of Minimal so you may have to chase more things down to use that style and the tagset together. The putvars and newline sound more like table output requests than a general style and may indicate an interaction with the Proc Print default table settings and the minimal style as well.   ... View more

You will find that having commas in macro variables is often a problem because that is the separator between values in the macro processor and when such macro variables are used in data step processing you will get similar problems except for the functions that lists of values that are separated by commas.  Additionally having quote characters as part of the value often complicates things as most functions will expect one value within a set of quotes. You encounter an example with your use of Scan ("&mynames",_n_,',') where the data step will see Scan (""AAA","BBB","CCC","V123"",_n_,','). So the first pair of "" is the empty string to search with everything else problematic as AAA" will not be a valid second parameter because of no comma.   Why was your Myname macro variable defined that way? If only to be parsed by this data step then other definitions will likely work better. ... View more

@SASdevAnneMarie wrote: Hello Ballardw, "With" spaces. Unfortunately, I can not modify my message. You should be able to edit any of the posts you have made. There should be a block of three lines next to the subject of the post. Roll your cursor over the block of lines and and "edit message" or "edit reply" should appear. Click and the edit option opens the message or reply. ... View more