Several solutions here for implementing this type of 'GROUP' control for these tasks. The method chosen really depends on the number of resources that you would need to manually control as a 'group'. Meaning, if it is for just a handful of resources, then the best method may be to add 'logic' to just handle these resources rather than a full blown solution such as adding a 'GROUPNAME' column to your STCTBL if the logic is only for a handful of resources.
#1) If the TYPE column is not being used for these MSM resources, then simply use this column, setting TYPE to something like MSM. Then if using the SSMCNTL sample control rule, or logic similar to it, a console command like SSM PT TYPE=MSM to stop all TYPE=MSM and SSM ST TYPE TYPE=MSM to start all can be issued.
#2) Designate the 'first' task to start (last one to stop) as the 'primary' control resource, and then in the UP_DOWN/DOWN_UP actions for that primary resource drive an OPS/REXX pgm (STARTMSM/SHUTMSM) that has logic to set DS for other components or invoke the supplied STATESET OPS/REXX pgm as the action with the SUBREQ() or PREREQ() options depending on UP_DOWN/DOWN_UP
#3) Simply add logic in SSMCNTL sample rule or similar pseudo SSM control rule that allows for something like SSM START MSM/SSM STOP MSM, and the supporting SQL update logic simply sets the DESIRED state "where JOBNAME like 'MSM%'" to cntl MSM components.
#4) Add a GROUPNAME column to the STCTBL and then adjust supporting code (like SSMCNTL) to manipulate via the GROUPNAME column (SSM SG GROUP=MSM to start a group, or SSM PG GROUP=MSM) to stop a group.
An Upcoming "Agile Feature" (incremental) PTF will soon be available for #4 (adding group column and then having logic in SSMCNTL to control the group) if you chose this method and want to use a distributed sample for this logic and if it fits your requirements.