Change management on SAP Central Services hosts

Edit online

This topic describes several tasks that you must perform before you can safely apply service and maintenance to z/OS® or to the hardware (LPAR) that runs your SAP central services. To keep your business operating continuously and secure, all SAP software should be stopped and/or moved away from the operating system and the LPAR that require service. This includes, for example, the SAP Central Services and the SAP control function for z/OS remotely managed SAP application servers.

At first, move the control function of an SAP application server managed remotely from SA z/OS.

The following command samples assume that you have implemented the *SAPSRV add-on policy for remotely managed SAP application servers. Log on to a NetView command session (SA z/OS command dialog) and list the remotely managed SAP AS application MOVE groups to get an overview. Issue INGMOVE SAP<SID>RM*.

  1. Find the MOVE group that is displayed with an observed status of AVAILABLE on the system that you would like to stop for maintenance. Move that group to a system from which you know it will stay up and available during the maintenance. A list of possible systems is displayed beneath the headline System.
  2. Type a target system name into column Move to, then type m into the command column.
  3. Press the Enter key and verify the selection. Then, press PF10 to actually start the move.
  4. Use PF9 to refresh the status until the move successfully completes. Now all resources used to control the remotely managed SAP AS should be off that system.
  5. Verify the result with command INGLIST SAP<SID>R*.

The second step is to move SCS away from the LPAR as described in Updating SAP central services components.

Now you can continue with other tasks for preparing the maintenance. After maintenance is complete, you can use the same procedure to move the control function back.