Skip to Content

Control-M for SAP PARMC.9.0.21.214

BMC Software is releasing Control-M for SAP patch PARMC.9.0.21.214 to correct the following problems in Control-M for SAP on UNIX and Windows.

You need to install this patch on top of Control-M for SAP 9.0.21.200. 

Corrected Problems

The following table describes the problems that are corrected in Control-M for SAP PARMC.9.0.21.214.

Tracking Number

Patch

Description

WBL-332497

CTM-13102

PARMC.9.0.21.214Centralized connection profile cache files are not removed during the New Day procedure.

WBL-284183

CTM-10257

PARMC.9.0.21.214

The View Job Steps action in a Control-M for SAP job definition fails and generates the following error message:

Socket closed due to unknown reason.

WBL-326396

CTM-12875

PARMC.9.0.21.214

(Windows only) The SAP plug-in tracker does not start on Windows if JRE version 17 or higher is installed.

WBL-337995

CTM-13309

PARMC.9.0.21.214

Job Name, Job Count, and Process Log details do not appear in the Process Chain job output.

WBL-339251

CTM-13371

PARMC.9.0.21.214

SAP R3 jobs fail if they were configured to detect child jobs prior to a Control-M for SAP Patch PARMC.9.0.21.202 installation and the SAPR3-DETECT_CHILD_JOBNAME variable is missing in the Variable attribute.

WBL-342788

CTM-13563

PARMC.9.0.21.214The SAP plug-in tracker does not track jobs that are configured with a centralized connection profile.

WBL-346485

CTM-13682

PARMC.9.0.21.214

The following error message appears in many log files in the Control-M Agent proclog directory:

OS_FILE_fopen failed to open file: ./procid/3BI5V_106.DAT. mode: r. errno=2, No such file or directory

WBL-346118

CTM-13654

PARMC.9.0.21.214

The Control-M for SAP Java process does not shut down when it is scheduled to be recycled.

WBL-302615

CTM-12064

PARMC.9.0.21.214

Control-M for SAP jobs fail when a variant name contains Latin-1 special characters and generate the following error message :

Variant <variant name> for report <report name> does not exist.

WBL-355976

CTM-13953

PARMC.9.0.21.214

Control-M for SAP jobs fail if they are configured to include step details which contain non-printable characters in the job output and trigger the following error message in the job output:

Request sent to account <connection profile name> failed. Please verify that the account is available.

WBL-369086

CTM-14664

PARMC.9.0.21.214

Control-M for SAP child jobs do not run in the correct folder if the folder is configured with a time zone.

WBL-380404

PARMC.9.0.21.214

Control-M for SAP jobs might fail and NullPointerException appears in the log files if a centralized connection profile is used to concurrently run dozens of jobs.

WBL-301343

CTM-12028

PARMC.9.0.21.207The p_ctmag process memory increases over time when the Agent executes SAP jobs.

WBL-302877

CTM-12072

PARMC.9.0.21.207Data archiving jobs fail with the following error message:
Cannot run a parent job. The extractor process is down.

WBL-289532

CTM-11479

PARMC.9.0.21.207The Extractor process fails on Control-M SaaS with the following error message in the logs:
Invalid argument -TOKEN

WBL-286111

CTM-10336

PARMC.9.0.21.207Control-M for SAP jobs fail with the following error when jobs that utilize different centralized connection profiles run concurrently:
Failed to find account

WBL-285130

CTM-10276

PARMC.9.0.21.207Connection profile cache files are not removed during the New Day procedure.

WBL-283882

CTM-10244

PARMC.9.0.21.207SAP jobs fail with the following error if the jobs are set with a Centralized Connection Profile and the connection profile is not configured to English:
JCO_ERROR_LOGON_FAILURE

WBL-279463

CTM-10059

PARMC.9.0.21.207Watch for an SAP event job fails if thousands of events exist in SAP Events History table.

WBL-268495

CTM-9573

PARMC.9.0.21.207(Windows only) The SAP Extractor process unexpectedly terminates when it tries to detect Spawned jobs.

WBL-272560

CTM-9799

PARMC.9.0.21.207Event Watcher fails to run jobs when the event parameter is empty.

Installing the Patch on UNIX

