Resolution:
Using the ss Java API, if a user places an unknown option (or mis-spells an option) in a startup config file. The user will not be notified of the error at runtime.
Example;
Suppose that the developer entered,
       ss.server_nams=tcp:_node:5661    (option is mis-spelled)
instead of
       ss.server_names=tcp:_node:5661
the end user will not get an error regarding the bad option, such as:
"com.smartsockets.TipcNotFoundException: option &ltss.server_nams> does not exist .".

However, if the bad option is set from inside the Java client:
      Tut.setOption("ss.server_nams","tcp:_node:5799");
then the following error does appear:
      WARNING: Error = 0: option &ltss.server_nams> does not exist

In C, if a bad option is given either from within the code or by way of reading a file the user will see the following error:
       TAL-SS-05038-I setopt: unknown option &ltserver_nams>

Be aware that there could  be potential side effects. In the example provided above the RTclient will connect to the default tcp:_node:5101 instead of using the named port id.
Another potential source of error is if the user does not adhere strictly to the option setting format.

key=value
or
key:value
or
key value

According to the Properties class Java API doc: "The key contains all of the characters in the line starting with the first non-white space character and up to, but not including, the first unescaped '=', ':', or WHITE SPACE [emphasis added] character other than
a line terminator."

If the user inadvertently does something such as the following:

setopt option value

the Java client will silently ignore the setting and use the default value of option.
This problem has been reported (Defect # 1-26DF19) but may not be addressed until the ss 7.0 release.

Java client fails to report bad options read from file.