About PascalMaurice

PascalMaurice · ‎03-23-2016

Hi there, we find this advice: A Linux startup script is used to set the needed Oracle and ODBC environment variables. Normally, the best place to set these in the SASENV_LOCAL file in the !SASROOT/bin directory because it ensures that they are set for whoever starts SAS, no matter how it is started. perhaps the SASENV_LOCAL could not be considered as the best place: now we have the Lev1... directory tree with all the files to be used to tune the SAS platform, doing so we are sure that all the specific tuning and parameters is done in this directory tree and not on files spreaded across Lev1 and sashome. for example Lev1/level_env_usermods.sh could be a best place ?

PascalMaurice · ‎03-03-2016

Hi Chris, thank you for your answer, I'll have to look to all this stuff and be back to you soon

PascalMaurice · ‎03-03-2016

Hi Jim thank you, I think your proposal could be the solution, until we find macro variables support in the SASEguide Import data task. I've opened another track to work on a translation of the Copy Files Task from Chris for my French Customers. And start to build a demo to show them they can use this Custom Task to answer their need. thanks again Jim

PascalMaurice · ‎03-02-2016

Hi there Chris Hemedinger as done a great job developing nice Custom Tasks like the Copy Files task, and I tell to my customers they should use it, but the gui is in English, and I'm working in France with French speaking users. Does somebody already worked on translation of the Chris' Custom Tasks ? Chris if you read this question, do you have any advice / approach to tell us on this subject ? thank you

PascalMaurice · ‎03-02-2016

Hi Chris, nice to see you on my track ! your proposal is perhaps the beginning of a solution for the path of the file to be imported, now we have to find something to manage the file name itself: for example you have a myWorkbook_2015.xls file and you want to make something like myWorkbook_&year..xls because the name of your excel file change over the year. thank you

PascalMaurice · ‎03-02-2016

Hi Jim there si some thing you cannot manage is the part of the importing task that extract the data from the Excel or csv file and then upload them on the server to be available to the sas data step. You can then use a macro to build the full pathname of the transfered file, but not to build the filename of the Excel or csv file thank you

PascalMaurice · ‎03-02-2016

Hi Tom perhaps some idea to dig in, I'll work on it when some time to do it and tell you my thoughts thank you

PascalMaurice · ‎03-01-2016

Hi all, I known all this stuff and alternatives to export SAS data to Excel, but my question is: how to use variables (SAS or not SAS...) to use parameters in the imported files path of the SASEguide task. I do not find any solution on my side, that's why I've asked to the community, hoping somebody already worked and addressed this need... If there no way, I'll post it in the SASWare Ballot... thank you

PascalMaurice · ‎02-29-2016

But sometimes there is some things passed from SEGuide to SAS Workspace, for example the SAS Workspace knows where the SASEguide project has been saved. and ok, there is no SAS macro-variable that can be used in this task, is there another way to provide parameters to be used in the path of the files imported ? thank you

PascalMaurice · ‎02-29-2016

Hi Kurt, the question is associated with the SEGuide task, not sas code, and in the SEGuide task you cannot (or I do not find how to) use macro-variables in the path of the Excel Workbook to be imported:

PascalMaurice · ‎02-29-2016

Hi there, We have been using macro-variables to parameterize the paths of the imported files, for example: %let year = 2015 ; filename in "&rootIn./myWorkBood&year..xls" ; proc import... now is we want to replace the old timer code by a brand new SASEguide task to import the data from the Excel Workbook, I do not find any way to get a variable known as well as by SASEguide as my sas Code, like _CLIENTPROJECTPATH any good idea ? thank you Pascal

Online Status	Offline
Date Last Visited	‎10-12-2018 09:11 AM

Re: Using SAS/ACCESS Interface to ODBC on UNIX Platforms

Re: Translated Chris' Custom Task

Re: How to use parameters (like macro variables) in the path of SASEgu...

Translated Chris' Custom Task

Re: How to use parameters (like macro variables) in the path of SASEgu...

Re: How to use parameters (like macro variables) in the path of SASEgu...

Re: How to use parameters (like macro variables) in the path of SASEgu...

Re: How to use parameters (like macro variables) in the path of SASEgu...

Re: How to use parameters (like macro variables) in the path of SASEgu...

Re: How to use parameters (like macro variables) in the path of SASEgu...

Re: How to use parameters (like macro variables) in the path of SASEgu...

Re: Using SAS/ACCESS Interface to ODBC on UNIX Platforms

Re: Translated Chris' Custom Task

Re: How to use parameters (like macro variables) in the path of SASEgu...

Translated Chris' Custom Task

Re: How to use parameters (like macro variables) in the path of SASEgu...

Re: How to use parameters (like macro variables) in the path of SASEgu...

Re: How to use parameters (like macro variables) in the path of SASEgu...

Re: How to use parameters (like macro variables) in the path of SASEgu...

Re: How to use parameters (like macro variables) in the path of SASEgu...

Re: How to use parameters (like macro variables) in the path of SASEgu...

How to use parameters (like macro variables) in the path of SASEguide'...