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

feat: mpe_validations table and a note about the pgmloc var in hook scripts
All checks were successful
Publish to docs.datacontroller.io / Deploy docs (push) Successful in 1m0s
Details

Browse Source
This commit is contained in:
zver
2026-02-08 00:22:29 +00:00
parent 45a46d6a0a
commit 81ec07117d
3 changed files with 27 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/dcc-tables.md
View File

@@ -212,7 +212,6 @@ The code is simply `%include`'d at the relevant point during backend execution.
* Physical, ie the full path to a `.sas` program on the physical server directory
* Logical, ie a Viya Job (SAS Drive), SAS 9 Stored Process (Metadata Folder) or SASJS Stored Program (SASjs Drive).
If the entry ends in `".sas"` it is assumed to be a physical, filesystem file. Otherwise, the source code is extracted from SAS Drive or Metadata.
To illustrate:
@@ -220,5 +219,7 @@ To illustrate:
* Physical filesystem (ends in .sas): `/opt/sas/code/myprogram.sas`
* Logical filesystem: `/Shared Data/stored_processes/mydatavalidator`
You can access the path to hook script at runtime (ie, in the HOOK script SAS code) using the `PGMLOC` macro variable.
!!! warning
Do not place your hook scripts inside the Data Controller (logical) application folder, as they may be inadvertently lost during a deployment (eg in the case of a backup-and-deploy-new-instance approach).