Defining CONTROL-M/EM components

This section explains how to define a new CONTROL-M/EM component and how to
update component properties.

Defining a new CONTROL-M/EM component

1 In the CONTROL-M Configuration Manager, choose Components => New =>
CONTROL-M/EM Component.

2 Fill in the CONTROL-M/EM Component dialog box:

Defining a new CONTROL-M/EM component

A At Desired State, select one of the following states:
■ Up if you want the component to be started

■ Down if you do not want the CONTROL-M Configuration Manager to start

■ the component.

BIM (Batch Impact Manager server)
GAS (Global Alerts server)
GCS (Global Conditions server)
GUI_Server
Forecast_Server

Enter the name of the component.

Optional for the GAS and GUI servers, and not relevant for the GCS server.
When defining a BIM or Forecast_Server component, you must enter the name
of the GUI server with which the component will communicate.

Observe the following guidelines when choosing a name for a new server:

■ You can define multiple GUI servers and multiple GAS servers to run
   simultaneously. (These capabilities allow you to balance job loads as needed in
  your environment.) These servers can run on the same account or on different
 hosts. Each instance of a GUI server (or GAS server) must have a unique name.
The GUI Server name and the GAS server name are used to reference both
components when using the CONTROL-M/EM client components.

■ You can specify any logical name for an instance of either component. For
   example, you can enter the virtual host name of a cluster computer in which the
  GUI Server (or Global Alerts Server) is installed, without specifying the node on
 which the component is installed.

■ By default, the GUI Server is named according to its host name. Thus, if more
   than one GUI Server exists on the same host, each instance must have a unique
  name.
3 Complete the Running on box:
A At Platform, select the operating system for the host computer on which the
component runs.
B At Host Name, enter the name of the host computer.

Updating a previously defined component
4 At Check Interval, enter how frequently, in number of seconds, you want to check
the component’s state.
5 (optional) In the Startup box, indicate the mode in which the component should
start:

■ To use a startup command other than the default, select the Override Manually
   check box and enter a command in the Command box.

■ If you want to use optional arguments for the startup command, enter them in
   the Additional Parameters box.
Updating a previously defined component

1 In the Component window of the Configuration Manager, right-click the
component and select Properties.

2 Modify the values as needed, and click OK.

Defining a CONTROL-M/Server and its Gateway

CONTROL-M refers to an instance of CONTROL-M/Server and its corresponding
Gateway.
When adding a new CONTROL-M/Server and its Gateway, you can use automatic
discovery or manual definition:

Automatic discovery bases the new server on an existing CONTROL-M, retrieving
the parameter values and requiring minimal information from you.


Defining a CONTROL-M/Server (automatic discovery method)
Defining a CONTROL-M/Server (automatic discovery method)

NOTE
This method is valid only for CONTROL-M/Server versions 6.3.01 and higher.

1 In the CONTROL-M Configuration Manager, choose Components => New =>
CONTROL-M/Server and Gateway.

2 In the CONTROL-M/Server Definition dialog box, choose Discover.

3 In the wizard, specify the CONTROL-M/Server connection parameters:

A At CONTROL-M Name, enter the logical name of the required CONTROL-M.
B At CONTROL-M ID, accept the default unique code or enter a unique 3-digit
code identifying the CONTROL-M/Server.
C At CONTROL-M Host, enter the name of the host computer on which the
CONTROL-M is installed.
D At Configuration Agent Port, enter the port number of the CONTROL-M’s
Configuration Agent.
E Click Next.

The discovery process begins. CONTROL-M automatically retrieves parameters
and shows how the discovery is progressing.

4 When the Step 3 wizard panel is displayed, ensure that Activate Gateway is
selected.

5 Review the list of retrieved parameters, and click Finish.
The new CONTROL-M is displayed in the CONTROL-M Configuration Manager
after a short period of time.
Defining a CONTROL-M/Server (manual definition method)
1 Perform one of the following in the CONTROL-M Configuration Manager:

■ To modify the definition of an existing CONTROL-M/Server, right click the
server, and choose Properties.

■ To define a new CONTROL-M/Server

— Choose Components => New => CONTROL-M/Server and Gateway.

— In the prompt, choose Define to display the CONTROL-M Definition dialog
box.

CONTROL-M Definition dialog box

