DSXchange

All this time I thought I was safe taking nightly backups/exports of all DS projects on all servers.... Only to realize that readonly objects (at least transforms for sure) aren't being exported via the DSAutoExport.bat script which uses dscmdexport.exe. Am I missing something like an undocumented f...

and then someone will want this functionality for jobs that also update rows (type II dims come to mind)... make sure you know where all the stones in the water are in order to keep up the impression of walking on water. Doable, but now you are probably getting into adding extra columns in your targ...

oh, you mean just like it says in the manual?

Anyone know where the job parameter default values are stored (those set by Director).

More importantly, how to access them... either a hack or API or command line?

Thanks,
Craig

Just to humor us, can you have your seq file stage write to the file /dev/null? And then are you still getting 3500 rps? If so, then your disk is the "problem". If greater than 3500 rps, then the problem is elsewhere.

I couldn't quite determine if the poster indicates the LOG is cleared (since RT_LOG is mentioned) or the STATUS cleared. I was assuming the log was cleared and that CLEAR STATUS FILE hadn't been done (yet).

This works in 7.x, should work in 8.x...

Have you tried this specifically in Director?
Highlight the job, click Job -> Clear Status File - Yes

Should remove the running status. Should only be used as your last option.

UNIX usually requires double quotes around the file name if it contains wildcards or other stuff for an expression. I've tried double and single quotes, and no quotes, with same error response. The -print is a default... you leave it off and it's implied. And I tried including it and same result. Ba...

That'd work, but I have a whole boat load of other UNIX commands chained to this one for sizing and sorting... Going to try putting the UNIX commands in a script, then execute the script. Wish me luck. Also, you need to update you bill rate. The was worth more than 2 cents. ;-) And get back to work....

you're right on both accounts... it is a ^ and it doesn't help.

I can't even reproduce that error message from the command line. If I could format a command to give me the error then I could maybe start there.

Tried the UNIX instead of NT... DS says "that command is not supported on this platform" Also did a "which find" command from the routine and it is using/finding the MKS find command. And the env var PATH, as seen from DS within the routine is "Path=C:\PROGRA~1\MKSTOO~1\bin;...

I have a DS routine that works just great on Linux/Unix. Trying to convert to work on an NT server. We have installed MKS Toolkit on the the NT server. The routine issues Unix commands and then does stuff with RT_LOG files... The very first command is giving me fits. The command is "find . -nam...

I've finally got to a machine to bring up the CFF stage and the settings. First of all, how did you acquire the data? I'm assuming it is from an IBM mainframe, right? Did you get it via FTP? Was the FTP performed in ASCII or BINARY mode? If in ASCII mode, your packed/binary data is no good anymore a...

Sorry to keep bringing up the CFF stage, but if you have it configured right and the meta data truely
reflects your data then the CFF stage works.

Else fall back to using the transform/routine mr. Hulett refers to. Their use is pretty straight forward.

Have you tried using the CFF stage yet?