C 1929650

IBM InfoSphere Information Server
Version 8 Release 5
Guide to Migrating to IBM InfoSphere Information Server, Version 8.5
SC19-2965-00
IBM InfoSphere Information Server

Version 8 Release 5
SC19-2965-00
Note Before using this information and the product that it supports, read the information in Notices and trademarks on page 53.
Copyright IBM Corporation 2006, 2010. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Part 1. Overview of migration . . . . 1
Chapter 1. Migrating to IBM InfoSphere Information Server, Version 8.5 . . . . . 3
Migration strategies . . . . . . . . . . . . 3 Job migration in legacy operational mode . . . QualityStage job migration in expanded form . . Rule set migration . . . . . . . . . . . Match specification migration . . . . . . . Installing the WebSphere QualityStage migration utility . . . . . . . . . . . . . . . Running the QualityStage migration utility . . . Importing the migrated files into the Version 8.5 Designer client . . . . . . . . . . . Preparing migrated QualityStage jobs for operation . . . . . . . . . . . . . Migrating real-time QualityStage jobs from Release 7 to Version 8.5 . . . . . . . . . . . . Replace InfoSphere QualityStage 7 data quality stages . . . . . . . . . . . . . . . . . . . 25 26 26 26
. 27 . 28 . 29 . 30 . 32 . 33
Part 2. Version 7.5.3 and earlier migrations . . . . . . . . . . . . . 5

Chapter 2. Migrations from Version 7.5.3 and earlier. . . . . . . . . . . . . . 7 Chapter 3. Migration from DataStage 7.5.3 and earlier versions . . . . . . . 9
Exporting projects . . . . . . . . . . . . 9 Exporting projects from the DataStage Manager client . . . . . . . . . . . . . . . 10 Exporting projects from the command line . . . 10 Saving DataStage settings files . . . . . . . . 11 Saving settings files (UNIX and Linux) . . . . 11 Saving the DSParams file (Windows) . . . . . 12 Move job dependency objects . . . . . . . . 12 Migrating hashed files . . . . . . . . . . 13 Remove previous versions of DataStage . . . . . 13 Removing a DataStage server (Windows) . . . 13 Removing a DataStage server (Linux, UNIX) . . 14 Removing DataStage clients . . . . . . . . 14 Importing DataStage projects . . . . . . . . 15 Restoring contents of DataStage 7.5.3 or earlier settings files . . . . . . . . . . . . . . 15 Restoring DataStage job dependencies . . . . . 15 Restoring hashed files . . . . . . . . . . 16 Recompiling jobs . . . . . . . . . . . . 17 Updating jobs that use the QualityStage 7.5 plug-in 18 Switching between different versions of clients . . 18 Multiple server method (Linux and UNIX only) . . 19 Installing Version 8.5 in addition to existing DataStage servers . . . . . . . . . . . 20 Installing IBM InfoSphere DataStage, Version 8.5 clients in addition to existing clients . . . . . 21 Starting and stopping multiple DataStage servers 21 Connecting to multiple DataStage servers . . . 22
Chapter 5. Migration from IBM WebSphere RTI 7.5, 7.5.1, and 7.5.2 installations . . . . . . . . . . . . 35
Migrating RTIX files to Version 8.5 . . . . . . 35
Part 3. Client-only upgrades . . . . 37

Chapter 6. Upgrading a client tier-only installation to Version 8.5. . . . . . . 39
Part 4. Appendixes. . . . . . . . . 43
Product accessibility . . . . . . . . 45
Accessing product documentation. . . 47 Reading command-line syntax . . . . 49 Links to non-IBM Web sites. . . . . . 51 Notices and trademarks . . . . . . . 53 Contacting IBM . . . . . . . . . . . 57 Index . . . . . . . . . . . . . . . 59
Chapter 4. Migration from QualityStage 7.5 and earlier releases . . . . . . . 25
Copyright IBM Corp. 2006, 2010
iii
iv
Part 1. Overview of migration
Chapter 1. Migrating to IBM InfoSphere Information Server, Version 8.5

Migration enables you to move existing source installations to new IBM InfoSphere Information Server, Version 8.5, installations. The current version and the translated versions of this information are on the Web at http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r5/topic/ com.ibm.swg.im.iis.productization.iisinfsv.migrate.doc/topics/migr_container.html. The version of your existing installation determines how you migrate to a new IBM InfoSphere Information Server, Version 8.5 installation.
Migration strategies
You will use different migration strategies and methods to migrate to Version 8.5 from existing installations. Plan your strategy and choose your migration method based on the version of your existing installation. Successful migration requires that you understand your IBM InfoSphere Information Server installation topology on the source computers and your InfoSphere Information Server installation topology on the target computers. You must use one of the following methods to migrate your source installation to a new Version 8.5 installation:
Table 1. Supported migrations to Version 8.5 Existing installation (source) Information Server, Version 8.0.1 and later Migration method If you want to do this type of migration, see www.ibm.com/support/ docview.wss?uid=swg21445403. Export projects and save the settings files from the existing installation. Then import the projects and move the settings files to the Version 8.5 installation. See Chapter 3, Migration from DataStage 7.5.3 and earlier versions, on page 9. Use the QualityStage migration utility. See Chapter 4, Migration from QualityStage 7.5 and earlier releases, on page 25. Use the WebSphere RTI Export Wizard. See Chapter 5, Migration from IBM WebSphere RTI 7.5, 7.5.1, and 7.5.2 installations, on page 35.
DataStage, releases from 7.5.3 and earlier
QualityStage, release 7.5 and earlier
IBM WebSphere RTI 7.5, 7.5.2, and 7.5.1
Note: You do not migrate computers that only have the client tier installed on them. Computers that only have client tier software installed do not contain installation information or data that requires migration. To upgrade these computers to Version 8.5, you run the InfoSphere Information Server suite installation program.
Part 2. Version 7.5.3 and earlier migrations
Chapter 2. Migrations from Version 7.5.3 and earlier

You can migrate from previous versions of DataStage, QualityStage, and WebSphere RTI to a new IBM InfoSphere Information Server, Version 8.5 installation. Export projects and jobs from release 7.5.3 and earlier versions of DataStage and QualityStage and then import the projects and jobs to an InfoSphere Information Server, Version 8.5 installation. You can also migrate from IBM WebSphere RTI 7.5, 7.5.1, and 7.5.2 to IBM InfoSphere Information Services Director, Version 8.5 and subsequent releases. DataStage Version 6 is the earliest release that is supported for migration to Version 8.5. Note: This export and import migration method for release 7.5.3 and earlier versions of DataStage, QualityStage, and WebSphere RTI does not use the ismigration tool. The DataStage Version Control component is not supported by InfoSphere Information Server, Version 8.5. Instead, use Information Server Manager to integrate a supported source control system.
Chapter 3. Migration from DataStage 7.5.3 and earlier versions

Migration involves exporting DataStage projects and saving the settings files from the existing installation, and then importing the projects and moving the settings files to the Version 8.5 installation. This migrate method applies to the development environment where the design-time information resides and moves all of your migrated projects to IBM InfoSphere Information Server, Version 8.5. Complete the following activities to migrate your source DataStage 7.5.3 and earlier environment to your target Version 8.5 development environment: 1. Export projects. See Exporting projects. 2. Save the DataStage settings files. See Saving DataStage settings files on page 11. 3. Installing InfoSphere Information Server, Version 8.5, including IBM InfoSphere DataStage. See "Installing IBM InfoSphere Information Server software" in the IBM InfoSphere Information Server Planning, Installation, and Configuration Guide. 4. Integrating the contents of your saved settings and configuration files. a. Restore the settings files. See Restoring contents of DataStage 7.5.3 or earlier settings files on page 15. b. Move job dependency objects such as flat files, libraries, schema files, and hashed files that your project uses. See Move job dependency objects on page 12. 5. Import projects. See Importing DataStage projects on page 15. 6. Recompile jobs in your projects. See Recompiling jobs on page 17. Note: Use the migration from DataStage 7.5.3 and earlier method to migrate to different computers for your Version 8.5 installation, or to the same computers by using an ITAG installation. This migration method information applies to migration to different target computers or the same computers for source and target installations. ITAG installations exist when you install more than one instance of DataStage or InfoSphere Information Server on the same set of Linux or UNIX computers.
Exporting projects
You export your DataStage projects from your source installation before migrating the projects to your Version 8.5 target installation.
Before you begin

Ensure that nobody is using DataStage and that all clients are disconnected.
About this task

You can export projects by using one of the following methods: v Export from the DataStage Manager client. v Export from the command line of a DataStage client computer.
Exporting projects from the DataStage Manager client

You can use the DataStage Manager client to export projects from your development environment.
About this task

Note: The current version of your installation determines the name of the DataStage Manager client. Your installation might refer to the client as the DataStage client.
Procedure
1. Open the DataStage Manager client, and attach to project that you want to export. 2. Ensure View Host View is selected. 3. Select Export DataStage Components. 4. In the Export window, specify details about the project that you want to export: a. In the Export to file field, type or browse for the path name of the file in which to store the project. By default, export files have the suffix .dsx. b. In the Components tab, select the Whole Project option. 5. Click OK. The project is exported to the file that you specified. 6. In the left pane of the DataStage Manager window, select the next project and repeat the export process from step 3, specifying a different name for the export file.
Exporting projects from the command line

