When you say the script is there, is that on the installed system ("scripts" folder of the IFL installation) or the "scripts" folder when rebooted to the IFL job (/tbu/scripts)? You may just need to run makeGRUB and Create & Install the files again so they are up to date.

That scripts that are in the IFL installation's "script" folder are included in the build when you run makeGRUB. It's recreating the files used by GRUB for booting.

For example, if you have "myscript1" in the "scripts" folder and run makeGRUB to create and install the booting files and then want to add "myscript2" you would need to put "myscript2" into the "scripts" folder and then run makeGRUB again to create and install the booting files. Both "myscript1" and "myscript2" will then be included in the booting files (assuming "myscript1" still exists in the "scripts" folder). Basically, you want your current scripts (those being used) in the "scripts" folder of your IFL installation so they get included.

Correct. The script name is passed as part of the cron job command. For example (from the KB article) the script "myscript" would be run by the cron job: 30 5 * * Sun root /usr/local/bin/iflreboot myscript

This works the same as if you ran iflreboot manually and specified a script to run. The script specified has to exist in the IFL booting files, though, or it won't be found.

Some scripting would probably be necessary. Depending on your goals you might get by with something simple (backup name/method based on month, for example) or even several different cron jobs (monthly or monthly/quarterly).