2 Fill in the CONTROL-M Definition dialog box. Table 4 describes the essential
parameter values that you need to provide.

Defining a CONTROL-M/Server (manual definition method)
Table 4

Parameters for manually defining a CONTROL-M/Server and its Gateway
Parameter field Description
Name descriptive name for the CONTROL-M/Server
You should choose a name that is meaningful enough to identify your CONTROL-M.
For example, if the CONTROL-M handles workloads for Division 7, which is associated
with the company’s headquarters in Paris, you might use HQ_PARIS_DIVISION-07.
The name can be a maximum of 20 alphanumeric characters long. You can include
symbols, but do not use blank spaces.
unique 3-character code (such as 999 or NYC) that CONTROL-M/EM uses to identify
each CONTROL-M/Server ID

The code must be unique. It can consist of numerals and uppercase letters.
operating system on which your CONTROL-M is installed. Note the following:
Platform

■ If your platform is UNIX, Windows, TANDEM, or not listed, choose Distributed.

■ If your CONTROL-M runs on iSeries (AS/400) but any of the connecting
   CONTROL-M/Agents run on non-iSeries operating systems, choose Distributed.
version number of the CONTROL-M/Server Version

Note: When defining an iSeries (AS/400) CONTROL-M, choose 225.
Time Zone time zone in which the CONTROL-M is located
Start day day that CONTROL-M/Server should consider to be the first day of the week
New Day Time the time that each new day should begin for the CONTROL-M/Server
Communication type of protocol for communication with CONTROL-M
Protocol

Communication host name of the CONTROL-M Host

Communication TCP/IP port for communicating with CONTROL-M/EM
CONTROL-M/E
M Port

For specific instructions pertaining to CONTROL-M installations on z/OS, see the

INCONTROL for z/OS Installation Guide.

3 If you are defining a new CONTROL-M/Server, under Gateway, click New. You

must specify a Gateway when you set up your work environment. Otherwise, you

can define a new gateway, or modify or delete an existing gateway.

The CONTROL-M/EM Component dialog box is displayed.

4 Specify the required parameters.

Chapter 2 Connecting components

A At Desired State, select one of the following states:

■ Up if you want the gateway to be started

■ Down if you do not want the CONTROL-M Configuration Manager to start

■ the gateway.

B Enter the name of the gateway. You can define multiple gateways for a

CONTROL-M/Server, but only one CONTROL-M can be up (started) at one

time. Additionally, each Gateway should be located on a separate computer.

C In the Platform field, select the operating system for the host computer on which

the component runs.

D In the Host Name, enter the name of the host computer.

E In the Check Interval field, enter how frequently, in seconds, to check the

gateway’s state.

F (optional) In the Startup box, indicate the mode in which the gateway should

start:

■ To use a startup command other than the default, select the Override

   Manually check box and enter a command in the Command box.

■ You want enter optional arguments for the startup command in the

   Additional Parameters box.

G Click OK to save the changes you made in the CONTROL-M/EM Component

dialog box.

5 Click OK in the CONTROL-M Definition dialog box to save your

CONTROL-M/Server definition.

This section explains how to add a new agent to an existing CONTROL-M, and if and

how to configure and manage remote hosts.

Planning your strategy

Completing this section can help you expedite the remaining tasks in this chapter.

This section summarizes prerequisites that you should know about before connecting

components. The provided worksheets also help you gather data that you will need

to provide for tasks in this chapter.

Before proceeding, ensure that you comply with the following requirements and

guidelines.

Deciding whether to define remote hosts

Both CONTROL-M/Agents and remote hosts have distinct advantages. Consider the

following before deciding which method to use on a particular computer:

■ The main advantage of remote hosts over CONTROL-M/Agents is that remote

hosts:

— Can run all jobs assigned to the specific node ID which identifies the remote

computer

— Do not require CONTROL-M/Agent installation on the remote computer

— Do not require version updates

— Require less management

■ The main advantages of CONTROL-M/Agents over remote hosts are that agents

support counters and multiple types of shouts:

— CONTROL-M/Agents can utilize features that require a CONTROL-M counter.

If you need any of these features, you should choose a CONTROL-M/Agent

over a remote host. For example, CONTROL-M/Agents can use the File

Watching feature, run jobs using CONTROL-M/Agent utilities, and run jobs

requiring Control Modules (plug-ins for the CONTROL-M/Agent).

