About Quentin

Quentin · ‎08-06-2012

Another option is to %unquote() the values. SAS is supposed to unquote values automatically after the macro processor has done all of its work, but sometimes it doesn't work, so you need to add the unquoting yourself. One rule I was taught with the macro language is that if the SAS code looks good (from mprint) but you are getting errors, try %unquote. %let a=%quote(A); %let b=%quote(B); data %unquote(&a.&b) ; x=1; run;

Quentin · ‎08-06-2012

Hi, Suggest you look into the character functions available in SAS. I suspect: if findw(ITEM_desc,"Nutella") then do ; could give you what you want. Hopefully this is a one-to-one merge. If not, you can run into surprises because PRODUCER and BRAND will be retained across iterations of the datastep. HTH, --Q.

Quentin · ‎08-01-2012

Thanks again Cynthia, That's just the approach I was hoping would work for a SPWA solution. So far I have had success streaming html/rtf/pdf back to SPWA (with the help of your posts and papers in figuring out how to set the appropriate content-type so that the file is opened by the appropriate app), so will take a shot at streaming TAGSETS.EXCELXP this afternoon. --Q.

Quentin · ‎08-01-2012

Thanks much Cynthia, That makes sense, and you saved me from trying (and failing) to get the add-in to consume tagesets.excelxp. --Q.

Quentin · ‎08-01-2012

Hi, I've only recently started using the Add-in, so this could be off base, but.... As is often the case, sounds like the problem is Excel (sigh). I think what you want is a way to specify the tagattr= style. Eric Gebhart has a paper on how to do this using tagsets.excelxp: http://support.sas.com/resources/papers/proceedings10/031-2010.pdf So the next question would be whether you can also do this using the (default) tagsets.sasreport12 (I'm not sure). Or I guess you could try changing your report to be generated using tagsets.excelxp instead of tagsets.sasreport12, and see if the add-in is happy consuming that format. It may be, because both tagsets.sasreport12 and tagsets.excelxp are xml. But I haven't tried it. Good luck, --Q.

Quentin · ‎07-27-2012

