This is the correct behavior of Control-M Server.
Control-M Parameter Guide explains how it works:
----------------------------------------------------------------------------
When Do Forcejob forces a job that belongs to a SMART Table, it treats it as a regular job and forces it alone (that is, without a SMART Table).
----------------------------------------------------------------------------
Additional Information
Request For Enhancement was implemented to change the default behavior:
BMPM008499: You can now determine, for a Do Force action, how to force a job that belongs to a Group Scheduling table. Set the new AutoEdit parameter INTO_TABLE_ORDERID to one of the following:
- LEGACY: Force the new job into the Scheduling Group of the job executing the Do Force action. The forced job must be defined within the same Scheduling Group.
- <Order ID of an existing Group Scheduling table>: Force the new job into the Scheduling Group of the specified Order ID. The forced job must be defined within the same Scheduling Group.
- ALONE: The new job is forced individually. The new job does not belong to any Scheduling Group.
- NEWG: Force the new job into a newly created Scheduling Group.
- LAST: Force the new job into the last ordered instance of the Scheduling Group in the Active Jobs file.
Notes:
If the forced job does not belong to any Group Scheduling table, the INTO_TABLE_ORDERID parameter is ignored and the job is forced individually.
If the INTO_TABLE_ORDERID parameter is not defined, the behavior remains as in Control-M/Server 6.4.01 fix pack 4:
If the Jobname parameter is empty in the Do Force action, then the NEWG value is used.
If there is a Jobname in the Do Force action, then the ALONE value is used.
To change the default behavior add %%INTO_TABLE_ORDERID=LEGACY autoedit variable all Smart Table jobs that performs a DoForce action. The new job will be added on the same Smart Table.
Legacy ID:KA389349