DSXchange

Variables defined only in the Administrator only exist when a job runs, so not something you can test for as you are trying to do.

Hashed file lookups are the Heart and Soul of the Server product. Direct database lookups are anathema.

But they do have their uses and so are not completely shunned.

You can't simply change the keys defined in a lookup without consequence. Running to completion doesn't necessarily mean running correctly. There's too many variables to make a blanket statement here, it would really depend (amongst other things) on the sql in the lookup stage - if it is generated u...

True, they are. Sorry. I was confused there for a moment and thinking about other routines. Keep the advise more as general advise not to make changes to existing routines unless you own them and are aware of the impact the change will have on every job that uses them. Otherwise, you're just asking ...

As I noted earlier, I counsel against the use of NOTFOUND with db stages. YMMV. And the constraint, while 'unusual' in my book, should work fine - unless the sql used in the stage has been monkeyed with.

They all can edited unless someone specfically goes and makes them RO.

All that means is whatever environment variable you are echoing is not set. Period.

Jeez, one or the other of your multiple personalities work a thread! Not both.

Don't even think about editing that routine - create a copy and edit that version if you want to try that. Anyone already using it will thank you... actually, they won't kill you. (I feel like I may have just saved a life today)

Something is wrong, as you should be perfectly able to view any kind of Oracle data. Report it as a bug, let us know the resolution.

I'd also be curious what is 'not working' about it other than the fact that it can't find the hashed file path you are trying to construct.

Log the output of the DSExecute. What does it show, what is actually being returned? What do you see when you test it and double-click on the result cell?

Course not, that's not what it is for. <smack>

Use that when you need it to pick up from where it left off last time. Use one of the ROWNUM system variables:

@INROWNUM
@OUTROWNUM

Read the online help available for them so you understand the difference.

Write up a FAQ.

Actually, what 'env' returns from your command line and what is available inside a running job are two different things as the environments are different. Yes, even when run 'by the same user'. Create a simple job that just executes 'env' and captures the result to the log, it will become more clear.

Right, no worries. :D One thing to note is I personally only use the NOTFOUND link variables with hashed file lookups. I have found them very unreliable when used with database stages, Oracle in particular - I guess they weren't written to properly support them - so I never use them there. [shrug] S...