DSXchange

Is this a server job (as marked) or a parallel job (as posted)? The APT... environment variables will have no effect whatsoever on a server job.

Have you tried using 000 as the field delimiter and as the record delimiter?

Post your subroutine code.

An after-anything subroutine does not have the direct ability to return values. How did you want to use this value?

Use the DB2/UDB API stage. DRS adds another layer of software that you don't need unless you require the flexibility to use other database types. For now, the DB2 Enterprise stage does not connect to DB2/400. Since the DB2/UDB API stage invokes DB2 Client software, you will need to have this install...

There are those who advocate bolting a star schema logical design onto a third-normal-form (3NF) physical design. These are mainly vendors of 3NF database products who don't have a good star schema story.

Teradata is an interesting and performant hybrid.

Indeed it's one of the lab exercises you do in the IBM DataStage Essentials (server edition) class. So, please verify the details as DSguru2B requested, also verify that you have sufficient privilege to create tables in the data source to which you are connecting. Are there any error/warning message...

In a parallel job?!! Good trick!

@NULL is a BASIC system variable. It can be used in server jobs and in BASIC Transformer stages and in expressions in job sequences. It can not be used in parallel Transformer stages. As noted, use SetNull().

In parallel jobs it's not done in the Transformer stage. DB2 rejects are captured by a reject link on the DB2 stage. However, better practice is to detect the duplicates upstream. The easiest way is a Sort stage that generates a Key Change column. The second easiest way is to use stage variables in ...

The pathname specified by the APT_CONFIG_FILE environment variable, wherever it is set, will be used to specify the configuration file with which a parallel job is run.

In the Generator property use the job parameter as the initial value.

"Warning" in DataStage logs can mean either "trouble" or "unusual". In this case, the creation of the SDKSequences hashed file is an unusual event; it only ever occurs once in a project.

This sugestion's a little bit "left field" but give it a try anyway. Set your breakpoints, then recompile immediately before starting the job in the debugger.

Put in a Peek stage and use it to grab a sample of rows into a file. Then use a hex editor to find out the ASCII code of the character in question.

Welcome aboard. :D

You really haven't given enough information. Presumably the status of the job is running and the debugger is paused at a breakpoint? What stages are on either end of the link where the breakpoint is defined?

Is there a DSD.RUN process on the server associated with this job? If not, does clearing the job's status file return it to a known status? You may then want to put some diagnostic routines in as before/after subroutines to see how far the job gets.