dc/docs.datacontroller.io
5
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update libraries.md

Browse Source
This commit is contained in:
Allan Bowe
2022-07-25 16:25:10 +01:00
committed by GitHub
parent 07d0c6d4dc
commit 320a979c4f
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/libraries.md
View File

@@ -10,7 +10,7 @@ og_image: img/libraries.png
The process for adding new libraries to Data Controller depends on whether we are talking about: The process for adding new libraries to Data Controller depends on whether we are talking about:
* The VIEW or EDIT menu * The VIEW or EDIT menu
* Which flavour of SAS is being used * The flavour of SAS being used
In VIEW mode, all available libraries are shown, unless the [DC_RESTRICT_VIEWER](/dcc-options/#dc_restrict_viewer) option is set. In VIEW mode, all available libraries are shown, unless the [DC_RESTRICT_VIEWER](/dcc-options/#dc_restrict_viewer) option is set.
@@ -18,19 +18,19 @@ In EDIT mode, only the libraries corresponding to the configuration in [MPE_TABL
![library list](img/libraries.png) ![library list](img/libraries.png)
Flavour specific guidance is below. Flavour specific guidance follows.
## Viya Libraries ## Viya Libraries
Library definitions should be added in the `autoexec.sas` of the designated Compute Context using Environment Manager. Library definitions should be added in the `autoexec.sas` of the designated Compute Context using Environment Manager.
If the above is not feasible, it is possible to insert code in the `[DC Drive Path]/services/settings.sas` file however this will have a performance impact due to the additional API calls. If the above is not feasible, it is possible to insert code in the `[DC Drive Path]/services/settings.sas` file however - this will have a performance impact due to the additional API calls.
## SAS 9 EBI Libraries ## SAS 9 EBI Libraries
In most cases, libname statements are NOT required, so long as they are accessible in metadata. In most cases, libname statements are NOT required so long as they are accessible in metadata.
For the VIEW menu, the libname statement is made using the [mm_assignlib](https://core.sasjs.io/mm__assignlib_8sas.html) macro (META engine). It is important that each library has a unique (up to 8 char) LIBREF. For the VIEW menu, the libname statement is made using the [mm_assignlib](https://core.sasjs.io/mm__assignlib_8sas.html) macro (META engine). It is important that each library has a unique LIBREF.
For the EDIT menu, direct libname statements are derived using the [mm_assigndirectlib](https://core.sasjs.io/mm__assigndirectlib_8sas.html) macro. For the EDIT menu, direct libname statements are derived using the [mm_assigndirectlib](https://core.sasjs.io/mm__assigndirectlib_8sas.html) macro.
@@ -39,4 +39,4 @@ If metadata extraction is not possible, libname statements may be added to the `
## SASjs Server Libraries ## SASjs Server Libraries
New library definitions can be added in the `[DC Drive Path]/services/public/settings.sas` Stored Program. New library definitions can be added to the `[DC Drive Path]/services/public/settings.sas` Stored Program.