TADDM 7.3.0 FP7 - Problems with discovery after installing Fix Pack 7

Problem

Unable to start discovery run after migrating to new TADDM fixpack

Symptom

When attempting to run a discovery on any of the Discovery Servers after migrating, the following error occurs:

MESSAGE OF ERROR:
=================
CTJOX0991E THE REQUESTED OPERATION CANNOT BE PERFORMED BECAUSE A
DATABASE MIGRATION IS IN PROGRESS.

Diagnosing The Problem

Check migration.log to ensure no errors occurred during the fixpack application. Check in the end of the migration.log for the following statement 'completed successfully'. If there are no error's and the migration did complete successfully, TADDM has only failed to move the 'in progress' status of the migration to 'COMPLETE'

Resolving The Problem

Run the following command to resolve the issue, according to the operating system, to change
the upgrade status to COMPLETED, which enables the TADDM processes to operate:
For Linux and UNIX systems:
/opt/IBM/taddm/dist/bin 

migration.sh -e
For Windows systems:
migration.bat -e

mboSet() in Automation Script, getMboSet() vs getThisMboSet() | Maximo

Most of the time automation script creates an implicit variable "mbo". It represents the current record on which the script was triggered. 

let say we open one workorder: 123. in this case, our mbo is 123. 

what If we want to get the MboSet of this mbo. (like we are going back to the list tab :)

here you go. 

mboSet = mbo.getThisMboSet()

2. Most common way to call an mboset is using famous method , which is

mbo.getMboSet("PR")

where PR is the Relation Name already exists in database configuration from this record. 

3. or we can create at run time a new relation with WhereClause, like this:

 woSet = mbo.getMboSet("woSet ", "WORKORDER", "status = 'APPR' and siteid = 'BEDFORD'")

4th and last is get any MBO from the system, which is the least recommended if the things can be handled with first 3 methods.  

If the "mbo" implicit variable is not exists then you need this:

woSet = MXServer.getMXServer().getMboSet("WORKORDER", userInfo)