You might get faster help if you post in the JMP community. https://communities.sas.com/community/support-communities/jmp_software EJ ... View more

did you try? hos_date = dhms("&curdate"d,0,0,0): The dhms variables are either date variables or numeric or something that converts to such like a date literal. Your posted code does not have the date literal syntax around your macro variable. EJ ... View more

Could you just read in all the rows with the import task in the flow and then limit what rows in a filter task? EJ ... View more

I might be remembering this wrong, but I think SAS used to let new customers buy licences abandoned from other companies at reduced rates. I think SAS has a sales chat through their website ... it wouldnt hurt to ask there either. EJ ... View more

Thanks for the reply! The interesting thing is our SID file does not reference the server computer name ... it is actually blank. Not sure we have a subcapacity license since when it was first researched it was CPU count that was effecting the pricing (of course this could just have been a mixture of jargon). In any case, I see a call to tech support in our future, either for a limited use test SID file and / or guidance in setting this up. If anyone else out there has done this successfully we would still be interested in hearing the process you went through. Thanks! EJ ... View more

If you havent go through the process of permanently storing the macro definition (see SAS(R) 9.2 Macro Language: Reference) you must have the macro definition in the program being run as batch. Calling the macro is the same in batch or interactive SAS: %macroname(vars to pass); EJ ... View more

Thanks for the responses! Perhaps more specific about our license setup.  Our install is just the standard SAS analytic products 9.3 (see setinit output below), which the 7 or so user remote into the server and start the a sas session as if it was loaded locally with either the standard sas interface or EG. Our license does not allow us to connect through a local instance of EG to the sas installed on the server. So in other words no thin clients, meta, web reporting, or app servers. The desire is to clone the current VM, upgrade its SAS install to  9.4 and then test key programs to see if we have issues. This way we can address the issues without causing problems for all users at once. If no major problems, then the test vm goes away, we install 9.4 on the production VM and we move forward. If problems exist we figure out the problems in a less "stressful" situation since everything is still running smooth on the production VM. I still trying to get more information from IT about the issues they are having. Right now all I know is: "Due to the way SAS does their server licensing and that we are running in a VMware environment, my efforts to clone have failed, many times.  " I will post more information once I get clarification. Proc Setinit output: CPU A: Model name='' model number='**NCSASPROD1*' serial='+2'. Expiration:   27FEB2014. Grace Period:  45 days (ending 13APR2014). Warning Period: 45 days (ending 28MAY2014). System birthday:   23JAN2013. Operating System:   WX64_SV . Product expiration dates: ---Base SAS Software                                    27FEB2014 (CPU A) ---SAS/STAT                                    27FEB2014 (CPU A) ---SAS/GRAPH                                    27FEB2014 (CPU A) ---SAS Enterprise Guide                                    27FEB2014 (CPU A) ---SAS/ACCESS Interface to PC Files                                    27FEB2014 (CPU A) ---SAS/ACCESS Interface to ODBC                                    27FEB2014 (CPU A) ---SAS Workspace Server for Local Access                                    27FEB2014 (CPU A) ... View more