Control-M/Server Management

The Control-M/Server management tab enables you to troubleshoot, manage, and monitor self-hosted Control-M/Servers and their databases, Services, Agents, and Gateways, as described in the following procedures:

• Adding a Self-Hosted Control-M/Server

• Pausing a Self-Hosted Control-M/Server

• Disabling a Self-Hosted Control-M/Server

• Recycling a Self-Hosted Control-M/Server

• Starting Up the Self-Hosted Control-M/Server

• Shutting Down the Self-Hosted Control-M/Server

• Ignoring a Self-Hosted Control-M/Server

• Recycling a Self-Hosted Service

You can navigate to the Notification Destinations and self-hosted Control-M/Server System Parameters from the Control-M/Servers toolbar, as described in Notification Destinations and Configuring Control-M/Server System Parameters.

Helix Control-M/Servers communicate with AWS services (SQS, S3, and IoT) via an HTTPS protocol on port 443. If your organization blocks internet access, ask your network administrator to grant outgoing access to the following URLs:

• *.controlm.com:443 (HTTPS protocol) (outgoing only)

• *.amazonaws.com:443 (outgoing only)

Adding a Self-Hosted Control-M/Server

This procedure describes how to add a self-hosted Control-M/Server or Control-M for z/OS to your environment, which enables you to divide job workflows based on load balancing requirements, geographic distribution, or organizational structure.

Before You Begin

• Verify that the self-hosted Control-M/Server is unmanaged by a Control-M/EM, as described in Unmanaging a Control-M/Server.

Begin

1. From the icon, select Configuration.

   The Configuration domain opens.

2. From the drop-down list, select Control-M/Servers.

   The Control-M/Servers tab appears.

3. Toggle on Self-Hosted.

   The Self-Hosted Control-M Servers tab appears.

4. Click , then click Add Server.

   The Add Self-Hosted Control-M/Server dialog box appears.

5. Define the self-hosted Control-M/Server or Control-M for z/OS parameters, as described in Self-Hosted Control-M/Server Component Parameters, and then click Add.

   A Self-Hosted Control-M/Server Added confirmation box appears.

   The added self-hosted Control-M/Server or Control-M for z/OS appears in the Self-Hosted Control-M/Servers tab, and Ready to Connect appears in the Status column of the added component.

6. Connect the self-hosted Control-M/Server or Control-M for z/OS to Helix Control-M, as described in Helix Control-M Unified View Migration.

Self-Hosted Control-M/Server Component Parameters

The following table describes the parameters that enable you to add a self-hosted Control-M/Server or Control-M for z/OS, as described in Adding a Self-Hosted Control-M/Server.