You can use the command line on the client computer to export your projects from your development environment. You can create a script that runs these commands and exports all of your projects in a single operation.
About this task

Export your projects from your source installation before you import the projects to your target installation.
Procedure
1. Open a command line editor and go to the DataStage client directory (the default path is C:\Ascential\Program Files\Ascential\DataStageversion). 2. Enter the command: dscmdexport /H=hostname /U=username /P=password project_name export_file_path [/V] The arguments are as follows: v hostname is the name of the DataStage server computer where the project is located. v username is your user name on the server computer. v password is the password for that user name. v project_name is the name of the project that you are exporting. v export_file_path is the path name of the destination file. By convention, export files have the suffix .dsx. v /V is optional. Including /V turns the verbose option on so that you can follow the progress of the export procedure.
10
Example
For example, the following command exports the project named monthlyaudit that is located on the DataStage server named R101 and writes the project to a file named monthlyaudit.dsx. The target file is located in a directory named migrated_projects on the client computer.
dscmdexport /H=R101 /U=BillG /P=paddock monthlyaudit C:\migrated_projects\monthlyaudit.dsx
What to do next
You can enter a command for each project that you want to export, or you can create a script that contains commands for all of the projects on your DataStage server computer.
Saving DataStage settings files

Back up your settings files on your existing DataStage server.
About this task

After you install IBM InfoSphere Information Server, Version 8.5, you can compare each of your saved settings files with the equivalent new file. You can then integrate the two files. You must not replace the new files with the files that you saved from your existing installation, because you will overwrite new settings. The files that you copy depend on whether your DataStage server is on a Windows computer, or a UNIX or Linux computer.
Saving settings files (UNIX and Linux)

If you are migrating an existing DataStage server on a UNIX or Linux computer, you must save copies of certain settings files.
Before you begin

The environment variable $DSHOME identifies the engine directory of your DataStage installation.
About this task

By default the engine directory is /user_home/Ascential/DataStage/DSEngine, where user_home is the home directory of the DataStage administrator who originally installed DataStage (by default, dsadm). Each project is in its own directory in the /user_home/Ascential/DataStage/Projects directory.
Procedure
1. Copy the $DSHOME/dsenv file to a location outside of the DataStage file structure. 2. To keep a record of the existing configuration and the configuration of your ODBC drivers, copy the following files to a location outside of the DataStage file structure: v $DSHOME/.odbc.ini v $DSHOME/uvodbc.config v The uvodbc.config file located in each project directory
11
3. Copy the DSParams file from each project directory to a location outside of the DataStage file structure. 4. Also, copy the DSParams file from the Template project. $DSHOME/../Template/ DSParams
Saving the DSParams file (Windows)

If you are migrating an existing DataStage server on a Windows computer, save a copy of the DSParams file from each project directory.
Before you begin

Each project has its own directory located, by default, in the directory C:\Ascential\DataStage\Projects.
About this task

Save the DSParams file so that you can move it to your target installation.
Procedure
1. Copy the DSParams file from each project directory to a safe location. 2. Also, copy the DSParams file from the Template project. For example, save the C:\Ascential\DataStage\Template\DSParams file. 3. Copy the $DSHOME/uvodbc.config in the engine directory. 4. The uvodbc.config file located in each project directory.
Move job dependency objects

The jobs in your projects might depend on objects outside of DataStage. You must move these objects to the Version 8.5 target installation. You need to move job dependency objects in the following situations: v If the files are in the DataStage server or client directory structures, or v If you are installing InfoSphere DataStage on a different computer. Note: If you have flat files, hashed files, or other dependencies that are located in your DataStage directory structure, or if you are migrating to a different computer, then you must move these files yourself. These files are not saved as part of the export procedure. The DataStage export procedure exports DataStage objects, such as job designs, table definitions and custom routines. If the jobs in your projects have other dependencies, then you might need to move these dependencies. Dependencies include flat files, files containing schemas used by parallel jobs, and libraries that are called by parallel job custom routines. It does not include parallel job data sets or file sets. If you are using data sets or file sets to permanently store data, then you must design a job to write the data to a flat file or other data target. You can move flat files, libraries, and schema files by using normal operating system commands. You might need to modify job designs to identify the new locations of these files. If there are server jobs in your projects that use hashed files, then you must use a dedicated procedure to move the hashed files.
12
Migrating hashed files

If your DataStage project contains server jobs that use hashed files, then you need to move the hashed files to a new location as part of the migration procedure.
Before you begin

Before moving the files, stop the DataStage server to ensure that dynamic hashed files are copied correctly. If you previously added indices to the hashed files, remove the indices.
About this task

The hashed files from your source installation need to be saved and moved to the target installation.
Procedure
1. Locate the hashed files in your directory structure: v Each static hashed file is represented by two operating system files. For example, a static hashed file named price_lookup is contained in the two files named price_lookup and d_price_lookup. v Each dynamic hashed file is represented by a directory with the same name as the hashed file and a file named D_hashed_file_name. For example, a dynamic hashed file named code_lookup is represented by the directory named code_lookup and the file named D_code_lookup. 2. Copy the files or directories that represent each of your hashed files to a safe location outside of the DataStage directory structure.
What to do next
You can restore these files after you install and configure InfoSphere DataStage.
Remove previous versions of DataStage

Removing DataStage completely removes your current version of DataStage from server and client computers. Ensure that your DataStage server computer is backed up before you remove DataStage, and that no one is using DataStage. There are separate procedures for removing DataStage clients and removing DataStage servers.
Removing a DataStage server (Windows)

You use Windows Add or Remove Programs to remove an existing DataStage server from a Windows computer.
Before you begin

Ensure that DataStage is not running and ensure that no clients are connected to the server.
About this task

Removes the DataStage server.
13
Procedure
1. 2. 3. 4. Open the control panel. In the control panel, select Add or Remove Programs. In the list of installed programs, select DataStage server. Click Change/Remove.
Removing a DataStage server (Linux, UNIX)

You run the uninstallation program to remove an existing DataStage server from a UNIX or Linux computer.
Before you begin

Mount the original installation CD, or copy the CD contents to your computer.
About this task

Removes the DataStage server.
Procedure
1. Log in as the root user. 2. Change directory to the top level directory of the CD, or the directory to which you copied the CD contents. 3. Type the relevant uninstallation command:
Operating System Solaris AIX
Command uninstll.sh uninstll.sh UNINSTLL.SH;1 uninstll.sh
HP-UX LINUX
The uninstallation program guides you through the procedure for removing the DataStage server.
Removing DataStage clients

You use Windows Add or Remove Programs to remove existing DataStage clients from a Windows computer.
Before you begin

Ensure that nobody is using DataStage and that no clients are connected to the DataStage server.
About this task

Removes DataStage clients.
Procedure
1. Open the Windows control panel. 2. In the control panel, select Add or Remove Programs. 3. In the list of installed programs, select DataStage Clients. 4. Click Change/Remove.
14
Importing DataStage projects

Import the projects to your Version 8.5 installation.
About this task

Import projects from earlier versions of DataStage to your Version 8.5 development environment.
Procedure
1. Move the .dsx file or files that you created to the computer where the IBM InfoSphere DataStage and QualityStage, Version 8.5 clients are installed. 2. Open the Administrator client and create a project or projects to contain the objects from your exported projects: a. On the Projects page, click Add. b. In the Add Project window, type the name of the project that you want to create and specify a path name for it. You can use the names of the original projects if required. c. Click OK to create the project. d. Repeat these steps for each project that you want to create. You might want to create a project for each of the projects that you exported and give it the same name as the original project. Open the Designer client and attach to the target project. Select Import DataStage Components. Specify the name of the .dsx file that you want to import, and click OK. After you unit test the migrated components in your Version 8.5 development environment, you must export the DataStage components from your Version 8.5 environment and then import them to your Version 8.5 production environment.
3. 4. 5. 6.
Restoring contents of DataStage 7.5.3 or earlier settings files

If you previously customized any of your DataStage 7.5 or earlier settings files, you might need to restore these customizations.
About this task

Do not copy your saved versions over the new ones to restore the settings files. You must merge the contents of your saved files with the new files. You must only add or edit settings in the new files. Do not delete settings. Use this procedure with any of the settings files that you saved earlier.
Procedure
1. Open the saved version of the settings file in a text editor. 2. Open the new version of the same file in a text editor. 3. Compare the contents of the saved file with the new file. 4. Add any required entries to the new file. 5. Save the new file and close the text editor.
Restoring DataStage job dependencies

You must restore any DataStage job dependencies that you saved.
15
About this task

After you migrate to Version 8.5, restore job dependency files to your new installation.
Procedure
1. For each file, find the location for the file in the new IBM InfoSphere Information Server directory structure. For example, if the file that you want to restore was in the project directory in your previous DataStage installation, find the project directory to which you imported the project contents. 2. Use operating system commands to copy the saved file to the required location. 3. Ensure that the jobs that reference these files can locate them. If the file is referred to directly, you must edit the path name in the job design. If the file is referred to by a job parameter, you might need to edit the default value of the parameter to reference the new location for the file.
Restoring hashed files

You need to restore the hashed files that you saved.
About this task

