Default Path for Files

patonp · Post by **patonp** » Thu Jan 26, 2006 2:51 pm

In our development environment, we're finding that some developers are occassionally unit testing jobs in which they've forgotten to specify a filename for sequential files. As a result, sequential files are automatically assigned their inbound linknames and placed in the project directory.

Although we're obviously encouraging developers to carefully check their code prior to execution, we're also wondering whether we could modify the default directory used when a path is not specified. Is it possible to specify a default directory that differs from the project directory? Any opinions as to whether this is a desirable approach?

Thanks for your help!

Peter

chulett · Post by **chulett** » Thu Jan 26, 2006 3:00 pm

I'm not aware of any mechanism to do so. The 'current working directory' of any job is the Project that it is running in so relative pathed files would be relative from there.

Best to fully path any files and use job parameters to specify those paths, in my opinion.

ray.wurlod · Post by **ray.wurlod** » Thu Jan 26, 2006 4:13 pm

There is no such mechanism. Your developers will need to adopt a more disciplined approach (which includes cleaning up any such files created in the project directory). A standard set of parameters helps; parameters for source directory, rejects directory, work directory and so on.

kduke · Post by **kduke** » Thu Jan 26, 2006 8:38 pm

I posted SQL recently which will allow you to find these jobs quickly. You could QA them before they are promoted to production.

chulett · Post by **chulett** » Thu Jan 26, 2006 9:25 pm

Linky?

kduke · Post by **kduke** » Fri Jan 27, 2006 6:52 am

What?

chulett · Post by **chulett** » Fri Jan 27, 2006 6:57 am

Sorry Mr Kim. Can you post a link to the SQL that you mentioned so us poor slubs don't have to go hunt it down?

kduke · Post by **kduke** » Fri Jan 27, 2006 7:04 am

I forgot search is a advanced concept.

viewtopic.php?t=96760

I think the path is included in the file name. You would need to look for slashes (either \ or / based on the OS). The absence of slashes says the file is in the project directory. The # should exist in a parameterized version. It should be easy to check for these before promoting the job to a production environment. If you have several DS developers then assign one to promote jobs and QA them. Make sure all ETL standards are met before promoting the job.

chulett · Post by **chulett** » Fri Jan 27, 2006 7:14 am

Some days, yes. Especially with a prolific poster like yourself, gives one alot of hits to wade through. Just trying to help out our fellow forum dwellers.

Ah yes... that post, I remember it well. Thanks.

kduke · Post by **kduke** » Fri Jan 27, 2006 11:46 pm

Mr. Craig.