<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" gd:etag="W/&quot;DU4HQ30zeCp7ImA9WhRRFE4.&quot;"><id>tag:blogger.com,1999:blog-6382168860269342737</id><updated>2011-11-27T18:52:12.380-05:00</updated><category term="Unix" /><category term="OLAP" /><category term="SQL" /><category term="Bitmap Join Indexs" /><category term="Informatica" /><category term="Performance Tuning of Data Stage" /><category term="Data Stage" /><category term="Oracle" /><category term="Business Intelligence" /><category term="data mart" /><category term="Bitmap Indexes on Partitioned Tables" /><category term="OCA/OCP Questions" /><category term="Data Modelling" /><category term="Unix commands" /><category term="Bitmap Index" /><category term="OLTP" /><category term="Business Objects" /><category term="PL/SQL Concepts" /><category term="ER Modelling" /><category term="WebSphere QualityStage" /><category term="QualityStage" /><category term="Data Warehousing" /><category term="Data Stage FAQ" /><category term="Dimensional Modelling" /><category term="Datastage Server" /><category term="Cognos" /><category term="Informatica Performance Tuning" /><title>ETL Data warehouse Concepts....Ascential Data Stage,Informatica ,SQL,PL/SQL,Unix</title><subtitle type="html">This Blog is all about ETL related Information.It gives information about Datastage ,Informatica,Oracle,SQL,PL/SQL ,Unix,Data warehousing ,Data Modeling and ER Model concepts and FAQ's</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://etl-information.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://etl-information.blogspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/6382168860269342737/posts/default?start-index=4&amp;max-results=3&amp;redirect=false&amp;v=2" /><author><name>sami</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>66</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>3</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/EtlDataWarehouseAndBusinessIntelligenceascentialDataStageAndInformaticaConcepts" /><feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="etldatawarehouseandbusinessintelligenceascentialdatastageandinformaticaconcepts" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry gd:etag="W/&quot;A0YASH46eyp7ImA9WxBUEkk.&quot;"><id>tag:blogger.com,1999:blog-6382168860269342737.post-8100219782381226636</id><published>2010-02-27T00:00:00.002-05:00</published><updated>2010-02-27T00:39:09.013-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-02-27T00:39:09.013-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="QualityStage" /><title>Investigating source data using Investigate Stage</title><content type="html">&lt;h1&gt;&lt;u&gt;&lt;b&gt;Investigating source data using Investigate Stage&lt;/b&gt;&lt;/u&gt;&lt;/h1&gt;

&lt;div&gt;&lt;h3&gt;Learn how to set up and process an Investigate job to provide data from which you can create reports in the IBM Information Server Web console.&lt;/h3&gt;

&lt;h4&gt;Follow these steps to set up and link an Investigate job&lt;/h4&gt;&lt;/div&gt;

&lt;div&gt;&lt;p&gt;Create a QualityStage job by adding Data Quality stages and DataStage sequential files and stages to the Designer canvas. Connect the stages together for the flow of data from source file to each stage.&lt;/p&gt;

The job should contain a Sequential file(Source File)---&gt;Copy Stage---&gt;2 Investigate Stages ---&gt;Sequential Files(3 Files.Name,AreaToken,Area Pattern)&lt;/div&gt;

&lt;div&gt;Check this diagram for the job canvas&lt;/div&gt;

