DSXchange

did you solve this? I believe the answer is simple. Even though the db2 instance you have co-located and defined as the home instance, I do not think the tables will be seen even in the drop down for importing metadata, right? You have to still catalog the connection just like you would for a remote...

One additional question/thought on the Samba vs. copy issue. I am familiar with older profilestage versions. When we did database connections or ODBC to profile data we also set the same connections up at the client side to enable the drill-through functions to query or sample the data through the p...

add a blank line after each entry in the project level odbc...I know it sounds weird...and also spell it the same [DB2_SEMATST] and <DB2_SEMSTST>

sqlserver 2005 requires new driver not in the orginal set. call support and should be available for download. you have: Driver=/dss/Ascential/DataStage/branded_odbc/lib/VMmsss20.sl Address=sqlserverhost,1433 you will need: Driver=/dss/Ascential/DataStage/branded_odbc/lib/VMmsss22.so we also had to b...

and you did make and entry in the project level uvodbc.config? also I believe you will find that you need a space following it, I place one before and after, some old bug.

<Bostontest>
DBMSTYPE = ODBC

Then try importing metadata, simplest test of connection I know

I see you have VMifcl20 I mentiond we are using VMifcl22. they are not the same.

We connect to a number of informix, try using the /branded_odbc/lib/VMifcl22.so driver, will work for version 9 and 10

I believe you can get to db2 on mainframe, but you would need a full UDB instance somewhere and use classic federation, otherwise a client instance only needs db2 connect. (to use the db2 api's)

you can always use the odbc and the data direct drivers and config using wire protocol

I think you need to step back and look at what ArndW said. FRom your description not sure if you are using a lookup fileset or a db2 stage directly, but the field in the lookup must be created nullable (assuming fileset) and the metadata in the job at hand also set this way. Basically all of the fie...

The problem with the work load manager is the identification of PID's. In order for this to be succesful we would need to have some level of seperation for each new invocxation that does not exits. I have used the job control path many times in the past. An alternative we have gone to at our current...

I have used a utility job to compare the differences from one category(sub-category) of table defs to another. This was part of the "old" bag of tricks and I probably have a copy somewhere. This Server job would produce in the log a diff report, first by member(new/deleted) and then for ma...

Thanks Ray That was my thoughts as well. I suppose I could add job activities to the sequencers which email log contents to a shared mailbox in the event of warnings and failures. Also, I have typically pulled job/link statisics(process metadata) for non-metastage clients and placed these in the tar...

Sorry I thought that is what I put in the last line of the details. :lol: If anyone is supporting this type of environment, How do you deal with viewing of job logs? How do you view intermediate files? Does anybody have anything in place which copies or moves this type of information to shadow or gh...

I have been a user of dsxchange for some time, but alas never a poster. I am very familiar wilth the entire tool suite, and have been using it for 5 - 6 years. I am currently at a client which has some prettty harse production server access issues. This is a DS EE client running version 7.5.1a on AI...