About PaulHomes

PaulHomes · ‎03-23-2018

No problem. Great to hear you got it working. If this was a process that used to work then I'd recommend looking into what changed that broke it and why it was changed. This is in case 1) the previous logins and memberships were slightly different and 2) is there a likelihood the changes will be repeated and break it again.

PaulHomes · ‎03-23-2018

I would ask how is the SAS process that uses that autoexec being started and which operating system identity (and SAS metadata identity) is launching it? Is it a metadata aware client application (like SAS Enterprise Guide) or a simple batch or DMS SAS process? The authdomain= option on the libname statement is used to look up any available credentials in that auth domain for the current SAS metadata identity. Your autoexec is using macro variables for them so are you sure the macro variables are being resolved (look in the SAS log). The libname statement authdomain option searches for logins for that auth domain through the identity hierarchy for the current SAS metadata identity: the user, the users direct groups, the users indirect groups, and the implicit groups. Often for database connections the credentials are stored in a group and the user is made a member of the group so that they have access to the shared credentials. I would suggest you look through the groups to see if any have logins for those authentication domains and see if the user that is launching the SAS process is a member of those groups. If you can post the SAS log (suitable sanitized) it would make things easier.

PaulHomes · ‎03-22-2018

You could also consider using proc metadata to get the XML in a file and then process it using other tools/languages.

PaulHomes · ‎03-22-2018

What is the specific problem you are having with auth domains? What are you trying to do when you get your error message? I think of auth domains as a tagging mechanism - they are used to tag which credentials/logins can be used with which servers. If you look in SAS Management Console you can find them used on server connections (e.g. Server Manager > SASApp - Logical Workspace Server > SASApp - Workspace Server > Connection: SASApp - Workspace Server > Properties > Options tab) and logins (e.g. User Manager > SAS Demo User > Properties > Accounts tab). Credentials/logins for the DefaultAuth authentication domain, whether stored and fetched from metadata, or captured from user login prompts and temporarily stored in memory, can be automatically used to connect to servers tagged with the same DefaultAuth auth domain. With other authentication domains (e.g. OracleAuth) this is commonly used for storing credentials in metadata to connection to databases. The name has no specific meaning for connections and logins other than to help admins know which is which. Good alignment of authentication domains can make for easier administration and a good user experience. For more info see the About Authentication Domains and Manage Authentication Domains sections in the SAS® 9.4 Management Console: Guide to Users and Permissions. You can view and edit the list of available auth domains by right mouse clicking over Server Manager or User Manager in SAS Management Console and selecting the Authentication Domains menu item. You usually also have the opportunity to add new auth domains wherever you need to specify them. If you want to see where auth domains are used then one way to do this is to use our free Metacoda Metadata Explorer plug-in. By searching for all auth domains in metadata and selecting one, the Associated Objects tabs will show which servers and logins are in that auth domain (see screenshot below). The next release of the Metacoda Plug-ins will have a new Auth Domain Reviewer plug-in which will make this info easier to find.

PaulHomes · ‎03-21-2018

I just tried it and ValidateServer works for me with SAS 9.4 M5 on Linux. Mine is a new install rather than an upgrade from 9.4 M4 etc. Are you running ValidateServer on a server or a client? I have occasionally found (with clients) that an upgrade from an earlier maintenance sometimes fails at the last step and doesn't update the SASVersionedJarRepository (VJR) cache. Perhaps you have class loading issues because of that? I usually notice it when SAS Management Console wont start - see https://communities.sas.com/t5/SAS-Data-Management/I-can-t-Open-SAS-Management-Console-amp-SAS-Data-Integration/m-p/399399/highlight/true#M12138 Are you able to run SAS Management Console on the same machine? If not, then it might be a VJR cache issue and you could look at renaming/deleting /opt/sas94m5/sashome/SASVersionedJarRepository/eclipse/com.sas.app.launcher.cacheFile and letting it get recreated on-demand. I have only ever done this on a client machine and not a server. I imagine you may want to schedule some down-time and service restarts if you try it on a server.

PaulHomes · ‎03-13-2018

