Profile parameter descriptions

Edit online

The default value is underlined in these descriptions and applies if the parameter is not specified.

ADSMNODE ORACLE_sid node_name
Specifies an ORACLE_sida node_namea node name that is registered to the IBM Storage Protect™ server as an IBM Storage Protect node. This parameter must be defined with the respective SERVER statement, as shown in the sample profile. You can assign a different node name to your database system with this option. It is used if you have several SAP database systems in your network with the same name, for example, SID, and they all use the same IBM Storage Protect server. This keyword must not be set when automated password handling is selected. It is to be set for manual password-handling.
ASNODE
Specifies a node name that is registered to the IBM Storage Protect server as an IBM Storage Protect node. This parameter must be defined with the respective SERVER statement, as shown in the sample profile. When automated password handling is selected and the node is accessed from multiple different SAP systems, for example, HANA scale-out or IBM Storage Protect Snapshot offload operations, this parameter avoids storing the encrypted password on multiple hosts (which would cause the password update to fail on all but the first host). For details in the HANA environment see: Protection of a scale-out solution This parameter must not be set when manual password handling is selected.
BACKEND pgmname [parameterlist]
Specifies a program pgmname that is called by IBM Storage Protect for ERP after the backup function completed and before program control is returned to DB2®. If pgmname is not a fully qualified path, the default search path is used to locate the program. If not specified, no backend processing is finished.
Example for UNIX™ or Linux™: 
BACKEND write operator@remotesite Backup of SAP database object completed.
This process sends a message to a remote user when the backup is finished.
BACKEND pgmname [parameterlist]
Specifies a program pgmname that is called by IBM Storage Protect for ERP after the backup function completes and before program control is returned to the SAP backup utility. If pgmname is not fully qualified, the default search path is used to find the program. If not specified, no backend processing is done.
Example for UNIX or Linux: 
BACKEND write operator@remotesite Backup of SAP database object completed.
This process sends a message to a remote user when the backup finishes.
BACKUPIDPREFIX 6-charstring | SAP___
Specifies a six-character prefix that is used to create a backup identifier for each archived object. If not specified, the default value is SAP___.All partitions of a partitioned DB2 database have the same BACKUPIDPREFIX.
BATCH YES|NO
Specify NO if IBM Storage Protect for ERP is running with an operator standing by. Specify YES if IBM Storage Protect for ERP is running in unattended mode. In unattended mode, IBM Storage Protect for ERP stops the run if operator intervention is required. The default for the BATCH parameter is YES for the backup-run and NO for the restore-run if the BATCH parameter is not present or is commented out in the IBM Storage Protect for ERP profile. This parameter has no effect if an RMAN backup or restore is started.
BRARCHIVEMGTCLASS management_class [management_class...]
Specifies the IBM Storage Protect management classes that IBM Storage Protect for ERP uses when backing up redo logs . when backing up redo logs.to back up offline DB2 log files. Each parameter string can consist of up to 30 characters. Specify a separate management classes for each log file copy requested. As a result, make sure the number of different management classes that are specified must be greater than or equal to the number of redo log copies redo log copies log file copies. This parameter must be defined with the respective SERVER statement, as shown in the sample profile.

To use different IBM Storage Protect servers for backup and archive data, the value :SKIP: can be used to define a server stanza with no archive management classes. This value is allowed for the parameter management classes only.

BRBACKUPMGTCLASS management_class [management_class...]
Specifies the IBM Storage Protect management classes that IBM Storage Protect for ERP uses when called through BRBACKUP when called through BRBACKUP. to back up the DB2 database. The parameter string can consist of up to 30 characters. This parameter must be defined with the respective SERVER statement, as shown in the sample profile.
BUFFCOPY SIMPLE|PREVENT|AUTO
This optional parameter controls how IBM Storage Protect for ERP uses the internal buffers for transferring data during a backup. If set to SIMPLE, data buffers are copied when they are sent between IBM Storage Protect components. This option is the default. If set to PREVENT, the original data buffers are sent between IBM Storage Protect components.

For this mode, BUFFSIZE is restricted to a maximum of 896 KB. Furthermore, it cannot be selected when the IBM Storage Protect client encryption or client compression features are activated. If set to AUTO, IBM Storage Protect for ERP runs in PREVENT mode whenever the configuration supports it. Otherwise, SIMPLE mode is automatically selected. This parameter has no effect on restore operations.

