yesterday
carl_sommer
SAS Employee
Member since
12-05-2011
- 38 Posts
- 9 Likes Given
- 5 Solutions
- 22 Likes Received
-
Latest posts by carl_sommer
Subject Views Posted 536 04-10-2025 04:56 PM 550 04-10-2025 04:42 PM 487 02-25-2025 09:01 PM 538 02-22-2025 09:08 PM 601 11-19-2024 03:21 PM 1091 11-11-2024 08:56 AM 1266 10-30-2024 10:13 AM 1004 10-24-2024 10:32 PM 1182 10-22-2024 06:34 PM 1521 10-13-2024 07:05 PM -
Activity Feed for carl_sommer
- Got a Like for Re: Getting a List of Metadata Folders. 11 hours ago
- Posted Re: SAS 9.4 installation failure on Administration and Deployment. 04-10-2025 04:56 PM
- Posted Re: SAS 9.4 installation failure on Administration and Deployment. 04-10-2025 04:42 PM
- Liked Older SAS 9.4 Platform Releases and Product Versions Moving to Limited Support in 2025 for kimberlymay. 04-10-2025 04:41 PM
- Liked The case for content and data administrators for DavidStern. 03-19-2025 10:43 PM
- Got a Like for Re: Pre-assign libnames depending on user permissions as in SAS 9.4 Metadata. 02-26-2025 12:43 AM
- Posted Re: Pre-assign libnames depending on user permissions as in SAS 9.4 Metadata on Moving to SAS Viya. 02-25-2025 09:01 PM
- Posted Re: Pre-assign libnames depending on user permissions as in SAS 9.4 Metadata on Moving to SAS Viya. 02-22-2025 09:08 PM
- Got a Like for Re: SAS User details from Metadata. 01-28-2025 02:04 AM
- Got a Like for Re: I need to migrate a large number of metadata bound libraries. 11-20-2024 02:06 AM
- Got a Like for Re: I need to migrate a large number of metadata bound libraries. 11-19-2024 03:23 PM
- Posted Re: I need to migrate a large number of metadata bound libraries on Administration and Deployment. 11-19-2024 03:21 PM
- Liked Re: Generate Report on User Group Access for MichelleHomes. 11-12-2024 10:47 AM
- Liked Re: Generate Report on User Group Access for Quentin. 11-11-2024 09:20 AM
- Posted Re: Generate Report on User Group Access on Administration and Deployment. 11-11-2024 08:56 AM
- Posted Re: Generate Report on User Group Access on Administration and Deployment. 10-30-2024 10:13 AM
- Posted Re: Getting a List of Metadata Folders on SAS Data Management. 10-24-2024 10:32 PM
- Posted Re: Store secrets - SAS 9.4M4 on Administration and Deployment. 10-22-2024 06:34 PM
- Got a Like for Re: How to Add an LDAP User to Connect to SAS Enterprise Guide ?. 10-14-2024 11:29 PM
- Got a Like for Re: How to Add an LDAP User to Connect to SAS Enterprise Guide ?. 10-14-2024 06:10 PM
-
Posts I Liked
Subject Likes Author Latest Post 11 5 3 3 2 -
My Liked Posts
Subject Likes Posted 1 10-24-2024 10:32 PM 1 02-25-2025 09:01 PM 2 11-19-2024 03:21 PM 2 10-13-2024 07:05 PM 1 08-26-2024 02:24 PM
04-10-2025
04:56 PM
I would recommend opening a case with SAS Technical Support.
Carl Sommer - SAS Technical Support
... View more
04-10-2025
04:42 PM
Please be aware that SAS 9.4 M4 is under Limited Support. See Older SAS 9.4 Platform Releases and Product Versions Moving to Limited... - SAS Support Communities
Carl Sommer - SAS Technical Support
... View more
02-25-2025
09:01 PM
1 Like
And now I feel like I should have also said this instead.
Look at the Resources tab when you edit a compute context.
Reference SAS Help Center: Contexts Page
A better reference / writeup: Managing Connections to Data Sources and SAS Libraries for Compute Sessions in SAS Viya
Carl Sommer - SAS Technical Support
... View more
02-22-2025
09:08 PM
Given that there are no library objects in SAS VIya (aside from CASLIBS in CAS sessions), the Viya General Authorization system isn't able to help with library permissions or preassignment.
However youu could look at creating appropriate compute contexts for these purposes and permitting your users/groups to these contexts. See SAS Help Center: SAS Compute: Server, Service, and Contexts and the section on the sas.compute.server: autoexec_code configuration instance. If you truly needed highly-specific code, I've seen situations where PROC HTTP was used in the autoexec to determine the groups the user is in, and assign the librefs based upon that.
Carl Sommer - SAS Technical Support
... View more
11-19-2024
03:21 PM
2 Likes
FYI - Steve has opened a tech support case on this; when it's resolved I'll update this thread with relevant information.
Carl Sommer - SAS Technical Support
... View more
11-11-2024
08:56 AM
This sounds like your WORK library had an issue. This could just be that you are making too-large of a metadata request.
Your original post said you were interested in what access specific groups had. You could filter on both the member type (Library) and the specific group. This is similar to what is shown in Example 3: ReadMetadata Permission for Libraries for a Specified User. Here's the form of this, looking for all libraries where the ETLDevelopers group have WriteMetadata access:
%mdsecds(identitynames="ETLDevelopers", identitytypes="IdentityGroup", membertypes="Library", perms="WriteMetadata");
What do you have for MEMSIZE? Have you verified your work library is OK? Since it shows the H: drive, I suspect it is a network drive. It's best to use a local disk for WORK.
If you continue to have issues, share your SAS log or open a case with SAS Technical Support.
Carl Sommer - SAS Technical Support
... View more
10-30-2024
10:13 AM
Please see the documentation for SAS Help Center: %MDSECDS Security Report Macro .
Note that you likely have granted permissions using groups, so if you really want to report on an individual user, you will probably need to also use SAS Help Center: %MDUEXTR User Import Macro to generate tables of users and group memberships that you can join with the data from %MDSECDS to report at an individual user-level.
Here's an example invocation of %mdsecds to generate tables and a view in the WORK library for all libraries defined to metadata.
%mdsecds(membertypes="Library");
Carl Sommer - SAS Technical Support
... View more
10-24-2024
10:32 PM
1 Like
4 years later, and Allan's macro now lives at core/meta/mm_getfoldertree.sas at main · sasjs/core
Carl Sommer - SAS Technical Support
... View more
10-22-2024
06:34 PM
To amend what Greg suggested, you'll want to use both the STORE and the SECURE options. STORE provides macro compilation; SECURE provides encryption (so nosy people turning on MPRINT, etc get nada, zip, zilch)
See Example 5: Using the %MACRO Statement with the STORE and SECURE Options
Carl Sommer - SAS Technical Support
... View more
10-13-2024
07:05 PM
2 Likes
As others have mentioned, importad.sas is the way to go for an automated method for maintaining users in metadata.
However it's not wrong to define users manually either; however if you do, and intend to use importad..sas either now or in the future, be sure to define the external identity for the users you manually create, so that the matching key between metadata and your identity provider is in place. See SAS Help Center: External Identities
Carl Sommer - SAS Technical Support
... View more
08-26-2024
02:24 PM
1 Like
This is the sort of thing that requires knowing the baseline behavior, and then being able to measure from that.
Do you have a log of each, with the FULLSTIMER system option enabled?
With elapsed time changing, it's important to know if data volumes changed accordingly, or if an index has been dropped, or if data has moved to a slower network link, or... the list goes on.
If you don't have an earlier log to compare against, at least you could generate a log with the problem exhibited, and work your way through the steps with the longest elapsed times. See how much CPU is being consumed vs the elapsed time; this will help you to make a determination if you are CPU or I/O constrained.
Carl Sommer - SAS Technical Support
... View more
08-07-2024
12:24 PM
2 Likes
SAS provides the %MDSECDS macro to build a set of tables for requested objects and their associated permissions.
See SAS Help Center: Overview of the Security Report Macros.
I've not used the metacode plugin, but have heard great things about it.
Carl Sommer - SAS Technical Support
... View more
07-16-2024
01:44 PM
FYI, the link (http://go.documentation.sas.com/?cdcId=calcdc&cdcVersion=3.3&docsetId=calauthzgen&docsetTarget=n1xnhxt4tj57wzn1kdridi7u2g27.htm&locale=en#p06lel9je9mt0sn18xx4pjrvnmbz) in this text is broken: Instead it means, to quote the Viya Administration documentation, "access to the associated service’s endpoints in the context of that particular object"
... View more
04-29-2024
01:11 PM
2 Likes
I believe most, if not all, of this information is available through tables produced by the SAS Help Center: %MDUEXTR User Import Macro
Carl Sommer - SAS Technical Support
... View more
04-22-2024
09:45 AM
I recently had a case for a customer who had exactly this situation. I'm a bit surprised that someone hasn't surfaced code for this sooner. Better late than never, a macro for this has been added at technical-support-code/usage/administration/sas-metadata-server/create_metadata_login_s9.sas at main · sascommunities/technical-support-code · GitHub
%createLoginObject(
Person_Name=sasdemo /* REQUIRED: metadata name for Person object */
,Authdomain=OracleAuth /* REQUIRED: metadata name for the Authdomain for the Login object */
,Login_userid=scott /* OPTIONAL: userid attribute for the Login object */
,Login_password=tiger /* OPTIONAL: password attribute for the Login object */
,Login_Name=sasdemo Oracle login /* OPTIONAL: metadata name for the Login object */
);
Carl Sommer - SAS Technical Support
... View more