DSXchange

Multiple writes to the same file is not allowed by the OS. You will get misaligned data. If this were a server job and you had two links going in then, theoratically, there will be roundrobin process of sending records and in both the sequential file stages the option should be append. I guess you c...

Create a job that does count(*) and loads to a file. This will be your first job activity, the second icon will be of execute command stage where you will read this file using type. Now depending on the count, branch your stream accordingly.

I doubt you can parametrize the delimiter. Process it in unix using awk. Dont do a global replace as the delimiter might appear in quoted data and it will be replaced as well.

Kill is the last resort. I dont think the OP is out of options. Many ways of doing it and a mere search will reveal all the different ways of doing it besides kill.

ady wrote:Ray , How can we do it in basic transformer without a routine ?

Use OCONV/ICONV with MCP format to convert all nonprintable characters to a dot. Then use the above convert statement to extract only alphabets and numers.

Itsi bitsi change in Nick's timestamp format. Nick, if i may

2B, I wouldn't even say it's a workaround, it's just using EE as it should be used. Just being polite I guess. If the OP really feels the dire need to use a hashed file then no problem in using a server job to do it. Its just that, in order to achieve the degree of parallism EE provides, needs to b...

You dont have to open a connection for each record. A connection remains open and all processing can be done within that one connection. Anywho, I gave you my 2 cents and along with others, provided plausible workarounds. Its your call.

Depending upon the file size and query complexity, it might be horribly slow. A better, viable workaround would be to load your flatfiles to tables and run your sql on them.

If one of the 10 jobs fail, the enterprise scheduler wont go to the 11th step as the 11th job will be dependent upon the successful completion of all 10. Say 9 complete successfully and the 10th one fails. You take two days to fix it and restart from point of failure, the enterprise scheduler whatev...

Dataset, lookup fileset are all viable options.
This logic that you are talking about, can't it be done at the database level. This eradicates the need to create a snapshot of the table.

Change your datatype to int or varchar from char. Because char is very particular about the length. If you specify 11 then the return has to be exactly 11 characters long.

Kris is right. I said "Pass only the records which are found" which means that you need a NOT of NOTFOUND constraint.

Depends upon your inhouse standards. If there is an enterprise scheduler, go for it.

Thats completely upto you and how much time window is allowed for a file to appear by your requirements.