uMSe : our migration solution for scheduler 100% optimised and made to measure

Developed in our Think Tank, uMSe (universal Migrate job Scheduler engine) is our totally unique migration solution. It was created by a team of experts on multiple platforms for job scheduling over 30 years ago. Today it is used by many customers, and is continuously being developed to adapt to job scheduler editors’ updates.

Sources/Targets and heterogeneous technologies

uMSe adapts to all the solutions on the market…

Selection of the most used job schedulers (Workload Scheduler) that our solution supports :

  • AUTOSYS
  • CONTROL-M
  • TWS
  • $UNIVERSE
  • OPEN JOBSCHEDULER
See complete list

If the target job scheduling software is not listed here, contact us. We will rapidly implement it

…and into all the server environments

uMSe operates also on heterogeneous technologies : Z/OS , LINUX , UNIX , WINDOWS et OS/400

MANY WORDS TO SAY THE SAME THING : SCHEDULER MIGRATION + CONVERSION OF JOB SCHEDULER…

uMSe : A meta model

Learn about our « meta model » with the arrows and colours

UMSE : our meta model schema

Click on picture to enlarge

Migration of the scheduler: 3 promises

Receive the uMSe document

Learn more about uMSe?

Ask for our detailed presentation
Receive the uMSe document

Features

Features most appreciated by our customers

  • Transforming conditions on resources into jobs crowned by the processing of post-treatment of transfer tools.
  • Destruction of conditions and reconstruction via meta-language.
  • Reconditioning the conditions in respect to the specificity of the targets, either type «predecessor » and or « trigger ».
  • Functionality allowing you to position the time conditions of processing of jobs converted and or in the chain.
  • Functionality allowing you to convert the calendars and the rules of scheduling or reference directly the same objects, if they already exist in the target.
  • Creating a spreadsheet type file for each object. This file contains all the source / target properties which our customers want to see clearly.
  • Take into account each new change made by the customer (if necessary) just in time.
  • Support renaming for all objects according to all recent standards and the specificities of the target (jobs, chains, machines etc).
  • Analyse scripts and JCL with an aim to catch possible commands or instructions coming from the source.
  • Create scripts allowing the movement of functional scripts to an a new hierarchy / tree.
  • Optimised performance allowing the user to do without maintenance reports on the source.
  • Renumbering the processes by two dimensions, in respect with the order of the conditions.
  • Test the conversion results in our offices, on a server and software environment which is identical to the customer environment.