For anyone that is interested, from the wiki
The following program should be substituted for HS.UPDATE.FILEINFO 0001: CALL *HS.FILEINFO( RESULT, "REFRESH", 1) 0002: PRINT RESULT 0003: END This gives you a verbose step by step of what is happening. It turns out that the files are processed in alphabetical order but only those with defined associations were being reported to the screen. This also pinpointed the problem which turned out to be a 'bad' Q pointer in the VOC. I occasionally do the following to quickly have a Q pointer point to a test file. 0001: Q 0002: ACCOUNT 0003: TESTFILE ... 000x: ORIGINALFILE When I'm done I restore the original filename. In many years at this game I have never seen this cause any problems but it looks like the extra lines/data cause the routine to barf for whatever reason - I haven't found any documentation saying that anything beyond the 1st 3 lines is significant for Q pointers. Removing the extra lines cleared things up and we are all happy again. > -----Original Message----- > From: [email protected] [mailto:owner-u2- > [email protected]] On Behalf Of Anthony W. Youngman > Sent: February 27, 2009 12:07 PM > To: [email protected] > Subject: Re: [U2] ODBC setup error > > In message <[email protected]>, > u2ug <[email protected]> writes > >We have an account setup to allow odbc access to specific files. > >We added access to a new file and ran HS.UPDATE.FILEINFO which > processed > >a few files but then aborted the session with that old standard : > > > > Abnormal termination of UniVerse > > Fault type is 11. Layer type is Unknown. > > > >The files that were processed are accessible via odbc but no others. > > > >I tried removing all data files references from the VOC , so there > >shouldn't be any files to update and it still gave me this error. > >I also tried disabling and re-enabling file access via HS.ADMIN but > the > >same result - we get the same error when the enable tries to run the > >HS.UPDATE.FILEINFO command. > > Quite likely. What version of UV are you on? > > >I am assuming that it is hitting a bad file and blowing up, but I > don't > >know what that file might be as the order that files are processed > seems > >to be pretty random. > > Try SELECT VOC WITH TYPE EQ "F" and see if that's the order it's > processing them in (I think it probably is). > > > >This is a major issue. > >Can anybody shed some light on this ? > > > Look on the UniVerse page on PickWiki. There's a page about setting up > ODBC - it's pretty out-of-date because it's based on 9.6, but it may > well give you some clues - especially about how to get > HS.UPDATE.FILEINFO into verbose mode, which stands a good chance of > telling you which file is blowing up. > > Cheers, > Wol > -- > Anthony W. Youngman <[email protected]> > 'Yings, yow graley yin! Suz ae rikt dheu,' said the blue man, taking > the > thimble. 'What *is* he?' said Magrat. 'They're gnomes,' said Nanny. The > man > lowered the thimble. 'Pictsies!' Carpe Jugulum, Terry Pratchett 1998 > Visit the MaVerick web-site - <http://www.maverick-dbms.org> Open > Source Pick > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