This procedure describes how to install Control-M for SAP patch PARMC.9.0.21.214 on UNIX.

Before You Begin

  • Verify that Control-M for SAP 9.0.21.200 is installed before you install this patch.
  • Verify that no Control-M jobs are executing on the Agent.

Begin

  1. Download the installation package from S3 to a temporary directory. Do not download the package to the Control-M/Agent directory.
  2. Extract the patch tar.Z file with the following command:
    zcat PARMC.9.0.21.214_unix.tar.Z     | tar -xvf -
  3. Log on to the Control-M for SAP user account under the Control-M/Agent installation.
  4. Run the following command to stop the Control-M/Agent processes:
    shut-ag
  5. If the SAP Extractor process is running, run the following command to stop it:
    shut-xt
  6. Run the following command to stop the Control-M for SAP process:
    sapcmbe.sh stop
  7. Verify that the extracted file permissions are set to 755.
  8. From the directory where you extracted the patch, run the the following command and follow the on-screen instructions:
    ./setup.sh
  9. Run the following command to start the Control-M/Agent processes:
    start-ag
    The Control-M for SAP process starts automatically and does not require manual startup.
  10. If you need to run the Control-M for SAP Extractor process, run the following command:
    start-xt

Installing the Patch on Windows

This procedure describes how to install Control-M for SAP patch PARMC.9.0.21.214 on Windows.

Before You Begin

  • Verify that Control-M for SAP 9.0.21.200 is installed before you install this patch.
  • Verify that no Control-M jobs are executing on the Agent.

Begin

  1. Log in to the host where Control-M/Agent is installed with administrator privileges.
  2. Download the installation package from S3 to a temporary directory. Do not download the package to the Control-M/Agent directory.
  3. Extract the PARMC.9.0.21.214_windows_x86_64.zip file.
  4. Stop the Control-M/Agent services.
  5. If the SAP Extractor process is running, stop the Control-M plug-in for SAP Extractor service.
  6. Run the following command to stop the Control-M for SAP process:
    <Agent_installation>\cm\SAP\EXE\sapcmbe.cmd stop
  7. Navigate to the temporary directory.
  8. Run the following command from the directory with the extracted files:
    PARMC.9.0.21.214_windows_x86_64.exe
  9. Start the Control-M/Agent services. The Control-M for SAP process starts automatically and does not require manual startup.
  10. If you need to run the Control-M for SAP Extractor process, start the Control-M plug-in for SAP Extractor service.

Uninstalling the Patch from UNIX

This procedure describes how to uninstall Control-M for SAP patch PARMC.9.0.21.214 from UNIX.

Before You Begin

  • Verify that no Control-M jobs are executing on the Agent.

Begin

  1. Log in to the Control-M for SAP user account where Control-M/Agent is installed.
  2. Run the following command to stop the Control-M/Agent processes: 
    shut-ag
  3. If the Control-M for SAP Extractor process is running, run the following command to stop it:
    shut-xt
  4. Run the following command to stop the Control-M for SAP process: 
    sapcmbe.sh stop
  5. Navigate to <agent root dir>/ctm/patches
  6. Run the following script:
    PARMC.9.0.21.214/unInstall_PARMC.9.0.21.214.sh
  7. Run the following command to start the Control-M/Agent processes: 
    start-ag
  8. If you want to start the Control-M for SAP Extractor process, run the following command:
    start-xt

 Uninstalling the Patch from Windows

This procedure describes how to uninstall Control-M for SAP patch PARMC.9.0.21.214 from Windows.

Before You Begin

  • Verify that no Control-M jobs are executing on the Agent.

Begin

  1. Log in to the host where Control-M/Agent with Control-M for SAP is installed with administrator privileges.
  2. Stop the Control-M/Agent service.
  3. If the SAP Extractor process is running, stop the Control-M plug-in for SAP Extractor service.
  4. Run the following command to stop the Control-M for SAP process:
    <Agent_installation>\cm\SAP\EXE\sapcmbe stop
  5. From the Control Panel, uninstall Control-M for SAP 9.0.21.214.
  6. Start the Control-M/Agent service.
  7. If you need to run the Control-M for SAP Extractor process, start the Control-M plug-in for SAP Extractor service.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

Control-M SaaS