About _Dan_

_Dan_ · ‎08-17-2018

Thanks for that, and it did work - almost. A curve ball I've just found is that the Style is defined within their code: proc template; define style TheStyleName; parent = Styles.fancyprinter; However, when referring to the style... WARNING: Could not locate style reference 'TheStyleName.colors("docfg")'. As this reference isn't explicitly set through the proc template, could it be that there's another Style with the same name that does contain those colours?

_Dan_ · ‎08-17-2018

Well, I 'run' the new platform, I've been asked to migrate people off an older platform onto this one. I'm taking it step by step, macros, formats etc as and when we come across them. The original code works on the old platform, so, like the macros, formats, all I need/want is a way to export the style. Is that possible or not? I am going to assume the worst that there's either no original style code, no original css, and the analysts running the code had inherited it without knowing what the exact style information is.

_Dan_ · ‎08-17-2018

Hi, I'm migrating some SAS code between two distinct SAS platforms. There's a section where I need a style for an ODS output. I expect this style will either have been hard coded or imported from a css file. Assuming I can't find either the original style code or css, is there an export I can use that'll produce a file for me that I can import into the target platform? Thanks in advance Dan

_Dan_ · ‎08-01-2018

I've found the resolution: superq. Here's the end result. %let cmd = ssh -o StrictHostKeyChecking=no %sysfunc(quote(%sysfunc(scan(&server.,&i.,|)))) "find &dir. -type f -exec stat -c %nrstr('%n|%y|%x|%s|%U|%u|%G') {} \%nrstr(;)" > &projDir./Data/&fname.Logs_%sysfunc(scan(&server.,&i.,|)).txt; systask command "%superq(cmd)" nowait;

_Dan_ · ‎08-01-2018

Thanks for your reply & that's certainly a good option. I will need to consider it as a "last resort" of sorts until I've exhausted any options on coding it directly into the SAS Macro.

_Dan_ · ‎08-01-2018

Hi, A brief description of my intent: I'm scanning file systems across several Unix servers. The Unix command is created dynamically in a Macro and used to be submitted via 'call systask'. I want to submit the statements in parallel, so now I'm going to use 'systask command nowait'. As I'm no long using the data _null_ with call systask I'm now building the Unix command in a fairly straightforward (but admittedly messy) %let statement. The command works, however, the Unix command contains the percent % symbol and so the macro processor is trying to resolve things that don't exist. I know I can use %nrstr() to resolve this (that's what I did with call systask) but this is not masking anything within the %let / systask command statement. It's a simple loop macro, but here's the line that builds the Unix command: %let cmd = ssh -o StrictHostKeyChecking=no %sysfunc(quote(%sysfunc(scan(&server.,&i.,|)))) "find &dir. -type f -exec stat -c %nrstr('%n|%y|%x|%s|%U|%u|%G') {} \%nrstr(;)" > &projDir./Data/&fname.Logs_%sysfunc(scan(&server.,&i.,|)).txt; systask command %sysfunc(quote(&cmd.)) nowait; When it's compiled It looks like this: ssh -o StrictHostKeyChecking=no "servername" "find /dir1/dir2/dir3/ -type f -exec stat -c '%n|%y|%x|%s|%U|%u|%G' {} \;"" > /dir1a/dir2a/dir3a/filename_servername.txt This code may send shivers down the spine of more seasoned coders - I have got myself in a rut because I've had to try all sorts of different methods to get this to work, so the code is admittedly not as efficient or tidy as I'd like. Any help regarding the forcible masking of the percent symbols is appreciated. Dan

_Dan_ · ‎02-28-2018

Thanks for that, I'd been using %if %then %do for a long time but wanted to use IFC more after seeing (and using) some very good examples. Looks like that's just not possible when calling another macro function but everything else works without issue. Shame, it's the only time I ever needed to use %goto as well. Cheers.

_Dan_ · ‎02-28-2018

Approach is 50% programmatic and 50% cosmetic. I've replaced it with a %let error = 1 and then I query this later. There's more than one of these statements so I just let them all run and now I query the outcome afterwards. %goto is now called by its own %if error = 1 %then...

_Dan_ · ‎02-27-2018

Hi there So basically everything works apart from the %goto. I've had various methods of running this little checker, usually the end result would be a %let statement instead of this %goto. That works fine. Essentially, the only problem is the %goto. There's no need for double %% because I'm not trying to escape anything (that's not what NRSTR is doing here). In fact, I want the %GOTO to work, and in theory it does, but SAS is seeing it outside of the context of it being inside of a %macro. I could literally write this statement anywhere else right now and it would work, just not inside of the %NRSTR. I've also tried UNQUOTE around the %goto bit but EGuide acts very strange - clearly it's causing a mismatch of some sorts and EGuide has no idea how to compile and run the entire macro.

