(a) TP1/Client/W

_s version of the function

 
#include <dcvclt.h>
DCLONG dc_clt_open_notification_s(HWND hWnd,
                                  DCCLT_ID *ntfid,
                                  char *defpath,
                                  unsigned short port,
                                  DCLONG flags)
 

Non-_s version of the function

 
#include <dcvclt.h>
DCLONG dc_clt_open_notification(unsigned short port,
                                DCLONG flags)
 

(b) TP1/Client/P

_s version of the function

 
#include <dcvclt.h>
DCLONG dc_clt_open_notification_s(HWND hWnd,
                                  DCCLT_ID CLTFAR *ntfid,
                                  char CLTFAR *defpath,
                                  unsigned short port,
                                  DCLONG flags)
 

Non-_s version of the function

 
#include <dcvclt.h>
DCLONG dc_clt_open_notification(unsigned short port,
                                DCLONG flags)
 

The dc_clt_open_notification_s function creates an environment for using the facility for receiving one-way messages from the server.

The dc_clt_open_notification_s and dc_clt_close_notification_s functions are used in a pair.

• hWnd
  Specify NULL.
  
• ntfid
  Specify a pointer to the area for receiving the one-way message reception ID.
  
• defpath
  Specify the path name of the client environment definition file. The path name must be specified with the full path or with a relative path from the current drive and the current directory. The following shows the order in which files are loaded when the path name is specified.
  
  • In TP1/Client/P
    Client environment definition files are loaded in the following order:
    1. The BETRAN.INI file in the Windows directory
    2. The client environment definition file specified in the defpath argument
    The definitions in both the client environment definition file and the BETRAN.INI file take effect.
    If the same definition is specified in each file with a different value, the value specified in the client environment definition file takes effect.
    If neither the client environment definition file nor the BETRAN.INI file contains the necessary specification, TP1/Client/P uses the defaults.
    
  • In TP1/Client/W
    All definitions specified in the environment variables will be invalid. TP1/Client/W uses the defaults for definitions that are not specified in the client environment definition file specified in the defpath argument.
    
  You can omit the path name by specifying NULL at the beginning of the defpath argument. The following describes the operation when the path name is omitted.
  
  • In TP1/Client/P
    TP1/Client/P uses the BETRAN.INI file in the Windows directory as the client environment definition file. If the BETRAN.INI file does not exist or if the contents of the definition file are invalid, TP1/Client/P uses the defaults.
    
  • In TP1/Client/W
    TP1/Client/W uses the values specified in the environment variables. If an environment variable is not specified, TP1/Client/W uses the default.
    
  The following describes operation when the client environment definition file specified in the defpath argument does not exist or when the contents of the definition file are invalid.
  
  • In TP1/Client/P
    TP1/Client/P uses the BETRAN.INI file in the Windows directory as the client environment definition file. If the BETRAN.INI file does not exist or if the contents of the definition file are invalid, TP1/Client/P uses the defaults.
    
  • In TP1/Client/W
    TP1/Client/W uses the defaults. The values specified in the environment variables will be invalid.
    
• port
  Specify a client's port number between 5001 and 65535. Specify a unique port number for each process or thread when multiple processes or multiple threads are executed simultaneously on the same machine.
  
• flags
  Specify DCNOFLAGS.
  

• ntfid
  Specifies the area for containing the returned one-way message reception ID.
  

Return value	Value (decimal)	Meaning
DC_OK	0	The function normally terminated.
DCCLTER_INVALID_ARGS	-2501	The value specified in an argument is incorrect.
DCCLTER_PROTO	-2502	The dc_clt_open_notification function has already been executed. This value is not returned if the dc_clt_open_notification_s function is executed.
DCCLTER_FATAL	-2503	Initialization failed. Alternatively, the client environment definition is specified incorrectly.
DCCLTER_NO_BUFS	-2504	A necessary amount of buffer could not be allocated.
DCCLTER_PORT_IN_USE	-2547	The specified port number has already been used.

• After the dc_clt_open_notification_s function is terminated normally, always issue the dc_clt_close_notification_s function. If the dc_clt_close_notification_s function is not issued, the resource used by the dc_clt_open_notification_s function may remain.
• Specify a unique port number in the port argument for each process or thread when multiple processes or multiple threads are executed simultaneously on the same machine. Do not specify a port number for use by the operating system or other programs even if one can be specified in the port argument. If you specify a port number in this case, response data might not be received correctly. The port numbers used by the operating system depend on the operating system. For details, see the documentation of your operating system.
• In TP1/Client, you can use a different client environment definition for each dc_clt_open_notification_s function call. To do so, create a separate client environment definition file for each dc_clt_open_notification_s function call, and specify the file name in the defpath argument of the function.