Is there any way to do this in 3.6 please? (OpenInsight Specific)
At 26 FEB 1998 02:20:42PM Dave Pociu wrote:
Lately I have been bugging the people in tech support about using COPY_TABLE to copy a table between two volumes that have the same volume label. (I get that by doing the development on a different machine and then trying to copy the new tables into the corresponding directory in the network copy).
I have the feeling that the new COPYTBL form in the Knowledgebase is a direct result of my nagging (but I'm not sure :) )
Either way, the COPY_TABLE command now fails with FS404 when the destination volume name is the same as one of the volumes already attached.
My request is this: Can we tweak that command in 3.6 so that it ignores the destination volume name and does the copy anyway (maybe add another flag to COPY_TABLE ) .
This would save me from the error-prone process that I'm using now (copy to a temp directory first, go to network copy, attach that, copy in from there) , and will save me quite a bit of time on deploying new or updated tables.
Thanks guys
At 26 FEB 1998 03:10PM Ilona Iguana wrote:
Wouldn't it be easier just to rename the volume? Sure there are indexing issues to contend with, but would solve the problem. Any code put in there to avoid the fully qualified file name (REAL_NAME*ACCOUNT*VOLUME) has the potential of reeking havoc with the system in biblical proportions.
You could try the NAME_VOLUME SSP :)
Ilona Iguana
At 26 FEB 1998 04:38PM Dave Pociu wrote:
Ah, the dreaded indexing problems (along with the biblical stuff ). That's exactly why I DO NOT want to mess with a renaming of the volumes if at all possible.
Help me out in this one :) !! I know how to do it the hard way, why not make it easy though ?
Am I asking for too much? Would you guys (RTI) at least consider it?
Thanks
At 26 FEB 1998 06:42PM Cameron Revelation wrote:
Dave,
The volume label uniqueness check is there for a reason … it prevents two references from being made to the same file. To change the volume label, attach the REVMEDIA table for the volume, edit the REVMEDIA record (field 1 is the label) and then detach/re-attach the volume.
Cameron Purdy
Revelation Software
At 27 FEB 1998 09:00AM Kimberly Kowari wrote:
Changing REVMEDIA might allow for the attachment, but it will not allow indexing to work. If Mr. Pociu is copying records from one indexed file to another and he does not recreate the indexing control records, all writes to both files will create index transactions in the 'original' file.
The iguana makes a good point, for a reptile. Use NAME_VOLUME
NAME_VOLUME VolumeName, NewMediaName
I have some documents here in my pouch. I placed them against the screen and hit the copy button but I'm not sure why they're not sending.
Kim Kowari