Usage > Migrations > Sequencing monitor 

This function can only be used in the supervisor folder. It makes it possible to define and monitor the execution of all the migration procedures for a given folder.

To that end, a migration plan will be created and identified using a code. The code to use is free. Nevertheless it is possible to customize the migration terms for a given folder. To that end, a migration plan will be created with the same code as the one for the folder to be migrated, and it will be then put on hold.

Otherwise, when the migration of a given folder is launched (via the folder revalidation function), a migration plan called MIGmmdd##(mm and dd being the numbers of the month and day of launch, and ## being a sequence number) is automatically created and launched.

The creation of a migration plan will duplicate all the procedures defined in the procedure table into a scheduling table whose lines are displayed in this screen

It will then be possible to manually launch and control the sequencing of the operations, interrupt them and start them again, and also check the generated log.

Screen management

The function screen contains a header with all the information concerning the current execution plan, a first tab displaying the detail of the operations, and a second tab listing the other migration plans and their status.

Header

Presentation

The header makes it possible to define the general parameters according to which the migration plan will be executed, the status of the current migration, and a set of control buttons.

Close

 

Fields

The following fields are present on this tab :

Identification

  • Plan (field PLAN)
  • Title (field INTIT)

It used to define a name associated with each record.

  • Folder (field DOSSIER)

Define the code of the folder in which the work will be carried out (such as it is defined in the table of the folders).

  • No. of parallel launches (field NBPARL)
  • field NBPROPAR
  • field NBLICBATCH
  • Phase auto start (field PHASEAUTO)
  • Post-migration auto start (field POSTAUTO)

Monitor

  • Global status (field STATUT)
  • Launch date (field DATEL)
  • Launch time (field HEUL)
  • Global time (hhh:mm) (field ELAPSEDG)
  • Pending (field NBM1)
  • Launched (field NBM8)
  • In progress (field NBM2)
  • Completed (field NBM3)
  • Completed with errors (field NBM4)
  • Bypassed (field NBM11)
  • Pending interruption (field NBM6)
  • Pending stop (field NBM7)
  • Interrupted (field NBM5)
  • Blocked (field NBM10)

Control

  • Launch/resume (field ACTIV)
  • Interrupt (field INTERR)
  • Suspend launches (field ARRET)
  • Refresh (field RAFR)
  • Block all (field BLOQUER)
  • Unblock all (field DEBLOQUER)

Close

 

Tab Monitor

Presentation

This header displays the status of the migration procedures. Each line in the grid is devoted to a specific procedure.

Close

 

Fields

The following fields are present on this tab :

Table

  • Code (field CODE)
  • Status (field STATUTM)
  • Title (field INTITM)

It used to define a name associated with each record.

  • Step (field RANGMOD)
  • Module (field MODULE)

Module belonging to the setup. This field is used to specify whether the screen has to be created in the folder database. It is specified when the module linked to the screen is active in the folder.

  • Index (field INDICEM)

 

  • Phase (field PHASE)
  • Sequence (field RANG)
  • No. processed (field NBENREGT)
  • No. to process (field NBENREG)
  • Time spent (field ELAPSED)
  • Launch date (field DATELM)
  • Launch time (field HEULM)
  • Update date (field DATEMAJ)
  • Update time (field HEUMAJ)

Close

 

Functions accessed by right click on the grid

Resume

Used to resume the execution of a procedure that has been interrupted. Resumption starts with the first piece of data not processed by the procedure yet.

Interrupt

Used to interrupt the execution of a migration procedure.

Log

Used to display the execution log of a procedure.

Restart

Used to restart the execution of a procedure (in other words, resume the execution from the start, by starting from an empty destination table and using all the data to be transcoded).

Block

Used to block a migration procedure that would not have been launched, i.e. prohibit its execution, even if the scheduling terms would have allowed for its launching. As a consequence, the execution of the procedures in earlier stages or phases is not authorized. As a matter of fact, the blocked task will need to be unblocked, and then executed, before the sequencing terms can apply again.

Unblock

Used to unblock a blocked migration procedure.

Bypass

Used to proceed with the next procedure stages or phases even when the previous procedure has ended with errors.

Warning! It is recommended to properly understand the potential risks before bypassing a migration procedure. Bypassing a migration procedure can have side effects for the next procedures and lead to an improperly migrated folder.

Relaunch with new filter

 

Fermer

 

Tab Options

Presentation

This tab is used to specify the table spaces (for Oracle) or the data files (for SQL Server) used for the data and indices of the temporary tables (starting with U) within the framework of the migration. It must be documented on creating a migration plan. Otherwise, the default table spaces and data files of the folder will be used.

