Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SAP SQL Anywhere, on-demand edition 1.0 » SAP SQL Anywhere, on-demand edition » Troubleshooting and additional resources » Documentation conventions


Command prompts and command shell syntax

The documentation provides command line examples in a generic form.

If these examples contain characters that the shell considers special, the command requires modification for the specific shell. The modifications are beyond the scope of this documentation, but generally, use quotes around the parameters containing those characters or use an escape character before the special characters.

  • Parentheses and curly braces   Some command line options require a parameter that accepts detailed value specifications in a list. The list is enclosed with parentheses or curly braces. The documentation uses parentheses. For example:
    -x tcpip(host=

    Where parentheses cause syntax problems, substitute curly braces:

    -x tcpip{host=}

    If both forms result in syntax problems, enclose the entire parameter in quotes as required by the shell:

    -x "tcpip(host="

  • Semicolons   On Unix, enclose semicolons in quotes.

  • Quotes   If you must specify quotes in a parameter value, the quotes can conflict with the traditional use of quotes to enclose the parameter. For example, to specify an encryption key whose value contains double quotes, enclose the key in quotes and then escape the embedded quote:
    -ek "my \"secret\" key"

    In many shells, the value of the key would be my "secret" key.