The trscopy utility creates a copy of a DirectConnect TRS Library by using an existing TRS as a template to find all of the related source files.
This utility makes a copy of a TRS service library executable
available for all DirectConnect servers defined under the installation
area, but it sets up a sample service only under
the same DirectConnect server as provided on the command line.
The trscopy utility copies files with a base file name of the source TRS in the directory tree of the source DirectConnect server to files with a base file name of the target TRS in the directory tree of the target DirectConnect server.
For example, if you are using Windows, to create a new instance of the TRS LU62 Library (named new_trslu62), run the trscopy program with the appropriate arguments. Doing this produces two complete sets of the TRS LU62 files:
The original trslu62 executable and all its files
An executable named new_trslu62 and a copy of all of its files, with a base file name of new_trslu62, placed in the destination DirectConnect server subdirectory tree
Table 2-1 shows the TRS executable file names based on the platform:
Platform |
File name and extension |
---|---|
Windows |
trslu62.dll and trstcp.dll |
HP |
trslu62.sl and trstcp.sl |
AIX |
trslu62.so and trstcp.so |
Solaris |
trslu62.so and trstcp.so |
After you run trscopy, you must edit the new TRS Library’s configuration file and change the service name. Then, add this new service name to the SYBASE interfaces file on the client. For instructions, see the Mainframe Connect DirectConnect for z/OS Option Installation Guide.
The UNIX version of trscopy has an
option that automatically generates a new TRS name in the target
TRS library configuration file. Then, it adds that service to the
SYBASE interfaces file on the server.