DSXchange

The entire contents of the file into a CLOB field? Yerk. You are going to have sizing problems but I'd try feeding the OCI stage from a Folder. That will automatically bring in the file contents as one large LongVarChar field.

As long as the '1 for = 0' is an 'OK (Conditional)' trigger and not something custom, I think you'll be fine with that.

Sorry, I meant 'Validate'. From the 'Run' dialogue box.

kollurianu wrote:i want know, if a job design is compiled does that imply all the user defined datastage routines called by job exist.

No, that would be a runtime check. You might want to investigate the 'Verify' option.

And? What have you tried? What is the 'problem' your subject mentions?

It's still "handling" it because it doesn't think you are. Try adding a third 'Otherwise' link so it does... or just let it handle it. Why not return negative values to indicate a problem? Returning five nines for that seems to me to be a bad idea. YMMV. The rule for '0 as valid' for Routines is onl...

Sgt Pepper taught the band to play.

Oh wait, that was only 20 years ago today, sorry.

Great! Please mark your topic as Resolved then.

Wait... if you get a 'path not found' error then it can't even find your script - so questions about 'clubs' inside it are moot at this point. What exactly are you putting in the User-Defined SQL tab when you select the 'File' update action? I don't recall that option needing any kind of extra keyw...

Try putting 'sh' or 'ksh' as the command and then your complete command with parameterized path in the Parameters area.

I have no clue, was just explaining the behaviour you are seeing. As Arnd asked, is this an RCP issue?

If you mark the constraint as a 'Reject Row' you'll automatically get an 'alert' (read 'warning') logged with the total row count rejected if anything goes down it. As noted, the answer is heavily dependant on what kind of 'alert' you want.

Joshy, they're not talking about a job parameter but rather the credentials used to log into DataStage...

What do the docs show are the supported compiler(s)?

We use the -file option and I don't recall that being an issue for us.