Re: [U2] Loading a UNIX-based UNIDATA file system on a Windows system...
Very good. Thank you for the responses. I will try those things out. Robert Norman On 11/6/2012 1:03 PM, Wally Terhune wrote: Fnuxi is UniVerse - not UniData. UDTBIN\convdata will convert the byte order of hashed files. If the source machine is Linux, this will not be necessary. You will need to run it - if the source UNIX is AIX, HPUX, Solaris. Convidx will convert UniData indexes. If you need to run programs: convcode Wally Terhune Technical Support Engineer Rocket Software 4600 South Ulster Street, Suite 1100 **Denver, CO 80237 **USA t: +1 720 475 8055 **e: wterh...@rocketsoftware.com **w: u2.rocketsoftware.com -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jeff Schasny Sent: Tuesday, November 06, 2012 1:49 PM To: U2 Users List Subject: Re: [U2] Loading a UNIX-based UNIDATA file system on a Windows system... After loading the data on the Windows system you will have to run fnuxi (C:\u2\UV\bin\fnuxi) on each file you wish to access. I would suggest you do this as follows: - locate the directory where the Unidata files are loaded - run fnuxi on the VOC and D_VOC - drop into Unidata and create a listing of the files in the directory (LIST ONLY VOC WITH F1 = "F") output to the hold file and copy the list from the hold file to the directory containing the Unidata files - using the editor of your choice prefix each line in the file tie c:\u2\UV\bin\fnuxi.exe and save it as a windows .bat file - run the batch file to convert all the files. - edit the batch file and change all the filenames to D_filename - run it again Robert wrote: I have a client that has a client's tape containing the file system from a UNIDATA system running under some form of Unix. They want to load it up on a Windows PC and using the Windows version of UNIDATA, retrieve file data. I have seen in the past that sometimes a file from one OS (like Unix) was not able to be read under a different OS (Windows). This happened once to me with a PKZIP file. There was something slightly different about the file headers or something like that. So the question is, what is the best way to load the data? Is there a conversion utility that you run AFTER you load the data to convert any file header differences? Or are the file headers compatible? Or...? Robert Norman ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users -- Jeff Schasny - Denver, Co, USA jschasny at gmail dot com ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Loading a UNIX-based UNIDATA file system on a Windows system...
Why not tar -cvzf MDB.tgz ACCOUNTNAME which will have the same effect as tar/compress. And depending on the nix system, if it's running samba and on the same net as the NT system, you should just be able to connect in Windows and do a drag-n-drop copy rather than faffing about with tar/compress/ftp. Or if it's a linux system you have the option of "mount -t cifs ...", which I do regularly, then you can copy from the linux side to windows. Cheers, Wol On 07/11/12 11:37, Martin Braid wrote: > and you want to make sure that the originating UNIX system does not > have files named in both upper and lower case e.g. EMPLOYEES and > employees. That causes some fun. > Correct these on the UNIX side before an attempt is made. There are > standard utilities e.g. NT_SCOUT for checking issues prior to conversion > (written to _HOLD_) > On UniData the simplest method of transferring ACCOUNTNAME from Unix to > NT is:- > tar -cvf MDB.tar ACCOUNTNAME > compress MDB.tar > This will then give you a single Unix file MDB.tar.Z which you can then > ftp harmlessly. Accessing this file in NT will act as a zip file that > can be extracted with folder names enabled. > Go to the exploded NT directory and > CONVMARK 255/192/129 > ACCOUNTNAME > CONVDATA -r ACCOUNTNAME > CONVCODE ACCOUNTNAME > CONVIDX -r ACCOUNTNAME > UPDATEVOC -oca ACCOUNTNAME > Martin > -Original Message- > From: u2-users-boun...@listserver.u2ug.org > [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wols Lists > Sent: 07 November 2012 10:42 > To: u2-users@listserver.u2ug.org > Subject: Re: [U2] Loading a UNIX-based UNIDATA file system on a Windows > system... > > And to add even further to the mix ... bear in mind my advice is about > operating systems not U2, and my knowledge is UV not UD ... > > Are you SURE it's not needed if the source is Linux? Or do you actually > mean Linux/x86? Certainly with UV, the OS is irrelevant, what matters is > the endian-ness of the chip, so files can be freely copied between Intel > machines regardless of OS. (Mind you, you probably can't get U2 for > non-Intel Linux :-) > > And nobody has even mentioned the file-corruption issue the OP asked > about ... this is *probably* ftp. Could be samba. Anyways, you need to > make sure that however you copy the files, you tell it that it is a > binary file. If ftp or samba think it's a text file, it will translate > between crlf and lf (and cr on a mac, I believe). > > Cheers, > Wol > > On 06/11/12 21:03, Wally Terhune wrote: >> Fnuxi is UniVerse - not UniData. >> >> UDTBIN\convdata will convert the byte order of hashed files. >> If the source machine is Linux, this will not be necessary. >> You will need to run it - if the source UNIX is AIX, HPUX, Solaris. >> >> Convidx will convert UniData indexes. >> If you need to run programs: convcode >> >> Wally Terhune >> Technical Support Engineer >> Rocket Software >> 4600 South Ulster Street, Suite 1100 **Denver, CO 80237 **USA >> t: +1 720 475 8055 **e: wterh...@rocketsoftware.com **w: >> u2.rocketsoftware.com >> >> >> -Original Message- >> From: u2-users-boun...@listserver.u2ug.org >> [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jeff >> Schasny >> Sent: Tuesday, November 06, 2012 1:49 PM >> To: U2 Users List >> Subject: Re: [U2] Loading a UNIX-based UNIDATA file system on a > Windows system... >> >> After loading the data on the Windows system you will have to run >> fnuxi >> (C:\u2\UV\bin\fnuxi) on each file you wish to access. I would suggest > you do this as follows: >> - locate the directory where the UniData files are loaded >> - run fnuxi on the VOC and D_VOC >> - drop into UniData and create a listing of the files in the directory > >> (LIST ONLY VOC WITH F1 = "F") output to the hold file and copy the >> list from the hold file to the directory containing the UniData files >> - using the editor of your choice prefix each line in the file tie >> c:\u2\UV\bin\fnuxi.exe and save it as a windows .bat file >> - run the batch file to convert all the files. >> - edit the batch file and change all the filenames to D_filename >> - run it again >> >> >> Robert wrote: >>> I have a client that has a client's tape containing the file system >>> from a UNIDATA system running under some form of Unix. They want to >>> l
Re: [U2] Loading a UNIX-based UNIDATA file system on a Windows system...
and you want to make sure that the originating UNIX system does not have files named in both upper and lower case e.g. EMPLOYEES and employees. That causes some fun. Correct these on the UNIX side before an attempt is made. There are standard utilities e.g. NT_SCOUT for checking issues prior to conversion (written to _HOLD_) On UniData the simplest method of transferring ACCOUNTNAME from Unix to NT is:- tar -cvf MDB.tar ACCOUNTNAME compress MDB.tar This will then give you a single Unix file MDB.tar.Z which you can then ftp harmlessly. Accessing this file in NT will act as a zip file that can be extracted with folder names enabled. Go to the exploded NT directory and CONVMARK 255/192/129 ACCOUNTNAME CONVDATA -r ACCOUNTNAME CONVCODE ACCOUNTNAME CONVIDX -r ACCOUNTNAME UPDATEVOC -oca ACCOUNTNAME Martin -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wols Lists Sent: 07 November 2012 10:42 To: u2-users@listserver.u2ug.org Subject: Re: [U2] Loading a UNIX-based UNIDATA file system on a Windows system... And to add even further to the mix ... bear in mind my advice is about operating systems not U2, and my knowledge is UV not UD ... Are you SURE it's not needed if the source is Linux? Or do you actually mean Linux/x86? Certainly with UV, the OS is irrelevant, what matters is the endian-ness of the chip, so files can be freely copied between Intel machines regardless of OS. (Mind you, you probably can't get U2 for non-Intel Linux :-) And nobody has even mentioned the file-corruption issue the OP asked about ... this is *probably* ftp. Could be samba. Anyways, you need to make sure that however you copy the files, you tell it that it is a binary file. If ftp or samba think it's a text file, it will translate between crlf and lf (and cr on a mac, I believe). Cheers, Wol On 06/11/12 21:03, Wally Terhune wrote: > Fnuxi is UniVerse - not UniData. > > UDTBIN\convdata will convert the byte order of hashed files. > If the source machine is Linux, this will not be necessary. > You will need to run it - if the source UNIX is AIX, HPUX, Solaris. > > Convidx will convert UniData indexes. > If you need to run programs: convcode > > Wally Terhune > Technical Support Engineer > Rocket Software > 4600 South Ulster Street, Suite 1100 **Denver, CO 80237 **USA > t: +1 720 475 8055 **e: wterh...@rocketsoftware.com **w: > u2.rocketsoftware.com > > > -Original Message- > From: u2-users-boun...@listserver.u2ug.org > [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jeff > Schasny > Sent: Tuesday, November 06, 2012 1:49 PM > To: U2 Users List > Subject: Re: [U2] Loading a UNIX-based UNIDATA file system on a Windows system... > > After loading the data on the Windows system you will have to run > fnuxi > (C:\u2\UV\bin\fnuxi) on each file you wish to access. I would suggest you do this as follows: > - locate the directory where the UniData files are loaded > - run fnuxi on the VOC and D_VOC > - drop into UniData and create a listing of the files in the directory > (LIST ONLY VOC WITH F1 = "F") output to the hold file and copy the > list from the hold file to the directory containing the UniData files > - using the editor of your choice prefix each line in the file tie > c:\u2\UV\bin\fnuxi.exe and save it as a windows .bat file > - run the batch file to convert all the files. > - edit the batch file and change all the filenames to D_filename > - run it again > > > Robert wrote: >> I have a client that has a client's tape containing the file system >> from a UNIDATA system running under some form of Unix. They want to >> load it up on a Windows PC and using the Windows version of UNIDATA, >> retrieve file data. >> >> I have seen in the past that sometimes a file from one OS (like Unix) >> was not able to be read under a different OS (Windows). This happened >> once to me with a PKZIP file. There was something slightly different >> about the file headers or something like that. >> >> >> So the question is, what is the best way to load the data? >> >> Is there a conversion utility that you run AFTER you load the data to >> convert any file header differences? >> >> Or are the file headers compatible? >> >> Or...? >> >> Robert Norman >> ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users Click https://www.mailcontrol.com/sr/M
Re: [U2] Loading a UNIX-based UNIDATA file system on a Windows system...
And to add even further to the mix ... bear in mind my advice is about operating systems not U2, and my knowledge is UV not UD ... Are you SURE it's not needed if the source is Linux? Or do you actually mean Linux/x86? Certainly with UV, the OS is irrelevant, what matters is the endian-ness of the chip, so files can be freely copied between Intel machines regardless of OS. (Mind you, you probably can't get U2 for non-Intel linux :-) And nobody has even mentioned the file-corruption issue the OP asked about ... this is *probably* ftp. Could be samba. Anyways, you need to make sure that however you copy the files, you tell it that it is a binary file. If ftp or samba think it's a text file, it will translate between crlf and lf (and cr on a mac, I believe). Cheers, Wol On 06/11/12 21:03, Wally Terhune wrote: > Fnuxi is UniVerse - not UniData. > > UDTBIN\convdata will convert the byte order of hashed files. > If the source machine is Linux, this will not be necessary. > You will need to run it - if the source UNIX is AIX, HPUX, Solaris. > > Convidx will convert UniData indexes. > If you need to run programs: convcode > > Wally Terhune > Technical Support Engineer > Rocket Software > 4600 South Ulster Street, Suite 1100 **Denver, CO 80237 **USA > t: +1 720 475 8055 **e: wterh...@rocketsoftware.com **w: u2.rocketsoftware.com > > > -Original Message- > From: u2-users-boun...@listserver.u2ug.org > [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jeff Schasny > Sent: Tuesday, November 06, 2012 1:49 PM > To: U2 Users List > Subject: Re: [U2] Loading a UNIX-based UNIDATA file system on a Windows > system... > > After loading the data on the Windows system you will have to run fnuxi > (C:\u2\UV\bin\fnuxi) on each file you wish to access. I would suggest you do > this as follows: > - locate the directory where the Unidata files are loaded > - run fnuxi on the VOC and D_VOC > - drop into Unidata and create a listing of the files in the directory (LIST > ONLY VOC WITH F1 = "F") output to the hold file and copy the list from the > hold file to the directory containing the Unidata files > - using the editor of your choice prefix each line in the file tie > c:\u2\UV\bin\fnuxi.exe and save it as a windows .bat file > - run the batch file to convert all the files. > - edit the batch file and change all the filenames to D_filename > - run it again > > > Robert wrote: >> I have a client that has a client's tape containing the file system >> from a UNIDATA system running under some form of Unix. They want to >> load it up on a Windows PC and using the Windows version of UNIDATA, >> retrieve file data. >> >> I have seen in the past that sometimes a file from one OS (like Unix) >> was not able to be read under a different OS (Windows). This happened >> once to me with a PKZIP file. There was something slightly different >> about the file headers or something like that. >> >> >> So the question is, what is the best way to load the data? >> >> Is there a conversion utility that you run AFTER you load the data to >> convert any file header differences? >> >> Or are the file headers compatible? >> >> Or...? >> >> Robert Norman >> ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Loading a UNIX-based UNIDATA file system on a Windows system...
Fnuxi is UniVerse - not UniData. UDTBIN\convdata will convert the byte order of hashed files. If the source machine is Linux, this will not be necessary. You will need to run it - if the source UNIX is AIX, HPUX, Solaris. Convidx will convert UniData indexes. If you need to run programs: convcode Wally Terhune Technical Support Engineer Rocket Software 4600 South Ulster Street, Suite 1100 **Denver, CO 80237 **USA t: +1 720 475 8055 **e: wterh...@rocketsoftware.com **w: u2.rocketsoftware.com -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jeff Schasny Sent: Tuesday, November 06, 2012 1:49 PM To: U2 Users List Subject: Re: [U2] Loading a UNIX-based UNIDATA file system on a Windows system... After loading the data on the Windows system you will have to run fnuxi (C:\u2\UV\bin\fnuxi) on each file you wish to access. I would suggest you do this as follows: - locate the directory where the Unidata files are loaded - run fnuxi on the VOC and D_VOC - drop into Unidata and create a listing of the files in the directory (LIST ONLY VOC WITH F1 = "F") output to the hold file and copy the list from the hold file to the directory containing the Unidata files - using the editor of your choice prefix each line in the file tie c:\u2\UV\bin\fnuxi.exe and save it as a windows .bat file - run the batch file to convert all the files. - edit the batch file and change all the filenames to D_filename - run it again Robert wrote: > I have a client that has a client's tape containing the file system > from a UNIDATA system running under some form of Unix. They want to > load it up on a Windows PC and using the Windows version of UNIDATA, > retrieve file data. > > I have seen in the past that sometimes a file from one OS (like Unix) > was not able to be read under a different OS (Windows). This happened > once to me with a PKZIP file. There was something slightly different > about the file headers or something like that. > > > So the question is, what is the best way to load the data? > > Is there a conversion utility that you run AFTER you load the data to > convert any file header differences? > > Or are the file headers compatible? > > Or...? > > Robert Norman > > ___ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users > -- Jeff Schasny - Denver, Co, USA jschasny at gmail dot com ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Loading a UNIX-based UNIDATA file system on a Windows system...
After loading the data on the Windows system you will have to run fnuxi (C:\u2\UV\bin\fnuxi) on each file you wish to access. I would suggest you do this as follows: - locate the directory where the Unidata files are loaded - run fnuxi on the VOC and D_VOC - drop into Unidata and create a listing of the files in the directory (LIST ONLY VOC WITH F1 = "F") output to the hold file and copy the list from the hold file to the directory containing the Unidata files - using the editor of your choice prefix each line in the file tie c:\u2\UV\bin\fnuxi.exe and save it as a windows .bat file - run the batch file to convert all the files. - edit the batch file and change all the filenames to D_filename - run it again Robert wrote: I have a client that has a client's tape containing the file system from a UNIDATA system running under some form of Unix. They want to load it up on a Windows PC and using the Windows version of UNIDATA, retrieve file data. I have seen in the past that sometimes a file from one OS (like Unix) was not able to be read under a different OS (Windows). This happened once to me with a PKZIP file. There was something slightly different about the file headers or something like that. So the question is, what is the best way to load the data? Is there a conversion utility that you run AFTER you load the data to convert any file header differences? Or are the file headers compatible? Or...? Robert Norman ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users -- Jeff Schasny - Denver, Co, USA jschasny at gmail dot com ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
