About ronan

ronan · ‎01-11-2021

@SASKiwi and @PaulHomes have given you comprehensive replies which should help you resolve the issue. As a side note, please consider using a low code interface to quickly retrieve information from SAS metadata rather than Data Step OMI requests which are preferably intended for batch programs. For running interactive requests on-the-fly, if you have a SAS Base (aka SAS DMS) available like SAS Base on Windows or on Unix/Linux using MobaXterm then you can very easily navigate in the Metadata object hierarchies with Metadata Browser : https://blogs.sas.com/content/sastraining/2012/06/12/using-metabrowse-to-find-metadata/ There is also a multi purpose (free) tool I'd strongly recommend, seamlessly integrated with the SMC : Metacoda Metadata Explorer Plugin https://platformadmin.com/blogs/paul/2012/08/metacoda-metadata-explorer-plug-in/ I am using it almost on a daily basis, this spares me a lot of time when looking around in the metadata repository.

ronan · ‎01-06-2021

Thank you, @ScottMcCauley . Of course, some metadata store localised, which means translated into non-English languages - user information. However, this situation doesn't occur systematically and most localised charsets have fixed-length (Single Byte) except - to the best of my knowledge - in Asia where UTF8 is required for Multi-Bytes characters (Hanzi, Kanji etc.). Therefore, knowing that SAS 9 with fixed-length charset (non UTF8) is rather the norm than the exception, I think that adjusting to this case could be very beneficial. Setting up a UTF8 SAS 9 session is quite demanding and implies in most deployments to configure another Logical Server only for this very purpose : this would drastically limit the scope of the tables generated by the Inventory report, which looks incredibly useful :).

ronan · ‎01-05-2021

Thanks for sharing the details. This looks promising, although the strong adherence to VA for rendering the results is still a pain point in my opinion. The doc specifies that Data Sets are created with UTF-8 encoding, thus preventing non utf8 SAS 9 sessions to load it, I guess. _ Would it be feasible in a future release to change the default UTF8 encoding with another fixed-length charset (Latin9 etc.) ? This would enable the comparison to take place within a standard SAS 9 session (proc compare ...).

ronan · ‎09-21-2020

Thanks for sharing. There is also the Multi Node Data Transfer mode which , although running in parallel, doesn't require SAS Embedded Process, only assuming the existence of a column to be partitioned in the source Data : https://documentation.sas.com/?docsetId=casref&docsetTarget=p12gi5eub04169n1x62tz74kvwt2.htm&docsetVersion=3.5&locale=en Highly effective on Hadoop/hive.

ronan · ‎09-14-2020

If you are sometimes switching from dual-monitor (e g on-site) to single screen desktop (e g Work From Home) then you might lose sight of the SMC or SDM (SDW) UI since these clients - Unix version - save the user screen coordinates into some hidden technical file (SMC => $HOME/.SASAppData/SASManagementConsole/9.4/app.smc). This in order to restore the client X11 UI at the same place next time it is launched. Cleaning up the files (app.*) shall harmlessly restore the centered position whether your Windows desktop has single or multiple displays.HTH

ronan · ‎08-31-2020

There is another way, by enabling ARM log files which requires to modify the Log4j SAS Workspace configuration (not an easy task). Using ARM logging, you can even drill down to the column level. https://support.sas.com/rnd/scalability/tools/arm/v9armlog.html The predefined reports installed with the SAS Environment Manager Framework Kit are the easiest way to go imho (these reports are based on ARM logging as regards Data access monitoring). Enabling full logging for Workspace Server sessions is usually not recommended : this consumes both computing ressources and storage. This said, if your SLA requires a high level of application tracing then the full log is inescapable.

ronan · ‎08-26-2020

