What happens when my MettleCI licence expires?

When your MettleCI license expires you will not need to uninstall the software. It will remain partially operational until you elect remove it. Existing jobs will continue to behave as normal. The Unit Test harness can be left in place and will have no effect on your solution unless you alter the value of the ‘Unit Testing’ environment variable in which case the job will abort. Specifying Execution or Interception, for example, will not have any effect on your job, and it will execute with no alteration in the functionality or performance observed before MettleCI was introduced. Further details about the behaviour of MettleCI as it approaches and passes your renewal date is provided below.

Note that Data Migrators reserves the exclusive right to alter, in future releases, the behaviour of any MettleCI component for which a current valid licence cannot be found.

Tool	Expiry Warning	Expired

Tool	Expiry Warning	Expired
Workbench	When using the Workbench User Interface you’ll receive warnings (in the form of popup messages) 30 days before your license expires.	Once expired, you’ll continue to be able to use Workbench as normal, with the following exceptions: You won’t be able to add DataStage projects to MettleCI, or remove them You won’t be able to execute Compliance checks You won’t be able to check jobs in to Git using MettleCI You won’t be able to create new Unit Test specifications, or remove existing specifications
Unit Test harness	When running a job with the MettleCI Unit Testing parameter set to Execution or Interception modes you’ll receive warnings (in the form of DataStage job log entries) 30 days before your license expires.	When running a job with the MettleCI Unit Testing parameter set to a non-default mode (e.g. Execution or Interception), the DataStage log will show an error message stating that your MettleCI license has expired. Then the job will abort without running.
MettleCI Command Line (Console Mode¹)	Each MettleCI plugin for which a valid license is required will produce a warning to the terminal when the console is invoked. After this the MettleCI Command Line prompt is displayed and the user is permitted to continue as normal.	Each MettleCI plugin for which a valid license is required will produce a warning to the terminal when the console is invoked, and these plugins will be not loaded into the MettleCI Command Line. If no plugins qualify for loading because of license constraints then the command line will report this and fail, returning an error code of 127 to the host shell.
MettleCI Command Line (Command Mode¹)	When calling the MettleCI Command Line in Command Mode (e.g. from a script) you will receive a warning at stdout for each MettleCI plugin for which a valid license is required. After this the command is executed as instructed. The command will return a code of 0 to the host shell.	When calling the MettleCI Command Line in Command Mode (e.g. from a script) you will receive a warning to stdout for each MettleCI plugin for which a valid license is required. After this the command will fail and return a code of 127 to the host shell.

(1) The difference between the MettleCI Command Line’s Console Mode and Command Mode is described here.