I actually am about to employ SAS follow-the-sun support on this in about 20 minutes but was wondering if there's anything I missed. Our server admins and information security folks are asking us to define potential exposure to the zero-day log4j2 vulnerabilities discovered recently. We've shut down anything on our SAS 9.4 mid-tiers. We think we're ok on Viya. But we utilize CI360 as SaaS and are uncertain if there is anything on SAS's end that has been done or anything that CI360 might be able to do via the direct agent to put itself in harm's way. Didn't see anything on the security bulletins page about this, so I thought I'd ask here.  I do have an open track on this: SAS 7613479191, but we didn't hear anything before the end of the day so I'm going to wade into after hours support, because security is still waiting for our answer. It looks to me like Environment Manager and a couple of mid-tier products might need some adjustments. But I only play a SAS Admin on TV. If anyone knows anything or has done anything, I'm all ears. Our 9.4 M6 environments are on Linux. Obviously I can get more product specific but I have no idea if this is even a point of concern and thus no idea how to guide our admins who are usually all over things at the OS level but often unsure of when SAS is using it's own version of things. I work at a non-profit so we're often wearing many hats. Chris ... View more

Wise and sage Wisepeople and Sages,   I have been asked by my supervisor to "do something with Python" because he believes I need to diversify my skillset. I have tried to explain that SAS in combination with what I can do from the UNIX command line is extraordinarily versatile without forcing me to go deep into the syntax of half a dozen different languages. But he insists, so without a practical entry point, I ask of you, are there places where you defer to Python as a solution for data management/integration in addition to your SAS powers?   Chris ... View more

I'll admit that I'm a little rusty on my use of the macro facility, so it's entirely possible that I'm missing something fundamental here, but here's the scenario - I'm trying to generate a dynamic where clause in a proc sql statement based on the values selected from a multiple values prompt in a stored process, including the "all possible values" option. In this particular case they are values based on a geographical hierarchy. If the user selects "all possible values" it moves on. If not, depending on if one or more values is selected, it adds an "and" phrase to the where clause with the appropriate in operator statement. Here's the syntax I went with at first:     %if  &designationregion. = _ALL_VALUES_ %then %do;%end; %else %do;   and d.designationregion in ( %if &designationregion_count. = 1 %then "&designationregion."; %else %do i=1 %to &designationregion_count.; "&&designationregion&i." %end;   ) %end;   Everything was working splendidly until I happened to choose a value for the prompt with the word "and" in it. For example Mexico and N Central America. If this is either the only value or the first in a series of values selected the SP errors out with this: ERROR: A character operand was found in the %EVAL function or %IF condition where a numeric operand is required. The condition was: &designationdivision. = _ALL_VALUES_ ERROR: The macro SPTEST will stop executing. So if values selected are like so: Mexico and N Central America Brazil it gets fussy. But if values are like so: Brazil Mexico and N Central America everything is lovely. This appears to happen because of the word "and" interfering with its thinking. I thought I needed quotes around the macro variable being resolved so I tried this syntax which adds quotes around the first occurrence of the &designationregion. macro variable.   %if  "&designationregion." = _ALL_VALUES_ %then %do;%end; %else %do;   and d.designationregion in ( %if &designationregion_count. = 1 %then "&designationregion."; %else %do i=1 %to &designationregion_count.; "&&designationregion&i." %end;   ) %end; This does in fact solve the problem and the error no longer occurs, but now, when I select "all possible values" from the prompt, the query returns nothing and I want instead for it to return everything. So I'm clearly missing something in how to properly get it to ignore the and AND properly compare against the default _ALL_VALUES_ value. We're running all of this in SAS 9.4 on Linux but my Spidey sense tells me that it's not versioning, but syntax that is at the heart of my problem.   So I ask you, wise and powerful onlookers, where am I going wrong? Chris   ... View more

LOOOONG time lurker, first time poster.   We run SAS 9.4 on a Linux box and use Platform LSF to manage our scheduled jobs. Permissions are being set on datasets created by scheduled jobs with a different UMASK (0022) than when I create them in EG (0002), even though my user owns the process for the scheduled job. We keep running into this when a dataset is first created by the scheduled job because group write privileges are missing and we have to manually update the permissions.   I can't find anywhere in the Config directory where umask is being set explicitly by the invoked SAS session. I also can't find anywere that's explicitly setting it in the LSF directories. I suspect it is getting the UMASK from an environment variable somewhere or by referencing a profile that isn't of the user themselves.    Can anyone help me unmask the masked man who is masking the UMASK?   Chris Befuddled Data Monkey ... View more