upscol & syscolval
Hi I have a database with a lot of new tables, and setting up COMMENTS entries via upscol is tedious in the extreme. I thought it would be possible to simply INSERT rows into syscolval but that didn't seem to work for me. Additionally, we are using a connection type that isn't supported by upscol. Am I missing a trick? The engine is IDS 7.31.FD9, upscol is 7.20.UE1.
On Oct 3, 7:27 am, Cats <ramwa...@uk2.net> wrote: > Hi > > I have a database with a lot of new tables, and setting up COMMENTS > entries via upscol is tedious in the extreme. I thought it would be > possible to simply INSERT rows into syscolval but that didn't seem to > work for me. > > Additionally, we are using a connection type that isn't supported by > upscol. > > Am I missing a trick? The engine is IDS 7.31.FD9, upscol is 7.20.UE1. There is no standard system catalog table syscolval and no upscol utility that's part of any IDS release of which I'm aware, certainly not in 7.31. This must be some site or vendor data dictionary table/ utility. Art S. Kagel
Cats wrote: > I have a database with a lot of new tables, and setting up COMMENTS > entries via upscol is tedious in the extreme. I thought it would be > possible to simply INSERT rows into syscolval but that didn't seem to > work for me. > > Additionally, we are using a connection type that isn't supported by > upscol. > > Am I missing a trick? The engine is IDS 7.31.FD9, upscol is 7.20.UE1. It's been a long while since I heard of someone using upscol, which is part of I4GL and I4GL-RDS, and stores information in the syscolval and syscolatt tables (which are regular tables with irregular names in the sense that playing with sys as a prefix is dangerous). In terms of content, there shouldn't be anything magical about it as long as the metadata to identify table and column is correct. Given the warnings in the manual about the use of upscol with MODE ANSI databases, it seems likely to use table name and column name (without owner), and I see no reason why (nor a mechanism how) a set of upscol data accurately loaded could be unused. I note that I4GL 7.20 is venerable - circa 1998 would be my guess. The current version is 7.32. You don't identify the connection type that isn't supported or the platforms, but the basic rule here is "if it (the connection method) wasn't supported when I4GL 7.20 was released, it hasn't been added to the software since - not in the 7.20 version, that is". -- Jonathan Leffler #include <disclaimer.h> Email: jleffler@earthlink.net, jleffler@us.ibm.com Guardian of DBD::Informix v2007.0914 -- http://dbi.perl.org/ publictimestamp.org/ptb/PTB-1444 ripemd320 2007-10-03 00:00:07 F55226E58D1BB99B0DE6FD717802316885080C3D3DC55A4B8256142135BD8999686E6F 0A359ED6F
On Oct 3, 1:38 pm, Jonathan Leffler <jleff...@earthlink.net> wrote: > Cats wrote: > > I have a database with a lot of new tables, and setting up COMMENTS > > entries via upscol is tedious in the extreme. I thought it would be > > possible to simply INSERT rows into syscolval but that didn't seem to > > work for me. > > > Additionally, we are using a connection type that isn't supported by > > upscol. > > > Am I missing a trick? The engine is IDS 7.31.FD9, upscol is 7.20.UE1. > > It's been a long while since I heard of someone using upscol, which is > part of I4GL and I4GL-RDS, and stores information in the syscolval and > syscolatt tables (which are regular tables with irregular names in the > sense that playing with sys as a prefix is dangerous). > > In terms of content, there shouldn't be anything magical about it as > long as the metadata to identify table and column is correct. Given the > warnings in the manual about the use of upscol with MODE ANSI databases, > it seems likely to use table name and column name (without owner), and I > see no reason why (nor a mechanism how) a set of upscol data accurately > loaded could be unused. > > I note that I4GL 7.20 is venerable - circa 1998 would be my guess. The > current version is 7.32. You don't identify the connection type that > isn't supported or the platforms, but the basic rule here is "if it (the > connection method) wasn't supported when I4GL 7.20 was released, it > hasn't been added to the software since - not in the 7.20 version, that is". Thanks Jonathan. I realise the upscol is venerable/antique/out of the ark-ware, but that's the 4GL version for the live system so until they move that to Genero we are stuck with what we have. When they do that I *might* get the latest version of I4GL on their box. The unsupported connection type is ontlitcp - we used to use shared memory but Genero V2 doesn't support that... Went round in circles because of problems with ISQL, ended up upgrading that and IDS and leaving the I4GL along. Platform is Solaris 8 on a Fujitsu SPARC box. We don't use MODE ANSI databases, so that shouldn't be a problem. So, I'll move onto 4Js to find out why I had problems. Thanks, and thanks especially for the quick reply.