Defining resource names with environment variables
You can avoid customizing resource name and configuration files for specific deployments by defining resources as operating system environment variables. At run time, the Resource Registry $GETENV() function resolves resource aliases that are defined as environment variables. The $GETENV() function can be used with or without Resource Registry encryption.
An informational log file message like the following indicates environment variable usage. For
example:
DTXLN2154I - Fri Feb 10 07:32:21 2017 - tid: 12068 inst: -1 - Resource Registry Info : Alias [username] uses environment variable [USERNAME] (mresname.c:1243)