Initializing Communications with exit_child_init() or exit_child_init_c()
Use the exit_child_init() or exit_child_init_c() function as the first line of code of the user exit program to initialize communications. This function performs a check to verify that each side is ready to communicate. Following is the format of the exit_child_init() function:
int exit_child_init( char * logfile )The exit_child_init() or exit_child_init_c() function has the following parameter:
| Parameter | Description | Value |
|---|---|---|
| logfile | The name of the log or trace file that is opened for use by the user exit programs. Because the file open and security exit are started by SMGR, which is running as root, the exits also run as root. Running the exits as root can cause problems with file permissions of the log file, so logfile enables you to easily change owner or permissions on the file. See the sample exit in d_dir/ndm/src/exit_skeleton.c for more details. | Name of log file or trace file |
The exit_child_init() or exit_child_init_c() function have the following return codes. Return codes for the function are defined in ndmapi.h.
| Return Code | Description |
|---|---|
| GOOD_RC | Communications between IBM® Connect:Direct® and the user exit program were successfully initialized. |
| ERROR_RC | Communications between IBM Connect:Direct and the user exit program could not be initialized. |