ADSM-L

Re: Retry: Server Clientoptionset Confusion

2001-10-23 16:08:31
Subject: Re: Retry: Server Clientoptionset Confusion
From: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Tue, 23 Oct 2001 13:05:33 -0700
I do not know why you are seeing this problem, although you are running at
fairly back-level code.

Some things to check:

Do you have more than one TSM server? If so, are you sure the probem
client is connecting to the server you think it is connecting to?

Did you confirm that the problem node is indeed associated with the
desired cloptset (QUERY NODENAME nodename FORMAT=DETAILED)?

If you do a QUERY STATUS, what does it show for the scheduling mode? If
it is set to PROMPTED, then that will over-ride whatever you put in the
cloptset or dsm.sys.

Do you have any non-AIX clients? If so, do they experience this problem?
If the problem seems clearly to be with the AIX clients, consider
upgrading one of the problem clients to the 4.1.3 level, and see if it
makes any difference.

If everything looks okay and nobody else here has any other ideas, then
you should open up a problem with support.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Steven Chaba <Steven_Chaba AT RGE DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
10/23/2001 11:47
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Retry: Server Clientoptionset Confusion



I sent this last week, to a response of deafening silence. Am I doing
something wrong here, or do I not understand how these are supposed to
work?



Server: TSM 4.1.0.0 running on H70 with AIX 4.3.3 ML8
Client: Various, running TSM for AIX 4.1.0.0


If I execute the following commands:

Session established with server ADSM: AIX-RS/6000
  Server Version 4, Release 1, Level 0.0
  Server date/time: 10/12/01   12:31:15  Last access: 10/12/01   08:10:29


tsm: ADSM>define cloptset test1
ANR2046I DEFINE CLOPTSET: Optionset TEST1 defined.

tsm: ADSM>define clientopt test1 compression yes force=yes
ANR2050I DEFINE CLIENTOPT: Option COMPRESSION defined in optionset TEST1.

tsm: ADSM>q cloptset test1

Optionset                     Description                   Last Update by
Managing profile
 (administrator)
-------------------------     ------------------------- ---------------
--------------------
--------------------
TEST1                                                       CHABA
TEST1                                                       CHABA

Option                        Sequence     Override     Option Value
                                number
-------------------------     --------     --------
------------------------------------------------------------
------------------------------------------------------------
COMPRESSION                          0          Yes     yes
COMPRESSION                          0          Yes     yes


It would seem to me that if I specify FORCE=YES, that would equate to
OVERRIDE=NO, based on the descriptions in the docs (TSM for AIX Admin Ref,
GC35-0404-00, pages 134-136 and 618).


Now, consider my production environment:

We use a single cloptset on our server, and define it to virtually all of
our client nodes. See below:

tsm: ADSM>q cloptset clientoptionset

Optionset                     Description                   Last Update by
Managing profile
 (administrator)
-------------------------     ------------------------- ---------------
--------------------
--------------------
CLIENTOPTIONSET               Unix and Desk Top client      ADMIN
CLIENTOPTIONSET               Unix and Desk Top client      ADMIN
                               option sets

Option                        Sequence     Override     Option Value
                                number
-------------------------     --------     --------
------------------------------------------------------------
------------------------------------------------------------
CHANGINGRETRIES                      0          Yes     4
CHANGINGRETRIES                      0          Yes     4
COMPRESSION                          0           No     no
MAXCMDRETRIES                        0          Yes     2
RETRYPERIOD                          0          Yes     20
SCHEDMODE                            0           No     polling
TAPEPROMPT                           0           No     no
TXNBYTELIMIT                         0          Yes     25600


Yet, I use SCHEMODE PROMPTED in the dsm.sys file of all my AIX clients,
and
they in fact run prompted, when this cloptset shouldn't allow that. On the
other hand, this option set *should* allow local overriding of the
CHANGINGRETIRES option, but any attempt to do so on several of my client
machines seems to be ignored.

I'm now officially confused. Any and all guidance would be appreciated.

Steven Chaba
Lead Analyst
Rochester Gas & Electric Corporation
Rochester, NY
716.771.2137 v
<Prev in Thread] Current Thread [Next in Thread>