Usage  >  Migrations >  Sequencing monitor  

Display all Hide all

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)

This field identifies the migration plan code (it is the default folder code).
  • Description (field INTIT)

Use this field to assign a description to each record.
  • Folder (field DOSSIER)

Define the folder code, as it is defined in the folders table, in which the work will be carried out.
  • No. of parallel launches (field NBPARL)

This value defines the maximum number of migration tasks likely to be launched in parallel. This number cannot exceed the number of authorized batch tasks. At a given moment in the migration, it cannot exceed the number of tasks of the current phase of the stage under progress.
  • Phase auto start (field PHASEAUTO)

When this box is selected, the phases follow each other automatically: when all the procedures of a migration phase are completed, the next phase is launched automatically. If the box is not selected, the user will have to use the corresponding button to relaunch the execution from the migration workbench.

This box is selected by default if the plan is created automatically via folder validation.
  • Post-migration auto start (field POSTAUTO)

When this box is selected, the procedures of the post-migration stage are automatically launched once the procedures of the previous phases and stages have been completed (otherwise, they will need to be launched manually from the workbench).

This box is selected by default if the plan is created automatically via folder validation.

Monitor

  • Global status (field STATUT)

This indicator provides the global status of the migration plan. The values can be the following:

  • Pending: the plan is ready to be launched.
  • In progress: at least one migration procedure is still in progress.
  • Completed: all the procedures of the migration plan have been completed successfully.
  • Completed with errors: at least one migration procedure has failed. As a consequence the procedures of the following phases could not be launched. The error will need to be fixed. This error is often linked to the data processed during the failed procedure). The procedure in question will then need to be relaunched for the migration to continue.
  • Interrupted: the user has launched the migration, then they have interrupted it: the button Resume will need to be used for the migration to resume.
  • Pending interruption: the user has requested that the migration be interrupted. Nevertheless some of the procedure have not finished processing the current group of data before being interrupted.
  • Pending stop: the user has requested that the migration be stopped, but the order is not effective yet.
  • Launched: the migration has been launched but no task has started yet.
  • Launch date (field DATEL)

This displayed field is used to indicate the time of launch of the migration.
  • Launch time (field HEUL)

This field is used to indicate the time of launch of the migration.
  • Global time (hhh:mm) (field ELAPSEDG)

This field specifies the total time spent since the start of the migration. This time corresponds to the difference between:

  • the end date and time if the execution of the plan is over,
  • the current date and time if the execution of the plan is not over.

the start date and time.

In other words, it does not represent a totaled execution time taking the real execution times into account.
  • Pending (field NBM1)

This field specifies the number of pending migration tasks.
  • Launched (field NBM8)

This field specifies the number of launched migration tasks.
  • In progress (field NBM2)

This field specifies the number of migration tasks in progress.
  • Completed (field NBM3)

This field specifies the number of migration tasks which have ended without errors.

  • Completed with errors (field NBM4)

This field specifies the number of migration tasks which have ended with errors.

  • Bypassed (field NBM11)

This field specifies the number of bypassed migration tasks.
  • Pending interruption (field NBM6)

This field specifies the number of migration tasks pending interruption.
  • Pending stop (field NBM7)

This field specifies the number of migration tasks pending stop.
  • Interrupted (field NBM5)

This field specifies the number of interrupted migration tasks.
  • Blocked (field NBM10)

This field specifies the number of blocked migration tasks.

Control

  • Launch/resume (field ACTIV)

This button is used to launch the migration, or resume it if it had been previously interrupted.
  • Interrupt (field INTERR)

This button is used to interrupt all the migration procedures being executed. The interruption of a task does not necessarily have an immediate effect. Indeed, a task processes the lines in the database by groups (the number of processed lines appears in the screen). With this button, an interruption order is sent to the task, and said task ends the group of lines in progress before stopping.

It will thus be possible to resume the execution of a migration procedure with the next group of data.
  • Suspend launches (field ARRET)

This button is used to stop the launch of migration procedures. In other words, the already launched batch tasks will be completed, but no new task linked to a migration procedure of the plan will be launched.
  • Refresh (field RAFR)

This button is used to refresh the grid that lists the procedures in progress, their status and the number of processed lines.
  • Block all (field BLOQUER)

This button is used to block all the procedures in progress. A blocked procedure will not be launched, even if it could be because the migration terms would allow it (i.e. the former stages and phases are completed). It is possible to individually unblock a blocked procedure by right-clicking on the line.
  • Unblock all (field DEBLOQUER)

This button is used to unblock all the blocked procedures. It is possible to unblock tasks individually by right-clicking on the line.

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 :

Grid

  • Code (field CODE)

This code identifies the current migration procedure in a unique way.
  • Status (field STATUTM)

