DSXchange

To find the jobs contained in a certain Sequence, pretty sure you would use the DSSEARCH command for that. An exact search here for that should turn up the gory details.

See if this helps.

chulett wrote:Why not ask your official support provider and post the answer back here?

Did you?

Contact your official support provider, see if they have any idea what might be going on. You'll have to get past the "backwards compatibility" hurdle first. Out of curiousity, I'm assuming you had to edit the .dsx file and change the version to allow it to import into the 8.5.0 project, y...

First thing to mention... there is no guaranteed backwards compatibility.

Secondly, what about jobs developed in that 8.5.0 environment with either of those stages, do they 'open'? Meaning, is the imported one the only one with the problem?

Sorry, I just converted it by eye... 30 is zero, 31 is one, etc. I do believe there are "conv" functions in Server for this but I'm afraid I don't know of the equivalent for a Parallel job. Hopefully someone else can help with the specifics.

Technically... my understanding is you can have two with the same name, it's just that it will never find and use the second one.

SFDC? Something to do with Sales Force?

Forever is a long time. :wink: First off, how large is the data set that you are attempting to view? Is it of a target or a source? If the table is 'large' or the source sql is complex, it can take quite some time for it to start returning data. Also note that the Oracle stages do not use ODBC but r...

Nope. They need to be unique.

Unsure of the answer but the issue is the write buffers, they only get flushed to disk periodically and only for certain when the job ends and the file is "closed".

Or maybe GIRLS.

Try it and let us know.

More efficient to do the Left() once into another stage variable and then reference it multiple times in the other derivations.

From a pure Oracle standpoint, there is no backwards compatibility. You should always use the "least common denominator" approach: of all of the Server versions you need to connect to, use the client from the lowest version. I've never had an issue over the years with that approach but the...

Before you change anything, you need to understand why it is there.