I think there may be some small benefits to PWENCODE (in addition to Tish's method). In an environment where you share code, people sometimes try to share secret passwords in an encrypted compiled macro like: %macro password(); options nomprint; MySecretPassword options mprint; %mend; Which usually keeps things secret until someone curious tries: %put %bquote(%password() ); I guess the real benefit of adding PWENCODE is that if source code for the macro is revealed, you don't see the actual password (useful to anyone who might want to misuse it for any application), you see the encoded password (useful only to SAS programmers). I suppose could also help someone meet a strict corporate rule not to store clear-text passwords anywhere.

Quentin · ‎07-27-2012

Well, I'm still confused as to what the rules are for what you want. Maybe post an example with ~20 records for ~3 or 4 permnos, and show what you would want for output. In any case, both Art and I took similar appraoches, using some sort of look-back (mine with by-group processing, his with lagging). I think playing with either might get you where you want. And of course there is likely SQL solution.... --Q.

Quentin · ‎07-27-2012

Sorry, there was at least one obvious mistake in my sugggestion. Something like this maybe: data want dropped ; set have; by PermNo Year; retain _Year _dropflag; if first.PERMNO then do; _year=.; _dropflag=.; end; if distcd IN (1262,1272) then do ; if (not missing(_year)) and (not _dropflag) then do ; *added not _dropflag to avoid it being reset to 0 after it has been set to 1; _dropflag=((year-_year)le 2) ; end ; _year=year; end; if last.PermNo and _dropflag then output dropped; else output want; run;

Quentin · ‎07-27-2012

Hi, Not sure I understand your requirements completely, but something like this might help: data want dropped ; set have; by PermNo Year; retain _Year _dropflag; if first.PERMNO then do; _year=.; _dropflag=.; end; if distcd IN (1262,1272) then do ; if not missing(_year) then do ; _dropflag=((year-_year) le 2) ; end ; _year=year; end; if last.PermNo and _dropflag then output dropped; else output want; run;

Quentin · ‎07-26-2012

Thanks, SASAUTOS can be defined in the actual stored process code. And that is what I'm doing now: options insert=(sasautos="/myautocalls/dir"); But lots of system options (ALTLOG, AUTOEXEC, CONFIG) can only be specified during invocation. Seems that when a new SAS process is invoked to run a stored process, it would be nice to be able to define (in the metadata associated with the stored process), the system options that should be set during the invocation. But I guess we can't do that yet. Maybe I'll propose this to the SASware ballot. Thanks, -Q.

Quentin · ‎07-25-2012

Abosolutely, always nice to see more than one way to approach a problem!

Quentin · ‎07-25-2012

Hi, If I write a stored process that uses a (non-pooled) workspace server, the server actually starts a new session to run the process, right? Is there a way I can define SAS invocation options for the stored process (-altlog -autoexec -config etc?). I want to define these at the stored process level (so, e.g. different stored processes might use different autoexecs), not at the server level. I'm developing stored processes, but I don't administer the server. One approach would be to use systask to kick off a new SAS session (with the desired options), as Scott Bass describes: https://communities.sas.com/thread/34901 But was wondering if I could define in the stored process metada (and/or as a prompt) the system options to be specified during invocation. Thanks, --Q.

Quentin · ‎07-24-2012

Hi, Thanks for posting your solution. I'm just starting to play with Excel<->Stored Process integration via VBA. Was wondering if you could explain why you went with your approach, rather than using VBA to script the excel-addin, as described in: http://support.sas.com/resources/papers/proceedings11/012-2011.pdf Thanks, --Q.

Quentin · ‎07-24-2012

Hi, Tech support responded that this is a bug resulting in the Excel Add-On not honoring the traffic lighting. I assume it is a bug in how the xml is generated, or the schema used to read the xml (?). They think it may be related to http://support.sas.com/kb/20/798.html , (which references a problem reported as fixed in 9.2). They are going to re-open that issue (or create a new one). Their suggestion in the mean time was to use html to send traffic-lighted reports back to the Office add-on. But then, of course, you lose all the neat benefits of the SASREPORT format (http://blogs.sas.com/content/sasdummy/2012/02/22/about-sas-report-format/). Thanks, --Q.

Quentin · ‎07-23-2012

Hi Milton, I knew you could specify an autoexec at the server level, but are you saying that you can specify an autoexec at the stored process level (i.e. a different autoexec for different stored processes)? I've been hoping to do that, but haven't been able to see how it could be done (I'm not an admin on the server, so may not be seeing all that is possible). So now I just start a stored process definition by %including an autoexec. I'm not seeing where I can specify an autoexec for a stored process in SMC: Thanks, --Q.

Online Status	Online
Date Last Visited	20m ago

Re: How to Reg on each row?! with Slope/Intercept saved out?!

Re: How to Reg on each row?! with Slope/Intercept saved out?!

Re: Report with 1000 days from now

Re: problem with ODS in SAS EG 8.3

Re: problem with ODS in SAS EG 8.3

Re: Create a catalog table

Re: Combine the coding on arrays in the same data step

Re: How to use a macro variable in a if else condition

Re: How to use a macro variable in a if else condition

Re: SAS macro in conjunction with PROC PYTHON

Re: SAS 9.4M8 and Git Integration

Re: VALIDVARNAME=V7

Re: How to Reg on each row?! with Slope/Intercept saved out?!

Re: sending emails from sas

Re: PROC COMPARE label attribute is missing

Re: Use of Infile and Input statements

Re: SAS macro in conjunction with PROC PYTHON

Re: send email +attach log file only in case of error or warning

Re: chart representing thestructure of data

Re: send email +attach log file only in case of error or warning

Re: Usage of macro variables in data step and table name

Re: If/where contains problem while merging

Re: Reporting with Excel SAS ADD-in

Re: Reporting with Excel SAS ADD-in

Re: Reporting with Excel SAS ADD-in

Re: Shield SQL Userid and Pwd

Re: RE: Keeping deleted data (in seperate database)

Re: RE: Keeping deleted data (in seperate database)

Re: RE: Keeping deleted data (in seperate database)

Re: Can you specify SAS invocation options for a particular stored pro...

Re: Excel VBA Stored Process with parameters

Can you specify SAS invocation options for a particular stored process...

Re: Excel VBA Stored Process with parameters

Re: Traffic lighting problems in Excel Add-In with tagsets.sasreport12

Re: autoexec code stored process

SAS Inner Circle Panel

SUGA

SAS User Groups

SAS Global Forum 2017

SAS Explore