You display the list of the database files of the current database instance. You have the option of specifying the scope of the detail list that is output.
Only those files that are actually available are listed however. The list may therefore vary with the state of the database instance.
You have the server authorization DBFileRead.
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 |
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
Value |
Description |
<file_ID> |
Key identifying name of a database file |
<mode> |
Specifies 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 |
Logging on to the Database Manager CLI as operator OLEG with password MONDAY, connecting to the database instance DEMODB, displaying 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
...