DSXchange

I do not know anything about the "dslockd" process. Well, it seems you know enough about the deadlock daemon to know that the actual process name is 'dslockd'. :wink: When on it would run 'all the time', mostly sleeping but waking up every 'x' (a configurable parameter) to check for locks...

Nope, it is testing the contents not the data type specifically. Give it a shot.

An exact search for "The modify operator has a binding for the non-existent output field" returned 20 matches, see if any of them help.

Ah... missed the -dom that was already there... sheesh.

Should be. In the 7.x world it was all documented in the manual for the Director client, not sure where it might have ended up in the 8.x world.

It's not an error, it's an informational message saying the function you attempted to use is not supported in your release. Are you thinking it should be? Is it documented as an active feature in your release?

I believe that you'll need to add the -d domain_name option to your command line.

There really isn't any burning need to revert it back is there, as noted all that accessing a project via VC does is add those APM hashed files to the project directory. It's is still also a 'regular' repository you could continue to use like normal. Nothing else is changed as far as I know, so yes ...

The istool utility can only export and import files of its own making, i.e. from the command line and they would have their own extension. Exports from the client would need to be imported using the same mechanism (the client) and would have a .dsx extension. Now, technically the istool produces .ds...

Make sure you understand what that does, jobs typically need to be designed with multi-instance capabilities in mind. There's more to it than simply flipping the switch.

You need to "source" your dsenv file to properly set the environment variables you need, that and you may need to include login credentials on the command line. To source the file:

What's your business rule?

Not sure what you need. You should be able to just add them to the Sequence itself and then tell each Job Activity stage to pass/use those parameters.

They only have an "extension" if they are multi-instance, that's when you add the "dot" and the Invocation Id to the name. Otherwise, it's just the name.

You submit the jobs ones by one, not 'the project'. Or just run the Sequence job if it handles all of the jobs itself.