10-12-2016 04:04 PM
You can make use of format that makes use of the nested format definition.
Here is a sample:
proc format; value my_mmyys (default=7) . = "99/9999" other = [mmyys7.] ; run; data have; do someDate = ., "01jan2016"d, "31aug2016"d; someDate2 = someDate; output; end; format someDate mmyys7. someDate2 my_mmyys. ; run;
10-12-2016 07:00 PM
10-13-2016 04:26 AM
To what purpose? If it is to display that in a report, then the simplest option is to have two variables - one a numeric date, and one a character version of that allowing for partials, and missing conversions. This is what we do for analysis domains, the numeric to perform windowing and such like, and character for listings so it reflects the data. I would not recommend applying some sort of internal format to the data for two (actually 3) reasons - first anyone who uses SAS knows dates and that . indicates missing - if you try to change that underlying understanding then anyone who uses your code/data has to learn all your specific things. Secondly it requires a SAS specific thing - formats - to achieve, if your data is going anywhere to another system/format then that will cause further issues for you. Also, I personally avoid the use of proprietary binary files as much as possible - the 32bit versus 64bit completely destroying any work done previously with catalogs is a very good example of why.