These principles apply to TRS configuration properties:
Service library properties apply to the service library as a whole. TRS configuration properties are service library properties, except the service-level properties Description, EnableAtStartup and ClientIdleTimeout. How a TRS service operates is affected by the values of its parent service library.
Configuration properties are not case sensitive. In this guide, property names appear in mixed case for easier reading.
A TRS configuration file consists of the following lines. (For a sample file, see “Sample TRS configuration file”.)
The name of the TRS service library is shown in brackets on the first line of the file. This character string must appear at the top of the file.
The subsection name, Transaction Router Service Property, is shown in braces on the next line. This character string must appear under the service library line. There are no other subsections.
Each configuration property and its value are shown on individual lines. Configuration properties can be listed in any order within their subsection. If a configuration property line is deleted or omitted from the file for any reason, the default value for that property is applied automatically. See “Service library configuration properties” for the default values of each configuration property.
The TRS service name is shown in brackets and must conform to the following rules:
Service names must be unique within the first 11 characters in length.
The initial character must be an alphabetic character (a–z, A–Z).
Subsequent characters can be alphabetic or numeric characters or the underscore (_) character.
To add a service named “ServiceA,” the following line must exist in the TRS configuration file:
[ServiceA]
For a client to successfully connect to a service, the service name must correspond to a query type entry in the client interfaces file. For an explanation of query type entries and how to add them to the interfaces file, see the Mainframe Connect DirectConnect for z/OS Option Installation Guide. When a client connects to DirectConnect, it specifies a service name, as shown in the following isql example:
isql -Usa -P -SServiceA
go
where ServiceA is the service name (or server name to the client).
You can include comments in the TRS configuration file. Each comment must be on a separate line and begin with a semicolon or “#” symbol.