Compatibility checks: Handling versions and restrictions

The Mosel Native Interface, any modules using the NI, and also Mosel models using module functionality all are likely to evolve over time—most often via the addition of new functionality. In a development context, the components of an application typically are compiled and run using the same Mosel version. However, this may not be the case for deployment, resulting in issues of version compatibility, in particular when deploying (partial) updates to older platforms. The following sections show how such backwards compatibility can be achieved for Mosel modules.

Furthermore, the use of Mosel in protected environments, usually in the context of remote model execution (e.g., via mmjobs, XPRD, Xpress Insight), requires modules to be compliant with access restrictions that are imposed by the environment. Section Restrictions shows how to implement the necessary checks.