The following environment variables are available for all script loads and script exports, both Windows and UNIX/Linux.

All scripts

In addition to the specific variables listed on the sections below, the following variables are available in all scripts:

Environment variableDescription
WSL_META_AUTHCFGAdditional user defined attributes as JSON, scripts can load attributes from this variable.
WSL_META_AUTHTKN_[1|2|3]

Additional Profile authentication token fields from the associated Metadata Connection, normally used directly in connection strings with the token format $AUTHTKN_[1|2|3]$ but can be accessed in scripts via this variable.

WSL_META_DBIDThe Database ID property of the meta-repository connection.
WSL_META_DBThe name of the database for the meta-repository connection.
WSL_META_SCHEMAThe meta-repository schema name, with a trailing dot.


 
WSL_META_USERThe user id for the meta-repository connection.
WSL_META_PWDThe password for the meta-repository connection.
WSL_WORKDIR
  • Windows: The work directory defined in the Windows connection.
  • UNIX/Linux: The work directory defined in the UNIX/Linux or Hadoop connection.
WSL_SEQUENCEA unique sequence number for the load or export task.
WSL_SCH_RESTAPI_URLThe server URL for the scheduler connection.
WSL_SCH_RESTAPI_USERThe api user id for the scheduler connection.
WSL_SCH_RESTAPI_PWDThe password for the scheduler connection
WSL_JOB_KEYID of the Job which started the script, '0' for interactive execution.
WSL_JOB_NAMEName of the Job which started the script, 'Develop' for interactive execution.
WSL_TASK_KEYID for the Task within the Job, or Object ID for interactive execution.
WSL_TASK_NAMEName of the Task within the Job, or Object Name for interactive execution.


Additional environment variables for load scripts

The following variables are available in all load scripts:

Environment variableDescription
WSL_LOAD_FULLNAMEThe fully-qualified load table name.
WSL_LOAD_TABLEThe unqualified load table name.
WSL_LOAD_SCHEMAThe schema for the load table.  
WSL_LOAD_DBThe name of the database for the load table.
WSL_TEMP_DB

The name of the staging database for the load (Teradata only). 

WSL_TGT_DBIDThe Database ID property of the load table's storage connection.
WSL_TGT_USERThe user id for the load table's storage connection.
WSL_TGT_PWDThe password for the load table's storage connection.
WSL_TGT_CONSTRINGThe ODBC connection string with RED tokens expanded.
WSL_TGT_AUTHCFGAdditional Profile authentication attributes (JSON format), from the associated Target Connection. Extract attributes by parsing the JSON, if required.
WSL_TGT_AUTHTKN_[1|2|3]

Additional Profile authentication token fields from the associated Target Connection, normally used directly in connection strings with the token format $AUTHTKN_[1|2|3]$ but can be accessed in scripts via this variable.

WSL_PARAMnnnAny parameters that start with the load table or export object name. Example: A table called load_abc has a parameter called load_abc_server defined. In this case, a variable called WSL_PARAM_SERVER will be created.

All load scripts from Database or ODBC connections

In addition to the variables in the previous table, the following variables are available in all load scripts from Database or ODBC connections:

Environment variableDescription
WSL_SRC_AUTHCFGAdditional user defined attributes as JSON, scripts can load attributes from this variable.
WSL_SRC_DSNThe ODBC data source name (DSN) for the source connection.
WSL_SRC_SERVERThe server for the source connection.
WSL_SRC_DBPORTThe database port for the source connection.
WSL_SRC_DBIDThe Database ID property of the source connection.
WSL_SRC_DBThe name of the database for the source connection.
WSL_SRC_AUTHTKN_[1|2|3]

Additional Profile authentication token fields from the associated Source Connection, normally used directly in connection strings with the token format $AUTHTKN_[1|2|3]$ but can be accessed in scripts via this variable.

WSL_SRC_SCHEMA

The Source Schema property of the load.

The property is fetched without modification, so there may or may not be a trailing dot depending on how it is configured.
However, it is better not to assume the trailing dot is or isn't appended by using the variable like this, when it is not empty:

OSIf no trailing dot is wantedIf a trailing dot is wanted
Windows !WSL_SRC_SCHEMA:.=! !WSL_SRC_SCHEMA:.=!.
UNIX/ Linux ${SRC_SCHEMA%.} ${SRC_SCHEMA%.}.


WSL_SRC_USERThe user id for the source connection.
WSL_SRC_PWDThe password for the source connection.

Additional environment variables for export scripts

The following variables are available in all export scripts:

Environment variableDescription
WSL_EXP_NAMEThe export object name.
WSL_EXP_FULLNAMEThe fully-qualified export table name.
WSL_EXP_TABLEThe unqualified export table name.
WSL_EXP_SCHEMAThe schema for the export table.
WSL_EXP_DBThe name of the database for the export table.
WSL_TEMP_DB
  • Others: Not used.
WSL_SRC_DSNThe ODBC data source name (DSN) for the export table's storage connection.
WSL_SRC_SERVERThe server for the export table's storage connection.
WSL_SRC_DBPORTThe database port for the export table's storage connection.
WSL_SRC_DBID
  • The Database ID property of the export table's storage connection.
WSL_SRC_USERThe user id for the export table's storage connection.
WSL_SRC_PWDThe password for the export table's storage connection.


Azkaban Environment Variables

Any script run from the Azkaban Scheduler also gets Azkaban environment variables:

Environment variableDescription
JOB_NAMEThis is the WhereScape Task Name given in the Azkaban Project Flow, in the form: "<Action> <Task Name> (<Task ID>)"
JOB_PROP_FILEPath to the Azkaban Properties file for this Job, useful for reading additional Azkaban properties for the Job, such as azkaban.flow.execid to get Azkaban's ID for the run.
JOB_OUTPUT_PROP_FILEPath to the Azkaban Properties Output file for this Job, useful when passing properties from one task to another.
  • No labels