top of page

Scheduler Migrations

A fully equipped migration of your workload automation.

Building on its experience in software development, ISC now accompanies its clients with scheduler migrations,

whether they might be motivated by a rehosting project or a will to uniformize their workload automation tools.   

 

Our approach is based on the integration of two of our software products, combining their strengths and  respective functions in order to provide an efficient end-to end migration.

 

A common denominator of the ISC software products is the ability to customize to our customers' specifics needs. It allows us to integrate any additional rule to the migration engine, enabling us to offer a functional transformation of the source scheduler into the target scheduler.

A specialized software for each step 

iCAN collects the scheduler definitions and batchs of the client, to meet the following needs :

  • Schedulers rules analysis,

  • Batchs analysis,

  • Data mapping and inventory,

  • Normalization,

  • Before-after comparisons.

uWME  is a universal migration engine. Attribute models allow the transformation of an source format into a target format, by going through a functional abstraction. The engine can assimilate any additional rule, allowing the integration of the clients' specifics to the migration.

30 Years

experience in scheduler migration

4 000 000

number of Jobs generated since the creation of uWME

20

100% mastered schedulers

Principle of operations

uwme photo.png

A functional approach

migr-pic1.png

 Functional migration

  • Technical migrations are inadequate and harm the understanding and scalability of the IT system,

  • Multiple functional alternatives can be suggested on a case-by-case basis.

migr-pic2.png

Any type of object

  • From a language structure to another

  • New models, parsers and generators can be easily developed

migr-pic3.png

Objective

  • The development of a rule or another is not different,

  • We provide recommendations, but in the end the final choice belongs to our customers.

  • Our goal: their satisfaction. 

Technical and functional tests
  • Scheduling rules are validated by comparing the 1-year forecast of both schedulers. The result is made available to the customer for validation purposes. 

  • Behaviors (e.g. : dependencies, utilities, commands) of the new scheduler are compared to the old one.

  • A "sandbox" environment is set up to replicate the customer's configuration.

  • The validation of the real execution of the scheduled jobs (e.g. : scripts, JCL, etc...) remains the responsibility of the client.

  • Reports and graphics are available to the client, in order to check the migration results, including a classification of every differences.

The schedulers currently covered

APM 

APX  

Automator

 

Automic WA

 

Autosys 

CA7 

 

CA-Scheduler

 

Control-M (z/OS and Open)

Crontab

HWA (z/OS and Open)

IWS (z/OS and Open) 

 

OpCon

OpenJobScheduler

 

PACEO

SAP SMC transaction

Schematics

TNG

$Universe

Visual TOM

Winat

?

Another perimeter to process? Its integration in the migration engine is performed within a month upon receiving the extractions and documentation.

bottom of page