DSXchange

manjunath.hukkeri wrote:Now in the need of hours part am changing the delimit from 10 to 19 to have the format as DD-MM-YYYY HH24:MI:SS

Hence my comment.

AFAIK, both sets of functionality should be there "out of the box" - for jobs to access web services and to expose a job as a service. The "RTI Input" and "RTU Output" stages are used for that, but for all I know they have new names as well. Maybe Ernie will wander in here and add some Words of Wisd...

YYYY-MM-DD HH24:MI:SS

Row out of Sequence means the Sort order you asserted in the stage does not match the sort order of the incoming data. You are aware that with those settings you are telling the stage how the incoming data is sorted, not asking it to "sort" it in that order, yes? If your incoming data is not sorted...

Must be, but hard for me to say what. Make sure your key values match exactly, case and length and are trimmed for trailing spaces (if applicable).

Semi-colons.

Dang, where's a WABAC machine when you need one?

No, it won't, not to speak of. Never mind that something of this nature is the only way to solve your "issue" and a sequential file 'staging table' is cheap and fast... unless you've got a crap disk subsystem, I suppose.

Try it.

Neither of these concerns are problems. Include the InvocationID in the name of the sequential file, just like you've probably done with the hashed files. And you write to the sequential file exactly the same information that you want to write to the hashed file. The end result will be the same reg...

I am having an issue, even if the job aborts, the output link from a Hashed File Stage opens, and processing certain (100) rows. I dont want to process, if the Job aborts, because i am doing some business caluclations in that link. The output from the Hashed File should fire, only if all the rows a...

I'm currently filling the DBA's role. I don't think doing a drop and recreate index is a viable option. This requires me to constantly maintain stored procedures to keep up to date with any new indexes I or others may create and/or drop because it's not used. Not really. Properly created processes ...

Ask IBM to provide you the physical media, it's free. Or a tar file with the bits you want.

Does your source stage support Transaction Isolation? Try changing it to Read-only to avoid locking the source records.

ArndW wrote:The simple method is to use ICONV() and OCONV() to convert a display date

Fixed that for ya.

They changed the name yet again for the 8.x releases. From what I recall seeing here and talking to Ernie, it is now known as WISD and is included with the base product.