Metalogic software is designed to be as code and feature compatible with as many MCP releases as possible. However, FLEX, JAMPACK and SUPERVISOR perform MCP version compatibility checks and generally require software updates whenever a major MCP is released by Unisys.
The following tables show product name, the preferred Metalogic release container version compatible for each MCP release and notes.
Each product has a reference Metalogic codefile that can be used to determine the release version currently installed on the system. For example, the codefile *METALOGIC/SUPERVISOR identifies the SUPERVISOR product.
The version is determined from the name the release container name used by the Metalogic INSTALL utility. This is a 4-digit number that is also held in all released codefiles within the PRODUCT file attribute.
PD METALOGIC/MAGUS
FILE METALOGIC/MAGUS ON DISK (NEWPCODE) & (DIRECTORY) IN USEFAMILY SERIAL NUMBER: 980505
This number is built into the name of the release container:
The notes column has the following variants:
This refers to the release of the *METALOGIC/MAGUS library that fully supports the new MCP version, including known MCP issues. This means that the MAGUS library, upon initiation, will not display warning messages about MCP compatibility.
This refers to a necessary change to a Metalogic product to handle the de-implementation by Unisys of a file/task attribute or feature previously used by the Metalogic product. The de-implementation may or may not cause problems but it is generally suggested that the customer upgrades to the latest software.
A stability release is usually recommended where one or more important fixes have been applied to the product, raising the recommended release container version for that MCP level.
Although the tables show the recommended release levels that should be installed for a particular MCP release, in many cases earlier Metalogic software levels will run fine on a new MCP. However, this assumes that the customer is satisfied with the stability of the software on his current MCP level.
If incompatible Metalogic software is run on a new MCP system, various warning and error messages may be seen:
From the Magus library, for example:
MAGUS: WARNING! MAGUS IS NOT QUALIFIED FOR MCP 54
MAGUS: WARNING! MAGUS IS QUALIFIED FOR MCP 48 TO 53
Typically, Magus will run on 5 MCP levels but a maximum MCP release is compiled into each codefile. If the host MCP exceeds this level, then the above warnings will be seen. Unless the Metalogic release is very old, it is unlikely that there will be other issues.
Similar warning messages may be displayed by Jampack, Supervisor and Flex/Library. Again, these are general warnings and it is likely that the software will continue to function without error.A rule of thumb is that if the version of the current Magus library is 1 less than the migrated MCP level and the note entry for the product shows ‘MCP compatibility release’ then Metalogic software should run without error except for the warnings described above. If in doubt, please contact Metalogic: support@Metalogic.eu.com
