Author: Joe Cascanette <Joe.Cascanette AT CUMIS DOT COM>
Date: Tue, 12 Mar 2002 11:00:13 -0500
Server 4.2.1.12 - Windows 2000 Client 4.2.1.20 - Windows 2000 I am having problem launching macros at the server under scheduling. I create a schedule: DEFINE SCHEDULE STANDARD AUTOMATION DESCRIPTION
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Tue, 12 Mar 2002 11:10:24 -0500
Try fully qualifying the macro name, i.e. OBJECTS='"C:\Program Files\Tivoli\TSM\baclient\database.mac"' (assuming you installed TSM to directory "C:\Program Files\Tivoli\TSM".) Note the use of double
Author: Marc Levitan <marc.levitan AT PFPC DOT COM>
Date: Tue, 12 Mar 2002 11:10:08 -0500
Joe, I believe the macro have to be located in the "saclient" directory. Try that... Marc Levitan Storage Manager PFPC Global Fund Services Joe Cascanette <Joe.Cascanette@ To: ADSM-L AT VM.MARIST DOT
Author: Joe Cascanette <Joe.Cascanette AT CUMIS DOT COM>
Date: Tue, 12 Mar 2002 11:17:26 -0500
In lower versions of ADSM I have used this directory (saclient), however there is no directory with my current version of TSM. I will create this directory and put the macros in there to see what hap
Author: Marc Levitan [mailto:marc.levitan AT PFPC DOT COM]
Date: Sun, 04 Oct 2015 17:10:42 -0500
Joe, I believe the macro have to be located in the "saclient" directory. Try that... Marc Levitan Storage Manager PFPC Global Fund Services Joe Cascanette <Joe.Cascanette@ To: ADSM-L AT VM.MARIST DOT
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Tue, 12 Mar 2002 11:27:09 -0500
An update to my last response: I think the real problem is that you are trying to launch a server macro from a client schedule (I didn't catch that the first time around). How about defining an admin
Author: "Rushforth, Tim" <TRushfor AT CITY.WINNIPEG.MB DOT CA>
Date: Tue, 12 Mar 2002 10:27:38 -0600
Does the macro run outside of the schedule? You have a typo in your select - not sure if that typo is actually in your macro! select process form processes
Author: Joe Cascanette [mailto:Joe.Cascanette AT CUMIS DOT COM]
Date: Sun, 04 Oct 2015 17:10:42 -0500
Server 4.2.1.12 - Windows 2000 Client 4.2.1.20 - Windows 2000 I am having problem launching macros at the server under scheduling. I create a schedule: DEFINE SCHEDULE STANDARD AUTOMATION DESCRIPTION
Author: Joe Cascanette <Joe.Cascanette AT CUMIS DOT COM>
Date: Tue, 12 Mar 2002 12:18:47 -0500
I have searched through the admin ref guide and there is no mention on how to "Fully-Qualify" this marco. Any docs that would point this out? Thanks Joe
Author: Andrew Raibeck [mailto:storman AT US.IBM DOT COM]
Date: Sun, 04 Oct 2015 17:10:42 -0500
An update to my last response: I think the real problem is that you are trying to launch a server macro from a client schedule (I didn't catch that the first time around). How about defining an admin
Author: Rushforth, Tim [mailto:TRushfor AT CITY.WINNIPEG.MB DOT CA]
Date: Sun, 04 Oct 2015 17:10:42 -0500
Does the macro run outside of the schedule? You have a typo in your select - not sure if that typo is actually in = your macro! select process form processes
Author: Joe Cascanette <Joe.Cascanette AT CUMIS DOT COM>
Date: Tue, 12 Mar 2002 13:15:01 -0500
I found some Docs on this, thanks for the idea. This way I dont have to keep restarting the client scheduler on the sever. Ill post if I have any other problems Joe
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Tue, 12 Mar 2002 13:44:38 -0500
By "fully-qualify", I mean to spell out the full path to the macro. That is, don't just use database as there is no implicit extension that I am aware of. You need to specify the .mac extension as we
Author: Joe Cascanette <Joe.Cascanette AT CUMIS DOT COM>
Date: Tue, 12 Mar 2002 14:27:02 -0500
Yep, got it working. I created all the macros as scripts. And just defined a schedule type=admin CMD='run databasecheck', this works fine. I am still working on error checking and testing, but here a
Author: Andrew Raibeck [mailto:storman AT US.IBM DOT COM]
Date: Sun, 04 Oct 2015 17:10:42 -0500
By "fully-qualify", I mean to spell out the full path to the macro. That is, don't just use database as there is no implicit extension that I am aware of. You need to = specify the .mac extension as