Besides using the predefined system symbols, you can also define
symbols specific to the check messages in the message table or setup
file. We'll call these local symbols. Keep the following in mind as
you plan whether to define local symbols and which ones to define:
- You should only create a local symbol for a known constant that
you use multiple times in the message table.
- National language support (NLS) variables are not created for
check specific symbols, and they do not require special support at
execution time.
- Local symbols can use symbols within symbols. In other words,
the symbol substitution text can include other local or system symbols.
Like system symbols, you specify the entity for your local symbol
as a name delimited by an ampersand (&) and a semi-colon. For
example, you could specify and use local symbols as follows:
- Create your own symbols for any text you use multiple times in
the message table. When you generate the message table, the symbols
will resolve to your text value. For example:
If I insert an entity, or symbol, &newsym;.
This
would resolve to:If I insert an entity, or symbol, the symbol resolves to this exciting text.
- Define your own symbols to make it easier to put accurate book
titles in the required <msgitem class="refdoc">
tag for check messages. For example:
For more information about the recommended settings, see &ieaa100t;.
This
resolves to:For more information about the recommended settings, see
z/OS MVS Auth Assm Services Reference ALE-DYN.
You can define symbols for your check using <!ENTITY> tags in
either:
Using either of these methods, the symbols are resolved in the
CSECT when you generate the message table.