DSXchange

You should prefer at the very very least to use a separate schema; I would prefer a separate database, though this can be on one of your existing instances (provided the Oracle version is 10g). A script is provided amongst the Information Server installation material for creating the metadata reposi...

Add the correct number of hours, which varies through the course of a year as the switch to daylight saving time is on different dates in PST and Greenwich.

Your next task, then, is to mark this thread as Resolved using the green button at the top of the page.

Read ALL of that other thread. Generally the key is not specified at all in the record schema (you can use a comment if you must).

Take a look at the data that the job is trying to read - the message gives the hex equivalent of non-printing characters. {c3 f0 e8 ef ef - eb f3 f7 f8 e5 20 ef f0 e5 e4 f3 ef f0 e5 e4 e8 f2 fc} beginning from position 7 in the line. There's neither a null nor a -1 there. You have some more investig...

Typically you will get a warning logged and fewer rows processed than you expected. Is that insufficient advice? The warning can be intercepted by the controlling sequence and an email sent.

Where is your log - common repository or local repository? (What are the values of RTLogging and ORLogging in the DSParams file of your project?)

As documented. All this information is on IBM website, and may change over time so it's better to direct you there rather than lock anything in here. Also, the total disk space is a function of the volume of data you will be processing, about which we have no information.

Verify that all parameter values are passed correctly to the job by inspecting both the sequence log (job run requested event) and the job log (job starting event).

Send email to membershipdirector@dsxchange.com with a copy to editor@dsxchange.com. You can find contact details for other modalities at www.ondemandstrategies.com or www.dsxchange.net.

I think you missed Ernie's point. DataStage does obey the OS rules, particularly permissions. So it suffices to protect your "no storage" locations with operating system permissions and, probably, rigorous developer management practices.

Why?

Would you use a hammer to tighten a screw?

Use the right tool for the job.

Resist stupid requirements!

Hai.

Only subsequently-created jobs.

Within the job properties of each job is a check box "Enable Runtime Column Propagation for new links" on the General tab.

Read the error message. Then know that "" is NOT the same as null. Fix that.