This flag specifies the status of the procedure defined on the line. The values can be the following:

  • Pending: the procedure is ready to be launched.
  • In progress: the migration procedure is still in progress.
  • Completed: the migration plan procedure has ended successfully.
  • Completed with errors: the migration procedure has failed. As a consequence the procedures of the following phases could not be launched. The error will need to be fixed. This error is often linked to the data processed during the failed procedure). The procedure in question will then need to be relaunched for the migration to continue.
  • Interrupted: the user has launched the migration, then they have interrupted it: the button Resume will need to be used for the migration to resume.
  • Pending interruption: the user has requested that the migration be interrupted. Nevertheless the procedure has not finished processing the current group of data before being interrupted.
  • Pending stop: the user has requested that the migration be stopped, but the order is not effective yet.
  • Launched: the procedure has been launched but has not started yet.
  • Stopped: the procedure is stopped.
  • Blocked: the procedure has the Blocked status. The procedure needs to be unblocked to resume.
  • Bypassed: the procedure has ended with errors, but the user has bypassed it manually (the decision is their responsibility), considering that the errors reported during this procedure do not jeopardize the execution of the remaining phases of the migration plan.
  • Description (field INTITM)

Use this field to assign a description to each record.
  • Step (field RANGMOD)

Specifies the procedure stage number.
  • Module (field MODULE)

Select a module for the setup.

Use this field to specify if the screen has to be created in the folder database. This is the case when the module linked to the screen is active on the folder.
  • Index (field INDICEM)

 
  • Phase (field PHASE)

The phase is a number likely to vary from 1 to 9. It enables the strict scheduling of the migration procedures. The next phases cannot be launched as long as all the procedures of a phase are not completed.
The phase cannot be modified for a standard procedure.
  • Sequence (field RANG)

The rank represents a number likely to vary from 1 to 99. It provides a preferential order to launch a migration procedure in a phase and for a given module. This rank can be modified for the standard procedures.
  • No. processed (field NBENREGT)

Specifies the number of lines already processed during the migration procedure.
  • No. to process (field NBENREG)

Specifies the number of lines to process during the migration procedure.
  • Time spent (field ELAPSED)

This value determines the time (in hours and minutes) spent on this procedure.

This field specifies the total time spent since the start of the procedure. This time corresponds to the difference between:

  • the end date and time if the procedure is over,
  • the current date and time if the procedure is not over.

the start date and time.

In other words, it does not represent an execution time totaled for this procedure and taking the real execution times into account.
  • Launch date (field DATELM)

This field indicates the launch date of the procedure.
  • Launch time (field HEULM)

This field indicates the launch time of the procedure.
  • Update date (field DATEMAJ)

This field indicates the last update date of the procedure status.
  • Update time (field HEUMAJ)

This field indicates the last update time of the procedure status.

Close

 

Action icon

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

 

Close

 

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)

File or table space used for the indices of the migration tables starting with U.
  • Index (field IDXFIL)

File or table space used for the indices of the migration tables starting with U.

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 :

Grid

  • Plan (field MPLAN)

This field identifies the migration plan code (it is the default folder code).
  • Folder (field MDOSSIER)

Define the folder code, as it is defined in the folders table, in which the work will be carried out.
  • Status (field MSTATUT)

This indicator provides the global status of the migration plan. The values can be the following:

  • Pending: the plan is ready to be launched.
  • In progress: at least one migration procedure is still in progress.
  • Completed: all the procedures of the migration plan have been completed successfully.
  • Completed with errors: at least one migration procedure has failed. As a consequence the procedures of the following phases could not be launched. The error will need to be fixed. This error is often linked to the data processed during the failed procedure). The procedure in question will then need to be relaunched for the migration to continue.
  • Interrupted: the user has launched the migration, then they have interrupted it: the button Resume will need to be used for the migration to resume.
  • Pending interruption: the user has requested that the migration be interrupted. Nevertheless some of the procedure have not finished processing the current group of data before being interrupted.
  • Pending stop: the user has requested that the migration be stopped, but the order is not effective yet.
  • Launched: the migration has been launched but no task has started yet.
  • Description (field MINTIT)

Use this field to assign a description to each record.
  • Launch date (field MDATEL)

This displayed field is used to indicate the time of launch of the migration.
  • Launch time (field MHEUL)

This field is used to indicate the time of launch of the migration.
  • Update date (field MDATEEC)

This displayed field is used to indicate the last time of update of the migration.
  • Update time (field MHEUEC)

This field is used to indicate the time of update of the migration.
  • Time spent (field MELAPSED)

This field specifies the total time spent since the start of the migration. This time corresponds to the difference between:

  • the end date and time if the execution of the plan is over,
  • the current date and time if the execution of the plan is not over.

the start date and time.

In other words, it does not represent a totaled execution time taking the real execution times into account.
  • Phase auto start (field PHASEAUTO)

When this box is selected, the phases follow each other automatically: when all the procedures of a migration phase are completed, the next phase is launched automatically. If the box is not selected, the user will have to use the corresponding button to relaunch the execution from the migration workbench.

This box is selected by default if the plan is created automatically via folder validation.
  • Post-mig auto start (field POSTAUTO)

When this box is selected, the procedures of the post-migration stage are automatically launched once the procedures of the previous phases and stages have been completed (otherwise, they will need to be launched manually from the workbench).

This box is selected by default if the plan is created automatically via folder validation.

Close

 

Action icon

Deletion

Used to delete a plan.

Log

Used to view the execution log of a migration plan.

 

Close

 

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