SlideShare ist ein Scribd-Unternehmen logo
1 von 32
Downloaden Sie, um offline zu lesen
www.bmc.com
Control-M for IBM InfoSphere DataStage
8.0.00
Administrator Guide
November 2012
2
Contacting BMC Software
You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain
information about the company, its products, corporate offices, special events, and career opportunities.
United States and Canada
Address BMC SOFTWARE INC
2101 CITYWEST BLVD
HOUSTON TX
77042-2827
USA
Telephone  713 918 8800
 800 841 2031
Fax 713 918 8000
May 14, 2012
Outside United States and Canada
Telephone (01) 713 918 8800 Fax (01) 713 918 8000
© Copyright 2012 BMC Software, Inc.
BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are
registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other
countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in
the U.S. or in other countries. All other trademarks or registered trademarks are the property of their
respective owners. IT Infrastructure Library® is a registered trademark of the Office of Government
Commerce and is used here by BMC Software, Inc., under license from and with the permission of OGC.
ITIL® is a registered trademark, and a registered community trademark of the Office of Government
Commerce, and is registered in the U.S. Patent and Trademark Office, and is used here by BMC Software,
Inc., under license from and with the permission of OGC.
Linux is the registered trademark of Linus Torvalds.
Oracle is a registered trademark of Oracle Corporation.
UNIX is the registered trademark of The Open Group in the US and other countries.
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.
Restricted rights legend
U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE
COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer
software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14,
DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended
from time to time. Contractor/Manufacturer is BMC SOFTWARE INC, 2101 CITYWEST BLVD, HOUSTON TX
77042-2827, USA. Any contract notices should be sent to this address.
3
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
Support by telephone or e-mail
In the United States and Canada, if you need technical support and do not have access to the web, call 800
537 1813 or send an e-mail message to customer_support@bmc.com. (In the subject line, enter
SupID:<yourSupportContractID>, such as SupID:12345). Outside the United States and Canada, contact
your local support center for assistance.
Before contacting BMC
Have the following information available so that Customer Support can begin working on your issue
immediately:
 product information
• product name
• product version (release number)
• license number and password (trial or permanent)
 operating system and environment information
• 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
4
 sequence of events leading to the issue
 commands and options that you used
 messages received (and the time and date that you received them)
