Hi @n6    In many cases "return to sender" is not an option, e.g. if the source is an application where data is generated by many users for a long period, so we have to deal with garbage and make the best of it. The definition of "best" depends on the further use of data, so it is not a technical matter to decide if a partial date is best represented as a missing value or as an interpretation where a missing day component is set to 1 or 15 or whatever.   If you are working on your own project you can make your own decisions like "I only want years in my final analysis". But if you are just preparing data, you shold always consult the requestor and make her define "best" instead of making your own interpretation and present the result as facts to the requestor.   It is tempting to read dirty dates with an any-informat as shown in @PeterClemmensen 's example. But be careful, because the result is an interpretation, where missing values are filled out and day/month may be shifted, as the following example will show:   data work.have; input VisitDate $20. ; cards; % %/%/% %/%/2008 %/%/2009 01/%/2010 01//2013 01/1/2010 02-03-2011 02-11-2011/ 03/%/2008 03/%/2010 03/13/12 13/03/12 03/5/2013 /% /%/%/% %/%/2008/ %/%/2009 /01/%/2010 /01//2013 ; data work.w ; set work.have; format date_any date_mdy mmddyy10.; date_any = input(VisitDate, ??anydtdte12.); date_mdy = input(VisitDate, ??mmddyy10.); run;   ... View more

Hi n6 In my situation,this WARNING message is deleted/ not shown.   How = Surround proc lifetest with ods graphics   ods graphics on; proc lifetest date = work.x; run; ods graphics off;     My situation. With my PC SAS (ver 9.4) ,when I do proc lifetest before using "ods graphics on/off", through interactive mode is no warning. But do the .sas file through batch executing, the log output this message.(WARNING: Output 'SurvivalPlot' was not created. ) After adding ods graphics on and off, there is no warning when I execute it by interactive and batch either. I wish you have no warning... Hand. ... View more

  The problem is solved, the old fashioned way by the person making it into a nice, rectangular thing on their end and sending it to me and then me putting the data into a data step.  The person wasn't crazy about having the data out there so I couldn't copy and paste the hexidecimal thing here so we solved it more primitively.  But much thanks to all who assisted. ... View more

Can you provide an example data set with the variables involved in the plot that shows this issue?   Minor style point: You are making this line more complicated than needed: axis1 label = ('Number of Cigs ' "&EL" ' in Previous ' "&MIN" ' Minutes')   try axis1 label = ("Number of Cigs &EL in Previous &MIN Minutes")   Breaking up the pieces of a label is really only needed if you are applying different text characteristics for different bits of the title. ... View more

The option WHISKERPCT is supported with SAS 9.40M2.  You seem to have SAS 9.40M1.   You could use the method described in the blog article. ... View more

Okay, I finally got it, thanks partly to the help of you all here, especially the part about making the whisker be the same color as the background, which worked and I've come to believe is the only way to do it.  Here is my code, made generic. proc sort data=dataset;   by day2;   run; proc sgplot data=dataset; panelby day / rows=1 columns=5 novarname sort=data; rowaxis label = 'Label'  value = (0 to 20 by 5); colaxis label = 'Sex'; vbox y / category=sex nooutliers; whiskerattrs = (color=white); run; Here is some explanation.  Pretend the group variable is Day and takes values Mon Tue Wed Thu and Fri.    I made another variable named Day2 like this: if Day = 'Mon' then Day2 = '1-Mon'; if Day = 'Tue' then Day2 = '2-Tue'; if Day = 'Wed' then Day2 = '3-Wed'; etc. That is why I sorted by Day2 at the start   And then in the PANELBY line I have Sort=Data.  That tells it to list the items in the order they are in the dataset, which I just sorted by Day2.  So it lists them in the order of 1-Mon, 2-Tue, 3-Wed, etc.  Earlier in that line I have PANELBY Day.  So I'm using Mon, Tue, etc, but instead of ordering by the default of alphabetical order, which would put Fri first, it orders it by 1-Mon, 2-Tue, etc.  At the top of each column of boxplots it would have Day=Mon or Day=Tue, etc, except that I use the novarname option and that tells it to just put Mon, Tue, etc at the top of each column. I use rows=1 columns=5 to get them all on the same line.  When I didn't do that it made two rows of three, with the last one on the bottom line empty.  So I tricked it to putting them all on the same line, which made them a little narrow, but it's okay. I used value = (0 to 20 by 5) because without that the y-axis will go way up to the highest value and all the boxplots will be squished at the bottom since there are some high outliers. You can omit the label= parts in ROWAXIS and COLAXIS and it will just use the variable name as the label instead. The nooutliers option is needed because even though the whiskers are white, the outliers will still be there in black unless you tell them not to be via the nooutliers option. And WHISKATTRS = (color=white) is the coup de grace that makes the whiskers white and thus invisible against the white background. Thanks for the help.  Hopefully you can use some of the tricks in the code above to make your life easier. ... View more

