DSXchange

Not sure if this helps but we had a very recent conversation on basically this same topic, primarily for PX:

http://www.dsxchange.com/viewtopic.php?t=120384

Welcome! :D What you need is a "User Defined" or custom routine, reusable code that encapsulates business logic. Create and test it in the Manager, then leverage it in the field derivations of your jobs. If your rules change, simply recode and redeploy the routine and all jobs that use it will autom...

Well, the answer to your second question is your syntax is wrong. Post what you are using.

Ah... so that's what that was for.

Nothing wrong with your previous macro use so something in the implementation of UserVariables v. Execute Command I guess.

Well, that's certainly intuitive.

When it magically has 78 columns the next day, are the first 60 the same as the previous day?

For an actual DOS command, all I am aware of is time /t and then you'd need to parse out the hour. If we're talking PX with the MKSToolkit then the UNIX commands can be used.

You used the 'following code' where?

Welcome. :D

What are your exact db NLS settings? And what is DataStage using?

All - this has been reposted in the proper forum and should be responded to there. Thanks.

In other words, you'd need to persist it... file, USERSTATUS, etc.

No, not directly in the manner you are thinking. They are ephemeral, transient things which do not survive the tragic heat death of their specific process.

We know... patience, my friend, patience.

And yes, I would wager this is an NLS issue. Do you NLS enabled? What are your NLS settings, project / job / database? Why do you keep saying "Oracle table/flat file" - which is it? In other words, what *is* your source, an Oracle table or a flat file?

Or just refer to the answer to your previous date question here, the answer is the same sans the "minus one" part.

Sure.