DSXchange

OK... the detail file is being overwritten in the process, wasn't sure if that was ok or if it would start stepping on itself when the file is quite large - that and how 'safe' it might be if there are any issues, seems like you'll end up with a trashed file and have to start all the way over. I gue...

We all did the same thing and it is SSL encrypted during the transmission, just not "on the screen". Just make sure no-one is peeping over your shoulder.

No such thing in a Server job, I'm afraid.

Okay... and? Any particular reason you posted all that? What does this have to do with the QualityStage product?

New with 425 and 6 years of posts. Must be a new Mandyli.

That was already considered but there is a concern about the size of the detail file so the OP was looking into... alternatives, techniques that don't require duplicating the data, even temporarily.

How can this be done in a transformer by stage variable It can't be. You can only bind in job parameters and thus values passed into the job. You may, however, be able to take your value and build the fully fleshed out sql into a file and then set the stage that you are looking to bind that into to...

Yah, that was a tangential Server question that I really should have qualified as such to avoid any unwitting cross-contamination.

There you go.

As noted, I could have overcome the problem that way as well except for the fact that we were dealing with strings much larger than 8k. Honestly, though, I don't recall what we ended up doing as this was many months and a client ago. I believe "they" ended up doing something to deliver it ...

You could probably make it work that way... set the UserStatus value in your job control and the run the Sequence. You'll need to add a 'pre-step' in the Sequence to then go fetch that UserStatus value from the job control and then it could then be automagically passed from that step to the actual J...

Sounds like you just need to declare it as a Job Parameter in the Sequence job and then have the "job control" set it appropriately before running the Sequence job. Search here or in the docs for the DSSetParam() function. Well... unless your job control isn't something you wrote in DataSt...

Have you actually tried it yet? Concerned you may end up with two header records.

Seems like it, I recall them being in "msh" files in each job's folder... under the "SC" directory, perhaps?

5. Nope.