DSXchange

Change your date to ISO format YYYY-MM-DD, pass thru a Sort stage and sort descending on site, date, then write to hash file. Last row into hash file with just site as key will be the oldest date for that site.

Recompiling the base job removes all instances, so the status files would thus be removed with the instance. It's also very fast.

By "read" you mean one read operation than stop, as opposed to using a constraint to only allow the first row to pass the first transformer? There's nothing outside of a filter using the "head -n1 yourfile" statement.

Did you happen to look at this sites home page and see the training being offered?

In the Start menu under the Ascential folder is the entire DS BASIC manual.

Script based, using cut, grep, and wc can accomplish what you need. Using DataStage you could just check the columns as you process and write out rows that qualify for loading, and that don't send to an exceptions file. You could check the exceptions file when finished and based on finding rows elec...

From the DSINCLUDE file in your project, the JobControl.h record: LIST.ITEM DSINCLUDE 11:06:25am 23 Feb 2006 PAGE 28 353 $IfNDef DSJobStartTimestamp 354 $Define DSJobStartTimestamp DSGetJobInfo(DSJ.ME, DSJ.JOBSTARTTIMESTAMP) The macro is a call to the DSGetJobInfo function from within the jo...

What's not working? Are you getting more or less rows than expected? What's your issue? You do realize that a lexicographic comparison works left to right, so that your format of MM/DD/YYYY doesn't work? Try using YYYY-MM-DD and you might be surprised. Better yet, use to_date on your "01/01/2004" in...

Welcome aboard!

chulett wrote:Actually, you can double-click on any log message. The Event Detail dialogue box that pops up has an area for User - as in the user that logged the message, i.e. ran the job.

Double brilliant! :D I didn't look up, just down at the text messages.

kris007 wrote:If you double click the event detail for Environment variable settings in your job log in the director you should be able to see the username. If thats what you are looking for??


-Kris

Brilliant!!! :D

None supported that I know. The userid is not tracked in the log files, nor is it available by double-clicking the job in Director.

Spelling, permissions, it's got to be one of those.

I'm having a head scratching moment because we've had to code around this "limitation" under 8i and 9i databases. I searched the 9i manuals to see where this was discussed, so I'd be very surprised to learn a lot of different folks at different customer sites all had the same mistake. I'd love to be...

Oracle 9 or 10? From your post you're using 10, but I'm sure 8 and 9 have this restriction. I somewhat stand corrected.