DSXchange

Hi, From version 8.5, if I'm not mistaken, there is actually a package utility enabling the packaging and deploying of repository objects into different projects and servers. I can't recall the exact name of this utility but I did use it a few times. I'll try to get the name (if no one posts it befo...

I agree craig, but I dont think if all goes well anyone will mark this post as having a workaround.

I bet the time of the scheduals is derived from the need to sequence them one after the other.
By the way, if your using any schedualer (organization wide) you can also define those dependancies there.
IHTH,

Hi,
Did you run the sftp from command line on the DS server machine?

It seems you have a workaround
Marking topic as such...

Note that having a size of over 2GB means you must have created the file with a 64Bit setting (unless your entire instance was built with 64bit), this limit is foreach of your data and overflow files seperatly. So eliminating the overflow might cause your data file to go over the limit and crash you...

Thanks for sharing!
I took the liberty of marking the topic resolved.

Hi,
This might be user related and/or parameter related.

Are you using the same user in the actual run and the one you log in with when viewing from the designer?

What is the difference in parameter values when the job runs and when you try to view the table from the designer?

IHTH,

Hi, I was wondering, was the read only attribute the product of importing to a protected project? Might be worth while to protect and unprotect (via Administrator client) turn your jobs to editable? (just thinking, cause I don't have DS V7 available) P.S. If you want to be able to edit your jobs you...

Hi, Generally the most significant , performance wise, impact is the number of groups built as you create the file. The number og groups required depends on the number of records your about to process divided by the number of rows that fits in one group (the hashed file is built from) the size of ea...

Any one knows the solution ?!
(even a year later as it may be)
I think it is not ok to open a topic and then simply say its resolved!
How about something regarding the solution

Hi All, I came across a strange behaviour. A server routine that calls dsexecute to performs: more +n filea > fileb works fine when executed from the test routine option but when used from a sequence job both via routine stage or exec command stage the output file is empty. parameters are same for t...

NLS was mentioned in the original post, so I had to ask. Is your job still hanging, or is it able to process around 8144 characters at a time, no problem? The 8144 characte limit was experianced in the routine test environment, the actual data tested had less then 8,000 charaters. I ended up keepin...

Are you talking about viewing the statistics on the links in the designer?
you should be able to see the performance via the monitor in the director.

Wel I got the Fold out but still no change :cry: Guess this wraps the thread... I did get to a limit on testing the input string via the routine test option and hit the old 8192 string length limit notification, actual was 8180 anf actual length with no data problems was around 8144 characters IHTH ...