DSXchange

Why is "always running" a problem?

You use the Information Server Console to control jobs that use Information Services Director, including any possible need to stop and start "always running" jobs.

And you use "end of wave" behaviour to identify units of work.

1. No. 2. Not in a Sequencer, but yes in a Sequence. My preferred formula in an expression in a Sequence is to use the @DATE and @TIME system variables, but you could use Date() and Time() functions instead. Assuming that you don't want fractional seconds, a suitable formulation is Oconv(@DATE,"...

I'm not really sure what you're asking here. Yes it's possible to load data into SAP using IDOCs, but there's not really any such thing as "SAP tables" - SAP sits atop a database. Your SAP licence explicitly prohibits your accessing these tables directly.

Execute your command and pipe the result through tr to convert the line terminators into commas. Optionally pipe through sed or awk to remove the empty "line" at the end, or use a user variable to strip this.

Yes, but one row can fail more than one constraint. For example, if the metadata specified all columns to be NOT NULL but the data contained three NULL values, then this would count as three errors, three reasons for rejection.

Make sure that the /.dshome has the correct value set. It might also be work setting environment variables DSHOME and, possibly, APT_ORCHHOME.

Is your Array size greater than 1?

Can any one row fail for more than one reason?

What does the after-job subroutine do with the result? Simply have the sequence read it from there. Ideally the subroutine will write the result into the job's User Status area.

Only one that I can imagine - reading a null (null field value) for Col1 or Col3 where there is no default value defined.

That message really only informs you that a previous error has caused DataStage to clean up. You can safely ignore the "attempting to cleanup" message - address the real error.

No, that's because your first argument is not a job handle. Error code -1 translates as DSJE.BADHANDLE.

Use Director client. Disable display of categories. Sort by start time. From the menu choose Print (and then, if required, check Print To File).

Looks like a problem connecting you your repository database. Check that the database is running, and the owner user (probably xmeta) has a password that has not expired and, for preference, does not expire.

Most examples of renice default to the current process. If you use ExecUV as the before-job subroutine you can use the "UniVerse" command CHAP DOWN. (CHAP = CHAnge Priority)

In short, you don't. Only the DataStage engine connects to Oracle. Your client connects to the DataStage engine. If you want to talk directly to Oracle from your Windows machine, simply install and configure Oracle client software and tools for Windows right there. But this will not involve DataStag...