"squished" is likely a result of the current goptions for hsize and vsize or xpixels and ypixels settings. These settings control the aspect ratio. You didn't mention the types of graphs your are producing but you may want to investigate the SG procedures as you can do many things that aren't possible with Gplot and Gchart. ... View more

"Always on" means different things to different folks. The behavior has changed. In SAS 9.3 for instance if you have sgraphics on then every time you run proc freq you get histograms and different graphs for other procedures, which you may not want. The addition of ODS complicates things with the older SAS Graph procs as well. They will generate a Listing output of the type around since SAS 6, and the specified ODS versions. EACH of those destinations may use a different ODS style to control appearance. To see if the style may be the cause of the only black output try this: ods listing style=meadow; ods html style=meadow; your graphics procedure goes here ods html close; ods listing close; and see if the two different results look more similar ... View more

I think I have figured it out.  Although your answer wasn't right it did lead me to realize what I was doing wrong. TEST=DIFF is for when your alternative hypothesis is that the two groups are different.  But I am doing an equivalence test, which means my alternative hypothesis is that the two groups are the same, or at least that the difference between the two groups is less than some specified number, and thus I want to use TEST=EQUIV_DIFF. In my original example I wanted to show that the difference between the two groups is at most 4.  I put that number (4) in the MEANDIFF line.  But if I wanted to show that the difference between the two groups was 4 then I should've used LOWER=-4 and UPPER=4.  LOWER and UPPER are the largest difference we'll allow between the two groups in each direction.  In an ordinary equivalence test LOWER and UPPER will have the same absolute value. OTOH, MEANDIFF is the difference in the means between the two groups that we are going to assume exists.  If we assume the two groups have the same mean then MEANDIFF=0. In my original example I wanted to answer the following question:  Assuming two groups have the same mean and also that both groups have a standard deviation of 8 and also assuming the two groups are equivalently sized, what is our required total N to have 90% power for an equivalency test to show that the difference between the two groups is at most 4?  Here is the code that answer that question.  We're also assuming a 0.05 alpha level but that is such a common assumption that we don't need to code for it. proc power;      twosamplemeans test=equiv_diff      lower = -4      upper = 4      meandiff = 0      stddev = 8      ntotal = .      power = 0.9; run; ... View more

My earlier paper 237-31.pdf spoke more about customising display manager, but it sounds like you need the easy way to avoid contention between EG and base SAS for the sasuser area and this year's paper shows the easy way to that solution. Good luck Peter ... View more

Well, one check would be to explore the LSMEANS and LSMESTIMATE statement (if this is available in your version). If your LSMEANS statement was: lsmeans varname/diff ilink; you could compare the results for the first comparison to each of the two methods.  See which corresponds. Went to the documentation--way down in the Details section is a part on Generalized Score Statistics under GEE models.  It looks like the contrast statement is using the quadratic form reported there, while the estimate statement uses the standard quadratic form to get the chi-square values. Also, in the documentation for the CONTRAST statement, it says "If you omit the WALD option, the test statistic computed depends on whether an ordinary generalized linear model or a GEE-type model is specified."  And there is the difference--the ESTIMATE statement always produces a Wald chi-square, while the CONTRAST statement picks based on the type of model.  So now you have to determine which is appropriate.  My money is on the generalized score statistic, since under GEE you should accommodate the covariance error structure, and it appears (at least to me) that this is not necessarily the case for the ESTIMATE statement. Steve Denham ... View more