Search found 41 matches

by vivekreddy
Thu Jan 18, 2007 12:12 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Microseconds extraction
Replies: 10
Views: 2053

I dont have access to PX now. I am expecting that there should be a option if you tweak the data type defaults of that field, which I already said. BTW: Why do you need to convert it into Time data type, why can you keep as varchar as is. Since many version including some earliar version of databas...
by vivekreddy
Wed Jan 17, 2007 4:37 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: insert a db2 sequence generated value
Replies: 1
Views: 1511

Re: insert a db2 sequence generated value

Hi all :) , I have to insert a db2 sequence generated value into a field for a table(say ABC),the sequence name is IA.INDIV_EN_ID_SEQ INSERT INTO #TgtDB#.ABC (IDENTITY_ID, INDIVIDUAL_ENTITY_ID) VALUES (ORCHESTRATE.IDENTITY_ID, NEXTVAL FOR IA.INDIV_EN_ID_SEQ) But while doing this i am getting the fo...
by vivekreddy
Tue Jan 16, 2007 11:37 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Problem witht the join stage
Replies: 10
Views: 2450

Sort the data in both input sets to the join stage(s) on the join key(s) before sending it to the join stage(s). And before sorting the respective data sets, clear the partitioning applied in the immediately preceding stage (s). I had the same problem, and this worked for me. Please let me know whet...
by vivekreddy
Tue Jan 16, 2007 10:35 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Microseconds extraction
Replies: 10
Views: 2053

Iam sorry I dont know where I got this from :oops: . You should be looking at the format of the data type of that field with the other method. Really no problem. You must be working with DataStage so much that you must have forgotten more than what you can remember. At least that way, I was compell...
by vivekreddy
Tue Jan 16, 2007 5:52 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Microseconds extraction
Replies: 10
Views: 2053

Try mentioning the extension of micro seconds in the datatype of that field using field properties. Converting seconds into micro second is by multiplying by 1000000 and adding with the microsecond part of the exisiting values. Converting minute into micro second would be 60*1000000 and so on... Al...
by vivekreddy
Tue Jan 16, 2007 5:36 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Microseconds extraction
Replies: 10
Views: 2053

You dont need to concatenate with ":" and then mention the format as %HH:%MI... You can straight away give %hh%nn%ss.xxxxx. The other method is convert all hh, nn, ss that you found using svToCharAccessID)[7,2]:":":(svToCharAccessID)[9,2],Sad(svToCharAccessID)[11,2],(svToCharAcc...
by vivekreddy
Tue Jan 16, 2007 2:54 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Microseconds extraction
Replies: 10
Views: 2053

What is the syntax you use to convert? Try %HH%NN%SS.xxxxxx. Alternatively you can convert it into microseconds, and can use time_from_microseconds() function. I use the syntax for conversion as follows. This step is preceded by converting the BIGINT field value to character value. StringToTime(((s...
by vivekreddy
Tue Jan 16, 2007 1:54 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Microseconds extraction
Replies: 10
Views: 2053

Microseconds extraction

Hi. I have a BIGINT field of length 18 and containing data in format YYMMDDHHNNSSssssss, basically timestamp. I need to split this field into two fields, one a date field YY-MM-DD, and time field HH:NN:SS.ssssss. I am able to generate the date part properly by first converting the number to characte...
by vivekreddy
Tue Jan 16, 2007 12:54 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Join stage not recognising match
Replies: 5
Views: 1460

What about partitioned on the join key(s)? ... Thanks for your assistance. Partitioning on the join keys worked. But I am not able to understand as to why it is necessary or rather why my not having partitioned the input data set(s) on the join key(s) was causing a problem. Could you please explain...
by vivekreddy
Tue Jan 16, 2007 12:27 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Join stage not recognising match
Replies: 5
Views: 1460

ray.wurlod wrote:Welcome aboard. :D

Before Join stage will work properly both its inputs much be identically partitioned and sorted on the join key(s). Is this the case in your job? ...
Hi.

The inputs are sorted on the join key(s), but the problem still persists.
by vivekreddy
Mon Jan 15, 2007 10:59 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Join stage not recognising match
Replies: 5
Views: 1460

Join stage not recognising match

I have a parallel job wherein I am expected to check whether a record in source data contains valid data. The format of the record is as follows: ACCESSID BIGINT 18 NOT NULL USERID VARCHAR 6 NOT NULL PURPOSEID SMALLINT 5 NOT NULL CLIENTID INTEGER 10 NOT NULL MASTERID INTEGER 10 NOT NULL Now, I have ...