To restore hashed files, use IBM InfoSphere DataStage to create empty hashed files for each of the files that you want to restore. You then replace the empty files with the saved files. To restore hashed files, follow one of the two procedures.
Procedure
1. For jobs in your migrated project that create the hashed files, open the InfoSphere DataStage and QualityStage Director client, and attach to the migrated project that uses the hashed files. 2. Run or validate the job that creates the hashed files. 3. Close all InfoSphere DataStage clients and stop the DataStage services. 4. Locate the newly created files in your directory structure and copy the saved hashed files over the top of them. 5. Restart the DataStage services.
What to do next
Your hashed files are now available for use.
Designing a job to create new hashed files

About this task
To design a job to create the new hashed files.
Procedure
1. Open the Designer client, and attach to the migrated project that uses the hashed files. 2. Create a new server job. 3. For each hashed file that you need to restore, add a Sequential File stage linked to a Hashed File stage.
16
4. In the Sequential File stage, point to an empty text file and define one column in the Outputs page Columns tab. 5. In the Hashed File stage, specify the name of the hashed file that you are restoring, then select the Create File option and specify the file type of the hashed file that you are restoring. 6. When you have added stages for all the hashed files that you want to restore, compile and then validate or run the job to create the empty hashed files. 7. Close all InfoSphere DataStage clients and stop the DataStage services 8. Locate the newly-created files in your directory structure and copy your saved hash files over the top of them. 9. Restart the DataStage services.
What to do next
Your hashed files are now available for use.
Recompiling jobs
You must recompile the jobs and routines in the migrated projects to create new executable jobs.
About this task

You can start the wizard from the Tools menu of the Designer client. Select Tools Multiple Job Compile . You can also select multiple items in the repository tree or Advanced Find window and use the shortcut menu to start the compiler wizard.
Procedure
1. If you started the wizard from the Tools menu, specify the criteria for selecting jobs to compile. Choose one or more of: v v v v v v Server Parallel Mainframe Sequence Custom server routines Custom parallel stage types
You can also specify that only currently uncompiled jobs will be compiled, and that you want to manually select the items to compile. 2. Click Next>. If you chose the Show manual selection page option, the Job Selection Override screen appears. Choose jobs in the left pane and add them to the right pane by using the Add buttons or remove them from the right pane by using the Remove buttons. Clicking Add while you have a folder selected selects all the items in that folder and moves them to the right pane. All the jobs in the right pane will be compiled. 3. Click Next>. If you are compiling parallel or mainframe jobs, the Compiler Options screen appears, allowing you to specify the following: v Force compile (for parallel jobs). v An upload profile for mainframe jobs you are generating code for. 4. Click Next>. The Compile Process screen appears, displaying the names of the selected items and their current compile status.
17
5. Click Start Compile to start the compilation. As the compilation proceeds, the status changes from Queued to Compiling to Compiled OK or Failed and details about each job are displayed in the compilation output window as it compiles. Click the Cancel button to stop the compilation, although you can only cancel between compilations so the Designer client might take some time to respond. 6. Click Finish. If the Show compile report checkbox was selected, the job compilation report screen appears, displaying the report generated by the compilation.
Updating jobs that use the QualityStage 7.5 plug-in

If you have existing DataStage jobs that use the QualityStage plug-in stage to connect to QualityStage 7.5, and you want to continue running those jobs, then you must rewrite those jobs to use the parallel canvas and the Version 8.5 stages.
About this task

You must rewrite the jobs that use the QualityStage 7.5 plug-ins. After you import the jobs to Version 8.5, rewrite the jobs to use the parallel canvas and the Version 8.5 stages.
Switching between different versions of clients

You can install different versions of DataStage clients on a single Windows computer and switch between them by using the Multi-client Manager.
Before you begin

The Multi-client Manager is installed on the Version 8.5 client tier. Note: The Multi-client Manager is not supported on DataStage releases earlier than 7.0. For DataStage releases earlier than 7.0, install each client version on a separate computer.
About this task

When your organization is using different versions of DataStage, it is useful to have different client versions on your Windows computer. You can then switch between the clients according to which DataStage server you want to connect to. For example, if you are evaluating IBM InfoSphere DataStage, Version 8.5 on one of your installations, while still running WebSphere DataStage, Version 7.5.3 on another installation, you can have the clients for both releases on a client tier computer, and switch between the clients as necessary. You can install multiple DataStage clients by running the client installer (versions earlier than WebSphere DataStage 8.0), or running the suite installer and selecting only the client tier (Version 8.0.1 and later). You must install the Version 8.5 client after you install any earlier client versions, so that the Version 8.5 Multi-Client Manager is the latest version installed.
Procedure
1. Start the Multi-client Manager by double-clicking the desktop shortcut.
18
2. In the Current installation field, check whether the currently selected version is the version that you want. v If the correct version is selected, you need take no further action. v If the correct version is not selected, select the correct client in the Known installations list and click Select. 3. Click Close to close the Multi-client Manager.
Multiple server method (Linux and UNIX only)

If your DataStage server is on a Linux or UNIX computer, you can keep that instance and install IBM InfoSphere Information Server, Version 8.5. You can also install multiple IBM InfoSphere DataStage engine tiers. Each engine tier must be registered to a different instance of the IBM InfoSphere Information Server services tier. Note: There is a change of terminology between DataStage 7 and InfoSphere DataStage, Version 8.0.1 and later. In earlier versions the engine component was identified as the DataStage server, for release 8.0.1 and later, the engine component is identified as the engine tier. If you maintain different releases of DataStage server, or multiple instances of the same server, you can keep all of those instances. You can also upgrade each of these servers to InfoSphere DataStage, Version 8.5 and keep their existing identity information. Each instance of a DataStage server is identified by a tag ID (an ITAG) and allocated a different port. You also specify a different home directory for each server. Each DataStage server has a different set of projects that you access through that server. You connect to different servers by specifying the port number in addition to the UNIX server ID. The existing DataStage server instance retains the default port number, 31538, and uses the default ITAG, ADE. If you already have multiple server instances, then you already have servers that use different ports and ITAGs. Each version of DataStage requires clients of the same version. You must use the Multi-Client Manager program to switch between different client versions on your Windows client computers. You can use the multi-server facility to install multiple instances of the InfoSphere DataStage, Version 8.5 engine tier on the same computer. When multiple instances of the engine tier are installed on the same computer, each engine tier requires a unique profile for IBM WebSphere Application Server. The following table shows a scenario of a multi-server installation, and illustrates the use of port numbers and ITAGs.
Table 2. Scenario 1: InfoSphere DataStage, Version 8.5 server installed on the same computer as an existing DataStage 7.5.1 server Engine tier instance WebSphere DataStage, release 7.5.1 server Server details v Itag ADE v Port 31538 v /disk1/Ascential/DataStage
19
Table 2. Scenario 1: InfoSphere DataStage, Version 8.5 server installed on the same computer as an existing DataStage 7.5.1 server (continued) Engine tier instance InfoSphere DataStage, Version 8.5 server Server details v Itag 123 v Port 31540 v /opt/IBM/InformationServer/Server
The following table shows a scenario of a multi-server installation with three servers, and illustrates the use of port numbers and ITAGs.
Table 3. Scenario 2: InfoSphere DataStage, Version 8.5 server installed on the same computer as two existing DataStage 7.5.1 servers Engine tier instance WebSphere DataStage, release 7.2 server Server details v Itag ADE v Port 31538 v /disk1/Ascential/DataStage WebSphere DataStage, release 7.5.1 server v Itag A23 v Port 31546 v /disk2/Ascential/DataStage InfoSphere DataStage, Version 8.5 server v Itag 123 v Port 31540 v /opt/IBM/InformationServer/Server
The following table shows a scenario of with three Version 8.5 servers, and illustrates the use of port numbers and ITAGs for Version 8.5 installations.
Table 4. Scenario 3: Three instances of InfoSphere DataStage, Version 8.5 server installed on the same computer Engine tier instance InfoSphere DataStage, Version 8.5 server Server details v Itag ADE v Port 31538 v /opt/IBM/InformationServer/Server InfoSphere DataStage, Version 8.5 server v Itag BED v Port 31540 v /opt2/IBM/InformationServer/Server InfoSphere DataStage, Version 8.5 server v Itag 123 v Port 31542 v /opt3/IBM/InformationServer/Server
Installing Version 8.5 in addition to existing DataStage servers

You can maintain existing DataStage server instances while installing IBM InfoSphere Information Server, Version 8.5.
20
About this task

The Version 8.5 installation wizard detects existing DataStage servers during installation. You must provide a unique ITAG value and port number to use for the Version 8.5 server.
Installing IBM InfoSphere DataStage, Version 8.5 clients in addition to existing clients
When you maintain multiple versions of the InfoSphere DataStage server on Linux or UNIX computers, you must maintain corresponding client versions on Windows computers.
Before you begin

You need the IBM InfoSphere Information Server, Version 8.5 client installation software and the IBM InfoSphere Information Server Planning, Installation, and Configuration Guide, which is in the top-level directory of the installation media.
About this task

You can install clients for InfoSphere DataStage, Version 8.5 on the same Windows computer as your existing DataStage clients, and use the Multi-client Manager to switch between the different versions. You can also install InfoSphere DataStage, Version 8.5 clients on a separate Windows computer. If you are installing clients on a computer with existing clients, the client installation program detects their presence and installs the Multi-Client Manager program.
Procedure
1. Log on to the Windows computer as an administrator. 2. Turn off any firewall software that is installed on the computer. 3. Optional: Turn off your antivirus software. 4. Go to the root directory on the InfoSphere Information Server, Version 8.5 installation media or downloaded installation image. 5. Double-click setup.exe. The installation program starts and guides you through the installation procedure. 6. When asked for an installation directory, select the New installation option and either use the default directory, or specify a new directory. 7. When asked to select the product modules and components, select InfoSphere DataStage and QualityStage. Select other components as required by your installation plan.
Starting and stopping multiple DataStage servers

