DSXchange

First off, this isn't a COBOL program so posting in all caps is considered shouting. No need to shout. This is not a simple thing, typically. There are entire products you can buy dedicated to parsing out things like names and addresses. Help us help you, provide a little bit more information when y...

Those are variables that the DSExecute call will automatically create and populate. After the call, 'Output' will have captured whatever the command that was run echoed to the screen and 'SystemReturnCode' will have the exit status of the command. From what I recall, multi-line 'Output' from the com...

To the best of my knowledge, there isn't a way to get Oconv with a 'D' conversion code to produce a date without delimiters. One way to 'work around' that would be to then remove them after the date was generated: EReplace(OCONV(ICONV(DSLink4.TransDate,"DMDY[2,2,2]"), "...

POST YOUR CODE.

Someone just pointed out to me a 'Before/After' routine called DSSqlLdr that I've never noticed before and I'm not having any luck finding it as it doesn't seem to exist in the Manager. Does anyone know anything about this and where I might find some documentation / information on it?

Right... dang, meant to mention that as well. Still think moving to a hashed lookup and away from hard-coding value pairs is a good idea, but if you want to do it a little 'cleaner' put it in a routine.

Check out the SEEK command. I would think you can use that to get back to the beginning of the file.

The number of Active stages are the key here, not the total number of stages in the job. And Ray did say that they may start separate processes, it depends on your job design (amongst other things).

I tried with @INROWNUM = 0, it didn't work out.. 'Course not, there's no such thing. As already noted, for the job to write to the audit table you need to have it process at least one row. Now, that can be a bogus record 'unioned' on in your source query that your job knows to not process or do som...

Why not 'View Data' and then use the Find option there?

ArndW wrote:Quite odd.

Yes Watson, indeed, never seen anything quite like it. Do keep us apprised of your progress, old chap.

My understanding is that the routine is compiled into the object code of the Job at run-time anyway. It doesn't do a call to an external routine. No, that would be a transform. Routines get called. That's why you have to recompile every job that uses a transform if you change it and you don't if yo...

You don't even need to use User Defined sql if you are doing that just to add the hint. With Column Generated I add it in the Derivation of the first field selected... works like a champ. For select statements anyway.

Post the complete sql and the complaint.

chulett wrote:That 'SYS_' prefix just means whomever modeled the database didn't give the constraint a name.

ray.wurlod wrote:Not in all databases.

True. But "SYS_Cnnnnnnnn" sure smells like a system generated Oracle constraint name to me and "not null" constraints are check constraints. In Oracle.

In any case, all previous advice still applies. If the OP doesn't get any joy on his own, hunt down the DBA.