DB2 Version 9.7 for Linux, UNIX, and Windows

DB2 Administration Server

The DB2® Administration Server (DAS) is a control point used only to assist with tasks on DB2 database instances. You must have a running DAS if you want to use available tools like the Configuration Assistant, the Control Center, or the Development Center.

Important: The DB2 Administration Server (DAS) has been deprecated in Version 9.7 and might be removed in a future release. The DAS is not supported in DB2 pureScale™ environments. Start using software programs that use Secure Shell protocol for remote administration. For more information, see DB2 Administration Server (DAS) has been deprecated.

Figure 1. Where DAS is used
Table showing where DAS is used on Windows, UNIX, and Linux DB2 systems.

DAS assists the Control Center and Configuration Assistant when working on the following administration tasks:

You can only have one DAS in a database server. If one is already created, you need to drop it by issuing db2admin drop. DAS is configured during installation to start when the operating system is booted.

DAS is used to perform remote tasks on the server system and the host system on behalf of a client request from the Control Center, the Configuration Assistant, or any of the other available tools.

The DAS is available on all supported Windows and UNIX platforms as well as the zSeries® (OS/390® and z/OS® only) platforms. The DAS on zSeries is used to support the Control Center, Development Center, and Replication Center in administrative tasks.

The DB2 administration server on zSeries (OS/390 and z/OS only), will be packaged and delivered as part of the DB2 Management clients feature of the DB2 system. Products that need DAS, like the Control Center, Replication Center, and Development Center, require the installation of the DAS function. For information on the availability of DAS on your operating system, contact your IBM representative.

The DAS on Windows and UNIX includes a scheduler to run tasks (such as DB2 database and operating system command scripts) defined using the Task Center. Task information such as the commands to be run; schedule, notification, and completion actions associated with the task, and run results are stored in a set of tables and views in a DB2 database called the Tools Catalog. The Tools Catalog is created as part of the setup. It can also be created and activated through the Control Center, or through the CLP using the CREATE TOOLS CATALOG command.

Although a scheduler is not provided on zSeries (OS/390 and z/OS only), you can use the Build JCL and Create JCL functions provided in the Control Center to generate JCL that is saved in partitioned datasets to be run using your system scheduler.