DSXchange

Because there's a space in the filename. If that is legitimate, you'll need to quote the filename so it doesn't think there are two files to delete.

Post the values of those two parameters. For the last question, google as I suggested for something like "dos check file empty".

So, a problem similar to this? Column names in the output file use the associated field name from the job, so your issue is only an issue if there are spaces in the column name. Otherwise, as noted, simply checking the option noted should suffice, regardless of type since sequential files have no da...

For that upgrade - 7.5.1 to 7.5.3 - you can easily do it "in place" where your existing installation gets upgraded, no export/import needed. Of course, backups are always a good idea!

You certainly could and then run it after job. Deleting is easy, UNIX or DOS, however a DOS size check is a little goofy from what I recall. A quick google would turn up the syntax.

Write a script / batch file to do the equivalent - test the size of the file and then delete it if it is 'empty'.

It would help if you specify what you meant by "open".

Please don't post a question multiple times or in multiple forums. If anyone wants to continue to help with this, here is the original thread:

viewtopic.php?p=387009

This one is done.

You can't, a job will always create the file.

That's why I tend to Preview what I'm writing several times, especially if I get... distracted. Too bad this forum doesn't do like I've seen others do and throw up a warning that another reply has been posted while you were in the middle of yours, it can be helpful.

One possibility - write out a single record to a file with your column names, then in another operation append your data to that file. That or create two files and cat them together to build the final file. That first option can even be accomplished 'before job' by echoing the values to your target ...

In other words, exactly what I posted.

No problem. Did want to mention you should look at an auto-generated upsert for the stage sometime to see why your custom one didn't work. The metadata needs to line up between the two sql statements, meaning all columns must be mentioned in both and that was something you couldn't do.

An exact search for "39202" returned 50 matches, perhaps some of them have useful information in them.

In a Server job, I would use a hashed file for this with a transformer both reading from and writing to the same hashed file with one key field and one data field. Make sure the lookup is not cached for read or write and your input data is sorted properly if the actor name order matters. Lookup with...