Time is AM, instead of PM, when using ODS RTF

To comp.soft-sys.sas --

I'm using ODS RTF to write SAS/GRAPH results to an RTF file.  The date-
time stamp that gets written in the header of the RTF file is:

05:33  Wednesday, April 09, 2008

The only problem is, that the time is really 5:33 PM -- so it should
say either "5:33 PM" or (preferably) "17:33".  Does anyone know how to
fix this?  Thanks much!

       --Tom

Tom,

There is probably an option that I'm not familiar with but, regardless,
you can always simply turn off the date with options nodate and add a
title with the date or datetime in the desired format.

Take a look at the thread:  http://www.**--****.com/ 

HTH,
Art
-----------

> - Show quoted text -



That was a great tip Aruthur... I saw that a few days ago and then
made one like this:

title2 "Double-Data Entry Progess report as of
	 %left(%sysfunc(today(),worddatx.) -- %sysfunc(time(),timeampm.))";


which produces this...

Double-Data Entry Progess report as of     10 April 2008 --  9:11:07
AM



The OP on that thread was troubled by the fact that the SAS date/time
is always stuck at the time SAS is started, and when one keeps SAS
running all day long, as many of us do, then that timestamp is not
very helpful at reporting time.




Tom,

I know on XP the display of time is obvious am/pm.  Maybe you're using
another OS and time is displayed differently  ...is the time set
correctly?  is the timezone set correctly?  Sorry to ask the obvious,
but that's me sometimes, captain obvious....and sometimes I'm major
over-complicating things.

In any case, Arthur's tip should provide you with an effective work-
around; but I hope you can find and fix the 12-hour time error you
observe.  Good luck!

Bill

Bill --  thanks!  But I *am* using Windows XP.  And my time & timezone
are set correctly (e.g. bottom right of screen shows "1:30 PM", which
is correct).  I'm don't think that what I'm getting is actually a "12-
hour time error" -- i.e. the RTF file just produced by ODS RTF is
saying, in its header, "01:30", which technically is correct, but
CONFUSING since one might easily think it's AM, when it's really PM.

And yes, I suppose the workaround will work, but I'm still hoping to
find what's at the bottom of this!  Thanks again ... Best,  --Tom

Another problem with this date and time  is that its not fixed. Its
actually a field code DATE which returns todays date and time when the
file is opened so it keeps changing. Not sure why SAS did this as it
makes it pretty well useless!
R

I think I have found the solution.
Use the SASDATE option in the ODS RTF statement. (uses the SAS date
time rather than the date the file is opened)
and use the system option
OPTION DTRESET  /*resets SAS date to current date time for any printed
output*/
The result is the date and time in 24hr format and for the actual time
the proc is run.


Cheers
R
use

> Another problem with this date and time s that its not fixed. I>s
> actually a field code DATE which returns todays date and time when t>e
> file is opened so it keeps changing. Not sure why SAS did this as >t
> makes it pretty well useles>!
> R

is that another example of the delights of ms-word !

For those of you who would like to place the title1 date information
into some other place, may I offer the (less-familiar) format TWMDY,
as in
%put %now( fmt= twmdy );

Here it is used on a title3, right aligned by ODS
title3 .j=R "%now(fmt=twmdy)" ;

That title uses the current timestamp rather than the time that a
title line would actually use. For the best approximation of that, use
%let titletime=%sysfunc( putn( "&sysdate9:&systime"dt, twmdy));
title3 .j=R "&titletime" ;

For the old listing destination, we don't enjoy that justification
convenience, so the title3 would need to be something like

option nodate ;
title1 "try puting date elsewhere";
title3 "%sysfunc( repeat( %str( )
           , %eval( %sysfunc(getoption(ls))
                  -1-%sysfunc(length( &titletime))) )
           )&titletime";
proc print data= sashelp.class;
run;

PeterC