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

Update dcc-tables.md

Browse Source
This commit is contained in:
Allan Bowe 2022-05-23 14:50:35 +01:00 committed by GitHub
parent 98b776a8d1
commit 2a31e3fe2d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/dcc-tables.md
View File

@ -91,7 +91,9 @@ Leave blank if not required.
#### SAS Developer Notes #### SAS Developer Notes
The submitted table can be referenced as (`work.staging_ds`). If your DQ check means that the program should not be submitted, then simply exit with `&syscc > 4`. You can even set a message to go back to the user by using the [mp_abort](https://core.sasjs.io/mp__abort_8sas.html) macro: The `&orig_libds` macro variable contains a reference to the base library.table or format catalog that will be loaded (on approval). The staged table is called `work.STAGING_DS`.
If your DQ check means that the program should not be submitted, then simply exit with `&syscc > 4`. You can even set a message to go back to the user by using the [mp_abort](https://core.sasjs.io/mp__abort_8sas.html) macro:
``` ```
%mp_abort(iftrue= (&syscc ne 0) /* if this condition is true, the process will exit */ %mp_abort(iftrue= (&syscc ne 0) /* if this condition is true, the process will exit */
@ -158,4 +160,4 @@ 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 * 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). * 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 the Job/STP. The Job/STP path can be relative (beneath the /DataController root) or full (to another item in Drive / Metadata). If the entry ends in ".sas" it is assumed to be a physical, filesystem file. Otherwise, the source code is extracted from the Job/STP. The Job/STP path can be relative (beneath the /DataController root) or full (to another item in Drive / Metadata).