— CONTROL-M/Agents support many types of shouts. (Remote host support is

limited to e-mail shouts and CONTROL-M/Server shouts.)

Planning your strategy

■ To use remote hosts, the CONTROL-M/Server must be in Managed state:

— If you discover the CONTROL-M, its default state is Managed.

— If you define the CONTROL-M, the default state is Unmanaged, and you must

change it to Managed via the CONTROL-M Configuration Manager.

Choosing a connection method for a remote host

To enable communication between the remote host and a CONTROL-M/Agent. You

can use either of the following connection methods, which are available with the

operating system:

■ Secured Shell (SSH)

You can use SSH connections for remote hosts running UNIX, Windows,

OpenVMS, Z/OS USS (OpenEdition) and PASE (AIX environment) on AS/400:

— Most UNIX operating system packages include SSH.

— To use SSH on Windows computers, you must purchase and install it

separately.

— SSH functionality on OpenVMS is available as part of TCP/IP Services Version

5.4 and higher. For older versions of OpenVMS, you must install it separately.

Third party packages are also available.

— To use SSH on AS/400 computers, you must install PASE on AS/400.

NOTE

When you work with z/OS USS (OpenEdition) or PASE AS/400 remote hosts, set the

RJX_CONN_MODE system parameter in CONTROL-M/Agent to 0.

If you will be using more simultaneous connections than your current SSH server

settings allow, you must increase the value for these settings accordingly.

EXAMPLE

For an OpenSSH server, set the MaxStartups and LoginGraceTime parameters in the

sshd_config file.

Planning your strategy

■ Window Management Instrumentation (WMI)

You can use WMI connections with remote hosts running Windows 2003,

Windows XP, or a later version. WMI is part of the Windows operating system.

NOTE

If the CONTROL-M/Agent will be connecting to a remote host on Windows by using the

WMI connection method, ensure that the following requirements are satisfied:

■ The CONTROL-M/Agent is installed on either Windows 2003, Windows XP, or a later

   version.

■ The Log On as option for the CONTROL-M/Agent service is set to This account.

■ The user account that is running the CONTROL-M/Agent service is Administrator and

   is defined as a Domain user.

■ Job owners are members of the Administrator group on the remote host.

Consider the following requirements when deciding which connection method to use

for remote hosts:

■ For Window Management Instrumentation (WMI) connections, the following

requirements apply:

— To use On statements and the View JCL, Edit JCL, and View Sysout options, you

must define a directory named SYSOUT on the remote host. This directory must

be writable by all the job owners on that host. This directory must also be shared

so that the CONTROL-M/Agent user can access it for reading and writing.

When defining the properties of a remote host, specify the full local path (for

example, C:\shared documents\SYSOUT) of this directory so that the job output

will be written to it.

— SYSOUTs created on remote hosts must be copied to a CONTROL-M/Agent. If

a SYSOUT is large, its file transfer can place a heavy load on system resources.

Also, a job will not end until its SYSOUT copying is finished.

■ For Secured Shell (SSH) connections, you must ensure that an SSH Server is

installed and running on each remote host.

A CONTROL-M/Agent should be installed first before it is defined. For information about

installing CONTROL-M/Agents, see the CONTROL-M Installation Guide.

1 From the CONTROL-M Configuration Manager, perform one of the following:

■ To modify the parameters of an existing CONTROL-M/Agent, right click the

agent and choose Properties.

The CONTROL-M/Agent Properties dialog box is displayed.

■ To add a new CONTROL-M/Agent to a CONTROL-M/Server, right click the

CONTROL-M/Server and choose New CONTROL-M/Agent.

The Add CONTROL-M/Agent dialog box is displayed. Fill in the name for the

agent. Click Advanced.

2 In the appropriate dialog box, fill in the fields in the General, Persistent Connection

and Retry/Timeout tabs.

CONTROL-M/Agents and remote hosts

In earlier releases of CONTROL-M/Server, each computer on which you planned to
run jobs required installation of a CONTROL-M/Agent. Beginning with version
6.3.01, CONTROL-M/Server supports agentless job submission. This method enables
submitting and executing jobs on computers that do not have a resident

CONTROL-M/Agent installed. These agentless computers are referred to as remote
hosts.
Although remote host computers do not require a resident CONTROL-M/Agent,
remote hosts come under the control of CONTROL-M/Agents on other computers, as
follows:

