!--a11y-->
The DBA
Cockpit (DB2 UDB for UNIX and Windows) 
You can access all monitoring and database administration tasks in CCMS using the DBA Cockpit.
The DBA Cockpit is a navigation frame that appears on each DB2 UDB for UNIX and Windows CCMS screen. The frame holds a tree structure, which is divided at the top level into the main task areas of database administration. These are:
|
Task Area |
Transaction |
|
ST04 |
|
|
DB02, DB20 |
|
|
DB12 |
|
|
DB03, DB21 |
|
|
Jobs (DBA Planning Calendar) |
DB13, DB24 |
|
DB16, DB17 |
|
|
DB6COCKPIT |
Within each task area there is a set of related action nodes.
You can access the DBA Cockpit by either calling transaction DB6COCKPIT or any of the transactions listed above. The initial screen Diagnostics: Single System Check appears. For more information, see Diagnostics: Single System Check.
On most screens a group box is displayed providing system information. The following fields appear on each screen:
|
Field |
Description |
|
System |
Name of the currently monitored system. If more than one system is configured, you can change your selection by using the corresponding list box. |
|
Partition |
Currently selected partition (node). If you are using a multi-partition database, you can choose other partitions from the corresponding list box. |
You can use the DBA Cockpit to:
· Navigate between different actions.
· Change to another action without closing the previous action and still hold all data retrieved by this action. You can return to this action without any loss of data by double-clicking the previous action in the navigation frame or by choosing Back.
· Handle central CCMS configuration.
· Monitor remote systems via RFC connections or remote database connections.
To use the functions offered for remote monitoring, you must configure the system you want to monitor. The local system is configured automatically when you start the DBA Cockpit for the first time.
In addition, the DBA Cockpit requires a set of user-defined functions (UDFs), which are normally configured automatically. If problems occur when starting the DBA Cockpit, you can check and reconfigure the user-defined function libraries. For more information, see Configuration: Monitoring Settings.
Depending on the remote connection you are using for monitoring, the following constraints apply:
· In general, the administration of RFC-monitored systems is downward-compatible in a way that you can also monitor SAP systems with a lower release than the current one. However, for new functions or for functions, which were extended with new screens, you have to take the following into consideration:
¡ The value for a new field might not be displayed or a wrong initial value is displayed.
¡ Some functions might be deactivated.
¡ If you have chosen a function and you want to switch from system “x” to system “y” but the function you have chosen is not supported for system “y” (due to a different release number), this action is not possible. In this case, an error message is displayed. The same applies if you want to switch between two functions and one of them is not supported.
· For systems that are monitored using a remote database connection, constraints depend on whether:
¡ The database release number of the remote system is compatible to the database release number of the local system.
¡ You want to monitor an ABAP-only SAP system or an Java-only SAP System.