When multiple DataStage servers are on a single computer, you must identify the server that you want to start or stop.
About this task

You identify the DataStage server that you want to start or stop by setting the $DSHOME environment variable to reference the DSEngine subdirectory of the server. For example, there are two servers on the same computer with the following DSEngine subdirectories: v /disk1/Ascential/DataStage/DSEngine (existing 7.5.1 server)
21
v /opt/IBM/InformationServer/Server/DSEngine (IBM InfoSphere DataStage, Version 8.5 server)
Procedure
1. Set the $DSHOME environment variable to point to the /opt/IBM/ InformationServer/Server/DSEngine directory. 2. Stop the server by using the following command: $DSHOME/bin/uv -admin -stop 3. Wait thirty seconds to give the server time to stop. 4. Start the server by using the following command: $DSHOME/bin/uv -admin -start
Connecting to multiple DataStage servers

To connect to a DataStage server from a client when you have multiple servers, you must specify the server port number in addition to the name of the computer where the server is located.
About this task

You use a different procedure depending on the version of DataStage server and the client, and whether you are connecting from the command line. The clients for DataStage release 7 attach directly to the engine; the clients for InfoSphere DataStage, Version 8.0.1 and later attach to the engine by way of the services tier, and so the default port numbers are different for each type of client. Use the Multi-Client Manager to switch between different versions of the clients. The client version must match the server version.
Connecting to DataStage version 7.5.3 or earlier

Use this procedure to connect to a DataStage version 7.5.3 or earlier server from any client other than the Administrator client.
Before you begin

If multiple versions of the DataStage clients are on your computer, ensure that the same version as the server version is currently selected in the Multi-Client Manager.
About this task

Connects clients to DataStage servers.
Procedure
1. Select the Manager, Designer, or Director client from the Start menu. 2. In the Host System field of the Attach to Project window, type the identity of the server computer in the form hostname:portnumber where portnumber is the port number that the server uses. For example, type R101:31538 in the Host System field. 3. Type your user name and password. 4. Specify the name of the project that you want to attach to.
22
Connecting to DataStage version 7.5.3 or earlier from the Administrator client

Use this procedure to connect to a DataStage version 7.5.3 or earlier server from the Administrator client.
Before you begin

If multiple versions of the DataStage clients are on your computer, ensure that the same version as the server version is currently selected in the Multi-Client Manager.
About this task

Connect Administrator clients to a DataStage version 7.5.3 or earlier server.
Procedure
1. Select the Administrator client from the Start menu. 2. In the Host System field of the Attach to DataStage window, type the identity of the server computer in the form hostname:portnumber where portnumber is the port number that the server uses. For example, type R101:31538 in the Host System field. 3. Type your user name and password.
Connecting to IBM InfoSphere Information Server, Version 8.5

Use this procedure to connect to an IBM InfoSphere DataStage and QualityStage, Version 8.5 server from any client other than the Administrator client.
Before you begin

If multiple versions of the DataStage clients are on your computer, ensure that the same client version as the server version is currently selected in the Multi-Client Manager.
About this task

Connects clients to Version 8.5 server.
Procedure
1. Select the Designer client or Director client from the Start menu. 2. In the Domain field of the Attach to Project window, type the name of the domain to which your InfoSphere DataStage server belongs in the form DomainServer:9080. For example, type R101:9080. 3. Type your user name and password. 4. In the Project field, specify the identity of the project that you want to attach to in the form hostname:portnumber/project where portnumber is the port number that the server uses. For example, type R101:31348/datastage.
Connecting to IBM InfoSphere DataStage and QualityStage, Version 8.5 from an Administrator client
Use this procedure to connect to a Version 8.5 server from the Administrator client.
23
Before you begin

If multiple versions of the InfoSphere DataStage clients are installed on your computer, ensure that the same version as the server version is currently selected in the Multi-Client Manager.
About this task

Connects Administrator clients to a Version 8.5 server.
Procedure
1. Select the Administrator client from the Start menu. 2. In the Domain field of the Attach to DataStage window, type the name of the domain to which your InfoSphere DataStage server belongs in the form DomainServer:9080. For example, type R101:9080 in the Domain field or type R201:80 if you are using a front-end Web server. 3. Type your user name and password. 4. In the DataStage Server field, specify the identity of the computer where the server that you want to attach to is located in the form hostname:portnumber where portnumber is the port number that the server uses. For example, type R201:9080 or type R301:80 if you are using a front-end Web server.
Connecting to a Version 8.5 DataStage server from the command line

You can use the command line interface to control DataStage jobs in different projects.
About this task

These instructions assume that you are logged in to the operating system as the user that runs the job.
Procedure
v To connect to a project from the command line, you specify the server name and port number of the required instance with the -server argument in the form -server server:portnumber for local computers. v For remote computers that run InfoSphere DataStage, Version 8.5 server instances, you must specify the domain and the server name in the form -domain domain:domain_portnumber -server server:portnumber. The default domain port number is 9080. For example, to run a job on the local computer on the server that uses port 31359, run this command: dsjob -server r101:31359 -run myproj myjob v To run a job on the local computer on the default server, run this command: dsjob -run myotherproj myotherjob v To run a job on a remote computer called R101 on the Version 8.5 server that uses port 31360, you must also specify the host computer, the domain, and supply the login information. For example, enter the following command: dsjob -domain mydomain:9080 -server r101:31360 -user billg -password paddock -run myproj myjob
24
Chapter 4. Migration from QualityStage 7.5 and earlier releases

Required premigration tasks if your Version 7.5 or earlier source installation includes QualityStage. If QualityStage 7 is installed, you need to migrate your jobs to Version 8.5. (The term 'QualityStage 7' refers to all releases between 7.0 and 7.5.) If you were using the QualityStage plug-in stage in DataStage jobs, the jobs will need to be edited after they are migrated to the Version 8.5 installation. To run these jobs after migration, you must configure the jobs to use the available stages in Version 8.5. The QualityStage plug-in is not available or supported in Version 8.5. QualityStage 7 provides a method to migrate QualityStage 7 jobs, match specifications, and standardization rule sets to the InfoSphere DataStage and QualityStage Designer client in the Version 8.5 environment. In legacy mode your migrated job will use the QualityStage Legacy stage. In expanded form, your migrated job will make full use of all the specialized data quality stage types as well as the QualityStage Legacy stage. If you are migrating to a platform that was supported by QualityStage 7, then you can migrate by using legacy mode or expanded form. If the platform was not supported for QualityStage 7, then only expanded mode migration is available, and any QualityStage Legacy stage types in the migrated job must be replaced. The migration utility uses information in the QualityStage 7 server project directory to build the .dsx file format that InfoSphere DataStage and QualityStage requires to import jobs. The migration utility migrates the following QualityStage 7 objects: v Standardization rule set v Jobs in full legacy operational mode v Jobs in expanded form, in which some legacy operations are replaced by InfoSphere DataStage and QualityStage, Version 8.5 stages v Match specification You export projects to create a .dsx file that contains migrated jobs, rule sets, and match specifications in the Temp directory in the QualityStage 7 project directory.
Job migration in legacy operational mode

When you migrate QualityStage 7 jobs in full legacy operational mode, the original job is replaced with a single instance of a QualityStage Legacy stage and Sequential File stages linked as source and target stages. If you migrate a QualityStage 7 job in legacy operational mode, you can make only minor changes to the resulting QualityStage Legacy stage. Use this option only for stable jobs that will not be modified or jobs that are due to be replaced.
25
Note that, in a Japanese environment, the migrated job uses Data Set stages instead of Sequential File stages. In this case, you must create an additional job that reads the source data from the sequential file and writes it to a data set. The data set can then be read by the migrated job. If your original job wrote results to a sequential file, then you must create another job to write the results from the data set produced by the migrated job to a sequential file. Do not use the legacy operational mode option if you are migrating a job that contains the following QualityStage 7 stages because their functionality is not supported by the QualityStage Legacy stage: v Postal stages such as CASS and SERP v v v v Program stage Multinational Standardize stage WAVES stage Format Convert stage
QualityStage job migration in expanded form

When you migrate a QualityStage 7 job in expanded form, the QualityStage migration utility replaces the original job with one or more parallel job stages for each stage in the QualityStage 7 job, and with Sequential File stages that are linked together to represent the QualityStage 7 job flow. A job migrated in expanded form might have a mixture of data quality, processing, and Legacy stages when you open the job in the Designer client. For complex jobs, you can move the stages around on the canvas to make the job more intelligible. You can also replace a QualityStage Legacy stage with a data quality stage that has equivalent functions.
Rule set migration

The migration of a QualityStage 7 standardization rule set option migrates the rule sets explicitly by name. When a QualityStage 7 job is migrated, the migration utility detects the dependent rule sets and displays them. You can then choose to include the rule sets in the .dsx file with the job. The migration utility renames the rule sets within the .dsx file to prevent a naming duplication with a built-in IBM InfoSphere QualityStage, Version 8.5 rule set. The utility uses the following naming convention:
QS-7-Ruleset-Name_QS-7-Project-Name
Match specification migration

