I have been a SAS admin of EBI/Grid environments for 7+ years now, but just recently have been pulled on to assist in administering a SAS Financial Crimes/AML environment.  I'm still learning a lot about this custom solution, the data model, all the macros/stored processes it uses, etc.  There have been various contractors involved in custom development over the past couple years, and I'm having to pick up the pieces and also differentiate between what is custom and what is standard.   We have a question from some users pointing out that the TIN of a Subject is showing up incorrectly in the data grid (on the Subjects tab of the Case), but shows up correctly under the Alert and Report that are associated with the case.   Does anyone know how the data grid for the Subjects tab of a Case is generated?  Is is a stored process, macro code or something else entirely? ... View more

I'm mainly a SAS admin and developer. I have some code provided by a statistician that runs in an Oracle database.  I'm trying to figure out how to convert to SAS syntax (with PROC SQL).  My problem is that I don't understand the PERCENTILE_DISC function enough to convert to relevant SAS syntax. Anyone able to help?   select PARTY_NUMBER, Min (CREDIT_CT) as CREDIT_CT_Min, PERCENTILE_DISC(0.01) WITHIN GROUP (ORDER BY CREDIT_CT ASC) as CREDIT_CT_P1, PERCENTILE_DISC(0.05) WITHIN GROUP (ORDER BY CREDIT_CT ASC) as CREDIT_CT_P5, PERCENTILE_DISC(0.10) WITHIN GROUP (ORDER BY CREDIT_CT ASC) as CREDIT_CT_P10, PERCENTILE_DISC(0.25) WITHIN GROUP (ORDER BY CREDIT_CT ASC) as CREDIT_CT_P25, PERCENTILE_DISC(0.5) WITHIN GROUP (ORDER BY CREDIT_CT ASC) as CREDIT_CT_Median, PERCENTILE_DISC(0.75) WITHIN GROUP (ORDER BY CREDIT_CT ASC) as CREDIT_CT_P75, PERCENTILE_DISC(0.95) WITHIN GROUP (ORDER BY CREDIT_CT ASC) as CREDIT_CT_P95, PERCENTILE_DISC(0.99) WITHIN GROUP (ORDER BY CREDIT_CT ASC) as CREDIT_CT_P99, Max (CREDIT_CT) as CREDIT_CT_Max, Min (DEBIT_CT) as DEBIT_CT_Min, PERCENTILE_DISC(0.01) WITHIN GROUP (ORDER BY DEBIT_CT ASC) as DEBIT_CT_P1, PERCENTILE_DISC(0.05) WITHIN GROUP (ORDER BY DEBIT_CT ASC) as DEBIT_CT_P5, PERCENTILE_DISC(0.10) WITHIN GROUP (ORDER BY DEBIT_CT ASC) as DEBIT_CT_P10, PERCENTILE_DISC(0.25) WITHIN GROUP (ORDER BY DEBIT_CT ASC) as DEBIT_CT_P25, PERCENTILE_DISC(0.5) WITHIN GROUP (ORDER BY DEBIT_CT ASC) as DEBIT_CT_Median, PERCENTILE_DISC(0.75) WITHIN GROUP (ORDER BY DEBIT_CT ASC) as DEBIT_CT_P75, PERCENTILE_DISC(0.95) WITHIN GROUP (ORDER BY DEBIT_CT ASC) as DEBIT_CT_P95, PERCENTILE_DISC(0.99) WITHIN GROUP (ORDER BY DEBIT_CT ASC) as DEBIT_CT_P99, Max (DEBIT_CT) as DEBIT_CT_MAX, Min (PCT_OUT) as PCT_OUT_Min, PERCENTILE_DISC(0.01) WITHIN GROUP (ORDER BY PCT_OUT ASC) as PCT_OUT_P1, PERCENTILE_DISC(0.05) WITHIN GROUP (ORDER BY PCT_OUT ASC) as PCT_OUT_P5, PERCENTILE_DISC(0.10) WITHIN GROUP (ORDER BY PCT_OUT ASC) as PCT_OUT_P10, PERCENTILE_DISC(0.25) WITHIN GROUP (ORDER BY PCT_OUT ASC) as PCT_OUT_P25, PERCENTILE_DISC(0.5) WITHIN GROUP (ORDER BY PCT_OUT ASC) as PCT_OUT_Median, PERCENTILE_DISC(0.75) WITHIN GROUP (ORDER BY PCT_OUT ASC) as PCT_OUT_P75, PERCENTILE_DISC(0.95) WITHIN GROUP (ORDER BY PCT_OUT ASC) as PCT_OUT_P95, PERCENTILE_DISC(0.99) WITHIN GROUP (ORDER BY PCT_OUT ASC) as PCT_OUT_P99, Max (PCT_OUT) as PCT_OUT_Max from my_table where tran_month <= add_months(to_date('20170901', 'YYYYMMDD'), -1) and tran_month >= add_months(to_date('20170901', 'YYYYMMDD'), -12) group by PARTY_NUMBER order by PARTY_NUMBER; ... View more

We have numerous flows (150-200) that are triggered by all kinds of triggering events.  Recently I saw some weird behavior where certain flows which are scheduled to run using the standard Daily@Sys calendar (varying times of the day) just simply did not start. There is no record in Flow Manager showing that they even tried (i.e. no history).  They've been running fine for a long time, but simply did not run on a given day. Then they ran fine the next day?   Does anyone know how to troubleshoot/investigate?  I'm guessing there are relevant logs somewhere within the PM product install directory, but I'm not as familiar with this product as I am with SAS products.   My first hunch is that maybe there's a load/server limit somewhere?  I would kind of doubt it, though, since the latest instance had to do with a job at 12:05 am, and we do not have many jobs scheduled for that time.   In case it's relevant, we are on SAS 9.4M4, Platform Suite 9.1.3, Linux x64 servers in a grid environment.   Thanks! ... View more