Hi @briankinnebrew , Thanks for you answer and clarification. I confirm that the systemEvaluation is a standalone tool, and I plan to use it sometime in the future. This is a nice addition to the documentation or tools (SDW) already provided for upgrade. As regards the other collection of tools, I still don't see why they're provided with a strong adherence to VA on Viya only : generating static reports OOTB look a base-line feature, whether you are planning to migrate or not. Usually, you carry out the inventory task before installing the next platform, and this one might be Viya-based or not depending on its specific requirements. Moreover, with a programming-only deployment, VA is not installed though Viya (CAS) still is. I perfectly understand a new request feature takes time to be added. My comment are just aiming to help the PO & Dev team with the point of view of someone installing the best-of-breed analytics software available (SAS, namely 😉 ) . HTH. Ronan

ronan · ‎08-25-2020

Thanks for providing these tools. The pre-requisites are rather strict : it is assumed that VA on Viya is already installed and running to display the reports ; I was expecting a more standalone product like the SMU, for instance. Usually, the assessment analysis on the source platforme takes place before migrating or even before choosing to migrate towards a certain target. In my understanding , ex post analysis are needed only for migrating contents which has been already assessed; once the target platform has been specified, qualified and installed. - is it planned to have a version requiring only SAS 9 to run the analysis and display the results ( base-line HTML reports) ? - is an AIX version planned in addition to Linux and Windows ?

ronan · ‎07-24-2020

In theory, yes. The documentation for XCMD option says that "it can be restricted by the administor" meaning, this option is compatible with Restriction options at SAS Foundation level. https://go.documentation.sas.com/?cdcId=pgmsascdc&cdcVersion=9.4_3.4&docsetId=hostunx&docsetTarget=n02699r064oqccn19vblte8xzr8m.htm&locale=en $SASROOT/misc/rstropts/groups the restriction applies selectively upon the SAS session owner account's login or - better - primary group. the admin creates a specific SASV9.cfg file in the directory below with the option values set accordingly <primary group>_rsasv.cfg -XCMD -this file will take precedence over any SASV9.cfg file globally applied -if the option value (not the case, here) can also be changed during the sas session, the restriction applies and the change is refused Never tested. I am suprised this very option is compatible with restriction since it applies only for IOM server sessions.

ronan · ‎06-30-2020

Thanks for this video, I'll read the aforementioned papers. Basechar() and Kpropdata() functions are especially useful with SAS SPRE sessions on Viya when dealing with extended (European here) Charsets.

ronan · ‎06-22-2020

Thank you both for your help 😃, with the correct operator, FedSQL runs OK on SAS 9 and CAS as well.

ronan · ‎06-19-2020

Thanks for your code; however the code I have to migrate requires to filter the rows with a calculated column. The requirement was not clearly expressed, my fault. I ran your code in a SAS 9 session, adding only a WHERE clause before the GROUP BY, like this : proc fedsql ; create table mycars as select origin, priceType, avg(invoice) as avg_invoice from ( select *, case when invoice >= 0 and invoice < 30000 then 'affordable' when invoice >= 30000 and invoice < 60000 then 'need to think' else 'not my budget' end as priceType from cars ) as c1 where c1.priceType eq 'affordable' group by origin, priceType ; quit; Proc SQL accepts this kind of syntax, Proc FedSQL does not unfortunately (on SAS 9 at least): ERROR: Syntax error at or near "EQ" NOTE: PROC FEDSQL has set option NOEXEC and will continue to prepare statements.

ronan · ‎06-19-2020

Thanks for your reply, I gave this simple code as an example. Of course we can apply the SCAN function straight in the WHERE clause (If I follow you correctly) . Then how can we proceed when the calculated column is a more complex transformation, for instance coming from a CASE manipulation of values ? The following code is quite arbitrary, this is just an example : Proc SQL; select t.*, CASE WHEN scan(t.email,-1) EQ 'com' THEN 'COMMERCIAL' ELSE 'NON COMMERCIAL' as FLAGCOM from mytable where t.FLAG = 'SPAM' AND calculated FLAGCOM = 'COMMERCIAL' ; quit;

ronan · ‎06-19-2020

