For the stub source file name that is specified in the stbmake command, make sure that you specify the suffix .def that indicates an RPC interface definition file.

Use the Shift JIS character encoding for the RPC interface definition file.

When an OpenTP1 UAP is executed in a single-thread environment, it must not create threads other than the main thread. If the UAP creates a thread other than the main thread (multi-thread environment), it might malfunction and terminate abnormally. Note also that, because UAPs under OpenTP1 run in a multi-thread environment through use of a DLL, you must specify msvcrt.lib as a linked runtime library when you create a UAP.

If you use code such as JNI (Java Native Interface) that creates threads, program operation cannot be guaranteed.

Do not issue a function or method that terminates a process or a thread within a service function (SPP) or service method (SPP.NET). Issuing such a function or method might result in the following:

• Service functions (SPP) and service methods (SPP.NET) do not run as designed.
• Service requests to service groups fail.
• The UAP cannot be terminated.
• OpenTP1 cannot be terminated normally.

• If you use a library created by using Visual Studio on the user server, make sure that you embed a manifest file in the library. If a manifest file is not embedded, the user server might be shut down with termination status 0xC0000135.
• An object file created in a Visual Studio debug build might not run in an environment where Visual Studio is not installed. If you debug an object file in an environment where Visual Studio is not installed, check the contents of the linked DLL files and manifest file and create an appropriate manifest file. For details about manifest files, see the description of manifest files in the Visual Studio documentation.

In an environment in which Visual Studio and COBOL are both used, make sure that the environment variables for the language used for compilation are specified before the environment variables for any other language. If the environment variables for another language are specified first, unexpected linkage might result.

• Of the arguments of OpenTP1's COBOL UAP creation program, numeric data must be declared with COMP-5, not COMP.
• When you execute a UAP, do not set a large value for the OpenTP1 console's buffer size and window size (height). If you specify a large value, the correct console display might not result and the UAP might not run successfully.
• If you run a UAP created with Net Express, OpenTP1 console's title characters might be changed.
• If you use a UAP created with Net Express to display messages on the OpenTP1 console by using the DISPLAY statement of the COBOL UAP creation program, and you log off the system during UAP execution, the UAP might be shut down. To display messages, use CBLDCLOG('PRINT ') provided by OpenTP1.