I was wondering how SSMv3 handles a situation when a second copy of a task is started. I remember in SSMv2 there was a DUPE state that allowed certain actions to be taken to avoid starting a second copy. However, I don't see much mention of it in the literature for SSMv3. I happened to be looking at the STOPVTAM REXX which requires the SSMVTAM rule which due to Policy Editor, I am not using in my SSMv3 setup. In the SSMVTAM rule there is message processing for a DUPE message which made me think about this.
It doesn’t handle duplicate starts. This is more of a control issue rather than a policy issue.
Also the default policy does not have to be used so you can continue to use the samples or create your own rules that control starting and stopping .
Agreed. I was just wondering because I remembered it in the old sample rules, SSMv2, but didn't remember reading anything about it in SSMv3. One of the reasons I went to SSMv3 was because of the Policy Manager and everything it can do.