Skip to content

Library Definitions

Overview

Altair SLC Hub enables you to centrally define and manage library definitions for use in Altair Analytics Workbench, in both the SAS Language Environment (SLE) and Workflow Environment. For SLE use, it is possible to set up user-specific access to libraries using a feature called Libname bindings.

The Altair SLC Hub web portal enables users with appropriate administrative access to create and manage library definitions centrally in the Altair SLC Hub. Altair SLC Hub also enables the specification of all appropriate options for each engine and operating system, in exact parallel to a LIBNAME statement in the SAS language.

The two key advantages of defining libraries in Altair SLC Hub are:

  • If any aspect of library access changes (location, options specified, etc), the change can be made once centrally, rather than changing multiple libname statements in SAS language code. This saves time and the risk of missing anything.
  • Library access can be fully customised for each Altair SLC Hub user type. For example, two Altair SLC Hub users could call the same library from Workbench, either with a different or the same reference, but be connected with different options appropriate to their user type. For example, a library definition could be created giving one user group read only access and another group read and write access.

Library definitions are called differently, depending on the Altair Analytics Workbench perspective: - For SLE use, Altair SLC Hub library definitions are referenced from SAS language code using keywords called Libname bindings, which are user or user group specific. When a user logs into Altair SLC Hub from Altair Analytics Workbench, the Libname bindings that are associated to them will automatically be visible as data sources and can be referenced by name in code. - For Workflow use, the Altair SLC Hub Library Definition name is used to reference the data source directly, without Libname bindings. As with any feature of Altair SLC Hub, control of the library definitions that users have access to can still be performed from within Altair SLC Hub using access control.

Note

Although libraries are defined in Altair SLC Hub, the actual library call is still being made by the end user from Workbench, so that end user will need appropriate software installed to access the library in question.

Libname binding names do not have to be unique, either within a library definition or Altair SLC Hub as a whole. This allows full flexibility in how libraries are defined and referenced; for example different user types can quote the same libname binding name in their code, but Altair SLC Hub can offer each user type different access. The downside of this flexibility is that the possibility exists for one user to see two identically named Libname bindings, with no way of differentiating them in their code. If that happens, then library referencing from SAS language code cannot be guaranteed to be consistent. It is therefore recommended that care is taken when defining Libname bindings to prevent clashes such as this occurring.

Changes made to library definitions and Libname bindings do not appear in a Workbench Processing Engine until that Processing Engine is restarted.

Portal interface

The Library Definitions page of Altair SLC Hub is used to create library definitions and libname bindings.

The New button creates a library definition.

Each library definition links to a further page where its details can be viewed and edited.

The Add button in the Libname Bindings section can be used to enter a libname for an Altair SLC Hub User or Group.