DSXchange

I don't think so. I've seen release notices for Sun Solaris, AIX, Linux Red Hat and SuSE and Windows 2003 but I've never seen a mention of HP-UX. I'm not surprised, IBM get on well with Sun and Microsoft but they are fierce competitors against HP in hardware and DW.

There is DataStage and QualityStage for Unix System Services on the mainframe that does a very good job of using the mainframes processing power. I don't think there is a QualityStage 8 tool that runs in an old mainframe operating system.

You can do this in a Sequence job. A stage would check the validity of the file - either by a BASIC routine or by calling an operating system script. A trigger from that stage would go to a notification stage if the file is bad or to a DataStage job to process the file if it is good.

Yes you can use a join stage or a lookup stage. You could do it in a lookup stage for any volume of data but the advice from IBM is to use join stages for very large lookup sources and lookup stages for smaller sources. You can also join tables in a database stage if they are on the same database th...

Can we create a new forum around Information Server events? We have the IoD2007 event coming up next month and it would be good to put IoD threads in one forum, it can then be used to announce or discuss other events and conferences.

The easiest and most robust way to do it is to use the IBM Rational Data Architect MetaBroker to export your table definitions and import them into the RDA modeling tool and use that to generate DDL. You can get a free 30 day eval of RDA from the IBM website. If you want to hack away at the reposito...

It's not supported by DataStage nor is it supported by MetaIntegration Technology who build the metadata import bridges for the Information Server. IBM are working on an ANS.1 to XML converter that DataStage could process though it's a round about way to get to the data.

Version 8 comes with an extra option on the Import menu that lets you import via a connector in addition to the standard plug-in imports. No extra code but you configure the connection up front instead of doing it in every job.

I'm under a non-disclosure agreement but you will find out everything at my IoD session! If you register for IoD and read my session abstracts you will get some additional details.

If you remove the word "worker" it all makes sense. Looks like a cut and paste mishap.

On the far right of the conference home page is one box for "Register Today" and a box below it (if you have already registered) with "Enrollment now open - Create Your Agenda". People are signing up to sessions with some of the smaller sessions already full.

You are on Unix so I don't think you can get a SQL Server native client option - you have to go with ODBC. As Ray says the Connector stage (new in version 8) is the best as it can be re-used across many jobs and should lead to faster development. I think ODBC is the only connector stage in version 8...

DataStage client might get slow on opening and compiling jobs. If the company is going to do this a lot they should get better results with DataStage running on Metaframe. I would go 2-3G of RAM for the client machine. It can run on less than 2G of RAM but the cost benefit says spending money on RAM...

I've signed up for the Information Server community reception on the Sunday night before the IOD conference . I fly in the previous day. This is the official social get together for DataStage nuts. Activity 2589 - IP&S - Information Server and Master Data Management Community Reception Abstract ...

If you can run the Information Server console but not a DataStage client product then it is a problem in the DataStage Server and has nothing to do with the WAS or Metadata Server. The version 8 DataStage server is much the same as previous versions and you can get some ideas on forum threads such a...