OpenTP1 Version 7 TP1/Client User's Guide TP1/Client/W, TP1/Client/P
- The environment variables are analyzed during dc_clt_cltin_s and dc_rpc_open_s function processing. 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/W, 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/W accesses the files specified in the defpath arguments so that the following functions can read the definitions:
- dc_clt_cltin_s
- dc_clt_accept_notification_s
- dc_clt_cancel_notification_s
- dc_clt_open_notification_s
If the value of the defpath argument is NULL, the environment variables are loaded into TP1/Client/W. If a file is specified in the defpath argument, the client environment definitions specified as environment variables do not take effect.
All Rights Reserved. Copyright (C) 2006, 2009, Hitachi, Ltd.