When you migrate a QualityStage job that contains match and unduplicate stages, the Match specifications are migrated with the job. The QualityStage migration utility includes the match processing information in the .dsx file with the job, if you selected the option "plus dependencies" to migrate the job. Once the job is imported, you can locate the match specification in the IBM InfoSphere DataStage and QualityStage Repository Match Specifications folder.
26
As with rule sets, match specifications are renamed when the information is imported. The match specification name has the following form:
QS-7-RefMatch-or-UndupMatch-Stage-Name_QS-7-Project-Name
Installing the WebSphere QualityStage migration utility

Use the WebSphere QualityStage migration utility to migrate QualityStage Version 7 to IBM InfoSphere QualityStage, Version 8.5. (The term 'QualityStage 7' refers to all releases between 7.0 and 7.5.)
About this task

Installs the QualityStage migration utility on your source installation.
Procedure
1. Choose one of the following options, depending on operating system type and whether you want to install the IBM InfoSphere DataStage and QualityStage server on the same computer as the QualityStage 7 server.
Option Installing the InfoSphere DataStage and QualityStage server on the same computer as the QualityStage 7 server Description Install IBM Information Server, installing the engine tier on the computer where the QualityStage 7 server is installed. The migration utility is installed with the engine tier. Install IBM Information Server on the target computer. The migration utility is installed with the engine tier. Before you run the migration utility on the target computer, make the QualityStage 7 project metadata available to the target computer. Make the metadata available by copying the entire QualityStage 7 project directory and all its contents to the target computer, or by making the directory available via the network (for example, by mapping a drive on Windows).
Installing the InfoSphere DataStage and QualityStage server on a different computer from the QualityStage 7 server (Windows or UNIX or Linux)
2. If you are migrating from a Unicode-enabled version of QualityStage Version 7, make the following changes to the qsmig.env file (located in the directory where the migration tool is installed). Make the changes before you use the migration utility. v Change the line, FLDEXTPR=0 to FLDEXTPR=1 v For the Japanese language, add the line, QSLCHARSET="CP932" v For the Chinese language, add the line QSLCHARSET="CP936" 3. On Windows, if the QualityStage Version 7 project directories are on a different drive from the migration utility, add the following line to the qsmig.env file: v APPCLIB=${PROJ}/Controls
What to do next
After you install the QualityStage migration utility, you can migrate QualityStage Version 7 jobs to InfoSphere DataStage and QualityStage, Version 8.5.
27
Running the QualityStage migration utility

Run the migration utility to create a file that contains the project metadata that is stored on a QualityStage 7 server.
Before you begin

The QualityStage migration utility runs on UNIX and Linux. For Windows, the script requires the MKS (Mortice Kerns Systems) Toolkit. The MKS toolkit is installed with the IBM InfoSphere Information Server client.
About this task

The QualityStage migration utility is automatically installed when you install the InfoSphere DataStage and QualityStage component of the suite. By default, the QualityStage migration utility is in the /opt/IBM/InformationServer/Server/ PXEngine/bin directory on a UNIX or Linux computer or C:\IBM\ InformationServer\Server\PXEngine\bin on a Windows computer.
Procedure
1. Ensure that the QualityStage project metadata is accessible from the computer on which the migration utility is installed. 2. From the migration utility directory, run the script to start the utility. v On UNIX or Linux computers, enter ./qsmigrate.sh. v On Windows, double-click the qsmigrate.bat file. 3. When prompted, enter the full path name of the QualityStage 7 project directory that contains the jobs that you want to migrate. The utility returns a list of the jobs and rule sets in the project. 4. Enter the number of an option from the list of options. 5. Select one of the following procedures, depending on the migration option that you selected:
Option 1. Migrate multiple QualityStage 7.x jobs plus dependencies OR 2. Migrate multiple QualityStage 7.x jobs in expanded form plus dependencies Steps for options 1. Enter a name for the output file that the migration utility produces. All the objects that you migrate are written to this file. The utility reports the path name of this file each time it informs you of the success or failure of an object migration. 2. When prompted with a job name, enter Y to migrate that job or N to skip that job. Repeat this step until you have migrated or skipped all the jobs. 3. When prompted with the name of a rule set or a match specification, enter Y to migrate that object or N to skip that object. Repeat this step until you have migrated or skipped all the objects. 3. Migrate individual QualityStage 7.x job OR 4. Migrate individual QualityStage 7.x job in expanded form When prompted, enter the name of the job that you want to migrate. The output file name is derived from the job name.
28
Option 5. Migrate individual QualityStage 7.x job plus dependencies OR 6. Migrate individual QualityStage 7.x job in expanded form plus dependencies
Steps for options 1. When prompted, enter the name of the job that you want to migrate. The output file name is derived from the job name. 2. When prompted with the name of a rule set or a match specification, enter Y to migrate that object or N to skip that object. Repeat this step until you have migrated or skipped all the objects When prompted, enter the name of the rule set or match specification that you want to migrate. The output file name is derived from this name.
7. Migrate individual QualityStage 7.x standardization rule set
What to do next
The QualityStage migration utility places the .dsx files that it creates in the Temp directory under the project directory. After you complete the migration of all of your jobs and objects, move the .dsx files to the computer where the Version 8.5 IBM InfoSphere DataStage and QualityStage client is installed.
Importing the migrated files into the Version 8.5 Designer client
After you complete the file migration, you must import the files into the metadata repository.
About this task

Imports the contents of the migrated files into the Designer client. The QualityStage clients in 7.5.3 and earlier are referred to as InfoSphere DataStage and QualityStage clients in Version 8.5.
Procedure
1. Move the .dsx file or files that you created when you ran the migration script to the computer where theInfoSphere DataStage and QualityStage clients are installed. 2. Open the Designer client and attach to the project where you want to save the InfoSphere DataStage and QualityStage jobs. 3. Select Import DataStage Components. 4. Specify the name of the migration file and click OK. The migrated jobs, rules sets, and match specifications are saved in the following folders: v Project_name Jobs folder. v Project_name Standardization Rules Imported Rules Rule Sets folder. v Project_name Match Specifications folder.
Provisioning imported rule sets

You need to provision imported rule sets from the Designer client before a job that uses them can be compiled.
About this task

Provisions the imported rule sets.
29
Procedure
1. In the Designer client, find the rule set within the repository tree Project Standardization Rules Imported Rules Rule Sets folder. 2. Select the rule set. 3. Right-click and select Provision All from the menu.
Results
You can compile and run any job that uses the rule set, except for migrated jobs that used the expanded mode to migrate. If you used the expanded form, read the instructions for preparing migrated jobs in the expanded format.
Preparing imported match specifications for use

You need to save the imported match specification in the InfoSphere DataStage and QualityStage Designer client and then provision the specification before you can use it in a job.
About this task

Prepares imported match specifications for use.
Procedure
1. In the Designer client, find the match specification within the repository tree Project Match Specifications folder. 2. Select the match specification and double-click to open the Match Designer. 3. Select Save All Passes. 4. Select Save Specification. 5. Click OK to close the Match Designer. 6. From the repository, select the match specification. 7. Right-click the match specification and select Provision All from the menu.
Results
You can now use the match specification in a Match job.
Preparing migrated QualityStage jobs for operation

You must prepare migrated jobs before they can be run. The steps can vary depending on the migration option that you selected.
Before you begin

For jobs that you migrated in Legacy operational mode (options 1, 3, or 5), compile the job to prepare it.
About this task

Prepares migrated jobs for operation in the target installation.
Procedure
1. Double-click the job in the Designer client repository tree to open it on the Designer canvas. When you run the migrated job, the results will vary depending on how you ran the job in previous versions of QualityStage. If you
30
used any mode other than the parallel extender mode, the results might be significantly different from previous runs. 2. If you did not previously run the job in parallel extender mode, insert a sort operation into the job design: a. Double-click the target Sequential File stage to open the Input Partitioning page. b. Select Sort Merge from the Collector type list. c. Under the Sorting section, click Perform sort. 3. Click OK to close the window. 4. Select File Compile to compile the job.
Preparing migrated jobs in the expanded format

You must prepare jobs migrated in expanded format before they can be run.
About this task

Prepares jobs migrated in expanded format.
Procedure
1. Double-click the job in the Designer client repository tree view to open it. The job contains both QualityStage Legacy stages and Data Quality stages. 2. If you have Standardize, Survive, MNS, or WAVES stages, double-click each stage to open it and then click OK. 3. Review any migration warnings that are displayed at the bottom of the job and resolve these issues. 4. Save the job. 5. Select File Compile. When you run the migrated job, the results will vary depending on how you ran the job in previous versions of QualityStage. If you used any mode other than the parallel extender mode, the results might be significantly different from previous runs. 6. If you did not previously run the job in parallel extender mode, insert a sort operation into the job design: a. Double-click the target Sequential File stage to open the Input Partitioning page. b. Select Sort Merge from the Collector type list. c. Under the Sorting section, click Perform sort. 7. Optional: Replace QualityStage Legacy stages with the equivalent data quality or processing stage. a. Double-click the QualityStage Legacy stage to open the Properties window. b. Find the stage that offers functionality that is equivalent to the Legacy stage functionality from the Data Quality section of the palette. c. Substitute the QualityStage Legacy stage with the equivalent data quality stage or stages. To optimize your job, it is more efficient to replace the QualityStage Legacy stages. d. Configure the new stage or stages. e. Compile the job.
31
Preparing migrated jobs to use updated Address Verification Interface and SERP libraries
The IBM InfoSphere QualityStage, Version 8.5 includes updated libraries for the Address Verification Interface and SERP modules. You must update the migrated jobs to use these updated libraries before they can be run.
About this task

