*FLR - Force Full Backup

Type of backup activity

Full backups save all objects that are specified regardless of whether they have changed since the last time they were included in a backup.
Incremental backups save objects that have changed since the last time they were included in a full or incremental backup.
Cumulative incremental backups save objects that have changed since the last time they were included in a full backup.

Force full backup days
The Force full backup days field can be specified in the attributes for a control group or in the backup policy. If an incremental or cumulative incremental backup of a library is run with the Force full backup days field set to a number of days and a full backup of the library has not been done within the number of days, the incremental backup will be changed to a full backup.

When using this option, BRMS will check for the last full save of each of the libraries being saved regardless of:

which control group is running
which item in the control group includes the library

Example
A backup control group has an *ALLUSR entry and the Force full backup days field is set to 30. The last full save of *ALLUSR was 31 days ago. A full save of library MYLIB was done 10 days ago using a different control group or the Save Library using BRM (SAVLIBBRM) command. No other libraries have been saved since the full save of *ALLUSR. If an incremental backup is run using the control group, changes will be saved for MYLIB since it has been saved within the time specified for the Force full backup days field but full saves will be done for all other libraries since a full save has not been done for them within the time specified for the Force full backup days field.

NOTES:

Using this option may result in longer backup times as full saves may occur on days when they are normally not scheduled.
Any new libraries that have not being saved within BRMS will result in a full save