DSXchange

I wasn't quite sure where to post this message but I guess we can start off in this Forum. I've been reading the DSXChange newsletter and came across the Server to Parallel Transition Lab article. It's the point about the next release of DataStage (Hawk) that is going to be released that interests m...

No need to post my code as my issue is now fixed :) . I emailed support and they recognised the incident as "case 62595". They sent me a patch (vmdsjsgn.dll) and this has fixed the problem. The actual description of the error is "Loop fails with runtime stack overflow at the 258 itera...

Sorry Kim but are you talking about official IBM/Ascential Support. I have logged a call with my administrators - they are the ones that are able to raise calls with support. Hopefully they will if they can't suss out what the problem is. When you say post your code - are you referring purely to the...

I have a job sequence that has start loop - end loop activities built in and am having a problem that is happening consistently. After 256 iterations of the loop the job sequence falls over with the error shown below: From previous run DataStage Job 72 Phantom 12977 Program "JOB.223462050.DT.13...

Thanks Ray but I was already using a Custom trigger rather that an unconditional one - my problem though was trying to use the ReturnStatus rather than CommandOutput. So my solution is: Check data file for Data (in Basic Routine) If data file has certain info then create a debug file with info added...

I have a Job Sequence that creates approx 500 data files (one at a time inside a loop). After each file is created I run an awk command in a Routine to check the contents of the file. If the file has certain data then I write debug info out to another file - this is the case in about 1 in 5 files. I...

I've just tried calling an MSSQL stored procedure via odbc and it actually worked - this goes against what I said above but don't confuse this with thinking that MSSQL Procedures will work as you expect. The definition of the procedure will only be picked up if defined as public but this is not a pr...

You do not have to re-import definitions for Production. What I am saying is : (1) MSSQL Stored Procedures are not supported/do not work within DataStage. (2) The reason you are able to bring back the definitions of the procedures is because the code is read form the same tables as Sybase (sysobject...

DataStage doesn't support Microsoft SQL Server Procedures - dynamic SQL I'm afraid. Import only works for SQL Stored Procedures when they have access rights granted to Public - this is not recommended for Production systems. Remove Public access and you won't be able to import the definition. While ...

This functionality used to exist pre-SQL Server 7.0 and should be maintained going forward even if the vendor changes their core. BCP still exist for SQL Server 2000 albeit for backward compatability but a loader could be built around the "bulk insert" function.

Has anyone ever gotten the "Sybase BCP Load" stage to work with MSSQL Server 2000 ? It appears that it worked with MSSQL 6.0 but hasn't for future releases of MSSQL Server as the changes to the core has made it quite different to Sybase. Is this really true ? So instead of BCP'ing data str...

Thanks very much

I exported a number of Job Sequences/Server Jobs from one Project and imported them into another. When I did this I noticed in Director that none of the Jobs are compiled. Rather than having to compile them all manually is there a quick way to compile them all ?

I had the 50 errors warning before when I ran my Job Sequence via dsjob but strangely it didn't complain when I ran it through Developer/Director. The reason that I had so many warnings was that I was passing a value out of a routine via Ans instead of the required 0 (hence a warning for each) - thi...

Type "which dsjob" - if the dsjob.exe isn't found then you'll have to add the directory in which it resides to your path.