DSXchange

You've got things in the right place as it is trying to do what you asked. And I wasn't specific enough in my previous reply - that "dir /b" output is an example of what the stage needs, not the actual command itself to be used there. Sorry. Try simply putting "D:/Employee*.txt" ...

Try passing in full credentials - server, domain, user and password.

Welcome. Can you please edit your first post and let us know your Release, Job Type and OS? Thanks.

Yes. You'll need to switch from Delimiter to Delimiter String to use more than a single character.

Now on to your question... First tell us if you have these formats in different fields, meaning you know what format will be coming where, or if they are all mixed into a single source field. The former is pretty straight-forward while the latter will require you to identify the proper format to use...

:!: Split from this topic. When you have a problem or question, please start a new post rather than jumping on the end of someone else's conversation. That way we know what product and version you have and you have full control over the destiny of the post since you 'own' it. If you really feel that...

Always good to help people out, but best to stick to posting in threads that are current... this one is two years old and I'm sure they figured out what they needed to do some time ago.

You mean statistics from the previous run (or runs I assume) not the previous day... and you can't. Not through this mechanism, that is, as it is strictly for the 'most recent' run of the job. If you need them, you should be capturing and archiving them on an on-going basis. Since I assume you're no...

How are you 'reading' the XML files - how exactly is your job designed? You should be doing something to get the filenames to process and having the XML Input stage do the actual reading using the 'URL/File Path' option which should also mean you already have the filename. Just pass it through using...

This can also be caused by the 'Automatically handle' compilation option in the Sequence. The built-in help explains how to override that "anything other than 0 is a failure" behaviour.

So... even without one?

Ah... the word you are looking for is 'Category', that must be what you are trying to dig out of the repository with your query. Sure, you can run those same commands from a script, it will actually be the same way (using TCL / UV) but you could parameterize and script it. Check this post for a disc...

Clarify for us exactly what you mean by "the path of a job". They all live in their respective projects, are you unsure where those are? What are you planning to use this "path" for - answering that may lead us to providing you with a better / more proper solution.

This just gets more confusing as we go deeper down the rabbit hole.

What makes you think your Sequence job is not passing the parameters properly to any jobs it runs? Are you using the Job Activity stage to run the jobs or some other mechanism?