DSXchange

Exactly. And you can write your own job control code or nowadays build a looping Sequence job. It's pretty much just a matter of running the job and then figuring out how much time is left in your slice to sleep for. And always (always) build yourself a way to interrupt the process so it can be shut...

Immediately?

You have to define what should happen if your job takes more than 15 minutes to run. And I would (and have) build a wrapper job that gets scheduled in once a day. It runs the sub-job every 15 minutes, sleeps between iterations and automagically handles an overrun. It should also poll for interrupts...

-4 is BADVALUE, your syntax is wrong. DSJ.LOGANY is valid for DSGetNewestLogId, your function requires a specific EventId and pulls a single entry from the log.

I suppose you could find that, yes, but not who cleared it. Use the standard 'DSGet' functions for the logs and search for 'Log cleared by user' as one of the events.

Reporting Tool not equal Usage Analysis. Two different things.

You could also find posts from Chuck Smith and get his free utility that would help in this effort. The URL is www.anotheritco.com from what I recall.

Have no idea how you are planning on using this hashed file, but try making all three fields as Keys to minimize duplicate removal.

gateleys wrote:

ray.wurlod wrote:What happens if you call the transform function from the before/after subroutine?

How do you expect him to call a function from before/aftter subroutine??

By including a Function Declaration - DEFFUN - in the B/A routine.

Oh, and wait... hold on, where is that... ah.

Alethesnake wrote:This second one puzzles me because if I write only:

Code: Select all

SELECT office_code, office_surrogate_code FROM office_pointer WHERE office_code = ?; 

It runs well.

When you have two question marks, do you have two columns marked as Key fields as well?

Slide the Columns display over to the right and change the Contains Terminators value for that column to 'Yes'.

How would you 'fix' this if you were doing this outside of DataStage? Do you have any alternate way to supply the password from the command line?

From a sequential file line termination standpoint? Yes. A UNIX Server will happily read and write "DOS" files without issue. I would *assume* a Windows Server could do the same with "UNIX" files but I've never had any hands-on time with DataStage on Windows to try.

It's an option in the XML Output stage - check the help for Trigger Column. Every time the value in the trigger column changes, it switched to a new file. ... The problem with this solution, you have to create a key beforehand and do the counting that way. Also you are not going to have much of a c...

[sigh]

Seeing as how you can't monitor a Sequence job, it just means that it is running.

I'm sorry, but how could something like that possibly be "urgent"? [sigh] I'll leave the lecture to others. Why not contact IBM Sales? They'd be more than happy to give you the sales pitch and list all of the glorious features of the 8.x release.