Beruflich Dokumente
Kultur Dokumente
Administrator Guide
Supporting
CONTROL-M for Databases version 6.4.01
July 2009
www.bmc.com
Telephone
Fax
Fax
BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is
subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted
rights notices included in this documentation.
Customer support
You can obtain technical support by using the BMC Software Customer Support website or by contacting Customer
Support by telephone or e-mail. To expedite your inquiry, see Before contacting BMC.
Support website
You can obtain technical support from BMC 24 hours a day, 7 days a week at http://www.bmc.com/support. From this
website, you can
read overviews about support services and programs that BMC offers
find the most current information about BMC products
search a database for issues similar to yours and possible solutions
order or download product documentation
download products and maintenance
report an issue or ask a question
subscribe to receive proactive e-mail alerts when new product notices are released
find worldwide BMC support center locations and contact information, including e-mail addresses, fax numbers, and
telephone numbers
product information
product name
product version (release number)
license number and password (trial or permanent)
machine type
operating system type, version, and service pack or other maintenance level such as PUT or PTF
system hardware configuration
serial numbers
related software (database, application, and communication) including type, version, and service pack or
maintenance level
messages received (and the time and date that you received them)
(USA or Canada) Contact the Order Services Password Team at 800 841 2031, or send an e-mail message to
ContractsPasswordAdministration@bmc.com.
(Europe, the Middle East, and Africa) Fax your questions to EMEA Contracts Administration at +31 20 354 8702, or send
an e-mail message to password@bmc.com.
(Asia-Pacific) Contact your BMC sales representative or your local BMC office.
Contents
About this book
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Syntax statements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
.......................................................................... 8
Chapter 1
Installation
13
Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNIX installation on CONTROL-M/Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing CONTROL-M for Databases on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing a silent installation on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows installation on CONTROL-M/Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing CONTROL-M for Databases on Windows. . . . . . . . . . . . . . . . . . . . . . . .
Performing a silent installation on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation on CONTROL-M/EM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Importing the Databases form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the CONTROL-M for Databases plug-in on the CONTROL-M
Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enabling Find and Update support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CONTROL-M for Databases Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uninstalling CONTROL-M for Databases from UNIX . . . . . . . . . . . . . . . . . . . . . .
Performing Silent Uninstall from UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uninstalling CONTROL-M for Databases from Windows . . . . . . . . . . . . . . . . . . .
Performing Silent Uninstall from Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14
14
16
16
17
18
18
19
20
21
Chapter 3
27
Account management
Contents
21
22
23
23
24
24
25
28
28
31
32
32
33
Chapter 4
35
47
57
NOTE
Online books are formatted as PDF or HTML files. To view, print, or copy PDF books, use the
free Adobe Reader from Adobe Systems. If your product installation does not install the
reader, you can obtain the reader at http://www.adobe.com.
The software also offers online Help. To access Help, press F1 within any product or
click the Help button in graphical user interfaces (GUIs).
Related publications
Syntax statements
The following example shows a sample syntax statement:
COMMAND KEYWORD1 [KEYWORD2 | KEYWORD3] KEYWORD4={YES | NO} fileName...
The following table explains conventions for syntax statements and provides
examples:
Item
Example
alias
{DBDName | tableName}
databaseDirectory
serverHostName
{commit | cancel}
columnName . . .
Chapter
Connect to any supported database from a single computer with secure login,
which eliminates the need to provide authentication, as described in Chapter 3,
Account management.
Define and monitor Stored Procedure, SQL Script, SQL Server Integration Services
(SSIS) Package, and Open Query database jobs, as described in Chapter 4,
Databases job definition.
Integrate database jobs with other CONTROL-M jobs into a single scheduling
environment, as described in CONTROL-M User Guide.
Administrative tasks
Certain CONTROL-M tasks might need to be performed by different professionals in
your organization, as follows:
10
Administrative tasks
Table 1 lists the tasks performed when working with the CONTROL-M for Databases
and the role of the professional who is responsible for its administration.
Table 1
Tasks
Roles
System Administrator
CONTROL-M
Administrator
CONTROL-M
Administrator
Production Controller
CONTROL-M
Administrator
Application Expert DBA
CONTROL-M Production
Controller
CONTROL-M
Administrator
Application Expert DBA
CONTROL-M Administrator
11
Administrative tasks
12
Chapter
Installation
Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNIX installation on CONTROL-M/Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows installation on CONTROL-M/Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation on CONTROL-M/EM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CONTROL-M for Databases Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2
Installation
14
14
16
18
20
23
13
Installation overview
Installation overview
CONTROL-M for Databases can be installed on Windows and UNIX and must be
installed on a CONTROL-M/Agent and a CONTROL-M/EM client.
Table 2 describes the installation information and tasks for CONTROL-M for
Databases.
Table 2
Task/Information
Description
Installation
requirements on page 14
UNIX installation on
CONTROL-M/Agent on
page 16
Windows installation on
CONTROL-M/Agent on
page 18
Installation on
CONTROL-M/EM on
page 20
Installation requirements
Table 3 describes the software requirements to install CONTROL-M for Databases.
Table 3
Software requirements
Software
Version
CONTROL-M/EM
CONTROL-M/Agent
CONTROL-M/Server
14
Installation requirements
Table 4
Requirements
Details
Minimum RAM
512 MB
256 MB
Supported databases
Database
Oracle
Versions
MSSQL
DB2
9.2
10
11
2000
2005
2008
9.1
9.5
NOTE
If you are using a DB2 database on z/OS or iSeries platforms, you need to obtain the required
license file by contacting an IBM representative.
After you have obtained the license file, you need to do the following:
1. Copy the license file to one of the following locations:
Windows: <Agent_Home_Dir>\CM\DB\JDBCDrivers\db2\9\
UNIX: <Agent_Home_Dir>/ctm/cm/DB/JDBCDrivers/db2/9/
2. Stop the container, as described in the Stopping the CONTROL-M for Databases service
on page 57.
3. Do the following:
A. Access the following configuration file:
Windows: <Agent_Home_Dir>\CM\DB\data\DriverList.xml
UNIX: <Agent_Home_Dir>/ctm/cm/DB/data/DriverList.xml
B. Open the file and locate <DBVendor>DB2</DBVendor>.
C. Locate <DriverJars> and add the following element value:
<Jar>db2/9/<license filename></Jar>
Chapter 2
Installation
15
NOTE
The default installation is interactive and uses a GUI display. XServer must be running and
configured using the DISPLAY environment variable. If you do not have XServer available, it
is recommended that you perform a silent installation. For more information, see Performing
a silent installation on UNIX on page 17.
To install on UNIX:
1 Ensure that all jobs running on the CONTROL-M/Agent have ended.
2 Log in as user root, and stop the CONTROL-M/Agent by running the following
command:
<CONTROL-M Agent directory>/scripts/shut-ag -u <agentUser> -p all
16
NOTE
If XServer is not available to run a full installation, to prepare the XML parameters file, copy
the XML parameters file from the Setup_files folder on the installation DVD.
3 From the installation DVD, activate the installation script with the following
command:
<dvd_path>/Setup.sh
4 Continue with the installation wizard, following the instructions on each screen to
complete the interactive installation.
5 On the last screen, click Generate Silent Installation File and select the location to
create the XML parameter file.
Chapter 2
Installation
17
4 Log in as user root, and start the CONTROL-M/Agent by running the following
command:
<CONTROL-M Agent directory>/scripts/start-ag -u <agentUser> -p all
18
To install on Windows:
1 Ensure that all jobs running on the CONTROL-M/Agent have ended.
2 Log in to the computer using a user ID that has Administrator privileges.
3 Do one of the following:
3 Continue with the installation wizard, following the instructions on each screen in
order to complete the interactive installation.
4 On the last screen, click Generate Silent Installation File and select the location to
create the XML parameter file.
Chapter 2
Installation
19
Installation on CONTROL-M/EM
Installation on CONTROL-M/EM
The following procedures describes how to install CONTROL-M for Databases on
CONTROL-M/EM and must be done in the following order:
1. Importing the Databases form on page 21
2. Installing the CONTROL-M for Databases plug-in on the CONTROL-M
Configuration Manager on page 21
3. Enabling Find and Update support on page 22
20
NOTE
This procedure must be performed on every computer that has CONTROL-M/EM client
components installed.
Chapter 2
Installation
21
NOTE
To use the CONTROL-M for Databases utilities in the CONTROL-M Configuration Manager,
you must ensure that the ctmgetcm utility has run in CONTROL-M/Server.
For more information, see the CONTROL-M Administrator Guide.
22
CONTROL-M for Databases has been successfully removed from your computer.
5 To restart CONTROL-M/Agent, log in as user root and run the start-ag command.
Chapter 2
Installation
23
CONTROL-M for Databases has been successfully removed from your computer.
4 To restart CONTROL-M/Agent, log in as user root and run the start-ag command.
24
CONTROL-M for Databases has been successfully removed from your computer.
Chapter 2
Installation
25
26
Chapter
Account management
Account management overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding an account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating an account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting an account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Testing an account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Copying an account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 3
Account management
28
28
31
32
32
33
27
Adding an account
This procedure describes how to add an account in the CONTROL-M Configuration
Manager, which enables you to connect to a database.
To add an account:
1 From the CONTROL-M Configuration Manager, right-click the Databases Control
Module and select Account Management.
The CONTROL-M for Databases - Account Management dialog box appears.
2 Click the
icon.
3 Do the following:
28
In the Account Name field, type the name of the account that you want to add
without any spaces.
Adding an account
From the Database Type dropdown list, select one of the following database
types:
MSSQL
DB2
Oracle
From the Database Version dropdown list, select the version of the database.
NOTE
CONTROL-M for Databases SSIS feature only supports MSSQL 2005 and 2008.
4 Click Next.
The Add Account-Database Connection Parameters dialog box appears.
NOTE
The database account type that appears depends on what you selected in the Add
Account-Initial Step dialog box.
Parameter
Description
Host Name
Port Number
Database Name
SQL Server
Authentication
Chapter 3
Account management
29
Adding an account
Table 6
Parameter
Description
Windows
Authentication
Verify that the defined user in the account has the Log on as a
batch job permission in the Local Security policy window
(Control Panel > Administrative Tools > Local Security Policy
> Local Policies > User Rights Assignment)
Verify that the defined user in the account either has read and
write permissions in the CONTROL-M/Agent root directory or
is added to the Administrator group
User Name
Password
Confirm Password
6 Click Next.
The Advanced Account Configuration dialog box appears.
Parameter
Description
Maximum concurrent
connections
Number of connection retries Determines the number of connection attempts between 1-24
after a connection failure
Connection retry time out
Disconnect after
8 Click Next.
If you selected the MSSQL database type, the Add Account-SSIS Package Password
Definition dialog box appears; otherwise, go to step 11.
9 To enable access to an SSIS package, add a password to the package by doing the
following:
30
Updating an account
A Click Add.
The Add Package dialog box appears.
12 Click Finish.
Updating an account
This procedure describes how to update an account in the CONTROL-M
Configuration Manager, which enables you to connect to a database.
To update an account:
1 From the CONTROL-M Configuration Manager, right-click on the Databases
Control Module and select Account Management.
The CONTROL-M for Databases - Account Management dialog box appears.
icon.
4 Click Test.
If the test completed successfully, the database account is validated and you can
now define a database job, as described in Chapter 4, Databases job definition. If
the test failed, review the account parameters and test it again.
5 Click OK.
Chapter 3
Account management
31
Deleting an account
Deleting an account
This procedure describes how to delete an account from the CONTROL-M
Configuration Manager.
To delete an account:
1 From the CONTROL-M Configuration Manager, right-click the Databases Control
Module and select Account Management.
The CONTROL-M for Databases - Account Management dialog box appears.
icon.
3 Click OK.
The account is deleted.
Testing an account
This procedure describes how to test an account in the CONTROL-M Configuration
Manager, to confirm that you are able to connect to the required database.
To test an account:
1 From the CONTROL-M Configuration Manager, right-click the Databases Control
Module and select Account Management.
The CONTROL-M for Databases - Account Management dialog box appears.
icon.
If the test completed successfully, the database account is validated and you can
now define a database job, as described in Chapter 4, Databases job definition. If
the test failed, review the account parameters and test it again.
32
Copying an account
Copying an account
This procedure describes how to copy an account in the CONTROL-M Configuration
Manager, which enables you to create an account using the parameters of an existing
account.
To copy an account:
1 From the CONTROL-M Configuration Manager, right-click the Databases Control
Module and select Account Management.
The CONTROL-M for Databases - Account Management dialog box appears.
icon.
4 Click Test.
If the test completed successfully, the database account is validated and you can
now define a database job, as described in Chapter 4, Databases job definition. If
the test failed, review the account parameters and test it again.
5 Click OK.
Chapter 3
Account management
33
Copying an account
34
Chapter
36
36
37
39
40
42
43
35
Stored Procedure: Defines a database job with a program that is stored on the
SQL Script: Defines a database job with a script that is stored on a file system, as
described in Defining an SQL Script job on page 39.
SQL Server Integration Services (SSIS): Defines an SSIS Package job, as described in
Defining an SSIS Package job on page 40
After you have defined a database job, you can enhance it by doing the following:
Integrate database jobs with other CONTROL-M jobs into a single scheduling
environment, as described in CONTROL-M User Guide.
36
Successful completion of Accessing the Database job editing form on page 36.
2 Select the account that you want to use to connect to a database and click OK.
3 From the Execution Type dropdown list, select Stored Procedure.
4 In the Name field, do one of the following:
37
The object parameters are retrieved from the database and appear in the
Parameters table.
For each In parameter, in the Value column, type a value such as string or an
integer, or type an autoedit, as described in the CONTROL-M Parameter Guide.
For each Out parameter, in the Auto-Edit Variable column, type an autoedit, as
described in the CONTROL-M Parameter Guide (optional).
For each In/Out parameter, in the Value column, type a value, such as an integer,
or a string, or type an autoedit, as described in the CONTROL-M Parameter
Guide.
format.
From the Select Output format dropdown list, select an output format and click
OK.
For more information about defining a job in the job editing form, see the
CONTROL-M User Guide.
38
NOTE
CONTROL-M for Databases does not support conversion of database separators between
different database types.
The following list the database separators for each database:
A block separator must appear on a new line at the end of each block.
Successful completion of Accessing the Database job editing form on page 36.
2 Select the account that you want to load and click OK.
3 From the Execution Type dropdown list, select SQL Script.
4 Click Browse.
5 Browse for the required SQL script and click Open.
6 If there are script variables for this script, in the Script Variables table, click the
icon and type the variable and its value.
39
EXAMPLE
If the script content is select count(*) from $1, then $1 is the variable that requires a value in
the Scripts Variables table.
NOTE
Variables and the conventions of the SQL script are not displayed in the CONTROL-M for
Databases job editing form.
format.
From the Select Output format dropdown list, select an output format and click
OK.
For more information about defining a job in the job editing form, see the
CONTROL-M User Guide.
NOTE
The SSIS feature in CONTROL-M for Databases has the following requirements:
40
SSIS Packages are executed locally on the computer where the CONTROL-M/Agent is
installed.
Successful completion of Accessing the Database job editing form on page 36.
2 Select the MSSQL account that you want to load and click OK.
3 From the Execution Type dropdown list, select SSIS Package.
4 From the Package Source dropdown list, select one of the following:
SSIS Package Store: Package stored on a file system that is managed by an SSIS
service.
5 Click the
6 If you want to apply specific data that is saved in a configuration file to the SSIS
Package, in the Configuration Files area, click the
icon.
7 Browse and select the configuration file that you want to add.
8 If there are property paths in this package, in the Properties table, click the
icon
41
11 Click OK.
For more information about defining a job in the job editing form, see the
CONTROL-M User Guide.
NOTE
CONTROL-M for Databases does not support conversion of database separators between
different database types.
The following list the database separators for each database:
A block separator must appear on a new line at the end of each block.
Successful completion of Accessing the Database job editing form on page 36.
2 Select the account that you want to load and click OK.
3 From the Execution Type dropdown list, select Open Query.
4 Do one of the following:
42
To create an SQL query statement, in the Query Text field, type the required
query.
Click Insert from File, and select the required SQL file.
In the Query Text field, edit the query, or use the Query Designer, as
described in Defining a database job with the Query Designer on page 43.
Append Output to Sysout: Shows the job output in a Text, XML, CSV, or HTML
format.
From the Select Output format dropdown list, select an output format and click
OK.
For more information about defining a job in the job editing form, see the
CONTROL-M User Guide.
Successful completion of Accessing the Database job editing form on page 36.
43
2 Select the account that you want to load and click OK.
3 From the Execution Type dropdown list, select Open Query.
4 Click Query Designer.
The Query Designer dialog box appears.
icon.
icon.
8 To create a relationship between two fields, from the Column dropdown lists,
select the field names.
icon.
44
Append Output to Sysout: Shows the job output in a Text, XML, CSV, or HTML
format.
From the Select Output format dropdown list, select an output format and click
OK.
For more information about defining a job in the job editing form, see the
CONTROL-M User Guide.
45
46
Chapter
Chapter 5
48
49
49
49
49
50
50
50
51
51
51
52
52
52
53
53
53
53
54
54
54
55
47
48
Parameter
Description
Account
Execution Type
Query
Schema
Package
Name
Parameter Name
Value
Auto-Edit Variable
Variable
Query text
Data Type
Parameter Type
Package Source
Package Name
Account
Account
Defines the CONTROL-M for Databases account.
Usage
Mandatory
Length
1 - 30 characters
Case Sensitive
Variable Name
%%DB-ACCOUNT
Execution Type
Defines the database job as a Stored Procedure, SQL Script, SSIS, or Open Query.
Usage
Mandatory
Length
N/A
Case Sensitive
No
Variable Name
%%DB-EXEC_TYPE
Possible Values
Query
Defines the database job as an Open Query job.
Usage
Length
Mandatory
Case Sensitive
No
Variable Name
%%DB-QTXT-Nnnn-SUBQTXT
Schema
Filters stored procedures results according to schema names.
Chapter 5
49
Package
Usage
Length
Optional
Case Sensitive
No
Variable Name
%%DB-STP_SCHEM
Package
Filters stored procedures results according to package names.
Usage
Length
Optional
Case Sensitive
No
Variable Name
%%DB-STP_PACKAGE
Name
Defines the name of the Stored Procedure or SQL Script.
Usage
Length
Mandatory
Case Sensitive
No
Variable Name
%%DB-STP_NAME
%%DB-SCRPT_NAME
Parameter Name
Defines the names of the stored procedure parameters.
50
Value
Usage
Length
Optional
Case Sensitive
No
Variable Name
%%DB-STP-PARAMS-Pnnn-PRM_NAME
Value
Defines the parameter values of the store procedure and SQL script.
Usage
Length
Optional
Case Sensitive
No
Variable Name
%%DB-STP-PARAMS-Pnnn-PRM_VALUE
%%DB-SCRPT-PARMS-Pnnn-VALUE
Auto-Edit Variable
Defines the autoedit name that stores the OUT and Return parameters result in stored
procedure submission.
Usage
Length
Optional
Case Sensitive
No
Variable Name
DB-STP_PARAMS-Pnnn-PRM_SETVAR
Variable
Defines the variables of the SQL Script.
Usage
Length
Optional
Chapter 5
51
Query text
Case Sensitive
No
Variable Name
%%DB-SCRPT-PARMS-Pnnn-VARIABLE
Query text
Defines the content of the SQL Script.
Usage
Length
Mandatory
Case Sensitive
No
Variable Name
%%DB-QTXT-Nnnn-SUBQTXT
Data Type
Defines the data type of the stored procedure, such as string or integer.
Usage
Length
Optional
Case Sensitive
No
Variable Name
%%DB-STP-PARAMS-Pnnn-PRM_TYPE
Parameter Type
Defines the stored procedure column type as IN or OUT.
Usage
Length
Optional
52
Case Sensitive
No
Variable Name
%%DB-STP_PARAMS-Pnnn-PRM_DIRECTION
Optional
Length
N/A
Case Sensitive
No
Variable Name
%%DB-APPEND_LOG
Default
Yes
Optional
Length
N/A
Case Sensitive
No
Variable Name
%%DB-APPEND_OUTPUT
Default
Yes
Mandatory
Length
N/A
Case Sensitive
No
Variable Name
%%DB-OUTPUT_FORMAT
Possible Values
Default
Text
Package Source
Defines the location of the SSIS Package in SQL Server, File System, or SSIS Package
Store.
Chapter 5
53
Package Name
Usage
Mandatory
Length
N/A
Case Sensitive
No
Variable Name
%%DB-SSIS_PACKAGE_SOURCE
Package Name
Defines the name of the SSIS Package.
Usage
Length
Mandatory
Case Sensitive
No
Variable Name
%%DB-SSIS_PACKAGE_NAME
Optional
Case Sensitive
No
Variable Name
%%DB-SSIS_CONFIGFILES-Nxxx-NAME
Mandatory
54
Case Sensitive
No
Variable Name
%%DB-SSIS_SETVALPARAMS-Nxxx-NAME
Mandatory
Case Sensitive
No
Variable Name
%%DB-SSIS_SETVALPARAMS-Nxxx-VALUE
Chapter 5
55
56
Appendix
Stopping the CONTROL-M for Databases service on page 57: Describes how to
stop the CONTROL-M for Database process, which enables you to reinstall,
upgrade, change port numbers, or run system maintenance on the CONTROL-M
for Databases service
Starting the CONTROL-M for Databases service on page 58: Describes how to
start the CONTROL-M for Database process, which enables you to restart the
CONTROL-M for Databases process if it failed to restart automatically after it was
shut down
Viewing the status of the CONTROL-M for Databases service on page 59:
Describes how to view the status of the CONTROL-M for Database process, which
enables you to know if the process is still up and running or failed due to an
internal problem
To disable the Preview feature in the Query Designer, see Disabling the Preview
feature on page 59.
57
NOTE
If you want to change the default port number of 38080, in the XML parameter file,
change the port number as needed.
Windows: <Agent_Home_Dir>\CM\DB\exe\
UNIX: <Agent_Home_Dir>/ctm/cm/DB/exe/
Windows: <Agent_Home_Dir>\CM\DB\exe\
UNIX: <Agent_Home_Dir>/ctm/cm/DB/exe/
58
Windows: <Agent_Home_Dir>\CM\DB\exe\
UNIX: <Agent_Home_Dir>/ctm/cm/DB/exe/
Windows: <Agent_Home_Dir>\CM\DB\data\CTMDB_container_conf.xml
UNIX: <Agent_Home_Dir>/ctm/cm/DB/data/CTMDB_container_conf.xml
59
60
Notes
*100934*
*100934*
*100934*
*100934*
*100934*