-Alan-
This might be why you are getting these errors in the dsmerror.log: Within
one dsmc session, 3 consequentive query backups are issued with quotes
surrounding the filespeciation with a wildcard and the 2nd query command
uses the options -todate and -fromdate.
For example:
# dsmc -se=ewathens
ADSTAR Distributed Storage Manager
Command Line Backup Client Interface - Version 3, Release 1, Lev
(C) Copyright IBM Corporation, 1990, 1998, All Rights Reserved.
dsmc> q backup "/home/ericka/d*"
Node Name: <EDITED> established with server ADSM: AIX-RS/6000
Server Version 3, Release 1, Level 1.3
Server date/time: 06/24/1998 10:00:20 Last access: 06/24/1998
Size Backup Date Mgm A/I File
25 06/23/1998 17:11:56 DEFAULT A /home/ericka/dsm.opt
973 06/23/1998 17:11:56 DEFAULT A /home/ericka/dsm.opt.smp
43,600 06/24/1998 09:48:33 DEFAULT A /home/ericka/dsmerror.30
461 06/24/1998 09:48:33 DEFAULT A /home/ericka/dsmerror.lo
dsmc> q backup "/home/ericka/d*" -fromdate=06/23/1998
-todate=06/24/1998
Size Backup Date Mgm A/I File
25 06/23/1998 17:11:56 DEFAULT A /home/ericka/dsm.opt
973 06/23/1998 17:11:56 DEFAULT A /home/ericka/dsm.opt.smp
43,600 06/24/1998 09:48:33 DEFAULT A /home/ericka/dsmerror.30
461 06/24/1998 09:48:33 DEFAULT A /home/ericka/dsmerror.lo
dsmc> q backup "/home/ericka/d*"
ANS1102E Excessive number of command line arguments passed to
the program!
ANS1133W An expression might contain a wildcard not enclosed
in quotes
dsmc> quit
Local Fix:
1. Do not use the quotes around the file specification.
2. Place a space behind the closing quote for the 3rd query.
Thanks,
Demetrius Malbrough
TSM Consultant
-----Original Message-----
From: Sulzer, Alan [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 09, 2001 8:49 AM
To: [EMAIL PROTECTED]
Subject: Errors in the DSMerror.log file.... Help
I am getting the following errors in the /dsmerror.log file constantly. If
any one has an idea why this seems to be happening, I am all ears.
ANS1102E Excessive number of command line arguments passed t
o the program!
ANS1133W An expression might contain a wildcard not enclosed
in quotes
They seemed to start up all of a sudden. My UNIX adminer removed some of
the data so it is relatively impossible to state with 100% accuracy what
changed on the systems that could have caused this.
Does any one have any idea what is causing this? Here is some more details
if you need them. We have no dsmc client listener processes running on the
client box for either nodes. We have two node names defined on the TSM
server for the client host. One node name is defined for the normal client
and the other node name is defined for the TDP API client. I believe the
TSM adminer has tried to expire or disable the node from the policy domains
so as to render them inactive.
Any help would be appreciated.
Alan Sulzer
Informix DBA
Unity Health
(314) 364-3164
[EMAIL PROTECTED]
