DSXchange

Next time please start a new topic when you have a question like this rather than finding an unrelated post and replying to it. I've split it out this time but I had to guess your DataStage version and platform...

So your example is of what it should have looked like? If so, what does it actually end up looking like? Are you certain that this is a USERSTATUS issue and not the classic case where job parameters have quotes stripped from them?

My comment comes from Oracle not having a DATETIME data type. Now, that may be a term that ODBC uses but Oracle has either a DATE or a TIMESTAMP both of which support date and time elements. The latter adds in microseconds or "fractional seconds". The column where it mentions "fractio...

So... not Oracle then.

50 is the Oracle default for sqlldr and is separate from job warnings. Zero isn't valid but you could set ERRORS=N to a large number as one of the OPTIONS the stage allows you to pass in, I would imagine.

Not that I remember. I recall having to create the new folder and then dragging everything from the old to the new.

sohasaid wrote:Thank you chulett for your replies; however, I couldn't read any of your suggestions it's hidden as a Premium content

how can I read them?!

That one is simple... renew your Premium Membership.

Add to that the advice to start by reading about and becoming familiar with what each function does, either in the BASIC manual pdf or in the Designer client's "online" help. That will help you figure out how to cobble them together to get the results you require. There are bigger question...

sohasaid wrote:2- The input file doesn't contain a fixed number of columns, i mean it could be three columns or more!

Any suggestions?

As a suggestion, that would have been an excellent bit of information to include in your initial post.

I just want to point out that since this is a horizontal pivot, the Pivot stage can handle this just fine. Yes, even with the column name column thrown in. All that needs is for you to add three new columns into the flow and 'hard code' the column names in them, they can then be pivoted in pairs wit...

Me, I'd like some clarification of what these two statements mean. Not sure I see any reference to Sequence jobs. :? In production Jobs get run as per daily Schedule. "As per daily schedule"? Via what mechanism? The below command is used during execution of Job. But we are not supposed to ...

Maybe. The accompanying DDL for this release might have been missed or perhaps it wasn't time for the code to have been migrated.

Cool, thanks.

So... for my own edification, if you please. When you say it is a "Universe program" is that equivalent to a BASIC routine or is it more like a stand-alone / "executable" version of a BASIC routine? Never really played any Universe games so unfamiliar with the term.

Thanks.

I do not believe that has ever been supported in the CFF stage. If true, as a workaround you could look into a looping Sequence job that calls the CFF job once per file found, passing in the filename to process as a parameter.