RE: [U2] Unidata logging of BASIC Runtime errors
The minimum modulo is not that bad. The current mod is 529447, and the minimum 482029. Primary File Head (dat001): modulo --> 122069 hashtype > 96 version -> 3 blksiz --> 15 (16384) idxinf --> 10 bproof --> 1 multi-over file -> 0 rm --> 255 prt_at --> 192 nullv --> 129 beg_modulo --> 0 file_limit --> 20 Overflow File Head (over001): modulo --> 0 (not used) hashtype > 0 (not used) block size --> 0 (1024) (not used) next_block --> 0 (block 0) block_count -> 0 max_blk_cnt -> 4077 file_logical_end > -2070724608 current_modulo --> 529447 min_modulo --> 482029 split_factor > 95 merge_factor > 40 grp_fre_blk_cnt -> 5 file_limit --> 20 total_free_blk --> 0 p_file_cnt --> 5 o_file_cnt --> 1 Free Block List: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Robert DunnMiller Sent: Thursday, May 11, 2006 11:42 AM To: u2-users@listserver.u2ug.org Cc: [EMAIL PROTECTED] Subject: RE: [U2] Unidata logging of BASIC Runtime errors I have seen this happen before when the minimum.modulo is too small (usually the original size of the file). As to the "#" delimiter in the key, that will contribute to poor hashing, but I would recommend the first step to be resizing, and resetting the minimum.modulo to the same size as the resize modulo. HTH --- Regards, Robert -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Baakkonen, Rodney A (Rod) 46K Sent: Thursday, May 11, 2006 09:07 To: 'u2-users@listserver.u2ug.org' Subject: RE: [U2] Unidata logging of BASIC Runtime errors How about some other hashing algorithms like Universe has. I have some files that have compound keys, where the separator is a '#' and the hashing is awful. This is what GROUP.STAT looks like: File = AUTHORIZATION modulo=529314 hash type=0 blocksize=16384 Split/Merge type = KEYDATA Grp# Bytes Records 0 770 1> 1 1158318>>>>>>>>>>>>>>>>>> 2 0 0 3 1210922>>>>>>>>>>>>>>>>>>>>>> 4 0 0 5 964717>>>>>>>>>>>>>>>>> 6 0 0 7 1221520>>>>>>>>>>>>>>>>>>>> 8 0 0 9 1033819>>>>>>>>>>>>>>>>>>> 10 0 0 11 1077619>>>>>>>>>>>>>>>>>>> 12 0 0 13 1028118>>>>>>>>>>>>>>>>>> 14 0 0 15 1047119>>>>>>>>>>>>>>>>>>> 16 0 0 17 1211522>>>>>>>>>>>>>>>>>>>>>> 18 0 0 19 1081219>>>>>>>>>>>>>>>>>>> I have experimented with blocksize, KEYONLY, HASHTYPE of 1 and this was the best I could do. I am sure that if I brought this file over to Universe, I could find an algorithm that could handle this compound key a lot better. If you need sample data for files that don't hash well, I have some good examples besides this one. The developers seem to love intelligent keys, and sometimes what they come up with does not hash worth a damn. - Rod -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Wally Terhune Sent: Wednesday, May 10, 2006 10:38 PM To: u2-users@listserver.u2ug.org Subject: Fw: [U2] Unidata logging of BASIC Runtime errors So - we are starting our planning cycle for the next release of UniData now. Is this something that there is a ground-swell of support for? If so - what would it look like? All or nothing switch? UDT.OPTIONS? udtconfig setting? environment variable? All users? Just selected users? New log name - eg unibasic.errlog vs udt.errlog? Some limit to the number logged before shutting it off? (concern about log size and filling disk?) ALL UniBasic run-time errors or warnings logged - regardless of fatality? Just some class of errors? Is so - how would you define the ones you want logged? Collect your thoughts and funnel them thru the U2UG Better and Better committee... That is likely a better way than flooding this list. Just my recommendation. Wally Terhune U2 Support Architect IBM Information Management 4700 South Syracuse Street, Denver
RE: [U2] Unidata logging of BASIC Runtime errors
Some of that is due to the KEYDATA causing splits. And when the records in the group gets rerun through the hashing algorithm using the new modulo, they hash into groups that already have a lot of records in them. And the new groups get nothing. So the hashing algorithm never puts any records into some of these groups. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Doug Miller Sent: Thursday, May 11, 2006 10:42 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] Unidata logging of BASIC Runtime errors Have you tried undersizing the file to force data into the other groups? From the sample, it looks as if your groups with data are not overflowing and consequently, the file may be oversized. Of course I am not looking at the entire stats so I could be off base. At 09:07 AM 5/11/2006, Baakkonen, Rodney A (Rod) 46K wrote: >How about some other hashing algorithms like Universe has. I have some files >that have compound keys, where the separator is a '#' and the hashing is >awful. This is what GROUP.STAT looks like: Doug Miller [EMAIL PROTECTED] Manager of Technical Services Strategy 7Dallas TX --- 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/
RE: [U2] Unidata logging of BASIC Runtime errors
I have seen this happen before when the minimum.modulo is too small (usually the original size of the file). As to the "#" delimiter in the key, that will contribute to poor hashing, but I would recommend the first step to be resizing, and resetting the minimum.modulo to the same size as the resize modulo. HTH --- Regards, Robert -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Baakkonen, Rodney A (Rod) 46K Sent: Thursday, May 11, 2006 09:07 To: 'u2-users@listserver.u2ug.org' Subject: RE: [U2] Unidata logging of BASIC Runtime errors How about some other hashing algorithms like Universe has. I have some files that have compound keys, where the separator is a '#' and the hashing is awful. This is what GROUP.STAT looks like: File = AUTHORIZATION modulo=529314 hash type=0 blocksize=16384 Split/Merge type = KEYDATA Grp# Bytes Records 0 770 1> 1 1158318>>>>>>>>>>>>>>>>>> 2 0 0 3 1210922>>>>>>>>>>>>>>>>>>>>>> 4 0 0 5 964717>>>>>>>>>>>>>>>>> 6 0 0 7 1221520>>>>>>>>>>>>>>>>>>>> 8 0 0 9 1033819>>>>>>>>>>>>>>>>>>> 10 0 0 11 1077619>>>>>>>>>>>>>>>>>>> 12 0 0 13 1028118>>>>>>>>>>>>>>>>>> 14 0 0 15 1047119>>>>>>>>>>>>>>>>>>> 16 0 0 17 1211522>>>>>>>>>>>>>>>>>>>>>> 18 0 0 19 1081219>>>>>>>>>>>>>>>>>>> I have experimented with blocksize, KEYONLY, HASHTYPE of 1 and this was the best I could do. I am sure that if I brought this file over to Universe, I could find an algorithm that could handle this compound key a lot better. If you need sample data for files that don't hash well, I have some good examples besides this one. The developers seem to love intelligent keys, and sometimes what they come up with does not hash worth a damn. - Rod -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Wally Terhune Sent: Wednesday, May 10, 2006 10:38 PM To: u2-users@listserver.u2ug.org Subject: Fw: [U2] Unidata logging of BASIC Runtime errors So - we are starting our planning cycle for the next release of UniData now. Is this something that there is a ground-swell of support for? If so - what would it look like? All or nothing switch? UDT.OPTIONS? udtconfig setting? environment variable? All users? Just selected users? New log name - eg unibasic.errlog vs udt.errlog? Some limit to the number logged before shutting it off? (concern about log size and filling disk?) ALL UniBasic run-time errors or warnings logged - regardless of fatality? Just some class of errors? Is so - how would you define the ones you want logged? Collect your thoughts and funnel them thru the U2UG Better and Better committee... That is likely a better way than flooding this list. Just my recommendation. Wally Terhune U2 Support Architect IBM Information Management 4700 South Syracuse Street, Denver, CO 80237 Tel: 303.773.7969 Fax: 303.773.5915 [EMAIL PROTECTED] - Forwarded by Wally Terhune/Denver/IBM on 05/10/2006 05:27 PM - "Bill Haskett" <[EMAIL PROTECTED] os.net>To Sent by: [EMAIL PROTECTED] cc stserver.u2ug.org Subject [U2] Unidata logging of BASIC 05/10/2006 04:07 Runtime errors PM Please respond to [EMAIL PROTECTED] er.u2ug.org Dave: UniData does not have logging for BASIC runtime errors (IBM got back with me on this). There aren't enough requests for this feature to include it in UniData. :-( Bill Haskett --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ [demime 1.01d removed an attachment of type image/gif which had a name of pic00485.gif] [demime 1.01d removed an attachment of type image/gif which had a name of ecblank.gif] --- 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/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Unidata logging of BASIC Runtime errors
Have you tried undersizing the file to force data into the other groups? From the sample, it looks as if your groups with data are not overflowing and consequently, the file may be oversized. Of course I am not looking at the entire stats so I could be off base. At 09:07 AM 5/11/2006, Baakkonen, Rodney A (Rod) 46K wrote: How about some other hashing algorithms like Universe has. I have some files that have compound keys, where the separator is a '#' and the hashing is awful. This is what GROUP.STAT looks like: Doug Miller [EMAIL PROTECTED] Manager of Technical Services Strategy 7Dallas TX --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Unidata logging of BASIC Runtime errors
How about some other hashing algorithms like Universe has. I have some files that have compound keys, where the separator is a '#' and the hashing is awful. This is what GROUP.STAT looks like: File = AUTHORIZATION modulo=529314 hash type=0 blocksize=16384 Split/Merge type = KEYDATA Grp# Bytes Records 0 770 1> 1 1158318>> 2 0 0 3 1210922>> 4 0 0 5 964717> 6 0 0 7 1221520 8 0 0 9 1033819>>> 10 0 0 11 1077619>>> 12 0 0 13 1028118>> 14 0 0 15 1047119>>> 16 0 0 17 1211522>> 18 0 0 19 1081219>>> I have experimented with blocksize, KEYONLY, HASHTYPE of 1 and this was the best I could do. I am sure that if I brought this file over to Universe, I could find an algorithm that could handle this compound key a lot better. If you need sample data for files that don't hash well, I have some good examples besides this one. The developers seem to love intelligent keys, and sometimes what they come up with does not hash worth a damn. - Rod -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Wally Terhune Sent: Wednesday, May 10, 2006 10:38 PM To: u2-users@listserver.u2ug.org Subject: Fw: [U2] Unidata logging of BASIC Runtime errors So - we are starting our planning cycle for the next release of UniData now. Is this something that there is a ground-swell of support for? If so - what would it look like? All or nothing switch? UDT.OPTIONS? udtconfig setting? environment variable? All users? Just selected users? New log name - eg unibasic.errlog vs udt.errlog? Some limit to the number logged before shutting it off? (concern about log size and filling disk?) ALL UniBasic run-time errors or warnings logged - regardless of fatality? Just some class of errors? Is so - how would you define the ones you want logged? Collect your thoughts and funnel them thru the U2UG Better and Better committee... That is likely a better way than flooding this list. Just my recommendation. Wally Terhune U2 Support Architect IBM Information Management 4700 South Syracuse Street, Denver, CO 80237 Tel: 303.773.7969 Fax: 303.773.5915 [EMAIL PROTECTED] - Forwarded by Wally Terhune/Denver/IBM on 05/10/2006 05:27 PM - "Bill Haskett" <[EMAIL PROTECTED] os.net>To Sent by: [EMAIL PROTECTED] cc stserver.u2ug.org Subject [U2] Unidata logging of BASIC 05/10/2006 04:07 Runtime errors PM Please respond to [EMAIL PROTECTED] er.u2ug.org Dave: UniData does not have logging for BASIC runtime errors (IBM got back with me on this). There aren't enough requests for this feature to include it in UniData. :-( Bill Haskett --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ [demime 1.01d removed an attachment of type image/gif which had a name of pic00485.gif] [demime 1.01d removed an attachment of type image/gif which had a name of ecblank.gif] --- 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/
RE: [U2] Unidata logging of BASIC Runtime errors {Unclassified}
Wally, As a current UniVerse user, I am perhaps a little biased, but ... > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Wally Terhune > Sent: Thursday, 11 May 2006 15:38 > To: u2-users@listserver.u2ug.org > Subject: Fw: [U2] UniData logging of BASIC Runtime errors > > So - we are starting our planning cycle for the next release > of UniData now. > Is this something that there is a ground-swell of support for? > If so - what would it look like? Exactly like the UniVerse one? - If there's no 'errlog' file, it doesn't log anything - The file is a rotating circular buffer of messages i.e. it has room for "x" messages, and when it gets to "x" it just wraps round to "1" again - A config option sets the value of "x" (UV default is 100) > > All or nothing switch? UDT.OPTIONS? udtconfig setting? environment > variable? All users? Just selected users? > New log name - e.g. unibasic.errlog vs udt.errlog? > Some limit to the number logged before shutting it off? > (concern about log size and filling disk?) > ALL UniBasic run-time errors or warnings logged - regardless > of fatality? UniVerse seems to log everything, which works for me! Why not have two the products work the same, unless there's a really good reason not to? Just my $0.02 Mike > Just some class of errors? Is so - how would you define the > ones you want logged? > > Collect your thoughts and funnel them thru the U2UG Better and Better > committee... > That is likely a better way than flooding this list. Just my > recommendation. > > > Wally Terhune > U2 Support Architect > IBM Information Management > 4700 South Syracuse Street, Denver, CO 80237 > Tel: 303.773.7969 > Fax: 303.773.5915 > [EMAIL PROTECTED] > > The information contained in this Internet Email message is intended for the addressee only and may contain privileged information, but not necessarily the official views or opinions of the New Zealand Defence Force. If you are not the intended recipient you must not use, disclose, copy or distribute this message or the information in it. If you have received this message in error, please Email or telephone the sender immediately. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Unidata logging of BASIC Runtime errors
Wally: Aren't options great? :-) Bill Haskett Advantos Systems, Inc. www.advantos.net (760)944-5570 (CA) (360)923-4838 (WA) > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Wally Terhune > Sent: Wednesday, May 10, 2006 4:05 PM > To: u2-users@listserver.u2ug.org > Subject: Fw: [U2] Unidata logging of BASIC Runtime errors > > Well, we added file open error logging at one point and upset > a lot of folks - until we made it optional (which was the > right thing to do...) :-( > > Wally Terhune > U2 Support Architect > IBM Information Management > 4700 South Syracuse Street, Denver, CO 80237 > Tel: 303.773.7969 > Fax: 303.773.5915 > [EMAIL PROTECTED] > > > - Forwarded by Wally Terhune/Denver/IBM on 05/10/2006 > 05:03 PM - > > "Bill Haskett" > <[EMAIL PROTECTED] > os.net> > To > Sent by: > [EMAIL PROTECTED] > cc > stserver.u2ug.org > > Subject >[U2] Unidata logging of BASIC > 05/10/2006 04:07 Runtime errors > PM > > > Please respond to > [EMAIL PROTECTED] > er.u2ug.org > > > > > > > Dave: > > UniData does not have logging for BASIC runtime errors (IBM > got back with me on this). There aren't enough requests for > this feature to include it in UniData. :-( > > Bill Haskett --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Unidata logging of BASIC Runtime errors
Bill, of course the flip side is .. why request something that you know you aren't going to get. Ah .. Unidata .. the ugly stepchild Wednesday, May 10, 2006, 3:07:05 PM, you wrote: BH> Dave: BH> UniData does not have logging for BASIC runtime errors (IBM got back with me BH> on this). There aren't enough requests for this feature to include it in BH> UniData. :-( -- DSig ` David Tod Sigafoos ( O O ) ___oOOo__( )__oOOo___ "Far better it is to dare mighty things, to win glorious triumphs even though checkered by failure, than to rank with those poor spirits who neither enjoy nor suffer much because they live in the gray twilight that knows neither victory nor defeat." Theodore Roosevelt --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
