MainView AutoOPERATOR Total Object Manager (TOM) 2.2 gets improved Move function

Version 1
    Share:|

    PTF BQO1108 provides additional capabilities to the MOVE function for Total Object Manager 2.2.  This PTF is currently available via the 1301B PUT service.  After this PTF has been applied users will be able to:

    • Set the scope of the objects to be moved to the selected object and its dependents.  Previously a move could only take place for the selected object.
    • Move an object that is not currently active on any system named in its valid system list (VSL).  Without BQO1108 an object could only be moved from a system that it was active upon to another system in its VSL where TOM was running.

    Move an Object and Its Dependents

    Previously users could only move a selected object that was active on a system in the TOMPLEX.  If you needed to move that object and its dependents you were required to determine the names of the objects involved, stop those objects in dependency order and then restart them in dependency order on the target system.  Such a sequence of actions is very difficult to perform successfully.  It certainly cannot be done in a single request. 

    The Move with Dependents function allows a user to move a selected object and its dependents in a single request.  Imagine that the active definition base had the following objects:

    TOBJOR.PNG

    The objects have the following dependency structure:

    MAMKZ001

    |

    MAMKZ002

    |

    MAMKZ003

    |

    MAMKZ004

     

    Each object had the following systems specified in their VSL:

    TVSYSR.PNG

    You want to move MAMKZ001 and its descendents from system SJSC to system SJSD.

    Start by issuing the MOVE line command from the TOBJO or TOBJOR views against the MAMKZ001 object.  This will lead to the following confirmation panel being issued:

    Move Confirmation.PNG

    Set ‘Proceed with move’ to ‘Y’, ‘Move dependents’ to ‘Y’ and ‘System name’ to 'SJSD' and issue the END primary command.  TOM will stop the objects in dependency order.  Each object will have its status set to ‘BLOCKED’ on each system specified in its VSL.  After the selected object and its descendents have been stopped on SJSC they will be started in dependency order on SJSD.

    If a descendent does not have the system named in the ‘System name’ field in its VSL then that descendent will be started on the first active system in its VSL when the move request is made.  So, to use our example above if we were to move MAMKZ001 and its descendents to SJSD but MAMKZ003 did not have SJSD in its VSL then all of the objects would be stopped and all of them would be restarted on SJSD except for MAMKZ003.  It would be restarted on SJSC since the first active system in its VSL was SJSC.

    Move with dependents can also be done with either a console command or an API call. 

    The API call to move MAMKZ001 and its descendents is as follows:

    TOMEXEC FUNC(MOVE) OBJECT=MAMKZ001 HOST=SJSC TOHOST=SJSD MOVEDEPS

    The console command to move MAMKZ001 and its descendents is as follows:

    F <tom identifier>,CMD MOVE OBJECT=MAMKZ001 HOST=SJSC TOHOST=SJSD MOVEDEPS

    Warning - If a RESET command with RESETOPT=ALL or RESETOPT=STATUS is issued against any of the objects involved with the move after they have been restarted then that object and its descendents will stop on the system they were moved to and restart on the first active system in their VSL.        

    Move an Inactive Object

    Previously users could only move a selected object that was active on a system in the TOMPLEX.  If that object was inactive for whatever reason you needed to first start the object and then issue a move request to start that object on another system named in the object’s VSL.  Another possible solution was to un-lock or un-block the object on the target system.   

    This requirement changes with the application of BQO1108.

    Let’s say that you wish to move object MAMKZ004 from SJSC to SJSD.  The object is not active on any of the systems listed in its VSL.  How can you accomplish this? 

    Start by issuing the MOVE line command from the TOBJO or TOBJOR views against the MAMKZ004 object.  This will lead to the following confirmation panel being issued:

     

    Move Confirmation 2.PNG

    Set ‘Proceed with move’ to ‘Y’, ‘Move inactive’ to ‘Y’ and ‘System name’ to 'SJSD' and issue the END primary command. The object will have its status set to ‘BLOCKED’ on each system specified in its VSL. 

    TOM will attempt to start the object in dependency order on SJSD after the status has been changed if its dependency and schedule criteria have been met.

    If TOM is active on SJSD then the object will be started on the named system if that system is in the object’s VSL.  If TOM is not active on that system then an exception will occur and return code 137 will be issued.  No change will be made to the selected object. 

    To move an inactive object and its descendents then you will need to also set ‘Move dependents’ to ‘Y’.  If you are using the API or a console command to perform the move function then you will need to add the MOVEDEPS parameter.

    Move for an inactive object can also be done with either a console command or an API call. 

    The API call to move MAMKZ001 when it is inactive is as follows:

    TOMEXEC FUNC(MOVE) OBJECT=MAMKZ001 HOST=SJSC TOHOST=SJSD MOVEINACT

    The console command to move MAMKZ001 when it is inactive is as follows:

    F <tom identifier>,CMD MOVE OBJECT=MAMKZ001 HOST=SJSC TOHOST=SJSD MOVEINACT

    Warning - If a RESET command with RESETOPT=ALL or RESETOPT=STATUS is issued against the object involved with the move after it has been restarted then that object will stop on the system it was moved to and will restart on the first active system in its VSL.