(a) TP1/Client/W

_s version of the function

 
#include <dcvclt.h>
DCLONG dc_clt_accept_notification_s(
                           HWND hWnd, char *defpath,
                           char *inf,
                           DCLONG *inf_len,
                           unsigned short port,
                           DCLONG timeout,
                           char *hostname,
                           char *nodeid, DCLONG flags)
 

Non-_s version of the function

 
#include <dcvclt.h>
DCLONG dc_clt_accept_notification(
                           char *inf, DCLONG *inf_len,
                           unsigned short port,
                           DCLONG timeout,
                           char *hostname, char *nodeid,
                           DCLONG flags)
 

(b) TP1/Client/P

_s version of the function

 
#include <dcvclt.h>
DCLONG dc_clt_accept_notification_s(
                           HWND hWnd, char CLTFAR *defpath,
                           char CLTFAR *inf,
                           DCLONG CLTFAR *inf_len,
                           unsigned short port,
                           DCLONG timeout,
                           char CLTFAR *hostname,
                           char CLTFAR *nodeid,
                           DCLONG flags)
 

Non-_s version of the function

 
#include <dcvclt.h>
DCLONG dc_clt_accept_notification(
                           char CLTFAR *inf,
                           DCLONG CLTFAR *inf_len,
                           unsigned short port,
                           DCLONG timeout,
                           char CLTFAR *hostname,
                           char CLTFAR *nodeid,
                           DCLONG flags)
 

This function waits for the message reported by the dc_rpc_cltsend function executed on the server side. This function stops waiting for the message if a timeout occurs before receiving the message. The timeout is specified by the timeout argument. On reception of the message, this function returns the return value, received message, host name of the message-originating server, and node identifier of the message-originating server, and control returns to the CUP. Before issuing this function, you do not need to issue the dc_clt_cltin_s and dc_rpc_open_s functions.

• hWnd
  Specify NULL.
  
• 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.
    
• inf
  Specify the area for storing the message sent from the server.
  
• inf_len
  Specify the length of the area for storing the message sent from the server. That is, specify the length of the inf argument. You can specify a value in the range from 0 to DCRPC_MAX_MESSAGE_SIZE^#.
  

  # If you specify 2 or a larger value for DCCLTRPCMAXMSGSIZE in the client environment definition, the value you specify is used rather than the value of DCRPC_MAX_MESSAGE_SIZE (1 megabyte).

• port
  Specify a client's port number between 5001 and 65535. Specify a unique port number for each process or thread if multiple processes or multiple threads are executed simultaneously on the same machine.
  
• timeout
  Specify a timeout value in seconds between 0 and 65535. Value 0 means an infinite wait.
  
• hostname
  Specify an area of 64 bytes^# or more for storing the host name of the server that sent the message. The host name is not stored if you specify NULL.
  

  # If you specify 00000008 for DCCLTOPTION in the client environment definition, this value is 256 bytes, not 64 bytes.

• nodeid
  Specify the 8-byte area for storing the node identifier of the server that sent the message.
  
• flags
  Specify DCNOFLAGS.
  

• inf
  Notification message from the server.
  
• inf_len
  Notification message length from the server.
  
• hostname
  Host computer name for the server that notified the message. An IP address in decimal dot notation is returned if resolution to a host name has failed. This value is not returned if you specify NULL.
  
• nodeid
  Node identifier for the server that notified the message. The node identifier is suffixed by a NULL character as shown below.
  

  

Return Value	Value (decimal)	Meaning
DC_OK	0	Normal termination
DCCLTER_INVALID_ARGS	-2501	Invalid argument
DCCLTER_FATAL	-2503	Unsuccessful initialization. Alternatively, the client environment definition is specified incorrectly.
DCCLTER_NO_BUFS	-2504	A necessary amount of buffer could not be allocated.
DCCLTER_NET_DOWN	-2506	Network error
DCCLTER_TIMED_OUT	-2507	A timeout occurred during reception of the message.
DCCLTER_SYSERR	-2518	System error
DCCLTER_VERSION	-2535	Different versions
DCCLTER_INF_TOO_BIG	-2546	The received message is too large for the CUP-provided area. The part that does not fit is truncated. Values have already been set in the hostname and nodeid arguments.
DCCLTER_PORT_IN_USE	-2547	The specified port number is already used.
DCCLTER_INVALID_MESSAGE	-2548	Invalid message received
DCCLTER_ACCEPT_CANCELED	-2549	The one-way message reception wait status was canceled by the dc_clt_cancel_notification_s function. Values have already been set in the inf, inf_len, and hostname arguments.

• Specify an area of 64 bytes^# or more for the hostname argument, and an area of 8 bytes or greater for the nodeid argument. If the area is smaller than the required value, the area may be corrupted during TP1/Client internal processing.
  

  # If you specify 00000008 for DCCLTOPTION in the client environment definition, this value is 256 bytes, not 64 bytes.

• 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_accept_notification_s function call. To do so, create a separate client environment definition file for each dc_clt_accept_notification_s function call, and specify the file name in the defpath argument of the function.