Close

 

Fields

The following fields are present on this tab :

  • field INTITFIL

 

  • Data (field DAAFIL)
  • Index (field IDXFIL)

Close

 

Tab Plan list

Presentation

This tab lists the available migration plans and displays their status.

Close

 

Fields

The following fields are present on this tab :

Table

  • Plan (field MPLAN)
  • Folder (field MDOSSIER)

Define the code of the folder in which the work will be carried out (such as it is defined in the table of the folders).

  • Status (field MSTATUT)
  • Title (field MINTIT)

It used to define a name associated with each record.

  • Launch date (field MDATEL)
  • Launch time (field MHEUL)
  • Update date (field MDATEEC)
  • Update time (field MHEUEC)
  • Time spent (field MELAPSED)
  • Phase auto start (field PHASEAUTO)
  • Post-mig auto start (field POSTAUTO)

Close

 

Functions accessed by right click on the grid

Deletion

Used to delete a plan.

Log

Used to view the execution log of a migration plan.

 

Fermer

 

Specific Buttons

Used to view the global log compiling all the migration procedures. This log can only be used if the migration has been launched in batch mode (usually via the folder validation).

This global log is updated at the end of each migration procedure, by adding to it the log lines of the procedure concerned. The procedures are thus displayed in the order in which they have ended. If a procedure is relaunched several times (further the a manual intervention on the plan), the log will display the procedure details several times but one line will specify "Initial launch" on the first launch, and the other lines will specify "Relaunch N" if it is the Nth relaunch.

Used to zoom in onto the batch request management.

Used to create the plan record.

Used to save modifications to a plan record.

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

Program is already in progress

An attempt is made to launch a migration procedure which is already being executed.

Do you wish to put back on hold the interrupted procedures and back into progress the procedure pending interruption?

This message is displayed in the form of a confirmation request when a plan is reactivated.

Launch cannot be carried out

This message is displayed when an attempt is made to launch a plan despite its execution terms not being complied with.

Do you want to launch plan xxx?

This message is displayed to request confirmation when launching a plan.

Do you want o resume plan execution xxx?

This message is displayed to request confirmation when resuming the execution of a plan.

Do you want to stop plan in progress (extractions in progress will be ended)?

This message is displayed to request confirmation when stopping a plan.

Do you want to interrupt the plan in progress (extractions in progress will be interrupted)?

This message is displayed to request confirmation when interrupting a plan.

Plan does not exist

This message is displayed when a non-existent plan code is entered while not being in plan creation mode.

You can only resume a process that was stopped, bypassed, or faulty

This message is displayed when an attempt is made to resume a migration which is neither stopped nor faulty.

Do you want to resume from the last stop in procedure xxx?

This message is a confirmation request when a unitary procedure needs to be resumed.

Do you want to restart from the beginning procedure xxx?

This message is a confirmation request when a unitary procedure needs to be relaunched.

Do you also want to restart all the lower rank procedures that are over or interrupted?

This message is displayed when a procedure is relaunched from the start, although higher rank phases or stages have already been executed. It is then possible to relaunch at the same time all the procedures of the next phases or stages, either ended (with or without errors) or interrupted, by answering Yes to the question.

You can only block a pending procedure

This message is displayed when an attempt is made to block a procedure that is not pending.

Do you want to block the whole phase?

This message is displayed when a procedure is blocked within a phase. In case of a positive answer, all the procedures of the current stage and of the phase concerned will be blocked.

You can only unblock a blocked procedure

This error message is displayed when an attempt is made to unblock a procedure which is not blocked.

Do you want to unblock the whole phase?

This message is displayed when a procedure is unblocked within a phase. In case of a positive answer, all the procedures of the current stage and of the phase concerned will be unblocked.

Do you confirm plan deletion xxx?

This message is used to confirm the deletion of a plan when said deletion has been requested.

Caution, your license is limited to ### batch tasks

This error message is displayed when an attempt is made to set up a number of simultaneous tasks larger than authorized by the license.

Caution, the parameters used only allow parallel launching of ### batch tasks

This error message is displayed when an attempt is made to set up a number of simultaneous tasks larger than the number of simultaneous batch tasks defined by the batch server setup.

Are you sure you want to bypass this procedure and consequently unblock the execution of the following phases?

This error message is displayed when an attempt is made to bypass a procedure whose execution has generated errors.

Tables used

SEEREFERTTO Refer to documentation Implementation