DSXchange

T30FILES is related only to dynamic hashed files, so can be discounted for parallel jobs (provided you're not running more than, say, 30 at a time). Increasing T30FILES enlarges a memory-based table in which sizing information about dynamic hashed files is stored; it's about 112 bytes per row, so in...

Yes, PRISM came "into the fold" when VMARK and UniData merged to form Ardent, PRISM (more formally PRISM Warehouse Executive, sometimes PWE, sometimes pronounced "pee wee") having been acquired earlier than that by UniData. Much of the PRISM architecture - especially the idea of JCL Templates - unde...

Aaaaaaaaaaaaaaarrrrrrrrrrrrrrggggggggghhhhh!!!!!!!!!!!!!!!!

NEVER use kill -9 on DataStage processes.

Particularly when you have no idea that you are seeing all the processes or the parent/child relationships between them.

SQLState is specific to ODBC. You will not get it in an Oracle Enterprise stage.

Are these server jobs (as marked) or parallel jobs (as posted)?

No it isn't, because you have not clicked the button at the top the thread that would mark it as Resolved.

Any chance of sharing the script?

Welcome aboard. First, if this is a server job question, it should have been posted in the server job forum, not the parallel job forum. Second, you can only send mail from active stages (which support after-stage subroutines). Third, you don't want to do this. Wait till the job finishes, then run o...

or

The "each field on different line", or "vertical format", happens automatically when there are two many fields to fit in the current device width (e.g. 80 or 132). The "splitting onto multiple lines", or "wrap", occurs because the data are too wide for the field width defined in the file dictionary....

The tab is enabled. The ability to limit the number of rows is not.

On the NLS tab of the stage properties select Unicode or UTF-8 as the character map for the file.

That answer IS yes, the syntax is setname.parametername but, when you use the mouse (Insert Job Parameter), the syntax is managed automatically.

Compile in trace mode (under File menu). This is the only mechanism available for limiting the number of rows, and it inserts a Peek operator onto every link in your job design (this is how it accomplishes the trace). For "ordinary" running it is correct that you can not limit the number of rows fro...

Does this job run through midnight?

Your understanding that "Key" = "consider to be primary key" is the flaw. In this context "Key" means "join key", or common value used to identify the join. Neither in DataStage nor in SQL does the join key have to be a primary key.