DSXchange

So... you're just making these sizes up?

Kumar has already answered your question as asked. Ray has attempted to bring some sanity to it.

Make sure you come back and ask questions if there's something in there you don't understand...

Unfortunately there is no system backup because against advice no backups were taken as it was deemed quicker to perform reinstall than get a system restore. I think the decision was based on the perceived service provided by the company that looks after the servers (no names but they also make sau...

Find it in the Manager and double-click on it. The Long Description and all 'source' code will be revealed.

In other words, talk to your SAs and/or Network guys.

From doing a quick test the difference between a hashed file using the account and one using dir path is an additional line Directory "/mydir/" It should be parameterized and I assume the parameter won't exist in any of the jobs yet. Keep that in mind as a need for this procedure. Hmmm... a rouge p...

I haven't had to do this, but if I did this is the approach I would take: Export a single job that uses an account based hashed file. Change one hashed file stage to be pathed with your parameter of choice. Export the changed job. Examine the differences. From that, determine the feasibility and lev...

And you really can't just concatenate the files together for processing all at once in a single file? That is so much easier to setup.

Unfortunately, I don't have the time to lay it all out right now. Perhaps tonight. Perhaps someone else would be willing to?

I'm sorry but I don't follow your question. Are you asking about the Folder stage, or the User Variables Activity stage or something else? Please explain the approach you decided to try and what exactly it is you are trying to accomplish. Concatenation? That is easy to setup. Looping in a Sequence j...

Either it is being monitored or it is in fact still running. You need to determine which.

Hi "soma_june",

You can find it here, two posts up from the last post.

Welcome! Known 'parasite' bug with Version Control. The job exists - it is just no longer in the catorgory it should be and, when you find and open it, you'll find the contents are another job entirely. Open it from VC to verify the presense of the parasite. Find out where it ended up with the follo...

A hex editor or perhaps 'od' - an Octal Dump of the file. There should be a 'show hex' switch if you're more comfortable with that. Tell us what you find.

In UAT an ODBC stage is giving an error as follows (I can see from the logs that the same error was generated before migration as well but the problem is that for the same job it is not giving the error on production which is currently running on 7.1.) That would imply a difference in the offending...

And for goodness sakes, if you are going to keep going back and forth on this, post some actual data samples you are seeing. Made up stuff like "I am seeing 1234567891234.00" doesn't help anyone help properly.