DSXchange

Basically you are not making use of the functionality that is provided. You can use a Routine activity to log a warning in the controlling job sequence; the Routine activity being triggered by detection of a failure (that is, a conditional trigger in the Job activity). You can also use the Exception...

Search the forum - you will find a query against DS_JOBOBJECTS and references to at least two (free) third-party utilities. None of them work if your table names are job parameter references.

One workaround would be to post-process the job log. Use DSGetNewestLogID to find the most recent Fatal event; this will return 0 if there is none.

Welcome aboard! :D You can create your own table definitions but, in order for MetaStage to gather data for lineage analysis, you must be disciplined about it. Any table definitions must first be created in the Repository (whether manually or via an Import mechanism). Column definitions in job desig...

When a database server generates any message (in this case "2 rows affected") DataStage logs it. This is the DataStage philosophy, on which I've posted at length before - search for "philosophy". The only possible way to suppress these messages is to cause the database (or ODBC driver) not to genera...

Julian means different things to different people. The conversion functions (Iconv() and OConv()) use "ordinal day within the year". If that's what you want use (or use "D/YJ" to get year first.

How about ----> IPC ---- ...TX ---+ +---> LC ---> IPC ---> TX ---> .... ----> IPC ---- Or, assuming that the results are going to a table ---> TX2A ---> .... ...T1X ---+ ---> TX2B ---> .... The two Transformer stages TX2A and TX2B perform identical processing (apart from the negative sign) and const...

I don't think there's a documented limit. What does Help say about the StartLoop activity properties?

The default default (ibid?) on version 7.0 is 50. Just checked. I'll have to wait till I get to a 7.5 system to verify your assertion. As to where it's set elsewhere, it wouldn't be a Registry hack if it were going to control dsjob - which can be, and usually is, executed on the server. Most of my s...

Look at the error message again. It's tried to authenticate against a domain. I guess that's why they have beta. Report it.

Each "Done" message from DSD.RUN indicates a run of a server job. In your case everything appears to have worked (there are no warning messages). Your loop runs job Load_GGSN then runs job Load_SGSN. Does your job design trap exceptions (via an Exception Handler) or non-success triggers from the con...

The message suggests that Windows authentication is trying to authenticate the user/password using a domain controller.

Are you executing in a domain or a workgroup?

Try logging in as machine\Administrator rather than using an unqualified user ID.

In Director, reset any job sequence that has aborted.

Tell us if any "from previous run..." message was logged.

And, by the way, a Sequencer is an activity that you can use in a Job Sequence. Please use correct terminology; exactitude aids precise communication.

Welcome aboard. :D Jim's answer is correct. There seems to be a bug in the metadata handling when buffering is enabled, whether explicitly or implicitly. An intermediate sequential file defeats the purpose of buffering by forcing data to be touched down to disk (at "disk speed" rather than at "memor...

Only because it has to be!

I think a better description in this case is a 32-bit application pretending to be a 64-bit application. Main hassle for this port was (is?) "word" alignment in shared memory segments.