DSXchange

CFF does not readily support a single record type having varying numbers of columns, outside of the support of the "OCCURS DEPENDING ON" COBOL FD clause. Hmmm ... I wouldn't call it a varying number of columns so much as optional columns. ;) If it hits the end of record before the end of ...

Pending a resolution of this with the CFF stage, I think build another job to preprocess the file by padding out records to their respective maximum lengths.

Hello, I am trying to update a table in an Access 2007 database on a pc. I have created a system DSN without a password but cannot get it to connect. Is this Access file and ODBC DSN on the same server as DataStage? Can you use something like Excel or Microsoft Query to first prove that the ODBC So...

I am reading 600 million records from the database and I don't want it to read 2000 records at a time because that would be too many hits against the database. I think you misunderstand what ths assay size is doing. It is NOT generating 300,000 separate queries against the database where each retri...

I'm having a problem variable record lengths on the CFF stage. I think my problem is the same as this thread, but I don't think respondants there really understood the problem: http://www.dsxchange.com/viewtopic.php?p=391304 I have several different record types and I have the meta data defined for ...

I have repeatedly run into this error and for me it is not because of a null in a column that I am grouping on. It is a null in a column that is the subject of an aggregate function, such as MAX. Normally, aggregate functions like MAX ignore nulls. However, when you use KEEP FIRST, it is different. ...

Confused as to how that actually fixed the problem as there was no need to return multiple anything in the example given, just one. :? Thanks guys, this thread helped me too. Craig, I agree with your confusion. I have the same situation where I have 2 columns with an equality match on the lookup, t...

OK, I had a quick look at the SCD stage. I'm not sure I'm seeing how it applies. Maybe I didn't describe my requirements very well ... actually, I didn't really describe my requirements at all. So, here is the functionality I require. I have from an external source an image of how my record should l...

OK, I'll admit that this had not occurred to me. The table is not a dimension, it is not tracking changes over time, nor is the structure in any way a star schema, but sure, if you think the SCD stage might still be useful for this, I'll have a look. Still interested in feedback on the Difference st...

I'm trying to compare a set of potential updates with existing data on a table. The updates have a natural key which is also on the table but is not the primary key (it has a surrogate key). the catch is that I also want to bring the primary (surrogate) key through for changed records so I can use i...

OK, all working. Just had to sort out correct namespace references in the header. To summarise the whole issue from start to end: * DataStage did not recognise anything in the WSDL when loaded directly from the URL. Once I saved it as a file, then read the file with DataStage, it found the necessary...

Aaaarrrgggghhh!!! Don't you hate it when the answer is in the manual. I had to read the section on adding headers 3 or 4 times before the penny finally dropped as to what it was saying. Instead of putting a value in for a field as you do with the body of the enevlope, it requires you to enter the ac...

As suggested above, the proxy may indeed be the issue. Assuming you can prove that, you may need to write your own handler to deal with it, if the other server expects the client to get the response ... Gah ... so it seems that I have to pay to see your response. That aside, we have done some furth...

Well, it turns out things aren't working so well after all. While I was getting a response, it was an empty response and independent tests have confirmed that this is what happens when authentication fails. The soap envelope from our independent tests looks like this. <soap:Envelope xmlns:xsi="...

Doh ... maybe I'm the problem.

Maybe I just can't run this in test mode from Designer.

I built a job to call the routine and it seems to work.