Hej det gør jeg lige men selve filen mangler ? jeg har dog ikke lavet nogle fixes og updates endnu da jeg startede igår morgens med installeringen. Men selve opt filen ser sådan ud. (noter at der er 2 opt filer en dsmserv.opt (som jeg selv lavede da den hed dsmserv.opt.smp (muliti kernel)).
-------------------------------------
dsmserv.opt filen ser så ledes ud:
-------------------------------------
* ====================================================================
* Tivoli Storage Manager
*
* 5698-TSM (C) Copyright IBM Corporation, 1990, 2003, All Rights Reserved.
* ====================================================================
* Sample Server Options File (dsmserv.opt.smp)
* Platform: Linux
*
* This file contains descriptions of all the options you can set
* in the server options file.
* Use this file as a quick reference or to customize your options files.
* You can copy sample options from this file to your server options file.
*
* Understanding the Syntax for Entering Options
* ---------------------------------------------
* Options consist of keywords and their values.
*
* If the option is supported in an options file, an example is
* shown with the following syntax:
*
* OPTION Parameter
*
* Keywords name the option. You can enter the entire keyword or
* the abbreviation, which is identified by uppercase characters.
* To enter an option in an options file, enter the option name
* followed by one or more blank spaces, followed by option
* parameters. When editing an options file, follow these guidelines:
*
* - Options can begin in any column of the input line.
* - Only one option can be on each line, and the option cannot
* span more than one line.
* - Keywords can be in uppercase or lowercase characters. The
* minimum abbreviation is shown in uppercase characters.
* - One or more blank spaces are allowed between keywords and values.
* - Blank lines are allowed in the file and are interpreted
* as comment lines.
* - Lines beginning with an asterisk (*) are interpreted as
* comment lines.
* - File names must be correctly specified, as required by
* your operating system.
*
* Verification of Selected Options
* ---------------------------------------------
* At server initialization, the server reads the server options file.
* If you make any changes to the server options file, you must stop
* and then start the server to have the server read the updated
* options file.
*
* During server initialization, the server will process the server
* options file and will display a warning message for any unknown
* option that is encountered. No warning messages will be displayed
* when the server recognizes all options in the server options file.
*
* After the server is running, you can issue the command:
*
* query option
*
* to see a list of all of the options that are in effect.
*
* ====================================================================
* Choosing Communication Method(s)
*
* To bring up the server with no communicatons method, specify
*
* COMMmethod NONE
*
* Otherwise, for each communication method to be used, specify
*
COMMmethod TCPIP
COMMmethod HTTP
* COMMmethod SNMP
*
* Note that the option file can include a set of communication
* method options. If COMMmethod NONE is included in the set
* it will override all other communication options.
*
* Example - To use both TCPIP and HTTP, specify
* COMMmethod TCPIP
* COMMmethod HTTP
*
* Example - To bring up the server with no communications method,
* specify:
*
* COMMmethod NONE
*
* Setting Communication Method Options
*
* Use the following options to set communication options:
*
* =====================================================================
*
* TCPIP
*
* ********************************************************************
* TCPport
*
* Specifies the TCP/IP port used to connect to the server.
*
* Syntax
* +------------------+----------------------------------------------+
* | TCPport | port_addr |
* +------------------+----------------------------------------------+
*
* Parameters
* port_addr Specifies the port address. The default is 1500.
* You can specify a value from 1024 to 32767.
* Contact your system administrator for this value.
*
TCPPort 1500
*
* Note: TCPADMINPort also defaults to 1500; If both TCPADMINPort and
* TCPport default to or are set to the same value, a single thread
* handles communications with both client and server sessions.
* If they differ, the port set with the TCPADMINPort option is
* is restricted to administrative ( and server-server ) communications.
* In this case, administrative ( and server-server ) communications
* are still allowed to use the port set with the TCPport option,
* but non-administrative client sesssions may not use the port
* specified with the TCPADMINPort option.
* Administrative client sessions, i.e., client session for which
* a node-administrator userid is used, may use the port specified
* with the TCPADMINPort option.
*
* =====================================================================
*
* ********************************************************************
* TCPADMINPort
*
* Specifies a TCP/IP port restricted to administrative-type sessions
*
* Syntax
* +------------------+----------------------------------------------+
* | TCPADMINPort | port_addr |
* +------------------+----------------------------------------------+
*
* Parameters
* port_addr Specifies the port address. The default is 1500.
* You can specify a value from 1024 to 32767.
* Contact your system administrator for this value.
*
TCPADMINPort 1500
*
* Note: TCPport also defaults to 1500; If both TCPADMINPort and
* TCPport default to or are set to the same value, a single thread
* handles communications with both client and server sessions.
* If they differ, the port set with the TCPADMINPort option is
* is restricted to administrative ( and server-server ) communications.
* In this case, administrative ( and server-server ) communications
* are still allowed to use the port set with the TCPport option,
* but non-administrative client sesssions may not use the port
* specified with the TCPADMINPort option.
* Administrative client sessions, i.e., client session for which
* a node-administrator userid is used, may use the port specified
* with the TCPADMINPort option.
*
*
* =====================================================================
*
* ********************************************************************
* TCPWindowsize
*
* Specifies the amount of data to send or receive
* before TCP/IP exchanges acknowledgements with the client node.
* This actual window size that is used in a session will be the
* minimum size of the server and client window sizes.
* Larger window sizes may improve performance
* at the expense of memory usage.
*
*
* Syntax
* +------------------+----------------------------------------------+
* | TCPWindowsize | window_size |
* +------------------+----------------------------------------------+
*
* Parameters
* window_size Specifies the TCP/IP windowsize in kilobytes.
* You can specify a value from 0 to 2048.
* 0 indicates that the default window size set
* for Linux should be used. Values from 1 to 2048
* indicate that the window size is in the
* range of 1K to 2M.
* The default window size is 0 which indicates
* that the server should accept the system default
* TCP window size.
*
*
* NOTE!! if we use a remote sites in the TSM setup then consider making the size bigger ex. 16 or 512 or 2048 (MAX)
TCPWindowsize 0
*
* =====================================================================
* TCPNODELAY
*
* ********************************************************************
*
* Specifies whether the server should send small amounts
* of data or allow TCP/IP to buffer the data.
* Disallowing buffering may improve throughput at the expense
* of more packets being sent over the network. .
*
*
* Syntax
* +------------------+----------------------------------------------+
* | TCPNODELAY | YES | NO |
* +------------------+----------------------------------------------+
*
* Parameters
* YES Specifies that TCP/IP should not buffer small
* messages.
*
* NO Specifies that TCP/IP should buffer small
* messages
*
* The default value is YES.
*
TCPNODELAY YES
*
*
*
* =====================================================================
*
* HTTP
*
* ********************************************************************
* Syntax
* +------------------+----------------------------------------------+
* | HTTPPort | port_addr |
* +------------------+----------------------------------------------+
*
* Parameters
* port_addr Specifies the port address. The default is 1580.
* Port number on which to listen for Browser connections.
* You can specify a value from 1024 to 32767.
* Contact your system administrator for this value.
* HTTP commmethod is used to enable a Web-browser based administrative
* interface
*
* HTTPPort portnumber
* Port number on which to listen for Browser connections.
* The default for portnumber is 1580.
* The range is 1-32767.
*
HTTPPort 1580
* =====================================================================
*
* SNMP
*
* ********************************************************************
* The SNMP commmethod is used to enable communication between
* a server and a subagent which communicates with an
* SNMP agent. The SNMPSUBAGENTHOST, SNMPSUBAGENTPORT, and
* SNMPHEARTBEATINTERVAL options control communications between
* the server and the subagent ( dsmsnmp ). The subagent
* should be started before starting the server.
* Related Files:
* adsmserv.mib is the Management Information Base (MIB)
* file that gets loaded into an SNMP manager program like
* NetView.
* aix.adsm.defs is a file that may be added to the end
* of /etc/mib.defs to allow the snmpinfo command to show
* ADSM MIB variable names.
*
* SNMPSUBAGENTHOST hostname
* Local hostname or TCP/IP address on which the subagent
* (dsmsnmp) is running. The default is 127.0.0.1.
* SNMPSUBAGENTPORT portname
* Port number on which the subagent is listening for
* connections from TSM servers.
* The default is 1521.
* The range is from 1000-32767.
* SNMPHEARTBEATINTERVAL minutes
* The amount of time to wait between heartbeat checkins
* with the subagent. The subagent maintains a timestamp
* for each server as to when it last checked in with the
* subagent ( this is the heartbeat ).
* The default is 5 minutes.
* The range is 0 to 1440 minutes. For 0 minutes, no
* heartbeat is maintained other than the initial contact.
*
* SNMPSUBAGENT HOSTname agent-host COMMunityname comm TIMEOUT time-secs
* This option is ignored by the server and read only by
* the SNMP subagent (dsmsnmp). It configures communications
* between the subagent and the SNMP agent.
* agent-host The hostname or TCP/IP address on which
* the SNMP agent is running. This should
* be the same as the local host name.
* The default is 127.0.0.1.
* comm The SNMP community name that allows
* contact with the SNMP agent ( this is
* a password the SNMP agent gets from it's
* configuration files ). The default
* is public.
* time-secs The amount of time to allow for a response
* from the SNMP agent. The default is
* is 600 seconds. The range is 1-86400.
*
* SNMPMESSAGECATEGORY [SEVERITY | INDIVIDUAL]
* --------
* This options is ignored by the server and read only
* by the SNMP subagent ( dsmsnmp ).
* The default is SEVERITY.
* If SEVERITY is specified or defaulted, messages
* sent by the server are routed through the subagent
* to the SNMP agent and on to the SNMP manger as one
* of four TRAP-TYPES. Each TRAP-TYPE corresponds to the
* message's severity. Severity 1 messages are severe errors.
* Severity 2 messages are warning messages.
* Severity 3 messages are error messages.
* Severity 4 messages are informational.
* The types of messages which may be forwarded are controlled
* by configuration of central logging functions in the
* server.
* If INDIVIDUAL is specified, each TRAP-TYPE corresponds
* to the numeric portion of the message. For example,
* if message ANR4483E is issued and INDIVIDUAL is specified,
* TRAP-TYPE 4483 will be forwared to the SNMP manager.
*
*
* MSGINTERVAL
*
* ********************************************************************
* MSGINTerval
*
* Specifies the number of minutes to wait between issuing a mount-tape
* tape message on the server console.
*
* Syntax
* +------------------+----------------------------------------------+
* | MSGINTerval | value |
* +------------------+----------------------------------------------+
*
* Parameters
* value Specifies the time between each reminder
* message that the server generates for manual
* mount requests. The default value
* is 1 minute. The minimum value is 1 minute.
*
* Examples
* MSGINTerval 1
*
* =====================================================================
* =====================================================================
* Section II -- Options common to all server platforms.
* ====================================================================
* =====================================================================
*
* MAXSESSIONS
*
* ********************************************************************
* MAXSessions
*
* Specifies the number of simultaneous client sessions.
*
* Syntax
* +------------------+----------------------------------------------+
* | MAXSessions | value |
* +------------------+----------------------------------------------+
*
* Parameters
* value Specifies the number of simultaneous client
* sessions. The minimum value is 2 and the
* default value is 25.
*
MAXSessions 25
*
* =====================================================================
*
* BUFPOOLSIZE
*
* ********************************************************************
* BUFPoolsize
*
* Specifies the size of the database buffer pool in Kbytes.
*
* Syntax
* +------------------+----------------------------------------------+
* | BUFPoolsize | value |
* +------------------+----------------------------------------------+
*
* Parameters
* value Specifies the size of the database buffer pool
* in Kbytes. The minimum value is 256 and the
* default value is 2048.
*
* Examples NOTE is this RAM (CMJ)
BUFPoolsize 2048
*
* Note: If SELFTUNEBUFpoolsize YES is also specified in the options
* this value becomes the starting point for managing the size
* of the buffer pool.
* =====================================================================
*
* LOGPOOLSIZE
*
* ********************************************************************
* LOGPoolsize
*
* Specifies the size of the log buffer pool in Kbytes.
*
* Syntax
* +------------------+----------------------------------------------+
* | LOGPoolsize | value |
* +------------------+----------------------------------------------+
*
* Parameters
* value Specifies the size of the log buffer pool
* in Kbytes. The minimum value is 128 and the
* default value is 512.
*
LOGPoolsize 512
*
* =====================================================================
*
* TXNGROUPMAX
*
* ********************************************************************
* TXNGroupmax
*
* Specifies the maximum number of files transferred as a group between
* the client and server.
*
* Syntax
* +------------------+----------------------------------------------+
* | TXNGroupmax | value |
* +------------------+----------------------------------------------+
*
* Parameters
* value Specifies the maximum number of files that are
* transferred as a group between the client and
* server. The minimum value is 4 and the maximum
* value is 256. The default value is 40.
*
TXNGroupmax 40
*
* =====================================================================
*
* COMMTIMEOUT
*
* ********************************************************************
* COMMTimeout
*
* Specifies the communication timeout value in seconds.
*
* Syntax
* +------------------+----------------------------------------------+
* | COMMTimeout | value |
* +------------------+----------------------------------------------+
*
* Parameters
* value Specifies the communication timeout value in
* seconds. The minimum value is 0. The default
* value is 60.
*
COMMTimeout 60
*
* =====================================================================
*
* IDLETIMEOUT
*
* ********************************************************************
* IDLETimeout
*
* Specifies the number of minutes that a client session can be idle
* before its session will be canceled.
*
* Syntax
* +------------------+----------------------------------------------+
* | IDLETimeout | value |
* +------------------+----------------------------------------------+
*
* Parameters
* value Specifies the number of minutes that a client
* session can be idle before the server cancels
* its session. The minimum value is 0. The
* default value is 15.
*
IDLETimeout 15
*
* =====================================================================
*
* LANGUAGE
*
* ********************************************************************
* LANGuage
*
* Specifies the language to use for help and error messages.
*
* Syntax
* +------------------+----------------------------------------------+
* | LANGuage | name |
* +------------------+----------------------------------------------+
*
* Parameters
* name Specifies the language to use for help and
* error messages. The name of the language
* must be between 1 and 16 characters. The
* default name is "en_US."
*
LANGuage en_US
*
* =====================================================================
*
* DATEFORMAT
*
* ********************************************************************
* DATEformat
*
* Specifies the format in which date references will be displayed.
*
* Syntax
* +------------------+----------------------------------------------+
* | DATEformat | value |
* +------------------+----------------------------------------------+
*
* Parameters
* value Specifies the date format. Valid values
* include:
* 1 = MM/DD/YYYY
* 2 = DD-MM-YYYY
* 3 = YYYY-MM-DD
* 4 = DD.MM.YYYY
* 5 = YYYY.MM.DD
*
DATEformat 2
*
* =====================================================================
*
* TIMEFORMAT
*
* ********************************************************************
* TIMEformat
*
* Specifies the format in which time references will be displayed.
*
* Syntax
* +------------------+----------------------------------------------+
* | TIMEformat | value |
* +------------------+----------------------------------------------+
*
* Parameters
* value Specifies the time format. Valid values
* include:
* 1 = HH:MM:SS
* 2 = HH,MM,SS
* 3 = HH.MM.SS
* 4 = HH:MM:SSA/P (12 hrs)
*
TIMEformat 1
*
* =====================================================================
*
* NUMBERFORMAT
*
* ********************************************************************
* NUMberformat
*
* Specifies the format in which number references will be displayed.
*
* Syntax
* +------------------+----------------------------------------------+
* | NUMberformat | value |
* +------------------+----------------------------------------------+
*
* Parameters
* value Specifies the number format. Valid values
* include:
*
* thousand seperator decmal point seperator
* 1 = ',' '.'
* 2 = ',' ','
* 3 = ' ' ','
* 4 = ' ' '.'
* 5 = '.' ','
* 6 = ''' ','
*
NUMberformat 5
*
* =====================================================================
*
* EXPINTERVAL
*
* ********************************************************************
* EXPInterval
*
* Specifies the number of hours between automatic inventory expiration
* runs.
*
* Syntax
* +------------------+----------------------------------------------+
* | EXPInterval | value |
* +------------------+----------------------------------------------+
*
* Parameters
* value Specifies the number of hours between automatic
* inventory expiration runs. The minimum value
* is 0, where automatic expiration will not
* execute and must be started with the
* EXPIRE INVENTORY command. The maximum value
* is 336 (14 days). ','
*
* NOTE: if it is set to 0 then the inventory will only be valid when run manual!
EXPInterval 24
*
* =====================================================================
* MIRRORREAD
*
* ********************************************************************
* MIRRORRead
*
* Specifies the mode used for reading recovery log pages or data base
* log pages
*
* Syntax
* +------------------+-----------+----------------------------------+
* | MIRRORRead | LOG | DB | Normal | Verify |
* +------------------+-----------+----------------------------------+
*
* Parameters
* LOG specifies that the mode for reading recovery
* log pages is being specified.
*
* DB specifies that the mode for reading database
* pages is being specified.
*
* Normal specifies that only one mirrored volume is
* read to obtain the desired page. This is the
* default. ','
*
* Verify specifies that the server read all mirror
* volumes for a page every time a recovery log
* or database page is read. If an invalid page
* is encountered on a mirror volume, it is
* automatically resynchronized with valid contents
* from another mirror volume. This mode decreases
* server performance since each mirror volume for
* the page is accessed on every read.
*
MIRRORREAD LOG NORMAL
MIRRORREAD DB NORMAL
* =====================================================================
*
* MIRRORWRITE
*
* ********************************************************************
* MIRRORWrite
*
* Specifies how mirrored volumes are accessed when the server writes
* pages to the recovery log or database during normal processing.
*
* Syntax
* +------------------+-----------+----------------------------------+
* | MIRRORWrite | LOG | DB | Sequential | Parallel |
* +------------------+-----------+----------------------------------+
*
* Parameters
* LOG specifies that the mode for writing recovery
* log pages is being specified.
*
* DB specifies that the mode for writing database
* pages is being specified.
*
* Sequential specifies that one mirror is written to
* successfully before other mirrored volumes are
* directed to write their page. A decrease in
* server performance is experienced because a
* successful I/O must occur before the other
* mirrored writes can begin. This parameter is
* the default when DB is specified.
*
* Parallel specifies that all mirrors are written to in
* parallel. This mode allows all mirrors to
* obtain the new page at approximately the same
* time. If a system outage occurs at exactly
* the instant that each mirror is partially
* complete in writing its page, a partial write
* to each mirror could result. This parameter
* is the default when LOG is specified.
*
* Examples
MIRRORWRITE LOG PARALLEL
MIRRORWRITE DB SEQUENTIAL
* =====================================================================
*
* VOLUMEHISTORY
* ********************************************************************
* VOLUMEHistory <filename>
*
* Specifies the name of a file that should contain sequential
* volume history information when it is changed by the server.
* Sequential volume history information is used by the administrator
* and server processes during server database recovery.
*
* More than one of these parameters may be specified to record
* sequential volume history information to multiple files
*
* Syntax
* +------------------+----------------------------------------------+
* | VOLUMEHistory | filename |
* +------------------+----------------------------------------------+
*
* Parameters
* filename - a fully-qualified file name
* to which the server is to automatically
* record volume history information
* when it changes
VOLUMEHistory /tsm/files/primary/volhist1.out
VOLUMEHistory /tsm/files/copy/volhist2.out
* =====================================================================
*
* DEVCONFIG
* ********************************************************************
* DEVCONFig <filename>
*
* Specifies the name of a file that should contain device
* configuration information when it is changed by the server.
* Device configuration information is used by the
* server processes during server database recovery or load and
* DSMSERV DUMPDB processing.
*
* More than one of these parameters may be specified to record
* device configuration information to multiple files.
*
* Syntax
* +------------------+----------------------------------------------+
* | DEVCONFig | filename |
* +------------------+----------------------------------------------+
*
* Parameters
* filename - a fully-qualified file name
* to which the server is to automatically
* record device configuration
* information when it changes.
DEVCONFig /tsm/files/primary/devconfg1.out
DEVCONFig /tsm/files/copy/devconfg2.out
* =====================================================================
*
* MOVEBATCHSIZE
* ********************************************************************
* MOVEBatchsize <nnn>
*
* Specifies the maximum number of client files that can be
* grouped together in a batch within the same server transaction
* for storage pool backup/restore, migration, reclamation, or
* move data operations. Specifying a larger number may improve
* performance but will require more server recovery log space.
*
* Any number between 1 and 256 (inclusive) may be specified.
* The default is 40.
*
* This parameter works with the MOVESIZETHRESH parameter below, in the
* following manner:
*
* The number of client files moved for each server database transaction
* during a server storage pool backup/restore, migration, reclamation or
* move data operation will be determined by the number and size of the
* files in the batch. If the number of files in the batch becomes
* equivalent to the MOVEBATCHSIZE before the cumulative size of the files
* becomes greater than the MOVESIZETHRESH, then the MOVEBATCHSIZE is used
* to determine the number of files moved or copied in the transaction. If
* the cumulative size of files being gathered for a move or copy operation
* exceeds the MOVESIZETHRESH value before the number of files becomes
* equivalent to the MOVEBATCHSIZE, then the MOVESIZETHRESH value is used
* to determine the number of files moved or copied in the transaction.
*
* Syntax
* +------------------+----------------------------------------------+
* | MOVEBatchsize | nnn |
* +------------------+----------------------------------------------+
*
* Parameters
* nnn - the number of files that should be batched
* in the same server transaction for server
* storage pool backup/restore, migration,
* reclamation, or move data operations.
* Values: 1-256 Default: 40
*
* Note: If the SELFTUNETXNsize option is specifed in the
* server options file the MOVEBATCHSIZE option will be set
* to its maximum value to optimize server throughput. To
* prevent running out of log space the * customer should use
* the DEFINE SPACETRIGGER command to * create a log space
* trigger. This will allow for dyanmic * expansion of the
* recovery log.
*
* =====================================================================
*
* MOVESIZETHRESH
* ********************************************************************
* MOVESizethresh <nnn>
*
* Specifies a threshold, in megabytes, for the amount of data moved
* as a batch within the same server transaction for storage pool
* backup/restore, migration, reclamation, or move data operations.
* When this threshold is reached, no more files are added to the current
* batch, and a new server transaction is started after the batch is
* moved.
*
* Specifying a larger number may improve performance but will
* require more server recovery log space.
*
* Any number between 1 and 500 (inclusive) may be specified.
* The default is 500 (megabytes).
*
* This parameter works with the MOVEBATCHSIZE parameter above, in the
* following manner:
*
* The number of client files moved for each server database transaction
* during a server storage pool backup/restore, migration, reclamation or
* move data operation will be determined by the number and size of the
* files in the batch. If the number of files in the batch becomes
* equivalent to the MOVEBATCHSIZE before the cumulative size of the files
* becomes greater than the MOVESIZETHRESH, then the MOVEBATCHSIZE is used
* to determine the number of files moved or copied in the transaction. If
* the cumulative size of files being gathered for a move or copy operation
* exceeds the MOVESIZETHRESH value before the number of files becomes
* equivalent to the MOVEBATCHSIZE, then the MOVESIZETHRESH value is used
* to determine the number of files moved or copied in the transaction.
*
* Syntax
* +------------------+----------------------------------------------+
* | MOVESizethresh | nnn |
* +------------------+----------------------------------------------+
*
* Parameters
* nnn - the threshold in megabytes for data
* that may be batched
* in the same server transaction for server
* storage pool backup/restore, migration,
* reclamation, or move data operations.
* Values: 1-500 Default: 500
*
* Note: If the SELFTUNETXNsize option is specifed in the
* server options file the MOVESIZETHRESH option will be set
* to its maximum value to optimize server throughput. To
* prevent running out of log space the * customer should use
* the DEFINE SPACETRIGGER command to * create a log space
* trigger. This will allow for dyanmic * expansion of the
* recovery log.
* =====================================================================
*
* USELARGEBUFFERS
*
* ********************************************************************
*
* Specifies whether the server should use larger buffers for transfering
* data, when processing large files (greater than 500KB). Larger buffers
* can increase server performance, but they increase the overall memory
* requirements of the server.
*
* Syntax
* +------------------+----------------------------------------------+
* | USELARGebuffers | Yes | No |
* +------------------+----------------------------------------------+
*
* Parameters
* YES Specifies that the server should use large buffers
*
* NO Specifies that the server should not use large
* buffers
*
* The default value is YES.
*
USELARGEBUFFERS YES
*
*
*==============================================================================
*
* EVENTSERVER
*
* Specifies whether, at startup, the server should try to contact the event
* server.
*
* Syntax
* +-------------------+-----+----+
* | EVENTSERVer | YES | NO |
* +-------------------+-----+----+
*
* Parameters:
* Yes Specifies that, at startup, the server tries to
* contact the event server. Contact occurs only if
* a DEFINE EVENTSERVER command has already been
* issued.
* No Specifies that, at startup, the server does not
* try to contact the event server.
*
* The default value is YES.
*
EVENTSERVer YES
*==============================================================================
*
* FILEEXIT
*
* Allow events to be saved to a file, in TSM native event record format.
* -- NOTE: Events generated are written to file exit when generated, but
* the system may not perform the actual physical write until sometime
* later - so events may not show up in the file right after they
* are generated by the server/client.
*
* Be sure to enable events to be saved (ENABLE EVENTLOGGING FILE ...)
* in addition to activating the file exit receiver.
*
* FILEEXit [YES | NO] <filename> [APPEND | REPLACE | PRESERVE]
*
* Parameters:
* [YES | NO] - Inform server to ACTIVATE the file exit receiver
* during startup. This is analogous to issuing
* a BEGIN EVENTLOGGING FILE on the server console.
* <filename> - The name of the file to save generated events to.
* If the filename does not begin with a '/' or '.',
* then the DSMSERV_DIR environment variable is
* prepended to the filename.
* [ APPEND - Append event information to the file specified.
* If the file did not exist, create it. If the
* file already exists, NO check is performed
* to ensure that the data already existing are
* TSM event records.
* REPLACE - If the file aready exists, replace the contents
* with new event records. All current data is
* destroyed before the first event is written.
* If the file did not exist previously, create it.
* PRESERVE]- If the file already exists, do not overwrite or
* append.
*
FILEEXit YES ./fileexit.out APPEND
*======================================================================
*
* USEREXIT
*
* Allow events to be sent to a C-function named "adsmV3UserExit" for
* processing.
*
* Be sure to enable events to be saved (ENABLE EVENTLOGGING USEREXIT ...)
* in addition to activating the userexit receiver.
*
* USEREXit [YES | NO] <C-compiled Module Name>
*
* Use the sample Makefile provided to create the specially formatted
* C-compiled Module.
*
* Parameters:
* [YES | NO] - Inform server to ACTIVATE the userexit receiver
* during startup. This is analogous to issuing
* a BEGIN EVENTLOGGING USEREXIT on the server console.
* <C-compiled> - The name of the module. If the module name
* does not begin with a '/' or '.', then the
* DSMSERV_DIR environment variable is prepended
* to the module name.
*
*======================================================================
*
* FILETEXTEXIT
*
* Allow events to be saved to a file in ASCII formatted fields. Each
* event is stored in a separate line. Each field is separated by a single
* space.
*
* -- NOTE: Events generated are written to filetext exit when generated,
* but Linux may not perform the actual physical write until
* sometime later - so events may not show up in the file right
* after they are generated by the server/client.
*
* Be sure to enable events to be saved (ENABLE EVENTLOGGING FILETEXT ...)
* in addition to activating the filetext exit receiver.
*
* FILETExtexit [YES | NO] <filename> [APPEND | REPLACE | PRESERVE]
*
* Parameters:
* [YES | NO] - Inform server to ACTIVATE the filetext exit receiver
* during startup. This is analogous to issuing
* a BEGIN EVENTLOGGING FILETEXT on the server console.
* <filename> - The name of the file to save generated events to.
* If the filename does not begin with a '/' or '.',
* then the DSMSERV_DIR environment variable is
* prepended to the filename.
* [ APPEND - Append event information to the file specified.
* If the file did not exist, create it. If the
* file already exists, NO check is performed
* to ensure that the data already existing are
* TSM event records.
* REPLACE - If the file aready exists, replace the contents
* with new event records. All current data is
* destroyed before the first event is written.
* If the file did not exist previously, create it.
* PRESERVE]- If the file already exists, do not overwrite or
* append.
*
FILETExtexit YES .../tivoli/tsm/server/bin/filetextexit.out APPEND
*======================================================================
*
* TIVOLI RECEIVER
*
* Allow events to be sent to a Tivoli Enterprise Console
*
* Be sure to enable events to be saved (ENABLE EVENTLOGGING TIVOLI ...)
* in addition to activating the tivoli receiver.
*
TECHOST tsm01.clipper-group.com
TECBEGINEVENTLOGGING YES
TECPORT
* NOTE:
* The TECPORT option should be specified ONLY if the Tivoli server
* does NOT have the portmapper running.
*
* TECHOST <hostname>
* Parameters:
* <hostname> - The Tivoli server hostname.
*
* TECBEGINEVENTLOGGING [YES | NO]
* Parameters:
* [YES | NO] - Inform server to ACTIVATE the tivoli receiver
* during startup. This is analogous to issuing
* a BEGIN EVENTLOGGING TIVOLI on the server console.
*
* TECPORT <port number>
* Parameters:
* <port number> - The port number the Tivoli server is listening on.
*
*======================================================================
*
* ACSTIMEOUTX
*
* Specifies the multiple for the build-in timeout value for ACSLS API.
* The build-in timeout value for ACS audit API is 1800 seconds, for
* all other APIs are 600 seconds. If the multiple value specifed is 5,
* the timeout value for audit API becomes 9000 seconds and all other
* APIs becomes 3000 seconds.
*
* Syntax
* +------------------+----------------------------------------------+
* | ACSTIMEOUTX | value |
* +------------------+----------------------------------------------+
*
* Parameters
* value Specifies the multiple for the build-in timeout
* value for ACSLS API. The minimum value is 1, the
* maximum value is 100 and the default is 1.
*
ACSTIMEOUTX 1
*========================================================================
*
* ACSACCESSID
*
* Specifies the id for the ACS access control.
*
* Syntax
* +------------------+----------------------------------------------+
* | ACSACCESSID | name |
* +------------------+----------------------------------------------+
*
* Parameters
* name Specifies the id for the ACS access control.
*
* The default id is hostname. When specified the
* name must be between 1 to 64 in length.
*
ACSACCESSID tsm01
*=======================================================================
**
* ACSLOCKDRIVE
*
* Specifies if the drives within the ACSLS libraries to be locked.
* Drive locking ensures the exclusive use of the drive within the
* ACSLS library in a shared environment. However, there are some
* performance improvements if locking is not performed. If the TSM
* drives are not shared with other applications in the configuration
* then drive locking are not required.
*
* The default is NO
*
* +------------------+----------------------------------------------+
* | ACSLOCKDRIVE | [YES | NO] |
* +------------------+----------------------------------------------+
ACSLOCKDRIVE NO
*=======================================================================
**
* ACSQUICKINIT
*
* Specifies if the initialization of the ACSLS library should be quick
* or full initialization during the server startup.
*
* The full initialization matches the ACSLS inventory with the server
* inventory and validate the locking for each TSM owned volume. It
* also validates the drive locking and dismount all volumes currently
* in the ADSM drive. The full initialization takes about 1-2 seconds
* per volume and can take a long time during the server startup if
* the library inventory is large.
*
* ACSQUICKINIT bypasses all the inventory matching, lock validation and
* volume dismounting from the drive. The user must ensure the integrity
* of the TSM inventory and drive availability, all TSM volumes
* or drives are assumed locked by the same lock_id and available.
* This option is useful for server restart, and should only be used
* if all TSM inventory and resources remain the same while the server
* is down.
*
* The default is NO
*
* +------------------+----------------------------------------------+
* | ACSQUICKINIT | [YES | NO] |
* +------------------+----------------------------------------------+
ACSQUICKINIT NO
* =====================================================================
*
* DISABLESCHEDS
*
* ********************************************************************
*
* Specifies whether administrative and client schedules are disabled
* during an TSM server recovery scenario.
*
* Syntax
* +------------------+----------------------------------------------+
* | DISABLESCheds | Yes | No |
* +------------------+----------------------------------------------+
*
* Parameters
* YES Specifies that the schedule manager is disabled.
*
* NO Specifies that the schedule manager is not
* disabled.
*
* The default value is NO.
*
* NOTE Choose YES if you want to be able to make a simple restore prio 1 instead of a ex. a disaster recovery, then it will become prio 2 instead of prio 1.
* Choose NO ex. you have a disaster recovery the it will keep on being prio 1.
DISABLESCHEDS NO
*
*==============================================================================
*
* REQSYSAUTHFILE
*
* Specifies whether, system authority is required for administrative
* commands that cause * the server to write to an external file.
*
* Syntax
* +-------------------+-----+----+
* | REQSYSauthoutfile | YES | NO |
* +-------------------+-----+----+
*
* Parameters:
* Yes Specifies that system authority is required for
* administrative commands that cause the server to
* write to a file. The commands and associated
* parameters that are controlled by this option are:
*
* - MOVE MEDIA and QUERY MEDIA with CMD parameter
* - BACKUP VOLHISTORY with FILENAMES
* - BACKUP DEVCONFIG with FILENAMES
* - TRACE BEGIN with a file name specified
* - QUERY SCRIPT when the OUTPUTFILE parameter
* has been specified
*
* No Specifies that system authority is not required for
* administrative commands that cause the server to
* write to a file. (i.e. there is no change to the
* privilege class required to execute the command)
*
* The default value is YES.
*
* REQSYSauthfile YES
*==============================================================================
*
* NORETRIEVEDATE
*
* Specifies that the retrieve date of a file in a disk storage pool not be
* updated when the file is restored or retrieved by a client. This option
* can be used in combination with the MIGDELAY storage pool parameter to
* control when files are migrated. If this option is not specified, files
* are migrated only if they have been in the storage pool the minimum number
* of days specified by the MIGDELAY parameter. The number of days is counted
* from the day that the file was stored in the storage pool or retrieved by a
* client, whichever is more recent. By specifying this option, the retrieve
* date of a file is not updated and the number of days is counted only from
* the day the file entered the disk storage pool.
*
* If this option is specified and caching is enabled for a disk storage pool,
* reclamation of cached space is affected. When space is needed in a disk
* storage pool containing cached files, space is obtained by selectively
* erasing cached copies. Files that have the oldest retrieve dates and
* occupy the largest amount of space are selected for removal. When the
* NORETRIEVEDATE option is specified, the retrieve date is not updated when a
* file is retrieved. This may cause cached copies to be removed even though
* they have recently been retrieved by a client.
*
* Syntax
* +----------------+
* | NORETRIEVEDATE |
* +----------------+
*
* Parameters: None.
*
* Examples
* NORETRIEVEDATE
************ Sumarumarun if you make a restore dd. 21-06-04 and the file is original from the 02-01-2003
************Then the new date will be 21-06-04 instead if it is set YES
*==============================================================================
* ASSISTVCRRECOVERY
*
* ********************************************************************
*
* Specifies whether the TSM server will assist the 3570/3590 drive in
* recovering from a lost or corrupted Vital Cartridge Records condition.
*
* Syntax
* +-------------------+----------------------------------------------+
* | ASSISTVCRRECovery | Yes | No |
* +-------------------+----------------------------------------------+
*
* Parameters
* YES Specifies that the server will locate
* directly to the end-of-data to allow the 3570/3590
* drives to restore the VCR.
*
* NO Specifies that the server will not take any
* additional actions.
*
* The default value is YES
*
* Examples
* ASSISTVCRRECOVERY YES
* ASSISTVCRREC Y
*
*==============================================================================
* SELFTUNEBUFpoolsize
*
* ********************************************************************
*
* Specifies whether the server will examine the buffer pool cache
* hit ratio statistics after expiration has been run and adjust the size
* of the buffer pool.
*
* Syntax
* +---------------------+----------------------------------------------+
* | SELFTUNEBUFpoolsize | Yes | No |
* +---------------------+----------------------------------------------+
*
* Parameters
* YES Specifies that the server will reset buffer
* pool cache hit ration statistics before running
* expiration. After expiration has run it will examine
* data base buffer pool cache hit ratio statistics.
* If the hit ratio is less than 98%, it will acquire
* additional memory to increase the size of the
* data base buffer pool. The maximum that will be
* acquired is
* 10% of physical memory on the UNIX Servers and NT.
* 50% of the region size on MVS.
* On NT, additional memory won't be acquired if
* the memory load factor is above 80.
*
* NO Specifies that the server will not attempt
* to adjust the buffer pool size after expiration
* has run and will not reset buffer pool cache
* hit statistics.
*
* The default value is NO
*
*
* SELFTUNEBUF YES
* SELFTUNEBUPOOLSIZE NO
*
*==============================================================================
* SELFTUNEBUFTXNsize
*
* ********************************************************************
*
* Specifies whether the server will adjust the MOVEBATCHSIZE and
* MOVESIZETHRESH options to their maximum values.
*
* Syntax
* +-----------------+----------------------------------------------+
* | SELFTUNETXNsize | Yes | No |
* +-----------------+----------------------------------------------+
*
* Parameters
*
* YES Specifies that the server will adjust the
* MOVEBATCHSIZE and MOVESIZETHRESH options
* to their maximum values to optimize server
* throughput. To prevent running out of log
* space the customer should use the DEFINE
* SPACETRIGGER command to create a log space
* trigger. This will allow for dyanmic
* expansion of the recovery log.
*
* NO Specifies that the server will not attempt
* to adjust the MOVEBATCHSIZE and MOVESIZETHRESH
* options to their maximum values.
*
* The default value is NO
*
SELFTUNETXN YES
SELFTUNETXNSIZE NO
*==============================================================================
* QUERYAuth
*
* ********************************************************************
*
* Specifies the administrative authority level that should be required
* to issue QUERY or SQL SELECT commands. By default any administrator
* can issue a QUERY or SELECT command. If you would like to restrict
* the use of these commands to administrators with a specific
* authority level, this option can be specified with the level of
* authority desired.
*
* Syntax
* +-----------------+-------------------------------------------------------+
* | QUERYAuth | NOne | SYstem | POlicy | STorage | OPerator | ANalyst |
* +-----------------+-------------------------------------------------------+
*
* Parameters
*
* NONE Specifies that any administrator can issue
* QUERY or SELECT commands without requiring
* any administrative authority.
*
* SYSTEM Specifies that administrators must have SYSTEM
* authority to issue QUERY or SELECT commands
*
* POLICY Specifies that administrators must have POLICY
* authority over one or more policy domains
* (or SYSTEM authority) to issue QUERY or SELECT commands
*
* STORAGE Specifies that administrators must have STORAGE
* authority over one or more storage pools
* (or SYSTEM authority) to issue QUERY or SELECT commands
*
* OPERATOR Specifies that administrators must have OPERATOR
* authority (or SYSTEM authority) to issue QUERY or SELECT
* commands
*
* The default value is NONE
*
* Examples
QUERYAUTH SYSTEM
* QUERYAUTH OPERATOR
*
*==============================================================================
* LOGWARNFULLPERCENT
*
* ********************************************************************
*
* Specifies the log utilization threshold at which warning messages
* will be issued.
*
* Syntax
* +------------------------------------------------------------------+
* | LOGWARNFULLPercent | percent |
* +------------------------------------------------------------------+
*
* Parameters
* percent Specifies the percentage of log utilization
* at which warning messages will begin.
* After messages begin, they will be issued for
* every 2% increase in log utilization until
* utilization drops below this percentage.
*
* The default value is 90%
* The mininum value is 0%
* The maximum value is 98%
*
* NOTE the log watch is 512M so that means a warning is recieved if the log file becomes > then 512M (ex. alert at > 256 M)
LOGWARNFULLPERCENT 50
*
*
*==============================================================================
* THROUGHPUTTIMETHRESHOLD
*
* ********************************************************************
*
* Specifies time threshold for a session after which it may be cancelled
* for insufficient throughput.
*
* Syntax
* +------------------------------------------------------------------+
THROUGHPUTTimethreshold 0
* +------------------------------------------------------------------+
*
* Parameters
* minutes Specifies the threshold for examining client
* sessions and cancelling them if the throughput
* threshold is not met ( see the
* THROUGHPUTDATATHRESHOLD option ).
* This threshold does not include time spent
* waiting for media mounts.
* The time threshold
* starts at the time a client sending data
* the server for storage ( as opposed to
* setup or session housekeeping data ).
* A value of 0 prevents examining client sessions
* for insufficient throughput.
*
* The default value is 0
* The mininum value is 0
* The maximum value is 99999999 minutes
*
* NOTE!! we might wanna consider changing that when remote backup is enabled
*
* Examples
* THROUGHPUTTIMETHRESHOLD 90
* Wait until 90 minutes ( plus media wait time )
* after a session has started to
* examine it as a candidate for cancellation due to low
* throughput.
*
* Note: THROUGHPUTTIMETHRESHOLD should be set at higher values than
* either COMMTIMEOUT or IDLETIMEOUT or the throughput threshold
* may unexpectedly cause client sessions to be cancelled.
*==============================================================================
* THROUGHPUTDATATHRESHOLD
*
* ********************************************************************
*
* Specifies throughput threshold that a client session must achieve to
* prevent being cancelled after THROUGHPUTDATATHRESHOLD minutes ( plus
* media wait time ). The time threshold starts at the time a
* client sending data the server for storage ( as opposed to setup or
* session housekeeping data ).
*
* Syntax
* +------------------------------------------------------------------+
THROUGHPUTDatathreshold 0
* +------------------------------------------------------------------+
*
* Parameters
* kilobytespersecond Specifies the throughput that client
* sessions must achieve to prevent cancellation
* after THROUGHPUTTIMETHRESHOLD minutes have elapsed.
* This threshold does not include time spent
* waiting for media mounts.
* A value of 0 prevents examining client sessions
* for insufficient throughput.
* Throughput is computed by adding send and receive
* byte counts and dividing by the length of the
* session. The length does not include time spent
* waiting for media mounts and starts at the time
* a client sends data to the server for storage.
*
* The default value is 0
* The mininum value is 0
* The maximum value is 99999999 kilobytes per second.
*
* NOTE!! We might change that is we have a reallly slow internet line or the internet linje is down on remote sites
*
* Examples
* THROUGHPUTTIMETHRESHOLD 90
* THROUGHPUTDATATHRESHOLD 50
* Wait until 90 minutes ( plus media wait time )
* after a session has started sending data for storage to
* examine it as a candidate for cancellation due to low
* throughput. If a session is not achieving 50 thousand bytes
* per second in transfer rates, it will be cancelled.
*==============================================================================
*
* SEARCHMPQUEUE (NOTE this is used if you wan't to backup files in a specific order on Linux/unix !!!this can not be used in a Windows env.
*
* Specifies that the server, when examining the mount point queue for a mount
* request to satifify, will first look to dispatch a request that needs an
* already mounted volume. The selected request may be dispatched before
* other request on the mount point queue even though they have been waiting
* longer for a mount point.
*
* With this option specified, when looking for the next mount request to
* service, the server will first look to see if any request on the mount
* point queue needs a currently mounted volume. If so, it will dispatch
* the request and the request will begin.
*
* Without this option specfied the server satisfies request on the mount
* point queue as first-come first-served.
*
*
* Syntax:
* +----------------+
* | SEARCHMQUEUE |
* +----------------+
*
* Parameters: None.
*
* Examples:
* SEARCHMPQUEUE
*==============================================================================
*
*DBPAGESHADOW
*
* Specifies whether database page shadowing is enabled. If database page
* shadowing is enabled, Tivoli Storage Manager mirrors every write to a
* database page. You can enable shadowing only if database volume mirrors
* are written to in parallel (that is, the MIRRORWRITE DB option is set to
* PARALLEL). The default is YES.
*
* Syntax
*
* DBPAGEShadow Yes|No
*
DBPAGEShadow Yes
*
* Parameters
*
* Yes
* Perform page shadowing.
*
* No
* Do not perform page shadowing.
*
* Examples
*
* dbpageshadow no
*
*
* DBPAGESHADOWFILE
*
* Specifies the name of the file to use for database page shadowing. If
* database page shadowing is enabled, the page shadow either goes to the
* default file or is created in the directory that the server is running
* from. The default file, dbpgshdw.bdt, resides in the directory where the
* server is installed.
*
* Syntax
*
* DBPAGESHADOWFILE dbpgshdw.bdt|file_name
*
*
* Parameters
*
* file_name
* Specifies the name of the file in which the database page shadow is
* stored.
*
* Examples
*
dbpageshadowfile shadow.bdt
* You
