DSXchange

Interesting... good luck with that.

Seriously, let us know what you come up with.

You can also take advantage of the User Status area each job has to pass a value to a downstream job without the intervening routine.

What about creating the routine as taking a fixed number of parameters and then putting a series of transforms over the top of it that take your 'variable number of arguments'. The transform could default / hard code the 'unused' parameters in that case.

Yes, it affects all projects on the server when done in the dsenv. For us, that's exactly what we needed. I have no idea how to set something like that different from project to project, perhaps someone else does...

What is the datatype in Oracle? Is it a DATE field or actually one of the newer TIMESTAMP types? If so, which exact type?

Sounds like you should do something to test for the existance of the file first, rather than let the job error out if it doesn't. Would the WaitForFile stage help you in this regard? What about a routine to test for the file - one that doesn't error if it doesn't exist, merely reports that fact - an...

Sorry - I edited the link at the last minute and hacked off one too many bits.

It's fixed now!

Methinks Arnd doth replyeth to the wrong post.

Search works. And it's Excel.

I have already known about the function alternative but am trying to avoid it as writing code in ds basic makes dificult the maintenance. I'd rethink that assertation as 'writing code in ds basic' is part and parcel of working with Server jobs. Well structured and well documented code will greatly ...

Ignoring your thread title and answering the question as asked would lead me to say - create a 'current month and year' routine that returns that value. Call it using a Routine Activity stage, the output of which can be easily passed in as a parameter value to any downstream jobs.

The solution is pretty straight forward - put an NLS_LANG entry in your dsenv file that matches your source / target systems and you should be fine.

That's what I would have thought...

You actually want a Range lookup, not a conditional one. Search the forum for the various discussions on that topic.

If it is externally pathed then yes, do so at the O/S level. Account based ones? I don't believe so... but there may be a RENAME.FILE command lurking out there somewhere for all I know.