Behavior when acknowledging an Observe daemon termination synchronization request

When a termination synchronization request is issued to the Observe daemon, the daemon is immediately terminated in both Process Synchronization mode and in Forced Stop mode as long as the daemon is not carrying out an Observe processing instance.

However, if the Observe daemon is carrying out an Observe processing instance, the behavior of the daemon when a termination synchronization request is acknowledged is different in Process Synchronization mode and in Forced Stop mode.

Details of the behaviors are described in Table 5.3 .

Table 5.3 Behavior of Observe Daemon When Termination Synchronization Request Is Acknowledged (Processing Is in Progress)
Requestee-side Status	Process Synchronization Mode		Forced Stop Mode
Requestee-side Status	Termination Procedure of Observe Daemon	Requestee-side Processing after Observe Daemon Is Terminated	Termination Procedure of Observe Daemon	Requestee-side Processing after Observe Daemon Is Terminated
During Send Request Acknowledge (SEND)	Waits until the processing is complete and then terminates	-	Forcibly stops the processing and then terminates	Outputs the error code 592 to the Observe Log and terminates unsuccessfully
During Resend Request Acknowledge (RESEND)	Waits until the processing is complete and then terminates	Executes Successful Job or Unsuccessful Job depending on the transfer result	Forcibly stops the processing and then terminates	Outputs the error code 592 to the Observe Log and terminates unsuccessfully
During Job Execution Result Notification (HULSNDRC)	Waits until the processing is complete and then terminates	Executes Successful Job or Unsuccessful Job depending on the transfer result	Forcibly stops the processing and then terminates	Outputs the error code 592 to the Observe Log and terminates unsuccessfully
During Remote Job Execution (HULRJOB)	Does not wait for the processing (Job) to complete and terminates immediately	The Job is executed asynchronously with the termination of the daemon (*1)	Forcibly stops the Job (processing) and then terminates	Outputs the error code 592 to the Observe Log and terminates unsuccessfully
During Remote Job Execution (with Synchronous Transfer Specified) (HULRJOB)	Waits until the processing (Job) is complete and then terminates	-	Forcibly stops the Job (processing) and then terminates	Outputs the error code 592 to the Observe Log and terminates unsuccessfully
During Post-receive Job Result Notification (HULJOB)	Waits until the processing is complete and then terminates	-	Forcibly stops the processing and then terminates	Outputs the error code 592 to the Observe Log and terminates unsuccessfully
During Connection to HULFT Manager (HULADMIN)	Waits until the processing is complete and then terminates	-	Forcibly stops the processing and then terminates	Outputs the error code 592 to the Observe Log and terminates unsuccessfully

Not applicable

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.

To end the Observe daemon after the Remote Job is completed, execute the Remote Job in synchronous mode.