Domdsmc query preferences

The domdsmc query preferences command displays a list of the current values that are set in the preferences file for Data Protection for IBM® Domino®.

Purpose

You can view a list of the current values that are set in the preferences file for Data Protection for HCL Domino by running the domdsmc query preferences command.

Syntax

>>-DOMDSMC--Query--PREFerences---------------------------------->

>--+-------------------------------+---------------------------->
   |               .-domdsm.cfg--. |   
   '-/CONFIGfile=--+-cfgfilename-+-'   
   
>--+----------------------------+--+--------------------+------><
   |            .-domdsm.log--. |  |             .-60-. |   
   '-/LOGFile=--+-logfilename-+-'  '-/LOGPRUne=--+-n--+-'   
                                                 '-No-'  

Parameters

/CONFIGfile=cfgfilename
Specifies the name of the Data Protection for HCL Domino preferences file. The file name can include a fully qualified path. If you do not specify a path, it is assumed the preferences file is stored in the directory where Data Protection for HCL Domino is installed.

The default preferences file is domdsm.cfg.

/LOGFile=logfilename
Specifies the name of the activity log that is generated by Data Protection for HCL Domino. The log file name is used for the current command and does not update the default log file that is stored in the preferences file. You can use the set command to change the default log file name that is stored in the preferences file. The command-line parameter can be used to override the default for one command run. If the specified file does not exist, it is created. If it does exist, new log entries are appended to the file. The file name can include a fully qualified path. If you do not specify a path, the file is written to the directory where Data Protection for HCL Domino is installed.

The default log file is domdsm.log.

When you are using multiple simultaneous instances of Data Protection for HCL Domino for operations, use the /logfile parameter to specify a different log file for each instance used. This parameter directs logging for each instance to a different log file and prevents interspersed log file records. Failure to specify a different log file for each instance can result in unreadable log files.

/LOGPRUne=60|n|No
Specifies whether to prune log entries. By default, log pruning is enabled and run daily. Use the set command to do the following actions:
  • Change the defaults so that log pruning is disabled.
  • Change the number of days log entries are saved.
You can use the /logprune option to override these defaults for one command run. When the value of /logprune is a number, the prune is run even if one has completed for the day.
You can specify:
60
Specifies that log entries are saved for 60 days before pruning. This is the default.
n
Specifies the number of days to save log entries. The range of values is 0 - 9999. A value of 0 deletes all entries in the log except for the current command run entries.
No
Do not prune the log.
Changes to the value of the timeformat or dateformat parameter can result in an undesired pruning of the log file. If you are running a command that prunes the log file and the value of the timeformat or dateformat parameter changes, run one of the following actions to prevent pruning of the log file:
  • Make a copy of the existing log file.
  • Specify a new log file with the /logfile parameter or logfile setting.

Example

This command shows the current values that are stored in the default preferences file for Data Protection for HCL Domino.
domdsmc query preferences
Output example:
Data Protection for Domino Preferences
--------------------------------

ADSMLOGDir .....................
ADSMOPTFile ....................
BUFFers ........................ 3
BUFFERSIze ..................... 1024
DATEformat ..................... 
LANGUAGE .......................
LOGFile ........................ domdsm.log
LOGPRUne ....................... 60
MOUNTWait ...................... Yes
NOTESInipath ...................
NUMberformat ................... 1
REPlace ........................ Yes
SESSions ....................... 1
STATistics ..................... No
SUBDir ......................... No
TIMEformat ..................... 1
DOMTXNBYTElimit................. 0
DOMTXNGROUPmaX.................. 2
COMMRESTARTDuration ............ 60
COMMRESTARTInterval ............ 15

DB2ALTDBname ................... DOM_ALT
DB2CONTainerpath ...............
DB2LOGPath .....................
DB2LOGTarget ...................
DB2REPlace ..................... Yes
DB2RESTIntopath ................
DB2SESSions .................... 1
DB2USER ........................