Knowing associated TECH-FILE location

Generally when you create a library, you don't compile in the tech file, but attach or reference the technology library (which has the tech file compiled already to produce the tech.db database).

Attaching just means that your library uses the other library for its technology data. 

Referencing means that your library has its own technology database which incrementally tops up the technology database from the referenced library. This allows extensions of layers, constraint groups etc in your own library. A facility known as ITDB (Incremental Technology Database).

When you compile a technology database from an ASCII technology file, it doesn't retain the path that was used to compile it.

Regards,

Andrew.

 Thnaks Andrew, for your reply.

I am little bit confused with the answers. so let me put the things in step by step manner :- 

  When we create a NEW library through Cadence (IC5141) CIW -> xxx_PDK
-> Library -> Create Pull Down , it gives -options as - a) Compile a
New Tech File b) Attach to an Existing Tech File.

In previous PDK-case, we choose option b).

Existing Tech file, means there is a single file somewhere in the PDK library path.

I want to know where that Tech File exists ?

When you attach to an existing tech file,  you're really attaching to the tech file in an existing library. You don't need to know where the tech file actually is. You pick the main technology library that's in the PDK - which should be documented. Provided that library is available via your cds.lib, you can pick it.

The technology database (in IC5141) will be called techfile.cds (in IC61X it's called tech.db) and is a binary database. It lives at the root of a library.

When you attach to a tech file, you'll only be offered the choice of libraries that contain binary technology databases within that library.

Regards,

Andrew.