Re: [U2] Bug in UV.VI
Awesome. I'll give it a try (after bringing my mail/web/client-access server back from the dead after the mirror broke). Karl > Hi Karl, > > Below is an email from Tony Wood explaining how to patch UV.VI to work > correctly. > Apparanently IBM have had a GTAR outstanding for years but it isn't > considered important enough to fix (you can use ED after all). > > > Craig > > > > Original Message > Subject: Re: [UV] file type question > Date: Wed, 14 May 2003 10:58:59 +1000 > From: Tony Wood <[EMAIL PROTECTED]> > Reply-To: > Organization: Reynolds & Reynolds > To: > References: > <[EMAIL PROTECTED]> > > Longname refers to the filenames only I believe. > > A type 1 file allows for item name of 14 characters then it creates a > subdirectory. This is described in the doco. Use a type 19 file instead if > this is a problem. > > UV.VI has a bug that incorrectly identifies a type 19 file as having a > type > 1 item name structure and looks in a non-exisitant subdirectory for the > item. > > >From the UV account try ED BP UV.VI.B (the line numbers are a guide > only) > > 125*** is edit file a directory > 126 > 127if file.info<21> = 1 or file.info<21> = 19 > 128then > 129 file.path = file.info<20> > 130 *dirtype = file.info<20> ;* This is where is > mis-identifies > the file type. > 131 dirtype = file.info<21> > 132end > 133else > > And futher on; > > 254 process.argument: > 255 > 256 * if dirtype ne 19 then > 257if dirtype eq 1 then > 258 execute 'UNIX.PATH "':f.arg:'"' capturing item.id > 259 > 260 item.id = item.id<1> > 261end else > 262 item.id = f.arg > 263end > > File and compile and your away. Don't forget to take a copy of this and > keep > somewhere so the next upgrade doesn't overwrite it. I have reported this > to > IBM but I doubt it's a high priority. > > Regards, > > T. > --- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ > -- karl _/ _/ _/ _/_/_/ __o _/ _/ _/ _/_/ _-\<._ _/_/_/ _/_/_/ (_)/ (_) _/ _/ _/ _/ .. _/ _/ arl _/_/_/ _/ earson[EMAIL PROTECTED] -- IT Director, ATS Industrial Supply, Inc. http://www.atsindustrial.com Toll-free: 800-789-9300 x29 Direct2Desk: 801-978-4429 Facsimile: 801-972-3888 -- --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Bug in UV.VI
Hi Karl, Below is an email from Tony Wood explaining how to patch UV.VI to work correctly. Apparanently IBM have had a GTAR outstanding for years but it isn't considered important enough to fix (you can use ED after all). Craig Original Message Subject: Re: [UV] file type question Date: Wed, 14 May 2003 10:58:59 +1000 From: Tony Wood <[EMAIL PROTECTED]> Reply-To: Organization: Reynolds & Reynolds To: References: <[EMAIL PROTECTED]> Longname refers to the filenames only I believe. A type 1 file allows for item name of 14 characters then it creates a subdirectory. This is described in the doco. Use a type 19 file instead if this is a problem. UV.VI has a bug that incorrectly identifies a type 19 file as having a type 1 item name structure and looks in a non-exisitant subdirectory for the item. >From the UV account try ED BP UV.VI.B (the line numbers are a guide only) 125*** is edit file a directory 126 127if file.info<21> = 1 or file.info<21> = 19 128then 129 file.path = file.info<20> 130 *dirtype = file.info<20> ;* This is where is mis-identifies the file type. 131 dirtype = file.info<21> 132end 133else And futher on; 254 process.argument: 255 256 * if dirtype ne 19 then 257if dirtype eq 1 then 258 execute 'UNIX.PATH "':f.arg:'"' capturing item.id 259 260 item.id = item.id<1> 261end else 262 item.id = f.arg 263end File and compile and your away. Don't forget to take a copy of this and keep somewhere so the next upgrade doesn't overwrite it. I have reported this to IBM but I doubt it's a high priority. Regards, T. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Bug in UV.VI
As fpath was ONLY designed to convert a file path into a Type1 file path, it's doing exactly what it was designed to do. I believe it's more a problem that UV.VI doesn't distinguish between Type 1 and 19 and should not be calling fpath on Type19 items. Just my $.02 > -Original Message- > Subject: Re: [U2] Bug in UV.VI > > This is happening on both my Solaris and Linux systems. It appears to be a > problem with the fpath program in the bin directory. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Bug in UV.VI
The fpath program is called as UNIX.PATH. - Original Message - From: <[EMAIL PROTECTED]> To: Sent: Wednesday, November 02, 2005 12:49 PM Subject: [U2] Bug in UV.VI Line 17 Reads: * 03/15/00 24466 SAP Change code to read long record names in type 19 files. But, if my BP file is type 19, UV.VI returns an empty record. This is on uniVerse 10.0.7 on AIX 5.2. It was a problem with each of the previous releases, too. Just thought I'd throw this out as I commonly use the following VOC entry for editing BP items: VFIX 0001 PA 0002 FORMAT BP <> 0003 UV.VI BP <> 0004 HUSH ON 0005 DELETE BP.O <> 0006 HUSH OFF 0007 BASIC BP <> I really prefer using type 19 files for BP source, but haven't been able to do so and still use UV.VI. I have toyed with the idea of writing my own script to do it, but that kind of defeats the purpose of UV.VI, doesn't it? TIA, -- karl _/ _/ _/ _/_/_/ __o _/ _/ _/ _/_/ _-\<._ _/_/_/ _/_/_/ (_)/ (_) _/ _/ _/ _/ .. _/ _/ arl _/_/_/ _/ earson[EMAIL PROTECTED] -- IT Director, ATS Industrial Supply, Inc. http://www.atsindustrial.com Toll-free: 800-789-9300 x29 Direct2Desk: 801-978-4429 Facsimile: 801-972-3888 -- --- 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] Bug in UV.VI
This is happening on both my Solaris and Linux systems. It appears to be a problem with the fpath program in the bin directory. - Original Message - From: <[EMAIL PROTECTED]> To: Sent: Wednesday, November 02, 2005 12:49 PM Subject: [U2] Bug in UV.VI Line 17 Reads: * 03/15/00 24466 SAP Change code to read long record names in type 19 files. But, if my BP file is type 19, UV.VI returns an empty record. This is on uniVerse 10.0.7 on AIX 5.2. It was a problem with each of the previous releases, too. Just thought I'd throw this out as I commonly use the following VOC entry for editing BP items: VFIX 0001 PA 0002 FORMAT BP <> 0003 UV.VI BP <> 0004 HUSH ON 0005 DELETE BP.O <> 0006 HUSH OFF 0007 BASIC BP <> I really prefer using type 19 files for BP source, but haven't been able to do so and still use UV.VI. I have toyed with the idea of writing my own script to do it, but that kind of defeats the purpose of UV.VI, doesn't it? TIA, -- karl _/ _/ _/ _/_/_/ __o _/ _/ _/ _/_/ _-\<._ _/_/_/ _/_/_/ (_)/ (_) _/ _/ _/ _/ .. _/ _/ arl _/_/_/ _/ earson[EMAIL PROTECTED] -- IT Director, ATS Industrial Supply, Inc. http://www.atsindustrial.com Toll-free: 800-789-9300 x29 Direct2Desk: 801-978-4429 Facsimile: 801-972-3888 -- --- 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] Bug in UV.VI
UV.VI ignores it is type 19 and treats it like a type 1. So any BP item names greater than 13 characters will cause it generate the wrong name. HTH Rod Hills -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, November 02, 2005 10:50 AM To: u2-users@listserver.u2ug.org Subject: [U2] Bug in UV.VI Line 17 Reads: * 03/15/00 24466 SAP Change code to read long record names in type 19 files. But, if my BP file is type 19, UV.VI returns an empty record. This is on uniVerse 10.0.7 on AIX 5.2. It was a problem with each of the previous releases, too. Just thought I'd throw this out as I commonly use the following VOC entry for editing BP items: VFIX 0001 PA 0002 FORMAT BP <> 0003 UV.VI BP <> 0004 HUSH ON 0005 DELETE BP.O <> 0006 HUSH OFF 0007 BASIC BP <> I really prefer using type 19 files for BP source, but haven't been able to do so and still use UV.VI. I have toyed with the idea of writing my own script to do it, but that kind of defeats the purpose of UV.VI, doesn't it? TIA, -- karl _/ _/ _/ _/_/_/ __o _/ _/ _/ _/_/ _-\<._ _/_/_/ _/_/_/ (_)/ (_) _/ _/ _/ _/ .. _/ _/ arl _/_/_/ _/ earson[EMAIL PROTECTED] -- IT Director, ATS Industrial Supply, Inc. http://www.atsindustrial.com Toll-free: 800-789-9300 x29 Direct2Desk: 801-978-4429 Facsimile: 801-972-3888 -- --- 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] Bug in UV.VI
Line 17 Reads: * 03/15/00 24466 SAP Change code to read long record names in type 19 files. But, if my BP file is type 19, UV.VI returns an empty record. This is on uniVerse 10.0.7 on AIX 5.2. It was a problem with each of the previous releases, too. Just thought I'd throw this out as I commonly use the following VOC entry for editing BP items: VFIX 0001 PA 0002 FORMAT BP <> 0003 UV.VI BP <> 0004 HUSH ON 0005 DELETE BP.O <> 0006 HUSH OFF 0007 BASIC BP <> I really prefer using type 19 files for BP source, but haven't been able to do so and still use UV.VI. I have toyed with the idea of writing my own script to do it, but that kind of defeats the purpose of UV.VI, doesn't it? TIA, -- karl _/ _/ _/ _/_/_/ __o _/ _/ _/ _/_/ _-\<._ _/_/_/ _/_/_/ (_)/ (_) _/ _/ _/ _/ .. _/ _/ arl _/_/_/ _/ earson[EMAIL PROTECTED] -- IT Director, ATS Industrial Supply, Inc. http://www.atsindustrial.com Toll-free: 800-789-9300 x29 Direct2Desk: 801-978-4429 Facsimile: 801-972-3888 -- --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
