Command Reference Guide
MXCS Commands and Objects
SQL/MX Connectivity Service Administrative Command Reference—526350-005
2-7
DS Name and EVAR Name
groupname
is the group login name and must be given if membername is used. This
component is an SQL identifier data type but is always set to uppercase after the
command processes it (see Fields or Tokens in Commands on page 2-4).
membername
is the NonStop OS user login with no aliases permitted. This component is an SQL
identifier data type but is always set to uppercase after the command processes it
(see Fields or Tokens in Commands on page 2-4).
If you use the asterisk (*) or question mark (?) in a name, enclose it in single (‘) or
double (“) quotation marks, or it is flagged as an invalid use of a pattern. The only valid
pattern is an asterisk (*) alone, with no quotes, which generally indicates all.
DS Name and EVAR Name
The DS and EVAR name are not case-sensitive, unless they are enclosed in double
quotes. To eliminate the need for double quotes, avoid spaces, punctuation, and
lowercase characters. When necessary, include a double quote in such a name by
doubling it. A backslash (\) is accepted as a character and not considered an escape
character.
An example of a DS name with embedded special characters is:
$AS."ds',; ?)n""ame" specifies DS: ds',; ?)n"ame
Default Object Name
Use the default when object name components are long and difficult to type. To ensure
all cases are well-defined, follow these guidelines:
After you use an object name, it is retained until you enter another name
component of the same type.
When you use an object name, the obj-type field on the command defines the
object type of the last specified component of the name. For example, the
commands info service $z0123; and info server $z0123; are well-
defined. (The first example will likely fail because $z0123 is probably not an
association server process ID.)
When the final component of the name is defaulted while other components are
specified, use trailing dot (period) separators to show missing components. This
guideline does not apply to missing leading components.
For example, this string addresses the named service on the same system as
before (no leading period is needed):
INFO SERVICE $AR