&lt;a href="http://4.bp.blogspot.com/_t0WXtUXDhhY/S4ivsyjK-QI/AAAAAAAAANU/1HSy9JxcLHk/s1600-h/g_qstutor_Investjob.gif"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 320px; height: 234px;" src="http://4.bp.blogspot.com/_t0WXtUXDhhY/S4ivsyjK-QI/AAAAAAAAANU/1HSy9JxcLHk/s320/g_qstutor_Investjob.gif" border="0" alt=""id="BLOGGER_PHOTO_ID_5442793333695641858" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6382168860269342737-8100219782381226636?l=etl-information.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6382168860269342737/posts/default/8100219782381226636?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6382168860269342737/posts/default/8100219782381226636?v=2" /><link rel="alternate" type="text/html" href="http://etl-information.blogspot.com/2010/02/investigating-source-data-using.html" title="Investigating source data using Investigate Stage" /><author><name>sami</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/_t0WXtUXDhhY/S4ivsyjK-QI/AAAAAAAAANU/1HSy9JxcLHk/s72-c/g_qstutor_Investjob.gif" height="72" width="72" /></entry><entry gd:etag="W/&quot;DEYDRXg4eyp7ImA9WxBQFkQ.&quot;"><id>tag:blogger.com,1999:blog-6382168860269342737.post-349815977831865359</id><published>2010-01-16T21:34:00.003-05:00</published><updated>2010-01-16T21:42:54.633-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-01-16T21:42:54.633-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="WebSphere QualityStage" /><category scheme="http://www.blogger.com/atom/ns#" term="QualityStage" /><title>Introduction to WebSphere QualityStage</title><content type="html">&lt;div id="{7B02D21F-69A0-4E46-BF2D-5DFD1EF100A3}" style="text-align: center;"&gt;WebSphere QualityStage comprises a set of stages, a Match Designer, and related capabilities that provide a development environment for building data-cleansing tasks called jobs.
&lt;/div&gt;
&lt;div id="{275CB0CF-D9E3-4E4E-BEC2-BD3CD238A271}" style="text-align: center;"&gt;Using the stages and design components, you can quickly and easily process large stores of data, selectively transforming the data as needed.
&lt;/div&gt;
&lt;div id="{A39BE705-23E9-462C-92AB-8C832883CB11}" style="text-align: left;"&gt;WebSphere QualityStage provides a set of integrated modules for accomplishing data re-engineering tasks:
&lt;/div&gt;
&lt;ul&gt;&lt;li&gt;    Investigating&lt;/li&gt;&lt;li&gt;    Conditioning (standardizing)&lt;/li&gt;&lt;li&gt;    Designing and running matches&lt;/li&gt;&lt;li&gt;    Determining which data records survive&lt;/li&gt;&lt;/ul&gt;
The probabilistic matching capability and dynamic weighting strategies of WebSphere QualityStage help you create high-quality, accurate data and consistently identify core business information such as customer, location, and product throughout the enterprise. WebSphere QualityStage standardizes and matches any type of information. By ensuring data quality, WebSphere QualityStage reduces the time and cost to implement CRM, business intelligence, ERP, and other strategic customer-related IT &lt;span style="font-weight: bold;"&gt;initiatives.

&lt;/span&gt;&lt;div id="{902FEC60-CAE7-4E0E-85E8-BFAE08438E93}" style="text-align: center;"&gt;&lt;span style="font-weight: bold;"&gt;Scenarios for data cleansing&lt;/span&gt;
&lt;/div&gt;
Organizations need to understand the complex relationships that they have with their customers, suppliers and distribution channels. They need to base decisions on accurate counts of parts and products to compete effectively, provide exceptional service, and meet increasing regulatory requirements. Consider the following scenarios:

&lt;ol&gt;&lt;li&gt;&lt;span style="font-weight: bold;"&gt;Banking: One view of households&lt;/span&gt;&lt;/li&gt;&lt;/ol&gt;   To facilitate marketing and mail campaigns, a large retail bank needed a single dynamic view of its customers’ households from 60 million records in 50 source systems.

  The bank uses WebSphere QualityStage to automate the process. Consolidated views are matched for all 50 sources, yielding information for all marketing campaigns. The result is reduced costs and improved return on the bank's marketing investments. Householding is now a standard process at the bank, which has a better understanding of its customers and more effective customer relationship management.
&lt;span style="font-weight: bold;"&gt;
          2.Pharmaceutical: Operations information&lt;/span&gt;

A large pharmaceutical company needed a data warehouse for marketing and sales information. The company had diverse legacy data with different standards and formats, information that was buried in free-form fields, incorrect data values, discrepancies between field metadata and actual data in the field, and duplicates. It was impossible to get a complete, consolidated view of an entity such as total quarterly sales from the prescriptions of one doctor. Reports were difficult and time-consuming to compile, and their accuracy was suspect.

  Most vendor tools lack the flexibility to find all the legacy data variants, different formats for business entities, and other data problems. The company chose WebSphere QualityStage because it goes beyond traditional data-cleansing techniques to investigate fragmented legacy data at the level of each data value. Analysts can now access complete and accurate online views of doctors, the prescriptions that they write, and their managed-care affiliations for better decision support, trend analysis, and targeted marketing.