BUFFSIZE n|131072
This parameter specifies the block size (in bytes) for the buffers that are used when it interacts with DB2. This parameter specifies the block size (in bytes) for the buffers that are used for disk I/O. The size of the buffers that are sent to the IBM Storage Protect API is the value of BUFFSIZE increased by approximately 20 bytes. The valid range is 4096 (4 KB) - 32 MB. Inappropriate values are adjusted automatically. If BUFFCOPY is set to PREVENT, the value of BUFFSIZE must not exceed 896 KB. If not specified, the default value is 131072 (128 KB) for UNIX or Linux systems and 32768 (32 KB) for Windows™ systems. In most cases, these values are appropriate. If you plan to increase the size of internal buffers, make sure that sufficient storage is available. The number of buffers that are acquired by IBM Storage Protect for ERP correlates to the number of files that are multiplexed in a DataStream (keyword MULTIPLEXING) multiplied by the number of sessions (keyword SESSIONS). By activating RL_COMPRESSION, the number of buffers is doubled. If not specified, the default value is 131072 (128 KB) for UNIX or Linux systems and 32768 (32 KB) for Windows systems. In most cases, these values are appropriate. If you plan to increase the size of internal buffers, make sure that sufficient storage is available. The number of buffers that are acquired by IBM Storage Protect for ERP correlates to the number of sessions (keyword SESSIONS). By activating RL_COMPRESSION, the number of buffers is doubled.
COMPR_INFO path
Specifies the file where IBM Storage Protect for ERP stores information about the compressed size of files. The path value specifies the full path and name of the file. When multiplexing is used, IBM Storage Protect for ERP attempts to optimize performance by putting files of the same size in one multiplexing stream. If RL_COMPRESSION is used in addition to multiplexing, the file sizes of the compressed files can differ very much from the original file sizes. IBM Storage Protect for ERP can collect information about the compressed file sizes and use it for further sorting of files. This file size information is stored in the file that is specified by the COMPR_INFO parameter. If backups serve as a basis for simulations, COMPR_INFO must denote a valid file and RL_COMPRESSION must be set to YES to get meaningful simulation results for compression. When the parameter RL_COMPRESSION is set to NO, this parameter has no effect. If specified, the information file is written after each backup and the information is used by the following backups and simulations. If there is no compression information about a file because of a database extension, the decompressed file size is used for sorting files.
CONFIG_FILE path/SID.bkipath/initSID.bki
Specifies the configuration file initSID.bki for IBM Storage Protect for ERP to store all variable parameters such as passwords and the date of the last password change. During processing, the string %DB2NODE is replaced automatically by the current DB2 node of a partitioned database or by NODE0000otherwise. This parameter is required.
CONFIG_FILE path/initSID.bki
Specifies the configuration file initSID.bki for IBM Storage Protect for ERP to store all variable parameters such as passwords and the date of the last password change. This parameter is required.
END
Specifies the end of the parameter definitions. IBM Storage Protect for ERP stops searching the file for keywords when END is encountered.
EXITONERROR YES|NO|n
This keyword specifies whether IBM Storage Protect for ERP exits on a backup or restore error during a BRBACKUP/BRRESTORE run. NO means do not exit if an error occurs. YES means exit if one file cannot be backed up. If a number is specified as an argument, IBM Storage Protect for ERP counts the number of errors (not warnings or attempts) and exits after the specified number of errors.

This keyword works only for the BRBACKUP/BRRESTORE runs. BRARCHIVE and RMAN activity always exit after the first error. This parameter is ignored if the BATCH parameter is set to NO.

