Earlier this year, in March 2020, we have published a blog entry about the new implementation of the Database Migration Option (DMO) in the SAP Software Update Manager (SUM) for the combined upgrade and conversion from SAP on IBM i to SAP S/4HANA release 1909 or higher. In this scenario, the SUM is running on a Windows application server instead of the IBM i application server. On October 5th, 2020, the new SAP Software Logistics Toolset 1.0 SPS 30 was released, providing a refined procedure for the described scenario. Together with the new toolset, we published two SAP Notes which describe important post-DMO steps after the SUM procedure has finished.
SAP Note 2835839 – Plans for Upgrade/Conversion to SAP S/4HANA 1809 and Higher for Systems on the IBM i Platform
In this SAP Note, y ou can find the details about the planning of a SUM procedure if you want to use the DMO function to switch the database from IBM Db2 for i to SAP HANA and upgrade to SAP S/4HANA. Refer to the SAP Note and its attached PDF documents to get detailed information about the preparation of a Windows application server for the execution of the SUM, the importance of the option “ASCS Move” during the SUM procedure and a description about manual post-DMO steps to move the SAPGLOBALHOST after the SUM procedure has successfully finished.
SAP Note 2957193 – IBM i: Uninstalling the SAP source system after the DMO to SAP S/4HANA 1809 and higher
After a database migration from Db2 for IBM i to SAP HANA, you must uninstall the remaining SAP instances running on IBM i. This is done as usual with the SAP Software Provisioning Manager (SWPM). Before you can start the uninstall, the instances of the SAP source system and their configuration must be prepared in order to avoid damages in the configuration of the migrated SAP S/4HANA target system. This includes a cleanup of SAP profiles as well as the shutdown of remaining processes running on IBM i. Warning: Start the uninstall of the SAP source system only after the SAPGLOBALHOST of the new SAP S/4HANA system has been moved already. Otherwise, your S/4HANA system will be damaged!