For the run window, you cannot specify anything greater than 24 hours, i.e. 86400 seconds, for the "bpplsched" command, but you can for the "bpplschedrep" command. And also note how the "bpplsched" command has a "-window" switch, whereas the "bpplschedrep" command does not and instead has a "-N start duration" switch, where N is a number representing a week day.
i) You want your run window to be 06:00 to 22:00 the next day, but this is not possible with only the "bpplsched" command on its own.
ii) If you specify "-window 21600 86400" then this would mean that the backups can and will start at 00:00 on 31st Dec. But you don't want this.
iii) Specifying a run window using the "-window start duration" on the "bpplsched" command means... setting a run window on every day of the week. But you don't want this.
iv) A possible option is to specify "-window 21600 64800", i.e. from 06:00 to midnight. This is the backup "window opportunity to start", i.e. a backup job which is actually started during this window will not be cancelled when the window expires. However, any queued backups not yet started will expire when the window closes. But you want to allow backups to start up until 22:00 the next day.
v) The solution is to use two commands, and because this year the 31st Dec is on a Saturday, so we need to specify day 6 in the second command, so maybe something like this:
# bpplsched TEST01 -add Annual -cal 1 -st FULL -rl 11 -incl 12/31/2016
# echo "$((6*3600))"
21600
# echo "$((18*3600))"
64800
# echo "$((22*3600))"
79200
# echo "$((64800+79200))"
144000
# bpplschedrep TEST01 Annual -6 21600 144000
...but you will need to adjust this each year, because next year (2017) the 31st Dec is probably not on a Saturday...
...you won't need the "echo" commands in your script, that is just me working out...
...start time of 06:00 = 21600 seconds
...seconds until end of day = 18 hours * 3600 = 64800...
...seconds from 00:00 to 22:00 = 22 * 3600 = 79200...
...so your run window duration is 64800 + 79200 = 144000.
HTH.
