RMCONFIGURATION

The RMCONFIGURATION table is reserved for Content Manager Enterprise Edition resource manager configuration.

Table 1.
Column	Data type	Attribute
PROPERTYNAME	VARCHAR(256)	NOT NULL
PROPERTYVALUE	VARCHAR(1536) FOR BIT DATA	NOT NULL
PROPERTYBINARY	VARCHAR(30000) Db2 ONLY BLOB ORACLE ONLY	NULLABLE

Primary key: (PROPERTYNAME)
Indexes: None
Referential constraints: None

Columns

PROPERTYNAME: Name of the parameter. See Table 2 for the property names that are allowed.
PROPERTYVALUE: Value of the parameter if it can be represented as a String (including numbers).
PROPERTYBINARY: Value in binary format when it cannot be represented as a String.

Table 2. PROPERTYNAME parameters
Parameter	Description
`ALLOWED_LOGON_FAILURES`	An integer value, this value is the number of sequential logon failures allowed. After the allowed number is reached, all logons are denied. A value of -1 is the infinite case. The valid range is -1 to 32 767.
`ADMIN_PASSWORD_MINIMUM_LENGTH`	Allows configuring a minimum resource manager administration password length.
`ADMIN_PASSWORD_MAXIMUM_LENGTH`	Allows configuring a maximum resource manager administration password length.
`ADMIN_PASSWORD_MINIMUM_ALPHA_CHARACTERS`	`1` or `0` disables this check. Allows configuring a minimum number of required alphabetic characters for resource manager administration password from the following set: `ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz`
`ADMIN_PASSWORD_MINIMUM_NUMERIC_CHARACTERS`	`1` or `0` disables this check. Allows configuring a minimum number of required numeric characters for resource manager administration password from the following set: `0123456789`
`ADMIN_PASSWORD_MINIMUM_OTHER_CHARACTERS`	`1` or `0` disables this check. Allows configuring a minimum number of required other characters for resource manager administration password from the following set: `!@#+.,?*_.`
`ADMIN_PASSWORD_MAXIMUM_REPEATED_CHARACTER`	Allows configuring a maximum number of repeated characters for resource manager administration password. `1` or `0` disables this check.
`ADMIN_PASSWORD_MINIMUM_DIFFERENT_CHAR ACTERS`	Allows configuring a minimum number of different characters for resource manager administration password. `1` or `0` disables this check.
`AUDITMODE`	The default is ASYNC.
`ADVERTISE_ACCEPT_RANGES`	Controls whether the server sets the Accept-ranges header for retrieve operations. If the value is `TRUE` then the Accept-ranges header is set. The default value is `FALSE`.
`ALWAYS_VERIFY_AND_STORE_INCOMING_CONTENT_MD5`	`TRUE` validates the MD5 hash that is sent from the API in a store operation, remote migration, or remote replication services. If the validation fails, the operation fails. `FALSE` does not validate the MD5 hash. This parameter applies only when the MD5 hash is sent from either the API or from another resource manager in remote replication or remote migration. The default value is `TRUE`.
`AZURE_BLOCK_LIST_UPLOAD_BLOCK_SIZE`	The block size (in megabytes) that is used to upload objects to Microsoft Azure Block Blob Storage in block list method. This value is used only if AZURE_ENABLE_BLOCK_LIST_UPLOAD is set to TRUE. The minimum value is 5. The maximum value is 4000. If this parameter is set to less than 5, 5 is used. If it is set to more than 4000, 4000 is used. The default value is 2047.
`AZURE_ENABLE_BLOCK_LIST_UPLOAD`	TRUE enables block list upload to Microsoft Azure Block Blob Storage. Use this if you are storing large objects on Microsoft Azure Block Blob Storage. FALSE disables block list upload to Microsoft Azure Block Blob Storage. If block list upload is disabled and the object size is more than 5000 megabytes, the block list is automatically used with a block size of 4000. The default value is FALSE.
`BACKGROUND_LS_DELETE_PROCESS`	A long value that expresses the milliseconds since the time 00:00:00 Coordinated Universal Time (UTC) on January 1, 1970. This value is used to serialize processing for items pending deletion within the library server (items identified in library server ICMSTItemsToDelete table) from the resource manager server. When the delete cycle begins, this value is compared to the current time. If this value is smaller, then processing of pending deletions in the library server starts immediately. Otherwise, the delete cycle portion for library server items pending deletion ends. When delete processing for a batch of library server deletions occurs, the value is reset. See the BACKGROUND_LS_DELETE_TASK_DEFERTIME property for details. Do not change this value unless directed by IBM® support.
`BACKGROUND_LS_DELETE_TASK_DEFERTIME`	A long value in milliseconds that specifies the maximum time allocated to a specific node or thread to process a batch of pending library server deletions. This value is used to calculate the value of the BACKGROUND_LS_DELETE_PROCESS. The values BACKGROUND_LS_DELETE_TASK_DEFERTIME and BACKGROUND_LS_DELETE_PROCESS are used specifically to serialize certain delete operations within the resource manager server. The default delay time is 900000 (15 minutes).
`BACKGROUND_RM_DELETE_PROCESS`	A long value that expresses the milliseconds since the time 00:00:00 Coordinated Universal Time (UTC) on January 1, 1970. This property controls the frequency in which the resource manager performs delete processing on objects marked for deletion ( OBJ_STATUS within RMOBJECTS table indicated pending deletion). When the delete cycle begins, this value is compared to the current time. If this value is smaller, processing of resource manager deletions is started immediately. Otherwise, the delete cycle portion for objects marked for deletion ends. See BACKGROUND_RM_DELETE_TASK_DEFERTIME for details. Do not change this value unless directed by IBM support.
`BACKGROUND_RM_DELETE_TASK_DEFERTIME`	A long value in milliseconds that specifies the frequency in which the resource manager performs delete processing on objects marked for deletion ( OBJ_STATUS within RMOBJECTS table indicated pending deletion). This property value is added to current time to calculate the BACKGROUND_RM_DELETE_PROCESS value. During the normal delete cycle (see BACKGROUND_SERVICE_CYCLE), if no objects marked for deletion are found, then future delete operations for these delete candidates ( OBJ_STATUS within RMOBJECTS table indicated pending deletion) are deferred for the period specified. The default delay time is 18000000 (5 hours).
`BACKGROUND_SERVICE_CYCLE`	The default background service cycle time is expressed in minutes. When active, Asynchronous delete and Asynchronous reconciliation runs automatically in the background.
`BACKGROUND_SERVICE_BATCH_SIZE`	The default is 1000.
`BLOB_STORE_SIZE_ENFORCED`	Controls whether to use the new BLOB behavior or old BLOB behavior. By default this flag is set to `True` to use the new BLOB behavior. With the new behavior, for store orders, the entire data stream received by resource manager for an object is stored, there is no truncation or padding, and the size specified in the order must match with the actual size of the data stream received by resource manager. If a size mismatch is detected in the store order, a size mismatch error is returned. Also with the new behavior, for third-party store orders, the size specified in the order is not checked. The entire data stream received by resource manager for an object is stored, there is no truncation or padding. If the order states the size is 10K but the actual content in the stream is 10 bytes, the actual 10 byte object is stored. If the order says that the size is 10 bytes but the actual content in the stream is 10K, the actual 10K object is stored. For third-party store orders, the actual size of the object stored in resource manager is used for an objects metadata size instead of the size specified in the third-party store order. This flag can be set directly in the RMCONFIGURATION table or by using the Advanced Parameters tab of the web-based Resource Manager Administration program.
`CMCOMMON_LDAP`	Reference for installing the properties files on the resource manager.
`COS_ALWAYS_USE_NON_VERSIONED_DELETE`	Specifies how the resource manager deletes objects that are on cloud object storage servers when bucket versioning is enabled or suspended. If bucket versioning is disabled, this parameter has no effect. `FALSE`: When the object version is deleted from IBM Content Manager, it is also deleted from the cloud object storage server. `TRUE`: When the object version is deleted from IBM Content Manager, the object version is left on the cloud object storage server and becomes a non-current version. The default value is `FALSE`. This parameter does not apply to Microsoft Azure Block Blob Storage. This parameter was added in V8.7 fix pack 1.
`COS_MAX_ALLOWED_SINGLE_UPLOAD_SIZE`	The maximum object size (in MB) that can be uploaded in a single request for non-retention cloud object storage (COS) server buckets. If an object is bigger than this value, multiple part upload is used (see also COS_MULTI_PART_UPLOAD_PART_SIZE). The value is an integer in megabytes (MB). The minimum value is 5. If you specify a smaller value, 5 is used. The maximum value is 10485760 (10 TB). If you specify a bigger value, 10485760 is used. The default value is 5120 (5 GB). This parameter does not apply to Microsoft Azure Block Blob Storage. This parameter was added in V8.7 fix pack 1.
`COS_MULTI_PART_UPLOAD_PART_SIZE`	The size (in MB) of each part, when multiple part upload is used for non-retention cloud object storage (COS) server buckets (see also COS_MAX_ALLOWED_SINGLE_UPLOAD_SIZE). The value is an integer in megabytes (MB). The minimum value is 5. If you specify a smaller value, 5 is used. The maximum value is 5120 (5 GB). If you specify a bigger value, 5120 is used. If you specify a value that is more than the value that is set in the COS_MAX_ALLOWED_SINGLE_UPLOAD_SIZE parameter, the value that is set in that parameter is used. The default value is 2047. This parameter does not apply to Microsoft Azure Block Blob Storage. This parameter was added in V8.7 fix pack 1.
`COS_RETENTION_ALWAYS_SAVE_CONTENT_MD5`	`TRUE`: The resource manager calculates and stores an MD5 hash in object store, migration, replication or changeSMS operations, when an MD5 hash is not available, but might be used in a later operation. `FALSE`: The resource manager does not calculate and store the MD5 hash. This parameter applies when the management class attached to the storage collection includes IBM Cloud Object Storage with retention or cloud object storage with object lock. The default value is `TRUE`.
`COS_RETENTION_ENABLE_MULTI_PART_UPLOAD`	`TRUE` enables multiple part upload to IBM Cloud Object Storage with retention or cloud object storage with object lock. Use this if you are storing large objects on IBM Cloud Object Storage with retention or cloud object storage with object lock. This can reduce the memory usage in the resource manager. `FALSE` disables multiple part upload to IBM Cloud Object Storage with retention or cloud object storage with object lock. The default value is `TRUE`.
`COS_RETENTION_MULTI_PART_UPLOAD_PART_SIZE`	The part size (in megabytes) that will be used to upload objects to IBM Cloud Object Storage with retention or cloud object storage with object lock in multiple parts method. This value is used only if `COS_RETENTION_ENABLE_MULTI_PART_UPLOAD` is set to `TRUE`. The minimum value is 5. The maximum value is 2047. If this parameter is set to less than 5, 5 is used. If it is set to more than 2047, 2047 is used. The default value is 5.
`COS_RETRIEVE_STAGING_ENABLED`	`TRUE`: When objects are retrieved from Cloud Object Storage (COS) servers, they are cached in the resource manager staging area. Resource manager will get the objects from the staging area instead of from the COS server for subsequent retrieve operations. `FALSE`: When objects are retrieved from COS servers, they are not cached in the resource manager staging area. Resource manager will get the objects from the COS server for subsequent retrieve operations. The default value is `FALSE`.
`DEFAULT_EVENT_BATCH_SIZE`	The audit event batch size. The default is 750.
`DISABLE_SERVICE_CHECK_OUT_TIMEOUT`	Internal usage for the replication utility. Do not define or change this parameter unless directed by IBM Support.
`DO_NOT_SUSPEND_VOLUME_ON_WRITE_IO_ERROR`	Allows configuration of volume suspend on I/O error behavior. `True` = IBM Content Manager V8.3 behavior. `False` = IBM Content Manager V8.4 and later behavior. `Last` allows suspend, but not on the last available volume.
`DO_NOT_SUSPEND_VOLUME_ON_THRESHOLD_FULL`	Allows configuration of volume suspend on I/O error behavior. `True` = IBM Content Manager V8.3 behavior. `False` = IBM Content Manager V8.4 and later behavior. `Last` allows suspend, but not on the last available volume.
`DSMI_DIR`	The fully qualified directory path for the IBM Spectrum Protect client API.
`DSMI_LOG_PATH`	The fully qualified path of the error log directory for IBM Spectrum Protect.
`ECM_DASHBOARD_ENABLED`	Use to enable or disable System Dashboard for Enterprise Content Management.
`ENABLE_ENCRYPTOR`	To enable the encryptor (to encrypt existing data), set this parameter to TRUE. The default value is FALSE. See also ENCRYPTOR_BATCH_SIZE and ENCRYPTOR_MAXIMUMPOOLSIZE. For more information about the encryptor, see Encrypting existing data.
`ENABLE_FILESYSTEM_WRITE_SYNC`	Controls whether to enable the resource manager file system write operations to synchronize with the underlying storage devices. For more information, see: http://www-01.ibm.com/support/docview.wss?uid=swg27043996.
`ENABLE_64BIT_TOKEN`	Controls which type of token is allowed by the resource manager. The default value is TRUE or 1 to enable the resource manager to use 64-bit encryption keys for the token. This setting also enables the content management system to use stronger 128-bit encryption keys if both the library server and resource manager are at V8.6 or later. If the library server and all resource managers in the system are V8.6 or later, then 128-bit encryption keys for the token are used. If the value is set to FALSE or 0, the resource manager must use the 128-bit or stronger encryption keys for the token from the AES-128 encryption standard or SHA-2 family encryption standard. Set this value to FALSE or 0 if your content management system is required to meet the 128-bit encryption key standards set by government or industry regulation. This setting ensures that no 64-bit encryption key for the token can be used.
`ENCRYPT_DATA_AT_REST`	Enables the resource manager to encrypt all object content when at rest. If set to TRUE, the resource manager encrypts incoming data. The default value is FALSE (does not encrypt incoming data).
`ENCRYPTIONKEY`	The key to generate the password.
`ENCRYPTIONKEY_DATA_AT_REST`	The key to generate the password.
`ENCRYPTIONKEY_STR`	The key to generate the password.
`ENCRYPTOR_BATCH_SIZE`	The batch size for the encryptor. The default value is 1000. The minimum value is 10. If you specify a value that is less than 10, it is reset to 10.
`ENCRYPTOR_MAXIMUMPOOLSIZE`	The maximum number of worker threads that can be queued to the work manager. The default value is 50. The minimum value is 1. If you specify a value that is less than 1, it is reset to 1.
`ICMRM_LBOSAREA`	llbosdata data area.
`ICM_AGGR_BULK_OPEN`	Controls how aggregate migration processes source files for aggregate. If setting is set to `True`, all source files are opened before transfer to target storage, and then all source files are closed after transfer. This process might result in a significant number of file descriptors in use during aggregate migration operations. Setting this value to `false` (the default), results in each aggregate source file being opened, a transfer of contents to target aggregate, and the closing files one at a time. This process limits the number of file descriptors needed for aggregate migration operations.
`ICM_MAX_AGGR_BATCH_SIZE`	200 (default). The count limit on number of objects stored in aggregate. The default is 200.
`ICMRM_USER`	Prevents writing object files with two different owners, or being unable to access previously written object files. If set, the value is checked with the value from the Java™ system variable user.name. If it is different a stoppage error results. If not set, the value from the Java system variable user.name is used to set it.
`ICMRM_UMASK`	Controls file permissions at create time.
`ICM_VALIDATION_BATCH_SIZE`	Controls the number of items added to the temporary RMLSTIEMS validation table for a single database transaction. The default value is 50 items.
`ICM_VALIDATION_QUEUE_SIZE`	Controls the maximum number of worker threads that can be queued to the work manager. The default value is 50 threads.
`IO_BUFFER_SIZE`	Allows control of non IBM Spectrum Protect I/O buffers sizes, to balance memory and performance.
`JMS_TOPIC_PUBLISHER_FIRST_CONNECT_MAX_WAIT_TIME`	The maximum time to wait and retry to connect to the JMS server before giving up when publishing an event for the first time connection at RM startup. During the wait time, the publisher repeatedly tries to connect to JMS server in a fixed interval. If the connection to the JMS server takes longer than the time set in this parameter, it will take that long to complete the wait. The value must be an integer in seconds in the range 5 to 600 (that is, 10 minutes). The default value is 60 (that is, 1 minute). If the value is smaller than 5, 5 is used. If the value is bigger than 600, 600 is used. This parameter was added in V8.7 fix pack 4.
`JMS_TOPIC_SUBSCRIBER_CONNECT_MAX_WAIT_TIME`	The time (in seconds) to keep trying to reconnect to JMS when there is a JMS connection issue. The value must be an integer in the range 5 to 43200 (that is, 12 hours). The default value is 300 (that is, 5 minutes). If the value is less than 5, 5 is used. If the value is bigger than 43200, 43200 is used. This parameter was added in V8.7 fix pack 2.
`KEY_MATERIAL`	Key for encrypting data at rest (JEKS keystore or obfuscated).
`LOGON_LOCKOUT_DURATION`	The integer value in minutes that the lock applies. 0 is the infinite case. The valid range is 0 to 32767 minutes.
`LOGON_LOCKED`	True or False. This value is always set to False at startup.
`LDAP_AUTO_SET_TRUSTSTORE_TO_CACERTS`	Specifies whether the resource manager sets the Java truststore to the Java cacerts file. This parameter is effective only when SSL is used for LDAP communication and the resource manager is run in traditional WebSphere. TRUE: Set the Java truststore to the Java cacerts file. FALSE: Do not set the Java truststore to the Java cacerts file. The default value is TRUE for backward compatibility. For more information, see Configuring the resource manager for SSL and TLS communication with the LDAP server. This parameter was added in V8.7 fix pack 4.
`LDAP_SECURITY_CREDENTIALS`	The password reference for installing the properties files on the resource manager.
`LDAP_INITIAL_CONTEXT_FACTORY`	The reference for installing the properties files on the resource manager. The default is sun.com.jndi.ldap.
`LDAP_PROVIDER_URL`	The reference for installing the properties files on the resource manager. The default is http://localhost.
`LDAP_PORT`	The port number reference for installing the properties files on the resource manager.
`LDAP_REFERRAL`	The default set to ignore reference for installing the properties files on the resource manager.
`LDAP_ROOT_DN`	Reference for installing the properties files on the resource manager. o (lowercase letter "O") = IBM c = US
`LDAP_SECURITY_AUTHENTICATION`	Reference for installing the properties files on the resource manager. The default is NONE.
`LDAP_SERVER_TYPE`	The LDAP server type reference for installing the properties files on the resource manager. The default is STANDARD_LDAP.
`LDAP_SEARCH_SCOPE`	Reference for installing the properties files on the resource manager. The default is SUBTREE_SCOPE.
`LDAP_SECURITY_PROTOCOL`	Reference for installing the properties files on the resource manager.
`LDAP_AUTHENTICATION_ATTRIBUTE`	Reference for installing the properties files on the resource manager. ON or OFF.
`LDAP_SECURITY_PRINCIPAL`	Reference for installing the properties files on the resource manager. The default is cn=root.
`RMBATCH_PROCESS_FREQ_SEC`	Audit event frequency. The default is 10800 seconds.
`MIGRATOR_LAST_STATE`	The default is stopped.
`MIGRATOR_TRANSACTION_TIMEOUT`	The migrator failed transaction retry timeout. The default is 900 seconds.
`PURGER_LAST_STATE`	The default is stopped.
`PURGER_TRANSACTION_TIMEOUT`	The purger failed transaction retry timeout. The default is 900 seconds.
`REPLICATOR_LAST_STATE`	The default is stopped.
`REPLICATOR_SKIP_IMPORT_REPLICA_ON_ERROR`	Specifies what happens when an error occurs in import replica to the library server. The import replica error can be caused by incorrect tasks that were manually inserted to the RMREPLICATION table as a step of enabling replication for existing objects. TRUE The replicator service omits the import replica step for the current replication cycle, and then processes the normal replication tasks. FALSE The replicator service ignores the error; it fetches the next batch for import replica in the current replication cycle. After the replicator service has processed all the import replica tasks, it processes the normal replication tasks. The default value is FALSE. This parameter was added in V8.7 fix pack 2.
`REPLICATOR_INTRANSACTION_TIMEOUT`	Internal usage for the replication utility. Do not define or change unless directed by IBM Support personnel.
`REPLICATOR_TRANSACTION_TIMEOUT`	The replicator failed transaction retry timeout. The default is 900 seconds.
`RETRIEVE_REQUEST_CHECK_FILE_EXTENSION`	Checks whether the file name extension that is on the retrieve request URL is the same as the original file name extension from the resource manager database. TRUE: The resource manager compares the file name extensions. If they are the same, the retrieve request is allowed. If they are different, or the original file name in the resource manager database does not have an extension, the resource manager tolerates the extension on the retrieve request URL if it is in this object's mime type suffixes list defined in the library server and the `RETRIEVE_REQUEST_TOLERATE_MIME_TYPE_SUFFIX` parameter is set to TRUE. FALSE: The resource manager does not check the file name extension that is on the retrieve request URL. The default value is FALSE.
`RETRIEVE_REQUEST_TOLERATE_MIME_TYPE_SUFFIX`	This parameter applies only when the `RETRIEVE_REQUEST_CHECK_FILE_EXTENSION` parameter is set to TRUE. TRUE: If the file name extension of an object on the retrieve request URL is different from the file name extension in the resource manager database and the extension is in the object's mime type suffixes list defined in the library server, the resource manager retrieves the object.. FALSE: If the file name extension of an object on the retrieve request URL is different from the file name extension in the resource manager database, the resource manager does not retrieve the object. Note: To retrieve objects from the resource manager that have no original file name, set this parameter to TRUE. The Content Manager API uses a default filename and extension (`item_ID.suffix_from_mime_type`) on the retrieve request URL for objects that have no original file name. If this parameter is set to FALSE, the mime type suffix is not tolerated; that is, the resource manager does not retrieve the object. The default value is TRUE.
`RETRIEVE_RESPONSE_USE_REQUEST_CONTENT_TYPE`	Controls how the value for the content-type is set when the resource manager responds to a retrieve request. To use the value when the content was originally stored, set this parameter to FALSE. To use the value that is provided in the retrieve request, set this parameter to TRUE. The default value is FALSE.
`RUN_SERVICE_CONTROLLERS_ON_NONMANAGED_THREADS`	Controls whether the controller threads of the resource manager background services are run on a non-managed thread. When they are run on a non-managed thread, they are not reported as "hung" in the WebSphere Application Server SystemOut.log file when they run for a long time. TRUE The controller threads run on non-managed threads. FALSE The controller threads run on managed threads. This behavior is the same as V8.7 fix pack 1 and earlier. The default value is FALSE. This parameter was added in V8.7 fix pack 2.
`STAGER_LAST_STATE`	The default is stopped.
`STAGER_TRANSACTION_TIMEOUT`	The stager failed transaction retry timeout. The default is 900 seconds.
`STATIC_FILE_PERMISSION`	The default value 400 causes a new file to be read-only.
`SEQUENTIAL_LOGON_FAILURES`	The current count of sequential logon failures. This value is always set to zero at startup, and cannot be a negative value.
`TSM_CONNECTION_TIMEOUT`	The maximum idle time, in seconds, for a connection. A connection is closed if the idle time is exceeded. The default connection timeout is 180 seconds (3 minutes). This value controls the reduction of the pool number when activity is slow. If this value is not configured correctly, an error is not shown. Set this value so that it is less than the IBM Spectrum Protect session timeout value.
`TSM_ENABLE_FASTQUERYBACKUP`	Enables sending of the IBM Spectrum Protect option -fastquerybackup on IBM Spectrum Protect DSMInitEx calls. This setting might improve IBM Spectrum Protect performance with IBM Spectrum Protect 6.1 and later.
`TSM_FORCE_TERMINATE_OPERATION_AT_RM_SHUTDOWN`	TRUE stops the IBM Spectrum Protect (TSM) operations that are not completed when the resource manager shuts down after the wait time specified in the TSM_MAX_WAIT_FOR_OPERATION_COMPLETE_AT_RM_SHUTDOWN parameter has passed. It does this by calling the TSM client API. FALSE does not stops the TSM operations (they might still complete on their own). This parameter applies only when the TSM connection pool is used. The default value is TRUE.
`TSM_MAX_POOLED_CONNECTIONS`	The default value is 50 IBM Spectrum Protect connections. The minimum value is 3. If the value exceeds 150, a warning is logged to the resource manager log file. The maximum allowed value is 32767. If you set a value that exceeds 32767, then it is ignored and the default value of 50 is used instead. You must set this value so that the number is less than the concurrent session limit that is set for the IBM Spectrum Protect server. Setting this value to a greater number than the concurrent session limit might result in errors in the clients for object storage and retrieval. Count all connections for this value, including multiple resource managers that share a single IBM Spectrum Protect server or other applications that also share this server. For example, if the resource manager is deployed in a WebSphere® Application Server cluster, then multiply the TSM_MAX_POOLED_CONNECTIONS value for a single resource manager by the number of cluster nodes and use that total as the value for TSM_MAX_POOLED_CONNECTIONS.
`TSM_MAX_WAIT_FOR_FREE_CONNECTION`	If this parameter is set to a positive value in milliseconds, then an error is shown if this value is exceeded while the resource manager is waiting for a connection. The default is -1 (no limit) and the maximum value allowed is 32767. If you set a value that exceeds 32767, then it is ignored and the default value of -1 is used instead.
`TSM_MAX_WAIT_FOR_OPERATION_COMPLETE_AT_RM_SHUTDOWN`	Maximum time (in seconds) to wait for IBM Spectrum Protect (TSM) operations to complete when the resource manager shuts down. The resource manager shuts down even if the TSM operations do not complete in the time specified. See also TSM_FORCE_TERMINATE_OPERATION_AT_RM_SHUTDOWN. This parameter applies only when the TSM connection pool is used. The default value is 180. If this parameter is set to more than 900, a warning is recorded in the resource manager log file.
`TSM_PARTIAL_RETRIEVE_DISABLED`	Disables IBM Spectrum Protect partial retrieve. You must set this value to `YES` if IBM Spectrum Protect contains any compressed objects. The default is `NO`, meaning that when IBM Spectrum Protect client compression and encryption are not used, then the IBM Spectrum Protect partial retrieve is used for aggregate object members.
`TSM_USE_QS`	Enables use of the IBM Spectrum Protect query session call to validate pooled IBM Spectrum Protect connections, instead of the query management class call.
`TSM_WAIT_FOR_FREE_CONNECTION`	The retry interval for getting IBM Spectrum Protect pooled connections. This value controls an internal wait time to ensure that a request does not remain on the queue indefinitely. This parameter enables the thread to check whether the value in TSM_MAX_WAIT_FOR_FREE_CONNECTION has been exceeded. The value is in milliseconds. The default value is 250 milliseconds. The maximum value is 32767. If you set a value that exceeds 32767, then it is ignored and the default value of 250 is used instead.
`USE_KEY_SIZE_BITS`	The size in bits for the key to encrypt data at rest (128 or 256). The default is 128.
`VAL_BEGIN_DATE`	Internal usage for validation utility.
`VAL_END_DATE`	Internal usage for validation utility.
`VAL_USE_TRUNCATE_TO_CLEAR_VU_TABLES`	(Applies only when the resource manager database is Db2.) Specifies how the validation utility tables, RMLSITEMS and RMVALREPORT, are cleared. TRUE The resource manager uses TRUNCATE to clear the validation utility tables. FALSE The resource manager uses ACTIVATE NO LOGGED INITIALLY to clear the validation utility tables. This is the same behavior as in V8.7 fix pack 1 and earlier. FALSE might cause Db2 return codes -1477 or -628 when you run the validation utility. For more information, see Db2 error -1477 or -628 when running the resource manager validation utility. The default value is TRUE. This parameter was added in V8.7 fix pack 2.
`VAL_VOLUME_ID`	Internal usage for validation utility.
`VALIDATE_LSITEMS_COUNT`	Internal usage for validation utility.
`VALIDATE_LSITEMS_PROCESSED_COUNT`	Internal usage for validation utility.
`VALIDATE_LSITEMS_TOTALITEMS_COUNT`	Internal usage for validation utility.
`VALIDATE_STATUS`	Internal usage for validation utility.
`VALIDATE_TYPE`	Internal usage for validation utility.
`VALIDATE_VOLUME_STATUS`	Internal usage for validation utility.
`VALIDATOR_LAST_STATE`	Internal usage for the validation utility. This property is the last state of the validation utility.
`VALIDATION_REPORT_CONDITION_MESSAGE`	Internal usage for the validation utility.
`VALIDATION_REPORT_CURRENT_CONDITION`	Internal usage for the validation utility.
`VALIDATION_REPORT_CURRENT_EVENTTIME`	Internal usage for the validation utility. Represents the last time validation was run (epoch time in milliseconds).
`VALIDATION_XML_LOGPATH`	The path to the XML validation reports. This path must be set to generate XML formatted validation reports.
`WLP_UUID_BACKGROUND_SERVICE_CYCLE`	This parameter applies when the resource manager application runs in WebSphere Liberty. The interval (in seconds) at which the UUID background service checks the storage management system (SMS) and background service state changes. In most systems, the default value of 60 is sufficient. Use a different value only if it is determined that more frequent checks are required. If you change the value, restart the resource manager application server. The minimum value is 1. The maximum value is 60. If the value is less than 1, 1 is used. If the value is more than 60, 60 is used. The default value is 60. This parameter was added in version 8.7 fix pack 3.
`WLP_LDAP_CONFIG_FILE`	This parameter applies when the resource manager application runs in WebSphere Liberty. The full path to the LDAP configuration properties file. For more information, see Enabling LDAP authentication for the resource manager application user. This parameter was added in version 8.7 fix pack 3.
`icmrm.tsm.jni.trace`	Internal usage for control of JNI tracing. Do not change this value unless directed by IBM Software Support.

Note: TOKEN_REQUIRED reserved parameter is not supported. Token is always validated regardless of the value of this parameter.