Warren here is my log under windows 9.1.3 and the result is correct blank second line are present on both pages so i have no idea why you have problem Andre 3952 OPTIONS ORIENTATION=LANDSCAPE; 3953 OPTIONS PAPERSIZE=A4; 3954 OPTIONS LS=110; 3955 OPTIONS NOCENTER; 3956 OPTIONS NODATE NONUMBER; 3957 RUN; 3958 PROC TEMPLATE; 3959 DEFINE STYLE warren; 3960 PARENT=STYLES.PRINTER; 3961 STYLE BATCH FROM OUTPUT / 3962 OUTPUTWIDTH=100% 3963 FONT_SIZE=9.99PT 3964 FONT_FACE=COURIER; 3965 END; NOTE: STYLE 'Warren' has been saved to: SASUSER.TEMPLAT 3966 RUN; NOTE: PROCEDURE TEMPLATE used (Total process time): real time 0.65 seconds cpu time 0.03 seconds 3967 ODS LISTING CLOSE; 3968 ODS PDF FILE="d:\temp\warren.pdf" STYLE=warren NOTOC; NOTE: Writing ODS PDF output to DISK destination "d:\temp\warren.pdf", printer "PDF". 3969 TITLE ' '; 3970 DATA _NULL_; 3971 INPUT @01 CC $CHAR1. 3972 @02 TXT $CHAR79. 3973 ; 3974 FILE PRINT; 3975 IF CC = '1' THEN PUT _PAGE_; 3976 PUT @10 TXT $CHAR79.; 3977 DATALINES; NOTE: Non-portable document will be produced. The current settings of FORMCHAR use non-standard line-drawing characters and the resultant output file will not render correctly unless all readers of the document have the SAS Monospace font installed. To make your document portable, issue the following command: OPTIONS FORMCHAR="|----|+|---+=|-/\<>*"; NOTE: 8 lines were written to file PRINT. NOTE: DATA statement used (Total process time): real time 0.78 seconds cpu time 0.00 seconds 3986 ; 3987 RUN; 3988 ODS pdf CLOSE; NOTE: ODS PDF printed 2 pages to d:\temp\warren.pdf. 3989 ODS LISTING; 3990 RUN; ... View more

Sivas, Asking without showing parts of the submitted code is often difficult for the reader I must presume you are using a proc print I consider that 20 columns is already much before opening ods pdf you may act upon options like orientation margins papersize=A3 ... and inside proc print you have also options like heading=vertical also the format statement can help you to reduce the width of columns and finally with template or style like var name/style=[fontsize=nnnpt] ... act upon the font choices Andre ... View more

Amit A way to understand [pre] Data z; input year type $ amount; cards; 2005 A 1000 2005 B 35 2006 A 345 2006 B 500 ; run; proc format ; value $t "A" = "top A" "B" = "bottom B" ; value $inv "A" = "bottom A" "B" = "top B" ; run; proc gchart data=z ; vbar year/discrete subgroup=type sumvar=amount; format type $t.; run; quit; proc gchart data=z ; vbar year/discrete subgroup=type sumvar=amount; format type $inv.; run; quit; [/pre] ... View more

Juan this is working you forget a % before local but from a point of view of sas code generate the value generated is outside any sas context and rejected by the processor [pre] %macro maxcol(in,var); %local max; proc sql noprint; select max(&var) into :max from &in; quit; &max. %mend; %maxcol(sashelp.class,age) [/pre] ... View more

Sas local macro variable are disapearing as soon the macro is executed! Andre ... View more

Teresa, you have made one mistake and think about the second remark Andre 1) you are overwriting your source LOS_Angeles With your code replacing it! see how to avoid this [PRE] 25 DATA MATCH LOS K; 26 MERGE LOS_ANGELES (IN=L) 27 KALA (IN=K); 28 BY SCHNAME; 29 IF L AND NOT K THEN OUTPUT LOS; 30 IF NOT L AND K THEN OUTPUT K; 31 IF L AND K THEN OUTPUT MATCH; 32 RUN; INFO: The variable one on data set WORK.LOS_ANGELES will be overwritten by data set WORK.KALA. INFO: The variable two on data set WORK.LOS_ANGELES will be overwritten by data set WORK.KALA. NOTE: There were 2 observations read from the data set WORK.LOS_ANGELES. NOTE: There were 3 observations read from the data set WORK.KALA. NOTE: The data set WORK.MATCH has 2 observations and 4 variables. NOTE: The data set WORK.LOS has 0 observations and 4 variables. NOTE: The data set WORK.K has 1 observations and 4 variables. NOTE: DATA statement used (Total process time): real time 0.06 seconds cpu time 0.01 seconds [/PRE] and second point How are you sure there is only one record that differ? This can also happen with this startpoint [PRE] Data los_angeles; input schname $1. one two; datalines; A 12 36 B 15 25 ; data Kala; input schname $1. one two three; datalines; D . 36 45 E 75 27 . C 1 2 3 ; run; Proc sort data=Kala; by schname;run; INFO: The variable one on data set WORK.LOS_ANGELES will be overwritten by data set WORK.KALA. INFO: The variable two on data set WORK.LOS_ANGELES will be overwritten by data set WORK.KALA. NOTE: There were 2 observations read from the data set WORK.LOS_ANGELES. NOTE: There were 3 observations read from the data set WORK.KALA. NOTE: The data set WORK.MATCH has 0 observations and 4 variables. NOTE: The data set WORK.LOS has 2 observations and 4 variables. NOTE: The data set WORK.K has 3 observations and 4 variables. NOTE: DATA statement used (Total process time): real time 0.01 seconds cpu time 0.01 seconds [/PRE] ... View more

