Effects of distributed data on programming

There are several effects that you must be aware of when you write programs for a distributed environment.

Keep in mind the following considerations when you write programs that are used in a distributed environment:

• Stored procedures

  If you use DRDA access, your program can call stored procedures. Stored procedures behave like subroutines that can contain SQL statements and other operations.

• Three-part names and multiple servers

  Assume that a statement runs at a remote server (server 1). That statement uses a three-part name or an alias that resolves to a three-part name. The statement includes a location name of a different server (server 2). To ensure that access to the second remote server is by DRDA access, bind the package that contains the three-part name at the second server.

• SQL differences at servers other than Db2 for z/OS®

  With explicit connections, a program that uses DRDA access can use SQL statements that a remote server supports, even if the local server does not support them. A program that uses three-part object names cannot execute non-z/OS SQL.