DSXchange

If the file is well-formed, and the only issue is that of figuring out if the file has too many or too few columns, there is one trick which can be used (Server Jobs Only): In the columns tab of a sequential file in server jobs there is a column titled "Incomplete columns". Set this value ...

In another transformer stage x-1S(Detail),

Please read as

In another transformer stage x-1S(Summary),

one possible solution: Calculate/Pass the detail data and your calculated summary in 2 different streams. In a transformer stage x-1D(Detail), Consolidate every detail column but Col1 into the required output format and pass it a a single Column(RowData longvarchar(4096)). Add a generated integer Co...

As from what I read from searches in the same forum (Try "SQL Server datetime" with the all words match option), If you get the format right, SQl server will parse the varchar and convert it to the right datetime format. No need of a Stored Procedure. This issue has been taken care of many...

Hi Via, I think the issue now is the base database table. The data type TimeStamp is (Possibly??) incorrect for what I think You want to achieve. Refer link: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_da-db_7msw.asp timestamp A database-wide unique number that gets u...

Carter, The reason I added 1899 and not 1900 is because: 105001 is 01 Jan 2005 Now to use the defined logic: 1899+105=2004. Create date 31- Dec- 2004 Add 1(001) day to 31 Dec 2004 Which is 1-Jan-2005 If we use 1900, we have to create the date as 1-Jan-(1900+cyy) subtract 1 day from our final additio...

Hi Via, That is a Trademark (well almost) JD Edwards date format. Dont have DSEE so cant give actual code: Step 1 is to seperate the year from the source: * for String input take everything from pos 1 to len-3; convert to Integer * for Integer divide by 1000 and use AsInteger() Add 1899 to either re...

One possible issue may be this line in the transformer output:

0006: extern string stripinvalidchars(string string,string termstring,string replace);

Try to rename the argument name from "string to something else("inpstr" perhaps).

HTH
Amey Vaidya

Hi Titto, The simplest solution would be to wrap a Job Sequence around your existing Job. The sequence can do the following: 1. Job Activity Executes the Job. Output trigger is unconditional to second stage 2. Second stage is a nested condition stage with one output trigger with the following condit...

When importing Objects into a new project, if the overwrite without Query check box is unchecked and an object with the same name already exists, you will be prompted if datastage is to overwrite the existing object with the new imported object. If the checkbox is checked, there will be no prompt an...

When I view data through oracle stage I am seeing bad data and when I run the job also it is giving fatal error. Just checking; Is the above- mentioned error the same as in your initial post: ##F TFDE 000030 10:06:29(002) <Org1,0> Fatal Error: APT_Decimal::assignFromString: invalid format for the s...

Hi Kumar, First of all, I apologize for the delay in responding. two points i've faced before with sequential files and transformers. 1. Setting null values in sequential files for fixed field length data types is very painful. Especially if those files are to be used as staging areas between jobs. ...

There is another way to set up aborts that I'd discovered by accident in 7.5. I dont have access to DataStage at the moment but heres how: When previewing data either from a Sequential file or database source, there is an option to view the generated OSH. In that OSH, you will find an abort operatot...

1. What is the Data source? is it a sequential file? 2. What stage type throws the warnings? is is a transformer? (Recommend pasting a subset of the log.) 3. what is the difference between the dev env and the testig env WRT the source data. Is there a possibility that the dev env may not have had n...

Hi kumar_s, Check if both projects have the same setting for Enable Runtime Column Propogation for Parallel Jobs. I suspect that this may have been switched off in the Dev Project and on in the testing project. If this is true, recompiling jobs in the testing project would have removed all modify op...