DSXchange

Per the online DS documentation, it looks as if we are to set the 'Preserve Trailing Blanks' setting to 'No' in the Oracle Connector stage, then trailing blanks in a column would be removed. http://pic.dhe.ibm.com/infocenter/iisinfsv/v9r1/index.jsp?topic=%2Fcom.ibm.swg.im.iis.conn.oracon.usage.doc%2...

I owe an apology to Franklin. I was mistaken. The UNIX Newline comes after the last filled position, so the remaining fields seem to be truncated. I tried what you specified above (delimiter "None", quotes "None", Final Delimiter = "End") and I got the Input buffer over...

FranklinE wrote:I'm just a bit confused by your description. Are the "blank" fields actually filled with spaces to the length shown, are they null fields, or do they have only one space where more are expected?

Franklin, they are filled with spaces to the length shown.

We are having issues reading in Sequential Files with blank values in the final columns. For example, lets say I have a Sequential File with 5 columns: Col_1 CHAR(5) Col_2 CHAR(5) Col_3 CHAR(1) Col_4 CHAR(2) Col_5 CHAR(6) If my record has values in Col_1, Col_2, and Col_3, but Col_4 and Col_5 are em...

Thanks. I've asked our DBA to look at this again, and will post the results.

I think so. The unique key is defined as the combination of CCYYS, SNAPSHOT, SRI, CLASS_UNIQUE, and PE_OCCURRENCE. As it happens, CLASS_UNIQUE is not really needed - the combination of the other four columns is still unique. I've tried it with and without 'AND CLASS_UNIQUE = :CLASS_UNIQUE' included ...

Absolutely. In the 'Properties' tab of the Oracle Connector stage, the write mode is set to PL/SQL and the following PL/SQL block is executed: declare change_code nchar(1); ccyys int(5); snapshot nvarchar2(3); sri int(9); class_unique nvarchar2(5); pe_occurrence nchar(3); dept_abbr nvarchar2(3); cou...

I have a very simple job which reads a dataset of changes with eight columns plus a change code, and uses a PL_SQL CASE statement to apply the changes using an Oracle connector. To process UPDATEs to about 230,000 records, it's taking about 3 1/2 hours. By contrast, a very similar job that actually ...

Looking at the Invocation ID input in Director it appears as if this is a hardcoded value. When you say to type in the parameter reference, we do have to create multiple instance via hardcoding, as the running of the sequence won't dynamically generate an Invocation ID. Say, append the job name to t...

We are using value files to create default values for testing.

Thanks, Ray!

I've got a sequence that collects pre-row counts on a table prior to loading a table. This sequence has been set up execute whatever parallel job the scheduler sends it. In the Job Properties of this PreCount job, I've checked 'Allow Multiple Instance'. What I'm hoping to see in Director is the resu...

Great suggestion, Andy, and we do this with server info parameters.

Here I'm looking more at a series of generic parameter defaults. So say, JOB_A will have PARAM01 as a year of 2013, but JOB_B may have PARAM01 as some code like D12.

Thanks!

The value files look like a good approach. As I add new value files, will I need to re-compile all of the jobs that use the parameter set whether they use the new value file or not? Also, to get these values from the value files to show up, how are they assigned within a job? It looks like they're a...

We've got 8 generic parameters in a parameter set and each DS job has its own, unique values it may or may not use, is it possible to set up a parameter in the Job Properties that can serve as a default value for one of the generic 8 parameters in the parameter set? I'm wondering something like if i...

Thanks, all, we've got our one sequencer now executing our DS jobs whether they have parameters or not.

I added the 8 parameters to a parameter set that all of our jobs use, made sure they were being referenced correctly (thanks for the tip, Andy!), and all is good.