&lt;span style="font-weight: bold;"&gt;          3.Insurance: One real-time view of the customer&lt;/span&gt;

  A leading insurance company lacked a unique ID for each subscriber, many of whom participated in multiple health, dental, or benefit plans. Subscribers who visited customer portals could not get complete information on their account status, eligible services, and other details.
  Using WebSphere QualityStage, the company implemented a real-time, in-flight data quality check of all portal inquiries. WebSphere QualityStage and WebSphere MQ transactions were combined to retrieve customer data from multiple sources and return integrated customer views. The new process provides more than 25 million subscribers with a real-time, 360-degree view of their insurance services. A unique customer ID for each subscriber is also helping the insurer move toward a single customer database for improved customer service and marketing.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6382168860269342737-349815977831865359?l=etl-information.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="enclosure" type="text/html" href="http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r1/index.jsp?topic=/com.ibm.swg.im.iis.qs.roadmap.doc/topics/qs_roadmap.html" length="0" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6382168860269342737/posts/default/349815977831865359?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6382168860269342737/posts/default/349815977831865359?v=2" /><link rel="alternate" type="text/html" href="http://etl-information.blogspot.com/2010/01/introduction-to-websphere-qualitystage.html" title="Introduction to WebSphere QualityStage" /><author><name>sami</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author></entry><entry gd:etag="W/&quot;CUYCSXg_fSp7ImA9WxVVEUw.&quot;"><id>tag:blogger.com,1999:blog-6382168860269342737.post-8262425470939668984</id><published>2009-03-03T14:01:00.009-05:00</published><updated>2009-03-03T15:46:08.645-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-03-03T15:46:08.645-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Data Stage" /><category scheme="http://www.blogger.com/atom/ns#" term="Data Stage FAQ" /><title>Data Stage Job Status Values</title><content type="html">&lt;h3&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;The Data Stage Job Status values can be found in &lt;br /&gt;$DSHOME/include/dsapi.h file &lt;/h3&gt;
&lt;br /&gt;
&lt;h4&gt;&amp;nbsp;&amp;nbsp;These are the values defined in dsapi.h file for JOB STATUS:&lt;/h4&gt;
&lt;br /&gt;&lt;br /&gt;
&lt;table align="left" border="1" &gt;&lt;ol&gt;
&lt;li&gt;#define DSJS_RUNNING&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;/* Job running */&lt;br /&gt;
&lt;li&gt;#define DSJS_RUNOK&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;/* Job finished a normal run with no warnings */&lt;br /&gt;
&lt;li&gt;#define DSJS_RUNWARN&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;/* Job finished a normal run with warnings */&lt;br /&gt;
&lt;li&gt;#define DSJS_RUNFAILED&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;3&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;/* Job finished a normal run with a fatal error */&lt;br /&gt;
&lt;li&gt;#define DSJS_VALOK&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;11&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /* Job finished a validation run with no warnings */&lt;br /&gt;
&lt;li&gt;#define DSJS_VALWARN&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;12&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;/* Job finished a validation run with warnings */&lt;br /&gt;
&lt;li&gt;#define DSJS_VALFAILED&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;13&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;/* Job failed a validation run  */&lt;br /&gt;
&lt;li&gt;#define DSJS_RESET&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;21&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /* Job finished a reset run */&lt;br /&gt;
&lt;li&gt;#define DSJS_CRASHED&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;96&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;/* Job was stopped by some indeterminate action */&lt;br /&gt;
&lt;li&gt;#define DSJS_STOPPED&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;97&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;/* Job was stopped by operator intervention (can't tell run type) */&lt;br /&gt;
&lt;li&gt;#define DSJS_NOTRUNNABLE&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;98&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;/* Job has not been compiled */&lt;br /&gt;
&lt;li&gt;#define DSJS_NOTRUNNING&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;99&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;/* Any other status */&lt;br /&gt;
&lt;/ol&gt;&lt;/table&gt;&lt;a href="http://www.dsxchange.com/viewtopic.php?t=125568&amp;highlight=job+status"&gt;&lt;/a&gt;
&lt;a href=" http://www.dsxchange.com/viewtopic.php?t=125568&amp;highlight=job+status" target="_new"&gt;
JobStatus&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6382168860269342737-8262425470939668984?l=etl-information.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/6382168860269342737/posts/default/8262425470939668984?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/6382168860269342737/posts/default/8262425470939668984?v=2" /><link rel="alternate" type="text/html" href="http://etl-information.blogspot.com/2009/03/data-stage-job-status-values.html" title="Data Stage Job Status Values" /><author><name>sami</name><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author></entry></feed>

