DSXchange

Since you've marked the post as such, what is your 'workaround'? So, you stopped it but your issue is the fact that the Director doesn't reflect that? The kill command should be avoided as much as possible, especially a "kill -9". You need to know that when you kill a phantom process, the fact that ...

Sorry, but the problem I have with 'silver platter' answers like this is there typically is no learning involved. I suggested the search because then one would get to read discussions on what exactly was happening and why the solution as provided, was provided. Then the brain juices start flowing an...

So do you always write only one record to the output file? Or do you process all of the incoming data, write some/all to the output and then always append one more record to the file? More of a curiosity than anything. I'd suggest you write an 'after job' routine. Pass it in the Stage Name of the Tr...

You're right, an empty source file will process zero records in the job and then nothing will be written to the target file. What is special about this 'one record' that needs to be written when you have no input? Describe it, please.

Doesn't matter, I've used both mechanisms without issue and I never knew how many files there will be. Concatenate / Loop based on a wildcard pattern.

Concatenate them together, then load. Or build a Sequence job to Loop through them one at a time, assuming you are on at lease a 7.5.x release.

I'd suggest you search the pdf docs for $PROJDEF as the bits that explain this are a little scattered around. The Administrator Guide and Designer Guide primarily cover it.

DSguru2B wrote:I have giving you a link in my previous post.

Oh really? Not in this thread.

Sorry, misunderstood what needed the quotes. So, coldes is passed into the routine as Arg1? With the double-quotes inside? And then you reassign inside the routine? coldes = Arg1 If you've done something like that, then you need to get the variable out of the string so the value gets properly substi...

Try:


So that the double-quotes are just part of the command string when built. Or there is something like a 'dquote' function, I believe.

Nothing is wrong, per se. You've got a version that doesn't allow PX jobs to run on Windows - it needs to be either 7.5x2 or 8.x for your jobs to be runable on Windows.

Yes, that's exactly what I mean.

Aren't you using Job Parameters for this? If so, why aren't those values stored in some sort of central location that all jobs leverage, like parameter files or tables? That would make the change a '2 second' change. You could play the export / edit /import game to do this all in one big whack but ...

Seems to me you have at least two choices. What people typically 'schedule' is a script that wrappers the dsjob command. If you want to build that functionality into the script itself, that would be one answer that is not AutoSys specific. Otherwise, I would think it would be trivial to just tell th...

Do you know the maximum occurances?