MCP: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
| Line 28: | Line 28: | ||
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, DMS II 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, DMS II 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> | <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, at least in any foreseeable near term, some fallback is needed.<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 and tested with these. Since this isn't in fact practicable, at least in any foreseeable near term, some fallback is needed.<br><br> | ||
The design principle embodying that fallback is that Unisys MCP will only have integration with the DCP cognitive architecture and not the physical one, each Unisys MCP in a DCP will be an island unlike the linux hosts which form a single system image. That being the case, no Unisys MCP components need to be altered. Rather the integration will be in software built with the standard Unisys dev kit targeting the DCP cog arch. | The design principle embodying that fallback is that Unisys MCP will only have integration with the DCP cognitive architecture and not the physical one, each Unisys MCP in a DCP will be an island unlike the linux hosts which form a single system image. That being the case, no Unisys MCP components need to be altered. Rather the integration will be in software built with the standard Unisys dev kit targeting the DCP cog arch. | ||
<br><br> | <br><br> | ||
