DSXchange

That's not "hard-coding". What is your target - a database? The format will probably need to be slightly different if that's the case.

How is this a "workaround"? That is the answer. And searching the forums here for dsjob will reveal complete examples of job launching scripts. Granted, mostly UNIX scripts but not impossible to convert to batch files if you don't have anything like the MKS Toolkit installed. Plus you'll either nee...

Great - then please mark your post as Resolved using the button at the top of the screen.

Actually, the comment was probably a request for the Moderator to move the post. We can't move our own posts but there's no need to duplicate everything as eventually Roy will find some time to put things where they belong.

First bit of advice will be that we don't diagnose errors from the "APT_CombinedOperatorController" so you'll need to disable that and run the job again to find out where the error is actually coming from.

The pdf manual shows how to generate unique numbers if that's what you need to do.

You could use it after job but more typical would be in a Routine Activity stage in a Sequence job. Really depends on what you want to do with the information. Build a generic routine that takes Job Name, Stage Name and Link Name as arguments and then call the function inside the routine. The result...

Column Generator? Based on your question, did you mean the Row Generator stage?

I've seem to recall FTP causing problems like this with fixed-width files. When the last column(s) in the record have spaces in them, the transfer tends to strip them. Don't recall the solution, perhaps a binary rather than an ascii transfer? Assuming this is being transferred from elsewhere to you,...

You would need an index over the update keys for it to have any kind of efficiency. Without it, every update becomes a full table scan, and only after that fails to find a record to update is the insert done. And without any unique constraint on the table, when inserts are done first they are all su...

While you may very well be able to merge the three streams (but don't cross them!) in the job before writing out a single link, there are no properties in the Sequential stage that will allow what you are doing otherwise to work.

We're veering off topic here, but read only code can be compiled as can code in Protected projects. Neither would allow changes to be made, however. We're singing from the same hymn book, I'm just saying that simply having the source available in production isn't necessarily a problem. But certainly...

It would help if we knew the database in question.

We have source and executables in Production so that we can "see" the production code/design there but all of the jobs are Read Only so there's no worries about any changes being made there.

In other words, it's neither a bug nor a problem, just an artifact of how View Data presents the data to you.