Is it possible to interrupt an offline IDXFIX operation?

Is it possible to interrupt an offline IDXFIX operation?
What are the side effects of pressing SIGINT or Ctrl+C during an offline PROUTIL -C IDXFIX ?
Are the changes already performed by IDXFIX committed to the database when the process is interrupted?

An offline proutil -c IDXFIX session can be interrupted by the user using Ctrl+C in the terminal running the command, or using SIGINT or SIGTERM on Unix.

An online proutil -c IDXFIX session should first be interrupted by disconnecting the user through PROMON or from the PROSHUT cmd line since the operation is run SHARED-LOCK:

Example:

$  proshut dbname -C disconnect <usernum>

or

$  promon dbname
8.  Shut Down Database
1  Disconnect a User
<enter the user number>

The user number can be obtained from either the database lg file: (The user number is 5 in this case)

[2011/02/07@15:06:44.731+0100] P-5000       T-6012  I IDXFIX  5: (452)   Login by uuser on batch.
[2011/02/07@15:06:44.736+0100] P-5000       T-6012  I IDXFIX  5: (7129)  Usr 5 set name to Idxfix.
[2011/02/07@15:06:44.738+0100] P-5000       T-6012  I IDXFIX  5: (451)   proutil -C idxfix session begin for uuser on batch

or from the PROMON, User Control menu itself, look for user Type = IDXF

1.  User Control 

Usr Name     Type      Wait  Table               Dbkey     Trans      PID Sem Srv Login  Time
  5 Idxfix   IDXF       --      0                    0         0     4604   0   0 02/07/11 15:07


Online or Offline, when the IDXFIX session is interrupted in “report and fix mode’ all changes caused by IDXFIX on the database up to the point of the interruption will be kept in the database. viz: The committed changes will not be rolled back. In other words, interrupting an IDXFIX operation in “report and fix mode’, should not cause corruption because changes performed by IDXFIX up to and including the point of process termination, are logged in the before-image file (and in the after-image files, if after-imaging is enabled), so normal crash recovery will take place and any incomplete index changes will be undone.

When run Online, ending the process will not necessarily mean that IDXFIX will be ended immediately. It will first need to backout the last IDXFIX transaction which, should be small - this is to ensure the data integrity. Since it is run SHARED-LOCK online, when the operation is terminated while the IDXFIX user is waiting on a lock for example, the process will not end before IDXFIX gets that lock. IDXFIX may then "seem to grind to a halt", while waiting on that lock. Please refer to the Article 000020051 below for further details on this behaviour.

Progress Article(s):

"What is the difference between idxfix idxcheck and idxbuild?"
"Why does idxfix ALL option 3 online seem to grind to a halt?"