Tag Archives for " example "

Data step view of login IDs stored in SAS metadata

This example provides data step code that will query the SAS Metadata and return a list of Logins stored in there. Learn how in this blog.

Login IDs are stored in SAS Metadata against Person Objects or Group Objects.  It can be handy to view a list of all these logins and this Data Step View just does that!

Overview

This example provides data step code that will query the SAS Metadata and return a list of Login Objects. The code as-is will create a data step view in the work library, so each time it is accessed it will dynamically query the SAS Metadata.

How to use it

The data step code below assumes that the connection to your Metadata Server has already been configured using the following System Options:

  • METASERVER
  • METAPORT
  • METAUSER
  • METAPASS
If you are running this code via an IOM client (e.g. Enterprise Guide, DI Studio, etc.) then these options will already be set to the user you have logged into SAS with.  If you are running this code from Base SAS you will need to issue an OPTIONS statement to set them.
Because access to the SAS Metadata requires security authorisation, the list of objects returned will be dependent on what the user specified in the METAUSER/METAPASS options can access.

Example

Metadata Logins View

Code

Data step view of web application connections in SAS metadata

This example provides data step code that will query the SAS Metadata and return a list of Web Application Connections, - learn how here.

If you have ever had to manually add in a reverse proxy, manually configure HTTPS, or otherwise needed to update the connection URLs for any of the SAS Web Applications you know that it can be a tedious job prone to errors.  This information can be updated in the Configuration Manager of SAS Management Console by right-clicking on each individual Web App and going to the Internal and External Connection tabs one by one… lots and LOTS of clicking and typing.  If you need a way to sanity check the connection information for the SAS Web Applications, or just want an easy way to see them all in the one place then this Data Step View is for you!

Overview

This example provides data step code that will query the SAS Metadata and return a list of Web Application Connections. The code as-is will create a data step view in the work library, so each time it is accessed it will dynamically query the SAS Metadata.

How to use it

The data step code below assumes that the connection to your Metadata Server has already been configured using the following System Options:

  • METASERVER
  • METAPORT
  • METAUSER
  • METAPASS
If you are running this code via an IOM client (e.g. Enterprise Guide, DI Studio, etc.) then these options will already be set to the user you have logged into SAS with.  If you are running this code from Base SAS you will need to issue an OPTIONS statement to set them.
Because access to the SAS Metadata requires security authorisation, the list of objects returned will be dependent on what the user specified in the METAUSER/METAPASS options can access.

Example

Metadata Web Application Connections View

Code

Data step view of email addresses stored in SAS Metadata

This example provides data step code that will query the SAS Metadata and return a list of Email Addresses stored in there.

Here is a simple way to access the details of Email Addresses stored in your SAS Metadata via a view.

Overview

This example provides data step code that will query the SAS Metadata and return a list of Email Addresses stored against users. The code as-is will create a data step view in the work library, so each time it is accessed it will dynamically query the SAS Metadata.

How to use it

The data step code below assumes that the connection to your Metadata Server has already been configured using the following System Options:

  • METASERVER
  • METAPORT
  • METAUSER
  • METAPASS
If you are running this code via an IOM client (e.g. Enterprise Guide, DI Studio, etc.) then these options will already be set to the user you have logged into SAS with.  If you are running this code from Base SAS you will need to issue an OPTIONS statement to set them.
Because access to the SAS Metadata requires security authorisation, the list of objects returned will be dependent on what the user specified in the METAUSER/METAPASS options can access.

Example

Metadata Email View

Code

Data step view of person objects in SAS metadata

This example provides data step code that will query the SAS Metadata and return a list of Person Objects (Users) that are registered.

Here is a simple way to access the details of Person Objects (Users) in your SAS Metadata via a view.

Overview

This example provides data step code that will query the SAS Metadata and return a list of Person Objects (Users). The code as-is will create a data step view in the work library, so each time it is accessed it will dynamically query the SAS Metadata.

How to use it

The data step code below assumes that the connection to your Metadata Server has already been configured using the following System Options:

  • METASERVER
  • METAPORT
  • METAUSER
  • METAPASS
If you are running this code via an IOM client (e.g. Enterprise Guide, DI Studio, etc.) then these options will already be set to the user you have logged into SAS with.  If you are running this code from Base SAS you will need to issue an OPTIONS statement to set them.
Because access to the SAS Metadata requires security authorisation, the list of objects returned will be dependent on what the user specified in the METAUSER/METAPASS options can access.

Example

Metadata Persons View

Code

Data step view of Visual Analytics reports in SAS metadata

This example provides data step code that will query the SAS Metadata and return a list of Visual Analytics Reports.

If you have ever wanted an easy way to list what Visual Analytics Reports exist in your SAS environment, read on!

Overview

This example provides data step code that will query the SAS Metadata and return a list of Visual Analytics Reports. The code as-is will create a data step view in the work library, so each time it is accessed it will dynamically query the SAS Metadata.

How to use it

The data step code below assumes that the connection to your Metadata Server has already been configured using the following System Options:

  • METASERVER
  • METAPORT
  • METAUSER
  • METAPASS
If you are running this code via an IOM client (e.g. Enterprise Guide, DI Studio, etc.) then these options will already be set to the user you have logged into SAS with.  If you are running this code from Base SAS you will need to issue an OPTIONS statement to set them.
Because access to the SAS Metadata requires security authorisation, the list of objects returned will be dependent on what the user specified in the METAUSER/METAPASS options can access.

Example

Data Step View of Tables in Metadata Example

