You can either change the ISOMODE setting in uvconfig or change the Begin Transaction statement to set a specific transaction isolation level. Refer to the DataStage BASIC manual for the BEGIN TRANSACTION or SET TRANSACTION ISOLATION LEVEL statement to learn what the options are.
Have at least one configuration containing N processing nodes for each N, where N is the number of partitions in a partitioned DB2 table. By using the DB2 partitioning algorithm in these cases you can achieve true parallel loading without the need to repartition data. Other than that, the main crite...
There are 15 digits in 000010000024.350 (count them). That means decimal[15,3] in my book. "Precision" is the number of digits in the number, not the number of digits to the left of the decimal place.
Similarly, the executing DataStage job assumes that your script is in the project directory if it's not given as a pathname and it's not findable via the PATH environment variable.
No, but is does make sense to create a dictionary using only those "D" and "I" type definitions you will actually need. Or create an @SELECT phrase, which will limit the fields visible to ODBC (technically @SELECT is to "SELECT *" as @ is to "LIST", defining what the "all columns" asterisk actually ...
You could use a Complex Flat File stage, if it's a fixed-width format (which I assume it must be if it contains binary data). This stage can decode binary data within its own processing. Otherwise do as the others have suggested; read the column as a string (type Char) and use the SDK data conversio...
No, "all the time" is correct behaviour. You add them as job parameters if you might want to override them for that job. Think about APT_CONFIG as an example.
Create another, really simple parallel job with one Integer column. SELECT COUNT(*) FROM DUAL; will do as the query; output can be to a Peek stage. Can you get this to work?
Something like the derivations that kumar_s has given are as simple as you will ever get it; they map your requirements exactly. The actual derivations are syntactically incorrect, since there is no corresponding Else for the final Then (and there must be). You DO have to do the condition testing (I...
No, what I mean is that, if you buy the PeopleSoft PACK, you get the table definitions already imported. You also get some server jobs already written to extract data from PeopleSoft ERM. Since server jobs are part of Enterprise Edition, there is no technical reason not to go this route, rather than...
It's probable, particularly if it's a development account, that the VOC is full of crap, that the file dictionaries are also full of crap, that the account has not been set up for ODBC access (using HS.ADMIN menu in the HS.ADMIN account) and is not an SQL schema. All of these will combine in a consp...