The time-based scheduling subservice shall reject any instruction to delete a time-based scheduling group if any of the following conditions occurs:
that instruction refers to a group that does not exist;
that instruction refers to a group that has associated activities.
This clause implies that the check on whether a group to be deleted has an associated activity is done as part of the Start Check for the deletion command. However, a few lines later, clause 6.11.6.2.2h states:
For each valid instruction to delete all time-based scheduling groups, the time-based scheduling subservice shall:
for each group that has no associated activity, delete the identifier of that group;
for each group that has associated activities, generate a failed execution notification for that group.
This clause instead implies that the check on whether a group to be deleted has an associated activity is done as part of the execution of the command itself.
The CORDET Extension of the PUS Framework puts the check in the Start Action of the Group Delete command (11,23).
Clause 6.11.6.2.2d states:
This clause implies that the check on whether a group to be deleted has an associated activity is done as part of the Start Check for the deletion command. However, a few lines later, clause 6.11.6.2.2h states:
This clause instead implies that the check on whether a group to be deleted has an associated activity is done as part of the execution of the command itself.
The CORDET Extension of the PUS Framework puts the check in the Start Action of the Group Delete command (11,23).