Lists the contents of the db2cli.ini file. This command can list the entire file, or a specified section.
The db2cli.ini file is used as the DB2 call level interface (CLI) configuration file. It contains various keywords and values that can be used to modify the behavior of the DB2 CLI and the applications using it. The file is divided into sections, each section corresponding to a database alias name. For more information about this file and the CLI/ODBC configuration keywords, see the CLI Guide and Reference.
Authorization
None
Required Connection
None
Command Syntax
>>-GET CLI----+-CONFIGURATION-+--------------------------------->
+-CONFIG--------+
'-CFG-----------'
>-----+----------------------------+---------------------------><
'-FOR SECTION--section-name--'
Command Parameters
Examples
The following sample output represents the contents of a db2cli.ini file that has two sections:
Section: tstcli1x
-------------------------------------------------
uid=userid
pwd=*****
autocommit=0
TableType='TABLE','VIEW','SYSTEM TABLE'
Section: tstcli2x
-------------------------------------------------
SchemaList='OWNER1','OWNER2',CURRENT SQLID
|
Usage Notes
The section name specified on this command is not case sensitive. For example, if the section name in the db2cli.ini file (delimited by square brackets) is in lowercase, and the section name specified on the command is in uppercase, the correct section will be listed.
The value of the PWD (password) keyword is never listed; instead, five asterisks (*****) are listed.
When LDAP (Lightweight Directory Access Protocol) is enabled, the CLI configuration parameters can be set at the user level, in addition to the machine level. The CLI configuration at the user level is maintained in the LDAP directory. If the specified section exists at the user level, the CLI configuration for that section at the user level is returned; otherwise, the CLI configuration at the machine level is returned.
The CLI configuration at the user level is maintained in the LDAP directory and cached on the local machine. When reading the CLI configuration at the user level, DB2 always reads from the cache. The cache is refreshed when:
See Also