DSXchange

The reason is that the DEFFUN declaration is required, and there's no mechanism for providing that directly from a trigger expression. For Routine activities compiling the job sequence adds the DEFFUN declarations for those, so that one level of indirection is required.

... with appropriate date format string, for example "%yyyy%mm%dd"

The Pivot stage also has its own manual, with very clear examples.

You should simply be able to name the Query as the "table name" in your ODBC stage.

You do NOT edit posts to remove the original questions to try to make those helping you look foolish.

YELLOW CARD

Introduce the environment variables into your job as job parameters (or in a parameter set), then use job parameter references within your DB2 Enterprise stage or DB2 API stage.

Right click on a database stage, or find it with quick or advanced search and right click, and you should get data lineage available on the pop-up menu. There's also a data lineage tool on the toolbar - hover your mouse pointer over the tools to get tool tips explaining what each is.

None without extra information. For example, during the upgrade were there any messages about indexes? It may be relevant to reindex the project using DS.REINDEX. (This is only an example, you might also like to run DS.CHECKER to verify that the local repository is intact.) One good piece of news; t...

Welcome aboard. When you mark a thread as resolved at DSXchange it is customary to make a short post explaining how it was resolved. Please do so.

mdbatra wrote:the formatting dint came correct.

Wrap it in Code tags.

One line in the file contains " Erico & Co CPA's " Each 20 in the raw string is a hexadecimal representation of a non-printing character - in this case the space character. It is this line that is generating the error - compare it with the record schema (which you did not include in yo...

No. The FTP stages do not transfer files. They transfer byte streams; they read the file on the remote server and stream the bytes directly into your DataStage job. Better approach is to create a script to effect the file transfer, and use the exit status of that script to trigger appropriate action.

Worry about

of PRIMARY KEY constraint 'PK__F4201__382F5661'. Cannot insert duplicate key in object 'dbo.F4201'.

first. This may have caused the statement truncation and consequent network buffer underflow.

No idea. What is your user-defined SQL doing? Are any constraints, joins, groupings or sorts supported by indexes in the database? Could this be faster using bulk unload and processing in DataStage?

Note that there are two separate properties. Record Delimiter is used when you have one character (or none) to mark the end of a line. Record Delimiter String is used when you have more than one character to mark the end of a line. Record Delimiter String offers "DOS style" as a preconfigured select...