_Dan_ · ‎02-27-2018

This entire process runs within a %macro, my understanding is fine. %NRSTR is affecting the compilation of the %goto.

_Dan_ · ‎02-27-2018

Here's my code: %sysfunc(ifc(%sysfunc(libref(LIBNAME)) ,%nrstr(%put ERROR: LIBNAME Libref does not exist.; %goto exit;) ,%nrstr(%put NOTE: LIBNAME Libref exists.;) )); My issue is of course that the %NRSTR is causing an issue with the %goto statement: ERROR: The %GOTO statement is not valid in open code. %NRSTR must exist to allow the 'ifc' to properly run the true/false statements. Without %NRSTR, ifc executes all of the statements regardless of the outcome. %unquote, %bquote %nrbquote %str etc etc have all been used to varying degrees of failure. Any idea how I break that portion of the code out of the %NRSTR to allow the %GOTO to work?

_Dan_ · ‎02-21-2018

Thanks Simon, you're right of course, but it just forces an ERROR: when the server has been terminated and I was looking for a method that would maybe prompt a Boolean response, or would be handled without forcing an ERROR: into the log. At this time, I'm just assigning a LIBNAME (that also returns an ERROR: if the server is down) and I then use an IFC statement to query the existence of the libref, which then allows me to conditionally set a macro variable as to the success or failure of the server startup. I wonder, is there a standard macro variable like &syserr, &sysrc etc that'll tell me the result of the PROC LASR CREATE once it's completed? As I'm not in a position to 'break' the CREATE procedure, I wouldn't be able to test the sort of response codes I could expect should the procedure fail or complete properly.

_Dan_ · ‎02-21-2018

Fair enough, it turned out to be one of the SAS hotfixes that was causing the issue with communicating via the Impala engine for us.

_Dan_ · ‎02-19-2018

Hi, did you get a resolution to this? We're on 94_M3, a recent Cloudera patch to 5.12.1 broke some fundamental code on the Hadoop side. Cloudera patched that, and now our queries are limited to 1000 rows per commit. Then, installing upgraded Jars and hotfixes has resulted in the Impala connection returning this error, even if you just try to view a table in EGuide.

_Dan_ · ‎02-15-2018

Hello there, I've written Base & Macro code to obtain from Metadata a list of LASR instances I'd like to start in anticipation of an outage this weekend. Whilst I don't doubt this will work, I do like to throw caution to the wind and program for all eventualities - such as the Macro failing half-way through, needing a restart, and then failing again because it tries to start a server that's already started. So, a very high level view of the code is this: - Obtain Metadata list of servers. - Define variables like Port, Tag, LogDir - ????? - Start Server - Check Server status ????? is the missing piece - this is where I'd like to check the server is active prior to trying to start it up. Is there a decent way of doing this, one that either tells me the server is alive, or, one that handles an ERROR: properly and doesn't kill the SAS code (sort of like On Error Goto Next in VBA). i'd like to do this in SAS code to remove any issues that may come with the permissions and governance of the Unix file system. Thanks in anticipation, Dan

Online Status	Offline
Date Last Visited	‎05-06-2021 08:23 AM

Re: How do I retrieve ResponsibleParties for Report.BI Objects

Re: Security Report with SAS-Autocall Macros mdsec**

Re: Security Report with SAS-Autocall Macros mdsec**

Re: Excel DateTime to SAS DateTime - have code - not working

Re: Security Report with SAS-Autocall Macros mdsec**

Re: Security Report with SAS-Autocall Macros mdsec**

Excel DateTime to SAS DateTime - have code - not working

How do I retrieve ResponsibleParties for Report.BI Objects

Re: Counting concurrency and grouping per event

Counting concurrency and grouping per event

Re: Security Report with SAS-Autocall Macros mdsec**

Re: Security Report with SAS-Autocall Macros mdsec**

Re: Security Report with SAS-Autocall Macros mdsec**

Re: Exporting a style from one platform to another

Deployed job cannot start, no log created. DI Studio shows "unable to ...

Re: Exporting a style from one platform to another

Re: Exporting a style from one platform to another

Exporting a style from one platform to another

Re: Sending a Unix command and masking the percent % sign

Re: Sending a Unix command and masking the percent % sign

Sending a Unix command and masking the percent % sign

Re: How to break out of %NRSTR to execute a %GOTO statement

Re: How to break out of %NRSTR to execute a %GOTO statement

Re: How to break out of %NRSTR to execute a %GOTO statement

Re: How to break out of %NRSTR to execute a %GOTO statement

How to break out of %NRSTR to execute a %GOTO statement

Re: Programmatically assess whether a LASR server is active

Re: Segmentation violation error

Re: Segmentation violation error

Programmatically assess whether a LASR server is active