Parameter	Description
Name	Defines the logical name of the self-hosted Control-M/Server or Control-M for z/OS. Rules: Alphanumeric Latin Characters: 1–20 Case-Sensitive: Yes Invalid Characters: Whitespace, %, &, (, ), $, ;, <, >, /, `, *, and \.
Host	Defines the self-hosted Control-M/Server or Control-M for z/OS hostname.
ID	Defines a unique three-character ID, such as 999 or NYC, which Helix Control-M uses to identify each self-hosted Control-M/Server or Control-M for z/OS. Default: The next available consecutive ID.

Pausing a Self-Hosted Control-M/Server

This procedure describes how to pause a self-hosted Control-M/Server or Control-M for z/OS, which enables you to keep jobs from executing until you resume the self-hosted Control-M/Server.

Begin

1. From the icon, select Configuration.

   The Configuration domain opens.

2. From the drop-down list, select Control-M/Servers.

   The Control-M/Servers tab appears.

3. Toggle on Self-Hosted.

   The Self-Hosted Control-M Servers tab appears.

4. From the Control-M/Servers tab, select the relevant self-hosted Control-M/Server or Control-M for z/OS, and from the Control-M/Servers toolbar click Pause.

   A Pause Control-M/Server confirmation dialog box appears.

5. Click Pause.

   The self-hosted Control-M/Server or Control-M for z/OS remains up, but jobs do not execute until you reselect the self-hosted Control-M/Server or Control-M for z/OS, and from the Control-M/Servers toolbar, click Resume.

Disabling a Self-Hosted Control-M/Server

This procedure describes how to disable a self-hosted Control-M/Server or Control-M for z/OS. This removes the ability to sync new folder and job definitions and monitor and manage the self-hosted Control-M/Server or Control-M for z/OS and its components.

Begin

1. From the icon, select Configuration.

   The Configuration domain opens.

2. From the drop-down list, select Control-M/Servers.

   The Control-M/Servers tab appears.

3. Toggle on Self-Hosted.

   The Self-Hosted Control-M Servers tab appears.

4. From the Control-M/Servers tab, select the relevant self-hosted Control-M/Server or Control-M for z/OS, and then from the Control-M/Servers toolbar click Disable.

   A Disable Control-M/Server confirmation dialog box appears.

5. Click Disable.

   The self-hosted Control-M/Server or Control-M for z/OS remains up, but you can neither monitor and manage it and its components, nor define and run new jobs until you reselect the self-hosted Control-M/Server or Control-M for z/OS, and from the Control-M/Servers toolbar, click Enable.

Recycling a Self-Hosted Control-M/Server

This procedure describes how to recycle (restart) a self-hosted Control-M/Server or Control-M for z/OS.

Begin

1. From the icon, select Configuration.

   The Configuration domain opens.

2. From the drop-down list, select Control-M/Servers.

   The Control-M/Servers tab appears.

3. Toggle on Self-Hosted.

   The Self-Hosted Control-M Servers tab appears.

4. From the Control-M/Servers tab, select the relevant self-hosted Control-M/Server or Control-M for z/OS, from the Control-M/Servers toolbar click Desired State, and then click Recycle.

   A Recycle Control-M/Server confirmation dialog box appears.

5. Click Recycle.

   The Desired State of the self-hosted Control-M/Server or Control-M for z/OS changes to Recycle, the Actual State changes to Down and then Up, and then the Desired State reverts to Up.

Starting Up the Self-Hosted Control-M/Server

This procedure describes how to start up a self-hosted Control-M/Server or Control-M for z/OS. This instructs the Configuration Agent to attempt to start up the Control-M/Server or Control-M for z/OS when it is down, which enables it to communicate with other components and schedule jobs.

Begin

1. From the icon, select Configuration.

   The Configuration domain opens.

2. From the drop-down list, select Control-M/Servers.

   The Control-M/Servers tab appears.

3. Toggle on Self-Hosted.

   The Self-Hosted Control-M Servers tab appears.

4. From the Control-M/Servers tab, select the relevant self-hosted Control-M/Server or Control-M for z/OS, from the Control-M/Servers toolbar click Desired State, and then click Up.

   A Set Desired State to Up confirmation dialog box appears.

5. Click Set to Up.

   The Desired State and then the Actual State of the self-hosted Control-M/Server or Control-M for z/OS changes to Up.

Shutting Down the Self-Hosted Control-M/Server

This procedure describes how to shut down a self-hosted Control-M/Server or Control-M for z/OS. This instructs the Configuration Agent to attempt to shut down the Control-M/Server or Control-M for z/OS when it is up, which disables communication with other components and removes the ability to schedule jobs.

Begin

1. From the icon, select Configuration.

   The Configuration domain opens.

2. From the drop-down list, select Control-M/Servers.

   The Control-M/Servers tab appears.

3. Toggle on Self-Hosted.

   The Self-Hosted Control-M Servers tab appears.

4. From the Control-M/Servers tab, select the relevant self-hosted Control-M/Server or Control-M for z/OS, from the Control-M/Servers toolbar click Desired State, and then click Down.

   A Set Desired State to Down confirmation dialog box appears.

5. Click Set to Down.

   The Desired State and then the Actual State of the self-hosted Control-M/Server or Control-M for z/OS changes to Down.

Ignoring a Self-Hosted Control-M/Server

This procedure describes how to ignore a self-hosted Control-M/Server or Control-M for z/OS. This instructs the Configuration Agent to make no attempts to change the state of a self-hosted Control-M/Server or Control-M for z/OS.

Begin

1. From the icon, select Configuration.

   The Configuration domain opens.

2. From the drop-down list, select Control-M/Servers.

   The Control-M/Servers tab appears.

3. Toggle on Self-Hosted.

   The Self-Hosted Control-M Servers tab appears.

4. From the Control-M/Servers tab, select the relevant self-hosted Control-M/Server or Control-M for z/OS, from the Control-M/Servers toolbar click Desired State, and then click Ignore.

   A Set Desired State to Ignore confirmation dialog box appears.

5. Click Set to Ignore.

   The Desired State and then the Actual State of the self-hosted Control-M/Server or Control-M for z/OS changes to Ignored.

Recycling a Self-Hosted Service

This procedure describes how to recycle (restart) a self-hosted Control-M Service. For more information, see Control-M Services.

Begin

1. From the icon, select Configuration.

   The Configuration domain opens.

2. From the drop-down list, select Control-M/Servers.

   The Control-M/Servers tab appears.

3. Toggle on Self-Hosted.

   The Self-Hosted Control-M Servers tab appears.

4. From the Control-M/Servers tab, select the relevant self-hosted Control-M/Server or Control-M for z/OS, and then from the Services Status column click the status message.

   The Services dialog box appears.

5. From the Service Type column in the Services tab, select the relevant Service, and then from the Recycle Service column click Recycle.

   A Recycle Service confirmation dialog box appears.

6. Click Recycle.

   The Service recycles and its new State and Desired State appears in the Services tab.