■ When you install CONTROL-M/Server in UNIX, a CONTROL-M/Agent is
   automatically installed on the same account. When you install
  CONTROL-M/Server in Windows, a CONTROL-M/Agent is automatically
 installed on the same computer, unless one already exists or you are performing a
cluster install. This automatically installed CONTROL-M/Agent is known as the
<Local> agent and is, by default, the agent that is used to connect to remote hosts.

■ You can place remote hosts under the control of any other CONTROL-M/Agents
   installed on computers under the same CONTROL-M/Server.
You will need to define the following information for each remote host:

■ host communication settings
You can define specific settings for a host, or use the default settings. For more
information, see “Configuring and managing remote hosts”

■ owner authentication settings
These settings specify the owners of the jobs that are running on the remote host,
and owner authentication parameters that are used for connecting to the remote
host. In a CONTROL-M job that is destined to be run on a remote host, you must
define each job owner that is specified.

CONTROL-M/Server definition and management

Several terms describe the definition and management of a CONTROL-M/Server:

■ Discovery/Define

When defining CONTROL-M/Servers and their gateways (which you do using the
CONTROL-M/Server Definition dialog box), you can choose either of the
following definition methods:

— Automatic discovery—provides automatic detection of a CONTROL-M/Server
and gateway, with minimal information supplied. (This option is available in
CONTROL-M/Server version 6.3.01 and later.)

— Manual definition—you manually define a CONTROL-M/Server and
corresponding Gateway.

■ Managed / Unmanaged —Managed and Unmanaged are modes of connection
between CONTROL-M/EM and CONTROL-M/Server.

— If a CONTROL/Server is Managed, the Configuration Agent automatically
provides CONTROL-M/EM parameter information about the
CONTROL-M/Server, and on an ongoing basis updates that information
whenever there is a change.

— If a CONTROL-M/Server is unmanaged, you must manually provide
CONTROL-M/EM with the CONTROL-M/Server parameters.
CONTROL-M/EM automatically manages CONTROL-M/Server version 6.3.01
and later, and CONTROL-M for z/OS versions 6.2.A and later. Furthermore, you
must manually manage CONTROL-M/Server versions earlier than 6.3.01 and
CONTROL-M for z/OS versions prior to 6.2.A.
In certain circumstances, you can choose to bypass automatic management of
CONTROL-M/Server versions 6.3.01 and later, and manually manage those
versions, though this is generally not recommended.
When you use Discovery to define CONTROL-M/Servers, they are automatically
Managed; when you manually define CONTROL-M/Servers, they are Unmanaged.
Using the CONTROL-M Configuration Manager, you can change the connection
mode (managed/unmanaged) of existing CONTROL-M/Servers.

Using the CONTROL-M/EM Root Menu

The database server must be running for the Root Menu and its submenus to be displayed.

1 Log on to the CONTROL-M/EM host computer.
2 Enter the root_menu command.
3 When prompted, enter the CONTROL-M/EM DBO user name and password.

The CONTROL-M/EM Root Menu is displayed.

4 To use the Root Menu and its submenus

A Enter the number of the menu option.
B Make the required changes.
C When you are done, enter q to quit.

Manually starting and stopping CONTROL-M/EM infrastructure processes using the interactive Activation menu

Using Root Menu

1 Display the CONTROL-M/EM Root Menu (root_menu)

2 In the CONTROL-M/EM Root menu, enter the number for the Activation Menu

option.

3 In the Activation menu, enter the number of the appropriate start or stop process

option (or start all or stop all option).

4 Enter q to exit.

You can manually shutdown and startup infrastructure components using the

following methods:

 - CONTROL-M Configuration Manager (to shut down CONTROL-M/Server)

 - CONTROL-M Manager Menu, which you access from the CONTROL-M Main

   Menu (ctm_menu)

 - supplied utilities

Using CONTROL-M Configuration Manager to shut down or start up CONTROL-M/Server

1 In the CONTROL-M Configuration Manager, right-click the

CONTROL-M/Server.

2 Choose Desired State and then choose one of the following submenu options:

Up—bring the component up

Down—bring the component down

Using CONTROL-M Manager Menu to shut down or start up CONTROL-M/Server infrastructure components

1 Display the CONTROL-M Main menu (ctm_menu). For instructions on displaying

