Interesting. I added this to support something else entirely, but you could actually use AT ACCOUNT like:
CREATE.INDEX MYFILE INDEXNAME AT /some/other/path I know the documentation SAYS that you have to have an entry in UV.ACCOUNT, but i implemented it to be pretty flexible. As long as /some/other/path resolves to a Type1 or Type19 directory you can do this. You REALLY do want a FULL path where your indexes exist, because if you have remote connections that use the file, it has to resolve where indexes are. _________________________________________________________ "I reject your reality and substitute my own" - Adam Savage Glenn M. Herbert - Connectivity Development Engineer Information Integration Solutions, IBM Software Group 50 Washington Street Westboro, MA 01581 508-599-7281 direct "Womack, Adrian" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 07/22/2005 04:31 AM Please respond to u2-users To <u2-users@listserver.u2ug.org> cc Subject RE: [U2] [UV] Create Secondary Indices with Relative Paths in file header Craig, Initially I thought - "wow, this is a good idea". But after trying it out, I realise it entirely depends on the files existing in the same account as you're accessing them. The majority of our data files (and hence their indices) exist in other directories (not necessarily accounts) - so the relative AK pointers don't work. It was a good idea though. Adrian -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig Bennett Sent: Friday, 22 July 2005 3:00 PM To: u2-users@listserver.u2ug.org Subject: [U2] [UV] Create Secondary Indices with Relative Paths in file header Hi All, apologies if you have already thought of this, but if you haven't you might find it useful. When UV creates secondary indices, it creates a directory in the account directory called I_file which holds the indices associated with file. The absolute path to this file is then stored in the file header. This causes problems if you copy the file using the os as the file points to the original index not to the copied index (assuming you copied the file and I_file). However CREATE.INDEX allows you to supply AT ACCOUNT to create the index for a file in an account other than the current account. To have file refer to I_file using a relative path (ie ./I_file instead of /account/I_file) you can do the following: 1. Create an entry in UV.ACCOUNT called CURRENT.ACCOUNT with a . in attribute 11. If you logto CURRENT.ACCOUNT you stay exactly where you are since you perform "LOGTO .". 2. Create your indices specifying AT CURRENT.ACCOUNT. The file headers will then contain ./I_file rather than /account/I_file. Now the file and I_file can be copied to other locations and the index will not break. Craig ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ DISCLAIMER: Disclaimer. This e-mail is private and confidential. If you are not the intended recipient, please advise us by return e-mail immediately, and delete the e-mail and any attachments without using or disclosing the contents in any way. The views expressed in this e-mail are those of the author, and do not represent those of this company unless this is clearly indicated. You should scan this e-mail and any attachments for viruses. This company accepts no liability for any direct or indirect damage or loss resulting from the use of any attachments to this e-mail. ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
