Administration

As an administrator for a distributed relational database, you are responsible for work being done on several servers.

Work that originates on your local system as an application requester (AR) can be monitored in the same way as any other work is monitored on an iSeries™ server.

When you are tracking units of work being done on the local system as an application server (AS), you use the same tools but look for different kinds of information.

This topic discusses ways that you can administer the distributed relational database work being done across a network. Most of the commands, processes, and other resources discussed here do not exist just for distributed relational database use, they are tools provided for the operation of any iSeries server. All administration commands, processes and resources discussed here are included with the i5/OS™ licensed program, along with all of the DB2 Universal Database™ for iSeries functions. Work management functions on the iSeries server provide effective ways to track work on several servers.

• Monitor relational database activity
  You can rely on control language (CL) commands, all of which provide similar information, but in different ways, to give you a view of work on an iSeries server.
• Operate remote iSeries servers
  As an administrator in a distributed relational database you might have to operate a remote iSeries server.
• Control DDM conversations
  The term connection in this topic collection refers to the concept of an SQL connection. An SQL connection lasts from the time an explicit or implicit SQL CONNECT is done until the logical SQL connection is terminated by such means as an SQL DISCONNECT, or a RELEASE followed by a COMMIT.
• Display objects used by programs
  You can use the Display Program References (DSPPGMREF) command to determine which tables, data areas, and other programs are used by a program or SQL package. This information is only available for SQL packages and compiled programs and can be displayed, printed, or written to a database output file.
• Drop a collection from a distributed relational database
  Attempting to delete a collection that contains journal receivers might cause an inquiry message to be sent to the QSYSOPR message queue for the application server (AS) job. The AS and application requester (AR) job wait until this inquiry is answered.
• Job accounting in a distributed relational database
  The job accounting function on the iSeries server gathers data so you can determine who is using the server and what server resources they are using. Typical job accounting provides details on the jobs running on a server and resources used, such as use of the processing unit, printer, display stations, and database and communications functions.
• Manage the TCP/IP server
  This topic collection describes how to manage the DRDA/DDM server jobs that communicate using sockets over TCP. It describes the subsystem in which the server runs, the objects that affect the server and how to manage those resources.
• Audit the relational database directory
  This topic discusses how to audit program access to the relational database directories.