ADSM-L

Re: CLIENTACTION Command

2006-01-25 18:44:58
Subject: Re: CLIENTACTION Command
From: William Boyer <bjdboyer AT COMCAST DOT NET>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 25 Jan 2006 18:45:36 -0500
Actually.... Q EV * @*  will filter only the clientaction events.


Bill Boyer
"Some days you're the bug, some days you're the windshield" - ??

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
John Monahan
Sent: Wednesday, January 25, 2006 5:54 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: CLIENTACTION Command

The command should be "q event * *".  Sorry about that.


______________________________
John Monahan
Senior Consultant Enterprise Solutions
Computech Resources, Inc.
Office: 952-833-0930 ext 109
Cell: 952-221-6938
http://www.computechresources.com




John Monahan/Computech
01/25/2006 11:01 AM

To
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> cc

Subject
Re: CLIENTACTION Command






"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 01/25/2006 
05:46:40 AM:

> Hi to all
>
> I am using the command DEFINE CLIENTACTION to schedule a client to
process
> a command for a one-time action. The command i am giving is as follow:
>
> define clientaction BIZTALK-DAILY domain=BIZTALK_DAILY action=command
> object='"C:\TSMUSER\PROD\WNA1BZT.bat"' wait=yes
>
> On the client side i have the following settings about the tsm
scheduler:
>
> Prompted
> - TCP/IP address:localhost
> - TCP/IP port: 1501
> - session Init.:server only
>
> The above command is defined successfully but the job
> C:\TSMUSER\PROD\WNA1BZT.bat is not executed at once. Do i have to
> change something?
>

After you define the clientaction, do a "query sched * *" from the server and 
look for a client schedule that starts with @ and
numbers after it, like @045 for BIZTALK-DAILY.  See what the status of the 
schedule is - repeat the command for a few minutes.
Also, the clientaction isn't exactly immediate, it may take one or two minutes. 
 If the clientaction actually runs, or says in
process then the server is contacting the client correctly.  From there, you'll 
have to check the dsmsched.log on the client and
possibly dsmerror.log on the client to check for client side errors.  If the 
server never contacts the client correctly then
something is wrong in the setup of your client and/or scheduler service (ie the 
immediateaction stays in pending status until it
times out).





______________________________
John Monahan
Senior Consultant Enterprise Solutions
Computech Resources, Inc.
Office: 952-833-0930 ext 109
Cell: 952-221-6938
http://www.computechresources.com

<Prev in Thread] Current Thread [Next in Thread>