trnlnkrm
{[-A OpenTP1-provided-RM-name-to-be-added[,OpenTP1-provided-RM-name-to-be-added]...]
  [-D OpenTP1-provided-RM-name-to-be-deleted[,OpenTP1-provided-RM-name-to-be-deleted]...]
  [-a RM-name-that-is-not-provided-by-OpenTP1
   [,RM-name-that-is-not-provided-by-OpenTP1]...
 -s RM-switch-name[,RM-switch-name]...
 -o "RM-related-object-name[RM-related-object-name]..."
 [,"RM-related-object-name[RM-related-object-name]..."]...]
 [-d RM-name-that-is-not-provided-by-OpenTP1
   [,RM-name-that-is-not-provided-by-OpenTP1]...]
|[-n]}
[-C "compiler-option-name[compiler-option-name]..."]
[-B "linkage-option-name[linkage-option-name]..."][-l][-f][-P]

-A OpenTP1-provided-RM-name-to-be-added ~<1 to 31 alphanumeric characters>

Neither OpenTP1_ISM nor OpenTP1_XATMI can be specified as the name of an OpenTP1-provided resource manager to be added. There are no other differences.

-D OpenTP1-provided-RM-name-to-be-deleted ~<1 to 31 alphanumeric characters>

Neither OpenTP1_ISM nor OpenTP1_XATMI can be specified as the name of an OpenTP1-provided resource manager to be deleted. There are no other differences.

-o RM-related-object-name ~<alphanumeric>

If you specify multiple objects, enclose the entire list of objects in double quotation marks ("). If you specify paths of RM-related object names, use double backslashes (\\) as the delimiter. There are no other differences.

-C compiler-option-name ~<string of 1 to 512 characters>

If you specify compiler option names, enclose them in double quotation marks ("). There are no other differences.

-B linkage-option-name ~<string of 1 to 512 characters>

If you specify the names of linkage options that are used during library linkage processing, enclose the linkage option names in double quotation marks ("). There are no other differences.

-P

There is no need to specify this option because it is assumed to be specified by default. There are no other differences.

• You need a C compiler to execute this command. You must specify the folder containing the command in the PATH environment variable beforehand because Visual Studio's cl, link, and mt commands execute during execution of this command. You must also specify the LIB and INCLUDE environment variables to run the compiler successfully. For details, see the Release Notes.
• A manifest file will have been embedded in the executable file created by this command. For details about the manifest file, see the Windows documentation.
• When you execute this command, make sure that you specify the path of Visual Studio at the beginning of the PATH, LIB, and INCLUDE environment variables. If the path of Visual Studio is omitted, unexpected linkage might result.