Notes on TP1/Client/P

The environment variables are analyzed during the processing of the dc_clt_cltin_s function and the dc_rpc_open_s function. Therefore, do not change the client environment definition after you call the dc_clt_cltin_s function. Similarly, do not change the client environment definition after calling the dc_clt_open_notification_s function.
In TP1/Client/P, you can use a different client environment definition for each dc_clt_cltin_s function call. To do so, create a separate client environment definition file for each dc_clt_cltin_s function call, and specify the file name in the defpath argument of the function. This information also applies to the following functions:
- dc_clt_accept_notification_s
- dc_clt_cancel_notification_s
- dc_clt_open_notification_s
TP1/Client/P first accesses the betran.ini file in the Windows directory to read the definition. It then accesses the files specified in the defpath arguments so that the following functions can read the definition items. Definition items loaded later overwrite those loaded previously.
- dc_clt_cltin_s
- dc_clt_accept_notification_s
- dc_clt_cancel_notification_s
- dc_clt_open_notification_s
If any definition items that are not specified in any of the files specified in the defpath arguments of the above functions are contained in the betran.ini file in the Windows directory, those definition items take effect.