This document presents a set of standard practices, methodologies, and examples for IBMWebSphere® DataStage Enterprise Edition™ (“DS/EE”) on UNIX, Windows, and USS.
Except where noted, this document is intended to supplement, not replace theinstallation documentation.
The primary audience for this document is DataStage developers who have been trained inEnterprise Edition. Information in certain sections may also be relevant for TechnicalArchitects, System Administrators, and Developers
This document is intended for the following product releases:- WebSphere DataStage Enterprise Edition 7.5.1 (UNIX, USS)- WebSphere DataStage Enterprise Edition 7.5x2 (Windows)
Document Revision History
April 16, 20041.0Initial Services releaseJune 30, 20052.0First version based on separation of EE BP into four separate documents, mergednew material on Remote DB2, configuring DS for multiple users.December 9, 20053.0Significant updates, additional materialJanuary 31, 20063.1Updates based on review feedback. Added patch install checklist item (7.10) andWindows 7.5x2 patch list.February 17, 20064.0Significant updates, new material on ETL overview, data types, naming standards,USS, design standards, database stage usage, database data type mappings, updatedstyles and use of cross-references.March 10, 20064.1Corrected missing Figure 9.March 31, 20064.2Added new material on establishing job boundaries, balancing job resourcerequirements / startup time with required data volume and processing windows, andminimizing number of runtime processes. Moved Baselining Performancediscussion to Performance Tuniing BP. Expanded performance tuning section.May 08, 20064.3Removed Architecture Overview (now a separate document). Expanded file stagerecommendations.July 17, 20065.0Updated directory naming standards for consistency with
. Segmented content into “Red Book” and “Standards”.Clarified terminology (“Best Practices”). Incorporated additional field feedback.
This document uses the following conventions:ConventionUsage
In syntax, bold indicates commands, function names, keywords, and options thatmust be input exactly as shown. In text, bold indicates keys to press, functionnames, and menu selections.
In syntax, italic indicates information that you supply. In text, italic also indicatesUNIX commands and options, file names, and pathnames.PlainIn text, plain indicates Windows NT commands and options, file names, and pathnames.
Parallel Framework Red Book: Data Flow Job DesignJuly 17, 20062 of 179
© 2006 IBM Information Integration Solutions. All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in aretrieval system, or translated into any language in any form by any means without the written permission of IBM.