MCP: Difference between revisions

Line 26:

About this time Unisys made MCP available to run from Windows 7 or 10 64 bit as "MCP Express" although I didn learn of this until 2019Q3 and didn bring it up till end of Q4 '20 (version 5). It is the full OS, sufficient to develop programs for current MCP (18). A main issue is that the license has to be renewed every August 1, but unclear how much disruption that is, working assumption is that worst case is that the backup restore utility would have to be used and the MCP rebuilt from reinstall.

Having hands on MCP 18 and seeing that it is fully available as a development target opens a role for the legacy MCP is the DCP, where "Unisys MCP" will be used wherever the distinction needs to be made clear. Also usages like ODT or MARC are unambiguously referring to the Unisys product as we never intended take more than inspiration from it and it is great to see that all of the mainframe stuff is available in the Windows based product including TCP/IP and DNS interfaces.

Having hands on MCP 18 and seeing that it is fully available as a development target opens a role for the legacy MCP in the DCP, where "Unisys MCP" will be used wherever the distinction needs to be made clear. Also usages like ODT or MARC are unambiguously referring to the Unisys product as we never intended take more than inspiration from it and it is great to see that all of the mainframe stuff is available in the Windows based product including TCP/IP and DNS interfaces.

The most natural form of integration of Unisys MCP is to allow it as an alternate to linux MCP in a DCP. Practically, this would require at least a DCP aware WFL and DCALGOL and for everything impacted to be recompiled with these. Since this isn't in fact practicable, some fallback is needed.

Navigation menu

Page actions

Page actions

Personal tools

About

Search

forewords

novel

Tools

@@ Line 26: / Line 26: @@
 About this time Unisys made MCP  available to run from Windows 7 or 10 64 bit as "MCP Express" although I didn learn of this until 2019Q3 and didn bring it up till end of Q4 '20 (version 5). It is the full OS, sufficient to develop programs for current MCP (18). A main issue is that the license has to be renewed every August 1, but unclear how much disruption that is, working assumption is that worst case is that the backup restore utility would have to be used and the MCP rebuilt from reinstall.
 <br><br>
-Having hands on MCP 18 and seeing that it is fully available as a development target opens a role for the legacy MCP is the DCP, where "Unisys MCP" will be used wherever the distinction needs to be made clear. Also usages like ODT or MARC are unambiguously referring to the Unisys product as we never intended take more than inspiration from it  and it is great to see that all of the mainframe stuff is available in the Windows based product including TCP/IP and DNS interfaces.
+Having hands on MCP 18 and seeing that it is fully available as a development target opens a role for the legacy MCP in the DCP, where "Unisys MCP" will be used wherever the distinction needs to be made clear. Also usages like ODT or MARC are unambiguously referring to the Unisys product as we never intended take more than inspiration from it  and it is great to see that all of the mainframe stuff is available in the Windows based product including TCP/IP and DNS interfaces.
 <br><br>
 The most natural form of integration of Unisys MCP is to allow it as an alternate to linux MCP in a DCP. Practically, this would require at least a DCP aware WFL and DCALGOL and for everything impacted to be recompiled with these. Since this isn't in fact practicable, some fallback is needed.