the Main menu, see “Using the CONTROL-M/Server Main Menu” on page 47.

2 In the CONTROL-M Main menu, enter the number of the CONTROL-M Manager

option.

3 In the CONTROL-M Manager menu, enter the number corresponding to the

component activity you want to perform.

4 When done, enter q.

Using pre-supplied utilities to shut down or start up CONTROL-M/Server infrastructure components

To shut down CONTROL-M/Server entities

1 Log on as the CONTROL-M/Server account owner.

2 Enter one of the following commands as appropriate:

To stop the SQL database server, specify the command: shutdb

To stop the CONTROL-M/Server Configuration Agent: shut_ca

To stop the CONTROL-M/Server, specify the command: shut_ctm

To start CONTROL-M/Server entities

1 Log on as the CONTROL-M/Server account owner.

2 Enter one of the following commands as appropriate:

To start the SQL server, specify the command: startdb

To start the CONTROL-M/Server Configuration Agent: start_ca

To start the CONTROL-M/Server, specify the command: start_ctm

Starting and stopping infrastructure processes in UNIX and Linux

In Unix and Linux, you must start processes after their host computer is booted up, and you must stop them before shutting down the host computer.

Although you can do this manually, you can instead add process startup or shutdown commands to the
operating system startup and shutdown scripts of the host computer.

To start processes on Unix and Linux

Add the following commands to the start-up script of your operating system as
appropriate:


su - ecs_account -c start_ns_daemon
su - ecs_account -c start_server
su - ecs_account -c start_cms
su - ecs_account -c start_config_agent
su - ecs_account -c start_web_server.sh

To stop processes on Unix and Linux

Add the following commands to the shut-down script of your operating system as
appropriate:

ecs ctl -U CONTROL-M/EM_database_owner -P CONTROL-M/EM_database_owner_password -C Maint_Agent -M hostname -cmd shutdown

su - ecs_account -c "stop_server -U db_server_administrator_name -P db_server_administrator_name"

su - ecs_account -c stop_ns_daemon

su - ecs_account -c stop_cms

su - ecs_account -c stop_config_agent

su - ecs_account -c stop_web_server.sh

Starting and stopping infrastructure processes in Windows

On Windows, all CONTROL-M/EM, CONTROL-M/Server, and
CONTROL-M/Agent processes are defined as services.

By default, they are automatically started when you bring Windows up, and they are automatically
stopped when you bring Windows down.

Therefore, it is normally not necessary for you to perform startup or shutdown of
these processes. However, you can bring these services down or up whenever useful.

To stop CONTROL-M/EM, CONTROL-M/Server, or CONTROL-M/Agent services in Windows

1. Choose Start => Control Panel => Administrative Tools => Services.
2. Right click the service, and choose Stop.

To start CONTROL-M/EM, CONTROL-M/Server, or CONTROL-M/Agent services in Windows

1. Choose Start => Control Panel => Administrative Tools => Services.
2. Right click the service, and choose Start.

CONTROL-M/EM, CONTROL-M/Server, and CONTROL-M Agent Infrastructure processes

CONTROL-M/EM processes

CONTROL-M/EM provides the following processes:

Naming Service: TAO NT Naming Service

CONTROL-M/EM processes:
— CONTROL-M Configuration Management Server (CMS)
— CONTROL-M Web Server
— CONTROL-M/Enterprise Manager Configuration Agent

CONTROL-M/Server processes

CONTROL-M/Server provides the following processes:

ctmsrv_service (Windows only, where it runs as a service)
p_ctmsu (Unix only)
p_ctmrt
p_ctmsl
p_ctmtr
p_ctmcd
p_ctmcs
p_ctmlg
p_ctmwd
p_ctmco
p_ctmns
p_ctmca (Unix only; Known as CONTROL-M/Server Configuration Agent)
ctmsca_service (Windows only, where it runs as a service; Known as
CONTROL-M/Server Configuration Agent)

CONTROL-M/Agent processes

CONTROL-M/Agent provides the following processes:


p_ctmar
p_ctmag (Known as CONTROL-M/Agent Listener, which on Windows runs as a
service).
p_ctmat (Known as CONTROL-M/Agent Tracker)
ctmfw_service (Windows only, where it runs as a service; Known as CONTROL-M
File Watcher)
CONTROL-M/Agent (on Unix and Windows it runs as a service)
CONTROL-M FileWatcher (Windows only, where it runs as a service)

