About DonH

DonH · ‎07-14-2013

Another possibility is the data that you are reporting on has no obvservations. In that case the reporting procedure will produce no output. I have a macro that I use to make sure that output is always produced. Check out my blog entry on this for the details: http://hcsbi.blogspot.com/2011/04/this-page-intentionally-left-blank.html

DonH · ‎04-17-2013

Sorry, left out the coalescec function (which returns the first non-blank/non-missing argument): %global _odsStyle; %let _odsStyle = %sysfunc(coalescec(&_odsStyle,sasweb));

DonH · ‎04-17-2013

You could use the request init facility that runs the code in the specified file before every stored process and just add something like this to the program: %global _odsStyle; %let _odsStyle = %sysfunc(&_odsStyle,sasweb); which will leave any provided value alone, but if none is provided it will set it to (in this case) sasweb. Just change sasweb to whatever your desired style is.

DonH · ‎11-01-2012

You will also need to make sure that your stored process server is set up so it has a SMTP mail server defined. See for example: http://support.sas.com/documentation/cdl/en/hostunx/61879/HTML/default/viewer.htm#email.htm This is for Unix for 9.2, but it is pretty general. You can also check out the online doc for the filename statement - specifically the email access method for details. Note that in 9.3, you can control/define all the settings in your program (in your case, your stored process). But before 9.3, some of the options need to be invocation options and so they will need to be added to the start up options for your stored process server (presumably by your SAS administrator).

DonH · ‎09-27-2012

Thx Cynthia. The link provided exactly the code I needed. And it was much cleaner than the examples I had found that used ODS PDF TEXT= to write raw PDF markup.

DonH · ‎09-27-2012

If you are creating stored process server sessions, the other option is to take advantage of the SAVE_ convention for saving macro variables from one request to the next one. This only works if you are using sessions. Basically what the server does is at the end of the request, it saves all the macro variables whose name begin with SAVE_ (not case-sensitive) and then when a new request reconnects to the session, it loads the macro variables back so they are available. This is a nice way to save state without having to embed values in the URL as name/value pairs.

DonH · ‎09-27-2012

Correct Cynthia, I don't want to have to (and, in fact, really can't) write code for each destination. The primary issue is two-fold. First, the links won't work unless I include the server name and port in the URL. Not hard to do assuming that the WIK has been set up to export _srvName and _srvPort to macro variables. But the bigger issue is that any click on a link in the document requires a new login. I figured the easiest way to avoid that frustration for the user was to just disable the links. What I suppose I will look into now is getting rid of the awful looking blue box around the cell with the link in the PDF version. The RTF and ExcelXP versions have no indication until you hover over the cell that it is a link. If I could do that for the PDF destination, that is probably a reasonable compromise. I found some posts dating back a few years on how to do that. But I figured before trying them out (and doing a little more research to see if there is a better way in 9.3 (the posts I found were about V8 and V9.1.3), I'd see if I could just suppress the URL first. Thanks for the quick reply.

DonH · ‎09-27-2012

I have a program (a stored process actually), that generates html, pdf, rtf and excel output. Here is a code snippet (really pseudo-code) that illustrate the technique: ods html .... ods pdf ..... ods rtf.... ods tagsets=ExcelXP ..... proc report .... call define (_col_,'url','the url') ods _all_ close; The way this works is that the html output is sent to the user's browser and the other output is written to a temporary location. At the bottom of the output I use the ods html text option to generate hyperlinks to allow the user to download the report (without rerunning any code) for the selected destination. But when the report contains, for example, drill down links, I don't want the urls to be active for the non-html destinations. So the question is whether there is an option or capability (perhaps via proc template) to disable the url capability for the HTML, PDF and ExcelXP destinations. TIA for any insights or suggestions.

DonH · ‎08-28-2012

Since I work for multiple clients, I don't have a single standard. I try to minimize what it does and typically limit it to defining librefs, filenames, updating the fmtsearch or sasautos option. It looks like you are trying to define macros. If so, I would use the SAS autocall facility to define the path to my macros. And I would use the insert or append options so as to make sure to not remove anything defined in the autoexec for the stored process server itself. Here is a link that talks about the insert and append options: http://www.sascommunity.org/wiki/Dynamically_Insert_and_Append_SAS_Format_and_Macro_Libraries_within_a_SAS_Program