Data Step View of VA Repors

Code

Data Step View of Libraries in SAS Metadata

This blog post discusses data step code that will query the SAS Metadata and return a list of Libraries and their Extended Attributes.

Here is an easy way to get a list of Libraries from SAS Metadata, including any extended attributes they may have.  This comes in handy for checking what extended attributes are in place on your Visual Analytics LASR Libraries, for example your Autoload settings!

Overview

This example provides data step code that will query the SAS Metadata and return a list of registered Libraries and their extended attributes. The code as-is will create a data step view in the work library, so each time it is accessed it will dynamically query the SAS Metadata.

How to use it

The data step code below assumes that the connection to your Metadata Server has already been configured using the following System Options:

  • METASERVER
  • METAPORT
  • METAUSER
  • METAPASS
If you are running this code via an IOM client (e.g. Enterprise Guide, DI Studio, etc.) then these options will already be set to the user you have logged into SAS with.  If you are running this code from Base SAS you will need to issue an OPTIONS statement to set them.
Because access to the SAS Metadata requires security authorisation, the list of Libraries returned will be dependent on what the user specified in the METAUSER/METAPASS options can access.

Example

Data Step View of Tables in Metadata ExampleData Step View of Libraries

Code

Data Step View of Web Report Studio Reports from SAS Metadata

This blog post provides insight into data step code that will query the SAS Metadata and return a list of Web Report Studio Reports.

If you are after a simple way to list all your SAS Web Report Studio Reports, then this post is for you!

Overview

This example provides data step code that will query the SAS Metadata and return a list of Web Report Studio Reports. The code as-is will create a data step view in the work library, so each time it is accessed it will dynamically query the SAS Metadata.

How to use it

The data step code below assumes that the connection to your Metadata Server has already been configured using the following System Options:

  • METASERVER
  • METAPORT
  • METAUSER
  • METAPASS
If you are running this code via an IOM client (e.g. Enterprise Guide, DI Studio, etc.) then these options will already be set to the user you have logged into SAS with.  If you are running this code from Base SAS you will need to issue an OPTIONS statement to set them.
Because access to the SAS Metadata requires security authorisation, the list of objects returned will be dependent on what the user specified in the METAUSER/METAPASS options can access.

Example

Data Step View of WRS Reports

Code

Data Step View of Stored Procedures in SAS Metadata

This blog posts discusses about data step code that will query the SAS Metadata and return a list of Stored Procedures.

Here is an easy way to get a list of Stored Procedures in your SAS environment!

Overview

This example provides data step code that will query the SAS Metadata and return a list of registered Stored Procedures. The code as-is will create a data step view in the work library, so each time it is accessed it will dynamically query the SAS Metadata.

How to use it

The data step code below assumes that the connection to your Metadata Server has already been configured using the following System Options:

  • METASERVER
  • METAPORT
  • METAUSER
  • METAPASS
If you are running this code via an IOM client (e.g. Enterprise Guide, DI Studio, etc.) then these options will already be set to the user you have logged into SAS with.  If you are running this code from Base SAS you will need to issue an OPTIONS statement to set them.
Because access to the SAS Metadata requires security authorisation, the list of objects returned will be dependent on what the user specified in the METAUSER/METAPASS options can access.

Example

Data Step View of Tables in Metadata Example

STP Dataset View

Code

Data Step View of Groups and Roles in SAS Metadata

This posts delves into the data step code that will query the SAS Metadata and return a list of Groups and Roles.

Ever wanted an easy way to query the Groups and Roles in SAS Metadata?

Overview

This example provides data step code that will query the SAS Metadata and return a list of Groups and Roles.  The code as-is will create a data step view in the work library, so each time it is accessed it will dynamically query the SAS Metadata.

How to use it

The data step code below assumes that the connection to your Metadata Server has already been configured using the following System Options:

  • METASERVER
  • METAPORT
  • METAUSER
  • METAPASS
If you are running this code via an IOM client (e.g. Enterprise Guide, DI Studio, etc.) then these options will already be set to the user you have logged into SAS with.  If you are running this code from Base SAS you will need to issue an OPTIONS statement to set them.
Because access to the SAS Metadata requires security authorisation, the list of objects returned will be dependent on what the user specified in the METAUSER/METAPASS options can access.

Example

Data Step View of Tables in Metadata Example

View of SAS Groups and Roles

Code

Data Step View of Directories Registered in SAS Metadata

This blog post discusses about the data step code that will query the SAS Metadata and return a list of Directory Objects.

You probably have Directories registered in your SAS Metadata and don’t even know it!  Each Base SAS Library points to a directory. Directories containing your Stored Process source code may already be registered. Directories that contains your deployed DI Studio jobs are in Metadata.

Overview

This example provides data step code that will query the SAS Metadata and return a list of Directory Objects.  The code as-is will create a data step view in the work library, so each time it is accessed it will dynamically query the SAS Metadata.

How to use it

The data step code below assumes that the connection to your Metadata Server has already been configured using the following System Options:

  • METASERVER
  • METAPORT
  • METAUSER
  • METAPASS
If you are running this code via an IOM client (e.g. Enterprise Guide, DI Studio, etc.) then these options will already be set to the user you have logged into SAS with.  If you are running this code from Base SAS you will need to issue an OPTIONS statement to set them.
Because access to the SAS Metadata requires security authorisation, the list of objects returned will be dependent on what the user specified in the METAUSER/METAPASS options can access.

Example

Data Step View of Directories in Metadata

Code

1 2

Privacy Policy - Terms and Conditions