Control-M presentation

Control-M is a scheduler (the best on the market) .

CONTROL-M/EM architectural structure

client components

The primary client components include:
— CONTROL-M Configuration Manager GUI—the main CONTROL-M
administrator interface to CONTROL-M/EM, CONTROL-M/Server and
CONTROL-M/Agent. It provides a single point of control for administering the
CONTROL-M environment and enables you to manage many of your
CONTROL-M administrative tasks from a central location.


— CONTROL-M/Desktop—GUI interface used by end-users for modeling the
production environment (defining jobs).

— CONTROL-M/EM GUI—GUI interface used by end-users and administrators
for monitoring the production environment and intervening when necessary.

— CONTROL-M Reporting facility—facility and GUI used by end-users and
administrators for generating useful reports of many types.

— Command line utilities—Many functions that are available through the GUIs
are also available through the use of interactive and batch utilities.

■

CONTROL-M/EM server components

— GUI Server—provides information to, and handles user requests issued
through, the CONTROL-M/Enterprise Manager window.

— Gateway—interface that handles communication between CONTROL-M/EM
and CONTROL-M/Server. A different gateway is dedicated to each
CONTROL-M/Server. The gateway is defined when the CONTROL-M/Server
is defined. CONTROL-M/EM and CONTROL-M for z/OS also interface
through a gateway.

— Configuration Management Server (CMS)—interfaces with the configuration
agents of CONTROL-M/Server and CONTROL-M for z/OS to provide
information to, and handle administrator requests issued through, the
CONTROL-M Configuration Manager.

— Global Alerts server (GAS) —manages alerts to CONTROL-M/EM GUIs
— Global Conditions server (GCS)—distributes global conditions to different
CONTROL-Ms.

— Batch Impact Manager (BIM) server—monitors critical batch services when your
site uses the BMC Batch Impact Manager add-on.

— Forecast server—helps you predict job patterns in order to forecast schedules for
running jobs in the future, when your site uses the CONTROL-M/Forecast
add-on.

CONTROL-M/Server and Agent components

■
infrastructure components
These components include:
— CONTROL-M/EM Configuration Agent—interface between
CONTROL-M/EM Configuration Manager Server and other CONTROL-M/EM
servers that provides CONTROL-M/EM server information to, and handles
administrator requests issued through, the CONTROL-M Configuration
Manager.

— CONTROL-M/EM database (Oracle, Sybase, MSSQL, or PostgreSQL) where
CONTROL-M/EM data resides

— CORBA-based naming services, which enables the client to locate the server to
which it must connect. For more information, see Appendix A, “Configuring
CORBA components.”

— CONTROL-M Web Server, used for deploying CONTROL-M client components
on client computers.


CONTROL-M/Server and Agent architectural structure

CONTROL-M/Server

Heart of the CONTROL-M family of products, CONTROL-M/Server submits jobs

for execution on Agent or remote host computers, monitors the jobs and performs

post-processing analysis, after which it may perform post-processing actions. The

completion status of jobs and the results of post-processing analysis are

transmitted to CONTROL-M/Enterprise Manager.

Agent computers

An agent computer is one on which CONTROL-M/Agent has been installed.

CONTROL-M/Agent submits jobs for execution, monitors the jobs, and performs

post-processing analysis of output files. The completion status of jobs and the

results of post-processing analysis are transmitted back to CONTROL-M/Server.

CONTROL-M/Agent can submit jobs to a remote host for execution.

Remote host computers

Agentless computer on which jobs can run. Each remote host is identified by its

node ID.

Control Modules

Control Modules (CMs) enable CONTROL-M/Agents to interface with the

external applications (for example SAP and Oracle E-Business Suite).

Infrastructure components

These components include:

— CONTROL-M/Server Configuration Agent —interfaces with

CONTROL-M/EM Configuration Manager Server to provide

CONTROL-M/Server information to, and handle administrator requests issued

through, the CONTROL-M Configuration Manager.

— CONTROL-M/Server database (Oracle, Sybase, MSSQL, or PostgreSQL)—

repository of CONTROL-M/Server data. One database exists for each

CONTROL-M/Server, which maintains the database by using a dedicated or

shared SQL server.