For details on the new output columns and how to update the migrated jobs, see the release notes for the InfoSphere QualityStage modules.
Migrating real-time QualityStage jobs from Release 7 to Version 8.5

To migrate Version 7 jobs that use the IBM InfoSphere QualityStage Real Time Client API, you run the migration utility, replace legacy stages, and publish the job as a service.
Before you begin

Before you publish real-time jobs as services, you must complete the following tasks: v Install IBM InfoSphere Information Services Director, which is a component of IBM InfoSphere Information Server. Unlike version 7, Version 8.5 requires that you use InfoSphere Information Services Director to publish jobs as services. For more information about installing InfoSphere Information Server, see IBM InfoSphere Information Server Planning, Installation, and Configuration Guide.
About this task

Migrates jobs in expanded form.
Procedure
1. Migrate the job by running the migration utility in expanded form. 2. Replace the legacy stages with appropriate stages according to the table of replacement stages. 3. If your migrated job contains more than one input stage and more than one output stage, reconfigure your job to reduce the number of inputs and outputs. Alternately, you can reconfigure a job with more than one input to align with the behavior of the real-time stages. For more information about creating real-time jobs with two input sources InfoSphere DataStage and QualityStage, see IBM InfoSphere Information Services Director User Guide. A job can have only one ISD Input stage and only one ISD Output stage. 4. Update your jobs to add the ISD Output and ISD Input stages to replace the sequential input and output stages that exist in the migrated jobs. 5. Use InfoSphere Information Services Director to connect to InfoSphere QualityStage. For more information about connecting to InfoSphere DataStage and QualityStage, see IBM InfoSphere Information Services Director User Guide. 6. Develop an application, service, and operation by using InfoSphere Information Services Director. Your migrated real-time job is the information provider for the operation of the service. For more information about developing applications, services, and operations, see IBM InfoSphere Information Services Director User Guide. 7. Deploy the application as a service. For more information about deploying applications, see IBM InfoSphere Information Services Director User Guide.
32
Replace InfoSphere QualityStage 7 data quality stages

You can use the table of replacement stages to select the InfoSphere DataStage stage to substitute for the QualityStage 7 stage. The following table lists replacement stages for previous versions of QualityStage stages.
Table 5. Replacement InfoSphere DataStage and QualityStage stages for migrated QualityStage stages. QualityStage 7 Abbreviate Purpose Creates match keys from company names. Replacement stage No direct replacement. Use the Standardize stage to reformat company names and pair with an appropriate match.
Build
Rebuilds a single record from No direct replacement. Build was multiple records that are often used with Parse to analyze created with a Parse stage. multi-domain data fields. Use Standardize to accomplish the same function in one step. Generates a list of each unique value in single-domain data fields. Sort stage
Collapse
Collapse
Generates frequency counts of Aggregate stage data values in a field or a group of fields. Reformats files from delimited to fixed-length and vice versa. Provides I/O to an ODBC database. Analysis of data quality. Sequential File stage
Format Convert
Format Convert Investigate
ODBC stage or database specific stage Investigate stage and the Reporting tab for the WebConsole for IBM Information Server.
Match
Identifying data duplicates in Unduplicate Match stage in conjunction with the Match a single file by using fuzzy Frequency stage. match logic. Pairing records from one file with those in another by using fuzzy match logic. Standardize multinational address data. Tokenizes a text field by resolving free-form text fields into fixed-format records that contain individual data elements. Invokes a customer-written program. Reference Match stage in conjunction with the Match Frequency stage. MNS stage No direct replacement. Parse was often used with Build to analyze multi-domain data fields. Use the Standardize stage to accomplish the same function in one step. Depends on the functionality of the customer-written program. Possibilities include adding a Parallel Build, Custom, or Wrapped stage type.
Match
Multinational Standardize Parse
Program
33
Table 5. Replacement InfoSphere DataStage and QualityStage stages for migrated QualityStage stages. (continued) QualityStage 7 Select Purpose Conditionally routes records that are based on values in selected fields. Sorts a list. Breaks down multi-domain data columns into a set of standardized single-domain columns. Produces the best results record from a group of related records. Rearranges and reformats columns in a record. Acts as a gatekeeper for files in non-standard formats (variable length records, non-standard code page, binary or packed data). Produces multiple output records from a single input record. Adds record keys that consists of sequence number plus an optional fixed "file identifier." Join records from two files based on a key. Pairing records from one file with those in another by using fuzzy match logic. Merges data from multiple records into one. Manipulate and transform data record. Standardize and validate multinational address data. Replacement stage Switch and Filter stages
Sort Standardize
Sort stage Standardize stage
Survive
Survive stage
Transfer Transfer
No separate stage is required to do this in QualityStage 8. Sequential File or Complex Flat File stage
Transfer
Splitting records can be achieved by Copy stage followed by Funnel stage Surrogate Key Generator stage
Transfer
Unijoin Unijoin
Join stage or Lookup stage Reference Match stage in conjunction with Match Frequency stage. Join stage and Merge stage Transformer stage WAVES stage
Unijoin Unijoin WAVES
34
Chapter 5. Migration from IBM WebSphere RTI 7.5, 7.5.1, and 7.5.2 installations
Use the WebSphere RTI Export Wizard to migrate from WebSphere RTI 7.5, 7.5.1, and 7.5.2 installations to an IBM InfoSphere Information Services Director, Version 8.5 installation. After migration, you can use one of the following methods to administer and deploy InfoSphere Information Services Director: v InfoSphere Information Services Director command line interface v IBM InfoSphere Information Server console
Migrating RTIX files to Version 8.5

Use the WebSphere RTI Export Wizard to migrate to IBM InfoSphere Information Services Director, Version 8.5 installations.
About this task

Use the WebSphere RTI Export Wizard to migrate from IBM WebSphere RTI 7.5, 7.5.1, and 7.5.2 installations to InfoSphere Information Services Director, Version 8.5 installations.
Procedure
1. Halt WebSphere RTI. 2. Use the WebSphere RTI Export Wizard on the source computer to create an RTIX file. This RTIX file contains descriptions of operations and services. 3. Move the RTIX file to the Version 8.5 computer. 4. Use the IBM InfoSphere Information Server console Import function to import the RTIX file. This imported file is the equivalent of the output of the console design function. 5. You must associate the imported service descriptions with an application object before you can deploy the services. The import function is done at the application level to create this association.
Results
The imported service description is the equivalent of a service that is designed in InfoSphere Information Server. You can deploy the service description like any natively designed information service.
35
36
Part 3. Client-only upgrades
37
38
Chapter 6. Upgrading a client tier-only installation to Version 8.5

Use the IBM InfoSphere Information Server installation program to upgrade existing client tier computers to Version 8.5.
Before you begin

Before you run the installation program: v Complete the preparation steps that are described in "Preparing to run the installation program" in the IBM InfoSphere Information Server Planning, Installation, and Configuration Guide. v If you are installing Metabrokers and bridges, remove any existing installations of MetaBrokers and bridges from the target computer before you run the InfoSphere Information Server installation program. v See "Configuring your browser" in the Installation Guide to ensure that your Web browser is configured properly.
About this task

