DSXchange

I assume you are running on the mainframe. If you have universal command, you can control starting, resetting, checking codes of your datastage job through your JCL. In most cases, you will not need sequence jobs. You then use your job scheduler to run your JCL.

Could you not use the CFF stage into a transform stage. The transform stage would have have multiple outputs. Use constraints for each record type for each corresponding redefined definition.

In the Administrator, set the option APT_AUTO_TRANSPORT_BLOCK_SIZE
to false.

In the Administrator, set the option APT_AUTO_TRANSPORT_BLOCK_SIZE
to false.

In the Administrator, set the option APT_AUTO_TRANSPORT_BLOCK_SIZE
to false.

In the Administrator, set the option APT_AUTO_TRANSPORT_BLOCK_SIZE
to false.

In the Administrator, set the option APT_AUTO_TRANSPORT_BLOCK_SIZE
to false.

set the APT_AUTO_TRANSPORT_BLOCK_SIZE to false in the administrator .

I have set record performance data in a parallel job, and I am getting the following error: Invalid value for option -f: Data/Performance/Performance/XXX. I created a directory to record performance information, set the value for APT_PERFORMANCE_DATA parm and enabled the job monitoring in the direct...

keshav0307 wrote:ooops. i was confused with the similar problem in my a job having Teradata stage.

problem in this job is because the oracle table has a column timestamp type. so the job is running fine in 7.5.2 and giving thsi problem in 7.5.1A.

what paramater setting in the administrator was changed to fix this

Is it possible to import table definitions from an oracle database link?

Ray, what is the APT_ variable name that has to be set to fix this problem?

Just put the column name in double quotes in the SELECT statement. Otherwise the "-" character could be interpreted as a request to perform subtraction. And/or you can use an alias column name in the SELECT statement; there's no need to create a view. Do I have to do anything special with...

The error message was pretty self-explanatory as to what the problem is. When I use the modify stage to rename the column, I am getting the same error on the oraread. Is there possibly another solution or should I create a view of the table and rename the column with the problem, or call IBM and cre...

stopping and starting the DS engine resolved the problem.