Resolution:
All tal_ss.cat resource file entries take the format of:
       TAL_SS-&ltinteger id>-&ltresource_entry_level>
where &ltresource_entry_level> is one of the following:
  -A:  Always
  -E:   Error
  -W:  Warning
  -I:  Informational
  -V:  Verbose
  -D:  Debug  

Example:
TAL-SS-10024-A RTserver started successfully.

Trace_Levels are used for debugging purposes in RTserver and RTclient.  (see the SmartSockets Option Trace_Level in the SmartSockets User’s Guide).

The following is a mapping of the trace_level and resource_entry_levels:

Trace_Level      Resource entry level messages that will be used.
Never                  A
Error                   A,E
Warning             A,E,W
Info                    A,E,W,I
Info_1                A,E,W,I
Info_2                A,E,W,I
Verbose            A,E,W,I,V
Verbose_1        A,E,W,I,V
Verbose_2        A,E,W,I,V
Debug               A,E,W,I,V,D

-A or Always resource_entry_level- All resource file entry numbers ending with “-A” will always be logged even at a trace_level of Never. An example is upon RTserver startup:

{SRV.EDM._node_pid} TAL-SS-10024-A RTserver started successfully.

The _1, _2 trace_levels don't correspond to anything that can set in the catalog file. They are used by the RTprocess to display more information in the RTprocess trace_file that is not included in the tal_ss.cat resource file.

It is possible to modify the resource file entries. An example are the entries:

TAL-SS-10031-I %s {'%s', '%s', '%s', T_INT4_SPEC, %s, %s, T_INT2_SPEC} DOWN.
TAL-SS-10032-I %s {'%s', '%s', '%s', T_INT4_SPEC, %s, %s, T_INT2_SPEC} UP.

These record an entry in the RTserver trace_file whenever an RTclient or RTserver connects/disconnects. They will only be displayed at a trace_level of Info or higher because they are (I)nformational messages. By changing these entries to (W)arning messages you can lower your trace_level to Warning and now see RTclient or RTserver connects/disconnects in addition to any other (W)arning messages.

TAL-SS-10031-W %s {'%s', '%s', '%s', T_INT4_SPEC, %s, %s, T_INT2_SPEC} DOWN.
TAL-SS-10032-W %s {'%s', '%s', '%s', T_INT4_SPEC, %s, %s, T_INT2_SPEC} UP.

It is recommended that if you change any tal_ss.cat resource file entries that you first make a copy of the original tal_ss.cat file. You can also make a copy of the tal_ss.cat file and name the copy which you will modify something other than the default name of tal_ss.cat .

Example: cp tal_ss.cat my_tal_ss.cat

After modifying the entries in my_tal_ss.cat you would put the following your rtserver.cm file:

setopt catalog_file some_directory/my_tal_ss.cat

As a final note modifying the entries in the tal_ss.cat resource file may hinder Tibco Support when examining a submitted trace_file produced with the modified resource file entries.

How do the entries in the $RTHOME\standard\tal_ss.cat resource filemap to Trace Levels?