Michael_Lowry

U00020206 Variable '&01' was stored with value '$-02'.

Discussion created by Michael_Lowry on Jun 13, 2018

Message U00020206 is printed to a task’s Activation log when an object or script variable is set. I’ve noticed some differences in the way this message is displayed, depending on how the variable is set.

 

In the examples below, the variables are all set to a null (empty) value.

 

Variables & Prompts tab

If an executable object has object variables defined (in the Variables & Prompts tab), messages like this are printed to the log:

2018-06-13 10:32:27 - U00020206 Variable '&VARIABLE_1#' was stored with value ''.
2018-06-13 10:32:27 - U00020206 Variable '&VARIABLE_2#' was stored with value ''.

Similar messages appear if the variable is set via an attached prompt set.

 

:SET command

If variables are set only using the :SET command, no messages appear in the log.

 

:RSET or :PSET command

If variables are not defined in the Variables & Prompts tab, but are instead set using the :RSET or :PSET command, messages like these appear in the log:

2018-06-13 11:05:52 - U00020237 The object variable '&VARIABLE_1#' in object: 'UC0.VARIABLE_TEST_1.SCRI', line: '00005' (RunID: '0150238287') has been created with the value '' by  using the command :RSET.
2018-06-13 11:05:52 - U00020206 Variable '&Variable_1#' was stored with value ''.
2018-06-13 11:05:52 - U00020237 The object variable '&VARIABLE_2#' in object: 'UC0.VARIABLE_TEST_1.SCRI', line: '00006' (RunID: '0150238287') has been created with the value '' by  using the command :RSET.
2018-06-13 11:05:52 - U00020206 Variable '&Variable_2#' was stored with value ''.

The :RSET command takes a script variable and promotes it to an object variable. The :PSET command does the same, and additionaly sets the variable at the level of the parent workflow, if the task is running in a workflow. In either case, message U00020237 is printed when the script variable is promoted to an object variable. (If the variable was already defined as an object variable, e.g., in the Variables & Prompts tab, this message does not appear.) Note that although script variable names may contain lowercase letters, object variable names are always comprised of only capital letters.

 

:READ command

If variables are instead set using the :READ command, messages like these appear in the log:

2018-06-13 11:10:39 - U00020206 Variable 'Variable_1#' was stored with value ' '.
2018-06-13 11:10:39 - U00020206 Variable 'Variable_2#' was stored with value ' '.

Note that the variable names lack the leading ampersand (&), and are stored with a single blank character instead of a null value.

Outcomes