absolute path of links

hi, I am using informix 9.3 on HP UX 11i. When the chunks are created, the links point to actual files on the volume groups. The onstat -d displays only the links but not the absolute path where the actual files reside. 1. Does the server any where store this info. 2. If any one changes the link to another file is it possible to know to which file the link was previously pointing to. bye.

Hi. See below: ----- Original Message ----- From: Parameshwar.... <pcdudyala@yahoo.com> At: 8/22 10:07 hi, I am using informix 9.3 on HP UX 11i. When the chunks are created, the links point to actual files on the volume groups. The onstat -d displays only the links but not the absolute path where the actual files reside. 1. Does the server any where store this info. No. IDS never directly follows the links, it just 'open()'s the links themselves. Indeed, this is the main advantage of using links for chunk paths - that you can redirect the links to another physical device and perform a restore if a disk device hard crashes. 2. If any one changes the link to another file is it possible to know to which file the link was previously pointing to. No, keep your own inventory. If you want, take a look at my package utils_ak. It contains a wrapper over onspaces, aspaces, that maintains a database of chunks, following the links, for multiple instances on a machine. When you use aspaces to add chunks it checks the database for overlaps between instances using different link names. It comes with a database print utility and has an option to initialize the database from the existing chunks (this uses onstat and was written for 5.xx & 7.xx so you may have to modify the awk scripts to use it with 9.xx/10.xx since the format of the onstat -d output has changed a couple of times in 9 and again for 10. Art S. Kagel bye.