Hi, usually, for this kind of logic, I think it better belongs to your scheduling tool. Most of them have file events that can trigger jobs depening on things like arrival.   That said, I also recognize the (weird?) fact that the User Written Transformation doesn't accept External Files. Using Pre-code to the File RFeade is to little avail since almos no useful macros are defined here, especially not the file name.   Allthough, the User Written Code might work. For some reason, you get a lot of automatic macros here. So one way to wrap it up is to write a mcaro that you stored in a SASAUTOS location (typically configdir/SASApp/SASEnvironment/SASMAcro. Then you need to instruct your users to simply add a call to that macro in the User Written Code Transformatino that is linked to the External File Object. ... View more

Forgot to mention - a worthwhile read may also be the discussion at https://communities.sas.com/t5/SAS-Visual-Analytics/GeoMapping-with-SAS-VA/td-p/349311 which seems to cover the same topic.  ... View more

Several people have already answered that for you, there is no difference.  My post was an addendum to that to point out that functions are available to help readability and add additional functionality. ... View more

Several people have already answered that for you, there is no difference.  My post was an addendum to that to point out that functions are available to help readability and add additional functionality. ... View more

I would say that you can't.  You will probably need to get additional information to help decide.   You might say that 201433 could only be divided into 2014-3-3, but perhaps the missing digit is a 1 or a 2 instead of a 0.  Then the intended value could be 2014-03-13 or 2014-03-23.  Or perhaps the 4 is the typo and it is really in ddmmyy format so that the intended value is really 1933-12-20.   ... View more

Hi,   I'm not sure of what platform you are running this on, but if you are using mainframe Z/OS, you might consider having one subtreatment in a generational file and then at the end in a separate JCL step, you might concatenate the gdgs into one dataset through a SyncSort - Copy option and you will have all subtreatments combined to one master dataset.    The individual generations will be pointing to sub-treatments and the output of the SyncSort  copy will hold the master data that includes all subtreatments.    If you are running in a Unix platform, you might use a concatenation utility to do what Syncsort does on the mainframe.   Hope this helps...!!!     ... View more

ok I can read it hex now  after "2," (32 2C)  there is that (18 0e    19 0e   1a 08   18 0e   19 0e    1a 08 )  "Ju"  (4a 75). can=18 so=0E  em=19   etc.   It are the lower 32 bytes of 7-bit ascii  once used as instructions. (Cancel, Shift out, empahized etc.  CR/LF SUB=eof 1A as still used). That doesn't make sense at a data record unless it is encoded string. It is US based data and 6*2 (12 bytes)  .   It looks as 6-2 byte conbinations  may be UTF16 UTN #12: UTF-16 for Processing    but that doesn't make sense with some chars.  (eastern ones) It could be the binary dump of some integers (reversed order 6 of them 3608,3609,2074  - repeated) doesn't see any meaning of that  ... View more