The installation program directly upgrades InfoSphere Information Server client software to Version 8.5. To upgrade client software directly by using the installation program, InfoSphere Information Server server-side software must not be installed on the computer. The installation program cannot directly upgrade the server-side software, or client software on a computer that also contains server-side software. To upgrade a computer that includes server-side software, you must create a new installation of InfoSphere Information Server, Version 8.5 that includes the client tier. To retain existing client versions, you must select a different installation directory location for Version 8.5. You can upgrade your client software at any time before, during, or after installing the server-side software on other computers. To upgrade a client tier-only computer, use one of the following two scenarios: v Manually uninstall existing client versions and install new client versions. Note: If you choose to manually remove existing client software, be sure to follow the documented procedure for your installation version to completely remove the software, restart the computer, and then use the Version 8.5 installation software to install the Version 8.5 client software. v Automatically upgrade the existing client versions on a client tier-only computer by using the following procedure. Procedure
Procedure
1. Start the installation program in graphical mode as described in "Starting the installation program in graphical mode" in the Installation Guide. 2. Follow the prompts in the wizard as they appear.
39
When the installation program detects that the target directory contains a client installation, confirm that you want to upgrade the installation. The current client installation is uninstalled. Note: To retain your existing client versions, you must select a different installation directory location for Version 8.5 to ensure that your existing versions remain intact. When the installation program has collected your settings, it saves a response file for you. This file is a text file that contains the settings that you made in the previous pages. When you run the installation program again, you can load the settings into the program instead of manually selecting them again. Note: Passwords are not saved in the response file. You must edit the response file by using a text editor to add passwords. Based on your settings, the installation program runs a prerequisites check. During this check, it analyzes the resources and file system of the computer to determine whether the new client installation is likely to succeed. The wizard page displays each check. If the prerequisites check fails, it is marked FAILED for the corresponding items. 3. If you receive a FAILED message, double-click the message to learn more about resolving it. Try to resolve the issue without exiting the installation program. If you believe that you solved the problem, click Check Again in the Prerequisites Check page. If it is necessary to exit the installation program, click Cancel and close the browser window. Resolve the issue and then restart the installation program. 4. The installation program summarizes your settings and then begins the installation. 5. Monitor the installation as described in "Installation progress monitoring" in the Installation Guide. Leave the terminal window open until the installation is complete. Note: During the installation process, the installation process might occasionally request a response from you. Check periodically to make sure that the system is not waiting for you to respond. The installation process might fail if the installation process halts for a long time. 6. After the installation is completed, install the correct Microsoft XML Core Services (MSXML) Service Pack. 7. Repeat the upgrade process for each client computer.
What to do next
If the installation fails: 1. View the installation logs for more information. See "Log files" in the Installation Guide. 2. Resolve any issues that are listed in the installation log files. 3. Remove the installation directory structure and the installation log file.
Windows Restart the computer. 4. 5. Run the installation program again.
Client tier computers that include DataStage client software include the Version 8.5 Multi-client Manager. After Version 8.5 is installed, use Version 8.5 is the active
40
version. To use an earlier version of the client software, use the Version 8.5 Multi-client Manager.
Chapter 6. Upgrading a client tier-only installation to Version 8.5
41
42
Part 4. Appendixes
43
44
Product accessibility
You can get information about the accessibility status of IBM products. The IBM InfoSphere Information Server product modules and user interfaces are not fully accessible. The installation program installs the following product modules and components: v IBM InfoSphere Business Glossary v IBM InfoSphere Business Glossary Anywhere v IBM InfoSphere DataStage v IBM InfoSphere FastTrack v v v v IBM IBM IBM IBM InfoSphere InfoSphere InfoSphere InfoSphere Information Analyzer Information Services Director Metadata Workbench QualityStage
For information about the accessibility status of IBM products, see the IBM product accessibility information at http://www.ibm.com/able/product_accessibility/ index.html.
Accessible documentation
Accessible documentation for InfoSphere Information Server products is provided in an information center. The information center presents the documentation in XHTML 1.0 format, which is viewable in most Web browsers. XHTML allows you to set display preferences in your browser. It also allows you to use screen readers and other assistive technologies to access the documentation.
IBM and accessibility

See the IBM Human Ability and Accessibility Center for more information about the commitment that IBM has to accessibility.
45
46
Accessing product documentation

Documentation is provided in a variety of locations and formats, including in help that is opened directly from the product client interfaces, in a suite-wide information center, and in PDF file books. The information center is installed as a common service with IBM InfoSphere Information Server. The information center contains help for most of the product interfaces, as well as complete documentation for all the product modules in the suite. You can open the information center from the installed product or from a Web browser.
Accessing the information center

You can use the following methods to open the installed information center. v Click the Help link in the upper right of the client interface. Note: From IBM InfoSphere FastTrack and IBM InfoSphere Information Server Manager, the main Help item opens a local help system. Choose Help > Open Info Center to open the full suite information center. v Press the F1 key. The F1 key typically opens the topic that describes the current context of the client interface. Note: The F1 key does not work in Web clients. v Use a Web browser to access the installed information center even when you are not logged in to the product. Enter the following address in a Web browser: http://host_name:port_number/infocenter/topic/ com.ibm.swg.im.iis.productization.iisinfsv.home.doc/ic-homepage.html. The host_name is the name of the services tier computer where the information center is installed, and port_number is the port number for InfoSphere Information Server. The default port number is 9080. For example, on a Microsoft Windows Server computer named iisdocs2, the Web address is in the following format: http://iisdocs2:9080/infocenter/topic/ com.ibm.swg.im.iis.productization.iisinfsv.nav.doc/dochome/ iisinfsrv_home.html. A subset of the information center is also available on the IBM Web site and periodically refreshed at http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r5/ index.jsp.
Obtaining PDF and hardcopy documentation

v PDF file books are available through the InfoSphere Information Server software installer and the distribution media. A subset of the PDF file books is also available online and periodically refreshed at www.ibm.com/support/ docview.wss?rs=14&uid=swg27016910. v You can also order IBM publications in hardcopy format online or through your local IBM representative. To order publications online, go to the IBM Publications Center at http://www.ibm.com/e-business/linkweb/publications/ servlet/pbi.wss.
47
Providing feedback about the documentation

You can send your comments about documentation in the following ways: v Online reader comment form: www.ibm.com/software/data/rcf/ v E-mail: comments@us.ibm.com
48
Reading command-line syntax

This documentation uses special characters to define the command-line syntax. The following special characters define the command-line syntax: [] ... | Identifies an optional argument. Arguments that are not enclosed in brackets are required. Indicates that you can specify multiple values for the previous argument. Indicates mutually exclusive information. You can use the argument to the left of the separator or the argument to the right of the separator. You cannot use both arguments in a single use of the command. Delimits a set of mutually exclusive arguments when one of the arguments is required. If the arguments are optional, they are enclosed in brackets ([ ]).
{}
Note: v The maximum number of characters in an argument is 256. v Enclose argument values that have embedded spaces with either single or double quotation marks. For example: wsetsrc[-S server] [-l label] [-n name] source The source argument is the only required argument for the wsetsrc command. The brackets around the other arguments indicate that these arguments are optional. wlsac [-l | -f format] [key... ] profile In this example, the -l and -f format arguments are mutually exclusive and optional. The profile argument is required. The key argument is optional. The ellipsis (...) that follows the key argument indicates that you can specify multiple key names. wrb -import {rule_pack | rule_set}... In this example, the rule_pack and rule_set arguments are mutually exclusive, but one of the arguments must be specified. Also, the ellipsis marks (...) indicate that you can specify multiple rule packs or rule sets.
49
50
Links to non-IBM Web sites

This information center may provide links or references to non-IBM Web sites and resources. IBM makes no representations, warranties, or other commitments whatsoever about any non-IBM Web sites or third-party resources (including any Lenovo Web site) that may be referenced, accessible from, or linked to any IBM site. A link to a non-IBM Web site does not mean that IBM endorses the content or use of such Web site or its owner. In addition, IBM is not a party to or responsible for any transactions you may enter into with third parties, even if you learn of such parties (or use a link to such parties) from an IBM site. Accordingly, you acknowledge and agree that IBM is not responsible for the availability of such external sites or resources, and is not responsible or liable for any content, services, products or other materials on or available from those sites or resources. When you access a non-IBM Web site, even one that may contain the IBM-logo, please understand that it is independent from IBM, and that IBM does not control the content on that Web site. It is up to you to take precautions to protect yourself from viruses, worms, trojan horses, and other potentially destructive programs, and to protect your information as you deem appropriate.
51
52
Notices and trademarks