• product error messages
• messages from the operating system, such as file system full
• messages from related software
License key and password information
If you have questions about your license key or password, contact BMC as follows:
 (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.
5
Contents
Introduction to Control-M for IBM InfoSphere DataStage ...................................................6
Control-M for IBM InfoSphere DataStage overview...........................................................................6
Administrative roles........................................................................................................................6
Installation ....................................................................................................................8
Setting environment variables in UNIX.............................................................................................8
Installing Control-M for IBM InfoSphere DataStage on Control-M/Agent on UNIX ...............................9
Installing Control-M for IBM InfoSphere DataStage on Control-M/Agent on Windows........................10
Installation on Control-M/EM.........................................................................................................12
Control-M for IBM InfoSphere DataStage Uninstall..........................................................................14
Account management................................................................................................... 17
Creating an Account .....................................................................................................................17
Control-M for IBM InfoSphere DataStage account parameters.........................................................18
Editing an account........................................................................................................................19
Deleting an account......................................................................................................................19
Testing an account .......................................................................................................................20
Copying an account......................................................................................................................20
Exporting an account....................................................................................................................21
Job definition ............................................................................................................... 22
Accessing the IBM InfoSphere DataStage form...............................................................................22
Defining a Control-M for IBM InfoSphere DataStage job .................................................................23
Monitoring a job...........................................................................................................................24
Control-M for IBM InfoSphere DataStage parameters .....................................................................24
6
1Chapter
1
Introduction to Control-M for IBM InfoSphere
DataStage
Control-M for IBM InfoSphere DataStage overview
Control-M for IBM InfoSphere DataStage is a control module that enables you to run and execute pre-defined
IBM InfoSphere DataStage jobs. Before you begin, do the following:
 Install Control-M for IBM InfoSphere DataStage, as described in Installation.
 Connect to an IBM InfoSphere DataStage server as described in CCM administration.
Control-M for IBM InfoSphere DataStage jobs are integrated with other Control-M jobs into a single
scheduling environment. This enables you to control and operate IBM InfoSphere DataStage jobs from within
Control-M. You can also do the following:
 Define and monitor Control-M for IBM InfoSphere DataStage jobs, as described in Control-M for IBM
InfoSphere DataStage job definition.
 Integrate IBM InfoSphere DataStage jobs with other Control-M jobs into a single scheduling
environment, as described in the Control-M User Guide.
 Introduce all Control-M capabilities to IBM InfoSphere DataStage, including advanced scheduling
criteria, complex dependencies, quantitative and control resources, and AutoEdit variables, as described
in the Control-M User Guide.
Administrative roles
Certain Control-M for IBM InfoSphere DataStage tasks might need to be performed by different professionals
in your organization, as follows:
 System Administrator: Responsible for reviewing the system requirements and performing the
installation process.
 Control-M Administrator: Responsible for the administration of all Control-M processes.
 Control-M Production Controller: Responsible for defining and/or monitoring Control-M jobs.
The following table lists the tasks performed when working with the Control-M for IBM InfoSphere DataStage
and the role of the professional who is responsible for its administration.
Control-M for IBM InfoSphere DataStage Administrator Guide
7
Tasks Roles
Install Control-M for IBM InfoSphere DataStage on a
Control-M/Agent on UNIX, as described in Installing
Control-M for IBM InfoSphere DataStage on Control-M/Agent
on UNIX (on page 9) and on Windows, as described in
Installing Control-M for IBM InfoSphere DataStage on
Control-M/Agent on Windows (on page 10).
 System Administrator
 Control-M Administrator
Install Control-M for IBM InfoSphere DataStage on a
Control-M/Enterprise Manager (Control-M/EM) client, as
described in Installation on Control-M/EM (on page 12).
 System Administrator
 Control-M Administrator
Manage Control-M for IBM InfoSphere DataStage accounts,
as described in CCM administration.
 Control-M Administrator
Define Control-M for IBM InfoSphere DataStage jobs, as
described in Control-M for IBM InfoSphere DataStage job
definition.
 Control-M Administrator
8
2Chapter
2
Installation
Control-M for IBM InfoSphere DataStage can be installed on Windows and UNIX on a Control-M/Agent. The
Control-M/Agent on which you install Control-M for IBM InfoSphere DataStage must also have the IBM
InfoSphere DataStage client or IBM InfoSphere DataStage engine installed on it.
The IBM InfoSphere DataStage form and the CCM client plug-in must be installed on a Control-M/EM client.
The following procedures describe how to install Control-M for IBM InfoSphere DataStage.
Setting environment variables in UNIX (on page 8): describes how to set environment variables in UNIX
Installing Control-M for IBM InfoSphere DataStage on Control-M/Agent on UNIX (on page 9): describes how
to install Control-M for IBM InfoSphere DataStage on Control-M/Agent on UNIX via regular and automatic
installation
Installing Control-M for IBM InfoSphere DataStage on Control-M/Agent on Windows (on page 10): describes
how to install Control-M for IBM InfoSphere DataStage on Control-M/Agent on Windows via regular and
automatic installation
Installation on Control-M/EM (on page 12): describes how to install Control-M for IBM InfoSphere DataStage
on a Control-M/EM client
Setting environment variables in UNIX
This procedure describes how to set environment variables in UNIX, which enables you to see messages from
the console.
1. Do one of the following:
• If you use csh or tcsh, use the following syntax:
setenv <envVar> <value>
Example: setenv DISPLAY myhost:0.0
• If you use sh or ksh, use the following syntax:
<envVar>=<value>
export <envVar>
Example: DISPLAY=myhost:0.0
export DISPLAY
<envVar> is the name of the environment variable.
<value> is the value assigned to the environment variable.
Control-M for IBM InfoSphere DataStage Administrator Guide
9
Installing Control-M for IBM InfoSphere DataStage on
Control-M/Agent on UNIX
This procedure describes how to install Control-M for IBM InfoSphere DataStage on Control-M/Agent on
UNIX interactively or automatically.
If you want to install multiple instances of Control-M for IBM InfoSphere DataStage on several computers
using the same configuration, use the automatic installation, as described in this procedure.
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, BMC recommends that you
continue with the console installation or perform an automatic installation.
Before You Begin
Make sure that the IBM InfoSphere DataStage client or IBM InfoSphere DataStage engine is installed on the
Control-M/Agent machine, and the Control-M/Agent has access and permission to run the IBM InfoSphere
DataStage DSJOB command line utility.
NOTE: The Control-M/Agent account must have all paths defined in order to run the DSJOB command line
utility.
Make sure that all jobs running on Control-M/Agent have ended.
 To install on UNIX:
1. Log in as the Control-M/Agent user, and stop the Control-M/Agent by typing the following command:
$CONTROLM/scripts/shut-ag -u <agentUser> -p all
NOTE: If the Control-M/Agent was installed with user root, then log in as user root every time you start
up or shut down the Control-M/Agent throughout this procedure.
If you are using an AIX operating system, you must remove unused libraries from memory, by typing the
following command as a root user:
/usr/sbin/slibclean
2. Do one of the following:
• Mount the installation DVD.
• Extract the files from the temporary directory that you created when obtaining the installation files
via EPD (see Control-M for IBM InfoSphere DataStage Release Notes).
3. Use one of the following modes:
• Display: if you install using GUI (or XServer), set your DISPLAY environment variable, as described
in Setting environment variables in UNIX (on page 8).
• Console: it is not necessary to set DISPLAY.
4. From the installation DVD or from the installation files via EPD, activate the installation script with the
following command:
<source_path>/setup.sh
Control-M for IBM InfoSphere DataStage Administrator Guide
10
5. Do one of the following:
• Interactive install: continue with the on-screen instructions until the installation is complete.
• Automatic install: do the following:
a. Continue with the on-screen instructions until the Summary window.
b. Click Generate and select the location to create the XML parameter file.
c. Click Yes.
d. Copy the automatic installation parameters file to a network location that is accessible to all
computers where you want to perform an automatic installation.
e. To run the installation script, type the following command:
<source_path>/setup.sh -silent <filename.xml>
The installation logs can be found at the following location:
$HOME/BMCINSTALL/log/cmdatastage/BMC_Control-M_For_IBM_InfoSphere_DataStag
e_Install_<date-time>.log
6. Start the Control-M/Agent by running the following command:
$CONTROLM/scripts/start-ag -u <agentUser> -p all
7. Log out of the Control-M/Agent account.
8. Set up the location of the IBM InfoSphere DataStage engine for Control-M for IBM InfoSphere DataStage.
a. Navigate to:
<Agent dir>/cm/DATASTAGE/exe
b. Run the following command:
./ctmdatastage_container setds <ds engine path>
EXAMPLE: ./ctmdatastage_container setds /opt/IBM/InformationServer/Server/DSEngine
9. To use the Control-M for IBM InfoSphere DataStage utilities in the CCM, run the ctmgetcm utility in the
Control-M/Server. For more information, see the Control-M Administrator Guide.
10. Continue with Installation on Control-M/EM (on page 12).
Installing Control-M for IBM InfoSphere DataStage on
Control-M/Agent on Windows
This procedure describes how to install Control-M for IBM InfoSphere DataStage on Control-M/Agent on
Windows.
If you want to install multiple instances of Control-M for IBM InfoSphere DataStage on several computers
using the same configuration, use the automatic installation, as described in this procedure.
Before You Begin
Make sure that the IBM InfoSphere DataStage client or IBM InfoSphere DataStage engine is installed on the
Control-M/Agent machine, and the Control-M/Agent has access and permission to run the IBM InfoSphere
DataStage DSJOB command line utility.
Control-M for IBM InfoSphere DataStage Administrator Guide
11
NOTE: The Control-M/Agent account must have all paths defined in order to run the DSJOB command line
utility.
Make sure that all jobs running on Control-M/Agent have ended.
 To install on Windows:
1. Log in to the computer as a user who has Administrator authorization.
2. Do one of the following:
• From the installation DVD, double-click the Setup.exe file.
• From a command prompt window, type <source_path>Setup.exe.
3. Do one of the following:
• Interactive install: Continue with the on-screen instructions until the installation is complete.
• Automatic install: Do the following:
a. Continue with the on-screen instructions until the Summary window.
b. Click Generate and select the location to create the XML parameter file.
c. Click Yes.
d. The automatic installation XML parameters file that is created (<filename>.xml) is relevant only
for computers with the same agent instance name. Otherwise, a separate <filename>.xml file
must be created for each computer, or modified manually for each computer.
e. Copy the automatic installation parameters file to a network location that is accessible to all
computers where you want to perform an automatic installation.
f. Run the installation script, as follows:
<installation_path>Setup.exe -silent <silent.xml>
The installation log can be found at the following location:
BMCINSTALLlogcmdatastageBMC_Control-M_For_IBM_InfoSphere_DataStage_Instal
l_<timestamp>.log
4. Set up the location of the IBM InfoSphere DataStage DSJOB for Control-M for IBM InfoSphere DataStage.
a. Navigate to:
<Agent dir>cmDATASTAGEexe
b. Run the following command:
ctmdatastage_container setds <dsjob path>
EXAMPLE: ctmdatastage_container setds c:IBMInformationServerClientsClassic
NOTE: Make sure that you provide only the path to the dsjob.exe file (without the file name).
5. To use the Control-M for IBM InfoSphere DataStage utilities in the CCM, you must run the ctmgetcm
utility in the Control-M/Server. For more information, see the Control-M Administrator Guide.
6. Continue with Installation on Control-M/EM (on page 12).
Control-M for IBM InfoSphere DataStage Administrator Guide
12
Installation on Control-M/EM
After you have installed Control-M for IBM InfoSphere DataStage on the Control-M/Agent, you must install
Control-M for IBM InfoSphere DataStage on the Control-M/EM client computer.
This procedure must be performed on every computer that has Control-M/EM client components installed.
The following procedures describe how to install the Control-M for IBM InfoSphere DataStage client and
server plug-in on Control-M/EM:
 Installing the Control-M for IBM InfoSphere DataStage client plug-in (on page 12)
 Enabling Find and Update support on Control-M/EM server (on page 13)
 Installing the Control-M Self Service plug-in (on page 14)
Installing the Control-M for IBM InfoSphere DataStage client plug-in
This procedure describes how to install Control-M for IBM InfoSphere DataStage on the Control-M/EM client,
which installs the CCM plug-in, imports the IBM InfoSphere DataStage form, and enables Find and Update
support.
Before you begin
Make sure that you have met the following requirements:
 Successful completion of one of the following:
• Installing Control-M for IBM InfoSphere DataStage on Control-M/Agent on UNIX (on page 9)
• Installing Control-M for IBM InfoSphere DataStage on Control-M/Agent on Windows (on page 10)
 Control-M for IBM InfoSphere DataStage DRDSG.8.0.00 DVD is mounted or accessible through your
network.
 Control-M/EM GUI server is shut down.
 Control-M/EM client applications are closed.
 To install on Control-M/EM client:
1. Do one of the following:
• If you download the Control-M for IBM InfoSphere DataStage 8.0.00 zip file from the BMC EPD site
for a Windows installation, you need to create the EM directory content that is required to install the
Control-M for IBM InfoSphere DataStage on the Control-M/EM client computer. Do the following:
a. Extract the files from the downloaded zip file.
b. Double-click the EM.exe self-extractor.
• If you download the Control-M for IBM InfoSphere DataStage 8.0.00 from the DVD, continue with
the next step.
2. Log in with a user ID with administrator privileges on the specific computer.
3. If you are not using Windows Vista, Windows 7, or Windows 2008, navigate to
<dvd_path>EMClient and continue with step 7.
Control-M for IBM InfoSphere DataStage Administrator Guide
13
4. Navigate to the following directory:
<dvd_path>EM
5. Copy or map the EM directory to your local disk.
6. Navigate to the mapped or copied directory:
<mapped/copied_location>EMClient
7. Run the Install_EM_Client_DataStage.cmd file, and follow the installation instructions provided.
You have installed the Control-M for IBM InfoSphere DataStage client on the Control-M Configuration
Manager. In addition, the IBM InfoSphere DataStage form is imported on the Control-M/EM client.
To use the Control-M for IBM InfoSphere DataStage utilities in the Control-M Configuration Manager,
make sure that the ctmgetcm utility has run in Control-M/Server. For more information, see the
Control-M Administrator Guide.
8. From the Control-M Configuration Manager, restart the Control-M/EM GUI server.
Enabling Find and Update support on Control-M/EM server
The following procedure describes how to enable Control-M for IBM InfoSphere DataStage Find and Update
support.
Before You Begin
Make sure that you have met the following requirements:
 You have successfully completed Installing the Control-M for IBM InfoSphere DataStage client plug-in
(on page 12).
 The Control-M for IBM InfoSphere DataStage DRDSG.8.0.00 DVD is mounted or accessible through your
network.
 The Control-M/EM GUI server is shut down.
 The Control-M/EM client applications are closed.
 To enable Find and Update support:
1. Do one of the following:
• If you download the Control-M for IBM InfoSphere DataStage 8.0.00 zip file from the BMC EPD site
for a Windows installation, you need to create the EM directory content that is required to enable find
and update support on the Control-M/EM server, do the following:
a. Extract the files from the downloaded zip file.
b. Double-click the EM.exe self-extractor.
• If you download the Control-M for IBM InfoSphere DataStage 8.0.00 from the DVD, continue with
the next step.
2. From the installation DVD, copy the DATASTAGE_appl.xml file located in the
<DVD>EMApplFields directory to one of the following Control-M/EM directories:
• Windows: <Control-M/EM home directory>etcapplfields
• UNIX: <Control-M/EM home directory>/etc/applfields/
Control-M for IBM InfoSphere DataStage Administrator Guide
14
3. From the Control-M Configuration Manager, restart the Control-M/EM GUI server.
After you have finished installing Control-M for IBM InfoSphere DataStage, you need to create an
account in the Control-M Configuration Manager, as described in CCM administration.
After you have created an account you can define a Control-M for IBM InfoSphere DataStage job, as
described in Control-M for IBM InfoSphere DataStage job definition.
Installing the Control-M Self Service plug-in
This procedure describes how to install the Control-M for IBM InfoSphere DataStage plug-in on Control-M
Self Service server.
 To install the Control-M Self Service plug-in:
1. Do one of the following:
• If you download the Control-M for IBM InfoSphere DataStage 8.0.00 zip file from the BMC EPD site
for a Windows installation, you need to create the EM directory content that is required to enable find
and update support on the Control-M/EM server, do the following:
a. Extract the files from the downloaded zip file.
b. Double-click the EM.exe self-extractor.
• If you download the Control-M for IBM InfoSphere DataStage 8.0.00 from the DVD, continue with
the next step.
2. From the installation DVD, copy the the content of the <DVD>EMSelfService directory to one of the
following directories:
• Windows: <Control-M/EM home directory>etc
• UNIX: <Control-M/EM home directory>/etc/
Control-M for IBM InfoSphere DataStage Uninstall
The following procedures describe how to uninstall Control-M for IBM InfoSphere DataStage from UNIX and
Microsoft Windows:
 Uninstalling Control-M for IBM InfoSphere DataStage from UNIX (on page 15)
 Uninstalling Control-M for IBM InfoSphere DataStage from Windows (on page 15)
 Performing an automatic uninstall from Windows (on page 16)
Control-M for IBM InfoSphere DataStage Administrator Guide
15
Uninstalling Control-M for IBM InfoSphere DataStage from UNIX
This procedure describes how to uninstall Control-M for IBM InfoSphere DataStage from UNIX.
Before You Begin
Make sure that all jobs have ended.
 To uninstall from UNIX:
1. From a Control-M/Agent computer, log in as a Control-M/Agent user, and type the following command to
shut down Control-M/Agent:
$CONTROLM/scripts/shut-ag -u <agentUser> -p all
NOTE: If the Control-M/Agent was installed with user root, then log in as user root every time you start
up or shut down the Control-M/Agent throughout this procedure.
2. If you are using an AIX operating system, you must remove unused libraries from memory by typing the
following command:
/usr/sbin/slibclean
3. Set your DISPLAY environment variable according to the computer name, as described in Setting
environment variables in UNIX (on page 8).
4. Type one of the following commands:
• Interactive: $HOME/BMCINSTALL/uninstall/DRDSG.8.0.00/uninstall.sh
• Automatic: $HOME/BMCINSTALL/uninstall/DRDSG.8.0.00/uninstall.sh -silent
Control-M for IBM InfoSphere DataStage has been successfully removed from your computer.
5. To restart Control-M/Agent, type the following command:
$CONTROLM/scripts/start-ag -u <agentUser> -p all
Uninstalling Control-M for IBM InfoSphere DataStage from Windows
This procedure describes how to uninstall Control-M for IBM InfoSphere DataStage from Windows.
Before You Begin
Make sure that all jobs have ended.
 To uninstall from Windows:
1. From the Start menu, select Settings > Control Panel.
2. Double-click Add/Remove Programs.
3. Select Control-M for IBM InfoSphere DataStage <Agent Name>, and click Add/Remove.
4. Click OK to continue.
Control-M for IBM InfoSphere DataStage is successfully removed from your computer.
Control-M for IBM InfoSphere DataStage Administrator Guide
16
Performing an automatic uninstall from Windows
This procedure describes how to perform an automatic uninstall from Windows.
Before You Begin
Make sure that all jobs have ended.
 To perform an automatic uninstall from Windows:
1. Log in to the computer using a user ID that has Administrator privileges.
2. Type the following command:
<Agent Install Path>BMCINSTALLuninstallDRDSG.8.0.00Uninstall.exe -silent
Control-M for IBM InfoSphere DataStage has been successfully removed from your computer.
17
3Chapter
3
Account management
Before you can define a Control-M for IBM InfoSphere DataStage job in the Control-M/Desktop, you need to
create an account in the Control-M Configuration Manager, which enables you to connect to the required IBM
InfoSphere DataStage server.
An account contains the connection parameters to a specified IBM InfoSphere DataStage server, such as
host name, user name, and password. By adding an account to the Control-M Configuration Manager, you
enable Control-M for IBM InfoSphere DataStage users to connect to the required IBM InfoSphere DataStage
server with only the account name. As a result, users can run a job without having to provide authentication
details every time they connect to the IBM InfoSphere DataStage server.
The following procedures describe how to create, edit, delete, test, copy, and export an account in the
Control-M Configuration Manager.
 Creating an Account (on page 17)
 Editing an account (on page 19)
 Deleting an account (on page 19)
 Testing an account (on page 20)
 Copying an account (on page 20)
 Exporting an account (on page 21)
Creating an Account
This procedure describes how to create an IBM InfoSphere DataStage account in the Control-M
Configuration Manager, which enables you to define an IBM InfoSphere DataStage job in the
Control-M/Desktop.
Before you begin
Make sure that you have set up the location of the IBM InfoSphere DataStage engine for Control-M for IBM
InfoSphere DataStage. For more information, see Installing Control-M for IBM InfoSphere DataStage on
Control-M/Agent on UNIX (on page 9) or Installing Control-M for IBM InfoSphere DataStage on
Control-M/Agent on Windows (on page 10).
 To create an account:
1. From Control-M Configuration Manager, right-click the CM (DATASTAGE) on the host that you want to
manage.
2. Select Account Management.
The Control-M for IBM InfoSphere DataStage Account Management dialog box appears.
Control-M for IBM InfoSphere DataStage Administrator Guide
18
3. Click the Add icon.
The Add Account dialog box appears.
4. In the Account Name field, enter the name of the account that you want to add. (The account name
must begin with a letter and without any blank spaces or special characters).
5. Select one of the following options:
• Local User: use only when Control-M for IBM InfoSphere DataStage is installed on an IBM
InfoSphere DataStage engine.
o Unix: IBM InfoSphere DataStage jobs run using the Control-M agent user account.
o Windows: IBM InfoSphere DataStage jobs run under the user specified in the Log On tab of the
Control-M/Agent Service Properties.
• Server Login (non-secured): use to connect to any remote IBM InfoSphere DataStage engine.
• Authentication File: use to connect to any remote IBM InfoSphere DataStage engine, using a local
credentials file. For more information about the credentials file, see your IBM InfoSphere DataStage
documentation.
NOTE: The available fields are determined by the option that you select.
6. For each field, enter the required value, as described in Control-M for IBM InfoSphere DataStage account
parameters (on page 18).
7. Click Next.
The Add Account - Summary dialog box appears.
8. (Optional) Review the account details, and click Test.
If the test was completed successfully, the account is validated and you can now define an IBM
InfoSphere DataStage job, as described in the Control-M for IBM InfoSphere DataStage Job Editing Form
Help in Defining a Control-M for IBM InfoSphere DataStage job (on page 23). If the test failed, review the
error message(s), fix any problems as necessary, and test the account again.
9. Click Finish.
The account is added to the Control-M for IBM InfoSphere DataStage Account Management
dialog box.
Control-M for IBM InfoSphere DataStage account
parameters
The following table lists the Set Connection Detail parameters to add an account.
Field Description
Server Name Defines the host name of the IBM InfoSphere DataStage engine
Domain Name (optional) Defines the domain of the IBM InfoSphere DataStage engine
User Name Defines the user name for the IBM InfoSphere DataStage engine
Control-M for IBM InfoSphere DataStage Administrator Guide
19
Field Description
Password Defines the password for the IBM InfoSphere DataStage engine
Confirm Password Confirms the password for the IBM InfoSphere DataStage engine
Authentication File Defines the full path, including the authentication file name of the local
credentials file for the IBM InfoSphere DataStage engine
Editing an account
This procedure describes how to edit an account in the Control-M Configuration Manager.
1. From Control-M Configuration Manager, right-click the CM (DATASTAGE) on the host that you want to
manage.
2. Select Account Management.
The Control-M for IBM InfoSphere DataStage Account Management dialog box appears.
3. Select the account that you want to edit, and click the Edit icon.
The Update <account> Account dialog box appears.
4. For each field, type the required value, as described in Control-M for IBM InfoSphere DataStage account
parameters (on page 18).
5. (Optional) Review the account details, and click Test.
If the test completed successfully, the account is validated and you can now define an IBM InfoSphere
DataStage job, as described in the Control-M for IBM InfoSphere DataStage Job Editing Form Help,
Defining a Control-M for IBM InfoSphere DataStage job (on page 23). If the test failed, review the error
message(s), fix any problems as necessary, and test the account again.
6. Click OK.
The account is updated in the Control-M for IBM InfoSphere DataStage Account Management
dialog box.
Deleting an account
This procedure describes how to delete an account from the Control-M Configuration Manager.
1. From Control-M Configuration Manager, right-click the CM (DATASTAGE) on the host that you want to
manage.
2. Select Account Management.
The Control-M for IBM InfoSphere DataStage Account Management dialog box appears.
3. Select the account that you want to delete, and click the Delete icon.
A confirmation message appears.
Control-M for IBM InfoSphere DataStage Administrator Guide
20
4. Click Yes.
The account is deleted.
Testing an account
This procedure describes how to test an account in the Control-M Configuration Manager, which enables you
to validate the connection parameters.
1. From Control-M Configuration Manager, right-click the CM (DATASTAGE) on the host that you want to
manage.
2. Select Account Management.
The Control-M for IBM InfoSphere DataStage Account Management dialog box appears.
3. Select the account that you want to test, and click .
If the test completed successfully, the account is validated and you can now define a IBM InfoSphere
DataStage job, as described in Defining a Control-M for IBM InfoSphere DataStage job (on page 23). If
the test failed, review the error message and test it again.
Copying an account
This procedure describes how to copy an account in the Control-M Configuration Manager, which enables
you to create an additional account using the parameters of an existing account.
 To copy an account:
1. From Control-M Configuration Manager, right-click the CM (DATASTAGE) on the host that you want to
manage.
2. Select Account Management.
The Control-M for IBM InfoSphere DataStage Account Management dialog box appears.
3. Select an account that you want to copy, and click .
The Copy <account> Account dialog box appears.
4. In the Account Name field, type a name for the new account, change any required parameters, and
then click OK.
5. (Optional) Click Test.
If the test completed successfully, the account is validated and you can now define a IBM InfoSphere
DataStage job, as described Defining a Control-M for IBM InfoSphere DataStage job (on page 23). If the
test failed, review the error message and test it again.
6. Click OK.
Control-M for IBM InfoSphere DataStage Administrator Guide
21
Exporting an account
This procedure describes how to export an account from one Control-M/Agent to another Control-M/Agent,
where Control-M for IBM InfoSphere DataStage is installed.
 To export an account:
1. From Control-M Configuration Manager, right-click the CM (DATASTAGE) on the host that you want to
manage.
2. Select Account Management.
The Control-M for IBM InfoSphere DataStage Account Management dialog box appears.
3. Select an account that you want to export and click .
The Account Management - Export Account Destination dialog box appears.
4. From the Control-M/Server name drop-down list, select the Control-M/Server that contains the
Control-M/Agent, where you want to export the account.
5. From the Control-M/CM Host Name drop-down list, select the Control-M/Agent that contains the
account on the CM you want to export.
6. Click OK.
The Export Account Destination dialog box appears.
7. In the Account Name field, type a name for the exported account and change any required parameters,
and then click OK.
8. (Optional) Click Test.
If the test completed successfully, the account is validated and you can now define a IBM InfoSphere
DataStage job, as described in the Control-M for IBM InfoSphere DataStage Job Editing Form Help
Defining a Control-M for IBM InfoSphere DataStage job (on page 23). If the test failed, review the error
message and test it again.
9. Click OK.
22
4Chapter
4
Job definition
Control-M for IBM InfoSphere DataStage is a control module that connects to an IBM InfoSphere DataStage
server and enables you to run IBM InfoSphere DataStage jobs, as described in Defining a Control-M for IBM
InfoSphere DataStage job (on page 23).
Control-M for IBM InfoSphere DataStage jobs are integrated with other Control-M jobs into a single
scheduling environment. Control-M capabilities are available for Control-M for IBM InfoSphere DataStage,
including advanced scheduling criteria, complex dependencies, quantitative and control resources, and
AutoEdit variables.
To access the IBM InfoSphere DataStage form, see Accessing the IBM InfoSphere DataStage form (on page
22).
Job definition parameters in Control-M for IBM InfoSphere DataStage enable you to apply values for the
AutoEdit variables, as described in the Control-M User Guide. For a list of Control-M for IBM InfoSphere
DataStage parameters, see Control-M for IBM InfoSphere DataStage parameters (on page 24).
Accessing the IBM InfoSphere DataStage form
This procedure describes how to access the IBM InfoSphere DataStage form, which enables you to define a
IBM InfoSphere DataStage job.
 To access the IBM InfoSphere DataStage form:
1. Log in to Control-M/Desktop, as described in the Control-M User Guide.
2. From the Edit menu, select New > Job.
3. From the Job Type dropdown list, select IBM InfoSphere DataStage.
4. Click the IBM InfoSphere DataStage tab.
The IBM InfoSphere DataStage form appears.
Control-M for IBM InfoSphere DataStage Administrator Guide
23
Defining a Control-M for IBM InfoSphere DataStage job
This procedure describes how to define a Control-M for IBM InfoSphere DataStage job, which enables you to
run IBM InfoSphere DataStage jobs on an IBM InfoSphere DataStage server.
Before You Begin
Make sure that you have met the following requirements:
 A configured IBM InfoSphere DataStage account, as described in Account management (on page 17).
 Successful completion of Accessing the IBM InfoSphere DataStage form (on page 22).
 To define an IBM InfoSphere DataStage job:
1. (Mandatory) In the Account field, do one of the following actions:
• Enter the account name.
• Click Load, select the account that you want, and click OK.
2. (Mandatory) In the Project field, do one of the following actions:
• Enter the project name.
• Click Load, select the project that you want, and click OK.
3. (Mandatory) In the Job Name field, do one of the following actions:
• Enter the job name.
• Click Load, select the job that you want, and click OK.
4. (Optional) In the Job Invocation ID field, enter the invocation ID for a multiple-instance job.
5. Do one of the following options:
• In the Parameter File field, enter the name of the parameter file that you want to use, or click
Load, and select a file from the list.
When clicking Load, a list of files in the <Agent dir>cmDATASTAGEparameters directory
appears. Make sure you have copied the parameters file to this location, and that the Agent user has
permissions to use this file.
• Click Load Parameters, and then click in the Value column to edit the value of a parameter.
6. In the Run options area, select any of the following options:
• Reset job before run: resets a job before it runs.
• Run in restart mode: runs a sequential job in restart mode.
7. Click Job Output to set the IBM InfoSphere DataStage log entry types that are written to the job Sysout.
8. Click Set limits to limit the number of rows and warnings. If you enter "0", the number of rows and
warnings is unlimited.
For more information about defining a job in the job editing form, see the Control-M User Guide.
Control-M for IBM InfoSphere DataStage Administrator Guide
24
Monitoring a job
While a Control-M for IBM InfoSphere DataStage job is running, you can monitor the progress of the job.
1. In the Control-M/EM GUI, locate the Control-M for IBM InfoSphere DataStage job that you want to
monitor.
2. Right-click the job, and select Sysout.
3. If more than one occurrence of the job appears in the list, select the sysout that you want to view.
The Sysout window appears.
If the job is still running on the IBM InfoSphere DataStage engine, an intermediate summary of the job
appears.
Control-M for IBM InfoSphere DataStage parameters
Job definition parameters in Control-M for IBM InfoSphere DataStage enable you to apply values for the
AutoEdit variables, as described in the Control-M User Guide.
The following table describes the parameters for Control-M for IBM InfoSphere DataStage.
Parameter Description
Account (on page 26) Defines the Control-M for IBM InfoSphere DataStage account.
Project (on page 29) Defines the Control-M for IBM InfoSphere DataStage project name.
Job Name (on page 27) Defines the Control-M for IBM InfoSphere DataStage job name.
Job Invocation ID (on page
27)
Defines the Control-M for IBM InfoSphere DataStage job invocation ID.
Parameter File (on page 28) Defines the Control-M for IBM InfoSphere DataStage parameter file.
Parameter Name (on page 28) Defines the name of a specific parameter.
Parameter Value (on page 28) Defines the value of a specific parameter.
Run in Restart Mode (on page
30)
Runs the Control-M for IBM InfoSphere DataStage job in Restart mode.
Reset Job Before Run (on page
30)
Resets the Control-M for IBM InfoSphere DataStage job before the job
runs.
Abort Job After <value>
Warnings (on page 25)
Sets the maximum number of warnings.
Control-M for IBM InfoSphere DataStage Administrator Guide
25
Parameter Description
Stop Stages After <value>
Rows (on page 31)
Sets the maximum number of rows.
Info (on page 27) Writes Info log entries to Control-M for IBM InfoSphere DataStage job
Sysout.
Warning (on page 31) Writes Warning log entries to Control-M for IBM InfoSphere
DataStage job Sysout.
Fatal (on page 26) Writes Fatal log entries to Control-M for IBM InfoSphere DataStage
job Sysout.
Reject (on page 29) Writes Reject log entries to Control-M for IBM InfoSphere DataStage
job Sysout.
Started (on page 30) Writes Started log entries to Control-M for IBM InfoSphere DataStage
job Sysout.
Reset (on page 29) Writes Reset log entries to Control-M for IBM InfoSphere DataStage
job Sysout.
Batch (on page 26) Writes Batch log entries to Control-M for IBM InfoSphere DataStage
job Sysout.
Abort Job After <value> Warnings
Sets the maximum number of warnings.
Usage Optional
Valid Values 0-9999999
Default Value 0
Case Sensitive No
Variable Name %%DataStage-MAX_WARNINGS
Control-M for IBM InfoSphere DataStage Administrator Guide
26
Account
Defines the Control-M for IBM InfoSphere DataStage account.
Usage Mandatory
Length 1 - 30 characters
Case Sensitive Yes - only capital letters
Variable Name %%DataStage-ACCOUNT
Batch
Writes Batch log entries to Control-M for IBM InfoSphere DataStage job Sysout.
Usage Optional
Valid Values Yes, No
Default Value No
Case Sensitive Yes
Variable Name %%DataStage-OUTPUT_BATCH
Fatal
Writes Fatal log entries to Control-M for IBM InfoSphere DataStage job Sysout.
Usage Optional
Valid Values Yes, No
Default Value Yes
Case Sensitive Yes
Variable Name %%DataStage-OUTPUT_FATAL
Control-M for IBM InfoSphere DataStage Administrator Guide
27
Info
Writes Info log entries to Control-M for IBM InfoSphere DataStage job Sysout.
Usage Optional
Valid Values Yes, No
Default Value No
Case Sensitive Yes
Variable Name %%DataStage-OUTPUT_INFO
Job Invocation ID
Defines the Control-M for IBM InfoSphere DataStage job invocation ID.
Usage Optional
Case Sensitive Yes
Variable Name %%DataStage-JOB_INVOCATION_ID
Job Name
Defines the Control-M for IBM InfoSphere DataStage job name.
Usage Mandatory
Case Sensitive Yes
Variable Name %%DataStage-JOB_NAME
Control-M for IBM InfoSphere DataStage Administrator Guide
28
Parameter File
Defines the Control-M for IBM InfoSphere DataStage parameter file.
Usage Optional
Case Sensitive Yes
Variable Name %%DataStage-PARAMS_FILE
Parameter Name
Defines the name of a specific parameter.
Usage Optional
Case Sensitive Yes
Variable Name %%DataStage-PARAMS-Pxxx-PRM_NAME
xxx determines the parameter number between 001-999
Parameter Value
Defines the value of a specific parameter.
Usage Optional
Case Sensitive Yes
Variable Name %%DataStage-PARAMS-Pxxx-PRM_VALUE
xxx determines the parameter number between 001-999
Control-M for IBM InfoSphere DataStage Administrator Guide
29
Project
Defines the Control-M for IBM InfoSphere DataStage project name.
Usage Mandatory
Case Sensitive Yes
Variable Name %%DataStage-PROJECT
Reject
Writes Reject log entries to Control-M for IBM InfoSphere DataStage job Sysout.
Usage Optional
Valid Values Yes, No
Default Value No
Case Sensitive Yes
Variable Name %%DataStage-OUTPUT_REJECT
Reset
Writes Reset log entries to Control-M for IBM InfoSphere DataStage job Sysout.
Usage Optional
Valid Values Yes, No
Default Value No
Case Sensitive Yes
Variable Name %%DataStage-OUTPUT_RESET
Control-M for IBM InfoSphere DataStage Administrator Guide
30
Reset Job Before Run
Resets the Control-M for IBM InfoSphere DataStage job before the job runs.
Usage Optional
Valid Values Yes, No
Default Value Yes
Case Sensitive Yes
Variable Name %%DataStage-RESET_JOB
Run in Restart Mode
Runs the Control-M for IBM InfoSphere DataStage job in Restart mode.
Usage Optional
Valid Values Yes, No
Default Value No
Case Sensitive Yes
Variable Name %%DataStage-RESTART_SEQUENCE
Started
Writes Started log entries to Control-M for IBM InfoSphere DataStage job Sysout.
Usage Optional
Valid Values Yes, No
Default Value No
Case Sensitive Yes
Variable Name %%DataStage-OUTPUT_STARTED
Control-M for IBM InfoSphere DataStage Administrator Guide
31
Stop Stages After <value> Rows
Sets the maximum number of rows.
Usage Optional
Valid Values 0-9999999
Variable Name %%DataStage-MAX_ROWS
Warning
Writes Warning log entries to Control-M for IBM InfoSphere DataStage job Sysout.
Usage Optional
Valid Values Yes, No
Default Value No
Case Sensitive Yes
Variable Name %%DataStage-OUTPUT_WARNING
Control m ibm info shpere data stage control module

Weitere ähnliche Inhalte

Was ist angesagt?

Hints for a successful hfs to zfs migration
Hints for a successful hfs to zfs migrationHints for a successful hfs to zfs migration
Hints for a successful hfs to zfs migration
satish090909
 
Cinema levantamento de requisitos 42756538
Cinema levantamento de requisitos   42756538Cinema levantamento de requisitos   42756538
Cinema levantamento de requisitos 42756538
Alex Sampaio
 
S18_ゼロトラストを目指し、Windows 10 & M365E5 を徹底活用した弊社 (三井情報) 事例のご紹介 [Microsoft Japan D...
S18_ゼロトラストを目指し、Windows 10 & M365E5 を徹底活用した弊社 (三井情報) 事例のご紹介 [Microsoft Japan D...S18_ゼロトラストを目指し、Windows 10 & M365E5 を徹底活用した弊社 (三井情報) 事例のご紹介 [Microsoft Japan D...
S18_ゼロトラストを目指し、Windows 10 & M365E5 を徹底活用した弊社 (三井情報) 事例のご紹介 [Microsoft Japan D...
日本マイクロソフト株式会社
 
Parallel Sysplex Implement2
Parallel Sysplex Implement2Parallel Sysplex Implement2
Parallel Sysplex Implement2
ggddggddggdd
 

Was ist angesagt? (20)

Plano de teste
Plano de testePlano de teste
Plano de teste
 
LTO/オートローダー/仮想テープライブラリの基礎知識
LTO/オートローダー/仮想テープライブラリの基礎知識LTO/オートローダー/仮想テープライブラリの基礎知識
LTO/オートローダー/仮想テープライブラリの基礎知識
 
Teste de software - Processo de Verificação e Validação
Teste de software - Processo de Verificação e ValidaçãoTeste de software - Processo de Verificação e Validação
Teste de software - Processo de Verificação e Validação
 
Hints for a successful hfs to zfs migration
Hints for a successful hfs to zfs migrationHints for a successful hfs to zfs migration
Hints for a successful hfs to zfs migration
 
Improving the Performance of the qcow2 Format (KVM Forum 2017)
Improving the Performance of the qcow2 Format (KVM Forum 2017)Improving the Performance of the qcow2 Format (KVM Forum 2017)
Improving the Performance of the qcow2 Format (KVM Forum 2017)
 
IBM WebSphere Application Server version to version comparison
IBM WebSphere Application Server version to version comparisonIBM WebSphere Application Server version to version comparison
IBM WebSphere Application Server version to version comparison
 
Testes de Software
Testes de SoftwareTestes de Software
Testes de Software
 
Utilizando views, stored procedures e triggers
Utilizando views, stored procedures e triggersUtilizando views, stored procedures e triggers
Utilizando views, stored procedures e triggers
 
TechWiseTV Workshop: Cisco HyperFlex Systems
TechWiseTV Workshop: Cisco HyperFlex SystemsTechWiseTV Workshop: Cisco HyperFlex Systems
TechWiseTV Workshop: Cisco HyperFlex Systems
 
Hybrid Azure AD Join 動作の仕組みを徹底解説
Hybrid Azure AD Join 動作の仕組みを徹底解説Hybrid Azure AD Join 動作の仕組みを徹底解説
Hybrid Azure AD Join 動作の仕組みを徹底解説
 
CE-4028, Miracast with AMD Wireless Display technology – Kickass gaming and o...
CE-4028, Miracast with AMD Wireless Display technology – Kickass gaming and o...CE-4028, Miracast with AMD Wireless Display technology – Kickass gaming and o...
CE-4028, Miracast with AMD Wireless Display technology – Kickass gaming and o...
 
Interface Humano Computador - Aula03 - design de experiência de usuário e aná...
Interface Humano Computador - Aula03 - design de experiência de usuário e aná...Interface Humano Computador - Aula03 - design de experiência de usuário e aná...
Interface Humano Computador - Aula03 - design de experiência de usuário e aná...
 
Voice over IP (VoIP) Deployment with Aruba Mobility Access Switch
Voice over IP (VoIP) Deployment with Aruba Mobility Access SwitchVoice over IP (VoIP) Deployment with Aruba Mobility Access Switch
Voice over IP (VoIP) Deployment with Aruba Mobility Access Switch
 
Cinema levantamento de requisitos 42756538
Cinema levantamento de requisitos   42756538Cinema levantamento de requisitos   42756538
Cinema levantamento de requisitos 42756538
 
BMC Control M Advantage
BMC Control M Advantage BMC Control M Advantage
BMC Control M Advantage
 
S18_ゼロトラストを目指し、Windows 10 & M365E5 を徹底活用した弊社 (三井情報) 事例のご紹介 [Microsoft Japan D...
S18_ゼロトラストを目指し、Windows 10 & M365E5 を徹底活用した弊社 (三井情報) 事例のご紹介 [Microsoft Japan D...S18_ゼロトラストを目指し、Windows 10 & M365E5 を徹底活用した弊社 (三井情報) 事例のご紹介 [Microsoft Japan D...
S18_ゼロトラストを目指し、Windows 10 & M365E5 を徹底活用した弊社 (三井情報) 事例のご紹介 [Microsoft Japan D...
 
Parallel Sysplex Implement2
Parallel Sysplex Implement2Parallel Sysplex Implement2
Parallel Sysplex Implement2
 
O que é Teste de Software?
O que é Teste de Software?O que é Teste de Software?
O que é Teste de Software?
 
Analise de Requisitos Software
Analise de Requisitos SoftwareAnalise de Requisitos Software
Analise de Requisitos Software
 
Aruba Instant 6.4.0.2-4.1 Command Line Interface Reference Guide
Aruba Instant 6.4.0.2-4.1 Command Line Interface Reference GuideAruba Instant 6.4.0.2-4.1 Command Line Interface Reference Guide
Aruba Instant 6.4.0.2-4.1 Command Line Interface Reference Guide
 

Ähnlich wie Control m ibm info shpere data stage control module

Symantec Backup Exec 15 Administrator's Guide
Symantec Backup Exec 15 Administrator's GuideSymantec Backup Exec 15 Administrator's Guide
Symantec Backup Exec 15 Administrator's Guide
Symantec
 
Backup Exec 15 Tuning and Performance Guide
Backup Exec 15 Tuning and Performance GuideBackup Exec 15 Tuning and Performance Guide
Backup Exec 15 Tuning and Performance Guide
Symantec
 
vxfs_admin_51sp1_hpux
vxfs_admin_51sp1_hpuxvxfs_admin_51sp1_hpux
vxfs_admin_51sp1_hpux
E. Balauca
 

Ähnlich wie Control m ibm info shpere data stage control module (20)

Cm peoplesoft admin
Cm peoplesoft adminCm peoplesoft admin
Cm peoplesoft admin
 
Automatic Performance Improvement for Legacy COBOL
Automatic Performance Improvement for Legacy COBOLAutomatic Performance Improvement for Legacy COBOL
Automatic Performance Improvement for Legacy COBOL
 
Symantec Backup Exec 15 Administrator's Guide
Symantec Backup Exec 15 Administrator's GuideSymantec Backup Exec 15 Administrator's Guide
Symantec Backup Exec 15 Administrator's Guide
 
z/OS V2R2 Enhancements
z/OS V2R2 Enhancementsz/OS V2R2 Enhancements
z/OS V2R2 Enhancements
 
Backup Exec 15 Tuning and Performance Guide
Backup Exec 15 Tuning and Performance GuideBackup Exec 15 Tuning and Performance Guide
Backup Exec 15 Tuning and Performance Guide
 
Z cloud with technical details
 Z cloud with technical details Z cloud with technical details
Z cloud with technical details
 
Server pac 101
Server pac 101Server pac 101
Server pac 101
 
Accel series 2020_summer en
Accel series 2020_summer enAccel series 2020_summer en
Accel series 2020_summer en
 
What is different about the ibm mainframe
What is different about the ibm mainframeWhat is different about the ibm mainframe
What is different about the ibm mainframe
 
Training Report
Training ReportTraining Report
Training Report
 
Acma Computers - Fms & Ims
Acma Computers - Fms & ImsAcma Computers - Fms & Ims
Acma Computers - Fms & Ims
 
BLADEHarmony Manager
BLADEHarmony ManagerBLADEHarmony Manager
BLADEHarmony Manager
 
IBM i and digital transformation
IBM i and digital transformationIBM i and digital transformation
IBM i and digital transformation
 
vxfs_admin_51sp1_hpux
vxfs_admin_51sp1_hpuxvxfs_admin_51sp1_hpux
vxfs_admin_51sp1_hpux
 
Changing the Status Quo for Small Business IT Solutions
Changing the Status Quo for Small Business IT SolutionsChanging the Status Quo for Small Business IT Solutions
Changing the Status Quo for Small Business IT Solutions
 
Data link mamut_magento
Data link mamut_magentoData link mamut_magento
Data link mamut_magento
 
Resume
ResumeResume
Resume
 
Vofflps
VofflpsVofflps
Vofflps
 
2016 02-16-announce-overview-zsp04505 usen
2016 02-16-announce-overview-zsp04505 usen2016 02-16-announce-overview-zsp04505 usen
2016 02-16-announce-overview-zsp04505 usen
 
Don't Risk Your Reputation or Your Mainframe: Best Practices for Demonstratin...
Don't Risk Your Reputation or Your Mainframe: Best Practices for Demonstratin...Don't Risk Your Reputation or Your Mainframe: Best Practices for Demonstratin...
Don't Risk Your Reputation or Your Mainframe: Best Practices for Demonstratin...
 

Kürzlich hochgeladen

CNv6 Instructor Chapter 6 Quality of Service
CNv6 Instructor Chapter 6 Quality of ServiceCNv6 Instructor Chapter 6 Quality of Service
CNv6 Instructor Chapter 6 Quality of Service
giselly40
 

Kürzlich hochgeladen (20)

A Domino Admins Adventures (Engage 2024)
A Domino Admins Adventures (Engage 2024)A Domino Admins Adventures (Engage 2024)
A Domino Admins Adventures (Engage 2024)
 
Evaluating the top large language models.pdf
Evaluating the top large language models.pdfEvaluating the top large language models.pdf
Evaluating the top large language models.pdf
 
Handwritten Text Recognition for manuscripts and early printed texts
Handwritten Text Recognition for manuscripts and early printed textsHandwritten Text Recognition for manuscripts and early printed texts
Handwritten Text Recognition for manuscripts and early printed texts
 
Automating Google Workspace (GWS) & more with Apps Script
Automating Google Workspace (GWS) & more with Apps ScriptAutomating Google Workspace (GWS) & more with Apps Script
Automating Google Workspace (GWS) & more with Apps Script
 
Scaling API-first – The story of a global engineering organization
Scaling API-first – The story of a global engineering organizationScaling API-first – The story of a global engineering organization
Scaling API-first – The story of a global engineering organization
 
Axa Assurance Maroc - Insurer Innovation Award 2024
Axa Assurance Maroc - Insurer Innovation Award 2024Axa Assurance Maroc - Insurer Innovation Award 2024
Axa Assurance Maroc - Insurer Innovation Award 2024
 
Raspberry Pi 5: Challenges and Solutions in Bringing up an OpenGL/Vulkan Driv...
Raspberry Pi 5: Challenges and Solutions in Bringing up an OpenGL/Vulkan Driv...Raspberry Pi 5: Challenges and Solutions in Bringing up an OpenGL/Vulkan Driv...
Raspberry Pi 5: Challenges and Solutions in Bringing up an OpenGL/Vulkan Driv...
 
Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
 
The Role of Taxonomy and Ontology in Semantic Layers - Heather Hedden.pdf
The Role of Taxonomy and Ontology in Semantic Layers - Heather Hedden.pdfThe Role of Taxonomy and Ontology in Semantic Layers - Heather Hedden.pdf
The Role of Taxonomy and Ontology in Semantic Layers - Heather Hedden.pdf
 
TrustArc Webinar - Stay Ahead of US State Data Privacy Law Developments
TrustArc Webinar - Stay Ahead of US State Data Privacy Law DevelopmentsTrustArc Webinar - Stay Ahead of US State Data Privacy Law Developments
TrustArc Webinar - Stay Ahead of US State Data Privacy Law Developments
 
Exploring the Future Potential of AI-Enabled Smartphone Processors
Exploring the Future Potential of AI-Enabled Smartphone ProcessorsExploring the Future Potential of AI-Enabled Smartphone Processors
Exploring the Future Potential of AI-Enabled Smartphone Processors
 
presentation ICT roal in 21st century education
presentation ICT roal in 21st century educationpresentation ICT roal in 21st century education
presentation ICT roal in 21st century education
 
Finology Group – Insurtech Innovation Award 2024
Finology Group – Insurtech Innovation Award 2024Finology Group – Insurtech Innovation Award 2024
Finology Group – Insurtech Innovation Award 2024
 
2024: Domino Containers - The Next Step. News from the Domino Container commu...
2024: Domino Containers - The Next Step. News from the Domino Container commu...2024: Domino Containers - The Next Step. News from the Domino Container commu...
2024: Domino Containers - The Next Step. News from the Domino Container commu...
 
Understanding Discord NSFW Servers A Guide for Responsible Users.pdf
Understanding Discord NSFW Servers A Guide for Responsible Users.pdfUnderstanding Discord NSFW Servers A Guide for Responsible Users.pdf
Understanding Discord NSFW Servers A Guide for Responsible Users.pdf
 
CNv6 Instructor Chapter 6 Quality of Service
CNv6 Instructor Chapter 6 Quality of ServiceCNv6 Instructor Chapter 6 Quality of Service
CNv6 Instructor Chapter 6 Quality of Service
 
08448380779 Call Girls In Greater Kailash - I Women Seeking Men
08448380779 Call Girls In Greater Kailash - I Women Seeking Men08448380779 Call Girls In Greater Kailash - I Women Seeking Men
08448380779 Call Girls In Greater Kailash - I Women Seeking Men
 
Data Cloud, More than a CDP by Matt Robison
Data Cloud, More than a CDP by Matt RobisonData Cloud, More than a CDP by Matt Robison
Data Cloud, More than a CDP by Matt Robison
 
The 7 Things I Know About Cyber Security After 25 Years | April 2024
The 7 Things I Know About Cyber Security After 25 Years | April 2024The 7 Things I Know About Cyber Security After 25 Years | April 2024
The 7 Things I Know About Cyber Security After 25 Years | April 2024
 
How to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected WorkerHow to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected Worker
 

Control m ibm info shpere data stage control module

  • 1. www.bmc.com Control-M for IBM InfoSphere DataStage 8.0.00 Administrator Guide November 2012
  • 2. 2 Contacting BMC Software You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information about the company, its products, corporate offices, special events, and career opportunities. United States and Canada Address BMC SOFTWARE INC 2101 CITYWEST BLVD HOUSTON TX 77042-2827 USA Telephone  713 918 8800  800 841 2031 Fax 713 918 8000 May 14, 2012 Outside United States and Canada Telephone (01) 713 918 8800 Fax (01) 713 918 8000 © Copyright 2012 BMC Software, Inc. BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners. IT Infrastructure Library® is a registered trademark of the Office of Government Commerce and is used here by BMC Software, Inc., under license from and with the permission of OGC. ITIL® is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office, and is used here by BMC Software, Inc., under license from and with the permission of OGC. Linux is the registered trademark of Linus Torvalds. Oracle is a registered trademark of Oracle Corporation. UNIX is the registered trademark of The Open Group in the US and other countries. 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. Restricted rights legend U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC SOFTWARE INC, 2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA. Any contract notices should be sent to this address.
  • 3. 3 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 Support by telephone or e-mail In the United States and Canada, if you need technical support and do not have access to the web, call 800 537 1813 or send an e-mail message to customer_support@bmc.com. (In the subject line, enter SupID:<yourSupportContractID>, such as SupID:12345). Outside the United States and Canada, contact your local support center for assistance. Before contacting BMC Have the following information available so that Customer Support can begin working on your issue immediately:  product information • product name • product version (release number) • license number and password (trial or permanent)  operating system and environment information • 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
  • 4. 4  sequence of events leading to the issue  commands and options that you used  messages received (and the time and date that you received them) • product error messages • messages from the operating system, such as file system full • messages from related software License key and password information If you have questions about your license key or password, contact BMC as follows:  (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.
  • 5. 5 Contents Introduction to Control-M for IBM InfoSphere DataStage ...................................................6 Control-M for IBM InfoSphere DataStage overview...........................................................................6 Administrative roles........................................................................................................................6 Installation ....................................................................................................................8 Setting environment variables in UNIX.............................................................................................8 Installing Control-M for IBM InfoSphere DataStage on Control-M/Agent on UNIX ...............................9 Installing Control-M for IBM InfoSphere DataStage on Control-M/Agent on Windows........................10 Installation on Control-M/EM.........................................................................................................12 Control-M for IBM InfoSphere DataStage Uninstall..........................................................................14 Account management................................................................................................... 17 Creating an Account .....................................................................................................................17 Control-M for IBM InfoSphere DataStage account parameters.........................................................18 Editing an account........................................................................................................................19 Deleting an account......................................................................................................................19 Testing an account .......................................................................................................................20 Copying an account......................................................................................................................20 Exporting an account....................................................................................................................21 Job definition ............................................................................................................... 22 Accessing the IBM InfoSphere DataStage form...............................................................................22 Defining a Control-M for IBM InfoSphere DataStage job .................................................................23 Monitoring a job...........................................................................................................................24 Control-M for IBM InfoSphere DataStage parameters .....................................................................24
  • 6. 6 1Chapter 1 Introduction to Control-M for IBM InfoSphere DataStage Control-M for IBM InfoSphere DataStage overview Control-M for IBM InfoSphere DataStage is a control module that enables you to run and execute pre-defined IBM InfoSphere DataStage jobs. Before you begin, do the following:  Install Control-M for IBM InfoSphere DataStage, as described in Installation.  Connect to an IBM InfoSphere DataStage server as described in CCM administration. Control-M for IBM InfoSphere DataStage jobs are integrated with other Control-M jobs into a single scheduling environment. This enables you to control and operate IBM InfoSphere DataStage jobs from within Control-M. You can also do the following:  Define and monitor Control-M for IBM InfoSphere DataStage jobs, as described in Control-M for IBM InfoSphere DataStage job definition.  Integrate IBM InfoSphere DataStage jobs with other Control-M jobs into a single scheduling environment, as described in the Control-M User Guide.  Introduce all Control-M capabilities to IBM InfoSphere DataStage, including advanced scheduling criteria, complex dependencies, quantitative and control resources, and AutoEdit variables, as described in the Control-M User Guide. Administrative roles Certain Control-M for IBM InfoSphere DataStage tasks might need to be performed by different professionals in your organization, as follows:  System Administrator: Responsible for reviewing the system requirements and performing the installation process.  Control-M Administrator: Responsible for the administration of all Control-M processes.  Control-M Production Controller: Responsible for defining and/or monitoring Control-M jobs. The following table lists the tasks performed when working with the Control-M for IBM InfoSphere DataStage and the role of the professional who is responsible for its administration.
  • 7. Control-M for IBM InfoSphere DataStage Administrator Guide 7 Tasks Roles Install Control-M for IBM InfoSphere DataStage on a Control-M/Agent on UNIX, as described in Installing Control-M for IBM InfoSphere DataStage on Control-M/Agent on UNIX (on page 9) and on Windows, as described in Installing Control-M for IBM InfoSphere DataStage on Control-M/Agent on Windows (on page 10).  System Administrator  Control-M Administrator Install Control-M for IBM InfoSphere DataStage on a Control-M/Enterprise Manager (Control-M/EM) client, as described in Installation on Control-M/EM (on page 12).  System Administrator  Control-M Administrator Manage Control-M for IBM InfoSphere DataStage accounts, as described in CCM administration.  Control-M Administrator Define Control-M for IBM InfoSphere DataStage jobs, as described in Control-M for IBM InfoSphere DataStage job definition.  Control-M Administrator
  • 8. 8 2Chapter 2 Installation Control-M for IBM InfoSphere DataStage can be installed on Windows and UNIX on a Control-M/Agent. The Control-M/Agent on which you install Control-M for IBM InfoSphere DataStage must also have the IBM InfoSphere DataStage client or IBM InfoSphere DataStage engine installed on it. The IBM InfoSphere DataStage form and the CCM client plug-in must be installed on a Control-M/EM client. The following procedures describe how to install Control-M for IBM InfoSphere DataStage. Setting environment variables in UNIX (on page 8): describes how to set environment variables in UNIX Installing Control-M for IBM InfoSphere DataStage on Control-M/Agent on UNIX (on page 9): describes how to install Control-M for IBM InfoSphere DataStage on Control-M/Agent on UNIX via regular and automatic installation Installing Control-M for IBM InfoSphere DataStage on Control-M/Agent on Windows (on page 10): describes how to install Control-M for IBM InfoSphere DataStage on Control-M/Agent on Windows via regular and automatic installation Installation on Control-M/EM (on page 12): describes how to install Control-M for IBM InfoSphere DataStage on a Control-M/EM client Setting environment variables in UNIX This procedure describes how to set environment variables in UNIX, which enables you to see messages from the console. 1. Do one of the following: • If you use csh or tcsh, use the following syntax: setenv <envVar> <value> Example: setenv DISPLAY myhost:0.0 • If you use sh or ksh, use the following syntax: <envVar>=<value> export <envVar> Example: DISPLAY=myhost:0.0 export DISPLAY <envVar> is the name of the environment variable. <value> is the value assigned to the environment variable.
  • 9. Control-M for IBM InfoSphere DataStage Administrator Guide 9 Installing Control-M for IBM InfoSphere DataStage on Control-M/Agent on UNIX This procedure describes how to install Control-M for IBM InfoSphere DataStage on Control-M/Agent on UNIX interactively or automatically. If you want to install multiple instances of Control-M for IBM InfoSphere DataStage on several computers using the same configuration, use the automatic installation, as described in this procedure. 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, BMC recommends that you continue with the console installation or perform an automatic installation. Before You Begin Make sure that the IBM InfoSphere DataStage client or IBM InfoSphere DataStage engine is installed on the Control-M/Agent machine, and the Control-M/Agent has access and permission to run the IBM InfoSphere DataStage DSJOB command line utility. NOTE: The Control-M/Agent account must have all paths defined in order to run the DSJOB command line utility. Make sure that all jobs running on Control-M/Agent have ended.  To install on UNIX: 1. Log in as the Control-M/Agent user, and stop the Control-M/Agent by typing the following command: $CONTROLM/scripts/shut-ag -u <agentUser> -p all NOTE: If the Control-M/Agent was installed with user root, then log in as user root every time you start up or shut down the Control-M/Agent throughout this procedure. If you are using an AIX operating system, you must remove unused libraries from memory, by typing the following command as a root user: /usr/sbin/slibclean 2. Do one of the following: • Mount the installation DVD. • Extract the files from the temporary directory that you created when obtaining the installation files via EPD (see Control-M for IBM InfoSphere DataStage Release Notes). 3. Use one of the following modes: • Display: if you install using GUI (or XServer), set your DISPLAY environment variable, as described in Setting environment variables in UNIX (on page 8). • Console: it is not necessary to set DISPLAY. 4. From the installation DVD or from the installation files via EPD, activate the installation script with the following command: <source_path>/setup.sh
  • 10. Control-M for IBM InfoSphere DataStage Administrator Guide 10 5. Do one of the following: • Interactive install: continue with the on-screen instructions until the installation is complete. • Automatic install: do the following: a. Continue with the on-screen instructions until the Summary window. b. Click Generate and select the location to create the XML parameter file. c. Click Yes. d. Copy the automatic installation parameters file to a network location that is accessible to all computers where you want to perform an automatic installation. e. To run the installation script, type the following command: <source_path>/setup.sh -silent <filename.xml> The installation logs can be found at the following location: $HOME/BMCINSTALL/log/cmdatastage/BMC_Control-M_For_IBM_InfoSphere_DataStag e_Install_<date-time>.log 6. Start the Control-M/Agent by running the following command: $CONTROLM/scripts/start-ag -u <agentUser> -p all 7. Log out of the Control-M/Agent account. 8. Set up the location of the IBM InfoSphere DataStage engine for Control-M for IBM InfoSphere DataStage. a. Navigate to: <Agent dir>/cm/DATASTAGE/exe b. Run the following command: ./ctmdatastage_container setds <ds engine path> EXAMPLE: ./ctmdatastage_container setds /opt/IBM/InformationServer/Server/DSEngine 9. To use the Control-M for IBM InfoSphere DataStage utilities in the CCM, run the ctmgetcm utility in the Control-M/Server. For more information, see the Control-M Administrator Guide. 10. Continue with Installation on Control-M/EM (on page 12). Installing Control-M for IBM InfoSphere DataStage on Control-M/Agent on Windows This procedure describes how to install Control-M for IBM InfoSphere DataStage on Control-M/Agent on Windows. If you want to install multiple instances of Control-M for IBM InfoSphere DataStage on several computers using the same configuration, use the automatic installation, as described in this procedure. Before You Begin Make sure that the IBM InfoSphere DataStage client or IBM InfoSphere DataStage engine is installed on the Control-M/Agent machine, and the Control-M/Agent has access and permission to run the IBM InfoSphere DataStage DSJOB command line utility.
  • 11. Control-M for IBM InfoSphere DataStage Administrator Guide 11 NOTE: The Control-M/Agent account must have all paths defined in order to run the DSJOB command line utility. Make sure that all jobs running on Control-M/Agent have ended.  To install on Windows: 1. Log in to the computer as a user who has Administrator authorization. 2. Do one of the following: • From the installation DVD, double-click the Setup.exe file. • From a command prompt window, type <source_path>Setup.exe. 3. Do one of the following: • Interactive install: Continue with the on-screen instructions until the installation is complete. • Automatic install: Do the following: a. Continue with the on-screen instructions until the Summary window. b. Click Generate and select the location to create the XML parameter file. c. Click Yes. d. The automatic installation XML parameters file that is created (<filename>.xml) is relevant only for computers with the same agent instance name. Otherwise, a separate <filename>.xml file must be created for each computer, or modified manually for each computer. e. Copy the automatic installation parameters file to a network location that is accessible to all computers where you want to perform an automatic installation. f. Run the installation script, as follows: <installation_path>Setup.exe -silent <silent.xml> The installation log can be found at the following location: BMCINSTALLlogcmdatastageBMC_Control-M_For_IBM_InfoSphere_DataStage_Instal l_<timestamp>.log 4. Set up the location of the IBM InfoSphere DataStage DSJOB for Control-M for IBM InfoSphere DataStage. a. Navigate to: <Agent dir>cmDATASTAGEexe b. Run the following command: ctmdatastage_container setds <dsjob path> EXAMPLE: ctmdatastage_container setds c:IBMInformationServerClientsClassic NOTE: Make sure that you provide only the path to the dsjob.exe file (without the file name). 5. To use the Control-M for IBM InfoSphere DataStage utilities in the CCM, you must run the ctmgetcm utility in the Control-M/Server. For more information, see the Control-M Administrator Guide. 6. Continue with Installation on Control-M/EM (on page 12).
  • 12. Control-M for IBM InfoSphere DataStage Administrator Guide 12 Installation on Control-M/EM After you have installed Control-M for IBM InfoSphere DataStage on the Control-M/Agent, you must install Control-M for IBM InfoSphere DataStage on the Control-M/EM client computer. This procedure must be performed on every computer that has Control-M/EM client components installed. The following procedures describe how to install the Control-M for IBM InfoSphere DataStage client and server plug-in on Control-M/EM:  Installing the Control-M for IBM InfoSphere DataStage client plug-in (on page 12)  Enabling Find and Update support on Control-M/EM server (on page 13)  Installing the Control-M Self Service plug-in (on page 14) Installing the Control-M for IBM InfoSphere DataStage client plug-in This procedure describes how to install Control-M for IBM InfoSphere DataStage on the Control-M/EM client, which installs the CCM plug-in, imports the IBM InfoSphere DataStage form, and enables Find and Update support. Before you begin Make sure that you have met the following requirements:  Successful completion of one of the following: • Installing Control-M for IBM InfoSphere DataStage on Control-M/Agent on UNIX (on page 9) • Installing Control-M for IBM InfoSphere DataStage on Control-M/Agent on Windows (on page 10)  Control-M for IBM InfoSphere DataStage DRDSG.8.0.00 DVD is mounted or accessible through your network.  Control-M/EM GUI server is shut down.  Control-M/EM client applications are closed.  To install on Control-M/EM client: 1. Do one of the following: • If you download the Control-M for IBM InfoSphere DataStage 8.0.00 zip file from the BMC EPD site for a Windows installation, you need to create the EM directory content that is required to install the Control-M for IBM InfoSphere DataStage on the Control-M/EM client computer. Do the following: a. Extract the files from the downloaded zip file. b. Double-click the EM.exe self-extractor. • If you download the Control-M for IBM InfoSphere DataStage 8.0.00 from the DVD, continue with the next step. 2. Log in with a user ID with administrator privileges on the specific computer. 3. If you are not using Windows Vista, Windows 7, or Windows 2008, navigate to <dvd_path>EMClient and continue with step 7.
  • 13. Control-M for IBM InfoSphere DataStage Administrator Guide 13 4. Navigate to the following directory: <dvd_path>EM 5. Copy or map the EM directory to your local disk. 6. Navigate to the mapped or copied directory: <mapped/copied_location>EMClient 7. Run the Install_EM_Client_DataStage.cmd file, and follow the installation instructions provided. You have installed the Control-M for IBM InfoSphere DataStage client on the Control-M Configuration Manager. In addition, the IBM InfoSphere DataStage form is imported on the Control-M/EM client. To use the Control-M for IBM InfoSphere DataStage utilities in the Control-M Configuration Manager, make sure that the ctmgetcm utility has run in Control-M/Server. For more information, see the Control-M Administrator Guide. 8. From the Control-M Configuration Manager, restart the Control-M/EM GUI server. Enabling Find and Update support on Control-M/EM server The following procedure describes how to enable Control-M for IBM InfoSphere DataStage Find and Update support. Before You Begin Make sure that you have met the following requirements:  You have successfully completed Installing the Control-M for IBM InfoSphere DataStage client plug-in (on page 12).  The Control-M for IBM InfoSphere DataStage DRDSG.8.0.00 DVD is mounted or accessible through your network.  The Control-M/EM GUI server is shut down.  The Control-M/EM client applications are closed.  To enable Find and Update support: 1. Do one of the following: • If you download the Control-M for IBM InfoSphere DataStage 8.0.00 zip file from the BMC EPD site for a Windows installation, you need to create the EM directory content that is required to enable find and update support on the Control-M/EM server, do the following: a. Extract the files from the downloaded zip file. b. Double-click the EM.exe self-extractor. • If you download the Control-M for IBM InfoSphere DataStage 8.0.00 from the DVD, continue with the next step. 2. From the installation DVD, copy the DATASTAGE_appl.xml file located in the <DVD>EMApplFields directory to one of the following Control-M/EM directories: • Windows: <Control-M/EM home directory>etcapplfields • UNIX: <Control-M/EM home directory>/etc/applfields/
  • 14. Control-M for IBM InfoSphere DataStage Administrator Guide 14 3. From the Control-M Configuration Manager, restart the Control-M/EM GUI server. After you have finished installing Control-M for IBM InfoSphere DataStage, you need to create an account in the Control-M Configuration Manager, as described in CCM administration. After you have created an account you can define a Control-M for IBM InfoSphere DataStage job, as described in Control-M for IBM InfoSphere DataStage job definition. Installing the Control-M Self Service plug-in This procedure describes how to install the Control-M for IBM InfoSphere DataStage plug-in on Control-M Self Service server.  To install the Control-M Self Service plug-in: 1. Do one of the following: • If you download the Control-M for IBM InfoSphere DataStage 8.0.00 zip file from the BMC EPD site for a Windows installation, you need to create the EM directory content that is required to enable find and update support on the Control-M/EM server, do the following: a. Extract the files from the downloaded zip file. b. Double-click the EM.exe self-extractor. • If you download the Control-M for IBM InfoSphere DataStage 8.0.00 from the DVD, continue with the next step. 2. From the installation DVD, copy the the content of the <DVD>EMSelfService directory to one of the following directories: • Windows: <Control-M/EM home directory>etc • UNIX: <Control-M/EM home directory>/etc/ Control-M for IBM InfoSphere DataStage Uninstall The following procedures describe how to uninstall Control-M for IBM InfoSphere DataStage from UNIX and Microsoft Windows:  Uninstalling Control-M for IBM InfoSphere DataStage from UNIX (on page 15)  Uninstalling Control-M for IBM InfoSphere DataStage from Windows (on page 15)  Performing an automatic uninstall from Windows (on page 16)
  • 15. Control-M for IBM InfoSphere DataStage Administrator Guide 15 Uninstalling Control-M for IBM InfoSphere DataStage from UNIX This procedure describes how to uninstall Control-M for IBM InfoSphere DataStage from UNIX. Before You Begin Make sure that all jobs have ended.  To uninstall from UNIX: 1. From a Control-M/Agent computer, log in as a Control-M/Agent user, and type the following command to shut down Control-M/Agent: $CONTROLM/scripts/shut-ag -u <agentUser> -p all NOTE: If the Control-M/Agent was installed with user root, then log in as user root every time you start up or shut down the Control-M/Agent throughout this procedure. 2. If you are using an AIX operating system, you must remove unused libraries from memory by typing the following command: /usr/sbin/slibclean 3. Set your DISPLAY environment variable according to the computer name, as described in Setting environment variables in UNIX (on page 8). 4. Type one of the following commands: • Interactive: $HOME/BMCINSTALL/uninstall/DRDSG.8.0.00/uninstall.sh • Automatic: $HOME/BMCINSTALL/uninstall/DRDSG.8.0.00/uninstall.sh -silent Control-M for IBM InfoSphere DataStage has been successfully removed from your computer. 5. To restart Control-M/Agent, type the following command: $CONTROLM/scripts/start-ag -u <agentUser> -p all Uninstalling Control-M for IBM InfoSphere DataStage from Windows This procedure describes how to uninstall Control-M for IBM InfoSphere DataStage from Windows. Before You Begin Make sure that all jobs have ended.  To uninstall from Windows: 1. From the Start menu, select Settings > Control Panel. 2. Double-click Add/Remove Programs. 3. Select Control-M for IBM InfoSphere DataStage <Agent Name>, and click Add/Remove. 4. Click OK to continue. Control-M for IBM InfoSphere DataStage is successfully removed from your computer.
  • 16. Control-M for IBM InfoSphere DataStage Administrator Guide 16 Performing an automatic uninstall from Windows This procedure describes how to perform an automatic uninstall from Windows. Before You Begin Make sure that all jobs have ended.  To perform an automatic uninstall from Windows: 1. Log in to the computer using a user ID that has Administrator privileges. 2. Type the following command: <Agent Install Path>BMCINSTALLuninstallDRDSG.8.0.00Uninstall.exe -silent Control-M for IBM InfoSphere DataStage has been successfully removed from your computer.
  • 17. 17 3Chapter 3 Account management Before you can define a Control-M for IBM InfoSphere DataStage job in the Control-M/Desktop, you need to create an account in the Control-M Configuration Manager, which enables you to connect to the required IBM InfoSphere DataStage server. An account contains the connection parameters to a specified IBM InfoSphere DataStage server, such as host name, user name, and password. By adding an account to the Control-M Configuration Manager, you enable Control-M for IBM InfoSphere DataStage users to connect to the required IBM InfoSphere DataStage server with only the account name. As a result, users can run a job without having to provide authentication details every time they connect to the IBM InfoSphere DataStage server. The following procedures describe how to create, edit, delete, test, copy, and export an account in the Control-M Configuration Manager.  Creating an Account (on page 17)  Editing an account (on page 19)  Deleting an account (on page 19)  Testing an account (on page 20)  Copying an account (on page 20)  Exporting an account (on page 21) Creating an Account This procedure describes how to create an IBM InfoSphere DataStage account in the Control-M Configuration Manager, which enables you to define an IBM InfoSphere DataStage job in the Control-M/Desktop. Before you begin Make sure that you have set up the location of the IBM InfoSphere DataStage engine for Control-M for IBM InfoSphere DataStage. For more information, see Installing Control-M for IBM InfoSphere DataStage on Control-M/Agent on UNIX (on page 9) or Installing Control-M for IBM InfoSphere DataStage on Control-M/Agent on Windows (on page 10).  To create an account: 1. From Control-M Configuration Manager, right-click the CM (DATASTAGE) on the host that you want to manage. 2. Select Account Management. The Control-M for IBM InfoSphere DataStage Account Management dialog box appears.
  • 18. Control-M for IBM InfoSphere DataStage Administrator Guide 18 3. Click the Add icon. The Add Account dialog box appears. 4. In the Account Name field, enter the name of the account that you want to add. (The account name must begin with a letter and without any blank spaces or special characters). 5. Select one of the following options: • Local User: use only when Control-M for IBM InfoSphere DataStage is installed on an IBM InfoSphere DataStage engine. o Unix: IBM InfoSphere DataStage jobs run using the Control-M agent user account. o Windows: IBM InfoSphere DataStage jobs run under the user specified in the Log On tab of the Control-M/Agent Service Properties. • Server Login (non-secured): use to connect to any remote IBM InfoSphere DataStage engine. • Authentication File: use to connect to any remote IBM InfoSphere DataStage engine, using a local credentials file. For more information about the credentials file, see your IBM InfoSphere DataStage documentation. NOTE: The available fields are determined by the option that you select. 6. For each field, enter the required value, as described in Control-M for IBM InfoSphere DataStage account parameters (on page 18). 7. Click Next. The Add Account - Summary dialog box appears. 8. (Optional) Review the account details, and click Test. If the test was completed successfully, the account is validated and you can now define an IBM InfoSphere DataStage job, as described in the Control-M for IBM InfoSphere DataStage Job Editing Form Help in Defining a Control-M for IBM InfoSphere DataStage job (on page 23). If the test failed, review the error message(s), fix any problems as necessary, and test the account again. 9. Click Finish. The account is added to the Control-M for IBM InfoSphere DataStage Account Management dialog box. Control-M for IBM InfoSphere DataStage account parameters The following table lists the Set Connection Detail parameters to add an account. Field Description Server Name Defines the host name of the IBM InfoSphere DataStage engine Domain Name (optional) Defines the domain of the IBM InfoSphere DataStage engine User Name Defines the user name for the IBM InfoSphere DataStage engine
  • 19. Control-M for IBM InfoSphere DataStage Administrator Guide 19 Field Description Password Defines the password for the IBM InfoSphere DataStage engine Confirm Password Confirms the password for the IBM InfoSphere DataStage engine Authentication File Defines the full path, including the authentication file name of the local credentials file for the IBM InfoSphere DataStage engine Editing an account This procedure describes how to edit an account in the Control-M Configuration Manager. 1. From Control-M Configuration Manager, right-click the CM (DATASTAGE) on the host that you want to manage. 2. Select Account Management. The Control-M for IBM InfoSphere DataStage Account Management dialog box appears. 3. Select the account that you want to edit, and click the Edit icon. The Update <account> Account dialog box appears. 4. For each field, type the required value, as described in Control-M for IBM InfoSphere DataStage account parameters (on page 18). 5. (Optional) Review the account details, and click Test. If the test completed successfully, the account is validated and you can now define an IBM InfoSphere DataStage job, as described in the Control-M for IBM InfoSphere DataStage Job Editing Form Help, Defining a Control-M for IBM InfoSphere DataStage job (on page 23). If the test failed, review the error message(s), fix any problems as necessary, and test the account again. 6. Click OK. The account is updated in the Control-M for IBM InfoSphere DataStage Account Management dialog box. Deleting an account This procedure describes how to delete an account from the Control-M Configuration Manager. 1. From Control-M Configuration Manager, right-click the CM (DATASTAGE) on the host that you want to manage. 2. Select Account Management. The Control-M for IBM InfoSphere DataStage Account Management dialog box appears. 3. Select the account that you want to delete, and click the Delete icon. A confirmation message appears.
  • 20. Control-M for IBM InfoSphere DataStage Administrator Guide 20 4. Click Yes. The account is deleted. Testing an account This procedure describes how to test an account in the Control-M Configuration Manager, which enables you to validate the connection parameters. 1. From Control-M Configuration Manager, right-click the CM (DATASTAGE) on the host that you want to manage. 2. Select Account Management. The Control-M for IBM InfoSphere DataStage Account Management dialog box appears. 3. Select the account that you want to test, and click . If the test completed successfully, the account is validated and you can now define a IBM InfoSphere DataStage job, as described in Defining a Control-M for IBM InfoSphere DataStage job (on page 23). If the test failed, review the error message and test it again. Copying an account This procedure describes how to copy an account in the Control-M Configuration Manager, which enables you to create an additional account using the parameters of an existing account.  To copy an account: 1. From Control-M Configuration Manager, right-click the CM (DATASTAGE) on the host that you want to manage. 2. Select Account Management. The Control-M for IBM InfoSphere DataStage Account Management dialog box appears. 3. Select an account that you want to copy, and click . The Copy <account> Account dialog box appears. 4. In the Account Name field, type a name for the new account, change any required parameters, and then click OK. 5. (Optional) Click Test. If the test completed successfully, the account is validated and you can now define a IBM InfoSphere DataStage job, as described Defining a Control-M for IBM InfoSphere DataStage job (on page 23). If the test failed, review the error message and test it again. 6. Click OK.
  • 21. Control-M for IBM InfoSphere DataStage Administrator Guide 21 Exporting an account This procedure describes how to export an account from one Control-M/Agent to another Control-M/Agent, where Control-M for IBM InfoSphere DataStage is installed.  To export an account: 1. From Control-M Configuration Manager, right-click the CM (DATASTAGE) on the host that you want to manage. 2. Select Account Management. The Control-M for IBM InfoSphere DataStage Account Management dialog box appears. 3. Select an account that you want to export and click . The Account Management - Export Account Destination dialog box appears. 4. From the Control-M/Server name drop-down list, select the Control-M/Server that contains the Control-M/Agent, where you want to export the account. 5. From the Control-M/CM Host Name drop-down list, select the Control-M/Agent that contains the account on the CM you want to export. 6. Click OK. The Export Account Destination dialog box appears. 7. In the Account Name field, type a name for the exported account and change any required parameters, and then click OK. 8. (Optional) Click Test. If the test completed successfully, the account is validated and you can now define a IBM InfoSphere DataStage job, as described in the Control-M for IBM InfoSphere DataStage Job Editing Form Help Defining a Control-M for IBM InfoSphere DataStage job (on page 23). If the test failed, review the error message and test it again. 9. Click OK.
  • 22. 22 4Chapter 4 Job definition Control-M for IBM InfoSphere DataStage is a control module that connects to an IBM InfoSphere DataStage server and enables you to run IBM InfoSphere DataStage jobs, as described in Defining a Control-M for IBM InfoSphere DataStage job (on page 23). Control-M for IBM InfoSphere DataStage jobs are integrated with other Control-M jobs into a single scheduling environment. Control-M capabilities are available for Control-M for IBM InfoSphere DataStage, including advanced scheduling criteria, complex dependencies, quantitative and control resources, and AutoEdit variables. To access the IBM InfoSphere DataStage form, see Accessing the IBM InfoSphere DataStage form (on page 22). Job definition parameters in Control-M for IBM InfoSphere DataStage enable you to apply values for the AutoEdit variables, as described in the Control-M User Guide. For a list of Control-M for IBM InfoSphere DataStage parameters, see Control-M for IBM InfoSphere DataStage parameters (on page 24). Accessing the IBM InfoSphere DataStage form This procedure describes how to access the IBM InfoSphere DataStage form, which enables you to define a IBM InfoSphere DataStage job.  To access the IBM InfoSphere DataStage form: 1. Log in to Control-M/Desktop, as described in the Control-M User Guide. 2. From the Edit menu, select New > Job. 3. From the Job Type dropdown list, select IBM InfoSphere DataStage. 4. Click the IBM InfoSphere DataStage tab. The IBM InfoSphere DataStage form appears.
  • 23. Control-M for IBM InfoSphere DataStage Administrator Guide 23 Defining a Control-M for IBM InfoSphere DataStage job This procedure describes how to define a Control-M for IBM InfoSphere DataStage job, which enables you to run IBM InfoSphere DataStage jobs on an IBM InfoSphere DataStage server. Before You Begin Make sure that you have met the following requirements:  A configured IBM InfoSphere DataStage account, as described in Account management (on page 17).  Successful completion of Accessing the IBM InfoSphere DataStage form (on page 22).  To define an IBM InfoSphere DataStage job: 1. (Mandatory) In the Account field, do one of the following actions: • Enter the account name. • Click Load, select the account that you want, and click OK. 2. (Mandatory) In the Project field, do one of the following actions: • Enter the project name. • Click Load, select the project that you want, and click OK. 3. (Mandatory) In the Job Name field, do one of the following actions: • Enter the job name. • Click Load, select the job that you want, and click OK. 4. (Optional) In the Job Invocation ID field, enter the invocation ID for a multiple-instance job. 5. Do one of the following options: • In the Parameter File field, enter the name of the parameter file that you want to use, or click Load, and select a file from the list. When clicking Load, a list of files in the <Agent dir>cmDATASTAGEparameters directory appears. Make sure you have copied the parameters file to this location, and that the Agent user has permissions to use this file. • Click Load Parameters, and then click in the Value column to edit the value of a parameter. 6. In the Run options area, select any of the following options: • Reset job before run: resets a job before it runs. • Run in restart mode: runs a sequential job in restart mode. 7. Click Job Output to set the IBM InfoSphere DataStage log entry types that are written to the job Sysout. 8. Click Set limits to limit the number of rows and warnings. If you enter "0", the number of rows and warnings is unlimited. For more information about defining a job in the job editing form, see the Control-M User Guide.
  • 24. Control-M for IBM InfoSphere DataStage Administrator Guide 24 Monitoring a job While a Control-M for IBM InfoSphere DataStage job is running, you can monitor the progress of the job. 1. In the Control-M/EM GUI, locate the Control-M for IBM InfoSphere DataStage job that you want to monitor. 2. Right-click the job, and select Sysout. 3. If more than one occurrence of the job appears in the list, select the sysout that you want to view. The Sysout window appears. If the job is still running on the IBM InfoSphere DataStage engine, an intermediate summary of the job appears. Control-M for IBM InfoSphere DataStage parameters Job definition parameters in Control-M for IBM InfoSphere DataStage enable you to apply values for the AutoEdit variables, as described in the Control-M User Guide. The following table describes the parameters for Control-M for IBM InfoSphere DataStage. Parameter Description Account (on page 26) Defines the Control-M for IBM InfoSphere DataStage account. Project (on page 29) Defines the Control-M for IBM InfoSphere DataStage project name. Job Name (on page 27) Defines the Control-M for IBM InfoSphere DataStage job name. Job Invocation ID (on page 27) Defines the Control-M for IBM InfoSphere DataStage job invocation ID. Parameter File (on page 28) Defines the Control-M for IBM InfoSphere DataStage parameter file. Parameter Name (on page 28) Defines the name of a specific parameter. Parameter Value (on page 28) Defines the value of a specific parameter. Run in Restart Mode (on page 30) Runs the Control-M for IBM InfoSphere DataStage job in Restart mode. Reset Job Before Run (on page 30) Resets the Control-M for IBM InfoSphere DataStage job before the job runs. Abort Job After <value> Warnings (on page 25) Sets the maximum number of warnings.
  • 25. Control-M for IBM InfoSphere DataStage Administrator Guide 25 Parameter Description Stop Stages After <value> Rows (on page 31) Sets the maximum number of rows. Info (on page 27) Writes Info log entries to Control-M for IBM InfoSphere DataStage job Sysout. Warning (on page 31) Writes Warning log entries to Control-M for IBM InfoSphere DataStage job Sysout. Fatal (on page 26) Writes Fatal log entries to Control-M for IBM InfoSphere DataStage job Sysout. Reject (on page 29) Writes Reject log entries to Control-M for IBM InfoSphere DataStage job Sysout. Started (on page 30) Writes Started log entries to Control-M for IBM InfoSphere DataStage job Sysout. Reset (on page 29) Writes Reset log entries to Control-M for IBM InfoSphere DataStage job Sysout. Batch (on page 26) Writes Batch log entries to Control-M for IBM InfoSphere DataStage job Sysout. Abort Job After <value> Warnings Sets the maximum number of warnings. Usage Optional Valid Values 0-9999999 Default Value 0 Case Sensitive No Variable Name %%DataStage-MAX_WARNINGS
  • 26. Control-M for IBM InfoSphere DataStage Administrator Guide 26 Account Defines the Control-M for IBM InfoSphere DataStage account. Usage Mandatory Length 1 - 30 characters Case Sensitive Yes - only capital letters Variable Name %%DataStage-ACCOUNT Batch Writes Batch log entries to Control-M for IBM InfoSphere DataStage job Sysout. Usage Optional Valid Values Yes, No Default Value No Case Sensitive Yes Variable Name %%DataStage-OUTPUT_BATCH Fatal Writes Fatal log entries to Control-M for IBM InfoSphere DataStage job Sysout. Usage Optional Valid Values Yes, No Default Value Yes Case Sensitive Yes Variable Name %%DataStage-OUTPUT_FATAL
  • 27. Control-M for IBM InfoSphere DataStage Administrator Guide 27 Info Writes Info log entries to Control-M for IBM InfoSphere DataStage job Sysout. Usage Optional Valid Values Yes, No Default Value No Case Sensitive Yes Variable Name %%DataStage-OUTPUT_INFO Job Invocation ID Defines the Control-M for IBM InfoSphere DataStage job invocation ID. Usage Optional Case Sensitive Yes Variable Name %%DataStage-JOB_INVOCATION_ID Job Name Defines the Control-M for IBM InfoSphere DataStage job name. Usage Mandatory Case Sensitive Yes Variable Name %%DataStage-JOB_NAME
  • 28. Control-M for IBM InfoSphere DataStage Administrator Guide 28 Parameter File Defines the Control-M for IBM InfoSphere DataStage parameter file. Usage Optional Case Sensitive Yes Variable Name %%DataStage-PARAMS_FILE Parameter Name Defines the name of a specific parameter. Usage Optional Case Sensitive Yes Variable Name %%DataStage-PARAMS-Pxxx-PRM_NAME xxx determines the parameter number between 001-999 Parameter Value Defines the value of a specific parameter. Usage Optional Case Sensitive Yes Variable Name %%DataStage-PARAMS-Pxxx-PRM_VALUE xxx determines the parameter number between 001-999
  • 29. Control-M for IBM InfoSphere DataStage Administrator Guide 29 Project Defines the Control-M for IBM InfoSphere DataStage project name. Usage Mandatory Case Sensitive Yes Variable Name %%DataStage-PROJECT Reject Writes Reject log entries to Control-M for IBM InfoSphere DataStage job Sysout. Usage Optional Valid Values Yes, No Default Value No Case Sensitive Yes Variable Name %%DataStage-OUTPUT_REJECT Reset Writes Reset log entries to Control-M for IBM InfoSphere DataStage job Sysout. Usage Optional Valid Values Yes, No Default Value No Case Sensitive Yes Variable Name %%DataStage-OUTPUT_RESET
  • 30. Control-M for IBM InfoSphere DataStage Administrator Guide 30 Reset Job Before Run Resets the Control-M for IBM InfoSphere DataStage job before the job runs. Usage Optional Valid Values Yes, No Default Value Yes Case Sensitive Yes Variable Name %%DataStage-RESET_JOB Run in Restart Mode Runs the Control-M for IBM InfoSphere DataStage job in Restart mode. Usage Optional Valid Values Yes, No Default Value No Case Sensitive Yes Variable Name %%DataStage-RESTART_SEQUENCE Started Writes Started log entries to Control-M for IBM InfoSphere DataStage job Sysout. Usage Optional Valid Values Yes, No Default Value No Case Sensitive Yes Variable Name %%DataStage-OUTPUT_STARTED
  • 31. Control-M for IBM InfoSphere DataStage Administrator Guide 31 Stop Stages After <value> Rows Sets the maximum number of rows. Usage Optional Valid Values 0-9999999 Variable Name %%DataStage-MAX_ROWS Warning Writes Warning log entries to Control-M for IBM InfoSphere DataStage job Sysout. Usage Optional Valid Values Yes, No Default Value No Case Sensitive Yes Variable Name %%DataStage-OUTPUT_WARNING