DSXchange

For grins, can you post the actual error message you are seeing?

They're not 'passed' but but they are inherited because they are all running under one environment - the one established by the Sequence. And if your jobs rely on certain values being set, don't assume they are already set in the environment, explicity set them in your jobs. That way a Master Sequen...

You already know the secret sauce: make sure the scheduling user has the PATH to dsjob in their profile. Sounds llike your scheduler isn't using bash so I would suggest you create a .profile with just the bits you need for this and see if that helps.

'Related' doesn't cut it, you need to start your own topic rather than jump on the end of someone else's resolved topic.

Split and linked.

ps. I added the

What have you tried? In the Parallel Sequential File stage, it can as simple as using the metadata for the detail records and the header/footer will automagically be rejected. Of course, that depends on how generic your metadata is. Can you post any FD information, what do your header/detail/footer ...

I know exactly what you mean, and it only looked like it worked. Sometimes also known as 'mostly works'. Had several run-ins with support over the issue... they were very insistent - don't do it. Just say no.

You could pass a parameter value of A','B (since you hard-coded the outer quotes) and then set the new magic environment variable that tells DataStage to not strip out the quotes. Sorry, don't remember the name, just the fact that it exists.

Me, personally, I would never build anything like that into a job. I prefer a separate process that runs after all jobs have completed that queries them for things like their ending timestamp, links counts, etc and outputs all of that to a flat file. Then another process can simply pick up that file...

You can view it in UNIX, you'd just need to enclose the filename (spaces and all) in single quotes to do so. In order to remove the spaces, you'd need something to retrieve the current timestamp before the job starts and then use a routine to remove everything but the numbers. A Sequence job could b...

Are you sure you're ok with that? From what I recall, the output from that macro has spaces in it, which can confuse things when used raw like that in a filename. The colons can also cause issues... but if it works for you like that, then we good.

The transformer would be 'too soon' as the job would still be running. Technically, the job is still running when it hits the 'After Job' section but you could get it there using the API - look at the documentation for DSGetJobInfo() and one of the InfoType values should get you the ending timestamp...

You don't need a script for that, just the 'move' command does a rename in UNIX. At its most basic: mv <old_name> <new_name> You'd have to be more specific as to exactly how you want it renamed to get more specific help. You could also pass in the 'timestamp' to use as a Job Parameter and then inclu...

I asked if you saw the 'truncation' outside of DataStage, not what 'View Data' shows.