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.