MXCS Commands and Objects
SQL/MX Connectivity Service Administrative Command Reference—526350-005
2-8
Command Size Limit
But the period is required in this command because the DS name is defaulted:
INFO DS $AR2.
This last example uses the DS named in the previous command but specifies a
different service (it assumes a previous command acted on a DS). The example
shows how to get state information on one specific DS from each service.
When an intermediate component is specified by a default, you must specify its
terminating period. For example, this command specifies the EVAR on $as2
owned by the same DS named in the previous example:
INFO EVAR $as2..Evar2;
Command Size Limit
Commands have no size limit, so you can continue long statements or commands over
multiple lines, breaking them at any space character. A semicolon (;) terminates a
statement or command you break over several lines. To break a line within SQL
identifier or string literal, use the CONCAT operator (||) and quote the two substrings
with the same single or double quote character. Using space characters around the
CONCAT operator is optional but is recommended for readability.
In this example, an EVAR name with a long DS name in it is broken. Make a break
within a quoted string, not at the period after it.
add evar "This is a long DS name that will " ||
"be broken into two, not three, parts”.”ThisEvarName”,
Type set, value 34567;
Single Quotes for Attribute Values
Using single quotes around attribute values is optional except when an SQL string
literal is required. That is, extra quotes around attribute values do not cause a syntax
error. Extra quotes on keywords do cause an error. The MXCS administrative
command parser removes unneeded single or double quotes before the strings are
used. It also adds single quotes if they are required by the MXCS subsystem or
database.
Double Quotes for Object Names
Using double quotes around object names (those that are SQL identifiers) is optional
except when there are nonalphanumeric characters, spaces, or lowercase characters
in the name. Extra double quotes around identifiers that do not require them do not
cause a syntax error, but do inhibit automatically translating lowercase characters to
uppercase. The command parser removes the quotes before using the name internally.
Empty Quoted Strings
Empty quoted strings are reported as syntax errors.
Comentarios a estos manuales