Andy,
Your suspicion was correct. I displayed the line with "od" options that cause
each byte to be displayed as both a character and an unsigned integer. The
integer value for the character in front of the drive letter turned out to be
150 (en-dash in the Latin I code page) rather than the correct 45. The Windows
system administrator used Notepad to delete the en-dash and insert an ASCII
hyphen. Once this was done the GUI started with no error messages.
Thank you for your assistance.
Thomas Denier
Thomas Jefferson University
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Andrew Raibeck
Sent: Friday, March 20, 2015 12:29 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Problem with "domain" option
No bugs with DOMAIN processing that I am aware of that could cause this. My
first guess would be that the character preceding the 'h' is not an ASCII minus
sign character (0x2D), but some kind of typographical hyphen or dash.
Suggestions:
* Open the dsm.opt file with a bona fide plain text editor (not a word
processor or editor that might default to non-plain text behavior). Remove the
offending line, and carefully type it in manually (no copy & paste from other
source). Then see if the problem persists.
* Send me the dsm.opt file and I'll have a look at it. If you go this route but
don't send it today, I won't be able to get back to you until the following
week.
Regards,
- Andy
____________________________________________________________________________
Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead | storman AT
us.ibm DOT com
IBM Tivoli Storage Manager links:
Product support:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager
Online documentation:
http://www.ibm.com/support/knowledgecenter/SSGSG7/welcome
Product Wiki:
https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2015-03-20
11:03:24:
> From: Thomas Denier <Thomas.Denier AT JEFFERSON DOT EDU>
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: 2015-03-20 11:06
> Subject: Problem with "domain" option
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> We have a client system running 64 bit Windows 2008 and using TSM 7.
> 1.1.0 client code. An H drive that does not need backup coverage was
> recently added to the system. The system administrator added the
> following line to dsm.opt:
>
> domain ALL-LOCAL -h:
>
> The GUI client claims that this line is invalid and "helpfully"
> offers to turn it into a comment line. The line is almost identical to
> one of the examples in the Windows client manual; the only difference
> is specifying "-h:" rather than the "-c:" in the example.
> I have used a Windows port of the Linux "od" utility to verify that
> the only non-printing characters in dsm.opt are the normal line end
> characters. The option is apparently acceptable to the client
> scheduler service; the service will start and remain started with the
> option in effect. I don't know how the option affects scheduled
> backups; the system administrator has accepted the "helpful" offer
> from the GUI a number of times, and has managed to coordinate
> acceptance of the offer with scheduler service restarts in such a way
> that the option has never been in effect during a scheduled backup.
>
> Is there something genuinely wrong with the "domain" option, or some
> quirk in the GUI's validity checking that we can work around (for
> example, stricter rules about capitalization or extra white space than
> the scheduler service and the documentation)?
>
> Thomas Denier
> Thomas Jefferson University
> The information contained in this transmission contains privileged and
> confidential information. It is intended only for the use of the
> person named above. If you are not the intended recipient, you are
> hereby notified that any review, dissemination, distribution or
> duplication of this communication is strictly prohibited. If you are
> not the intended recipient, please contact the sender by reply email
> and destroy all copies of the original message.
>
> CAUTION: Intended recipients should NOT use email communication for
> emergent or urgent health care matters.
>
The information contained in this transmission contains privileged and
confidential information. It is intended only for the use of the person named
above. If you are not the intended recipient, you are hereby notified that any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact the
sender by reply email and destroy all copies of the original message.
CAUTION: Intended recipients should NOT use email communication for emergent or
urgent health care matters.
|
