A load can be forced to rollback any records loaded if the number of reject records exceeds a given limit.
This is different from aborting the load based on the number of reject records. Hence it is possible to continue the load to the end regardless of the number of rejects found – but finally rollback if the number of rejects is too great. Note that if the load aborts because of the number of reject records, it also implicitly rolls back any records loaded.
It is also possible to force an unconditional rollback regardless of the number of reject records.
By default, a file is not rolled back unless the load aborts.
The ‘b’ and ‘B’ switches control rollback behaviour.