Administration

 

As an administrator for a distributed relational database, you are responsible for work that is done on several systems.

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 the i5/OS^® operating system.

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 any i5/OS operations. 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. The i5/OS work management functions provide effective ways to track work on several systems.

• Monitoring relational database activity
  You can use control language (CL) commands, all of which provide similar information, but in different ways, to give you a view of work on the i5/OS operating system.

• Operating remote systems
  As an administrator in a distributed relational database, you might have to operate a remote System i™ product.

• Controlling 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.

• Displaying 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.

• Dropping 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 i5/OS job accounting function gathers data so you can determine who is using the system and what system resources they are using.

• Managing the TCP/IP server
  The DRDA^® and DDM TCP/IP server does not typically require any changes to your existing system configuration. At some time, you might want to change the way the system manages the server jobs to better meet your needs, to solve a problem, to improve the system performance, or to look at the jobs on the system.

• Auditing the relational database directory
  This topic discusses how to audit program access to the relational database directories.

 

Parent topic:

Distributed database programming

 

Related tasks

Setting up DDM files