DSXchange

Some sales dude from Ascential shows up to sell you more licenses?

No it doesn't. The next event number is kept in a control record called //SEQUENCE.NO in the data portion.
There are two other control records in a log file; //PURGE.SETTINGS and //JOB.STARTED.NO, which is why it's never a good idea to use CLEAR.FILE on DataStage logs.

All plug-in (= optionally installed) stage types have their manuals in the Packages folder on the DataStage client CD. In the output link of a Pivot stage you specify which columns are to be the pivot keys, which are other key columns (repeated in every row) and which columns generate new rows. Mark...

Test them exactly the same way you'd test them if you hadn't upgraded. :D
I'm in the middle of doing the same upgrade, but there's a change of hardware and operating system and an upgrade of database involved too. But the test suite is the same test suite used on the old system.

I did see the example properly. My suggestion was only about preventing the header rows from appearing in the output.
In the stage variable all you're doing is recording the final field and whether it changed, where field 2 begins with "n".

sivatallapaneni wrote:There's no shift in columns. columns are in the same position. only some columns are balnk in the second job.

You've missed the point.
What values are in the Position column in the Columns grid?

On that basis job design B should run faster than job design A.

Design A


Design B

because in job design B it all flows down hill!

What you're doing in ETL is like plumbing. You have a certain amount of data (water) to get from point A to point B. Your pipe has a finite capacity. You can get a larger pipe (faster CPU), you can get more pipes (multiple CPUs).

And remember, it ain't all water!

The NULL statement is a true no-op; it does nothing. This is not the same as the NULL, or unknown, value. But, as noted earlier, you're not interested in either. You seem to need a constraint expression of the form Left(inlink.Column002, 1) = "q" so that only these rows appear on t...

Scroll to the right in the Hashed File stages' Columns grids and verify that the Position column information is the same in each. Identification of fields in hashed file records is by Position rather than name, if Position is supplied.

That looks like a bad call to the underlying message logging routine $DS.WRITELOG (or perhaps DSR_LOG) in which none of the required information has been provided. In turn this could be an incomplete or damaged server installation. Or you may have uncovered a bug. You need to log a call with your su...

You can also use DSLogEntry to put an entry into an attached job's log. In your case, you could log entries into Job1 and/or Job2 log from the code in Job0 using this function.

Which hashed files in the repository you need to check depends on which hashed files were being written when the power failed. You're right that the most likely candidates will be the log files and the status files. But, if development work was being done at the time, there's also the config files a...

SIGBUS is a UNIX signal. It means that there has been a "bus error". The "bus" referred to here is usually the communication channel between the CPU and memory or other hardware components. Thus, you are being told in UNIX's beautifully succinct way that your application has done something that has ...

I tried it.

There were two pop-up advertisements (totally annoying) and the software complained that no email address had been supplied, which is false.

In short it does not work.