Re: inherited cobol app., can't run (xm.exe)?

Richard wrote:
>
>
> 'Persuade' may require the ability to write cheques for 6 or 7 figure
> numbers.
>
> Why would they 'give', or even sell, the source code to a product that
> you are contracted to create a competitor or replacement for ?
>
> In fact they may even 'persuade' you via the courts that you are
> attempting to steal their IP and/or Trade Secrets. There may even be
> EULA or contracts that prevent you, as an agent of the customer, from
> doing what you have done so far.  Check your liability and indemnity
> clauses in the contract with your customer. Don't have any ? oh bad
> luck, get a lawyer.
>
>
>> * Can .GNT files be decompiled?
>
> No.
>
> If you are trying to run .GNT files, or are wanting to use XM.EXE then
> you will need to buy a licensed run-time from Microfocus. With DOS
> based MF systems there are ways of building applications that do not
> require run-time fees, but .GNT and XM and not within that.
>
>> * What is the purpose of the IDX file -- some kind of index into the
>> main data file?
>
> Yes.
>
>> * Are the data files parseable without knowing the record
>> definitions?
>
> No. Not generally anyway. You may be able to work out what many data
> items are from knowing the data values and seeing where they are in
> the record.
>
>> I tried a tool from Siber which did a so-so job of displaying the
>> data. I'm sure there's some rules to doing it, but I surely don't
>> know them.
>
> That may be as good as it gets.
>
>> * Is there a tutorial online where I can learn how to read data
>> properly out of these files? I can see some things which look
>> familiar in there, but others do not (I'm using a hex text editor --
>> notepad++ actually)
>
> Stuff may be binary or packed decimal or even proprietary. If you
> recognise something then it may be that, otherwise you may never know
> what the data represents.
>
>>> I agreed to take on a COBOL conversion project.
>
> It seems that it _isn't_ a "COBOL conversion project" at all. It is a
> 'ground up' reimplementation of what they are doing with a packaged
> solution. That would be fine if:
>
> a) you are paid an hourly or weekly rate suitable for an analyst/
> programmer (which you are obviously not).
>
> b) there is an unlimited budget
>
> c) there is no completion date specified.
>
> However, if there are date and budget limits, or specified contractual
> performance, then run away now.

Maybe he could use Linux or a pile of steaming GNU stuff?