DSXchange

Your quote characters are in the wrong places. Also you need two levels of quoting, which implies that you need to use two of the three available quote characters.

"Custom UniVerse routine" is intended for customers who are running the UniVerse database and wish to use their own cataloged routines. Clearly you do not fit these criteria.

You don't use Call statement like that, as an rvalue in an assignment statement. Read all about the CALL statement in the DataStage BASIC guide. Read all about the DSExecute subroutine in the DataStage Programmer's Guide. It may be in the DataStage BASIC manual too. Command = "LIST.READU" ...

In my experience Information Analyzer is a profiling tool. There is no concept of a "target table".

Funnel the sources then Sort on the key field generating a Key Change column. In a downstream transformer stage use the Key Change field to trigger an increment in the Group ID.

How are you managing to use Information Analyzer to load a target table?

SCD-1 is not "include a current value for the attribute". SCD-1 is "update the dimension record with the new value". In SCD-1 there is only ever a current value - SCD-1 does not preserve history. The SCD stage does allow you to generate an IsCurrent indicator field when SCD-2 is ...

I do not have RCP enabled. But when I output it to a dataset, it does not have any metadata defined, but the columns are there in the dataset when ran. This is because the operator that writes to a Data Set is copy - it simply makes a copy of the virtual Data Set in the job. And virtual Data Sets d...

Simply omitting the word "nullable" will suffice.

A word of warning. 2004041 might mean the 41st day of 2004. In that case you need to use StringToDate() with a mask of "%yyyy%ddd" to yield a date, then date component functions to extract the relevant pieces of date (year, month and day).

Are you running on a single physical machine or multiple physical machines? Are you repartitioning the data for the second sort?

What are the sort keys for the two sorts? Can you leverage the "don't sort (previously sorted)" functionality for some of the keys in the second sort?

You can't calculate it. It's a given. Your network transmits data in "packets". Talk to your network administrator about the concept. Typically packet size is 1KiB, 2KiB or 4KiB.

Probably not. The error is "statement failed to run". Something in the database server actually prevented execution of the statement.

Are all the services - particularly the WebSphere Application Server service server1 - running? What was the error message? What user registry are you using?

You can achieve this with judicious use of triggers within the sequence for the first part. For the second part you would need to design your sequence to test each job's most recent exit status (via a routine activity perhaps), the exit status of the sequence itself, the dates associated therewith, ...