DSXchange

It seems like quite a few people need processing in PX to allow the stripping of header and trailer records for an incoming dataset. Wouldn't it be nice if the Sequential file import had separate header and trailer flags that would tell the engine to strip an existing header/trailer and output them ...

T.J.,

"parjdev.pdf" is wrong? ASCL put out a bad doc? It couldn't be.

I hope you are kind enough to let ASCL know what its errors are in parjdev.pdf. You will be doing a service to the community.

-BP

T.J.,

What are the output messages for the other "APT_CombinedOperatorController"s?

Also, have you tried turning off the combined operators env var? That would be a good step in debugging this error.

- BP

It is recommended to run PX on an even number of nodes. If you set the config to be 14-way or 16-way, do you still get the same problem?

-BP

TJ mentioned that buildop and a regular transform can have similar run times when executing similar code. How do the runtimes compare for the PX Basic Transform?

-BP

Is this issue resolved?

BP

Thanks bigpoppa. Time to show off for me :D So, you use OSH for writing OPERATORS and later save them, compile them, make them as a stage and use them in PX jobs. Is that the usage of them ? What you're describing is a build-op. An "operator" is just a generic term for a PX stage. A build...

You can still call modify/filter and all the old stages by directly invoking them using the generic PX stage..

As for the constraint.. A record travels downstream only if it satisfies the constraint of the outbound dataset. Please post an explanation of the constraint and the constraint code.

- BP

In OSH or thru the PX GUI? If the record schema has been saved to a file, you can open it in DS Manager and manipulate it there.

- BP

An operator in PX is the same thing as a stage in DataStage Server. An operator is a piece of ETL code that is displayed as an icon in the GUI, similar to a stage in DS Server. PX operators offer different functionality than do Server's stages. And PX operators run only on the PX engine which is sep...

Looks as if you need another outbound dataset - one for the rejects and one for the non-rejects, right? How many outbound links does your dataset have?
-BP

Can you post the error messages?

Thanks,
BP

A work around:

Set your global env vars in a file. Source that file in a new "osh" executable in the PX bin directory.

- BP

A thought for a hack:

A parser somewhere in this job must be expecting '>' and '<' to be special characters. Could you try escaping the '>', like '/>', in your query?

Ultimately I believe you have discovered (or rediscovered) a bug with the DB2 stage.

-BP

You can always see what your transform and buildop compiled code looks like. You just need to find the right .trx file associated with the transform/buildop.

Please look thru previous posts to determine how to find the .trx file.

-BP