FILE_RETRIES n|3
This parameter specifies the number of retries when a file cannot be saved or restored. This parameter has no effect if an RMAN backup/restore is started.
FRONTEND pgmname [parameterlist]
Specifies a program pgmname that is called by IBM Storage Protect for ERP in a backup run before the connection to the IBM Storage Protect server is established. If pgmname is not a fully qualified path, the default search path is used to find the program. If not specified, front-end processing is not done.
Example for UNIX or Linux: 
FRONTEND write operator@remotesite Backup of SAP database 
object is starting.
This process sends a message to a remote user before backup begins.
HDB_KEYSTORE_ENTRY string
The parameter HDB_KEYSTORE_ENTRY specifies the name of a key in the user store. The credentials of the named key are used to connect to the HANA database.
INCREMENTAL NO/CUMULATIVE/DIFFERENTIAL
This parameter specifies whether a backup is run by Oracle RMAN. If it is set to CUMULATIVE or DIFFERENTIAL, incremental backups are done by using Oracle RMAN. The default value is NO. All the other INCREMENTAL* parameters have no effect if INCREMENTAL is set to NO.
Note: This parameter can be used only when IBM Storage Protect Snapshot is used to offload backups of an SAP Oracle database from the production system and the backups on the backup server are run by Oracle RMAN.
INCREMENTAL_CATALOG_CONNECT_STRING string
This parameter specifies the name of the catalog that is passed to RMAN to connect to the catalog database. This catalog is the name of the listener for the catalog database. There is no default value. If INCREMENTAL is enabled and this value is missing, an error message is displayed.
INCREMENTAL_CATALOG_USER string
This parameter specifies the name of the user that is passed to RMAN to connect to the catalog database. There is no default value. If INCREMENTAL is enabled and this value is missing, an error message is displayed.
INCREMENTAL_CHANNELS integer in the range 1 or higher
Specifies the number of parallel RMAN channels that can transfer the data. The default is 1.
INCREMENTAL_LEVEL integer 0 or 1 [USE_AT days of week][From time TO time
The RMAN incremental level. The default for the incremental level is 0. You can optionally limit the specified incremental level to a specific time or day. If you specify a time or day, multiple occurrences of this parameter are valid while the time specification does not overlap. Time must be specified in 24 hour format. Days can be specified by weekday abbreviations like Mon, Tue, ... or by numerical values 0, 1, ..., 6 where 0 stands for Sunday and 6 for Saturday.
LOG_SERVER servername [verbosity]
The servername value specifies the name of the IBM Storage Protect server to which log messages are sent. The servername must match one of the servers that are listed in a SERVER statement in order for IBM Storage Protect for ERP messages to be logged in the IBM Storage Protect server activity log. The verbosity value can be one of these specifications: ERROR, WARNING, or DETAIL. This value determines which messages are sent. The default value is WARNING, which means that error and warning messages are sent. ERROR sends only error messages. DETAIL sends all message types (errors, warnings, and informational messages). If there is no LOG_SERVER statement in the profile, log messages are not sent to any of the IBM Storage Protect servers.
MAX_SESSIONS n|1
Specifies the maximum number of parallel IBM Storage Protect client sessions that IBM Storage Protect for ERP establishes for backup, archive (redo logs) and restore. for backup, archive (redo logs) and restore. Each session transfers one database object or, in the case of an RMAN backup or restore, a set of data blocks to or from the IBM Storage Protect server by using the IBM Storage Protect API client functions. This keyword is required. IBM Storage Protect for ERP optimizes the data transfer with attention to the physical location of the Oracle objects. Files that are stored on different volumes are backed up in parallel if multiple sessions are configured. A maximum of 32 parallel sessions can be configured. For a direct backup or restore on tape drives, the number of sessions must be less than or equal to the number of tape drives available for the backup. Make sure that the MOUNTLIMIT (mountl) parameter in the device class is set to the number of available tape drives. Make sure that the MAXNUMMP parameter of the node is set to the number of available tape drives. The value of keyword MAX_SESSIONS must be less than or equal to the sum of the SESSIONS values specified in the SERVER statements of the currently available servers.
MAX_SESSIONS n|1
Specifies the maximum number of parallel IBM Storage Protect client sessions that IBM Storage Protect for ERP establishes for backup, archive redo logs and restore. For a direct backup or restore on tape drives, the number of sessions must be less than or equal to the number of tape drives available for the backup. Make sure that the MOUNTLIMIT (mountl) parameter in the device class is set to the number of available tape drives. Make sure that the MAXNUMMP parameter of the node is set to the number of available tape drives. The value of keyword MAX_SESSIONS must be less than or equal to the sum of the SESSIONS values specified in the SERVER statements of the currently available servers.
MAX_ARCH_SESSIONS, MAX_BACK_SESSIONS, MAX_RESTORE_SESSIONS, MAX_CONTROL_SESSIONS
These parameters provide the same function as the MAX_SESSIONS parameter but they also provide a more specific use:
  • MAX_ARCH_SESSIONS defines the number of parallel sessions that are used for archive (backup of log files). Usually archive does not need as many sessions as (data file) backups since the volume is much smaller with log files. This value overrides the value of MAX_SESSIONS for the backup of database files.
  • MAX_BACK_SESSION defines the number of parallel sessions that are used for (data file) backup. This value overwrites the value of MAX_SESSIONS for the backup of database files.
  • MAX_CONTROL_SESSION defines the number of parallel sessions that are used for backing up the control files after a database or redo log backup. If MAX_CONTROL_SESSION is not specified, the number of sessions that are used for the control file backup is the same as for the corresponding database or redo log backup. Typically, for a control file backup, the number of sessions can be reduced to avoid unnecessary tape mounts. This value overwrites the value of MAX_ARCH_SESSIONS or MAX_BACK_SESSION for the backup of control files.
  • MAX_RESTORE_SESSION defines the number of parallel sessions that are used for restore. For restore, more tape drives might be available than for backup. Using more tape drives might speed up the data transfer for restore if the backup was written to a sufficiently large number of tapes. This value overwrites the value of MAX_SESSIONS for restore.
If MAX_SESSIONS is specified with one or more of these parameters, these specific parameters override the MAX_SESSIONS parameter. You must specify them all if you do not specify the MAX_SESSIONS parameter. For the valid range and the rules, see keyword MAX_SESSIONS.
MAX_VERSIONS n|0
The n value defines the maximum number of database backup versions to be kept in backup storage. The default setting for this value is 0, meaning that backup version control is disabled. Every time a full backup completes successfully, the version count is increased by an increment of 1 and stored in the IBM Storage Protect for ERP configuration file. This value is also assigned to the table space files and to all subsequent DB2 log file backups. If the number of versions that are kept in backup storage is larger than the specified maximum number of backup versions (stored by the parameter MAX_VERSIONS), the oldest version is deleted, together with the corresponding table space, incremental, and log file backups until only the specified maximum number of most recent versions remain. For partitioned DB2 databases, a backup version control is done on a partition basis. Therefore, full backups must always be initiated for all partitions at the same time, for example by the DB2 script db2_all. For details on the db2_all script, see your DB2 documentation. Also, consider these characteristics:
  • When IBM Storage Protect for ERP deletes an old full backup, all partial backups older than this full backup are also deleted.
  • If the backups are distributed over multiple IBM Storage Protect servers and one of the servers is temporarily unavailable at the time of a new full backup, it is not possible to find all the backup versions. This situation might result in retaining a backup that would otherwise delete it.
  • Every database partition needs its own configuration file. Partitions of a partitioned database must have the same BACKUPIDPREFIX.
IBM Storage Protect uses the value of the RETVER parameter (specified when a copy group is defined) to give files an expiration date. Use only one of these methods to control how long you keep backups:
  • If you use IBM Storage Protect for ERP backup version control, you must bypass this expiration function. Set the IBM Storage Protect parameter RETVER=9999 so that the files are not considered expired and are not deleted by IBM Storage Protect.
  • If you use the IBM Storage Protect expiration function, turn off the maximum number of full database backups versions control. Deactivate IBM Storage Protect for ERP backup version control by setting MAX_VERSIONS=0.
MAX_VERSIONS n|0
The n value defines the maximum number of full database backup versions to be kept in backup storage. The default setting for this value is 0, meaning that backup version control is disabled. If the number of versions that are found in backup storage is larger than the specified maximum number of backup versions (as specified by the parameter MAX_VERSIONS), the oldest versions are deleted (together with the corresponding table space and redo log files) until only the specified maximum number of most recent versions remain. Also, consider these characteristics:
  • When IBM Storage Protect for ERP deletes an old full backup, all partial backups older than this full backup are also deleted.
  • If the backups are distributed over multiple IBM Storage Protect servers and one of the servers is temporarily unavailable at the time of a new full backup, it is not possible to find all the backup versions. This situation might result in retaining a backup that would otherwise be deleted.
IBM Storage Protect uses the value of the RETVER parameter (specified when a copy group is defined) to give files an expiration date. Use only one of these methods to control how long you keep backups:
  • If you use IBM Storage Protect for ERP backup version control, you must bypass this expiration function. Set the IBM Storage Protect parameter RETVER=9999 so that the files are not considered expired and are not deleted by IBM Storage Protect.
  • If you use the IBM Storage Protect expiration function, turn off IBM Storage Protect for ERP backup version control. Deactivate IBM Storage Protect for ERP backup version control by setting MAX_VERSIONS=0.
MAX_VERSIONS n|0
The n value defines the maximum number of full database backup versions to be kept in backup storage. The default setting for this value is 0, meaning that backup version control is disabled. If the number of versions that are found in backup storage is larger than the specified maximum number of backup versions (as specified by the parameter MAX_VERSIONS), the oldest versions are deleted (together with the corresponding table space and redo log files) until only the specified maximum number of most recent versions remain. Also, consider these characteristics:
  • When IBM Storage Protect for ERP deletes an old full backup, all partial backups older than this full backup are also deleted.
  • If the backups are distributed over multiple IBM Storage Protect servers and one of the servers is temporarily unavailable at the time of a new full backup, it is not possible to find all the backup versions. This situation might result in retaining a backup that would otherwise be deleted.
IBM Storage Protect uses the value of the RETVER parameter (specified when a copy group is defined) to give files an expiration date. Use only one of these methods to control how long you keep backups:
  • If you use IBM Storage Protect for ERP backup version control, you must bypass this expiration function. Set the IBM Storage Protect parameter RETVER=9999 so that the files are not considered expired and are not deleted by IBM Storage Protect.
  • If you use the IBM Storage Protect expiration function, turn off IBM Storage Protect for ERP backup version control. Deactivate IBM Storage Protect for ERP backup version control by setting MAX_VERSIONS=0.
MULTIPLEXING n|1
Specifies the number of files, which are multiplexed into one DataStream. The allowed range is 1 - 8. The optimal value depends on the actual hardware environment. Multiplexing is most effective when fast tape access exists, fast networks are available, database files are compressed, and the CPU load is moderate. Optimal values are in the range 1 - 4. If not specified, the default value of 1 means multiplexing is not used. This parameter has no effect if an RMAN backup or restore operation is started.
PASSWORDREQUIRED NO|YES
Specifies whether IBM Storage Protect requires a password to be supplied by the IBM Storage Protect client. This situation depends on the IBM Storage Protect installation. If not specified, the default is PASSWORDREQUIRED YES, which implements manual password handling. This parameter must be defined with the respective SERVER statement, as shown in the sample profile.
REDOLOG_COPIES n|1
Specifies the number of copies IBM Storage Protect for ERP stores for each processed redo log file.Oracle redo log. DB2 log file. The valid range is 1 - 9. If not specified, IBM Storage Protect for ERP stores one copy of the redo logs the redo logseach log file. The number of different management classes for archived logs (keyword BRARCHIVEMGTCLASS specified must be greater than or equal to the number of log file copies specified. The number of different management classes that are specified must be greater than or equal to the number of log file copies specified.
REPORT NO|YES|2
If set to YES, IBM Storage Protect for ERP produces more information such as information about transferred files. If set to 2, IBM Storage Protect for ERP generates an extra summary report that contains detailed backup and restore performance statistics. This summary is displayed at the end of the complete operation. The output is sent to stdout, which is typically the console. If not specified, the default is REPORT NO. This keyword has no effect if an RMAN backup or restore operation is started.
RL_COMPRESSION NO|YES
If set to YES, IBM Storage Protect for ERP runs a null block compression of the data before they are sent over the network. Although RL compression introduces more CPU load, throughput can be improved when the network is the bottleneck. It is not advised to use RL compression together with the IBM Storage Protect API compression. If not specified, the default value is NO meaning null block compression is not done. RL_COMPRESSION is only run if a full database backup (BRBACKUP) was started. The offline log files (BRARCHIVE) are not compressed.
SEGMENTSIZE size[GB|TB]
This keyword specifies the maximum size of the segments that are split from large backup objects. The required size value must be a positive integer equal to or greater than 1. Consider these characteristics when you specify this parameter:
  • The scale units (GB or TB) are not required. GB is the default value.
  • When you specify the scale units (GB or TB), you can use lowercase letters, uppercase letters, or a combination of both cases. However, you cannot specify single-character abbreviations (G or T).
  • When this parameter is not specified, one backup object per DB2 backup session is transferred to IBM Storage Protect.
  • If the specified segment size is less than the DB2 block size specified during the backup, the specified segment size is ignored at run time. The specified DB2 backup block size is used instead.
The following example sets the maximum size of the backup objects segments on IBM Storage Protect to 100 GB: 
SEGMENTSIZE   100 GB

You can also specify the command in the following way:

SEGMENTSIZE   100
SERVER servername
This keyword specifies the name of the IBM Storage Protect server to which IBM Storage Protect for ERP backups are to be stored. This statement begins a server section in the IBM Storage Protect for ERP profile. At least one server section is required. Server sections are at the end of the profile. A server section ends before a following SERVER keyword, before the END keyword, or at the end of the profile. These dependent keywords are applicable in a server section:
  • ADSMNODE
  • BRARCHIVEMGTCLASS
  • BRBACKUPMGTCLASS
  • PASSWORDREQUIRED
  • SESSIONS
  • TCP_ADDRESS
  • USE_AT

The server name must be defined in the IBM Storage Protect profile dsm.sys. To set up alternate or parallel paths, each path is denoted by its own logical server name and corresponding server section, although these logical names refer to the same server. In this case, the profiles specify the same TCP/IP address for these server names. To set up alternate or parallel servers, each server is represented by one or more server statements and the corresponding server sections (depending on the number of paths to the server). In this case, the profiles specify different TCP/IP addresses for the different servers.

The server name must be defined in the IBM Storage Protect profiles dsm.sys (UNIX, Linux) or servername.opt (for Windows). To set up alternate or parallel paths, each path is denoted by its own logical server name and corresponding server section, although these logical names refer to the same server. In this case, the profiles specify the same TCP/IP address for these server names. To set up alternate or parallel servers, each server is represented by one or more server statements and the corresponding server sections (depending on the number of paths to the server). In this case, the profiles specify different TCP/IP addresses for the different servers. Do NOT use any profile keywords, ADSM, or TSM as the server name.

SESSIONS n|1
The n value specifies the number of parallel sessions IBM Storage Protect for ERP uses for the server. This keyword is required in every server section. This parameter must be defined with the respective SERVER statement, as shown in the sample profile.
SORT_FILE
To do a manual sort, a file must be created (sortfile). This example of sortfile contents is given: 
/path/filename1 disknumber
/path/filename2 disknumber
    .
     .
     .
/path/filenameN disknumber
The disk numbers are counted 1 - n. They do not have any relation to the physical disks. You must specify only the same number for the files on the same physical disk.
TCP_ADDRESSIP address of server
Specifies the IP address of the IBM Storage Protect server in dotted decimal notation. This parameter overrides the value for the parameter TCPSERVERADDRESS in the IBM Storage Protect client system options file (dsm.sys) on UNIX or Linux or in the client options file (servername.opt) on Windows. This parameter must be defined with the respective SERVER statement, as shown in the sample profile.
TCP_ADDRESS
Specifies the IP address of the IBM Storage Protect server in dotted decimal notation. This parameter overrides the value for the parameter TCPSERVERADDRESS in the IBM Storage Protect client system options file (dsm.sys) on UNIX or Linux or in the client options file (servername.opt) on Windows. The parameter TCP_ADDRESS must be defined with the respective SERVER statement as shown in the sample profile.
TRACE FILEIO_MIN | FILEIO_MAX | COMPR_MIN | COMPR_MAX | MUX_MIN | MUX_MAX | TSM_MIN | TSM_MAX | ASYNC_MIN | ASYNC_MAX | APPLICATION_MIN | APPLICATION_MAX | SYSCALL_MIN | SYSCALL_MAX | COMM_MIN | COMM_MAX | DEADLOCK_MIN | DEADLOCK_MAX | PROLE_MIN | PROLE_MAX | BLAPI_MIN | BLAPI_MAX | SOCKET_DATA | ALL | OFF
This parameter writes trace information to the file specified with the TRACEFILE parameter. Arguments to TRACE can be any combination of the possible components and levels that are separated by spaces. A trace is written only if both TRACE and TRACEFILE are specified. Do not use this parameter unless instructed to use it by IBM Storage Protect for ERP support. Using it can significantly deteriorate the performance of IBM Storage Protect for ERP.
TRACEFILE path
Specifies the name and location of the trace file for IBM Storage Protect for ERP to store all trace information. When TRACE is used, path specifies the full path and the name of file. If the value of TRACEFILE contains the string %BID, this string is replaced by the backup ID to get the path and name of the trace file used. For example, specifying /tmp/%BID.trace yields a trace file /tmp/myBackup.trace for backup ID myBackup. A trace is written only if both TRACE and TRACEFILE are specified.
TRACEMAX n
Specifies the maximum size of the trace file in KB. The valid range is 4096 (4 MB) - unlimited. If not specified, the trace file size is unlimited.
USE_AT days
Specifies the days that the IBM Storage Protect server (specified with the corresponding SERVER keyword) is used. The days value can be numbers in the range 0 (Sunday) - 6 (Saturday). Multiple numbers can be used when separated by spaces. If not specified, the default is to use the IBM Storage Protect server on all days. Make sure that the same IBM Storage Protect server is used for a simulation and its corresponding basis production backup. The parameter USE_AT must be defined with the respective SERVER statement as shown in the sample profile. The parameter has no effect on actions other than on a backup.This parameter must be defined with the respective SERVER statement. The parameter USE_AT has no effect on actions other than on a backup.