Sounds like you installed it in the root file system (you have no /data mount point listed) and maybe filled it up (my basic SAS Viya 3.3 install is 26G). Looking at your df output it looks like / is just for the operating system and you have /opt/SAS, /db_data and /sastmp as large storage volumes for SAS software, data, and temporary files perhaps? I would get your storage admins to create a suitably sized /data mount and move the SAS install onto that or re-install (if required) to fit with your original storage plan.

PaulHomes · ‎03-13-2018

It looks like your 40G root file system (/) is full. Have a look and see what is consuming the space. I see that the 50G /opt/SAS is practically empty. I'm guessing that's where SAS Viya was supposed to be installed? Was it installed in the root file system instead?

PaulHomes · ‎03-13-2018

It looks like a disk full error. What do you see run you run df -h?

PaulHomes · ‎03-12-2018

From the SAS Object Spawner log fragment you posted it looks like your SAS Workspace Server is most likely configured for SAS Token Authentication using the sassrv account and that the sassrv account has since been disabled and so the sasdemo identity cannot use that workspace server. I would suggest you start by re-enabling the sassrv account in the host operating system (or domain). Alternatively revert the SAS Workspace Server definition to username/password, restart the SAS Object Spawner, and let the sasdemo identity launch a workspace server using its own identity. Of course, if you decide to reconfigure the SAS Object Spawner you should first investigate why it was configured for SAS Token Authentication (there can be very good reasons for doing this) and who and what may be disrupted if you change it.

PaulHomes · ‎03-07-2018

If you need to do it programmatically then you can use the SAS Open Metadata API to find the objects with the appropriate filter criteria and then delete them. For a manual approach in SAS Management Console, you could try using the Search Tab. You can filter based on type, folder, and date, and then shift/control-click-select a range (or Control-A for all), right-mouse-click and delete the selected items.

PaulHomes · ‎03-07-2018

I was curious so I tried it out with the RollingFileAppender FileNamePattern value in a SAS 9.4 M5 Workspace Server logconfig.xml and it seems to work (even though it is not documented). Probably best to ask SAS tech support if it is supported and what SAS versions it works with.

PaulHomes · ‎03-07-2018

Hi Jan, I see that documentation for SAS ESP 4.3/5.1 and SAS DataFlux Data Management Server 2.6 have examples of the form %S{OSENV.env_var_name} in their logging XML - e.g. https://support.sas.com/kb/60/591.html There's another example of it at https://communities.sas.com/t5/SAS-Communities-Library/The-Node-Less-Traveled-Improving-Job-Performance-with-Node/ta-p/221293 I note that OSENV isn't documented as a key for the S Conversion Character in the SAS 9.4 Logging: Configuration and Programming Reference but it'd be worth a try - you never know 🙂 Cheers Paul

PaulHomes · ‎02-27-2018

The usage information you require is not in SAS metadata. You can find a list of potential users in metadata, but for actual platform usage information you will need to look in log files. To save you time I would strongly suggest you start by looking at the SAS Environment Manager Service Architecture Data Marts. The Service Architecture Framework Data Mart tables contains information extracted from log files (as well as other sources). You may find the information you need in those tables (or at least a subset as a starting point). For more information start by reading the Understanding SAS Environment Manager Service Architecture section in the SAS Environment Manager 2.5 Users Guide. In that book you will find information on how to enable the Service Architecture Framework (if not already enabled at your site), the reports available in the Report Centre, as well as information on the structure of the data mart tables.

PaulHomes · ‎02-26-2018

I haven't specifically setup SMS notifications in SAS Environment Manager but I have with other applications in the past. This was done with an email-to-SMS gateway service where you could send an email message to an SMTP server which then sent it as a text message e.g. phonenumber@gatewaysmtpserver.example.com This may be an option if you don't get any better suggestions: i.e. configure SAS Environment Manager for email alerts where the email alerts are sent via a email-to-SMS gateway service.

PaulHomes · ‎02-13-2018

Good to hear you got it fixed. Thanks for marking it solved too!

Online Status	Offline
Date Last Visited	2 weeks ago