This information was developed for products and services offered in the U.S.A.
Notices
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd. 1623-14, Shimotsuruma, Yamato-shi Kanagawa 242-8502 Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web
53
sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation J46A/G4 555 Bailey Avenue San Jose, CA 95141-1003 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to
54
IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs. Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows: (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. Copyright IBM Corp. _enter the year or years_. All rights reserved. If you are viewing this information softcopy, the photographs and color illustrations may not appear.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at www.ibm.com/legal/copytrade.shtml. The following terms are trademarks or registered trademarks of other companies: Adobe is a registered trademark of Adobe Systems Incorporated in the United States, and/or other countries. IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. 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 UNIX is a registered trademark of The Open Group in the United States and other countries. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom.
Notices and trademarks
55
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. The United States Postal Service owns the following trademarks: CASS, CASS Certified, DPV, LACSLink, ZIP, ZIP + 4, ZIP Code, Post Office, Postal Service, USPS and United States Postal Service. IBM Corporation is a non-exclusive DPV and LACSLink licensee of the United States Postal Service. Other company, product or service names may be trademarks or service marks of others.
56
Contacting IBM
You can contact IBM for customer support, software services, product information, and general information. You also can provide feedback to IBM about products and documentation. The following table lists resources for customer support, software services, training, and product and solutions information.
Table 6. IBM resources Resource IBM Support Portal Description and location You can customize support information by choosing the products and the topics that interest you at www.ibm.com/support/ entry/portal/Software/ Information_Management/ InfoSphere_Information_Server You can find information about software, IT, and business consulting services, on the solutions site at www.ibm.com/ businesssolutions/ You can manage links to IBM Web sites and information that meet your specific technical support needs by creating an account on the My IBM site at www.ibm.com/account/ You can learn about technical training and education services designed for individuals, companies, and public organizations to acquire, maintain, and optimize their IT skills at http://www.ibm.com/software/swtraining/ You can contact an IBM representative to learn about solutions at www.ibm.com/connect/ibm/us/en/
Software services
My IBM
Training and certification
IBM representatives
Providing feedback
The following table describes how to provide feedback to IBM about products and product documentation.
Table 7. Providing feedback to IBM Type of feedback Product feedback Action You can provide general product feedback through the Consumability Survey at www.ibm.com/software/data/info/ consumability-survey
57
Table 7. Providing feedback to IBM (continued) Type of feedback Documentation feedback Action To comment on the information center, click the Feedback link on the top right side of any topic in the information center. You can also send comments about PDF file books, the information center, or any other documentation in the following ways: v Online reader comment form: www.ibm.com/software/data/rcf/ v E-mail: comments@us.ibm.com
58
Index A
Abbreviate stage replacing QualityStage legacy 33 Administrator client, Version 8.5 importing 7.5.3 and earlier DataStage projects 15 DataStage Designer client (continued) importing files after migrating from 7.5.3 and earlier 29 installing multiple versions with Multi-Client Manager 21 restoring hashed files after migration from 7.5.3 and earlier 16 DataStage servers attaching to multiple 22 connecting to DataStage Version 7.5.3 and earlier 22 connecting to multiple 22 uninstalling Linux and UNIX 14 uninstalling Windows 13 Designer and Director clients connecting to multiple servers on Version 8.5 23 Designer client compiling jobs and routines 17 exporting projects before migration from 7.5.3 and earlier 10 importing 7.5.3 and earlier DataStage projects 15 importing files after migrating from 7.5.3 and earlier 29 importing migrated files (QualityStage) 29 importing projects to 15 installing multiple versions with Multi-Client Manager 21 recompiling DataStage jobs for 17 restoring hashed files after migration from 7.5.3 and earlier 16 Designer Manager client exporting projects before migration from 7.5.3 and earlier 10 different versions of clients switching between 18 Director client using to restore hashed files 16 dscmdexport command exporting DataStage 7.5.3 and earlier projects 10 dsenv environment variable saving DataStage 7.5.3 and earlier 11 DSHOME environment variable saving DataStage 7.5.3 and earlier 11 dsjob command using to connect to a Version 8.5 after migration 24 DSParams file saving DataStage 7.5.3 and earlier, Linux and UNIX 11 saving DataStage 7.5.3 and earlier, Windows 12 export about DataStage 7.5.3 and earlier projects 9 DataStage 7.5.3 and earlier projects using Manager client 10
F
files .ini, saving DataStage 7.5.3 and earlier 11 DSParams, saving DataStage 7.5.3 and earlier 11 odbc.ini, saving DataStage 7.5.3 and earlier 11 uvodbc.config, saving DataStage 7.5.3 and earlier 11 flat files moving DataStage 7.5.3 and earlier 12 Format Convert stage replacing QualityStage legacy 33
B
Build stage replacing QualityStage legacy 33
C
client tiers upgrading client-only installation 39 Collapse stage replacing QualityStage legacy 33 command line interface connecting to DataStage 7.5.3 and earlier projects 24 exporting DataStage 7.5.3 and earlier projects 10 command-line syntax conventions 49 commands syntax 49 compile DataStage 7.5.3 and earlier jobs after migration 17 DataStage 7.5.3 and earlier routines after migration 17 connect to Version 7.5.3 and earlier Designer, Manager, and Director clients 22 conversion script QualityStage migration utility 30 customer support contacting 57
H
hashed files importing into Designer client after migration 16 migrating DataStage 7.5.3 and earlier 13
I
import importing 7.5.3 and earlier DataStage projects 15 importing Version 7.5.3 and earlier QualityStage jobs 29 ini files saving DataStage 7.5.3 and earlier 11 install client-only installation 39 ITAG, multiple servers 19 Investigate stage replacing QualityStage legacy 33 ITAG installation migrating multiple DataStage servers 21 iTag installations multiple servers Linux, UNIX 19
D
DataStage 7.5.3 and earlier export using command line 10 export using Manager client 9 importing projects to Version 8.5 15 job dependencies, moving 12 legacy projects, exporting 9 moving schema files 12 saving setting files 11 DataStage Administrator client importing 7.5.3 and earlier DataStage projects 15 DataStage client uninstalling 14 DataStage Designer client compiling jobs and routines 17 exporting projects before migration from 7.5.3 and earlier 10 Copyright IBM Corp. 2006, 2010
J
job migration (QualityStage) legacy 25 match specification 26
E
expanded job migration QualityStage 7.5.3 and earlier 26
59
L
legacy migration replacing QualityStage Legacy stages 30 legacy migration (QualityStage) QualityStage jobs 25 legacy operational mode QualityStage 7.5.3 and earlier 25 legacy stages QualityStage, replacing 33 legal notices 53
O
odbc files saving DataStage 7.5.3 and earlier odbc.ini file saving DataStage 7.5.3 and earlier overview migration 3 11 11
P
Parse stage replacing QualityStage legacy product accessibility accessibility 45 product documentation accessing 47 Program stage replacing QualityStage legacy projects (DataStage) exporting 10 33
M
Manager client 10 match specification migration 26 Match stage replacing QualityStage legacy 33 migrated files (QualityStage) importing 29 provisioning 29 migrating hashed files 12 migration client tiers 39 compiling jobs after 17 DataStage schema files 16 from release 7.5.3 and earlier 7 ITAG installations 9 process overview 3 QualityStage v7.5.3 or earlier 25 real-time QualityStage jobs 32 RTI 7.5.2 and earlier 35 RTI 7.5.3 and earlier 35 scenarios and methodology 3 strategies 3 migration from 7.5.3 and earlier DataStage flat files 16 migration utility running QualityStage 28 Multi-client Manager using to switch between different client versions 18 Multi-Client Manager 21 installing multiple DataStage client versions 21 Multinational Standardize stage replacing QualityStage legacy 33 multiple DataStage clients connecting to 22 multiple DataStage servers connecting to Version 7.5.1 and earlier 23 connecting to Version 8.5 24 Multiple Job Compile tool for recompiling DataStage jobs 17
Sort stage replacing QualityStage legacy 33 special characters in command-line syntax 49 Standardize stage replacing QualityStage legacy 33 start DataStage 7.5.3 and earlier server 21 stop DataStage 7.5.3 and earlier server 21 strategy migration 3 support customer 57 Survive stage replacing QualityStage legacy 33 syntax command-line 49
33
T
trademarks list of 53 Transfer stage replacing QualityStage legacy 33
Q
QualityStage 7.0 to 7.5 job migration legacy form 25 QualityStage 7.5 plug-in rewriting jobs after migration 18 QualityStage 7.5.3 and earlier job migration, expanded form 26 QualityStage migration utility installing 27 UNIX and Linux 28 Windows 28 QualityStage rule sets migrating 7.5.3 and earlier 26 QualityStage stages replacing legacy 33
U
Unijoin stage replacing QualityStage legacy 33 uninstall DataStage client 14 DataStage server, Windows 13 DataStage servers, Linux and UNIX 14 overview, previous DataStage versions 13 UNIX and Linux installing QualityStage 7 migration utility 27 upgrade client-only installation 39 utility QualityStage migration 28 uvodbc.config file saving DataStage 7.5.3 and earlier 11
R
real-time QualityStage jobs migrating 32 replacing legacy stages QualityStage version 7.5.3 and earlier 33 restore 7.5.3 and earlier DataStage settings files 15 DataStage 7.5.3 and earlier settings files 15 RTI 7.5.2 and earlier migration export 35 rule sets, QualityStage migrating 7.5.3 and earlier 26
W
WAVES stage replacing QualityStage legacy 33 Web sites non-IBM 51 Websphere RTI 7.5.3 and earlier migration 35 Windows installing QualityStage migration utility 27 wizards WebSphere RTI Export 35
S
Select stage replacing QualityStage legacy 33 settings files restoring DataStage 7.5.3 and earlier files 15 saving DataStage 7.5.3 and earlier 11 software services contacting 57
N
non-IBM Web sites links to 51
60
Printed in USA
SC19-2965-00

C 1929650

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

C 1929650

Uploaded by

Copyright:

Available Formats

IBM InfoSphere Information Server

Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

IBM InfoSphere Information Server

Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

Part 2. Version 7.5.3 and earlier migrations . . . . . . . . . . . . . 5

Part 3. Client-only upgrades . . . . 37

Chapter 4. Migration from QualityStage 7.5 and earlier releases . . . . . . . 25

Copyright IBM Corp. 2006, 2010

Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

Part 1. Overview of migration

Copyright IBM Corp. 2006, 2010

Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

Chapter 1. Migrating to IBM InfoSphere Information Server, Version 8.5

DataStage, releases from 7.5.3 and earlier

QualityStage, release 7.5 and earlier

IBM WebSphere RTI 7.5, 7.5.2, and 7.5.1

Copyright IBM Corp. 2006, 2010

Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

Part 2. Version 7.5.3 and earlier migrations

Copyright IBM Corp. 2006, 2010

Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

Chapter 2. Migrations from Version 7.5.3 and earlier

Copyright IBM Corp. 2006, 2010

Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

Chapter 3. Migration from DataStage 7.5.3 and earlier versions

Before you begin

About this task

Copyright IBM Corp. 2006, 2010

Exporting projects from the DataStage Manager client

About this task

Exporting projects from the command line

About this task

Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

Saving DataStage settings files

About this task

Saving settings files (UNIX and Linux)

Before you begin

About this task

Saving the DSParams file (Windows)

Before you begin

About this task

Move job dependency objects

Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

Migrating hashed files

Before you begin

About this task

Remove previous versions of DataStage

Removing a DataStage server (Windows)

Before you begin

About this task

Removing a DataStage server (Linux, UNIX)

Before you begin

About this task

Command uninstll.sh uninstll.sh UNINSTLL.SH;1 uninstll.sh

Removing DataStage clients

Before you begin

About this task

Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

Importing DataStage projects

About this task

Restoring contents of DataStage 7.5.3 or earlier settings files

About this task