DSXchange

Sure. You can change the metadata or column definition for any stage that can use a schema file AND has column propagation turned on. Two huge limitations. I don't have a complete list of the stages where this can be done but have used it on a Sequential stage. It can be done because the schema file...

Add a column as normal in the Column Generator with all the properties you require. Save it as a table definition. Edit the table definition and go to the layout tab. Select the Parallel radio button. This will show you in schema file format the column and properties you just defined in the Column G...

The "how" has certainly been answered but the "Why" has been bugging me. Has the company you are with spent money for EE and yet does not have a solution for Change/Version Control for other non-EE software? Wow! It seems to me that using The "Hammer" Websphere product ...

Escape the quotes in the parmfile and I bet it works.
parm1=\"fdsafasfd sadfsfasfd\"

I don't think it is dsjob, rather the mechanism you are using to extract the parms from your parmfile. The following works just fine on AIX UNIX;

dsjob -run -param parm1="tim robinson" todd test

This may be way off... Can you verify the EXACT string that is being passed to the SQL. I'm guessing that when your UNIX parmfile parse functionality does the command substitution from the parmfile to the dsjob command line, it stops at the first space. Consequently, you are passing dsjob -run ... -...

You mean what is step 5? That's easy. Copy and paste the results of step 3 and paste it into a UNIX file. Yes, it would be oh so sweet to do a save as and FTP it to UNIX but baby steps, baby steps. I'm concerned with generating it correctly. Actually saving it as a schema file is a bell and whistle ...

1. Open any Table Definition.
2. Go to the Layout tab.
3. Select the Parallel radio button.
4. Still Clueless?

Here's the run-time error;

main_program: Fatal Error: Caught ORCHESTRATE exception in main program: APT_ParseError: In field "Alloc_Unit_ID": In property list: Expected property name, value, or "}", got: ",", line 6

Ah, the light bulb goes off. When I say Table Definition I was referring to a DataStage object called a Table Definition. These things do not need to be spawned from a dbms object, they can be native to DataStage. This particular one comes from the column tab from a Copy stage. It results from savin...

Thank you Mr. Guru. You might take a peek at my questions as they don't appear to correlate to your reply. I apologize if I didn't state my problem succintly. I have a schema file, generated from a table definition, that is incorrect. DataStage is failing when attempting to use it with column propag...

I am using Column Propagation because I have 19 output Sequential files, all defined exactly the same way. I would like to maintain a single schema file and use it with column propagation. Works great except DS cannot generate a reliable schema from a table definition. This is extremely aggravating....

I'm guessing there are two ways to set this property for the field. Both are from the columns tab. Highlight an entire row in the columns grid and double click. This will bring you to the properties screen. Set Null handling from there. OR Right click on the REL_KEY field select properties. Select t...

Most code is sensitive about NULLS. A NULL means "NOTHING". You cannot compare something to nothing therefore an IF will not work on a NULL value in a field. This is why we have NULL Processing functions.

PX is very persnickety when it comes to datatypes and null handling. It looks like RELA_KEY has been defined as a fixed width field but the null handling for this field is not of the same fixed width. It is of width 0. Check either the properties for this particular field or the format tab of the Or...