ADSM-L

ADSM V3.1 - client options invalid in cloptset, move media

1997-12-23 07:23:25
Subject: ADSM V3.1 - client options invalid in cloptset, move media
From: Tom Brooks <tbrooks AT VNET.IBM DOT COM>
Date: Tue, 23 Dec 1997 04:23:25 PST
 Yes, due to a variety of client related reasons, the client options
as listed in hard copy pubs are not in sync with reality. I believe
the readme file with the PTFs should have the correct list. In answer
to your question:
1) Schedlogretention is not available as cloptset member.
2) Include and Exclude have been replaced with the following:
  Define clientopt namex INCLEXCL "include c:\date\*"
  or
  Define clientopt namex INCLEXCL "exclude c:\data\*"

 This change was made to allow for sequencing on INCLEXCL instead of
on INCLUDE or EXCLUDE. This allows for interweaving of INCLUDE and
EXCLUDE as would nornally be found in the client DSM.OPT file. The
client will strip off the INCLEXCL. Note the option value must be
enclosed in quotes. I know the INCLEXCL is usually used to indicate
a file containing more INC/EXC statements. This is still true, the
only difference being that when the INCLEXCL is used in a cloptset
the client will use it in the manner described above.

 Below is what I believe to be the current options available for use
in cloptset processing. More may be delivered at a later date:

BOOKS
CHANGINGRETRIES
COMPRESSALWAYS
COMPRESSION
DIRMC
DOMAIN
DOTDIRCHECK
DSMCDEFAULTCOMMAND
INCLEXCL
MAXCMDRETRIES
MEMORYEFFICIENTBACKUP
NFSTIMEOUT
POSTNSCHEDULECMD
POSTSCHEDULECMD
PRENSCHEDULECMD
PRESCHEDULECMD
QUERYSCHEDPERIOD
QUIET
RETRYPERIOD
RUNASSERVICE
SCHEDMODE
SCROLLLINES
SCROLLPROMPT
SLOWINCREMENTAL
SUBDIR
TAPEPROMPT
TRACEFLAGS
TRACEMAX
TXNBYTELIMIT
VERBOSE

 NOTE: Some options like verbose and quiet may now require a value
       of YES/NO or ON/OFF when used in the cloptset:
       define clientopt namex verbose yes


Tom Brooks
ADSM Server Development
<Prev in Thread] Current Thread [Next in Thread>