The *LOCAL directory entry

The directory entry containing *LOCAL is unique in that there is only one such entry in the directory, and that it specifies the name of the local system database.

The associated RDB name can be used in the SQL statement CONNECT TO xxx (where xxx is the local system name) to connect to the local database. The effect of CONNECT TO xxx is equivalent to using the SQL statement CONNECT RESET.

If you want to make a DRDA connection to the local system database, such as for program testing, there are two special RDB names that can be used for that purpose: ME and MYSELF. For example, a programmer adds a directory entry with an RDB name of ME, with type of *IP, and with the Remote Location name of LOOPBACK. The programmer can then, in a program, run an SQL CONNECT TO ME statement and establish a sockets DRDA connection to the local system. However, general use of these RDB names is discouraged and they are documented only to warn that unexpected behavior can result from using them in some situations.

However, if you must change the name of the local RDB entry, the procedure includes doing the remove and add operation. But there are special considerations for removing the local entry, because that entry contains some system-wide DRDA attribute information. If you try to remove the entry, you will get message CPA3E01 (Removing or changing *LOCAL directory entry might cause loss of configuration data (C G)), and you will be given the opportunity to cancel (C) the operation or continue (G). The message text goes on to tell you that the entry is used to store configuration data entered with the Change DDM TCP/IP Attributes (CHGDDMTCPA) command. If the *LOCAL entry is removed, configuration data might be destroyed, and the default configuration values will be in effect. If the default values are not satisfactory, configuration data will have to be re-entered with the CHGDDMTCPA command. Before removing the entry, you might want to record the values specified in the CHGDDMTCPA command so that they can be restored after the *LOCAL entry is deleted and added with the correct local RDB name.

You cannot add an alias to a relational database directory entry that specifies *LOCAL as the remote location name. Message CPD3EC8 is displayed if you attempt to do so.

Server side RDB aliases are supported over TCP/IP. To create a server side RDB aliases, use the RDB name from the *LOCAL entry, the desired alias name, the remote location LOOPBACK and type *IP. The DRDA server jobs will then accept incoming requests against the alias name.

                      Add RDB Directory Entry (ADDRDBDIRE)                      
 Type choices, press Enter.                                                     
   Relational database  . . . . . > LCLRDB                                      
   Relational database alias  . .   LCLALS                                      
 Remote location:                                                               
   Name or address  . . . . . . .   LOOPBACK                                    
   Type . . . . . . . . . . . . . > *IP           *SNA, *IP                     
 Port number or service program     *DRDA                                       
 Remote authentication method:                                                  
   Preferred method . . . . . . .   *USRENCPWD    *USRENCPWD, *USRID...         
   Allow lower authentication . .   *ALWLOWER     *ALWLOWER, *NOALWLOWER        
 Encryption algorithm . . . . . .   *DES          *DES, *AES                    
 Secure connection  . . . . . . .   *NONE         *NONE, *SSL                   
 F3=Exit   F4=Prompt   F5=Refresh   F12=Cancel   F13=How to use this display    
 F24=More keys