About Ricardo_Neves

Ricardo_Neves · ‎01-18-2018

The prompt shows the default value we define. I'm guessing that when I run a program and set a different value it change the definitions of the prompt for that session so every time I run a program that calls the same prompt it shows the last inserted value. I read somewhere that it is possible to right a program that changes the definitions of the prompt but I couldn't find anything on how to do it. I even tried looking at the log to see if I could find how the system is doing it, but I don't think it is there.

Ricardo_Neves · ‎01-11-2018

Hi, I'm using prompts to define some variables to use in a SAS EG project. I managed to configure them to show on every program I need. One of those prompts ('camp') is a text where I list a number of IDs separated by spaces that will then be used as input for a macro function. I sometimes change the values of the macro variable 'camp' using code on a program but when I run other program that uses the same prompt, the default value it shows is the value I entered and not the value stored in the macro variable. Is there a way to change the default value of the prompt when I change the macro variable value using code? Thanks, RN

Ricardo_Neves · ‎12-21-2017

Yes you're right ,for this particular case it is not necessary, but I will have to do other calculations inside the loop using the obtained value. That is why I'm using them

Ricardo_Neves · ‎12-21-2017

Thanks @WarrenKuhfeld I used your code and modified it a bit to fit my purpose. Here is the final version %let Alist =1 2 3 4 5 7 8 9 10 11 12 13; %let A = 1; data _null_ (drop=i); array A(4); do i=1 to 4; A{i} = scan("&Alist.",ifn(&A-i le 0,&A-i-1,&A-i)); call symputx(cats('A',i),A(i)); end; run; %put _user_;

Ricardo_Neves · ‎12-21-2017

Hi, This project will run in cycles (13 each year), and in some processes I have to check the results of previous cycles (sometimes up to 4 cycles back). For that I defined these variables so that every time I run the project it will automatically find the tables marked as the previous cycle (for example we are now on cylce 13 so I need to check some info from cycle 12, 11, 10...). Since will be starting a new year, this will reset, so in January will start cycle 1 of 2018, but I still need to check cycles 13, 12, 11 and 10 of 2017, and when a cycle 2 starts I need cycle 1 of 2018, 1, 13, 12 ,11. What I want is for the variables A1, A2 A3 to update automatically when I define A.

Ricardo_Neves · ‎12-21-2017

Hi, I'm trying to set up a SAS EG project where multiple macro variables are create at the beginning of the project. These variables are A, A1, A2, A3, A4 and must obey the following rules: A is introduced by the user and must be an integer between 1 and 13 A1 = A-1; A2=A-2 .... if any of the variables is below 1 than it should go from 13 backwords I define A using a prompt and All the rules are defined so my problem is with the other variables that depende on A. In python I would just use a list and define the variables using negative indexes. Is any way to do this in SAS other than programming a condition for each variable? Thanks in advance

Ricardo_Neves · ‎10-12-2017

BTW if I think that applying De Morgan's law to id = 000 and SYSTEM NE 'BBBB' then delete we should get (id ^= 320 or SOURCE_SYSTEM_DSC ='BSCS')

Ricardo_Neves · ‎10-12-2017

thanks for the advice, I'll do just that 🙂

Ricardo_Neves · ‎10-12-2017

my problem is that I need to only apply filters if they are not missing, and the data step aproach seemed a better way to avoid adding so many logical conditions but I'll try implementing it that way then... Another reason I was trying to implement the code this way is because I understand the way data is procesed in data step (as much as one can understand during 4 months of work xD) and thought it would be a very big improvement in performance. I am not familiar with the way sql processes data, will this augment the performance significantly? Just by curiosity, do you know why my code isn't working properly?

Ricardo_Neves · ‎10-12-2017

Hi @Kurt_Bremser, In the original code, the data step part is almost identical I just do a simple Cartesian product with proc sql. Here is a sample: (I have much more conditions than these) proc sql; create table campaign_&id. as select * from work.base cross join parametro; quit; data campanha_000_testes; set ampaign_&id.; if id = 000 and SYSTEM NE 'BBBB' then delete; if not missing('oferta Origem'n) then do; if compress('oferta Origem'n) = compress(pack_dsc); end; if find(RP_ID_EXCLUDE,compress(put(pack_cod,10.))) then delete; end; if not missing(Desconto_mens_max) then do; if Desconto_mens_min <= Beneficio <=Desconto_mens_max; end; if not missing(mensalidade_maxima) then do; *distinguir a abordagem; if abordagem in ('Client','Conta') and id ne 303 then do; if mensalidade_minima < mens_liq_conta <= mensalidade_maxima; end; else if compress(abordagem) in ('Client','Conta') and id = 303 then do; if mensalidade_minima < mens_liq_im_conta <= mensalidade_maxima; end; else if abordagem = 'NIF' then do; if mensalidade_minima < mens_liq_NIF <= mensalidade_maxima; end; else do; if Mensalidade_Minima < Mensalidade_Liq_Siva <= Mensalidade_maxima; end; end; run;

Ricardo_Neves · ‎10-12-2017