Hello Everyone, This is partially off-topic since Proc FedSQL goes geyond Viya, however my question might be especially relevant here since Proc SQL is not CAS-enabled (or, ist it ? in preproduction seems to work fine 😉 ) : /* Proc SQL with calculated column */ Proc SQL; select t.*, scan(t.email,-1) as MAILTLD from mytable as t where t.flag = 'SPAM' and calculated MAILTLD eq 'com' ; quit; How do we refactor this code on Viya using Proc FedSQL ANSI syntax ? I was thinking of correlated subqueries, something like /* Proc FedSQL correlated subquery - roughly sketched*/ Proc FedSQL sessref=mycas; select t.* from caslib."mytable" as t where t.flag = 'SPAM' and 'com' = ( select scan( v.email , -1) from caslib."mytable" as v where v.email = t.email ) ; quit; But, then I read in Proc FedSQL documentation : Note: Correlated subqueries are not yet supported on the CAS server. https://go.documentation.sas.com/?cdcId=pgmsascdc&cdcVersion=9.4_3.5&docsetId=proc&docsetTarget=p0d70hfuuzsq0tn1ndl5k4x9m56z.htm&locale=en What option do we still have ? Creating a second "outer" result set then merging with the "inner" query ?

ronan · ‎03-02-2020

There is no such thing as a (re-usable) audit trail of metadata changes over time. However, you can enable such a change capture database - at least for high level objects (ACE, ACT, User, Group) with SAS Environment Manager Service Framework Architecture reports. See for instance the Audit Reports (log forensic) : https://support.sas.com/rnd/emi/SASEnvMgr/EVSAF/SAS_Environment_Manager_Service_Architecture_Quickstart_9.4M5.pdf https://support.sas.com/rnd/emi/SASEnvMgr/EVSAF/Report_Center_Report_Listings.pdf This summary list is not 100% up to date with latest M6 release.

Online Status	Offline
Date Last Visited	a week ago

Re: Accelerating SAS9 to Viya Migration with Log Intelligence

Installing SAS 9.4 for Linux in WSL2

Re: Accelerating SAS9 to Viya Migration with Log Intelligence

Re: Kubernetes Storage Patterns for SASWORK – part 1

Re: Accessing SAS Content with FILENAME FILESRVC in SAS Viya

Re: Now I see you, now I don’t. How to prevent users from seeing other...

Re: Now I see you, now I don’t. How to prevent users from seeing other...

Re: SAS Viya Administration documentation PDFs

Re: Data Encoding Impacts in SAS Viya

Re: can we capture any events (or run a script) at compute pod end?

setting sas.logon.initial password in sitedefault.yaml during SAS Viya...

Introducing the SAS Container Runtime Batch Agent

Fixing Broken Hearts and Macros: A Character Variable Check

Data Factory Inventory Mastery: Optimizing Stock with Enterprise Sessi...

Building Dynamic Lineage: From Factory Floor to Viya’s Control Room

Re: SAS Viya 4 storage from Red Hat OpenShift Data Foundation

Re: SAS Bowl XXXI, SAS Support Communities

Re: SAS Bowl XXVII, CAS Actions

Re: Join our upcoming live workshop on SAS Viya 4 Administration

Re: Why is SAS Viya single instance only?

Installing SAS 9.4 for Linux in WSL2

Re: Enforce Row Level Access

Re: Enforce Row Level Access

Re: Libname with AUTHDOMAIN option does not work as intended

Re: Using SAS 9 Inventory to Validate an Upgrade or Migration

Re: Using SAS 9 Inventory to Validate an Upgrade or Migration

Re: Parallel data load to SAS Viya

Re: SMC/SDM Launching on Unix

Re: Parsing SASAPP_WorkspaceServer Logs for table names

Re: The SAS 9 Content Assessment Tool

Re: The SAS 9 Content Assessment Tool

Re: Is it possible to limit xcmd to certain users?

Re: See All of Your Characters in SAS® Studio

Re: Migrating Proc SQL code with calculated column to Proc FedSQL

Re: Migrating Proc SQL code with calculated column to Proc FedSQL

Re: Migrating Proc SQL code with calculated column to Proc FedSQL

Migrating Proc SQL code with calculated column to Proc FedSQL

Re: Track changes in SAS metadata