DSXchange

You should contact your official support provider in order to verify whether or not the Surrogate Key Stage (and the transformer's SK logic) support a DB sequence on DB2 z/OS. A workaround would be to call the DB sequence in the connector by using the NEXT VALUE function--this will require coding yo...

That is not the proper way to modify a date. Your source will be converted to a simple integer, then the math performed, then the outer functions performed. While probably most dates might work, several would not--for example, 20100501 - 1 = 20100500, which would not be a valid date. Take a browse t...

Is the target defined as Number(16) or Integer? You've stated both :| It's not the conversion that's the problem, it's the datatype the value is being placed into. Make sure your datatype out of the transformer can hold the value. As Andy stated, an Integer cannot hold a value that large. Either a B...

There is currently no automatic method to do this that I'm aware of. You can examine the job's osh script and recreate it's functionality in the GUI. However, for any transformers, buildops and custom operators you will need the original source as that won't be available in an executable-only job ex...

Within the context of a buildop (opd file) or a custom operator, inrec: * and outrec: * are called "schema variables" and represent all columns which have not been explicitly named within the schema (similar to Runtime Column Propagation in the GUI). For more detail, look in the IIS 8.5 Cu...

This has been mentioned in other threads in the forum but bears occasional repeating for those searching: ParameterSet default values are included in the job at COMPILE time. Therefore, hardcoding default values for parameters that will change value over time (such as userids and passwords!) is neve...

The text of the error message itself tells you what needs to be done to resolve the error. You do realize that it appears to be a transformer stage that is throwing the error and NOT the lookup stage (the stage name in the message is "XFM")? Here's some supporting documentation Regards,

Column Generator is probably already running in parallel. Row Generator runs in sequential mode by default. You should understand that by setting it to parallel, you will have more records generated (number of nodes executing * number of records requested). You may not want to do that, or you may wa...

Use the block size of 1 if you require it, otherwise you should consider the default or even larger block sizes if you are assigning a lot of surrogate keys. Lower value block sizes introduce more overhead to the job due to needing to access the statefile more often. I've seen a block size of 1 brin...

The transformer will evaluate the entire logic of a complex condition, even if one of the conditions of an OR construct is already true. This can cause issues like this when null handling is combined with other conditions as in your logic. The sequential file records make it through probably because...

What is the datatype of the column in Oracle, and what is it within DataStage? Is the column in Oracle nullable and does it contain nulls (no date, no empty string)?

All of those stages should work with DB2 on Linux/Unix and Windows. You should contact your official support provider for verification and for the specific versions of DB2 supported by those stages in the version of Information Server you are working in. FYI...there is no need to send a private mess...

Which DB2 stages are your jobs using? In general, the DB2 Connector stage is compatible, DB2Z stage is not. If the DBAs perform the migration successfully, you shouldn't have any data issues but you should ALWAYS thoroughly test to identify any issues that may be particular to your environments. Reg...

Yes, either through the filter option in the sequential file (calling awk or sed or cut commands) or by running an external command against your file after it's been written. Either way, if you leave the 4th column defined in your output you will need to supply some sort of data for it, even if it's...

You have to make a choice: You will either need to remove the 4th output column from your output definition or populate the column with default data if you need to keep the column defined in the output. What drives the choice: What is required by the downstream process that receives your output file...