## file_getlist

### Use

You display the list of the database files of the current database instance. You have the option of specifying the scope of the file list that is output.

Note, however, that the system only displays those DBM commands which it can access at the time of execution. The list may therefore vary with the state of the database instance.

See also:

Glossary, Database File

### Prerequisites

You have the server authorization DBFileRead.

### Syntax

file_getlist <list_level>

<list_level> | Scope of the file list displayed; possible values are: 0: The most important files (default value) 1: All files

### Reply

OK

key_name,mode,size,date,time,comment,file_name

<file_ID> <mode> <file_length> <date> <time> <comment> <file_name>

<file_ID> <mode> <file_length> <date> <time> <comment> <file_name>

...

Values for the Reply Fields

Field | Description
<file_ID> | File ID of the database file
<mode> | Indicates whether the file is plain text or binary Possible values are: ASCII|BINARY ASCII: plain text file (also UNICODE) BINARY: Binary file
<file_length> | Size of database file
<date> | Date of last change
<time> | Time of last change
<comment> | Additional information
<file_name> | File name

### Example

Call the Database Manager CLI, log on as operator OLEG with password MONDAY, connect to the database instance DEMODB, display the list of the most important database files:

>dbmcli -u OLEG,MONDAY -d DEMODB file_getlist 1

OK

keyname,mode,size,date,time,comment,filename

KNLDIAG ASCII 50608 20050421 133815 Database Messages knldiag.classic

KNLDIAGERR ASCII 1447 20050421 133815 Database Errors knldiag.err.classic

KNLDIAGOLD ASCII 56767 20050421 133816 Database Messages (OLD) knldiag.old.classic

KNLTRC BINARY 5595136 20050418 141944 Database Trace knltrace

UTLPRT ASCII 102400 20050418 141927 Utility Statements dbm.utl

BACKHIST ASCII 1424 20050418 131056 Backup History dbm.knl

...