Central DBA Planning Calendar
The Central DBA Planning Calendar creates a single point of control for managing multiple databases in SAP system environments. It manages different types and versions of database systems. Generally, it also enables the administration of non-SAP databases.
However, DB2 UDB for z/OS databases can only be managed if they are SAP databases. The Central Planning Calendar can be especially beneficial for managing MCOD landscapes.
To use the Central DBA Planning Calendar, choose one of the following:
· Call transaction DB13C
· Call transaction DB2- Section Performance Tuning- choose Central Planning Calendar.
To manage a remote database using the Central DBA Planning Calendar, you need to set up an RFC connection to the system where the database is located using transaction SM59. The user specified for the RFC connection needs to have a valid TSO equivalent because the TSO user is used to submit scheduled JCL jobs.
Use DB13C, menu item configuration, to determine which systems to be displayed. Use for example ‘add systems’ to define the systems to be displayed in the calendar or use change or delete to update the list of systems.
Select Configuration ® copy system if you want to add systems that are already defined in the repository. See the SAP online documentation for more details.
To refresh the display of the system from which the Central DBA Planning Calendar has been called, choose Local on DB13C. The display for all remote systems can be refreshed using the Remote button. Three options are offered:
· Execute in Dialog (runs in dialog, takes a long time)
· Start in Background (runs immediately as background job)
· Schedule as Job (the scheduled jobs run daily at the specified time)
The execution state of the refresh jobs can be monitored on the local system by selecting
‘Display job log’.
To schedule actions, you select a database. This implicitly calls the DBA Planning Calendar of the selected database.
You can only schedule DBA actions of the database of the selected system. If a DBA action has been specified, you are prompted to select the database systems of the same type for which you want to schedule this action as well. This facilitates the scheduling of identical DBA actions on multiple databases. You can update or delete planned actions for remote systems on the Central Planning Calendar.

The DBA Planning Calendar of each database is also capable of running on SAP systems that make use of a different database.
You can monitor DBA actions for the database of the systems that have been registered using the Central Planning Calendar. The user interface of central and local DBA Planning Calendar are very similar. The main difference is that the central versions is only for viewing DBA actions by systems (from here you can easily switch to local version). The local version shows actions for one system. You can schedule, change, delete or execute actions there.
The Central Planning Calendar shows only jobs that have been submitted from DB13C - Local Calendar. Jobs submitted directly on the local Planning Calendar of a remote system are NOT shown when using DB13 - Local Calendar for that system.
They can only be monitored using DB13 on the remote system directly. You can use DB13C, menu item “Calendar - Calendar Display” to customize the screen to your needs. The number of weeks to be displayed and the number of lines per week can be changed and saved.
For each day, DB13C provides a summary of the DBA actions of each registered system.
The number of actions and the number of actions with the highest status severity are displayed for each system. Status color-coding for each system indicates if actions have been executed successfully.
By double-clicking an entry, you can display all actions for the databases.
See the SAP online documentation for more information on the Central Planning Calendar.
You can monitor DBA actions for the databases that have been registered using the Central DBA Planning Calendar.
For each day, it provides a summary of the DBA actions of each database. By doubleclicking an entry, you can display all actions for that database.
To schedule actions, you select a database. This implicitly calls the DBA Planning Calendar of the selected database.
You can only schedule DBA actions of the selected database. If a DBA action has been specified, you are prompted to select the database systems of the same type for which you want to schedule this action as well. This make is easier for you to schedule identical DBA actions on multiple databases.
