When ACS is used in database tasks, aliases should never contain a catalog or user ID. Use of ACS is not permitted for the actual database files.
The ACS is effective only within a task. Consequently, the same alias may be defined for different files in different tasks.
Example
Task | Alias | File name |
TASK1 | ALIAS | FILE-1 |
TASK2 | ALIAS | FILE-2 |
TASK3 | ALIAS | FILE-3 |
Since UDS/SQL operates across multiple tasks, this could lead to inconsistencies in UDS/SQL databases.
If possible UDS/SQL checks on opening a database file whether the file name involved is an alias. If this is the case, an error message is output, and the corresponding action is aborted. In particular when aliases are used with a catalog and/or user ID (COMPLETE-ALIAS-NAMES=*ALLOWED) it is not possible to guarantee fully that this check is correct.