Olivier make allusion to the fact he is working in french and i was following this trend. But i have a more general remark who (which?) is just applying to the appearance of the trend Both Olivier and Cynthia have written very long messages upon their screen (without line break) and the conclusion is if ianybody want to keep a paper copy of an interesting solution he has difficulties even in reduced view before printing as at 30% reduce the end of the lines are cutted. In landscape mode it happen me in the past on this forum having twice impossibility to print as reducing at 20% was not more readable and the end of the line were yet cutted. So if some explicit councel to writer could appear to avoid TOO LONG LINES and with also the trick [PRE] [\PRE] Many thanks Cynthia for a direct answer (wielki@ined.fr) ... View more

I tried upon this contents (a french one saved in utf8) but showed here in windows [PRE] Nom,Adressé "Bob","cité Bergère" "Ann","impasse Dôme" [/PRE] with this code under sas windows [PRE] options validvarname=any; filename a "z:\utf8.csv" encoding=utf8; PROC IMPORT OUT= WORK.PAPER3 DATAFILE=a DBMS=CSV REPLACE; GETNAMES=YES; DATAROW=2; RUN; [/PRE] the results are [PRE] Nom Adressé Bob cité Bergère Ann "impasse Dôme" [/PRE] But as soon as i have a third variable the solution is going down! I think the only sas solution is to -read each line of the external file -suppress the line break and rewrite it Andre ... View more

the Note, following me, is comming from the number 3 which is printed on the axis so at the limit of the data area! j=l is only meaning left and it doesn't matter here and the functionning of the repeat is issued from some try as this was working symbol3 v=dot pointlabel=("#n" c=red position=top); use of a x ou y and even the following was not working symbol3 v=dot pointlabel=("#alpha" c=red position=top); so would i have luck or not? and i tried the repeat=11 but in fact repeat=2 is working already ! The mystery in inside Sas. Andre ... View more

I don't have those note with the code you have posted the only one i got is WARNING: Can not use MODE=RESERVE and POSITION=(INSIDE). Changed to MODE=PROTECT. and it disappear as soon as i specify mode=share in legend Your program produce no more note or error! but your problem is related to what the documentation say about pointlabel "The variables that you specify must be the plot's X and Y variables. Specifying any other variables will cause unexpected labeling. " I tried with this code and it seems working avoiding explicitly interpol and allowing repeat 11 times following your max value of threshold [PRE] goptions reset=all ; Proc Gplot data=set5; plot ucl*N=alpha / vaxis=axis1 haxis=axis2 legend=legend1 vref=.03 cvref=ltgray lvref=2 noframe; symbol1 c=yellow i=join h=.5; symbol2 c=lime i=join h=.5; SYMBOL3 V=dot i=none repeat=11 pointlabel=(position=top j=l "#threshold") ; axis1 order=(0 to .5 by .1) label=(a=90 c=black "Upper Confidence Limit (%)") value=(h=1.5 '0%' '10%' '20%' '30%' '40%' '50%') minor=(number=1) color=black; axis2 order=(10 to 120 by 10) label=(c=black "Patients Enrolled") value=(h=1.5) minor=none color=black; legend1 mode=share position=(inside top right) value=(c=black h=1.5 "95% CL (Alert)" "80% CL(Watch)" "Threshold") label=none down=3 across=1; Run; quit; [/PRE] And i have finally your NOTE normal as you have 4 5 6 7 8 who are present twice for the alpha=3 I hope i have well understand your problem. Andre ... View more

You encounter a sas table stocked in an xport format (xpt is usually the suffix but not always) so you need a special manner to recreate a normal sas table try this [pre] libname in xport 'C:\04572-0002-Data.xpt'; libname ou v9 "c:\"; proc copy in=in out=ou; select one;run; *if you are sure that the dataset name is 'one' ,otherwise dont use the select and read your log to find the table name; proc means data=ou.one; run; [/pre] Andre ... View more

First you make a mistake in copying the code your first type is in that case: type ='0'; if not go to third! Second you have a first datastep creating a sas dataset with the name type written in the library defined behind the libref ca In that data step, you are reading temporary sas dataset cak and adding to every observations a new variable numeric type with value 0 with a second datastep you are taking the preceeding table issued from the datastep and adding once again cak dataset. as the structure is the same for both dataset except that you don't have the type variable in cak, type will take as value the . as missing value in the third step you are sorting the final ca.type dataset upon the value of type Third Now a personnal remark : If you are saying that type as already values like 1 2 3 I too don't understand nothing so my final suggestion work step by step and after every step take a look at your output table with VT command to understand what's happening to type! And read your log especially after the first step submit. Andre HTH Andre ... View more

Which procedure please? Show your code! ... View more

Cynthia, ok for this ods rtf text= manner of doing even if my knowledge of english did not permit me to understand every nuances of a jabberw...! but why in the three proc print does i have 'subliminal' non printable text before Obs [pre] .(. tc "Print" \f \l 1...."Dataset SASHELP CLASS " \f C \1 2) [/pre] Andre ... View more

You were asking text generation corresponding to a libname and a table to use inside a proc print of course c:\ is not a libref which must be written in upcase and clean8 is not in upcase and is perhaps a table name reachable only if you have passed a libname previous so correct your input, please Andre ... View more