DonH · ‎07-28-2012

Many thanks Paul. This has been a great exchange and you've given me all the info I will need. The point about _metaPerson being unique is a nice nugget that I will have to stash away. I have a couple of tools that use _UserName (for descriptive info) and I suspect that I should be using _metaPerson instead.

DonH · ‎07-28-2012

Paul, Thanks for the reply and the followup. Thanks for the _metaperson reminder. I will check into it. Not sure however that it is an option since, I believe, two users can have the same value. In answer to your other question, this is code that will be run nightly (as part of a job stream that will have the credentials defined) and it is used as the input to a process to build a complex table structure for a work flow process that will be managed by a set of stored processes. So I really need a unique key. But perhaps one of the object id values can be used. Definitely something for me to check into. And there are no custom repositories and I don't need to get indirect groups. So this should work (I've marked you answer above as correct, BTW). Also, good point about the variability of _metauser. The current project is Unix, so it is not an issue. I usually handle this by defining a very simple utility macro to handle this, e.g.,: %macro metaUser; %lowcase(%sysfunc(coalesceC(%scan(&_metauser,2,\),&_metauser))) %mend metaUser; and I simply use %metauser instead of &_metauser.

DonH · ‎07-28-2012

Assuming my assumption about where to get the value that becomes the value of the _metauser macro variable is correct, I think it is simpler that what I described above. Here is a SQL query that I think gives me what I need: proc sql; create table metaUser_Groups_Crosswalk as select scan(logins_info.Name,2,'.') as MetaUser, groupmempersons_info.memName as UserName, groupmempersons_info.Name as GroupName from logins_info, logins, groupmempersons_info where logins_info.id = logins.objid and logins.keyid = groupmempersons_info.memid ; quit; This does drop users with no external id, but for my current use case that is not an issue. So Paul, can you comment on whether this looks right to you?

DonH · ‎07-28-2012

Thanks Paul. That macro certainly creates a lot of output information. I thiink I have figured out what datasets I need to use. However I am frankly making a guess at the the value that will become _metauser and would apprreciate your input. I think that I need the value of Name from logins_info (actually a parsed value because the format appears to be be "Login.&_metauser.xx" where xx is a number). I would need to use the ID field to match to the logins table (on objid) to get the keyid field that I can then match to the grpmems table (which appears to be the crosswalk of id of groups/users) on memkeyid. Then I would have to navigate comparably to get the group name. If you can confirm that the Name field in logins_info is where I will get the value that the stored process will see as _metauser, I'd appreciate it. And I agree on a metadata forum. I will figure out where/how to suggest that here. Thanks, Don

DonH · ‎07-27-2012

This is probably more a metadata server question. But since there is no metadata group, and the context of what I need to do is the Stored Process server, here is my question. I need to create a program that queries the metadata to provide a complete list of all the users and their assigned groups. The output data set should contains three variables: the group name the user display name the user metadata id (i.e., the value that is &_metauser in a stored process). I have found a bunch of examples on support.sas.com that give me the group and display name; or the group name and external login. I have tried to reconcile the various programs to give me a data set with all three of the above variables. Note that this program will be run on a nightly basis to just extract what groups a user belongs to. I then need to use that in a stored process where I know who the current user is (i.e., &_metauser). Does anyone know of a way to do this?

DonH · ‎07-27-2012

There is an option that you can set in the metadata to specify the name of a program to run before each stored process. You can also define a program to run after the completion of each stored process. You can also define such programs at the session level. I don't have 9.2 anymore, but here is how you do it in 9.3. And I believe it is the same in 9.2. Note that this was a new feature added in 9.2. Login to SAS Management Console On the Plug-Ins tab, expand Server Manager Expand the name of your App Server (e.g., SASApp) Right click on the appropriate logical stored process server Go to the Options tab Click the Set Server Properties button Select the Request tab Define the path for the programs to run before (and/or) after each stored process I use this almost all the time to set autocall libraries, issue libnames based on the user, etc. All the macro vars that are available to your stored process are available to the program that is run before the stored process, as is the user id (i.e., &_metauser). So you can even do user specific things. Note however that what you put here run before EVERY stored process. So don't overload it.

Online Status	Offline
Date Last Visited	‎04-05-2024 10:32 PM