] [mailto:hardhats-
[EMAIL PROTECTED] On Behalf Of Kevin Toppenberg
Sent: Tuesday, August 30, 2005 4:27 PM
To: Hardhats Sourceforge
Subject: [Hardhats-members] COBOL advise needed
OK, OK, I know this is a M list. But hear me out.
The December our Mysis contract will expire, which is our old
Kevin,
Can you get the data into a file accessible to GT.M or Perl? Do you have access
to the
source code or documentation on the data layout? If you're up for a little
programming
challenge then it might be surprisingly easy to read the data directly out of
the COBOL
data files. At most, you
My recollection of COBOL is that the files are defined in a beginning
section of the program and that things are fairly clearly defined, although
some might have a generic description of the data file (saying for example
that each record is 1100 characters) and then move each record into a
Of Kevin Toppenberg
Sent: Tuesday, August 30, 2005 4:27 PM
To: Hardhats Sourceforge
Subject: [Hardhats-members] COBOL advise needed
OK, OK, I know this is a M list. But hear me out.
The December our Mysis contract will expire, which is our old EMR.
The company says that it will be $5,000
OK, OK, I know this is a M list. But hear me out.
The December our Mysis contract will expire, which is our old EMR.
The company says that it will be $5,000+ to get the old progress notes
exported. Recently our group voted not to do that, and to just go
forward with our paper printouts of that
I'm not sure about MicroFocus Cobol (which is a PC Cobol, as I recall)
but I recall that on the mainframes (IBM 360/370 range)
Cobol did NOT provide its own database layer.
It is probably something like VSAM or ISAM, or possibly SQL.
A web search yielded:
to
extract the data to VistA.
Best wishes; Chris
- Original Message -
From: Kevin Toppenberg [EMAIL PROTECTED]
To: Hardhats Sourceforge hardhats-members@lists.sourceforge.net
Sent: Tuesday, August 30, 2005 3:26 PM
Subject: [Hardhats-members] COBOL advise needed
OK, OK, I know
