DSXchange

Search the forum for DSU - off the top of my head you'll need (at the very least) a DEFFUN statement and the DSU prefix. And you may need to refer to it in all UPPER CASE in the DEFFUN as that's how they are catalogued.

Anywho, a search of the forums for DSU and/or DEFFUN should reveal all.

Again, just to be clear - under what exact circumstances are you expecting the Exception Handler to jump into the fray? Without anything special, it will catch problems with the Sequence job itself - jobs not compiled, non-existent parameters, that kind of stuff - but not something like a job failur...

Under what circumstances are you expecting it to execute? Granted, most of the time you would use the two together as that greatly simplifies your error handling, but there's no requirement they be used together. Make sure you read the Help on the stage to understand the functionality it brings to t...

Seems to me you would be best served by contacting Support for this.

Not an area I've ventured much into, to be honest. The '.B' extension would imply BASIC runtime code AFAIK. 'DSU' means something User supplied. 'BCI' is the BASIC Call Interface, so probably something to get around the licensing restrictions? Or to leverage non-branded ODBC drivers? [shrug] Just gu...

What about it? Are we moving now from Server to PX jobs?

Don't see how it would help as it can't make metadata up out of whole cloth.

Sure.

Keep in mind, however, that the way it works changed significantly over the earlier 7.x releases. Which exact version are you running?

Perhaps it's only an 'upgrade' issue, and wouldn't affect someone starting with 8.x? Wondering...

I think that the limit of 2Gb of Hashed files was "removed" in the lastest versions. No. How I can change the hash file to 64-bit in DS Designer? You can't, at least not in the Hashed File stage itself. I must do the CREATE.FILE command in universe? Or from your O/S, and with the -64BIT option. Fro...

If you have an Oracle client installed and everything configured, why would you use ODBC over OCI?

kaps wrote:Yes. I do. I had them as my second option. I got more respect for you guys ! :D

That's cool... but nothing beats someone sitting right there, putting greasy fingerprints on your screen as they point out all kinds of pertinent bits of information.

Your SA / Sys Admin. Got one there you can chat with?

The parameter name you passed on the command line as paramname in your example cannot be correct or it would not have given you that error. Whatever name you've assigned to the parameter in the job - name, not prompt or default value - is what you should be using here. And no, the command line will ...

Welcome aboard! :D

That error means the parameter name you've supplied does not exist in the job. Make sure you've spelled it correctly - case and all. And you've got the right job!

It's in the linked posts, but to bring it here:


stage_label meaning the name of the Job Activity stage to check.