TASM State Changes are Streamlined in Teradata 14.0 - comment by carrie

Interesting question.
 
This should work for you by just adding a new planned environment that is for the first 6 days of each month.
 
At each TASM event interval, all system events are checked to see if a health condition needs to be changed.   After that, all defined planned environments are checked to see if a different planned environment should now be in effect.   If more than one planned environment meets to current conditions (in your terms they overlap), then the planned environment with the highest ID number takes precedence.  This will usually be the one in the rightmost position in the state matrix.   If you add you planned environment for the first 6 days of each month after your other planned environments were defined, this new one will naturally be added in the rightmost position and will naturally be higher in precedence that the others.
 
Notice that in your state matrix the Always planned environment is in the leftmost position, and will have an ID of 1, so it will always be the lowest in precedence order. The further to the right of there, the higher the precedence position becomes.
 
If you are not sure about which planned environment has the highest ID (or the higher ID amongst two that overlap), you can validate this by looking at tdwmdmp -a output.   Under the heading "State and Event Information" it will show you each Operating Environment (same as planned environment) with its OPENV-ID and the precedence order it has.
 
Overlap will not matter because when the check on planned environments are made at the event interval, all planned environments that match the current time-of-day/day-of-week will be considered, and the one with the highest precedence among them wins.
 
If for some reason your planned environment for the first 6 days of the month is not in the rightmost position in your state matrix, you can drag it into that position.
 
Thanks, -Carrie