When spawned jobs or child jobs are created in SAP, these jobs are not being tracked or handled by Control-M for SAP. Jobs are stuck in an executing state or SAP child jobs are not spawned in Control-M.

Knowledge Article

When spawned jobs or child jobs are created in SAP, these jobs are not being tracked or handled by Control-M for SAP. Jobs are stuck in an executing state or SAP child jobs are not spawned in Control-M.
Control-M for SAP
Control-M/CM for SAP
Control-M for SAP all versions
Control-M for SAP is configured to monitor spawned jobs from SAP application server.

However, when the child jobs are created and finished in SAP, these jobs are not reflected in the Control-M/Enterprise Manager GUI under Monitoring.

The parent and/or child SAP jobs in Control-M GUI Monitoring stayed in executing state and do not change to ended ok.
Control-M for SAP Extractor process is not started. Control-M for SAP version upgrade will stop the running extractor process and this process will need to be started manually.

1) Verify that the Control-M for SAP Extractor process is running.

On Unix:
ps -ef | grep xt
Ensure one p_ctmxt process is running

On Windows:
Open task manager and look for a p_ctmxt process

2) If the Control-M for SAP Extractor process is not running, start it with the following steps:

On Unix:
Logon as the Control-M/Agent owner account
Execute the command: start-xt
If the command is not found, navigate to the $CONTROLM/cm/SAP/exe directory, then execute start-xt

On Windows:
Open Windows Services
Start the Windows Service "Control-M for SAP <Agent Instance> Extractor"

Additional information:
Refer to article 000018086 to enable the automatic start up of the Control-M for SAP Extractor process when the Control-M/Agent is started.
    Control-M for SAP
    Control-M/CM for SAP
    Control-M for SAP all versions
    Control-M for SAP
    Control-M/CM for SAP
    Control-M for SAP all versions
    Attachment(s):