RE: Keypoint and Linux?
I'll admit I was wrong about Cobol being a database. I guess it is in the sense that an encrypted text file or a spreadsheet could be considered the same. But you should at least admit that you are dealing with an old piece of crap. And I mean that in the nicest possible way. ;-)
-----Original Message----- From: On Behalf Of RtX Sent: Thursday, November 16, 2006 1:19 PM
On 11/16/06, Jeremy Fowler <JFowler@westrope.com> wrote:
Cobol is a programming language but it stores its data in binary flat files. So in a sense it is its own database. There are applications that can extract data out of cobol files, but it's a messy task. There is no such beast as an ODBC Cobol driver...
I knew Cobol was/is a programming language. Someone pointed the obvious out for me. Thanks. True, there is no ODBC Cobol driver. Could make things interesting in data conversion. We'll see.
We had a Cobol based Agency Management system here four years ago. We ended up moving to a SQL based solution from another vendor. We did have to extract some data from the Cobol app, but luckily the new vendor had experience with our old system and was able to do that for us. The data wasn't very pretty.
Did your vendor have to write a data conversion app? I would assume so.
I would recommend your client shop around for a more technologically advanced trucking system. Or have one designed.
My client is happy with the current software so shopping is probably not an option.
On 11/16/06, Kelsay, Brian - Kansas City, MO <brian.kelsay@kcc.usda.gov> wrote:
I'll admit I was wrong about Cobol being a database. I guess it is in the sense that an encrypted text file or a spreadsheet could be considered the same. But you should at least admit that you are dealing with an old piece of crap. And I mean that in the nicest possible way. ;-)
Admitted. ;-) Right now, I have used Ghost to dupe a copy for testing purposes. I thought I would at least be able to mount the drive under Linux and peruse the files however trying to mount a type 63 SCO UNIX (sysv) filesystem does not work. I'm not sure if it's incompatible with Linux or if it's a bum dupe. I read somewhere that I would have better luck mounting the drive under one of the BSD's. ?!?!?!
-----Original Message----- From: On Behalf Of RtX Sent: Thursday, November 16, 2006 1:19 PM
On 11/16/06, Jeremy Fowler <JFowler@westrope.com> wrote:
Cobol is a programming language but it stores its data in binary flat files. So in a sense it is its own database. There are applications that can extract data out of cobol files, but it's a messy task. There is no such beast as an ODBC Cobol driver...
I knew Cobol was/is a programming language. Someone pointed the obvious out for me. Thanks. True, there is no ODBC Cobol driver. Could make things interesting in data conversion. We'll see.
We had a Cobol based Agency Management system here four years ago. We ended up moving to a SQL based solution from another vendor. We did have to extract some data from the Cobol app, but luckily the new vendor had experience with our old system and was able to do that for us. The data wasn't very pretty.
Did your vendor have to write a data conversion app? I would assume so.
I would recommend your client shop around for a more technologically advanced trucking system. Or have one designed.
My client is happy with the current software so shopping is probably not an option.
_______________________________________________ Kclug mailing list Kclug@kclug.org http://kclug.org/mailman/listinfo/kclug
-- RtX... Ty Unes - Overland Park, Ks. riverty@gmail.com
On 11/17/06, RtX <riverty@gmail.com> wrote:
Admitted. ;-)
Right now, I have used Ghost to dupe a copy for testing purposes. I thought I would at least be able to mount the drive under Linux and peruse the files however trying to mount a type 63 SCO UNIX (sysv) filesystem does not work. I'm not sure if it's incompatible with Linux or if it's a bum dupe. I read somewhere that I would have better luck mounting the drive under one of the BSD's. ?!?!?!
No idea on if BSDs have support for this. I searched on the OpenBSD mailing list and didn't find any information about mounting SCO drives in OpenBSD. Maybe you know the partition type name and can find it in the man page for mount. http://www.openbsd.org/cgi-bin/man.cgi?query=mount&apropos=0&sektion=0&manpa...
A SCO partition is subdivided into 'divisions', each of which can hold a filesystem. It can be a real PITA to deal with that under any other OS. Why don't you try creating a tarball of the files the existing system uses, and put that on an ext3 or Reiser filesystem for your testing? On 11/17/06, djgoku <djgoku@gmail.com> wrote:
On 11/17/06, RtX <riverty@gmail.com> wrote:
Admitted. ;-)
Right now, I have used Ghost to dupe a copy for testing purposes. I thought I would at least be able to mount the drive under Linux and peruse the files however trying to mount a type 63 SCO UNIX (sysv) filesystem does not work. I'm not sure if it's incompatible with Linux or if it's a bum dupe. I read somewhere that I would have better luck mounting the drive under one of the BSD's. ?!?!?!
No idea on if BSDs have support for this. I searched on the OpenBSD mailing list and didn't find any information about mounting SCO drives in OpenBSD. Maybe you know the partition type name and can find it in the man page for mount.
http://www.openbsd.org/cgi-bin/man.cgi?query=mount&apropos=0&sektion=0&manpa... _______________________________________________ Kclug mailing list Kclug@kclug.org http://kclug.org/mailman/listinfo/kclug
This might be a bit convoluted, but it might be a clue or a least a general direction... http://aplawrence.com/Bofcusm/2645.html Good Luck!! Jeffrey A. McCright, A+ 816-210-3107 jmccright@hotmail.com
From: "Monty J. Harder" <mjharder@gmail.com> To: djgoku <djgoku@gmail.com>, "KCLUG (E-mail)" <kclug@kclug.org> Subject: Re: Re: Keypoint and Linux? Date: Fri, 17 Nov 2006 22:06:02 -0600 MIME-Version: 1.0 Received: from kclug.org ([139.146.133.42]) by bay0-mc10-f1.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Fri, 17 Nov 2006 20:06:10 -0800 Received: from localhost (localhost.localdomain [127.0.0.1])by kclug.org (Postfix) with ESMTP id 801FA704D7B;Fri, 17 Nov 2006 21:51:30 -0600 (CST) Received: from kclug.org ([127.0.0.1])by localhost (kclug.org [127.0.0.1]) (amavisd-new, port 10024)with ESMTP id KiLvTZeqqy-T; Fri, 17 Nov 2006 21:51:29 -0600 (CST) Received: from kclug.org (localhost.localdomain [127.0.0.1])by kclug.org (Postfix) with ESMTP id 00027704D75;Fri, 17 Nov 2006 21:51:27 -0600 (CST) Received: from localhost (localhost.localdomain [127.0.0.1])by kclug.org (Postfix) with ESMTP id E6492704D69for <kclug@kclug.org>; Fri, 17 Nov 2006 21:51:26 -0600 (CST) Received: from kclug.org ([127.0.0.1])by localhost (kclug.org [127.0.0.1]) (amavisd-new, port 10024)with ESMTP id MiQlH4Usnvv4 for <kclug@kclug.org>;Fri, 17 Nov 2006 21:51:26 -0600 (CST) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.185])by kclug.org (Postfix) with ESMTP id 753D0704D67for <kclug@kclug.org>; Fri, 17 Nov 2006 21:51:26 -0600 (CST) Received: by nf-out-0910.google.com with SMTP id q29so1722256nfcfor <kclug@kclug.org>; Fri, 17 Nov 2006 20:06:02 -0800 (PST) Received: by 10.78.127.3 with SMTP id z3mr2702633huc.1163822762153;Fri, 17 Nov 2006 20:06:02 -0800 (PST) Received: by 10.78.186.7 with HTTP; Fri, 17 Nov 2006 20:06:02 -0800 (PST) X-Message-Info: LsUYwwHHNt05/9ZF4VM1vpUN7nVhxHcpyJB4MNPzn1Q= X-Original-To: kclug@kclug.org Delivered-To: kclug@kclug.org References: <1DF8586D689C1F4A9008A81552BBDEE50644C2@MOKANSASCIS301.agcentral.one.usda.gov><c44362420611170738q54245d52u5e798b532d85a707@mail.gmail.com><99dd19c90611171451r24845cf6y72ce081b1f99444@mail.gmail.com> X-BeenThere: kclug@kclug.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: KCLUG mailing list <kclug.kclug.org> List-Unsubscribe: <http://kclug.org/mailman/listinfo/kclug>,<mailto:kclug-request@kclug.org?subject=unsubscribe> List-Archive: <http://kclug.org/pipermail/kclug> List-Post: <mailto:kclug@kclug.org> List-Help: <mailto:kclug-request@kclug.org?subject=help> List-Subscribe: <http://kclug.org/mailman/listinfo/kclug>,<mailto:kclug-request@kclug.org?subject=subscribe> Errors-To: kclug-bounces@kclug.org Return-Path: kclug-bounces@kclug.org X-OriginalArrivalTime: 18 Nov 2006 04:06:10.0822 (UTC) FILETIME=[E19B9260:01C70AC6]
A SCO partition is subdivided into 'divisions', each of which can hold a filesystem. It can be a real PITA to deal with that under any other OS. Why don't you try creating a tarball of the files the existing system uses, and put that on an ext3 or Reiser filesystem for your testing?
On 11/17/06, djgoku <djgoku@gmail.com> wrote:
On 11/17/06, RtX <riverty@gmail.com> wrote:
Admitted. ;-)
Right now, I have used Ghost to dupe a copy for testing purposes. I thought I would at least be able to mount the drive under Linux and peruse the files however trying to mount a type 63 SCO UNIX (sysv) filesystem does not work. I'm not sure if it's incompatible with Linux or if it's a bum dupe. I read somewhere that I would have better luck mounting the drive under one of the BSD's. ?!?!?!
No idea on if BSDs have support for this. I searched on the OpenBSD mailing list and didn't find any information about mounting SCO drives in OpenBSD. Maybe you know the partition type name and can find it in the man page for mount.
http://www.openbsd.org/cgi-bin/man.cgi?query=mount&apropos=0&sektion=0&manpa... _______________________________________________ Kclug mailing list Kclug@kclug.org http://kclug.org/mailman/listinfo/kclug
_______________________________________________ Kclug mailing list Kclug@kclug.org http://kclug.org/mailman/listinfo/kclug
_________________________________________________________________ MSN Shopping has everything on your holiday list. Get expert picks by style, age, and price. Try it! http://shopping.msn.com/content/shp/?ctId=8000,ptnrid=176,ptnrdata=200601&tc...
participants (5)
-
djgoku -
Jeffrey McCright -
Kelsay, Brian - Kansas City, MO -
Monty J. Harder -
RtX