Hi, I have a process where I do a Cartesian product of 2 tables (one with data and one with parameters) using proc sql and then I use data step to apply the needed filters so that at the end only the lines where the data matches the parameter remain. As you can imagine this is a very inefficient process and so I'm trying to use a datastep approach to apply the filters during the cross join so that the process becomes more efficient. But unfortunately it doesn't seem to be working since and don't get the same results in both cases. In fact, instead of getting something between 1.000 - 10.000 observations, I get only 25! I'm using the code mentioned here http://support.sas.com/kb/24/652.html Here is a sample of what I'm doing: data campanha_000_testes; set base do i=1 to n; set parameter point=i nobs=n; if id = 000 and SYSTEM NE 'BBBB' then delete; if not missing('oferta Origem'n) then do; if compress('oferta Origem'n) = compress(pack_dsc); end; if find(RP_ID_EXCLUDE,compress(put(pack_cod,10.))) then delete; end; if not missing(Desconto_mens_max) then do; if Desconto_mens_min <= Beneficio <=Desconto_mens_max; end; if not missing(mensalidade_maxima) then do; *distinguir a abordagem; if abordagem in ('Client','Conta') and id ne 303 then do; if mensalidade_minima < mens_liq_conta <= mensalidade_maxima; end; else if compress(abordagem) in ('Client','Conta') and id = 303 then do; if mensalidade_minima < mens_liq_im_conta <= mensalidade_maxima; end; else if abordagem = 'NIF' then do; if mensalidade_minima < mens_liq_NIF <= mensalidade_maxima; end; else do; if Mensalidade_Minima < Mensalidade_Liq_Siva <= Mensalidade_maxima; end; end; output; end; run; Any ideas on how to perform this? Thanks in advance

Ricardo_Neves · ‎10-12-2017

Hi, I have a process where I do a Cartesian product of 2 tables (one with data and one with parameters) using proc sql and then I use data step to apply the needed filters so that at the end only the lines where the data matches the parameter remain. As you can imagine this is a very inefficient process and so I'm trying to use this approach to and/or merge to apply the filters during the cross join so that the process becomes more effecient. But unfortunately it doesn't seem to be working since and don't get the same results in both cases. Here is a sample of what I'm doing: data campanha_000_testes; set base do i=1 to n; set parameter point=i nobs=n; if id = 000 and SYSTEM NE 'BBBB' then delete; if not missing('oferta Origem'n) then do; if compress('oferta Origem'n) = compress(pack_dsc); end; if find(RP_ID_EXCLUDE,compress(put(pack_cod,10.))) then delete; end; if not missing(Desconto_mens_max) then do; if Desconto_mens_min <= Beneficio <=Desconto_mens_max; end; if not missing(mensalidade_maxima) then do; *distinguir a abordagem; if abordagem in ('Client','Conta') and id ne 303 then do; if mensalidade_minima < mens_liq_conta <= mensalidade_maxima; end; else if compress(abordagem) in ('Client','Conta') and id = 303 then do; if mensalidade_minima < mens_liq_im_conta <= mensalidade_maxima; end; else if abordagem = 'NIF' then do; if mensalidade_minima < mens_liq_NIF <= mensalidade_maxima; end; else do; if Mensalidade_Minima < Mensalidade_Liq_Siva <= Mensalidade_maxima; end; end; output; end; run; Any ideas on how to perform this? Thanks in advance

Ricardo_Neves · ‎05-02-2017

"it's imho a brute force approach which fights the symptoms and not the cause." @Patrick I agree it's a brute force approach because I don't know a lot of error handling in SAS and I don't know the functions you mentioned. But I created a separate job just for sending the email, and since sending the email isn't an essential part of the process, I guarantee that the chain of events isn't stopped by any problems related to sending the email and this way I still get the error report. I wasn't the one writting the code for sending the email, but here it is in case you or anyone has a idea for a more clean solution: %macro envia_email; %let datetime_var = %sysfunc(time(),hhmm.); %let RC2=%eval(&SYSERR); %let RC1=%eval(&SYSRC); %IF &RC1=0 AND &RC2=0 %then %DO; FILENAME Mailbox EMAIL TO=(&VAR_GALILEU_EMAIL_LIST.) Subject="PTC | &VAR_GLOBAL_AMBIENTE. | PDS da cadeia &VAR_ODATE_CHAR. " attach=(&File content_type="application/xlsx"); DATA _NULL_; FILE Mailbox; PUT "Segue em anexo o ficheiro do PDS."; PUT " "; PUT " "; PUT "Não responda a este email"; PUT "----------------------------------Auto-reply-----------------------------------------------"; RUN; %END; %mend envia_email; %envia_email;

Ricardo_Neves · ‎05-02-2017

@Patrick thanks for your help, I think we managed to solve the problem by changing the return code in the unix process, this way the DIS job still returns an error but the next process still executes.

Ricardo_Neves · ‎05-02-2017

Hi @Patrick, The Error the code is throwing is due to the email service of the server being down, not due to errors in the code. We just don't want our chain to stop because of that again, because the email part is for control only.

Online Status	Offline
Date Last Visited	‎07-18-2018 10:36 AM

Re: Define prompt default value using Macro Variabe

Define prompt default value using Macro Variabe

Re: Create Macro variable from array

Re: Create Macro variable from array

Re: Create Macro variable from array

Create Macro variable from array

Re: Cartesian Product with filters using Datastep

Re: Cartesian Product with filters using Datastep

Re: Cartesian Product with filters using Datastep

Re: Cartesian Product with filters using Datastep

Re: All text goes green (as in comments) when any word is selected

Re: Create Macro variable from array

Re: 8 Day interval starting on Friday

Define prompt default value using Macro Variabe

Abort job if source and compare tables are different - SAS DI Studio 4...

Re: Define prompt default value using Macro Variabe

Define prompt default value using Macro Variabe

Re: Create Macro variable from array

Re: Create Macro variable from array

Re: Create Macro variable from array

Create Macro variable from array

Re: Cartesian Product with filters using Datastep

Re: Cartesian Product with filters using Datastep

Re: Cartesian Product with filters using Datastep

Re: Cartesian Product with filters using Datastep

Cartesian Product with filters using Datastep

Re: How to get Cartesian product in Datastep

Re: Ignore Error in transformation

Re: Ignore Error in transformation

Re: Ignore Error in transformation