Moving Microfocus 3.1 to a better laptop

I own a copy of Microfocus 3.1 that I use for small personal
projects. I want to move the license to a newer computer - it is on a
very unstable old laptop now. I know there is/was a process that
involved "revoking" the license on the old computer, then doing some
2nd step to activate that license on the new computer. I have
installed 3.1 on the new computer, and can use the 30 day trial period
- it works fine. I'm retired and living on socsec, so cannot afford
to pay thousands of dollars to be on maintenance, just to move my
compiler. I can move other products from one computer to another,
windows for example, so I should be able to do the same with
Microfocus 3.1 - I paid over $4,000 for it, I think. Can someone tell
me the 2nd step? TIA, Paul
.

Relevant Pages

  • Re: An Ada Advice Inquiry
    ... around for 10 years for maintainance (which every sane customer will ... While I agree it is nice to keep maintenance around for that time, this is probably another example of the different bar people set when they use Ada. ... it had to be a certified compiler. ... Just about the worst thing you can do if you really care about long term support is pick any tool that requires some automated method for license enforcement. ...
    (comp.lang.ada)
  • Re: Moving Microfocus 3.1 to a better laptop
    ... involved "revoking" the license on the old computer, ... Microfocus 3.1 - I paid over $4,000 for it, I think. ... If this is CryptKey, the technique might be the same as for Fujitsu. ...
    (comp.lang.cobol)
  • RE: Dumb question?
    ... That the system you are shipping the object/load module to is ... license should be required. ... Suppose we licensed a COBOL compiler for one system; ... The sender believes that this E-mail and any attachments were free of any ...
    (bit.listserv.ibm-main)
  • Open64 Not Setting World on Fire: Why?
    ... FORTRAN compiler that had already implemented the Fortran 95 standard ... Initially, when I did a web search, it seemed that the name Open64 was ... now out of date, and the compiler is now called ORC, the Open Research ... license is modified from the GPL in respect of the section about ...
    (comp.lang.fortran)
  • Open64 not setting world on fire
    ... FORTRAN compiler that had already implemented the Fortran 95 standard ... Initially, when I did a web search, it seemed that the name Open64 was ... now out of date, and the compiler is now called ORC, the Open Research ... license is modified from the GPL in respect of the section about ...
    (comp.lang.fortran)