Chris,

The error log message "10/04/2003 15:08:37 ANS1076E *** Directory path not
found ***" is what I would expect for this kind of problem. Since the
"archmc" option was not preceded by a hyphen, TSM interpreted it as a file
specification. Since you have no file by that name, it generated the
ANS1076E message. If, when you run the archive, you redirect stdout to a
file, then somewhere in that file you would also see the message.

By the way, as of 5.1, you can also test the return code from dsmc (from a
script check %errorlevel% or if you just enter the command manually, when
dsmc ends issue "echo %errorlevel%"). It would have ended with a return
code of '12' due to the error message. That is another means of gauging
the success of the operation.

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.




Chris Murphy <cmurphy AT IDL.STATE.ID DOT US>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
10/06/2003 08:51
Please respond to "ADSM: Dist Stor Manager"

        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Archives not bound to correct MC ?


>I imagine that your problem is due to a missing hyphen (-) in front of
the
"archmc" option.


Thanx Andy!  Is now a good time to remove my foot from my own *** ?  Yes,
I
checked the script file and you were correct!  However, the only logs in
the
DSMERROR.LOG file anywhere near the time the archive ran are:

10/04/2003 15:04:04 ConsoleEventHandler(): Caught Ctrl-C console event .
10/04/2003 15:04:04 ConsoleEventHandler(): Cleaning up and terminating
Process ...
10/04/2003 15:08:37 ANS1076E *** Directory path not found ***

It is a Monday isn't it...

Chris