Behavior when acknowledging a Send daemon termination synchronization request

The behavior of the Send daemon when a termination synchronization request is issued varies depending on the status of the daemon.

The Send daemon immediately terminates in both Process Synchronization mode and Forced Stop mode if the Send processing is not in progress.

If the Send daemon is carrying out the Send processing or interacting with the receiving side, the behavior of the daemon when a termination synchronization request is acknowledged is different in Process Synchronization mode and in Forced Stop mode. The differences in behavior for Process Synchronization mode and Forced Stop mode are explained in Table 5.1 .

Table 5.1 Behavior of Send Daemon When Termination Synchronization Request Is Acknowledged (Processing Is in Progress)
Sending Side Status	Receiving Side Status	Process Synchronization Mode		Forced Stop Mode
Sending Side Status	Receiving Side Status	Termination Procedure of Send Daemon	Sending Side Processing after Send Daemon Is Terminated	Termination Procedure of Send Daemon	Sending Side Processing after Send Daemon Is Terminated
In Send Queue	-	Deletes the records in the Send Queue and then terminates	-	Keeps the records in the Send Queue and then terminates	-
In Resend Queue	-	Keeps the records in the Resend Queue and then terminates	-	Keeps the records in the Resend Queue and then terminates	-
Executing Pre-send Job (*1)	-	Does not wait for the Job to complete and terminates immediately	The Job is executed asynchronously with the termination of the daemon (*2)	Does not wait for the Job to complete and terminates immediately	The job execution is not completed and the transfer is not carried out
Sending	Receiving (Transferring)	Waits until the transfer is complete and then terminates	Executes Successful Job or Unsuccessful Job depending on the transfer result	Forcibly stops the transfer and then terminates	Outputs the error code 590 to the Send Log and terminates unsuccessfully (*3)
	CSV Interface Processing	Waits until the processing is complete and then terminates	-	Forcibly stops the Sending processing and then terminates	Outputs the error code 590-271 to the Send Log and terminates unsuccessfully (*4)
	Executing Successful Job on Receiving Side (Notification 'J')	Waits until the Job is complete and then terminates	-	Forcibly stops the Sending processing and then terminates	Outputs the error code 590-271 to the Send Log and terminates unsuccessfully (*4)
Executing Successful Job on Sending Side	-	Does not wait for the Job to complete and terminates immediately	The Job is executed asynchronously with the termination of the daemon (*2)	Forcibly stops the Job and then terminates	Sending terminates successfully
Executing Unsuccessful Job on Sending Side	-	Does not wait for the Job to complete and terminates immediately	The Job is executed asynchronously with the termination of the daemon (*2)	Forcibly stops the Job and then terminates	-
Connecting or Standby	-	Waits until the retries for receiving are complete and then terminates	-	Forcibly stops the connection with the receiving side and then terminates	Outputs the error code 590 to the Send Log and terminates unsuccessfully (*3)
In Auto Resend Queue	-	Waits until the retries for receiving are complete and then terminates	-	Deletes the records in the Auto Resend Queue and then terminates	The deleted records are placed in the Resend Queue
-	Executing Successful Job on Receiving Side (Notification 'T')	Does not wait for the Job to complete and terminates immediately	The Job is executed asynchronously with the termination of the daemon (*2)	Does not wait for the Job to complete and terminates immediately	The job runs until it is completed
-	Executing Unsuccessful Job on Receiving Side	-	-	-	-

Not applicable

*1	:	The Pre-send Job is executed asynchronously with the Send daemon. This is because the job for the Send File is executed by the Send File command (utlsend), but the job for the Send Request is executed by the Observe process.
*2	:	After the daemon is terminated, if a failover occurs while an asynchronous Job is being executed, the job may be stopped by the clustering software before the job is completed.
*3	:	If error code 590-000 is output to the Send Log, auto resending (on the sending side) is carried out after a failover.
*4	:	If error code 590-271 is output to the Send Log, auto resending (on the sending side) is not carried out because the transfer of the Send files has completed.