@RPoumarede - Links to SAS Documentation in this article are broken, specifically in the sentence "And here is another one (from the SAS documentation) to mount a specific volume for the CAS Disk Cache and change its location."  ... View more

I believe in log-cleanup-find.yml and others the line "- host: sas-all" should actually be sas_all as defined in the sas_viya_playbook/inventory.ini.   Is that correct?   If we leave the default of sas-all the log-cleanup-find.yml playbook fails with the following:   PLAYBOOK: log-cleanup-find.yml ********************************************************************************************************************************************************************************************************* 1 plays in viya-ark/playbooks/log-cleanup/log-cleanup-find.yml [WARNING]: Could not match supplied host pattern, ignoring: sas-all   If I change log-cleanup-find.yml to have sas_all it finds all my hosts and completes: ... ok: [casWorker1] => (item={u'rusr': True, u'uid': 1000, u'rgrp': True, u'xoth': False, u'islnk': False, u'woth': False, u'nlink': 1, u'issock': False, u'mtime': 1677747600.0891082, u'gr_name': u'sas', u'path': u'/opt/sas/viya/config/var/log/log-20230131090000Z.zip', u'xusr': False, u'atime': 1677747600.076109, u'inode': 279195785, u'isgid': False, u'size': 22, u'isdir': False, u'ctime': 1677747600.0891082, u'isblk': False, u'wgrp': False, u'xgrp': False, u'isuid': False, u'dev': 64768, u'roth': True, u'isreg': True, u'isfifo': False, u'mode': u'0644', u'pw_name': u'sas', u'gid': 1000, u'ischr': False, u'wusr': True}) => { "msg": "/opt/sas/viya/config/var/log/log-20230131090000Z.zip" } META: ran handlers META: ran handlers PLAY RECAP ***************************************************************************************************************************************************************************************************************************** casWorker1 : ok=4 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 casWorker2 : ok=4 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 deployServices : ok=4 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 deployTarget : ok=4 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0   If this is correct each one of the .yml files above with sas-all may need to be changed to sas_all instead to match the sas_viya_playbook/inventory.ini file. ... View more

Hello, is this feature available in SAS Viya 3.5? This is present in the SAS Viya 4 CAS Reference documentation but is not documented for SAS Viya 3.5. ... View more

Hey, @StuartRogers excellent article I use it all the time. We also have to provide this Problem Note if the UPN does not match the SPN for 9.4 TS1M7. I thought it would also be a good thing to have on this page that they may need this hot fix if that is the case.   66937 - You see a "Kerberos failure" message after you set up Integrated Windows Authentication and single sign-on for SAS® 9.4M7 (TS1M7) ... View more

John,   it doesn't look like your procedure is complete in your example. See this techniques in processing in Hadoop paper, it has a few examples using proc sql;   https://support.sas.com/resources/papers/proceedings14/SAS033-2014.pdf    It has this sample code to write to hadoop using proc sql that might help;   proc sql; connect to hadoop (server=duped user=myUserID); execute (create table myUserID_store_cnt row format delimited fields terminated by '\001' stored as textfile as select customer_rk, count(*) as total_orders from order_fact group by customer_rk) by hadoop; disconnect from hadoop; quit;     ... View more