DSXchange

That's the weirdest thing about this: It happens with any routine in any sequence. And it just appeared one day -- of course, no one knows what was done prior. :wink: I can pick any sequence, right-click to view properties on any routine stage, and up comes the error. P.S. I found "fixtool"...

This is a Windows server so I don't think it has dsfixtool -- at least, I am unable to find it. I can locate and execute UVFIXFILE but am not familiar with its options. I ran "UVFIXFILE DS_ROUTINES" and it simply reported back: Beginning TRACE of DS_ROUTINES. TRACE of DS_ROUTINES completed...

Just the standard "This error message generally indicates corruption in the DS_ROUTINES file in DataStage." Which is what was expected to be the issue. But, if true, then I wonder why REINDEX didn't fix it.

Just an update: I opened a case with IBM and they said that their typical direction is to use DS.REINDEX (or DS.TOOLS #2). Since I had already done that, they said the only options were to 1. re-import the routines from an existing export 2. export the modules from the project, recreate the project,...

[I've found several posts that address the error "FieldToProp: Internal error - Bad number of subobjects" but none of them provide any solutions.] A particular project has begun exhibiting this error when attempting to view properties on any routine in any sequence in the project. Based up...

Thanks for the tip on the ODBC stage. I'll check that out as an alternative.

[Oh sure, figure it out just after I post it. Oh well, I'll keep this here in case anyone else encounters this issue. Discovery below.] Though the job didn't indicate any issues, the log showed an error for every insert attempt on the second input link. The error was "OLE DB provider error: Can...

[If this is in the manual or in the help somewhere, I've missed it.] I have a single MSOLEDB stage which has two input links from the same transformer stage. The two links target two separate tables and each uses the generate SQL option with read committed transaction isolation. When I run the job, ...

I am migrating to v8.5 and am having issues getting in through telnet. (I'm an old DATA-BASIC programmer so it is convenient for me to do a lot of my function development at the UV command-line. This was my typical development model under 7.5.) After searching, I found some posts about telnet that l...

I have successfully installed 8.5 and imported a project which was exported from 7.5. I compiled all the jobs and sequences. As a result, it updated the environment variables and I went in to Administrator and updated all the values. So far, so good. My SQL Server related jobs all run fine. However,...

Ok, give me a cone hat to wear... :? I found this http://etl-tools.info/en/datastage-faq-219_error-81021-calling-subroutine-record-action=2.htm that reminded me that I had recently begun using the Omit option when logging in. I'd never used it before; never even played around with it until recently....

Additional info: These same 16 sequences now no longer compile successfully from Designer when running in the source project. I know these all compiled succesfully before. I was working with two of them just last week and they were fine at that time. But if I open them in designer and attempt to com...

So far, all my efforts have failed. I ran UVFIXFILE on DS_JOBS, DS_JOBOBJECTS, and DS_ROUTINES on the source project. Then I re-exported this entire project and tried to import it into the newly created project. The majority of the jobs came in but there are 16 (all are sequences not jobs) that will...

I'm still curious. Would you be so kind as to post the previous iteration of CompareFiles routine? Believe me, so am I! :) The current version was included in my prior post. The version using DSExecute() can be found at the top of the post prior to that (the really long one). The original version (...

Since this road is simply not getting me there, time to try a new route. I wrote a DATA-BASIC routine that returns the same values (0=same, 1=different, 2=missing). It simply opens the files, reads the content into two variables and checks whether they are equal. So, I'll tag this as a workaround. T...