it is a reality that people want date and time separate, but I find that expectation disappointing
When time information is also relevant, I find it no problem to extend a date constant (in a macro variable) for use as a datetime constant. For example, select all transactions since noon on &sysdate
where tran_date >= "&sysdate:12:0"dt ;
When seeking to report, there are many formats with names beginning DT. These were designed to provide just the date information from a datetime value.
Are there any formats designed to reveal only the time part? I expect so. If I cannot find the one I need, it is easy to construct a new one using proc format's picture statement and the date and time directives.
When separating time from the appropriate date, storage is needed for another numeric variable, adding a few gigabytes or much more for some transactional information systems like flight bookings and card transactions and phone call connections and internet activity.
Ok, sometimes I might want just the day -e.g. for sql-type joins, or just the time -e.g. for time-of-day analysis. Then I would extract the relevant part only when really needed through a view .... minimising use of storage and I/O, and runtime........
but people want it, and the customer is always right,,,,,, sigh
PeterC