Variable References

Some string attributes in the AWM model support the use of variable references. Referenced variables can be defined dynamically as part of a string and can reference AWM properties, environment properties, and certain static variables. See the table below for more information. If AWM properties are referenced, values are resolved at run time and preferably taken from the "previous tool" execution context pool, if available.

Variable references are only resolved by the following attributes:

References can be defined by using the Start Reference and End Reference symbols (default "&" and ".") which are defined in the application options. See Application Options for more information. It is possible to define a value containing several references as well as static characters. The following table shows the syntax of all variables that are available:

Variable/Syntax Description Example
%<env-var> Reference to an environment variable on the client’s local operating system. &%PUBLIC. = C:\Users\Public
<property ID> Reference to a property in the execution context. &PROP_WorkspaceFilename. = /MyProject/MyFile.txt
numelements Number of elements being processed in the current context.

In single processing contexts the resolved number is always 1. In mass processing contexts it is the number of sub-contexts.

See Mass Processing Overview for more information.

&numelements. = 4
userid Client’s user ID on the z/OS system. This variable can only be resolved if a connection to the mainframe has been established. &userid. =

USER123

wspath Path of the active Eclipse Workspace on the client’s local machine. &wspath. = C:\workspaces\workspace1

Examples

The following example show the definition of a dynamic file path.

Attribute value of Name_Physical (File Descriptor):

Reference Resolved Value
&%PUBLIC.\MyCache\&PROP_FileName. C:\Users\Public\MyCache\MyFile.txt
&userid..SOURCE(&PROP_Membername.) USER123.SOURCE(MEMXYZ)