DSXchange

Been asked before, here for example. A job activity stage simply starts a job, which will typically take a second or two. So in your example, a job activity will start job 2, then once job 2 has started, a job activity will start job 3. Now it's been awhile but that's not how I remember it, nor what...

As Eric said the answer is yes but the gory details depend on the hashed file type - specifically if they were created as "pathed" hashed files or are associated with an "account" which would generally mean live in a project. For the former, you can simply migrate them. The latte...

Of course, wasn't implying that was the full syntax. I shall... rephrase. Revisionist history FTW!

FWIW, that's exactly the situation where I've seen that error before back in the 7.x world.

That format is for the incoming string, not the expected output so should not include the colons.

Or it is simply not finding the 'parameter name' it is looking for so returning nothing. Seems to me they are passing it a 'ParName' to look for on the left side of the name/value pairs in a parameter file and when found it returns the 'ParValue', the right side. Not found - return nothing. Not look...

Right, there's no "coding" involved. You're just telling it how to launch any other command line application from that menu.

Use the -ljobs option of the dsjob command, then iterate through the list that generates.

Those "double letters" in your format tell it the format is fixed, i.e. always two digits. Start by trying single letters. I don't think it will solve all your problems but give it a shot and let us know.

You are not alone, my friend.

As noted, you can identify the user by simply looking in the log. Of course at some point the logs will purge and that information will be gone. I was looking for more specifics as to what you need to do with it - 'track' is a far too generic term. Do you need to store it somewhere, in say something...

There's no reason to use BBCode for stuff like bold or italics and then have the "Disable BBCode in this post" option checked. #JustSayin

Fixed.

U wrote:Or is it sufficient to provide this for the setup command itself?

That was certainly the case in the old days. Did exactly that many times.

Define 'not working'. Times two.

It means you cannot see the complete message because you are not a Premium user.