R/3 Database Detection
Not all the databases at a company are R/3 databases. Therefore, it is necessary to ensure that SAP-DB2admin is used only for those databases that are R/3 databases.
This problem is solved partly by the program logic and partly through the use of a configuration file.
The program logic does the following to determine whether or not a database is an R/3 database.
If these criteria are met, it is assumed that the database is an R/3 database.
However, for certain special databases, this program logic can be overwritten. A configuration file is used for this. This file is located in the executables directory of the DB2 database. Assuming the database software is installed on the C: drive in the \sqllib directory, the file will be located in c:\sqllib\bin\r3db.db2 . The name of the file is r3db.db2 .
The file consists of a number of lines, each of which describes a database. First of all, the fully qualified database name is given, for example "P24190.DB2DB2.DB2". In this case, there is a database "db2" on the instance "db2db2" which is on a system "P24190". The separate parts of the fully qualified name are separated by means of a period (.). The name itself is followed by a colon (:), which is followed, in turn, by an upper-case "Y" or "N". "Y" signifies that the database is an R/3 database; "N" that the database is not an R/3 database and, consequently, that no SAP-DB2admin functions are provided. The full entry in the file for the database in our example would be:
Editing the Configuration File for R/3 Database Detection