Possible values:

• Report. Policy Manager checks each NSF file listed in the [NSF] sections of the initialization file, to determine whether it can migrate the file's contents. Policy Manager creates a new initialization file, which contains a count of all the files that are not ready for migration. In the new initialization file, any NSF file which cannot be migrated has the entry DoNotProcess=True added to its [NSF] section. This setting prevents Policy Manager from attempting to process the file when it is next run in process mode.

  The new initialization file has the same name as the original, with a number appended to make it unique. For example, if the original file was called NSFMigration.ini, the new file is called NSFMigration_1.ini.

• Process. Policy Manager migrates items from the NSF files that are listed in the [NSF] section, and generates summary and detailed reports. Policy Manager also writes a new initialization file. You can use the new file to migrate any failed files when you have corrected the problems that prevented their migration. Each NSF file has a JobStatus entry added to its [NSF] section of the new initialization file. For example, the files that were successfully migrated have JobStatus=Processed added to the [NSF] section. Policy Manager does not attempt to migrate these files again when you use the new initialization file for the next migration run.

  The new initialization file has the same name as the original, with a number appended to make it unique. For example, if the original file was called NSFMigration.ini, the new file is called NSFMigration_1.ini.